GITARATTAN JINDAL PUBLIC

SCHOOL
PROJECT REPORT ON
QUIZ SOFTWARE MANAGEMENT SYSTEM

PROJECT REPORT ON
QUIZ SOFTWARE MANAGEMENT SYSTEM

ROLL NO :
NAME : VANIKA SADANA AND SMRITI LUTHRA
CLASS : XII
SUBJECT : INFORMATICS PRACTICES
SUB CODE : 065

PROJECT GUIDE: Mrs. PRABHJOT KAUR

 TABLE OF CONTENTS [ T O C ]
SER DESCRIPTION PAGE NO
01 ACKNOWLEDGEMEN 04
T

02 INTRODUCTION 05

03 OBJECTIVES OF THE 05
PROJECT

04 PROPOSED SYSTEM 06
05 SYSTEM 07

DEVELOPMENT LIFE
CYCLE (SDLC)

06 PHASES OF SYSTEM 08
DEVELOPMENT LIFE
CYCLE

07 FLOW CHART 15

08 SOURCE CODE 16

09 OUTPUT 19

10 TESTING 20

11 HARDWARE AND 23
 SOFTWARE
REQUIREMENTS
12 BIBLIOGRAPHY 24
PROJECT ON QUIZ SOFTWARE
MANAGEMENT SYSTEM

INTRODUCTION:
Quizzes are a great way to test one's knowledge. But when it comes
to storing the data it is a structured and planned way, it is a busy job
so to deal with this problem we must have a data management
system for it, so this job of software management is not only for you
will help to store the data but will also help you to maintain a
detailed record of your quiz schedule. let's start!!!!!
OBJECTIVES OF THE PROJECT:
The purpose of this project is to allow management to maintain
a clean and structured description of its quiz schedule. Write
programs using modern software tools.
1. Apply simple principles effectively when developing small to
medium sized projects.
2. Write efficient procedural code for storing small to medium
sized information.
3. Students will demonstrate broad knowledge in computer
science, as exemplified in the areas of systems, theory and
software development.
4. Students will demonstrate the ability to conduct a research or
applied computer science project that requires writing and
presentation skills that exemplify the scholarly style in computer
science.

PROPOSED SYSTEM
No one can afford to rely on humans today to really stand up
against today's ruthless competition, where not being wise that
"it's human to make a mistake" is no longer valid, it's your fault
to rationalize old for. Therefore, in order to keep pace with the
times, to bring the best results without malfunction and more
efficiency so that endless piles of flies can be replaced with a
very sophisticated hard disk of the computer.
Data management software has to be used. Software has been
an ascent in the atomization of various organizations. Many
working software products are now in the markets, which have
helped the organizations to work easily and efficiently. Data
management initially had to maintain a lot of ledgers and a lot
of paper work but now the software product of this organization
has made their work faster and easier. Now just load this
software in computer and work can be done.
This saves a lot of time and money. The work becomes fully
automated and any information regarding the organization can
be accessed at the click of a button. Also, now it is the era of
computers and automating this kind of organization gives a
better look.
SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)

The systems development lifecycle is a project management

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

PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE

INITIATION PHASE
The initiation phase begins when a business sponsor identifies a need
or opportunity.
The purpose of the Initiation Phase is to:
1. Identify and validate an opportunity to improve the organization's
business achievements or shortfalls related to business need.
2. Identify key assumptions and constraints to address that need.
3. Recommend exploring alternative concepts and methods to meet
the need, including questioning the need for technology, i.e., would
a change in business process provide a solution?
4. Assure executive business and executive technical sponsorship.
5. The sponsor nominates a project manager and the business
requirement is documented in a concept proposal. The concept
proposal includes information about the business process and
relationship to the agency/organization.
6. Infrastructure and Strategic Planning. A successful concept
proposal results in a project management charter that outlines the
project manager's authority to initiate project.
Careful oversight is required to ensure that projects support strategic
business objectives and that resources are effectively implemented
across an organization's enterprise architecture. The initiation phase
begins when an opportunity to add, improve or improve a system is
identified and formally requested through the presentation of a
business case. The business case should, at a minimum, describe the
purpose of the proposal, identify the expected benefits, and explain
how the proposed system supports one of the organization's
business strategies. The business case should 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 the
agency/organization program leadership and the
agency/organization CIO confirm the business need or opportunity.
The purpose of the System Concept Development Phase is to:

• Determine the feasibility and suitability of alternatives.

• Identify system interfaces.
• Identify basic functional and data requirements to meet business
needs.
• Establish system limits; Identify goals, objectives, critical success
factors and performance measures.
• Evaluate the costs and benefits of alternative methods to meet
basic functional needs
• Assess Project Risks
• Identify and initiate risk mitigation actions, and develop high-level
technical architecture, process models, data models and operations
concepts. This phase explores possible technical solutions in the
context of the business requirement.
• This may include a number of 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 distribution versus a full, one-time deployment .

