SHAHEED PATH, LUCKNOW

COMPUTER SCIENCE

PROJECT

CLASS : XII
SESSION : 2021 - 22

Submitted To:
Mr. Sarman Singh

Submitted By:

Mridul Rastogi Hardik Raj Kapoor

XII - A XII - A
(2021-22) (2021-22)
Roll no. Roll no.
 Acknowledgement
We would like to express our special thanks of gratitude

to our teacher Mr. Sarman Singh PGT (COMPUTER

SCIENCE), for his vital support, guidance and

encouragement – without which this practical (TERM-

2) would not have come forth.

We would also like to express our gratitude to our

principal Mrs. Poonam Kochitty and our school Seth

Anandram Jaipuria School, Lucknow for giving us this

opportunity to make this project.

We are making this project not only to increase marks

but also to gain knowledge.

THANKS AGAIN TO ALL WHO HELPED US.

 SHAHEED PATH, LUCKNOW

Certificate
This is to certify that Mridul Rastogi
and Hardik Raj Kapoor students of
class XII - Seth Anandram Jaipuria
School has successfully completed the
project during the academic year 2021-
22 towards partial fulfillment of
Computer Science examination
conducted by CBSE.

Teacher's Signature Principal's Signature External Examiner's

Signature
 Index
XII CS – PRACTICAL ASSIGNMENTS FOR TERM 2
S.No. Description of Assignment Sign

1. Brief Overview

2. Input Data and Validation of Project

3. Software and hardware Requirements

4. Characteristics of DBMS

5. Different Types of files: - Based on Access

6. Need of Computerization

7. Merits

8. Demerits

9. System Development Life Cycle (SDLC)

10. Phases of Cycle Development

11. Pictorial Representation of SDLC

12. SQL Command Line

13. Python Source Code

14. Output

15. Future Enhancements

16. Hardware and software Requirements

17. Bibliography

 Bill Management

BRIEF OVERVIEW
Bill management system is developed using python.
While using this bill management system we can easily
calculate total bill of the customer.
Moreover, the total bill is calculated including service
charge and state tax.
All you have to do is to just fill the questions asked by
the computer with item and quantities. The program
will display your total bill with number of items
purchased. There is no error and warning content in
this project. This design is so simple that user won’t find
it difficult to use and navigate.

INPUT DATA AND VALIDATION OF

PROJECT
 All the fields such as sales payments discounts are
validated and do not
 take invalid values.
 Each form of sales, discounts, stock cannot accept
the blank values.
 Avoiding errors in data.
 Controlling amount of given data.
 SOFTWARE AND HARDWARE
REQUIREMENTS

Data file handling: Has been effectively used in the

program. The database is a collection of interrelated
data to serve multiple applications. That is database
programs create files of information. So, we see that files
are worked with most, inside the program.

DBMS: The software required for the management of

data is called as DBMS. It
has 3 models:
 Relation model
 Hierarchical model
 Network model

RELATIONAL MODEL: It’s based on the concept on

relation. Relation is the table that consists of rows and
columns. The rows of the table are called tuple and the
columns of the table are called attribute. Numbers of
rows in the table is called as
cardinality. Number of columns in the table is called as
degree.
HIERARCHICAL MODEL: In this type of model, we have
multiple records for each record. A particular record has
one parent record. No chide record can exist without
parent record. In this, the records are organized in tree.

NETWORK MODEL: In this, the data is represented by

collection of records and Relationship is represented by
(link or association).

CHARACTERISTICS OF DBMS
 It reduces the redundancy
 Reduction of data in inconsistency
 Data sharing
 Data standardization

DIFFERENT TYPES OF FILES: -BASED ON

ACCESS
 Sequential file
 Serial file
 Random (direct access) file BASED ON STORAGE: -
 Text file
 Binary File
 Need of computerization
