COMPUTER SCIENCE

PROJECT REPORT
ON QUIZ SOFTWARE MANAGEMENT
COMPUTER SCIENCE

FOR
CLASS XII

(2023-24)
Submitted in partial fulfillment of the requirement of CBSE, Delhi.

[Link]

UNDER THE GUIDANCE OF

[Link] PRIYA M.C.A.,M.E.,[Link].,
(P.G.T Computer Science)

Mahatma Global Gateway

(CBSE)
Gopalakrishnan Guruvasal,Veerapanchan,
Madurai-625020.

1
 ACKNOWLEDGEMENT

At the outset I would like to take the opportunity of expressing

my sincere thanks to the Almighty for keeping me in good health all
through this grueling project work.

I would like to express my special thanks to my worthy

Academic Director [Link] Priya, Principal Mrs. Meena
Karuppiah and to my teacher guide [Link] Priya who provided
motivation and valuable guidance to complete this project.

I got ample opportunity to do research which enriched my

knowledge and widen my thoughts in this arena. I am indebted to
them.

I would also like to thank my parents and friends who always

inspired and helped me to complete this project.

Signature of the student

1
 CERTIFICATE

This is to certify that [Link] of class XII of Mahatma Global

Gateway (CBSE), Madurai, has completed his project file as a part of
the paper of computer science under my supervision. He has taken
proper care and shown utmost sincerity in the completion of this
project.

I certify that this project is up to my expectation and as per the

guidelines issued by CBSE.

Signature of the Principal Signature of the Teacher In-charge

([Link] Karuppiah) ([Link] Priya)

Submitted for the viva-voce examination held on , at

Mahatma Global Gateway (CBSE), Madurai.

Signature of the Examiner

1
 TABLE OF
CONTENTS

[Link] DESCRIPTION PAGE NO

01 ACKNOWLEDGEMENT 1

02 INTRODUCTION 3

03 OBJECTIVES OF THE PROJECT 3

04 PROPOSED SYSTEM 4

05 HARDWARE AND SOFTWARE REQUIREMENTS 5

06 SYSTEM DEVELOPMENT LIFE CYCLE (SDLC) 6

07 PHASES OF SYSTEM DEVELOPMENT LIFE 7

CYCLE

08 SOURCE CODE 15

09 OUTPUT 18

10 TESTING 22

11 BIBLIOGRAPHY 25

2
 PROJECT ON QUIZ SOFTWARE
MANAGEMENT SYSTEM

INTRODUCTION

Quiz is a wonderful way to test one’s knowledge . But when it comes to

storing the data is a structured and schematic way it is a hectic task so in order

to tackle this problem we must have a data management system for this ,so

this work of software management will not only help you to store the data but

will also help youto maintain a detailed record of your quiz programme.

OBJECTIVES OF THE PROJECT

The objective of this project is to allow the management to maintain a

cleanand structured detail of their quiz programme.

Write programs utilizing modern software tools.

1. Apply simple principles effectively when developing small to medium

sized projects.

2. Write effective procedural code to store small to medium sized information.

3. Students will demonstrate a breadth of knowledge in computer science, as

exemplified in the areas of systems, theory and software development.

4. Students will demonstrate ability to conduct a research or applied

Computer Science project, requiring writing and presentation skills which

exemplify scholarly style in computer science.

3
PROPOSED SYSTEM

Today one cannot afford to rely on the fallible human beings of be really

wants to stand against today’s merciless competition where not to wise saying

“to err is human” no longer valid, it’s outdated to rationalize your mistake. So,

to keep pace with time, to bring about the best result without malfunctioning

and greater efficiency so to replace the unending heaps of flies with a much

sophisticated hard disk of the computer.

One has to use the data management software. Software has been an

ascent in atomization various organisations. Many software products working

are now in markets, which have helped in making the organizations work easier

and efficiently. Data management initially had to maintain a lot of ledgers and a

lot of paper work has to be done but now software product on this organization

has made their work faster and easier. Now only this software has to be loaded

on the computer and work can be done.

This prevents a lot of time and money. The work becomes fully

automated and any information regarding the organization can be obtained by

clicking the button. Moreover, now it’s an age of computers of and automating

such an organization gives the better look.

4
 HARDWARE AND SOFTWARE REQUIREMENTS

HARDWARE REQUIREMENTS

I. OPERATING SYSTEM : WINDOWS 7 AND ABOVE

II. PROCESSOR : PENTIUM(ANY) OR AMD

ATHALON(3800+- 4200+ DUAL

CORE)

III. MOTHERBOARD : 1.845 OR 915,995 FOR PENTIUM 0R MSI

K9MM-V VIA K8M800+8237R

PLUS CHIPSET FOR AMD

ATHALON

IV. RAM : 512MB+

V. Hard disk : SATA 40 GB OR ABOVE

VI. CD/DVD r/w multi drive combo: (If back up required)

VII. FLOPPY DRIVE 1.44 MB : (If Backup required)

VIII. MONITOR 14.1 or 15 -17 inch

IX. Key board and mouse

X. Printer : (if print is required – [Hard copy])

SOFTWARE REQUIREMENTS:

I. Windows OS
II. Python

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