PICTORIAL REPRESENTATION OF SDLC:

PLANNING PHASE
The planning phase is the most important step in completing
development, acquisition and maintenance projects. Careful
planning, especially in the initial stages of a project, is essential for
coordinating activities and managing 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
information gathered during the initiation phase by identifying
specific activities and resources needed to complete a project.
An important part of a project manager's job is to coordinate
discussions between user, audit, security, design, development and
network personnel to identify and document functional, security and
network requirements as closely 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
schedules and target dates are established.
A project management plan has been created with the components
related to the concept of acquisition plan, configuration
management plan, quality assurance plan, Operations, Systems
Security, Verification and Verification, and Systems Engineering
Management Planning.

REQUIREMENTS ANALYSIS PHASE

This phase formally defines detailed functional user requirements
using the high-level requirements identified in the initiation, system
concept, and planning phases. It also delineates the requirements for
the system in terms of data, system performance, security and
maintenance requirements. Requirements are defined at this stage
to a level of detail sufficient for system design to proceed. They need
to be measurable, testable and related to the business need or
opportunity identified at an early stage. The requirements that will
be used to determine acceptance of the system are included in the
Testing and Evaluation Masterplan.
The purposes of this phase are to:
 1. Further define and refine functional and data requirements and
document them in the requirements document,
2. Complete business process reengineering of what needs to be
supported (ie, verify what information drives the business
process, what information is generated, who generates it,
where the information goes, and who processes it ),
3. Develop detailed data and process models (system input,
output and process.
4. Develop 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 integrated design specifications that developers
use to script programs during the development phase. Program
designs are prepared in a variety of ways. Using a top-down
approach, designers first identify and link major program
components and interfaces, then expand the design layout as they
identify and link smaller subsystems and connections. Using a
bottom-up approach, designers first identify and link smaller
program components and interfaces, then expand the design layout
as they identify and link larger systems and connections.
Contemporary design techniques often use prototyping tools that
create simulated designs of objects such as application screens,
database layouts, and system architecture. End users, designers,
developers, database managers and network administrators must
review and refine prototype designs in an iterative process until an
acceptable design is agreed. Audit, safety and quality assurance
personnel should be involved in the review and approval process.
During this phase, the system is designed to meet the functional
requirements identified in the previous phase. Since it can be very
costly to solve problems in the design phase at a later stage of
software development, various elements are considered in the
design to reduce the risk. These include:
1. Identifying potential risks and defining design features that
reduce them.
2. Performing a security risk assessment.
3. Develop a conversion plan for migrating the existing data to the
new system.
4. Determination of the operating environment.
5. Defining the major subsystems and their inputs and outputs.
6. Allocation of processes to resources.
7. Preparation of detailed logic specifications for each software
module. The result is a draft system design document that
captures the initial design for the system.
8. Everything that requires user input or approval is documented
and reviewed by the user. Once these documents are approved
by the agency CIO and business sponsor, a final system design
document is created to serve as the critical/detailed design for
the system.
9. This document receives a rigorous review by the agency's
technical and functional representatives to ensure that it meets
business requirements. Along with developing the system
design, the agency project manager begins development of the
implementation plan, operation and maintenance manual, and
training plan.

DEVELOPMENT PHASE
The development phase involves converting the design
specifications into executable programs. Effective development
standards include requirements that programmers and other
 project participants discuss on design specifications before
programming begins. Processes help ensure that programmers
clearly understand program design and functional requirements.
Programmers use different techniques to develop computer
programs. Large transaction-oriented programs involving financial
institutions have traditionally been developed using procedural
programming techniques. Procedural programming involves line-
by-line scripting of logical instructions that are combined to form a
program. Effective completion of the previous phases is an
important factor in the success of the development phase. Stages
of development include:
1. Translating detailed requirements and designs into system
components.
2. Testing individual elements (units) for usability.
3. IT system integration and testing preparation.

INTEGRATION AND TEST PHASE

Subsystem integration, systems, security and user acceptance testing
is conducted during the integration and testing phase. The user,
together with those responsible for quality assurance, confirms that
the functional requirements, as defined in the functional
requirements document, are satisfied by the system developed or
modified. OIT security personnel assess system security and issue
security certification and accreditation prior to
installation/implementation.
Several levels of testing are performed, including:
1. Tested at a development facility by the contractor and possibly
supported by end users
2. Testing as a deployed system with end users working closely
with contract personnel
 3. Operational testing by the single end user performing all the
tasks. Requirements are ascertained during testing, a final
independent verification and validation assessment is carried
out and all documents are reviewed and accepted prior to
system acceptance.

IMPLEMENTATION PHASE
This phase is initiated after the system has been tested and accepted
by the user. In this step, the system is set up to support the intended
business functions. System performance is compared with
performance objectives established during the planning phase.
Implementation includes user notification, user training, installation
of hardware, installation of software on production computers, and
integration of the system into daily work processes. This phase
continues until the system is operating in production as per the
defined user requirements.

OPERATIONS AND MAINTENANCE PHASE

System operation continues. Systems are monitored for continuous
performance as per user requirements and necessary system
modifications are incorporated. Operations continue as long as the
system can be effectively adapted to respond to the needs of the
organization. When modifications or changes are identified, the
system can re-enter the planning phase.
The purpose of this step is to:
● System operation, maintenance and improvement.
● Prove that the system can process sensitive information.
● Conduct periodic evaluations of the system to ensure it
continues to satisfy functional requirements.
 ● Determine when the system needs to be modernized, replaced
or retired.

FLOW CHART

Source code

import mysql.connector
mydb=mysql.connector.connect(host="localhost",u
ser="root",passwd="manager",database="quiz_comp
")
mycursor=mydb.cursor()
#mycursor.execute("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("2.participants")
print("3.scores update")
print("4.display")
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:")
sql_in= "insert into questions1 values(" + str(
sql) + ",'" + (sql1)+ "'"+",'" + (sql2) +
"'"+",'" + (sql3) +"'" +",'"+ (sql4) +"'"+",'"
+ (sql5) +"'"+ ",'"+(sql6) +"'"")"
mycursor.execute(sql_in)
mydb.commit()
print("your request has been processed.Thank
you for making us as a part of your project")
#mycursor.execute("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)
mycursor.execute(sql_int)
print("participants are all updated")
mydb.commit()
#mycursor.execute("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)
mycursor.execute(sql_insert)
mydb.commit()
if choice==4:
mycursor.execute("select * from questions1")
data=mycursor.fetchall()
print(data)

OUTPUT
 TESTING
Software testing is an empirical investigation conducted to
provide stakeholders with information about the quality of the
product or service under test, with respect to the context in
which it is intended to be operated. Software testing also
provides an objective, independent view of the software to
allow the business to appreciate and understand the risks in the
implementation of the software. Testing techniques include, but
are not limited to, the process of executing a program or
application with the intention of finding software bugs.
It can also be termed as the process of verifying and verifying
that a software program/application/product meets the business
and technical requirements that guide its design and
development, so that it works as expected and be implemented
with similar characteristics. Software testing, depending on the
test method employed, can be implemented at any time in the
development process, although most testing effort is employed
after the requirements are defined and the coding process is
complete.

TESTING METHODS
Software testing methods are traditionally divided into black box
testing and white box testing. These two approaches are used
to describe the approach that a test engineer takes when
designing test cases.

BLACK BOX TESTING

Black Box treats test software as a "black box", without any
information of internal implementation. Black box testing
methods include: equivalent segmentation, boundary value
analysis, all-pairs testing, fuzzy testing, model-based testing,
traceability matrix, exploratory testing, and specification-based
testing.

SPECIFICATION-BASED TESTING
Specification-based testing aims at testing the functionality of
the software as per the applicable requirements. [16] Thus, the
tester inputs the data, and only sees the output from the test
object. This level of testing usually requires the tester to have a
complete set of test cases, who can then simply verify that, for
a given input, the output value (or behavior), is either "is" or
"is". No" is the same as the expected value specified in the test
case. Specificity-based testing is necessary, but insufficient to
protect against certain risks.

ADVANTAGES AND DISADVANTAGES

The black box tester has no "bond" with the code, and a tester's
assumption is very simple: a code must contain bugs. Using the
principle, "ask and you will receive," black box testers find bugs
where programmers don't. But, on the other hand, black box
testing has been said to be "like walking in a dark maze without
a flashlight", because the tester does not know how the
software being tested was actually built.
So there are situations when
(1) a black box tester writes multiple test cases to test
something that can only be tested by one test case, and/or
(2) parts of the back end Testing is not done. Therefore, black
box testing has the advantage of "a disjointed opinion" on the
one hand, and the disadvantage of "blind finding" on the other.

WHITE BOX TESTING

White box testing, in contrast to black box testing, occurs when
the tester has access to internal data structures and algorithms
(and the code that implements these).

Types of white box testing:-

● API Testing - Testing the application using public and

private APIs.
● Code Coverage - Creating tests to meet certain criteria of
code coverage.

For example, to check, all communications are tested for 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 created with black box testing
methods. This allows the software team to test the parts of the
system that are rarely tested and ensure that the most critical
function points have been tested.

There are two common forms of code coverage:

● Function coverage: which reports on the tasks performed
and
● Detail Coverage: Which reports on the number of lines
executed to complete the test?
They both return the coverage metric, which is measured as a
percentage.

HARDWARE AND SOFTWARE 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
 BIBLIOGRAPHY
1. Informatics Practices - Class XII By : Sumita Arora
2. A Project Report On QUIZ SOFTWARE MANAGEMENT
SYSTEM.(QSMS)

By : CDT J GNANESH
3.Website: https://www.w3resource.com