Airline Reservation System

MSE Project Phase 2 Presentation

-- Kaavya Kuppa Committee Members: Dr.Daniel An resen Dr.!orben Amto"t Dr. Mitchell #. $eilsen

Agenda
Action

Items from Phase I Architecture Design Formal Requirements Specification Test Plan Architecture Prototype Formal Technical Inspection Letters Questions

Action Items from Phase I

!he use cases "or the Airline %eservation System &ere not numbere in the 'ision ocument. So( ) numbere them an correcte the ocument. !he basis "or assi*nin* values to some o" the e""ort a justment "actors &as not mentione clearly. So( ) mentione the reasons "or selectin* the values "or some o" the important "actors. !he e+planation "or some o" the use cases &as not very clear( so ) *ave a clear e+planation o" the use cases. All the up ate ocuments are uploa e at http:,,people.cis.-su.e u,.-aavya,MSE/20P%12EC!PA3E.htm

Architecture Design
The architecture of the Airline Reservation System pro ect follo!s the three"tier architecture#

Presentation !ier

This includes the ASP#$%T !e& forms and the ASP#$%T user controls for the Airline Reservation system pro ect# This includes the '( classes or the '( &usiness components for the pro ect This includes the Data&ase servers for the Airline Reservation System pro ect# SQL server )*** is used as the Data&ase server in this case#

4usiness #o*ic !ier

Data Access !ier

Architecture Design continued##

The Architecture Design of the Airline Reservation System follows the three-tier architecture. 1. Presentation Tier 2. Business Logic Tier . Data!ase Tier The architecture "esign of the Airline Reservation System has !een re#resente" with the hel# of the $lass Diagram an" the Se%uence Diagram.

'lass Diagram

Page Flo! Diagram for +ser

Page flo! diagram continued##

ASP.&'T (e! )orms Home.aspx Register.aspx Customer.aspx !lightSear h.aspx !light"oo#ing.aspx $a #ageSear h.aspx $a #age"oo#ing.aspx P*RP+S' The home page for the Kansas Air Airline Reservation System website The page provided for the Customer Registration The home page that appears after the ustomer logs in The page whi h helps the ustomer to sear h for the available flights The page whi h enables the ustomer to ma#e reservations for the flights available online. The page whi h helps the ustomer to sear h for the pa #ages available. The page whi h enables the ustomer to ma#e reservations for the pa #ages available online.

Page flo! diagram continued##

HotelSear h.aspx Hotel"oo#ing.aspx About.aspx The page whi h helps the ustomer to sear h for the available hotels and rooms in ea h hotel. The page whi h enables the ustomer to ma#e reservations for the hotel rooms available online. This page gives the ustomer some information about the Airline Reservation System website.

Formal Requirements Specification

Each

customer shoul have a uni5ue useri Each customer shoul have a uni5ue email i no t&o "li*hts have the same "li*ht number. 6otel has multiple rooms A "li*ht shoul have 789 number o" seats

Formal Requirements Specification continued##

class :ser attributes useri : strin* pass&or : strin* emaili : strin* name: strin* lo*instatus : 4oolean operations 'eri"y#o*in;email : strin* ( pass&or : strin*< : 4oolean 8 user.all)nstances -7 e+ists ;u: user = u.emaili 8 emaili an u.pass&or 8 pass&or < en

Test Plan
!he

main purpose o" the test plan "or the Airline %eservation System is to iscuss the testin* etails o" the use cases o" the Airline %eservation System. !he so"t&are project test plan also escribes the objective( scope an approach o" the so"t&are testin* e""ort "or the Airline %eservation System project.

Test Plan continued##

!he main objectives o" the test plan are as "ollo&s: !o i enti"y the "eatures o" the system that &ill be teste . !o i enti"y an e"ine all the activities necessary to prepare "or an con uct the testin* process on the Airline %eservation System !o e"ine the pass,"ail criteria "or each item that &ill be teste !o i enti"y the eliverables o" the testin* phase. !o e"ine any suspension criteria an resumption techni5ues !o iscuss the testin* techni5ues bein* use to test the Airline %eservation System.

Test Plan continued##

The different types of testing are,

+nit Testing , The +nit Testing is a test that tests each single module of the soft!are to chec- for errors# This is mainly done to discover errors in the code of the Airline Reservation System# The main goal of the unit testing !ould &e to isolate each part of the program and to chec- the correctness of the code# System Testing, The system testing is mainly done on the !hole integrated system to ma-e sure that the pro ect that has &een developed meets all the requirements Acceptance Testing, This testing is generally performed !hen the pro ect is nearing its end# This test mainly qualifies the pro ect and decides if it !ill &e accepted &y the users of the system#

Test Plan continued##

!he test items "or the Airline %eservation System project are as "ollo&s: #o*in Search an boo- "li*hts Search an boo- pac-a*es Search an boo- hotels %e*ister

Architecture Prototype " Pro ect .ome Page

Architecture Prototype /+ser home page

Architecture Prototype" Flight Search

Formal Technical Inspection Letters

!he "ormal technical inspection letters are bein* submitte by : San hya 4athini Sruno-shi $eela-antan

Questions 0