A

Micro project report On

“SRS Document on Flight Management System”

SUBMITTED TO M.S.B.T.E., Mumbai

For the Award of

DIPLOMA IN INFORMATION TECHNOLOGY BY

Roll Name of Student Enrollment no

no
08 Pawar Rohit Shrikant 2110740077
14 Dhiraj Dattatray Gaikwad 2110740084
23 Om Manojkumar Gavali 2110740095
49 Parth Sanjay Pawar 2110740124

UNDER THE GUIDANCE OF

Mr.Janrao.A.A

DEPARTMENT OF COMPUTER ENGINEERING

NBA ACCREDIATED

SVERI’s College of Engineering (Polytechnic), Pandharpur

Gopalpur Pandharpur-413304
2022-23
AFFILIATED TO

M.S.B.T.E.
Evolution sheet for Micro Project
Academic Year:2022-23 Name of Faculty:Janrao.A.A
Course:-Information technology Course code:- IF4I
Subject: SEN Subject Code:- 22421
Semester:- 4 Scheme:- I
Project name:- SRS Document on Flight Management System
COs addressed by the Micro Project:
CO 1 Prepare software requirement specifications.

Comments/Suggestions about team work/leadership/inter-personal communication (if any)

T
ot
al
Marks out of
Marks out of 4 m
6 for
for performance ar
performance
Roll No Name of students in oral/ s
in group
Presentation ou
activity
t
of
10
08 Rohit Shrikant Pawar
14 Dhiraj Dattatray Gaikwad
23 Om Manojkumar Gavali
49 Parth Sanjay Pawar

Name and
Signatur Janrao.A.A
e of
faculty
 SVERI’s COLLEGE OF ENGINEERING (POLYTECHNIC), PANDHARPUR.

CERTIFICATE

This is to certify that the Project report entitled

“SRS Document on Flight Management System”
Submitted by

Roll Name of Student Enrollment

no no
08 Pawar Rohit Shrikant 2110740077
14 Dhiraj Dattatray Gaikwad 2110740084
23 Om Manojkumar Gavali 2110740095
49 Parth Sanjay Pawar 2110740124

( Mr.janrao.A.A)

(Mr.Misal.G.S.) (Dr. Misal.N.D.)

HOD Principal

Place: Pandharpur

Date: / /
 Acknowledgement

“SRS Document on Flight Management System” has been developed successfully with
a great contribution of two students in a period of two months. We like to appreciate their guidance,
encouragement and willingness since without their support the project would not have been a success.
We would like to give our heartfelt gratitude to Principal Dr.N.D.Misal & HOD Mr.G.S.Misal Guide Mr
janrao.A.A who is the supervisor of our project for helping and encouraging us in many ways to make
our project a success. We would never been able to finish our work without great support and enthusiasm
from friends and support from our family. We would like to thank the department of Information
Technology, for giving us permission to initiate this project and successfully finish it.
Introduction:-
1. INTRODUCTION
1.1 PURPOSE

The purpose of this document is to build an online system to manage flights and passengers to ease
the flight management. <<Include the purpose as applicable to your project >>

1.2 DOCUMENT CONVENTIONS

This document uses the following conventions. <<Include the conventions as per your application >>

DB Database

DDB Distributed Database

ER Entity Relationship

1.3 INTENDED AUDIENCE AND READING SUGGESTIONS

This project is a prototype for the flight management system and it is restricted within the college
premises. This has been implemented under the guidance of college professors. This project is
useful for the flight management team and as well as to the passengers.

1.4 PROJECT SCOPE

The purpose of the online flight management system is to ease flight management and to create a
convenient and easy-to-use application for passengers, trying to buy airline tickets. The system is
based on a relational database with its flight management and reservation functions.
1.5 REFERENCES

● https://krazytech.com/projects

2. OVERALL DESCRIPTION
2.1 PRODUCT PERSPECTIVE

A distributed airline database system stores the following information.

● Flight details:
It includes the originating flight terminal and destination terminal, along with the stops
in between, the number of seats booked/available seats between two destinations etc.
● Customer description:
It includes customer code, name, address and phone number. This information may be
used for keeping the records of the customer for any emergency or for any other kind
of information.
● Reservation description:
It includes customer details, code number, flight number, date of booking, date of
travel.

2.2 PRODUCT FEATURES

The major features of airline database system as shown in below entity–relationship model (ER
model)
The diagram shows the layout of airline database system – entity–relationship model
2.3 USER CLASS and CHARACTERISTICS

Users of the system should be able to retrieve flight information between two given cities with the
given date/time of travel from the database. A route from city A to city B is a sequence of connecting
flights from A to B such that: a) there are at most two connecting stops, excluding the starting city
and destination city of the trip, b) the connecting time is between one to two hours. The system will
support two types of user privileges, Customer, and Employee. Customers will have access to
customer functions, and the employees will have access to both customer and flight management
functions. The customer should be able to do the following functions:

The Employee should have following management functionalities:

