Airline Reservation System REQUIREMENTS Analysis-libre

7/22/2019 Airline Reservation System REQUIREMENTS Analysis-libre

http://slidepdf.com/reader/full/airline-reservation-system-requirements-analysis-libre 1/27

REQUIREMENTS Analysis

Documentation for

Air ticket reservation

system (ATRS)

Team Composition

Project Title Air ticket reservation systemPrepared By S No. Name ID. No. Email/Mobile Responsibility

1 Abey Getachew 03034628 [email protected] Team leader

2 Daniel Gebrehiwot 03035200 [email protected]

3 Ledetu Tekle 03035313

4 Ephrem Mitiku 02021962

5 Fuad Mudesir

Date

Advisor

mailto:[email protected]





1. INTRODUCTION

1.1 PURPOSE AND MOTIVATION

The main purpose of this vision document is to list the requirements of the AirlineReservation System project. This document also helps us to collect and analyze theideas gathered for the project. This vision document will be subject to change, if morerequirements are added to the project. This document is mainly prepared to set stage forthe design phase of the project. The document being prepared is the first version ofvision document for the Airline Reservation System project.

1.2 Scope of the project

This project designs and implements air ticket reservation system. Supported by a well-designed

database, all available air flight information is integrated together and can be accessed easily

through a single point. A friendly user interface is provided so that various combinations of

search criteria can be fetched from user and generates corresponding database search statements.

The air ticket reservation system provided both customer and administration interfaces with the latter

used for administration purposes. If time permits, the reservation system will support frequent user

registration and personal information management.

1.3 Objective of the project

General Objective:

The main goal of the proposed system is to make online the processes of the air ticket reservation and

cancelation system.

Specific Objectives:

Some of the Specific Objectives of the system are listed below:

To create a distributed system that will be used by customers.

To ensure that ticket reservation is easy and user friendly for customers.

To satisfy customers need by reaching them at their place.



1.3 PROJECT OVERVIEW

The Airline Reservation System project is an implementation of a general Airline

Ticketing website, which helps the customers to search the availability and prices of

various airline tickets, along with the different packages available with the reservations.

This project also covers various features like online registration of the users, modifying

the details of the website by the management staff or administrator of the website, by

adding, deleting or modifying the customer details, flights or packages information. In

general, this website would

be designed to perform like any other airline ticketing website available online.

1.4 REFERENCES

Some of the references used for preparing the vision document include:

1. http://inkboard.sourceforge.net/docs/VisionDocument.pdf

2. www.orbitz.com

3. IEEE document for Software Requirements Specifications

4. E-Draw software is used to generate the use case diagrams

5. wikipedia

2 EXISTING SYSTEM

The existing system is manual entry of up keeping of the details of the persons who are

registered already. And it is very difficult for each person to come to the office. Userscan also enquire about the tickets through phones. It is very difficult for the user toremember all the



details that they received through phones. And it is also very difficult to calculate howmany peoples registered in a month by hand. This requires quite a lot of time andwastage of money as it requires quite lot of manpower to do that. Another factor thattakes into account that is the possibility of errors and which requires verification andchecking of data relating to various operations which is done manually. Data's are

stored globally and are retrieved in the same manner. Most of the data are hidden fromoutside the world. The limitations of existing system are that it is not all personalized. Itcannot be used for personal and quick reference. Even the other staff members canmake quick entries if the responsible person is not present.

3 PROPOSED SYSTEM

3.1 proposed system Overview

The modern computerized system is developed with the aim to overcome thedrawbacks of existing system. The proposed system has got many advantages. People

from different parts of the world can register very easily. The new system is morepersonalized. It is maze in such a manner that all the new users can understand all theoptions in it very easily. It is made in a quick and easy referential manner. This systemhelps the user to go through the rates quoted by different travel agencies and select theconvenient rate that is suitable for him.

Access to all important matters are not always locked and can be opened easily at thetime of urgency. The advantages of proposed system are that security is maintained inthe new system. Securities for all important data are maintained confidentially. As it iseasily understandable and user friendly, quick entries can be made in this system.

3.2 FUNCTIONAL REQUIREMENTS

The functional requirements of the Airline Reservation System are divided among

the

Customer and the administrator of the application.

These functional requirements can be explained in detail as follows:

1.1 Use Case name: User Registration

Description: This use case describes the scenario where the user registers with

the application by providing all the necessary details, in order to make

reservations or bookings for flights, motels, special packages.

Actor: User or the Customer



Input: The user or the customer will have to provide all the necessary details

present in the customer registration form of the application.

Output: All the details entered in the customer registration page will be verified

and accepted by the system into the database.

1.2 Use Case name: User Login

Description: This use case describes the scenario where the user logs into the

application, with the username and password he has provided while registering

with the system.