6
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 andthe 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,
7
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.

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
8
 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’ sjob is to coordinate discussions
between user, audit, security, design, development, and network personnel to
9
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 alevel 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 MasterPlan.

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,
10
 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 scriptprograms during the
development phase. Program designs are c onstructed in various ways. Using a
top-down approach, designers first identify and link majorprogram 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.

11
 Performing a security risk assessment.
Developing a conversion plan to migrate current data to the new
[Link] 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 [Link] completion of the
12
 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.

13
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
functionalrequirements continue to be satisfied.
Determine when the system needs to be modernized, replaced, or retired.

FLOWCHART

14
 SOURCE CODE

import [Link]

mydb=[Link](host="localhost",user="root",pass

wd="manager",database="quiz_comp")

mycursor=[Link]()

#[Link]("create table questions1(qno_no int(3) primary key ,

qno_desc varchar(10000),opt_a varchar(500), opt_b varchar(500), opt_c

varchar(500) ,opt_d varchar(500) , ans varchar(5000))")

print("QUIZ SOFTWARE")

print("[Link]") print("[Link]")

print("[Link] update") print("[Link]")

choice=int(input("enter your wish:"))if

choice==1:

sql=int(input("enter the index_no:"))

sql1=input("enter the ques_desc:")

sql2=input("enter the option a:")

sql3=input("enter the option b:")

sql4=input("enter the option c:")

sql5=input("enter the option d:")

sql6=input("the answer is:")

15
 sql_in= "insert into questions1 values(" + str( sql) +",'" +

(sql1)+ "'"+",'" + (sql2) + "'"+",'" + (sql3) +"'"

+",'"+ (sql4) +"'"+",'" + (sql5) +"'"+ ",'"+(sql6) +"'"")"

[Link](sql_in)

[Link]()

print("your request has been [Link] you formaking us as a

part of your project")

#[Link]("create table participants(reg_no int(5) primary

key, pname varchar(50) ,age_group int(10),city

varchar(50),no_of_appearances_made int(10))")

if choice==2:

sql6=int(input("enter the participant reg_no:"))

sql7=input("enter the participant name:")

sql8=int(input("enter the age group:")) sql9=input("enter

the city:")

sql10=int(input("enter the no of appearances made:"))

sql_int="insert into participants values("+ str(sql6)+ ",'" + (sql7) +

"'" + ",'"+str(sql8) + "'" + ",'"+(sql9) +"'"+ ",'"+str(sql10)+"'"")"

print(sql_int) [Link](sql_int)

print("participants are all updated")

[Link]()

16
 #[Link]("create table scores(reg_no int(5)

primary key , participant_name varchar(50), scores

int(50),total_correct int(50), total_wrong

int(50), total_attempted int(50))")

if choice==3:

a=int(input("enter the reg_no")) b=input("enter the

participants name") c=int(input("enter the scores"))

d=int(input("enter the total correct answer"))

e=int(input("enter the incorrect answer"))

f=int(input("enter the no_of_attempted_questions"))

sql_insert="insert into scores values("+ str(a) +",'"+ (b)

+"'"+",'"+ str(c)+"'"+",'"+ str(d) +"'"+ ",'"+str(e)

+"'"+",'"+ str(f)+ "'"")"

print(sql_insert)

[Link](sql_insert)

[Link]()

if choice==4:

[Link]("select * from questions1")

data=[Link]()

print(data)

17
OUTPUT

18
19
20
21
 TESTING

Software Testing is an empirical investigation conducted to provide

stakeholders with information about the quality of the product or service under
test[1], with respect to the context in 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
and white box testing. These two 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.

22
 SPECIFICATION-BASED TESTING
Specification-based testing aims to test the functionality of software
according to the applicable requirements.[16] Thus, the tester inputs data into, and
only sees the output from, the test object. This level of testing usually requires
thorough test cases to be provided to the tester, who then can simply verify that
for a given input, the output value (or behaviour), either "is" or "is not" the same
as the expected 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.

WHITE BOX TESTING

White box testing, by contrast to black box testing, is when the tester has
access to the internal data structures and algorithms (and the code that implement
these).

Types of white box testing:-

The following types of white box testing exist:
api testing - Testing of the application using Public and Private APIs.
23
 Code coverage - creating tests to satisfy some criteria of code
coverage.
For example, the test designer can create tests to cause all statements in
the program to be executed at least once.
fault injection methods.
mutation testing methods.
static testing - White box testing includes all static testing.

CODE COMPLETENESS EVALUATION

White box testing methods can also be used to evaluate the completeness
of a test suite that was created with black box testing methods. This allows the
software team to examine parts of a system that are rarely tested and ensures that
the most important function points have been tested.

Two common forms of code coverage are:

Function Coverage: Which reports on functions executed and
Statement Coverage: Which reports on the number of lines
executed to complete the test?
They both return coverage metric, measured as a percentage

24
 BIBLIOGRAPHY

1. Computer science With Python - Class XI &XII By : PreetiArora

2. Head-First Python’(2nd Edition) By: Paul Barry

3. Python Programming: An Introduction to Computer Science

(3rd Edition) By John Zelle

4. Website: [Link]

***

25