● CUSTOMER FUNCTIONS.
• Get all customers who have seats reserved on a given flight.
• Get all flights for a given airport.
• View flight schedule.
• Get all flights whose arrival and departure times are on time/delayed.
• Calculate total sales for a given flight.

Each flight has a limited number of available seats. There are a number of flights which depart from
or arrive at different cities on different dates and time.
2.4 OPERATING ENVIRONMENT

Operating environment for the airline management system is as listed below. <<Include the details
as per your application >>

● distributed database
● client/server system
● Operating system: Windows.
● database: sql+ database
● platform: vb.net/Java/PHP

2.5 DESIGN and IMPLEMENTATION CONSTRAINTS

1. The global schema, fragmentation schema, and allocation schema.

2. SQL commands for above queries/applications
3. How the response for application 1 and 2 will be generated. Assuming these are global
queries. Explain how various fragments will be combined to do so.
4. Implement the database at least using a centralized database management system.

2.6 ASSUMPTION DEPENDENCIES

Let us assume that this is a distributed airline management system and it is used in the following
application:

● A request for booking/cancellation of a flight from any source to any destination, giving
connected flights in case no direct flight between the specified Source-Destination pair
exist.

Assuming both the transactions are single transactions, we have designed a distributed database
that is geographically dispersed at four cities Delhi, Mumbai, Chennai, and Kolkatta as shown in fig.
below.
3. SYSTEM FEATURES
● DESCRIPTION and PRIORITY

The airline reservation system maintains information on flights, classes of seats, personal
preferences, prices, and bookings. Of course, this project has a high priority because it is very
difficult to travel across countries without prior reservations.

● STIMULUS/RESPONSE SEQUENCES
● Search for Airline Flights for two Travel cities
● Displays a detailed list of available flights and make a “Reservation” or Book
a ticket on a particular flight.
● Cancel an existing Reservation.
● FUNCTIONAL REQUIREMENTS

Other system features include:

DISTRIBUTED DATABASE:

Distributed database implies that a single application should be able to operate transparently on
data that is spread across a variety of different databases and connected by a communication
network as shown in below figure.

Distributed database located in four different cities

CLIENT/SERVER SYSTEM

The term client/server refers primarily to an architecture or logical division of responsibilities, the
client is the application (also known as the front-end), and the server is the DBMS (also known as
the back-end).

A client/server system is a distributed system in which,

● Some sites are client sites and others are server sites.
● All the data resides at the server sites.
● All applications execute at the client sites.

4. EXTERNAL INTERFACE REQUIREMENTS

4.1 USER INTERFACES

● Front-end software: Vb.net version

● Back-end software: SQL+

4.2 HARDWARE INTERFACES

● Windows.
● A browser which supports CGI, HTML & Javascript.

4.3 SOFTWARE INTERFACES

Following are the software used for the flight management online application. <<Include the software
details as per your project >>

Software used Description

Operating system We have chosen Windows operating system for its

best support and user-friendliness.

Database To save the flight records, passengers records we

have chosen SQL+ database.

VB.Net To implement the project we have chosen Vb.Net

 language for its more interactive support.

4.4 COMMUNICATION INTERFACES

This project supports all types of web browsers. We are using simple electronic forms for the
reservation forms, ticket booking etc.

5. NONFUNCTIONAL REQUIREMENTS
5.1 PERFORMANCE REQUIREMENTS

The steps involved to perform the implementation of airline database are as listed below.

A) E-R DIAGRAM

The E-R Diagram constitutes a technique for representing the logical structure of a database in a
pictorial manner. This analysis is then used to organize data as a relation, normalizing relation and
finally obtaining a relation database.

● ENTITIES: Which specify distinct real-world items in an application.

● PROPERTIES/ATTRIBUTES: Which specify properties of an entity and relationships.
● RELATIONSHIPS: Which connect entities and represent meaningful dependencies
between them.
 the diagram shows the ER diagram of airline database

5.2 SAFETY REQUIREMENTS

If there is extensive damage to a wide portion of the database due to catastrophic failure, such as a
disk crash, the recovery method restores a past copy of the database that was backed up to archival
storage (typically tape) and reconstructs a more current state by reapplying or redoing the
operations of committed transactions from the backed up log, up to the time of failure.

5.3 SECURITY REQUIREMENTS

Security systems need database storage just like many other applications. However, the special
requirements of the security market mean that vendors must choose their database partner
carefully.

5.4 SOFTWARE QUALITY ATTRIBUTES

● AVAILABILITY: The flight should be available on the specified date and specified time
as many customers are doing advance reservations.
● CORRECTNESS: The flight should reach start from correct start terminal and should
reach the correct destination.
● MAINTAINABILITY: The administrators and flight in chargers should maintain correct
schedules of flights.
● USABILITY: The flight schedules should satisfy a maximum number of customers
Conclusion:

software requirements specification (SRS) is a document that describes what the software will do
and how it will be expected to perform.