Bill management is a python-based project and we have
developed bill management system using MySQL and
MySQL connector. It is easy to operate and understand by
users. The calculations of bills are done in a short period
of time and it’s not time consuming. It ensures accurate
records and minimizes the inevitable and costly errors
with manual data enter.
This accurate data helps to provide accurate
performance and payroll data. Most bill management
system is built around highly secure system and highly
reliable and secure and can help prevent time theft and
administrative costs stemming. With just few clicks we
can generate accurate reports on hours worked.
Software programs constantly evolve. A program used
today may be obsolete within several years. Being trained
on today software does not guarantee it will be used
when you are ready to go out into the field.
Understanding calculations is timeless, as is computer
competency. Software, however, shifts rapidly.

Merits
 It generates the report on the number of items
purchased by customer.
 Provides filter report on payments, inventory and
products.
 We can easily export PDF on products sold.
 Applications can also provide excel export for sales
and discounts.
 It deals with monitoring the information and
transaction of products.
 It increases the efficiency of managing sales and
discount.
 It has higher efficiency of editing, adding and
updating of records.
 Provides the searching facilities on various factors

Demerits
 Excel export has not been developed for products
sold.
 The transactions are executed in offline mode only.
 Online transactions for sales, discounts, or other
data modifications are not possible.
 Offline reports of sales, products, discounts and
stocks cannot be generated due to batch mode
execution.
SYSTEM DEVELOPMENT LIFE CYCLE
(SDLC)

The systems development life cycle is a project

management technique that divides complex projects
into smaller, more easily managed segments or
phases. Segmenting projects allows managers to
verify the successful completion of project phases
before allocating resources to subsequent phases.
Software development projects typically include
initiation, planning, design, development, testing,
implementation, and maintenance phases. However,
the phases may be divided differently depending on
the organization involved.
For example, initial project activities might be
designated as request, requirements-definition, and
planning phases, or initiation, concept-
development, and planning phases. End users of the
system under development should be involved in
reviewing the output of each phase to ensure the
system is being built to deliver the needed
functionality.

PHASES OF SYSTEM DEVELOPMENT

LIFE CYCLE
 INITIATION PHASE

The Initiation Phase begins when a business sponsor

identifies a need or an opportunity. The purpose of
the Initiation Phase is to:
• Identify and validate an opportunity to improve
business accomplishments of the organization or
a deficiency related to a business need.
• Identify significant assumptions and constraints
on solutions to that need.
• Recommend the exploration of alternative
concepts and methods to satisfy the need
including questioning the need for technology,
i.e., will a change in the business process offer
a solution?
• Assure executive business and executive
technical sponsorship. The Sponsor designates a
Project Manager and the business need is
documented in a Concept Proposal. The Concept
Proposal includes information about the
business process and the relationship to the
Agency/Organization.
• Infrastructure and the Strategic Plan. A
successful Concept Proposal results in a Project
Management Charter which outlines the
authority of the project manager to begin the
project.
 SYSTEM CONCEPT DEVELOPMENT PHASE

The System Concept Development Phase begins after

a business need or opportunity is validated by the
Agency/Organization Program Leadership and the
Agency/Organization CIO.
The purpose of the System Concept Development Phase
is to:
• Determine the feasibility and appropriateness of
the alternatives.
• Identify system interfaces.
• Identify basic functional and data requirements to
satisfy the business need.
• Establish system boundaries; identify goals,
objectives, critical success factors, and
performance measures.
• Evaluate costs and benefits of alternative
approaches to satisfy the basic functional
requirements
• Assess project risks
• Identify and initiate risk mitigation actions,
andDevelop high-level technical architecture,
process models, data models, and a concept of
operations. This phase explores potential
technical solutions within the context of the
business need.
• It may include several trade-off decisions such as
the decision to use COTS software products as
opposed to developing custom software or
reusing software components, or the decision to
use an incremental delivery versus a complete,
onetime deployment.
• Construction of executable prototypes is
encouraged to evaluate technology to support
the business process. The System Boundary
Document serves as an important reference
document to support the Information
Technology Project Request (ITPR) process.
• The ITPR must be approved by the State CIO before
the project can move forward
.
PICTORIAL REPRESENTATION OF SDLC

 PLANNING PHASE:
 The planning phase is the most critical step in
