57
Case Study:Airline Reservation System Submitted By:Prashant Kumar Singh:391385 Vinitesh Garima:391368 Amit Pal Singh:391390 Randhir Kumar Pandey:391375

AIRLINE_RESERVATION_GRP08

Embed Size (px)

Citation preview

Page 1: AIRLINE_RESERVATION_GRP08

Case Study:Airline Reservation System

Submitted By:Prashant Kumar Singh:391385Vinitesh Garima:391368Amit Pal Singh:391390Randhir Kumar Pandey:391375

Page 2: AIRLINE_RESERVATION_GRP08

Introduction• Airline Reservation System is a automated

project with following functionalities• Customer TransactionSearch FlightBook TicketCancel ticket• Administrator TransactionFare managementInventory management

Page 3: AIRLINE_RESERVATION_GRP08

Assumptions:

•We have assumed that all the planes have capacity which is equal to 1000•We are assuming that the passenger will not postpone or prepone his schedule•Our Airline Reservtion System operates only for domestic routes

Page 4: AIRLINE_RESERVATION_GRP08

Stake Holders:

•Passengers:Passengers are the main beneficiaries of the Airline Reservation System •Airline Staff:The revenue generated by this system helps tp pay the Airline Staff

Page 5: AIRLINE_RESERVATION_GRP08

System Requirements:

•Intel Pentium4 2.4 GHz•256 MB RAM•20 GB HDD•Windows XP,Windows Vista,Windows 7.0,Linux•Browsers:Internet Explorer 5.0 and above,Mozilla FireFox,Google Chrome

Page 6: AIRLINE_RESERVATION_GRP08

List of Use Cases:

•Search a Flight•Book a Flight•Cancel a Flight•Inventory Management•Fare Management

Page 7: AIRLINE_RESERVATION_GRP08

Use Case Diagram:

Page 8: AIRLINE_RESERVATION_GRP08

Use Case Description• Use case ID: Inventory Management• Goals in Context:Administrator wishes to

update and add new flights to the existing flights.

• Scope: Airline Reservation system.• Pre condition: Administrator has clicked on

the Inventory management link from the menu .

• Success end condition: Flight has been successfully updated or deleted and displayed.

Page 9: AIRLINE_RESERVATION_GRP08

• Failed end condition: Flight has not been updated or deleted in the flight database.

• Primary actor:Administrator

• Stake holders:Administrator,Airline staffs

• Trigger event: Selects “Inventory Management” link from the search flight results .

Page 10: AIRLINE_RESERVATION_GRP08

Main Success ScenarioStep s Actor Action Description

1 Administrator Selects Invetory Management

2 ARS Displays screen withInput fields.

3 Administrator Enter details .

4 Administrator Clicks submit.

Page 11: AIRLINE_RESERVATION_GRP08

Scenario ExtensionStep Actor Action Description

3.a Administrator Does not complete necessary fields

3.a.1 ARS Redisplay the input fields

3.b Administrator Selects cancel option

3.b.1 ARS Displays main option screen

Page 12: AIRLINE_RESERVATION_GRP08

SEARCH FLIGHT USER VISITS THIS PAGE TO SEARCH

FOR FLIGHTS AVAILABLE. USER CHOOSES THE SOURCE CITY &

DESTINATION CITY, & ALSO ENTERS THE NO. OF PASSENGERS TRAVELLING.

USER SUBMITS THE CHOICES FOR CHECKING AVAILABILITY OF FLIGHTS.

Page 13: AIRLINE_RESERVATION_GRP08

Use Case:Search Flight Goal : Customer wishes to Search for Available

Flights between 2 cities .

Scope : Airline Reservation System

Precondition : Customer has Successfully

navigated to Main Screen.

Primary Actor : Customer

Success Guarantee: A List of Flights matching

the Search Criteria is presented.

Page 14: AIRLINE_RESERVATION_GRP08

Use Case UC1 Search:Main Success Scenario

Step s Actor Action Description

1 Passenger Enters Search page

2 ARS Displays screen withInput fields forSource City, Destination City & Number of Passengers.