Input: The user or the customer creates a username and password at the time of

registering with the system. He then uses them to logon to the system and make

reservations or view any information.

Output: The application then verifies the authenticity of the username and

password that the customer has provided and allows the user to view the

information available on the system, if the username and password are valid.

1.3 Use Case name: Contact the company

Description: This use case describes the scenario where the user contacts the

company for any information.


Input: The customer can contact the airline company, requesting them for any

information he needs.



Output: The application verifies the authenticity of the username and password

that the customer has provided and allows the user to view the contact

information for the company.

1.4 User Case name: Booking Instructions

Description: This use case describes the scenario where the user views the

instructions for booking flights, packages, or motels.


Input: After the customer logs onto the application with his username and

password, he can look up the instructions posted on the website for booking

flights, packages or motels.


and displays the how to book instructions page.

1.5 Use Case name: Book Flights

Description: This use case describes the scenario where the user books airline

tickets.


Input: After logging into the application, the customer looks up the information

related to various airlines and checks the availability of seats on flights. If he finds

that there are any available tickets, he then purchases them.


and then displays information related to various flights to the customer.



1.6 Use Case name: Book Motel

Description: This use case describes the scenario where the user books motels

at the time of airline ticket reservation

Actor: Customer or the user

Input: After logging onto the application, the customer looks up the information

for all the available motels at his destination.


and then displays information pertaining to various motels at the customer’s

destination.

1.7 Use Case name: Booking Packages

Description: This use case describes the scenario where the user books

different touring packages at the airline ticket reservation

Actor: Customer or the user

Input: The customer looks up information regarding various touring packages

available at his destination at the time of airline ticket reservation.


of the customer and then displays information of various touring packages

available at customer’s choice of place.

The administrator activities use cases will be described here:

1.8 Use Case name: Login/Logout

Description: This use case describes the scenario where the administrator of

theapplication, logs into the system and logs out after the work is done.

Actor: Administrator

Input: The administrator of the website logs into the application with the

username and password provided to him.



Output: The application verifies the authenticity and displays the home page of

the administrator.

1.9 Use Case name: Add/Delete or Modify Customer information

Description: This use case describes the scenario where the administrator

adds, deletes or modifies customer information in the system database


Input: The administrator of the applications logs onto the system with his

username and password.

Output: The application authenticates the administrator, and then displays thepage where the administrator can add new customers to the database, or delete

existing customers or modify details of customers in the database.

1.10 Use Case name: Add/Delete or Modify flight information


adds, deletes or modifies flight information in the application database


Input: The administrator logs onto the system with the username and password

provided to him.

Output: The application authenticates the administrator, by verifying the

username and password. Then the application displays the page where the

administrator can add new flights to the database, delete the flights that have

been cancelled or modify information for the flights. Hour

1.11 Use Case name: Cancellation of Reservations


handles the cancellation of reservations by the customers.




Input: The administrator logs onto the system with the given username and

password.

Output: The application authenticates the administrator and then displays the

page where the administrator looks up the id of the customer who has requested

cancellation of reservation. After canceling the reservation, the administrator thensends a confirmation e-mail to the customer.

1.12 Use Case name: E-mail confirmations


sends e-mail confirmations to the customers of the application.


Input: The administrator logs onto the application with the username and

password provided.

Output: The application then authenticates the administrator and displays the

page where the administrator can send e-mail confirmations to the customer.

These e-mail confirmations may be sent in cases where the customer has

cancelled a reservation or changed the personal information available on the

website.

1.13 Use Case name: Modifying details of webpage

Description: This use case describes the scenario where the administrator logs

onto the application to modify the details of the airline website


Input: The administrator logs onto the application with the username and

password provided to him

Output: After verifying the username and password of the administrator, the

application then allows the administrator to login. The administrators can then

browse through the website and change the details of any webpage in the Airline

Reservation system application.



1.14 Use Case name: Add/Delete or Modify Motel information


adds, deletes or modifies motel information in the database.



provided to him.



administrator can add new motels to the database, delete a specific motel from

the list of motels, since there are no more available rooms there. He can even

update the price per room of each motel. To make it easier, the administratormight assign a unique id for each hotel.

1.15 Use Case name: Add/Delete or Modify package information


adds, deletes or modifies package information in the application database



provided to him.



administrator can add new packages to the database, delete the packages that

are no longer available or modify information for any particular package.

3.3 Nonfunctional Requirements

1 Performance Requirements The system shall accommodate 400 users during the peak usage time

window of 2:00am to 4:00am local time

All Web pages generated by the system shall be fully downloadable in nomore than 10 seconds.



Responses to queries shall take no longer than 10 seconds to load ontothe screen after the user submits the query.

The system shall display confirmation messages to users within 4 secondsafter the user submits information to the system.

