Software Requirement Engineering Project
Online
Air Ticket Booking system is to provide an option to customers to book the
tickets online and to check the confirmation online. This system will help the
company to sell the flight tickets online. Unless like in the previous stage
people as to walk into travel agency or this company ticket counter to buy the
tickets .And also to check the flight timings. This problem is overcome by
introducing this problem solution "The Online Airline Reservation
System".
Before there were
manual systems people come to the airport reserve seats, find timing by asking
from the agents. While in propose system the main purpose is to provide
alternatives and convenient way to passengers to reserve a seat. History of
Airline reservation is that "David J. Wardle" said in
his journal that before the electronic age reservation were managed manually
using records book and manifest and other printed media. The basic Airline
Reservation system was made in 1971 with the "Apollo Reservation
system" and "Programmed Airline Reservation System"
(PARS).
1.1 Project purpose:
The main purpose of this
project is to reduce the manual errors involved in the airline reservation
process and make it convenient for the customers to book the flights as when
they require such that they can utilize this project to make reservations, modify
reservations or cancel a particular reservation. The project is to construct a specification, refinement and
implementation of an airline reservation system.
1.2 Project Overview:
Airline Reservations Systems
contain airline schedules, fare tariffs, passenger reservations and ticket
records. An airline’s inventory contains all flights with their available
seats. The inventory of an airline is generally divided into service classes
(e.g. First, Business or Economy class) and other booking classes, for which
different prices and booking conditions apply. Inventory data is imported and
maintained through a Schedule Distribution System over standardized interfaces.
One of the core functions of the inventory management is the inventory control.
Inventory control steers how many seats are available in the different booking
classes, by opening and closing individual booking classes for sale. In
combination with the fares and booking conditions stored in the Fare Quote
System the price for each sold seat is determined.
1.3 Project Scope:
The name of the software is “Online Airline Reservation
System”. This software provides options for viewing different flights available
with different timings for a particular date and provides customers with the
facility to book a ticket, modify or cancel a particular reservation but it
does not provide the customers with details of cost of the ticket and it does
not allow the customer to modify a particular part of his reservation and
he/she can modify all his details.
2 Functional
Requirements:
User:
Sign up.
Login.
Search for flight.
Search for fare.
Select class
Reserve
flight type (1) one way (2) round trip.
Make
Reservation.
Modify
flight.
Cancel
flight..
Logout.
Admin:
1.
Sign
up.
2.
Admin
login.
3.
Add
a flight.
4.
Delete/cancel
a flight.
5.
Modify
flight information
6.
Modify
user reservation
7.
Maintain
user information
8.
View user information
Details (user):
If
the user want to reserve a seat and he is not register then he must sign up. In
sign After
sign up user information will be saved in database and he will be able to login
for login user will enter his email id and password that he give in enter
during filling sign up page.
When
user is login then he can easily search a flight by giving source and
destination only and enter submit button. Through the standard flight search
method the user will be able to search one-way, round-trip, or
multi-destination flights. The screen by default will display options for
searching round trip flights. The search criteria can be modified by the user by
selecting one-way and multi-destination options which would be displayed.
When
user click on search button and matched flight found then the detail of fare of
that flight will be also displayed with it.
There
is a choice for user to select a seat type i.e. business seat or economy seat.
6 There
is also an option of one way flight or round trip means multi-destination.
User
can reserve his seat by just clicking on reserve link and a message will
displayed you want to reserve seat if yes so seat will reserve and vice versa. The user must
complete all the necessary steps to reserve the flight for the seat reservation
to be guaranteed.
8. After
reserving flight user has also an option to modify the flight or modify his
information.9.
User
is also able to cancel his seat according to his wish.
In last user will logout and will come out to
main page again.
Details
(Admin):
1. Admin
for the first time should also use sign up so his information will save in
database.
2. The
admin must specify a valid e-mail when login into the system that email and
password should match database values.
3. Admin
has an authority to add a new flight.
4. Admin
is also able to delete a flight.
5. Modification
in flight details is also done by the admin.
6. Admin
can also modify an user information as for need.
7. Admin
can also view user whole details even a password.
8. All
the data of user is maintain by the admin.
4 Assumptions and Dependencies:
1.
The
user must have the ability to use the internet.
2.
The
user must have connected to the internet to use the system.
3.
The
users must have Window XP installed on system or later version platforms and
browser should be Google chrome.
4.
There
are two classes of tickets as listed below
·
Economy
class.
·
Business
class.
5.
The
flights will be assumed to be of a constant size that accommodates 150
passengers at a time. They will consist of :
·
50
Business class seats.
·
100
Economy class seats.
6.
The
accuracy of the information of the users is the responsibility of all users.
7.
It
is also assume that all the clients running this software are not blocked by
Firewalls, proxies etc.
5 System Architecture:
5.1 data flow
diagram:
5.2 data flow
diagram:
5.3 data flow
diagram:
5.4 data flow
diagram:
5.7 Class
diagram:
6. Use Cases:
User use Cases:
11.
Users
sign up.
12.
User
login.
13.
Search
for flight.
14.
Search
for fare.
15.
Make
Reservation.
16.
Modify
flight.
17.
Cancel
flight.
18.
Select
no of seats.
19.
Select
class.
20.
Reserve
flight type (1) one way (2) round trip.
21.
Logout.
Admin use Cases:
9.
Admin
login.
10.
Add
a flight.
11.
Delete/cancel
a flight.
12.
Modify
flight information
13.
Modify
user reservation
14.
Main
user information
15.
View
user information.
6.1 Use Case
Diagrams:
6.1.1 Use
Case:
6.1.1 Activity Diagram:
6.1.1 Sequence
Diagram:
6.2 Use Case
Description:
User
use cases
Use case Id: User Sign up
|
||||
Actors: User
|
||||
Feature: It will register a new user and save his data in database.
|
||||
Use case Id:
|
UC-1
|
|||
Pre-condition:
|
User
should log on.
|
|||
Scenarios
|
||||
Step#
|
Action
|
Software Reaction
|
||
1.
|
User selects the option
of Sign up.
|
System shows him
options.
|
||
2.
|
User
enters Name ,Dob, Email, password, phone no,
address, city, etc.
|
System will check
availability
|
||
3.
|
The user will have to provide all the necessary details. Present in
the user sign up form of the application.
|
System
will register him.
|
||
Alternate Scenarios:
|
||||
1a:
if detail is incomplete then he will not register
and system will show an error message.
2a: if details is already exists
then system show an error message that "User email id already exists
".
|
||||
Post
Conditions
|
||||
Step#
|
Description
|
|||
1.
|
All the details enter in the user sign up page
will be verified and accepted by the system into the database.
|
|||
Use Case Cross referenced
|
UC-2
|
|||
User Interface reference
|
U1-3
|
|||
Concurrency and Response
An estimate of the following
¨
100 users are assumed
¨
10 seconds
|
||||
Use case Id: User Login
|
||||
Actors: User
|
||||
Feature: It
denied un authorized user from entering the admin page
|
||||
Use case Id:
|
UC-2
|
|||
Pre-condition:
|
User
should have internet and must Registered.
|
|||
Scenarios
|
||||
Step#
|
Action
|
Software Reaction
|
||
1.
|
User click on Reservation menu.
|
System shows him log in
page.
|
||
2.
|
User
enters Email and password.
|
System will check him
in database and log him in.
|
||
3.
|
User can do further work.
|
|||
Alternate Scenarios:
|
||||
1a:
in case of wrong user name and password show him
error.
|
||||
Post
Conditions
|
||||
Step#
|
Description
|
|||
1.
|
If users change his name or password system
should update data base.
|
|||
Use Case Cross referenced
|
UC-1
|
|||
User Interface reference
|
U1-2
|
|||
Concurrency and Response
An estimate of the following
¨
100 users are assumed
¨
10 seconds
|
||||
Use case Id: Search for Flight
|
||||
Actors: User
|
||||
Feature: It
helps us for searching our concern flight.
|
||||
Use case Id:
|
UC-3
|
|||
Pre-condition:
|
User
should open the home page for searching flight.
|
|||
Scenarios
|
||||
Step#
|
Action
|
Software Reaction
|
||
1.
|
Click on the "Search Flights" option.
|
System shows him
matched flight details.
|
||
2.
|
User will enter source and destination for
searching flight.
|
System will Display concern flight.
|
||
3.
|
||||
Alternate Scenarios:
|
||||
1a:
if the concern flight does not match system will
show an error message.
|
||||
Post
Conditions
|
||||
Step#
|
Description
|
|||
1.
|
. If users change his name or
password system should update data base.
|
|||
Use Case Cross referenced
|
UC-4
|
|||
User Interface reference
|
U1-1
|
|||
Concurrency and Response
An estimate of the following
¨
100 users are assumed
¨
20 seconds
|
||||
Use case Id: Make Reservation
|
||||
Actors: User
|
||||
Feature: In this section
user make reservation.
|
||||
Use case Id:
|
UC-4
|
|||
Pre-condition:
|
User
should be login and also search for his flight.
|
|||
Scenarios
|
||||
Step#
|
Action
|
Software Reaction
|
||
1.
|
User will login.
|
System will check his authority.
|
||
2.
|
User will select type of trip one way or round
trip.
|
System will check availability of that option.
|
||
3.
|
User enters the destination city and source city name
|
System will check the availability of flight.
|
||
Alternate Scenarios:
|
||||
1a if there is not any flight available on desired
date system will give an error.
|
||||
Post
Conditions
|
||||
Step#
|
Description
|
|||
1.
|
Reservation
has been made and Database should be updated.
|
|||
Use Case Cross referenced
|
UC-3
|
|||
User Interface reference
|
U1-4
|
|||
Concurrency and Response
An estimate of the following
¨
150 users are assumed
¨
10 seconds
|
||||
Use case Id: Purchase Ticket
|
||||
Actors: User
|
||||
Feature: After
reservation user will purchase his ticket to confirm seat.
|
||||
Use case Id:
|
UC-5
|
|||
Pre-condition:
|
User
has successfully made a reservation as documented in the "Make a
Reservation" use case.
|
|||
Scenarios
|
||||
Step#
|
Action
|
Software Reaction
|
||
1.
|
Select the "Purchase Ticket" option.
|
System will display three different option of purchasing ticket i.e.
credit card, cheque, cash.
|
||
2.
|
.
|
|||
Alternate Scenarios:
|
||||
1a. if user does not purchase ticket within 28 hours
the reservation will be cancel.
|
||||
Post
Conditions
|
||||
Step#
|
Description
|
|||
1.
|
Ticket
will be given to him and his seat will be confirmed.
|
|||
Use Case Cross referenced
|
UC-4
|
|||
User Interface reference
|
U1-4
|
|||
Concurrency and Response
An estimate of the following
¨
150 users are assumed
¨
10 seconds
|
||||
Use case Id: Modify Reservation
|
||||
Actors: User
|
||||
Feature: User can modify
his information and also flight information if he commits some mistake
|
||||
Use case Id:
|
UC-6
|
|||
Pre-condition:
|
User
should be login.
|
|||
Scenarios
|
||||
Step#
|
Action
|
Software Reaction
|
||
1.
|
User login.
|
System verifies him
from database.
|
||
2.
|
User select edit option.
|
System will display him his details saved in
database.
|
||
3.
|
User will change his information and flight
details.
|
System updates the
database and shows a massage.
|
||
Alternate Scenarios:
|
||||
1a. in case of database connectivity error, system should show an error.
|
||||
Post
Conditions
|
||||
Step#
|
Description
|
|||
1.
|
New
user information will be replaced with old information in database.
|
|||
Use Case Cross referenced
|
UC-5
|
|||
User Interface reference
|
U1-4
|
|||
Concurrency and Response
An estimate of the following
¨
150 users are assumed
¨
10 seconds
|
||||
Use case Id: Cancel Reservation
|
||||
Actors: User
|
||||
Feature: It
help the user to cancel his flight if he don't want yet
|
||||
Use case Id:
|
UC-7
|
|||
Pre-condition:
|
User
should be login.
|
|||
Scenarios
|
||||
Step#
|
Action
|
Software Reaction
|
||
1.
|
User login.
|
System verifies him
from database.
|
||
2.
|
User select cancel option.
|
System will give him a warning message.
|
||
3.
|
User cancel the reservation
|
System updates the
database and shows a massage.
|
||
Alternate Scenarios:
|
||||
1a. In case of database connectivity error, system should show an error.
2a. In case of light going the customer should be log in again and then perform
again each step.
|
||||
Post
Conditions
|
||||
Step#
|
Description
|
|||
1.
|
System
should cancel reservation after check database record.
|
|||
Use Case Cross referenced
|
UC-4
|
|||
User Interface reference
|
U1-4
|
|||
Concurrency and Response
An estimate of the following
¨
150 users are assumed
¨
10 seconds
|
||||
Use case Id: User Logout
|
||||
Actors: User
|
||||
Feature: User session
will destroy and it will bring user to main page
|
||||
Use case Id:
|
UC-8
|
|||
Pre-condition:
|
User
should be login via using login use case.
|
|||
Scenarios
|
||||
Step#
|
Action
|
Software Reaction
|
||
1.
|
User login.
|
System verifies him
from database.
|
||
2.
|
User select logout option.
|
System will close his session and home page will
be displayed.
|
||
.
|
||||
Alternate Scenarios:
|
||||
1a. User closes the browser which leads to finish his/her session.
|
||||
Post
Conditions
|
||||
Step#
|
Description
|
|||
1.
|
System
should close his/her session.
|
|||
Use Case Cross referenced
|
UC-2
|
|||
User Interface reference
|
U1-5
|
|||
Concurrency and Response
An estimate of the following
¨
100 users are assumed
¨
10 seconds
|
||||
Use case Id: Admin Sign up
|
||||
Actors: Admin
|
||||
Feature: It will
register a new admin and save
his data in database.
|
||||
Use case Id:
|
UC-9
|
|||
Pre-condition:
|
Admin
should log on.
|
|||
Scenarios
|
||||
Step#
|
Action
|
Software Reaction
|
||
1.
|
Admin selects the
option of Sign up.
|
System shows him
options.
|
||
2.
|
User
enters Name ,Dob, Email, password, phone no,
address, city, etc.
|
System will check
availability
|
||
3.
|
The Admin will have to provide all the necessary details. Present in
the admin sign up form of the application.
|
System
will make him admin. But there will be constraint not every 1 is able to
become an admin only owner of the system will be admin and the people he
want.
|
||
Alternate Scenarios:
|
||||
1a:
if detail is incomplete then he will not become
admin and system will show an error message.
2a: if detail is incorrect then system
shows an error.
|
||||
Post
Conditions
|
||||
Step#
|
Description
|
|||
1.
|
All the details enter in the admin sign up page
will be verified and accepted by the system into the database.
|
|||
Use Case Cross referenced
|
UC-10
|
|||
User Interface reference
|
U1-3
|
|||
Concurrency and Response
An estimate of the following
¨
3 admins are assumed
¨
10 seconds
|
||||
Use case Id: Admin Login
|
|||
Actors: Admin
|
|||
Feature: It denied un
authorized user from entering the admin page.
|
|||
Use case Id:
|
UC-10
|
||
Pre-condition:
|
User
should have internet and must Registered.
|
||
Scenarios
|
|||
Step#
|
Action
|
Software Reaction
|
|
1.
|
Admin click on Reservation menu.
|
System shows him log in
page.
|
|
2.
|
Admin
enters Email and password.
|
System will check him
in database and log him in.
|
|
3.
|
Admin can do further work.
|
||
Admin
use cases
11 Gantt chart:
References:
Software
Requirements, Second edition By Kerl.E.Wiegers
