NARAYANA JUNIOR COLLEGE, BHAYANDER (W)

ACADEMIC YEAR: 2023-2024

CBSE ROLL NO:

NAME: ARYAN CHOUDHARY

CLASS: XII

SUBJECT: COMPUTER SCIENCE

SUB CODE: 083

1
 NARAYANA JUNIOR COLLEGE, BHAYANDER (W)

CERTIFICATE

This is to certify that Cadet ARYAN CHOUDHARY CBSE Roll No:

has satisfactorily completed the laboratory work in
Computer Science (083) Python laid down in the regulations of CBSE for the
purpose of Term 1 and 2 Practical Examination in Class XII to be held in
Narayana Junior College, BHAYANDER (W) on .

PGT for Computer Science

Examiners:
1.NAME: Signature:
(Internal)

2 NAME: Signature:
(External)

School Stamp Principal Signature

2
 TABLE OF CONTENTS [ T O C]
SER DESCRIPTION PAGENO

01
ACKNOWLEDGMENT 4

02
INTRODUCTIONS 5

03
OBJECTIVES OF THE 5
PROJECT
04
PROPOSED SYSTEM 6

05
SYSTEM DEVELOPMENT 6
LIFE CYCLE(SDLC)
06
PHASES OF SDLC 8

07
FLOW CHART 16

08
SOURCE CODE 18

09
OUTPUT 22

10
TESTING 27

11 HARDWARE/SOFTWARE
REQUIREMENTS 30

12
BIBLIOGRAPHY 31

3
 ACKNOWLEDGEMENT

I would like to express my deepest regard to the Principal,

Mrs. Queena Fernando, for providing us with infrastructure and facilities
for the project.

I would like to extend my thanks to my computer teacher,

Ms. Poonam Lad under whose guidance this project was performed.
Her constant support and invaluable guidance helped me to achieve completion of this
project.

I also want to express my gratitude to the Computer department of college and

Computer laboratory in-charge.
Last but not least, I would like to thank my family for their moral support.

4
 PROJECT ON CREATING AIRLINE RESERVATION MANAGEMENT
SYSTEM

INTRODUCTION

This program helps the users to manage and streamline the processes associated with
airline bookings and passenger management.
After adding information about the bookings ,the program creates a database in
MYSQL in the respective bookings you choose and creates a table to store the
bookings information in Tabular format in MYSQL.

OBJECTIVES OF THE PROJECT

Efficient Booking Process: Streamline the flight booking process to make it quick,
user-friendly, and efficient for customers. The objective is to reduce the time and
effort required for passengers to search for flights and complete reservations.

User-Friendly Interface: Develop an intuitive and user-friendly interface that

enhances the overall user experience. The objective is to make it easy for customers to
navigate the system, find relevant information, and complete bookings without
unnecessary complications.

Reservation Process : Streamline the booking process to minimize the number of

steps required for users to make a reservation. Provide clear and concise instructions
throughout the reservation process .

Data Management:
Develop a robust database system to store and manage flight information and flights
schedule as per the convience .Ensure updates and synchronization of data to provide
accurate and current information to users.

5
PROPOSED SYSTEM

The proposed system ensures the complete freedom for users where
users on its own system can log on to the website and book his or her
flights .Our proposed system allows user to book the flights, view
timings and cancel their flights
In this proposal the entire work is done on online platform and an
reservation id is also provided to the passenger. From passenger role
they should enter all their details properly such as name etc.

The proposed system for the problem is “Airline reservation system” , a

web based system that allows online reservations. The system is divided
into three layers namely presentation layer , business layer and data
layer. The presentation layer is at the client side. At server side , business
layer and data layer reside. The system requires a server side technology
for its implementation.

It has the following advantages.

 Reservations are supported up to 1 year.

 Accessing and Updating the system is Fast.

 Higher productivity and effective management

 Quick Response to the passengers.

 Both domestic and international flights available

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

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

8
 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, 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 incremental delivery versus a complete,
onetime deployment.
⦁Construction of executable 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.

9
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's job is to coordinate discussions between

user, audit, security, design, development, and network personnel to identify any
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.