2 Security Requirements

Users shall be required to log in to the system for their own reservationinformation and modification with e-mail address and password.

The system shall permit only authorized members who are on the list ofauthorized Menu Managers to do administrator’s task.

The system shall permit customers to view only their own previouslyplaced orders, not orders placed by other customers.

3 Software Quality Attributes Availability: The system shall be available to users on the Internet 99.9%

of the time. And should be available to administrators all the time.

Robustness: If the connection between the user and the system is brokenprior to an order being either confirmed or canceled, the system shallenable the user to recover an incomplete reservation.

Consistency: The ticket availability in system shall be updated when atransaction (more, administrator’s update operation) is finalized to ensurethat the most updated information is delivery to any following queries fromother customers. When administrator is updating the information, theconsistency should also hold among user view.

3.4 EXTERNAL INTERFACES

The different types of interfaces that we would come across while developing the

Airline

Reservation System application are as follows:• User Interface

• Hardware Interface

• Software Interface



3.4.1 USER INTERFACE

There are two types of users for the Airline Reservation System project. One is

the

customer and the other is the administrator. Both the customer and administrator

user interface

would be a graphical user interface. The graphical user interface for the customer

home page would be as follows:

Figure representing the sample Customer GUIThe Graphical User Interface would mainly consist of Hyperlinks, Data entry

fields like

the E-mail Id field, push down buttons like the Login button etc.

The administrator of the website would also have a similar Graphical User

Interface.

After an administrator logs onto the system, the home page for the administrator

would be as

follows:



Figure representing the sample Administrator Interface

3.4.2 HARDWARE INTERFACE

The Airline Reservation System does not use any hardware interface

3.4.3 SOFTWARE INTERFACE

The application should run on a Windows 8 Operating System. Since the

application needs a database to store all the customer details, airline, motel and

package information, MySQL would be used.Visual Studio.NET 2003 would be used for creating the application. All the coding

will be done in C#.



3.5 System models

3.5.1 Scenarios

1 The business scenario (Register Profile) is as follows:

The customer should register himself in order to proceed to book ticket service.

The customer needs to input all the required particular details during the

registration process.

The web service will perform validation checks on customer input and length

constraints.

Upon successful login, the customer will be registered officially to the web service

and he can login using his username and password.

The guest is only permitted to check flight availability.

2 The business scenario (Update Profile) is as follows:

The customer should login by himself in order to perform update profile process.

The customer will only change those fields that need to be updated.

Then, any changes will be updated respectively.

3 The business scenario (Check Flight) is as follows:

The customer is permitted to search available flights based on the origin city,

destination city, departure date and return date.

The web service will display any matching records based on the search criteriaentered.

The web service will notify the customer about the flight availability.

If the searched flights are available, then web service will display flights which are

within a week. Otherwise, the web service will prompt to ask the

user to re-enter new searching criteria.

4 The business scenario (Book Ticket) is as follows:

From the Check Flight, the customer is required to log in and the web service will

prompt the customer to confirm the flights.The web service will then ask the customer whether to update his profile details or

not.

Subsequently, the customer will be asked to purchase and confirm the selected flights.



5 The business scenario (Cancel Ticket) is as follows:

The customer is required to be logged in before he has privilege to cancel his

confirmed tickets.

The customer will select which ticket to be cancelled in the booking history.

Once the confirmed ticket has been selected then theweb service will delete the data

off from the database.

The customer is given cancellation ID upon successful transaction.

6 The business scenario (View Booking Status) is as follows:

The customer is required to be logged in before he has privilege to cancel his

confirmed tickets.

The customer will select details in the booking history to view booking status

7 The business scenario (Pay Ticket) is as follows:

After Book Ticket, the web service will generate payment ID upon successful

transaction is made.

Once it has been confirmed, the web service will generate booking id to the customer

and require the customer to print out the mini itinerary receipt..



3.5.2 Use case model

Use Case Description

The above use case diagram depicts all the functions or activities that a user or a

customer can perform on the application. They can be discussed in detail as

follows:

Home Page: Like all the other airline websites available online, the user can

access the user home page of the Airline Reservation System website, after he



logs into the system.Here, he can look up information regarding flights, packages

and motels.

Login and Register: The Airline Reservation System also comes with the

customer registration details page, where the customer can enter his details and

register. He can also create a username and password. Moreover, he will also be

able to modify the registration information in case of a change in his e-mail

address or any other information.

Booking Flights: The customer can also search for the flights available and

reserve his place on the flight by purchasing a ticket.

Book Motels: Different Airline websites like Orbitz also offer various deals for

booking Motels along with the airline tickets. So, the customer will also be able to

view this functionality on the website.

Book Packages: This functionality is similar to the motel booking function,

except the fact that the customer can look up various touring packages available

at the person’s destination.

