CERTIFICATE

This is to certify that [Student Name], a student of Class 12, has successfully completed the project
titled "[Project Name]" as part of the Computer Science curriculum under the guidelines provided
by the Central Board of Secondary Education (CBSE).

The project was carried out under the supervision of [Teacher’s Name], and it has been duly
submitted as a requirement for the Computer Science Examination of Class 12.

Signature of Teacher: _____________________

 TABLE OF CONTENTS
S. No. DESCRIPTION PAGE NO

1. ACKNOWLEDGEMENT

2. INTRODUCTION

3. OBJECTIVES OF THE PROJECT

4. PROPOSED SYSTEM

5. SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)

6. PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE

7. FLOW CHART

8. SOURCE CODE

9. OUTPUT

10. TESTING

11. HARDWARE AND SOFTWARE REQUIREMENTS

12. BIBLIOGRAPHY
 ACKNOWLEDGEMENT

I would like to express my sincere gratitude to all those who have contributed to the successful
completion of my project titled "[Project Name]" in Computer Science for Class 12.

First and foremost, I would like to thank my project guide, [Teacher's Name], for their invaluable
guidance, constant support, and expert advice throughout the course of this project.

I also wish to extend my thanks to the Head of the School, Ms Rekha Sharma, for the support and
for providing the resources necessary to complete this project.

I am deeply grateful to my family and friends for their continuous encouragement and
understanding. Their patience and motivation have kept me focused throughout the process.

Finally, I would like to thank the Central Board of Secondary Education (CBSE) for providing the
framework and guidelines that made this project possible.

This project is the result of collective efforts, and I acknowledge all the contributions that have
helped me in its successful completion.

[Your Name]

Class 12 A, Computer Science

 Introduction of the Project
Write about project in around 200 words.
 OBJECTIVES OF THE PROJECT
Write about objective of project in around 200 words
 SYSTEM DEVELOPMENT LIFE CYCLE

The Systems Development Life Cycle (SDLC) is a project management technique that

divides complex projects into smaller, more manageable segments or phases. Segmenting

projects allows managers to verify the successful completion of each phase before allocating

resources to the subsequent ones. Software development projects typically include the

initiation, planning, design, development, testing, implementation, and maintenance phases.

However, these phases may be organized differently depending on the organization involved.

For example, initial project activities might be categorized 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 that the system is being built to deliver the required 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 the business accomplishments of the

organization or address 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 necessity of technology—i.e., will a change in the business process offer a
solution?
- Ensure executive business and 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 its relationship to the agency/organization.
- Address 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. Careful oversight is required to ensure that
projects support strategic business objectives and that resources are effectively integrated into an
organization's enterprise architecture.

The Initiation Phase starts when an opportunity to add, improve, or correct a system is identified
and formally requested through the presentation of a business case. The business case should, at a
minimum, describe the proposal’s purpose, identify expected benefits, and explain how the
proposed system supports one of the organization’s business strategies.

The business case should also identify alternative solutions and detail as many informational,
functional, and network requirements as possible.

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, and Develop 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 by Agency 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

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 assesses 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.

 FLOW CHART
Draw and explain the flow chart of the project.
 SOURCE CODE

Write down the project Python Source code as well as MySQL tables’ structures and queries
related to the project if required.
 OUTPUT
Mention the output or output screen shots of the project
 TESTING
Software Testing is an empirical investigation conducted to provide With Information about
the quality of the product or service under test stakeholders a with respect to the context
which it is intended to operate. Software Testing also provides an objective, independent
view of the software to allow the business to appreciate and understand the risks at
implementation of the software. Test techniques include, but are not limited to, the process of
executing a program or application with the intent of finding software bugs. It can also be
stated as the process of validating and verifying that a software program/application/product
meets the business and technical requirements that guided its design and development, so that
it works as expected and can be implemented with the same characteristics. Software Testing,
depending on the testing method employed, can be implemented at any time in the
development process, however the most test effort is employed after the requirements have
been defined and coding process has been completed.

TESTING METHODS
Software testing methods are traditionally divided into black box testing. These one
approaches are used to describe the point of view that a test engineer takes when designing
test cases.

BLACK BOX TESTING

Black box testing treats the software as a "black box, without any knowledge of internal
implementation. Black box testing methods include: equivalence partitioning, boundary
value analysis, all-pairs testing, fuzz testing, model-based testing, traceability matrix,
exploratory testing and specification-based testing.

SPECIFICATION-BASED TESTING

Specification-based testing aims to test the functionality of software according to the

applicable requirements. Thus, the tester inputs data into, and only sees the output from the
test object. This level of testing usually requires through test cases to be provided to the
tester, who they test that for a given input. The output value (or behaviour), either RUUPE
value specified in the test case. Specification-based testing is necessary, but it is insufficient
to guard against certain risks.
ADVANTAGES AND DISADVANTAGES

The black box tester has no "bonds" with the code, and a tester's perception is very simple: a
code must have bugs using the principle. "Ask and you shall receive." black box testers find
bugs where programmers don't. But, on the other hand, black box testing has been said to be
like a walk in a dark labyrinth without a flashlight, because the tester doesn't know how the
software being tested was actually constructed. That's why there are situations when (1) a
black box tester writes many test cases to check something that can be tested by only one test
case, and/or (2) some parts of the back end are not tested at all. Therefore, black box testing
has the advantage of "an unaffiliated opinion," on the one hand, and the disadvantage of
"blind exploring," on the other.
HARDWARE AND SOFTWARE REQUIREMENTS

Recommended System Requirements:

Processors: Intel® Core™ i3 processor 4300M at 2.60 GHz. RAM: 2 to 4 GB.
Operating systems: Windows® 10, MACOS, and UBUNTU. Python Versions: 3.10.2 or
Higher.
With [Link] module installed MYSQL Versions: 8.0.28 or
Higher.

Minimum System Requirements Processors: Intel Atom® processor or Intel®

Core™ i3 processor. Disk space: 512 GB to 1TB.
Operating systems: Windows 8 or later, MACOS, and UBUNTU.
Python Versions: 2.7.X, 3.6.X

Prerequisites before installing MySQL Connector Python

You need root or administrator privileges to perform the installation process. Python must be
installed on your machine.
Note: – MySQL Connector Python requires python to be in the system’s PATH. Installation
fails if it doesn’t find Python.

On Windows, If Python doesn’t exist in the system’s PATH,

Please manually add the directory containing [Link] yourself

 BIBLIOGRAPHY

1. [Link]
2. Preeti Arora and Sumita Arora Python
Class 12 Book
3. [Link]
4. Google