Upload
subhodeep1988
View
206
Download
0
Embed Size (px)
Citation preview
Case Study:Airline Reservation System
Submitted By:Prashant Kumar Singh:391385Vinitesh Garima:391368Amit Pal Singh:391390Randhir Kumar Pandey:391375
Introduction• Airline Reservation System is a automated
project with following functionalities• Customer TransactionSearch FlightBook TicketCancel ticket• Administrator TransactionFare managementInventory management
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
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
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
List of Use Cases:
•Search a Flight•Book a Flight•Cancel a Flight•Inventory Management•Fare Management
Use Case Diagram:
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.
• 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 .
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.
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
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.
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.
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
UC1 Extensions : Search
Step Actor Action Description
3.a Passenger Does not complete necessary fields
3.a.1 ARS Redisplay the input fields
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.
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.
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.
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
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
• 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 .
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
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
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.
• 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 .
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.
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
Domain Level Class Diagram:
System Initialization Sequence Diagram:
Design Level Class Diagram:
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.
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
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
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...
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
Screen shots:
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
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