3 Passenger Enter details and click submit

4 ARS Generates New Page with Options matching Search Criteria

Page 15: AIRLINE_RESERVATION_GRP08

UC1 Extensions : Search

Step Actor Action Description

3.a Passenger Does not complete necessary fields

3.a.1 ARS Redisplay the input fields

Page 16: AIRLINE_RESERVATION_GRP08

CANCEL RESERVATION EVERY USER IN THE SYSTEM HAS A

UNIQUE PASSENGER-ID PROVIDED TO THEM.

IN CANCELLATION PAGE, THE USER MENTIONS THIS PASSENGER-ID ALONG WITH THE FLIGHT-ID MENTIONED IN THE GENERATED TICKET.

ON PROVIDING CORRECT DETAILS, THE TICKET IS CANCELLED & THE SAME IS REFLECTED IN THE DATABASE.

Page 17: AIRLINE_RESERVATION_GRP08

Use Case : Cancel Ticket

Step s Actor Action Description

1 Passenger Enters Cancel page

2 ARS Displays screen withInput fields forPassenger Id & Flight Id.

3 Passenger Enter details and click submit

4 ARS Generates New Page with Message Cancellation Successful.

Page 18: AIRLINE_RESERVATION_GRP08

Main Success Scenario

Passenger navigates to the Main Menu Customer selects Cancel Reservation. Customer enters the Passenger Id & the

Flight Id. System checks & validates the data. System displays the “Reservation

Cancellation Successful” Message on the Screen.

Page 19: AIRLINE_RESERVATION_GRP08

Extensions

Step Actor Action Description

3.a Passenger Does not complete necessary fields

3.a.1 ARS Redisplay the input fields

3 b. Passenger Enters Incorrect Details

3 b 1. ARS Displays Unsuccessful Cancellation page

Page 20: AIRLINE_RESERVATION_GRP08

Use Case :Book Ticket• Use case ID: Book Ticket• Goal in Context:A passenger wishes to make

reservation• Scope: Airline Reservation system• Pre condition: Actor has Successfully

generated a list of flights as documented in “search for flights” Use case.

• Success end condition: Reservation has been made and travel ticket has been generated

Page 21: AIRLINE_RESERVATION_GRP08

• Failed end condition: a reservation has not been made.

• Primary actor:Passenger

• Stake holders:Passenger,Airline staffs

• Trigger event: Selects “Book Flight” link from the search flight results .

Page 22: AIRLINE_RESERVATION_GRP08

Main Success ScenarioStep s Actor Action Description

1 Passenger Selects Book Ticket

2 ARS Displays screen withInput fields.

3 Passenger Enter details and click submit

4 Passenger Clicks generate ticket

Page 23: AIRLINE_RESERVATION_GRP08

Scenario Extension

Step Actor Action Description

3.a Passenger Does not complete necessary fields

3.a.1 ARS Redisplay the input fields

3.b Passenger Selects cancel option

3.b.1 ARS Displays main option screen

Page 24: AIRLINE_RESERVATION_GRP08

Use Case Description

• Use case ID: Fare Management• Goal in Context: Administrator wishes to

update and change fare of the existing flights.• Scope: Airline Reservation system.• Pre condition: Administrator has clicked on

the fare management link from the menu .• Success end condition: Fare has been

successfully updated and displayed.

Page 25: AIRLINE_RESERVATION_GRP08

• Failed end condition: Fare has not been updated fro the particular flight.

• Primary actor:Administrator

• Stake holders:Administrator,Airline staffs

• Trigger event: Selects “Fare Management” link from the search flight results .

Page 26: AIRLINE_RESERVATION_GRP08

Main Success ScenarioStep s Actor Action Description

1 Administrator Selects FareManagement

2 ARS Displays screen withInput fields.

3 Administrator Enter details .

4 Administrator Clicks submit.

Page 27: AIRLINE_RESERVATION_GRP08

Scenario ExtensionStep Actor Action Description

3.a Administrator Does not complete necessary fields

3.a.1 ARS Redisplay the input fields

