ADARSH VIDYA KENDRA

2025-2026

COMPUTER INVESTIGATORY PROJECT

MOVIE TICKET BOOKING SYSTEM

NAME : SREE JAYANI.S

CLASS : XII-A

SUBJECT : COMPUTER SCIENCE

SUBJECT CODE : 083

REGISTRATION NO :

1
 CERTIFICATE

This is to certify that this “COMPUTER INVESTIGATORY

PROJECT” on the topic “Movie Ticket Booking System”
has been successfully completed by SREE JAYANI.S of class
XII A under the guidance of my Computer Teacher
Mrs.Dhanya.H.P.in partial fulfilment of the curriculum of
Central Board of Secondary Education (CBSE) leading to the
award of Annual Examination of the year 2025-2026.

INTERNAL SIGNATURE OF EXTERNAL

EXAMINER PRINCIPAL EXAMINER

2
 ACKNOWLEDGEMENT

I have taken efforts in this project. However, it would not

have been possible without the kind support and help of many
individuals.
I would like to thank my School and my Principal Mr. Maria
Joe Jegadhesh for providing me with facilities required to do
my project.
I am highly indebted to my Computer teacher
Mrs.Dhanya.H.P for her invaluable guidance which has
sustained my efforts in all the stages of this project work.
I also like to thank my Parents for their continuous support
and encouragement.
My thanks and appreciations also go to my fellow classmates
and the laboratory assistant in developing the project and to
the people who have willingly helped me out with their
abilities.

3
 INDEX

S.NO CONTENTS PG NO

1 INTRODUCTION 5

OBJECTIVES OF THE PROJECT

2 5

3 PROPOSED SYSTEM 7

SYSTEM DEVELOPMENT LIFE

4 CYCLE (SDLC) 8

PHASES OF SYSTEM
5 DEVELOPMENT LIFE CYCLE 9

SOURCE CODE 17
6

OUTPUT 19
7

8 TESTING 20

9 SOFTWARE REQUIRED 21

10 BIBLIOGRAPHY 22

4
 INTRODUCTION

This program helps the users to book the ticket for the movie
that he/she wish to see from the available seat where they
wish to be seated in the theatre.

OBJECTIVE:

The objective of this project is to let the students apply the

programming knowledge into a real-world situation/problem
and exposed the students how programming skills helps in
developing a good software.

1.Write programs utilizing modern software tools.

2.Apply object-oriented programming principles effectively

when developing small to medium sized projects.

3.Write effective procedural code to solve small to medium

sized problems.

4. Students will demonstrate a breadth of knowledge in

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

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

6
 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 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 paperwork 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.

7
 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

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

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

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
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,

10
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 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

11
 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
12
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.

13
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
14
 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.
 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.

15
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.
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
SOURCE CODE

17
18
OUTPUT

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

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

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

SOFTWARE REQUIREMENTS
I. Windows OS
II. Python
III. MySQL

21
 BIBLIOGRAPHY
 NCERT Textbook Class 12
 Preeti Arora Class 12
 Google Search

22