10
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 generates it, where does the information go, and who processes it),

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

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

13
⦁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 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 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

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

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, replace or retrieve

15
FLOWCHART

16
17
18
19
 SOURCE CODE
Import mysql .connector
from mysql.connector import Error

def create_connection():
try:
connection = mysql.connector.connect(
host='localhost',
database='airline_reservations',
user='root',
password='1234'
)
if connection.is_connected():
return connection
except Error as e:
print(f" Error: {e}")
return None

def create_tables(connection):
try:
cursor = connection.cursor()

tables = [
"""
CREATE TABLE IF NOT EXISTS flights (
id INT AUTO_INCREMENT PRIMARY KEY,
flight_number VARCHAR(255),
source VARCHAR(255),
destination VARCHAR(255),

20
 type VARCHAR(255)
)
""",
"""
CREATE TABLE IF NOT EXISTS reservations (
id INT AUTO_INCREMENT PRIMARY KEY,
flight_id INT,
passenger_name VARCHAR(255),
FOREIGN KEY (flight_id) REFERENCES flights(id) ON DELETE CASCADE
)
""",
"""
CREATE TABLE IF NOT EXISTS food_choices (
id INT AUTO_INCREMENT PRIMARY KEY,
reservation_id INT,
food_option VARCHAR(255),
FOREIGN KEY (reservation_id) REFERENCES reservations(id) ON DELETE
CASCADE
)
"""
]

for table in tables:

cursor.execute(table)

connection.commit()
except Error as e:
print(f"Error: {e}")

def get_user_flight_type_choice():

21
 while True:
print("\nSelect Flight Type:")
print("1. Domestic Flights")
print("2. International Flights")

flight_type_choice = input("Enter your choice (1 or 2): ")

if flight_type_choice in ['1', '2']:

return flight_type_choice
else:
print("Invalid choice. Please enter 1 or 2.")

def get_flights_by_type(connection, flight_type):

try:
cursor = connection.cursor()
cursor.execute("SELECT * FROM flights WHERE type = %s", (flight_type,))
return cursor.fetchall()
except Error as e:
print(f"Error: {e}")
return []

def display_flights(connection):
try:
flight_type_choice = get_user_flight_type_choice()
flight_type = 'Domestic' if flight_type_choice == '1' else 'International'

flights = get_flights_by_type(connection, flight_type)

if not flights:
print(f"No {flight_type} flights available.")

22
 else:
print(f"\nAvailable {flight_type} Flights:")
for flight in flights:
print(f"ID: {flight[0]}, Flight Number: {flight[1]}, Source: {flight[2]},
Destination: {flight[3]}")

except Error as e:
print(f"Error: {e}")

def make_reservation(connection, flight_id, passenger_name):

try:
cursor = connection.cursor()
cursor.execute("INSERT INTO reservations (flight_id, passenger_name)
VALUES (%s, %s)",
(flight_id, passenger_name))
reservation_id = cursor.lastrowid
connection.commit()
print(f"Reservation (ID: {reservation_id}) made successfully.")
return reservation_id

except Error as e:
print(f"Error: {e}")
return None

def display_food_choices():
print("\nFood Choices:")
print("1. Veg Option 1: Sandwich")
print("2. Veg Option 2: Burger")
print("3. Non-Veg Option 1: Chicken Tikka Masala")
print("4. Non-Veg Option 2: Chicken Noodles")

23
def get_food_choice():
while True:
food_choice = input("Enter the number of your food choice : ")
if food_choice in ['1', '2', '3', '4']:
return display_food_choices
else:
print("Invalid choice. Please enter a valid option.")

def insert_food_choice(connection, reservation_id, food_option):

try:
cursor = connection.cursor()
cursor.execute("INSERT INTO food_choices (reservation_id, food_option)
VALUES (%s, %s)",
(reservation_id, food_option))
connection.commit()
except Error as e:
print(f"Error: {e}")

def display_reservation_details(connection, reservation_id):

try:
cursor = connection.cursor()
cursor.execute("""
SELECT
r.id,
r.passenger_name,
f.flight_number,
f.source,

24
 f.destination,
fc.food_option
FROM
reservations r
JOIN flights f ON r.flight_id = f.id
LEFT JOIN food_choices fc ON r.id = fc.reservation_id
WHERE
r.id = %s
""", (reservation_id,))
reservation_info = cursor.fetchone()

if reservation_info:
print("\nReservation Details:")
print(f"Reservation ID: {reservation_info[0]}")
print(f"Passenger Name: {reservation_info[1]}")
print(f"Flight Number: {reservation_info[2]}")
print(f"Source: {reservation_info[3]}")
print(f"Destination: {reservation_info[4]}")

else:
print("Reservation not found.")
except Error as e:
print(f"Error: {e}")

def check_flight_status(connection, reservation_id):

try:
cursor = connection.cursor()
cursor.execute("""
SELECT

25
 f.flight_number,
f.source,
f.destination
FROM
reservations r
JOIN flights f ON r.flight_id = f.id
WHERE
r.id = %s
""", (reservation_id,))
flight_info = cursor.fetchone()

if flight_info:
print("\nFlight Status:")
print(f"Flight Number: {flight_info[0]}")
print(f"Source: {flight_info[1]}")
print(f"Destination: {flight_info[2]}")
print(f"
else:
print("Reservation not found.")
except Error as e:
print(f"Error: {e}")

def cancel_reservation(connection, reservation_id):

try:
cursor = connection.cursor()
cursor.execute("DELETE FROM reservations WHERE id = %s", (reservation_id,))
connection.commit()

rows_affected = cursor.rowcount
if rows_affected > 0:

26
 print("Reservation canceled successfully.")
else:
print("Reservation not found.")
except Error as e:
print(f"Error: {e}")

def fancy_exit_message():
print("\n*****************")
print("* THANK YOU FOR CHOOSING BLUEPHOENIX AIRLINES *")
print("***************\n")

def main():
print("\n WELCOME TO BLUEPHOENIX AIRLINES BOOKING WINDOW ")
connection = create_connection()

if connection:
create_tables(connection)
display_flights(connection)

try:
flight_id = int(input("\nEnter the ID of the flight you want to reserve: "))
passenger_name = input("Enter your name: ")
passenger_number = input("Enter your phone number: ")

eat_choice = input("\nDo you want to eat food during the journey?

(yes/no): ").lower()
if eat_choice == 'yes':
display_food_choices()
food_choice = get_food_choice()

27
 reservation_id = make_reservation(connection, flight_id, passenger_name)
display_reservation_details(connection, reservation_id)
check_flight_status(connection, reservation_id)
display_foodchoice ()

cancel_choice = input("\nDo you want to cancel the reservation? (yes/no):

").lower()
if cancel_choice == 'yes':
cancel_id = int(input("Enter the ID of the reservation to cancel: "))
cancel_reservation(connection, cancel_id)

fancy_exit_message()

except ValueError:
print("Invalid input. Please enter a valid numeric value.")

connection.close()

if _name_ ==
"_main_"main()

28
29
OUTPUT

30
 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 test
engineer takes when designing test cases.

31
 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 behavior), 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.

32
 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.
⦁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

33
 HARDWARE AND SOFTWARE REQUIREMENTS

I. OPERATING SYSTEM : WINDOWS 7 AND ABOVE

II. PROCESSOR : PENTIUM(ANY) OR
AMD ATHALON(3800+- 4200+ DUALCORE)
III. MOTHERBOARD : 1.845 OR 915,995 FOR PENTIUM 0R
MSI K9MM-V VIAK8M800+8237R PLUS CHIPSET FOR AMD
IVT
A . RHAAMLON : 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:

 WINDOWS 10/8/7
 PYTHON 3.12
 MYSQL 8.0

34
.

BIBLIOGRAPHY

⦁ Computer science With Python - Class XI By : SumitaArora

⦁ Computer science With Python - Class XII By : SumitaArora

⦁ Computer science NCERT - Class XI

⦁ Computer science NCERT - Class XII

⦁ A Project Report On Employee database management

system

...

35