completing development, acquisition, and
maintenance projects. Careful planning,
particularly in the early stages of a project, is
necessary to coordinate activities and manage
project risks effectively. The depth and formality
of project plans should be commensurate with the
characteristics and risks of a given project. Project
plans refine the information gathered during the
initiation phase by further identifying the specific
 activities and resources required to complete a
project.
 A critical part of a project manager’s job is to
coordinate discussions between user, audit, security,
design, development, and network personnel to
identify and document as many functional, security,
and network requirements as possible. During this
phase, a plan is developed that documents the
approach to be used and includes a discussion of
methods, tools, tasks, resources, project schedules,
and user input. Personnel assignments, costs, project
schedule, and target dates are established.
 A Project Management Plan is created with
components related to acquisition planning,
configuration management planning, quality
assurance planning, concept of operations, system
security, verification and validation, and systems
engineering management planning.
 REQUIREMENTS ANALYSIS PHASE
This phase formally defines the detailed functional
user requirements using high- level requirements
identified in the Initiation, System Concept, and
Planning phases. It also delineates the requirements in
terms of data, system performance, security, and
maintainability requirements for the system. The
requirements are defined in this phase to a level of
detail sufficient for systems design to proceed. They
need to be measurable, testable, and relate to the
business need or opportunity identified in the
Initiation Phase.
The requirements that will be used to determine
acceptance of the system are captured in the Test and
Evaluation Master Plan.
 The purposes of this phase are to:

 Further define and refine the functional and

data requirements and document them in the
Requirements Document,
 Complete business process reengineering of the
