Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
University Area, Plot No. III - B/5, New Town, Action Area - III, Kolkata, West Bengal 700156
Submitted By:
1. Rahul Roy
2. Godhuli Das
3. Soumi Adhikari
………………
Date: 08.04.2019
Rahul Roy(43)
Godhuli Das(44)
Soumi Adhikari(45)
2
CERTIFICATE
DATE:
………………………
Project In-charge
3
Software Requirements Specification for Online Air Ticket Reservation System Page ii
Table of Contents
Table of Contents ...........................................................................................................................1
Revision History ............................................................................... Error! Bookmark not defined.
1. Introduction ..............................................................................................................................1
1.1 Purpose............................................................................................................................................. 1
1.2 Document Conventions.................................................................................................................... 1
1.3 Intended Audience and Reading Suggestions .................................................................................. 1
1.4 Product Scope .................................................................................................................................. 1
1.5 References ........................................................................................................................................ 1
2. Overall Description ..................................................................................................................1
2.1 Product Perspective.......................................................................................................................... 1
2.2 Product Functions ............................................................................................................................ 2
2.3 User Classes and Characteristics ..................................................................................................... 2
2.4 Operating Environment.................................................................................................................... 2
2.5 Design and Implementation Constraints .......................................................................................... 3
2.6 User Documentation ........................................................................................................................ 3
2.7 Assumptions and Dependencies ...................................................................................................... 3
3. External Interface Requirements ...........................................................................................4
3.1 User Interfaces ................................................................................................................................. 4
3.2 Hardware Interfaces ......................................................................................................................... 4
3.3 Software Interfaces .......................................................................................................................... 4
3.4 Communications Interfaces ............................................................................................................. 4
4. System Features .......................................................................................................................5
4.1 Opening Screen ................................................................................................................................ 5
4.2 Book Tickets .................................................................................................................................... 5
4.3 Check Status..................................................................................................................................... 6
4.4 Cancel Tickets ……………………………………………………………………………..6
5. Other Nonfunctional Requirements .......................................................................................8
5.1 Performance Requirements .............................................................................................................. 6
5.2 Safety Requirements ........................................................................................................................ 6
5.3 Security Requirements ..................................................................................................................... 6
5.4 Software Quality Attributes ............................................................................................................. 6
5.5 Business Rules ................................................................................................................................. 7
6. Design Documents ...................................................................... Error! Bookmark not defined.
7. Output………………………………………………………………………………….……..5
Appendix A: Glossary....................................................................................................................9
Appendix B: Analysis Models .....................................................................................................13
Software Requirements Specification for Online Air Ticket Reservation System Page 1
1. Introduction
1.1 Purpose
1.2 Conventions
1.5 References
https://krazytech.com/projects
2. Overall Description
Flight details:
It includes the originating flight terminal and destination terminal, price of travel
between two destinations, flights available etc.
Customer description:
It includes customer name, age, sex, email id 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, PNR, flight number, date of booking.
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 (the starting city and destination city of the trip).
The system will support user privileges of Customer. Customers will have access to customer
functions, The customer should be able to do the following functions:
• Make a new reservation
• One-way
• Flexible Date
• Confirmation
• Cancel an existing reservation
• View his itinerary
Let us assume that this is airline ticket reservation system is used in the following application:
A request for booking/cancellation of a flight from any source to any destination.
Assuming transaction is single transaction, we have designed a distributed database that is
geographically dispersed at four cities Delhi, Mumbai, Bangalore and Kolkata and International
for London, Dubai, Abu Dhabi, Singapore and New York.
DEV C++ To implement the project we have chosen DEV C++ language for
its more interactive support.
This project supports all types of C++ supported IDE. We are using simple electronic forms in
output terminal for the reservation forms, ticket booking etc.
4. System Features
Description and Priority: The user can use the Book Tickets function to purchase seats for an airplane
flight. The system shall present the user with information on all current flights. The user may then select source
and destination and fight on which to purchase seats. Finally, the system shall guide the user completely through
the checkout process.
Inputs: Domestic or International choice, Source, Destination, Flight name, User information.
Source: Inputs are from the user except flight information, which is retrieved from the system.
Software Requirements Specification for Online Air Ticket Reservation System Page 5
Output: The purchased seat are tied to the user’s account, so he/she can reserve seats later.
Destination: The booked flights will be stored in the user’s account information when the user finishes
payment. The flight information shall also display on the screen.
Pre-Conditions: The user must be logged in the session.
Post-Conditions: Completion of this function guarantees that the user has seats on a specific flight. Any
successfully-booked flight from this function is assumed to have completed payment already.
Side-Effects: User’s account is charged. Flight is associated with user’s account.
Stimulus/Response:
User Action System Application
1.The system shows the user a list of
domestic or International flights .
2. The user selects seats 3. The system checks for avaliable flights.
from a list flights by giving source,destination and allow users to confirm their selection.
and date of travel. The The seats and confirmation selection seats
on chosen as individual seats for the screen are displayed.
departing and returning flights.
.
4. The user confirms by giving personal 5. Once confirmed, the seats are applied
details on the screen. and user is shown a final confirmation
screen which displays selected seats
and account information.
Description and Priority: The user can use the Cancel Ticket function to cancel seats for an airplane flight.
The system shall ask for the details of the user. Finally, the system shall guide the user completely through the
checkout and cancellation process.
Software Requirements Specification for Online Air Ticket Reservation System Page 6
2. The user gives details of flight and PNR no 3. The system checks for booked flight.
and allow users to cancel their selection.
The seats and cancelled seats are displayed.
.
For each session,system shall guarantee the connection time. A close operation will be
performed when expired. This design is to satisfy each user’s usability and connection
quality.
The system restarts after a session is closed.
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.
Software Requirements Specification for Online Air Ticket Reservation System Page 7
A secure session is to monitor activity and remain open throughout the entire session. If
a certificate cannot be verified the session will not be created.
1. A city of departure and city of arrival must be entered by the user.
2. A travel date must be entered by the user.
All flights must be paid in full for the reservation to be successfully created.
If a flight has been cancelled, the flight details should still be available to the user along
with a notation that the flight is no longer scheduled
6. Output
Appendix A: Glossary
Authentication The process of identifying an individual, usually based on username and
password
Input Criteria A defined particular group of criteria, which defines inputs.
Class Diagram
Software Requirements Specification for Online Air Ticket Reservation System Page 14
ER Diagram
Structure Chart
Software Requirements Specification for Online Air Ticket Reservation System Page 16
Sequence Diagram