3.b Administrator Selects cancel option

3.b.1 ARS Displays main option screen

Page 28: AIRLINE_RESERVATION_GRP08

Domain Level Class Diagram:

Page 29: AIRLINE_RESERVATION_GRP08

System Initialization Sequence Diagram:

Page 30: AIRLINE_RESERVATION_GRP08

Design Level Class Diagram:

Page 31: AIRLINE_RESERVATION_GRP08

Overview of MVC Architecture

MVC Architecture is the Architecture which is used in the software industry to develop

software.MVC means Model-View-ControllerThe View Component is the User Interface with

which the user interacts.Controller component is the component which interacts with Model

and calls all the modules.The Model component is the component which comprises of all the functional modules,it is the heart of

any Application which implements MVC Architecture.

Page 32: AIRLINE_RESERVATION_GRP08

Implementation of MVC in Airline Reservation System

We have implemented MVC Architecture in our project by using JSP,Servlets and POJOs.In our

system the JSP pages comprises the view component that displays the User

Interfaces.We have one Servlet which acts as the Controller it is a .java file with a doGet()

method.Our POJO file acts as the Model where all the functions have been declared

Page 33: AIRLINE_RESERVATION_GRP08

Description of Model Component

In our Airline Reservation System we have one POJO file i.e Airline.java which contains all the

functionalities like addPassenger(),addNewPassenger(),CancelTick

et() etc.This file interacts with the Controller which in turn interacts with the JSP pages

Page 34: AIRLINE_RESERVATION_GRP08

Description of View ComponentWe are using JSP Pages which acts as the user interface for the passenger and the administratorThe list of JSP Pages are:•Welcome.jsp•Menu.jsp•SearchFlight.jsp•BookTicket.jsp•InventoryManagement.jsp•FareManagement.jsp•CancelFlight.jsp etc...

Page 35: AIRLINE_RESERVATION_GRP08

Description of Controller:

We are using one Servlet file as our Controller which is AirlineServ.java.This file interacts with

the User Interface i.e the JSP pages and the Model Component i.e Airline.java file.The Servlet invokes all the components of the

Model Component after taking the necessary details from the User Interface i.e the JSP pages

Page 36: AIRLINE_RESERVATION_GRP08

Screen shots:

Page 37: AIRLINE_RESERVATION_GRP08
Page 38: AIRLINE_RESERVATION_GRP08
Page 39: AIRLINE_RESERVATION_GRP08
Page 40: AIRLINE_RESERVATION_GRP08
Page 41: AIRLINE_RESERVATION_GRP08
Page 42: AIRLINE_RESERVATION_GRP08
Page 43: AIRLINE_RESERVATION_GRP08
Page 44: AIRLINE_RESERVATION_GRP08
Page 45: AIRLINE_RESERVATION_GRP08
Page 46: AIRLINE_RESERVATION_GRP08
Page 47: AIRLINE_RESERVATION_GRP08
Page 48: AIRLINE_RESERVATION_GRP08
Page 49: AIRLINE_RESERVATION_GRP08
Page 50: AIRLINE_RESERVATION_GRP08
Page 51: AIRLINE_RESERVATION_GRP08
Page 52: AIRLINE_RESERVATION_GRP08
Page 53: AIRLINE_RESERVATION_GRP08
Page 54: AIRLINE_RESERVATION_GRP08
Page 55: AIRLINE_RESERVATION_GRP08
Page 56: AIRLINE_RESERVATION_GRP08

Future Scope of development:• The user interfaces generates alert boxes for

wrong Input in the input fields. The book ticket user interface can be made more user interactive by adding more client side validations.

• The session for the Clients are efficiently managed .so it can be deployed on the web server after adding some more security features like URL encoding.

• Postponing or preponing a flight can be added to this system

Page 57: AIRLINE_RESERVATION_GRP08

Bibliography

• Sites reffered:https://www.w3Schools.comhttps://umlweb.com

https://www.javaworld.com

Books reffered:Head first j2ee servlet by Kathy sierraHead First Java by Kathy Sierra