functions to be supported (i.e., verify what
information drives the business process, what
information is generated, who generates it,
where does the information go, and who
processes it),
 Develop detailed data and process models (system
inputs, outputs, and the process.
 Develop the test and evaluation
requirements that will be used to
determine acceptable system performance.
 • DESIGN PHASE:

The design phase involves converting the

informational, functional, and network requirements
identified during the initiation and planning phases
into unified design specifications that developers use
to script programs during the development phase.
Program designs are constructed in various ways.
Using a top-down approach, designers first identify
and link major program components and interfaces,
then expand design layouts as they identify and link
smaller subsystems and connections. Using a bottom-
up approach, designers first identify and link minor
program components and interfaces, then expand
design layouts as they identify and link larger
systems and connections.
Contemporary design techniques often use
prototyping tools that build mock-up designs of items
such as application screens, database layouts, and
system architectures. End users, designers, developers,
database managers, and network administrators
should review and refine the prototyped designs in an
iterative process until they agree on an acceptable
design. Audit, security, and quality assurance
personnel should be involved in the review and
approval process. During this phase, the system is
designed to satisfy the functional requirements
identified in the previous phase. Since problems in the
design phase could be very expensive to solve in the
later stage of the software development, a variety of
elements are considered in the design to mitigate risk.

 These include:
• Identifying potential risks and defining mitigating
design features.
• Performing a security risk assessment.
• Developing a conversion plan to migrate current
data to the new system.
• Determining the operating environment.
• Defining major subsystems and their inputs and
outputs.
• Allocating processes to resources.
• Preparing detailed logic specifications for each
software module. The result is a draft System
Design Document which captures the preliminary
design for the system.
• Everything requiring user input or approval is
documented and reviewed by the user. Once these
documents have been approved by the Agency CIO
and Business Sponsor, the final System Design
Document is created to serve as the
Critical/Detailed Design for the system.
• This document receives a rigorous review
byAgency technical and functional
representatives to ensure that it satisfies the
business requirements. Concurrent with the
development of the system design, the Agency
Project Manager begins development of the
Implementation Plan, Operations and
Maintenance Manual, and the Training Plan.
• Developing a conversion plan to migrate current
data to the new system.
• Determining the operating environment.
• Defining major subsystems and their inputs and
outputs.
• Allocating processes to resources.
• Preparing detailed logic specifications for each
software module. The result is a draft System
Design Document which captures the
preliminary design for the system.
• Everything requiring user input or approval is
documented and reviewed by the user. Once
these documents have been approved by the
Agency CIO and Business Sponsor, the final
System Design Document is created to serve as
the Critical/Detailed Design for the system.
• This document receives a rigorous review
byAgency technical and functional
representatives to ensure that it satisfies the
business requirements. Concurrent with the
development of the system design, the Agency
 Project Manager begins development of the
Implementation Plan, Operations and
Maintenance Manual, and the Training Plan.

 DEVELOPMENT PHASE:
The development phase involves converting design
specifications into executable programs. Effective
development standards include requirements that
programmers and other project participants
discuss design specifications before programming
begins. The procedures help ensure programmers
clearly understand program designs and functional
requirements. Programmers use various techniques
to develop computer programs. The large
transaction-oriented programs associated with
financial institutions have traditionally been
developed using procedural programming
techniques. Procedural programming involves the
line-by-line scripting of logical instructions that are
combined to form a program. Effective completion
 of the previous stages is a key factor in the success
of the Development phase.

 The Development phase consists of:

• Translating the detailed requirements and design
into system components.
• Testing individual elements (units) for usability.
• Preparing for integration and testing of the IT
system.

INTEGRATION AND TEST PHASE:

Subsystem integration, system, security, and user
acceptance testing is conducted during the
integration and test phase. The user, with those
responsible for quality assurance, validates that the
functional requirements, as defined in the functional
requirements document, are satisfied by the
developed or modified system. OIT Security staff
assess the system security and issue a security
certification and accreditation prior to
installation/implementation.
 Multiple levels of testing are performed,
including:

• Testing at the development facility by the

contractor and possibly supported by end users
• Testing as a deployed system with end users
working together with contract personnel
• Operational testing by the end user alone
performing all functions. Requirements are
traced throughout testing, a final Independent
Verification & Validation evaluation is
performed and all documentation is reviewed
and accepted prior to acceptance of the system.
 IMPLEMENTATION PHASE:

This phase is initiated after the system has been

tested and accepted by the user. In this phase, the
system is installed to support the intended business
functions. System performance is compared to
performance objectives established during the
planning phase. Implementation includes user
notification, user training, installation of hardware,
installation of software onto production computers,
and integration of the system into daily work
processes. This phase continues until the system is
operating in production in accordance with the
defined user requirements.
 OPERATIONS AND MAINTENANCE PHASE:

The system operation is ongoing. The system is

monitored for continued performance in accordance
with user requirements and needed system
modifications are incorporated. Operations continue
as long as the system can be effectively adapted to
respond to the organization’s needs. When
modifications or changes are identified, the system
may reenter the planning phase.

 The purpose of this phase is to:

 Operate, maintain, and enhance the system.

 Certify that the system can process sensitive
information.
 Conduct periodic assessments of the system to
ensure the functional requirements continue to be
satisfied.
 Determine when the system needs to be modernized,
replaced, or retired.
 SQL Command Line:

 Python Source Code:

 OUTPUT:
To get output: press f5

Future enhancements

 The process of gathering information, diagnosing the

problems, then interpreting facts is known as System
analysis. It also includes recommending system
improvements needed, based on the same data.

 The system is observed as a whole; the inputs need to

be identified firstly before turning them and then the
system is subjected to study as a whole to identify the
problem areas.
 Although tunings any system is a complex procedure,
but tuning individual statements is not the best as
something that is correct for one input may hurt
another inputs performance.

 The solutions are given as a proposal. The suggestion

is revised on user request and optimal changes are
made. This loop terminates as soon as the user is
gratified with the proposal.

 So, on the whole, system analysis is done to improve

the system performance by monitoring it and
obtaining the best through put possible from it.
Therefore, system analysis plays a crucial role in
designing any system.
 SHAHEED PATH, LUCKNOW

Bibliography
HARDWARE AND SOFTWARE REQUIREMENTS:
Software Required:
Windows OS
Python
References I used:
Website References
Computer Class XII Books