Contact the Company: The Customer can also call the company if he has any

concerns or questions related to the bookings he has made online.

Booking Instructions: The website also provides instructions to the customers

on how to book airline tickets or motels along with the different packages.Some of the functions of the Airline Reservation System, such as creating,

maintaining and updating the database are available only to the administrator.



The functions of the administrator, explained in detail are as follows:

Some of the functions of the Airline Reservation System, such as creating, maintainingand updating the database are available only to the administrator. The functions of theadministrator, explained in detail are as follows:

Administrator Activities

Login/Logout: The administrator has to login first in order to be able to makechanges to the Airline Reservation System, by adding, deleting or modifying the

data in the Airline Reservation System database. After making the necessary

changes, he then has to logout of the system, in order to prevent misuse of the

data.

Add/Modify Customer Information: Daily the Airline Reservation System will

have many customers registering with the website and many of them

unsubscribing. Only the administrator will have the sole rights to modify the

database accordingly.

Add/Modify Flight Information: The Administrator also has the sole rights to

add, delete or modify the flight information. Sometimes, flights get cancelled for

some reason, so such flights would be removed from the list of flights available to

the customer. Similarly whenever any flight information has to be modified or if

any new flights need to be added to the database, these operations are

performed by the administrator.

Add/ Modify Motel Information: The administrator can also add/delete or

modify information related to different motels. This information can be thenumber of rooms available at the motel, the prices etc.

Cancellation of Reservations: Sometimes, after making a reservation, a

customer might cancel the reservation he has made. So, the administrator also

handles such special situations and sends the customer an e-mail confirmation

after deleting the specific transaction.



E-mail confirmations: Whenever a customer makes or cancels a reservation,the administrator is responsible for sending confirmation e-mails to the customer,confirming the transaction.



3.5.3 Object model

4.1 CLASS DIAGRAM

The class diagram of the Airline Reservation System project would be as follows:



CLASS DESCRIPTIONS (Data Dictionary)

1 USER

The user class is responsible for handling all the user functions. This user classis the super class or the base class for two types of users namely the customer

and the administrator. The user logging into the system will be mainly verified for

their username and password., which is the email id for the customer and a

username for the administrator.

2 ADMINISTRATORS

The administrator class is the sub class of the user class. This class is mainly depictedhere to define all the attributes and functions carried out by the administrator of theAirline Reservation System website. The attributes for the administrator of the AirlineReservation System website are the userid and password, which the administrator usesto log on to the Airline Reservation system website. The administrator would be able to



perform the tasks of adding or updating the information for flights, motels and packagesetc.

3 CUSTOMER

The customer class has been depicted here as it is a sub class for the super class userof the Airline Reservation System project. The attributes for the customer would be theuserid, password, customer name, email id, credit card number, address, phone

number.

The functions that the customer of the website would be able to perform are :

Register() – the customer would be able to register onto the system

Login() - the customer can login with the email id and password



Logout() – the customer would be able to logout of the system

Browse () – the customer can browse through the website

Searchflights() and bookflights() – the customer would be able to search and book the

flights available on the website.

Searchpackages() and bookpackages() - the customer would be able to search andbook packages available on the website

Searchhotels() and bookhotels() - the customer would be able to search and book forthe hotels available on the website

4. PACKAGE

The class package is depicted in the class diagram to represent the set of packagespresent in the application. The customer can book packages using the PackageSearchpage. Package generally has the following attributes:

Package id – a unique id given to a packagePackage name – the name of the packagePackage location - the location of the package…it indicates the place where thepackage is availablePackage price – the price of the package





6 HOTEL

The class hotel is depicted in the class diagram to represent the set of hotels present inthe application. The customer can book hotels using the HotelSearch and HotelBooking

page.A Hotel available in the Airline Reservation System application generally has the

following attributes:

hotel id – a unique id given to a hotel

hotel name – the name of the hotel

location - the location of the hotel

number of rooms – the number of rooms available at each hotel

price – the price of each room in a hotel



3.5.4 SEQUENCE DIAGRAMThe sequence diagram for the Customer of the Airline Reservation System would be asfollows:

3.5.5 User interface — navigational paths and screen mock-ups

1 USER INTERFACE

There are two types of users for the Airline Reservation System project. One is the

customer and the other is the administrator. Both the customer and administrator

user interface would be a graphical user interface. The graphical user interface for

the customer home page would be as follows:



Figure representing the sample Customer GUI

The Graphical User Interface would mainly consist of Hyperlinks, Data entry

fields like

the E-mail Id field, push down buttons like the Login button etc.

The administrator of the website would also have a similar Graphical User

Interface.

After an administrator logs onto the system, the home page for the administrator

would be as follows:

Documents

Airline Reservation System REQUIREMENTS Analysis-libre