Airline Reservation System

Software Requirements Requirements Specification for 

Version 1! appro"e#

$repare# %&'

Ars(an A)*ar+!,-./

0mair Ra)a+!./

A R Ars(an+!-1./

M 0sman+11,.



Copyright

© 1999

by Karl E. Wiegers. Permission is granted to use, modify, and distribute this document.

Software Requirements Specification for

Page ii

Table of Contents Table of Contents...........................................................................................................................ii Revision History.............................................................................................................................ii 1. Introduction............................................................. .................................................................1 1.1 1.2 1.3 1.4 1.5

Purpose........................................................................................................................................... 1 Document Conventions..................................................................................................................1 Intended Audience and Reading Suggestions............................................................................... ..1 Product Scope................................................................................................................................. 1 References.....................................................................................................................................1.

2. Overall Description...................................................................... ............................................2 2.1 2.2 2.3 2.4 2.5 2.6 2.7

Product Perspective........................................................................................................................2 Product Functions...........................................................................................................................2 User Classes and Characteristics............................................................................................... .....2 Operating Environment......................................................................................................... .........2 Design and Implementation Constraints.........................................................................................2 User Documentation.......................................................................................................................2 Assumptions and Dependencies.....................................................................................................3

3. External Interface Requirements......................................................... ..................................3 3.1 3.2 3.3 3.4

User Interfaces................................................................................................................................ 3 Hardware Interfaces........................................................................................................................ 3 Software Interfaces.........................................................................................................................3 Communications Interfaces.......................................................................................................... ..3

4. System Features............................................................. ..........................................................4 4.1 System Feature 1.......................................................................................................................... 4 ..

5. Other Nonfunctional Requirements.................................................... ...................................4 5.1 5.2 5.3 5.4

Performance Requirements.............................................................................................................4 Safety Requirements.......................................................................................................................5 Security Requirements.................................................................................................................... 5 Software Quality Attributes............................................................................................................5

6. Other Requirements....................................................................... .........................................5 Appendix A: Glossary....................................................................................................................5 Appendix B: Analysis Models.......................................................................................................5 Appendix C: To Be Determined List............................................................................................6

Revision History Name

Date

Reason For Changes

Version

Software Requirements Specification for

1.

Introduction

1.1

Purpose :

Page 1

The main purpose of this vision document is to list the requirements of the Airline Reservation System project. This document also helps us to collect and analyze the ideas gathered for the  project. This vision document will be subject to change, if more requirements are added to the  project. This document is mainly prepared to set stage for the design phase of the project. The document being prepared is the first version of vision document for the Airline Reservation System project. !."#T is a new technology which is being used a lot in the $T field. %y interest to learn this new technology has prompted me to ta&e up this project.

1.2

Document Conventions:

 All system development activities should follow the final version of this document. Any discrepancy that found during in later phases should be modified subject to SRS. 'owever, this document may be subject to change dependent on the decision of the group members.

1.3

Intended Audience and Reading Suggestions: 

Reading sequence $ntroduction (verall description #)ternal interference Requirement  System *eatures (ther "on *unctional Requirements • • • • •

•

1.4

(ther Requirements

Product Scope:

The name of the software is +A$R$"# R#S#R-AT$(" SST#%/.This software provides options for viewing different flights available with different Timmings for a particular 0ate and  provides customers with the facility to boo& a Tic&et,%odify or ancel a particular Reservation but  it does not provide the customers with the details of cost of the tic&et and it does not allow the customers to modify a particular part of his reservation and he can modify all his details.

1.5

References:

Some of the references used for preparing the vision document include1 2. http133in&board.sourceforge.net3docs3-ision0ocument.pdf  4. www.orbitz.com

Software Requirements Specification for

Page 2

5. $### document for Software Requirements Specifications 6. #70raw software is used to generate the use case diagrams 8. 9i&ipedia :. %S# ;ortfolio presentation $ lecture by 0r. 0eloach, on the $S website would set the stage for the applications $ would be developing in the future.

2.

Overall Description

2.1

Product Perspective:

The Airline Reservation System project uses the "et *rame9or& and is completely independent. The project itself is a bigger product and does not need to be introduced into a larger system. The application would be running on a 9indows < ultimate (perating system.

2.2

Product Functions:

The major functions include ;roviding flight details *light boo&ings for a particular destination, date and time and also providing with a pin code.  Allowing the customer to modify or cancel his reservation provided the correct pin code is given. 0isplaying a report of the number of people flying in a particular flights. • •

•

2.3

User Classes and Characteristics:

There are two &inds of users for the Airline Reservation System. (ne is the customer and the other is the administrator. The customers do not need to have any prior training to use the application. 'owever, instructions for ma&ing flight and motel reservations would be provided to them on the airline website. The administrators would however need to be trained in order to use the application. They may wish to update3add3delete any information in online reservation database . They may need to create and manage temporary views of fetched records from the databases of airlines  .

2.4

Operating Environment:

 Airline Reservation System should be accessed using any popular versions of the following 9eb browsers1 %icrosoft $nternet #)plorer, %ozilla *irefo), and =oogle hrome.

Software Requirements Specification for

2.5

Page 3

Design and Implementation Constraints:

The system database design will be based #R modeling which will in turn transfer to database schema formulated using S> 00 statements. All 'T% code should conform to the 'T% 6.? standard.

2.6

User Documentation: *inal release will be accompanied with a user guide to inform new users how to use  Airline Reservation System. The system will be designed as user friendly as possible.

•

•

2.7

Assumptions and Dependencies: •

• •

•

@sers of Airline Reservation System are assumed to have a computer with internet access. redit and debit card authorization services are assumed to be available.  Airline Reservation System has collaboration with every airlines databases thus it must be able to communicate with these systems. Also it has to obey airlines business rules. (nly domestic flights are supported.

3.

External Interface Requirements

3.1

User Interfaces:

There are two types of users for the Airline Reservation System project. (ne 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 follows1 The =raphical @ser $nterface would mainly consist of 'yperlin&s, 0ata entry fields li&e the #7mail $d field, push down buttons li&e the ogin button etc. The administrator of the website would also have a similar =raphical @ser $nterface. After an administrator logs onto the system, the home  page for the administrator would be as follow.

3.2

Hardware Interfaces: "o hardware interface specified for Airline Reservation System.

Software Requirements Specification for

3.3

Page 4

Software Interfaces:

The application should run on a 9indows < @ltimate (perating System. Since the application needs a database to store all the customer details, airline, motel and pac&age information. -isual Studio would be used for creating the application. All the coding will be done in .

3.4

Communications Interfaces •

•

4.

 Airline reservation System should send an e7mail message to the user to confirm the acceptance of acceptance of reservation.  Airline Reservation System is a 9eb7database system, all &inds of user7system interaction is presented by user7side web browser. So the communication standard is 'TT; protocol.

System Features: The search feature allows the user to search for an airline flight on a variety of dimensions.

4.1

System Feature 1

4.1.1

Description and Priority: •

•

•

•

•

•

•

•

•

This *eature allows users to boo& a reservation for a trip. @ser will be able to specify the *light lass which will be with respect to the flight chosen. C;riority D owE  The user will be able to choose from a listing of available seats. C;riority D owE  The system shall accept reservations for 2 person per flight and seat number. C;riority D 'ighE  The user must complete all the necessary steps to boo& the flight for the seat reservation to be guaranteed. C;riority D 'ighE  The user must specify a valid e7mail address when boo&ing a flight. C;riority D 'ighE @sers may only boo& flights within the @nited States. C;riority D 'ighE   All times displayed are e)pressed in local time, specific to the location. C;riority D 'ighE  The user will only be able to boo& flight within one year of the present date. Futoff  time may be appliedG C;riority D 'ighE

Software Requirements Specification for

•

4.1.2

Page 5

 After boo&ing, the user may cancel3modify their flight. C;riority D owE 

Stimulus/Response Sequences:  Reservation @se case  @se ase $01 2  @se ase "ame1 ;lace reservation reated By1 Arsl   ast @pdated By1 Arsl   0ate reated1 ?:3?H34?2:   0ate ast @pdated1 ?832?34?2:   Actors1 ustomer   0escription1 A customer accesses the A*$RS from the $nternet, optionally search for specific tic&et3flight information of interest, selects tic&etFsG, and places reservation.  ;reconditions1 "one  ;ost conditions1 2. 0atabase of available tic&ets is updated to reflect items in this order.  4. Remaining tic&ets number is updated.  "ormal *low1 2.? (rder a Single Tic&et   2. ustomer uses the web interface to enter a certain query to view flight information for a specified interest.  4. System displays available flight information satisfied the query.  5. ustomer selects one or more items from page. ustomer can also clic& on a particular tic&et to see the detailed information.  6. System displays reservation with detailed price information including all ta)es.  8. ustomer confirms reservation or requests to modify reservation Fbac& to step 5G.  :. ustomer specifies payment method.