A “COMPUTER SCIENCE” PROJECT FILE

SUBMITTED TO

CAMPION SCHOOL
BHOURI HUZUR BHOPAL MP-462030

DEPARTMENT OF

COMPUTER SCIENCE
ON SPECIALISATION OF
QUIZ GAME
AISSCE – 25

IN THE ACADEMIC SESSION 2024-25

SUBMITTED BY: – SUBMITTED TO: –
Atharva Mehta MR. AMIT KUMAR VERMA (HOD)
CLASS: 11th A (PGT - COMPUTER SCIENCE)

ROLL NO: 21

CAMPION SCHOOL
 BHOURI HUZUR BHOPAL MP-462030

CERTIFICATE
This is to certify that Atharva Mehta Roll No: 21 has successfully
completed the project Work entitled “QUIZ GAME” in the subject
COMPUTER SCIENCE (083) laid down in the regulations of CBSE for the
purpose of Practical Examination in Class XI to be held in Campion School
Bhouri Bhopal.

Approved By Permitted By

Mr. Amit kumar Verma Fr. Amritlal Toppo, S.J.

(PGT COMPUTER SCIENCE) PRINCIPAL

CAMPION SCHOOL
BHOURI HUZUR BHOPAL MP-462030
 DECLARATION

I hereby declare that the work is being presented in the project file on the
specialization of "Contact Management System" in partial fulfillment of the
requirement for the subject of XI Class, Computer Science (083), is an authentic record
of our own work carried out under the able guidance of MR. AMIT KUMAR VERMA
SIR.

The work has been carried out at CAMPION SCHOOL, BHOURI

HUZUR BHOPAL.

I here declare that above statement is correct to the best of my

knowledge.

(Student Name)

(Subject)

(Class)

KNOWLEDGEMENT
I express our deep sense of gratitude to my respected and learned guide Mr. Amit
Kumar Verma sir for their valuable help and guidance.

I am grateful to my respected Principal Fr. Amritlal Toppo, S.J., Campion School,

Bhouri, Huzur, Bhopal for permitting me to select Computer Science and utilize all the
necessary facilities of the institution.

I am also thankful to all the faculty & staff members of our School for their kind co-
operation and help.

Lastly, I would like to express my deep appreciation towards my classmates and my

indebtedness to my parents for providing us the moral support and encouragement.

Student Name

Class
 About the Project
What is the use of contact book?

Contact Book helps in organizing, managing and sharing contacts so

relevant people always have access to the right contacts.

Back up & sync device contacts by saving them as

contacts:

Contacts lists' windows show screen names that represent

actual other people. To communicate with someone on the list, the user can select a name and
act upon it, for example open a new E-mail editing session, instant message, or telephone call.
In some programs, if your contact list shows someone, their list will show yours. Contact lists
for mobile operating systems are often shared among several Apps.

The advantage of saving contacts

By saving your contacts in Gmail, you are making sure that even if you lose diary, your
contacts will always be backed up there. You will just have to sign in your new mobile with the
same Gmail account and all your contacts will be back.
 INTRODUCTION TO PYTHON

Python is an interpreted, object-oriented, high-level programming language with dynamic

semantics. Its high-level built in data structures, combined with dynamic typing and dynamic
binding, make it very attractive for Rapid Application Development, as well as for use as a
scripting or glue language to connect existing components together. Python language is
simple, has easy to learn syntax ,emphasizes readability and therefore reduces the cost of
program maintenance. Python supports modules and packages, which encourages program
modularity and code reuse. The Python interpreter and the extensive standard libraries are
available in source or binary form without charge for all major platforms, and can be freely
distributed.

Its official website is :

Hyperlink : Welcome to Python.org

