SHIKSHA NIKETAN

ACADEMIC YEAR 2024-25

COMPUTER PROJECT

NAME : VINIT KUMAR SINGH

CLASS : 12
SEC : B
ROLL NO.: 31
BOARD ROLL NO.:
TOPIC: MOVIE TICKET BOOKING SYSTEM
PROJECT GUIDE : MR.NILADRI MUKHERJEE

1
SHIKSHA NIKETAN

CERTIFICATE

THIS IS TO CERTIFY THAT VINIT KUMAR SINGH,ROLL

NO:__________
HAS SUCCESSFULLY THE PROJECT WORK ENTITLED “MOVIE
TICKET BOOKING”.

IN THE SUBJECT COMPUTER SCIENCE (083) LAID DOWN IN

THE REGULATION OF CBSE FOR THE PURPOSE OF PRACTICAL
EXAMINATION OF CLASS’ XII’ TO BE HELD IN SHIKSHA
NIKETAN.

EXTERNAL TEACHER SIGNATURE COMPUTER TEACHER SIGNATURE

2
 TABLE OF CONTENTS
S.no. Description .

1 ACKNOWLEDGEMENT

2 INTRODUCTION

3 PROPOSED SYSTEM

4 SYSTEM DEVELOPMENT LIFE

CYCLE (SDLC)

5 PHASES OF SYSTEM
DEVELOPMENT LIFE CYCLE

6 FLOW CHART

7 SOURCE CODE

8 OUTPUT

9 TESTING

10 HARDWARE AND SOFTWARE

REQUIREMENTS

11 BIBLIOGRAPHY

3
 ACKNOWLEDGEMENT

Apart from my efforts, the success of any project

depends largely on the encouragement and guidelines of
many others. I take this opportunity to express my
gratitude to the people who have been instrumental in
the successful completion of this project. I express deep
sense of gratitude to almighty God for giving me strength
for the successful completion of the project. I express my
heartfelt gratitude to my parents for constant
encouragement while carrying out this project. I
gratefully acknowledge the contribution of the
individuals who contributed in bringing this project up to
this level, who continues to look after me despite my
flaws, I express my deep sense of gratitude to Mina
Wilkhu The Principal, Vidya Bharati Chinmaya Vidyalaya
who has been continuously motivating and extending
their helping hand to us. I am overwhelmed to express
my thanks to The Administrative Officer for providing me
an infrastructure and moral support while carrying out
this project in the school. The guidance and support
received from all the members who contributed and who
are contributing to this project, was vital for the success
of the project. I am grateful for their constant support
and help.

4
 INTRODUCTION
Movie theatres have become one of the most
preferred getaways in today's world. And yet going
to the theatre, selecting a movie, and making sure
the tickets aren't sold out, could prove tedious. Any
knowledge about the list of movies, show timings,
or even seats can be attained by the customer only
by being present physically.An Online Movie Ticket
Booking System brings the theatres closer to the
customers. It eases and improves the booking
experience. The system holds the database of all
the movies being played along with their show
timings and available seats. This system can be
accessed using a website by the customers a few
days before the show to book their seats of
choiceand at the same time, keeps the theatre
admins updated about the seats being booked.

5
 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 out
dated 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
organizations. Many software products working are
now in markets, which have helped in making the
organizations work easing and efficiently Data
management initially had to maintain a let of
ledgers and a lot of paperwork has to be done but
now software production this organization has
made their work faster and easier. Now only this
software has to be loaded on the computer and
work con 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 Dutton. Moreover, now it's an age of
computers of and automating such an organization
gives the better look. 6
 SYSTEM DEVELOPMENT
LIFE CYCLE
PLANNING ANALYSIS DESIGN

SUPPORT Implementation
Construction, Testing, &
Software Configuration
(Consisted of three iterations
on Different hardware
platforms)

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, and
planning phases, initiation, concept
requirements-definition, 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 bult to deliver the needed
functionality 7
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 business improve 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 correcta system is
identified and fornmally requested through the presentation of a
business case. The business case should, at a minimum describe a
proposof's purpose, identify

8
 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 of 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
afternatives
• 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 incrementol
delivery versus a complete, onetime deployment.
9
 • Construction of executable prototypes is encouraged
to evaluate technology to support the business
process. The System Boundary 9 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

Analysis Planning

PLANNING PHASE
Design (Implementation) Maintenance The planning phase
is the most critical step in completing development.
acquisition, and maintenance projects. Careful planning.
particularly in the early stages ofa project, isnecessary 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
specificactivities and resources required to complete a 10

project
 A critical part of a project manager sjob is to coordinate
discussions between user, audit, security, design,
development, and network personnel to identify and
document as many functional, security, and network
requirements 10 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.

REQUIRENMENTSANALYSIS 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 MasterPlan.

The purposes of this phase are to:

• Further define and refine the functional and data

requirements and document them in the Requirements 11
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 12
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:
• ldentifying 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 12 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. 13
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 13 satistied by the developed or
modified system, OlT 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 14
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 on-going. 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 re-enter the planning phase.

15
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

16
17
18
19
20
 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 software
program/application/product meets the business and 21
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.

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
22
 ADVANTAGES AND DISADVANTAGES
The black box tester has no "bonds with the code, ond a
tester's perception is very simple: a code must have bugs,
Using the principle, "Ask nd you shall recelve."' black box
testers find bugs where progrommers don't. But, on the
other hand, blak box testing has been sold to be "like a
walk in a dark labyrinth without a flashlight." because the
tester doesn't know how the software being tested was
actualy 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 odvantoge of an
unaffilioted opinion, on the one hand, and the
disadvantoge 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 intenal data structures ond
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. " 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
23
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:
• FunctionCoverage: 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
25
 BIBLIOGRAPHY

1. Computer science With Python -Class XII

2. 2. Website: https://www.youtube.com

26