Url address : https://www.python.org/
History of Python:
Python is a widely used general-purpose, high-
level programming language. It was initially
designed by Guido van Rossum in 1991 and
developed by Python Software Foundation. It
was mainly developed for emphasis on code
readability, and its syntax allows programmers
to express concepts in fewer lines of code.
 SYSTEM DEVELOPMENT LIFECYCLE (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 typically includes 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.
Careful oversight is required to ensure projects support strategic business
objectives and resources are effectively implemented into an organization's
enterprise architecture. The initiation phase begins 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 a
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.
 THE SYSTEM CONCEPT DEVELOPMENT
PHASE
The System Concept Development Phase begins after a business need or
opportunity 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 technol solutions within the context of the business
need.
 It may include several trade-off decisions such as decision to use COST
software products as opposed to developing custom software or reusing
software components, or the to use an incremental delivery versus a complete
onetime development.
 Construction of 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.
 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 system 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 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 identity 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 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.
 SOURCE CODE
||Program Menu ||
||1..Add Contact Number ||
||2..Update Contact Number||
||3..Delete Contact Number||
||4..Search Contact Number||
||5..Show Contact ||
||6..Exit Contact Apps ||

ANSWER:
phoneDict = {}
choice = 0
print("Created dictionary is:")
print(phoneDict)
while True:
print("||Program Menu ||")
print("||1..Add Contact Number ||")
print("||2..Update Contact Number||")
print("||3..Delete Contact Number||")
print("||4..Search Contact Number||")
print("||5..Show Contact ||")
print("||6..Exit Contact Apps ||")
choice = int(input("Enter Your Choice : "))
if choice == 1:
pName = input("Enter Person Name")
pContact = input("Enter Contact Number")
phoneDict[pName] = pContact
# print(phoneDict)
elif choice == 2:
pName = input("Enter Person Name")
pContact = input("Update Contact Number")
if pName in phoneDict:
phoneDict[pName] = str(pContact)
print(pName, " contact has been updated with ",
pContact, " Number")
else:
print("This Person Not in your Contact List")
elif choice == 3:
pName = input("Enter Person Name")
if pName in phoneDict:
phoneDict.pop(pName)
print(pName, " contact has been Successfully
deleted")
else:
 print("This Person is Not in your Contact List")
elif choice == 4:
pName = input("Enter Person Name")
if pName in phoneDict:
print(pName, " contact is :", phoneDict[pName])
else:
print("This Person is Not in your Contact List")
elif choice == 5:
print("Person Name & Contact Number")
for x in phoneDict.keys():
print(x, " : ", phoneDict[x])
elif choice == 6:
print("Thank you for using our ContactApps")
break
 OUTPUT SCREEN
||Program Menu ||
||1..Add Contact Number ||
||2..Update Contact Number||
||3..Delete Contact Number||
||4..Search Contact Number||
||5..Show Contact ||
||6..Exit Contact Apps ||

||Program Menu ||

||1..Add Contact Number ||

||2..Update Contact Number||

||3..Delete Contact Number||

||4..Search Contact Number||

||5..Show Contact ||

||6..Exit Contact Apps ||

Enter Your Choice : 1

Enter Person NameRohit

Enter Contact Number9866654789

||Program Menu ||

||1..Add Contact Number ||

||2..Update Contact Number||

||3..Delete Contact Number||

||4..Search Contact Number||

||5..Show Contact ||

||6..Exit Contact Apps ||

Enter Your Choice : 1

Enter Person NameAkash

Enter Contact Number8877885512

||Program Menu ||

||1..Add Contact Number ||

||2..Update Contact Number||

||3..Delete Contact Number||

||4..Search Contact Number||

||5..Show Contact ||

||6..Exit Contact Apps ||

Enter Your Choice : 5

Person Name & Contact Number

Rohit : 9866654789

Akash : 8877885512

||Program Menu ||

||1..Add Contact Number ||

||2..Update Contact Number||

||3..Delete Contact Number||

||4..Search Contact Number||

||5..Show Contact ||

||6..Exit Contact Apps ||

Enter Your Choice : 2

Enter Person NameAkash

Update Contact Number8877885533

Akash contact has been updated with 8877885533 Number

||Program Menu ||

||1..Add Contact Number ||

||2..Update Contact Number||

||3..Delete Contact Number||

||4..Search Contact Number||

||5..Show Contact ||

||6..Exit Contact Apps ||

Enter Your Choice : 4

Enter Person NameRohit

Rohit contact is : 9866654789

||Program Menu ||

||1..Add Contact Number ||

||2..Update Contact Number||

||3..Delete Contact Number||

||4..Search Contact Number||

||5..Show Contact ||

||6..Exit Contact Apps ||

Enter Your Choice : 3

Enter Person NameRohit

Rohit contact has been Successfully deleted

||Program Menu ||

||1..Add Contact Number ||

||2..Update Contact Number||

||3..Delete Contact Number||

||4..Search Contact Number||

||5..Show Contact ||

||6..Exit Contact Apps ||

Enter Your Choice : 3

Enter Person NameAmit

This Person is Not in your Contact List

||Program Menu ||

||1..Add Contact Number ||

||2..Update Contact Number||

||3..Delete Contact Number||

||4..Search Contact Number||

||5..Show Contact ||

||6..Exit Contact Apps ||

Enter Your Choice : 6

Thank you for using our ContactApps

Process finished with exit code 0

 SYSTEM REQUIREMENTS

HARDWARE REQUIREMENT:

 Printer- to print the required documents of the

project.
 Compact Drive
 Proccesor: Pentium IV and above
 RAM: 1 GB (minimum)
 Hard-Disk : 20 GB (minimum)

SOFTWARE REQUIREMENT:

 Windows 7 or higher
 My-SQL server 5.5 or higher (as back end)
 Python idle 3.6 or higher or spyder (as front
end).
 Microsoft Word 2010 or higher for
documentation.
 BIBLIOGRAPHY

BOOKS:

 NCERT Computer Science Textbook for Class XI and XII

-By NCERT
 COMPUTER SCIENCE WITH PYTHON
- BY SUMITA ARORA
 COMPUTER SCIENCE WITH PYTHON
-BY PREETI ARORA
 PYTHON COOKBOOK

WEBSITES:
 www.geeksforgeeks.org
 https://docs.python.org/3/
 https://www.w3schools.com/python/
 https://www.youtube.com/channel/
UCGe2Q-fWpU9MoxcygLZ-R2A/playlists