AirLine
Content
AIRLINE e-ticket RESERVATION
1. Introduction 1.1 Purpose: Airline e-ticket Reservation Provides enhanced services for customers to reserve ticket. The main objective of our project is to create an Airline Reservation system where a Counter Assistant can request all flight information as per the need of the customer’s Journey date. Our Project intends to check all the available flight services from the database and provide the information that are much useful for the Passenger. They can get information regarding Departure Time, Journey Hours, Date, Cost etc. When the Customer contacts the Counter Assistant, He will collect all the necessary information and reserves the ticket for the Customer. Certain payment modes also available. This site uses database to store all customer information and to retrieve flight details which makes the Airline services to provide better Service. 1.2 Scope: We describe what features are in the scope of the software and what are not in the scope of the software to be developed. In Scope:
a) Booking flights through the Internet means that you have greater access to flight schedules.
b) Online booking allows you to see the exact costs of each leg of a flight and the costs of various options associated with a particular flight.
c) airline reservations online is the ability to check in up to 24 hours before your flight, select your seat and print your boarding passes from home.
d) Booking online can often save you money.
Out of Scope: 1.3 Definitions, Acronyms, and Abbreviations:
a) SRS
:
Software Requirements Specification.
b) WWW c) GUI d) RIA
: : :
World Wide Web. Graphical User Interface. Rich Internet Application
Definitions:
a) Reservation: This event is used to reserve tickets for the Customers. This will provide numerous information regarding the Fleet schedule Details, Cost etc. b) Cancellation: This event is used to cancel the reserved ticket. Cancellation can be made using booking Id, flight no and Journey date. c) Reports : This is used to provide collective information regarding Passenger’s Contact Details, Income Details in Particular flight, Passport No., Availability of Flight Services, No. of Tickets Reserved in Particular flight.
1.4 Software Specifications: OS Front end Platform Framework Language Back End Other Essentials : : : : : : : Windows 7 Silverlight 4 with SDK Visual Studio 2010 .net 4.0 C#.net 4.0 Microsoft SQL Server 2008 Mozilla Firefox or Internet Explorer Internet Information Services 7.0 Microsoft Web Platform Installer.
1.5 Overview: The rest of this SRS is organized as follows: Section 2 gives an overall description of the software. It gives what level of proficiency is expected of the user, some general constraints while making the software and some assumptions and dependencies that are assumed. Section 3 gives specific requirements which the software is expected to deliver. Functional requirements are given by various use cases. Some performance requirements and design constraints are also given. Section 4 gives some possible future extensions of the system. Finally the appendices in Section 5 user screen. 2. Overall Description: 2.1 Product Perspective: Airline Reservations Systems contain airline schedules, fare tariffs, passenger reservations and ticket records.An airline’s inventory contains all flights with their available seats. The inventory of an airline is generally divided into service classes (e.g. First, Business or Economy class), for which different prices and booking conditions apply. Inventory control
steers how many seats are available in the different booking classes, by opening and closing individual booking classes for sale. In combination with the fares and booking conditions stored in the Fare Quote System the price for each sold seat is determined. 2.2 Product Functions: AirLine e-Ticket Reservation should support the following use cases: Class of use cases Use cases Description of use cases Use case related to web Deployment This will deploy our project as website. Use cases related to Login Login authorization using user Id and Password Use cases related to Search Flights Used to Search Flights Provide information regarding seat availability Journey duration, Cost etc. Use cases related to Passenger Information Used to Collect passenger information who is reserving tickets. Also collects information of other Passengers who are travelling along with him. Provides Booking ID for each Passengers Booking. Use cases related to Seat Reservation Provides facilities to select date and Flight No. Provides Flight Destination Details. Provides Seat Layout which is used to select seats. Use cases related to Payment Mode Provides Cash and Credit/Debit payment Facilities. Use cases related to e-ticket Used to provide all the necessary information for printing e-ticket Use cases related to Ticket Cancellation Used to Cancel tickets using Booking ID that are provided while booking tickets. Use cases related to Reports Used to provide reports such as contact details, Income Details of Passenger, Passport numbers, Flight Services etc.
2.3 User Characteristics: a) The user should be familiar with the Flight oriented Details and Payment mode specifications. b) The user should know the details of an Online Ticket Reservations.
2.4 Principal Actors: The two principal actors in AirLine e-Ticket Reservation are “Counter Assistant” and “System”.
2.5 General Constraints: a) For full working Airline e-ticket Reservation requires Internet connection. b) It is single-user software. 3 Specific Requirements: 3.1 Functional Requirements: We describe the functional requirements by giving various use cases.
Use case related to web Deployment:
Use Case 1: Installation Primary Actor: Counter Assistant Pre Condition: Internet connection available. Main Scenario : 1. User initiates web deployment files. 2. User is also asked for the initial login and password. 3. User specifies the home directory and login/password. 4. System creates the working files in the specified home directory. Working files contain: a. Web Config files. b. DataBase Structure. c. Images used in the Project. Alternate Scenario: 1. Network failure. 2. Installation aborted.
Use case related to Login:
Use Case 2: Login Primary Actor: Counter Assistant Pre Condition: Nil Main Scenario : 1. Start the application. User prompted for login and password. 2. User gives the login and password. 3. System does authentication. 4. Main screen is displayed. Alternate Scenario :
1(a). Authorization fails (a). Prompt the user that he typed the wrong password (b). Allow him to re-enter the password. Give him 3 chances.
Use case related to Search Flights:
Use Case 3: Search Flight Primary Actor: Counter Assistant Pre Condition: User logged in. Main Scenario: 1. System asks the Journey Date. 2. It also requires Flight no. 3. All the Details regarding flights are displayed which is retrieved from Database. Alternate Scenario: If Flight Services are not available means it will display it will display an information in the screen itself.
Use case related to Passenger Information:
Use Case 4: Passenger Information Primary Actor: Counter Assistant Pre Condition: User logged in. Main Scenario: 1. System asks the Passenger Information who is going to Book tickets 2. It Provides booking id for the Passenger which will used as reference. 3. Other Passenger Details are also collected. Alternate Scenario: If the Information is not provided means it is not possible to precede the next step.
Use case related to Seat Reservation:
Use Case 5: Seat Reservation Primary Actor: Counter Assistant Pre Condition: User logged in. Main Scenario: 1. System Requires information such Journey Date and Flight Service nos. 2. System Provides layout of the seats available in the flight 3. Allow Counter Assistant to select/deselect seats. Alternate Scenario:
Nil
Use case related to Payment Mode:
Use Case 6: Payment Mode Primary Actor: Counter Assistant Pre Condition: Seats Should be reserved. Main Scenario: 1. Provides the Fare Details. 2. System Requires information Cash or credit/debit card details. 3. Collects the details information regarding Payment collection.
Alternate Scenario: Nil
Use case related to e-ticket:
Use Case 6: e-Ticket Primary Actor: Counter Assistant Pre Condition: Payments should be completed successfully. Main Scenario: Provides e-ticket for printing with all the necessary information that require for Passenger Alternate Scenario: Nil
Use case related to Cancellation:
Use Case 7: Ticket Cancellation Primary Actor: Counter Assistant Pre Condition: Nil. Main Scenario: 1. Requires Date and Flight No. 2. Booking ID is necessary Alternate Scenario: If Booking ID is not available means it is not possible to cancel tickets.
Use case related to Reports:
Use Case 7: Reports Primary Actor: Counter Assistant Pre Condition: Logged in. Main Scenario: 1. Requires Date and Flight No. 2. Provides reports regarding Flight Reservation details, Total Income Details, Contact information in case of Emergency. Alternate Scenario: Nil.
3.2 Performance Requirements: (a) Should run on 3.0 GHz Processor, 1 GB RAM machine. (b) 90% of the responses should be within 5 sec. 3.3 Design Constraints: 1. Fault Tolerance: Data should not become corrupted in case of system crash or power failure. 3.4 External Interface Requirements: The user screen is Split into several categories based on the nodules. Appendix B shows the intended user screen. 4. Future Extensions:
1. AirLine e-Ticket Reservation is developed for Stand Alone systems. In the future its capability is extended to cloud computing using sql azure. 2. Moreover Flight routes are provided in GUI interface using Bing Maps.
Appendix: Screens
1. Introduction 1.1 Purpose: Airline e-ticket Reservation Provides enhanced services for customers to reserve ticket. The main objective of our project is to create an Airline Reservation system where a Counter Assistant can request all flight information as per the need of the customer’s Journey date. Our Project intends to check all the available flight services from the database and provide the information that are much useful for the Passenger. They can get information regarding Departure Time, Journey Hours, Date, Cost etc. When the Customer contacts the Counter Assistant, He will collect all the necessary information and reserves the ticket for the Customer. Certain payment modes also available. This site uses database to store all customer information and to retrieve flight details which makes the Airline services to provide better Service. 1.2 Scope: We describe what features are in the scope of the software and what are not in the scope of the software to be developed. In Scope:
a) Booking flights through the Internet means that you have greater access to flight schedules.
b) Online booking allows you to see the exact costs of each leg of a flight and the costs of various options associated with a particular flight.
c) airline reservations online is the ability to check in up to 24 hours before your flight, select your seat and print your boarding passes from home.
d) Booking online can often save you money.
Out of Scope: 1.3 Definitions, Acronyms, and Abbreviations:
a) SRS
:
Software Requirements Specification.
b) WWW c) GUI d) RIA
: : :
World Wide Web. Graphical User Interface. Rich Internet Application
Definitions:
a) Reservation: This event is used to reserve tickets for the Customers. This will provide numerous information regarding the Fleet schedule Details, Cost etc. b) Cancellation: This event is used to cancel the reserved ticket. Cancellation can be made using booking Id, flight no and Journey date. c) Reports : This is used to provide collective information regarding Passenger’s Contact Details, Income Details in Particular flight, Passport No., Availability of Flight Services, No. of Tickets Reserved in Particular flight.
1.4 Software Specifications: OS Front end Platform Framework Language Back End Other Essentials : : : : : : : Windows 7 Silverlight 4 with SDK Visual Studio 2010 .net 4.0 C#.net 4.0 Microsoft SQL Server 2008 Mozilla Firefox or Internet Explorer Internet Information Services 7.0 Microsoft Web Platform Installer.
1.5 Overview: The rest of this SRS is organized as follows: Section 2 gives an overall description of the software. It gives what level of proficiency is expected of the user, some general constraints while making the software and some assumptions and dependencies that are assumed. Section 3 gives specific requirements which the software is expected to deliver. Functional requirements are given by various use cases. Some performance requirements and design constraints are also given. Section 4 gives some possible future extensions of the system. Finally the appendices in Section 5 user screen. 2. Overall Description: 2.1 Product Perspective: Airline Reservations Systems contain airline schedules, fare tariffs, passenger reservations and ticket records.An airline’s inventory contains all flights with their available seats. The inventory of an airline is generally divided into service classes (e.g. First, Business or Economy class), for which different prices and booking conditions apply. Inventory control
steers how many seats are available in the different booking classes, by opening and closing individual booking classes for sale. In combination with the fares and booking conditions stored in the Fare Quote System the price for each sold seat is determined. 2.2 Product Functions: AirLine e-Ticket Reservation should support the following use cases: Class of use cases Use cases Description of use cases Use case related to web Deployment This will deploy our project as website. Use cases related to Login Login authorization using user Id and Password Use cases related to Search Flights Used to Search Flights Provide information regarding seat availability Journey duration, Cost etc. Use cases related to Passenger Information Used to Collect passenger information who is reserving tickets. Also collects information of other Passengers who are travelling along with him. Provides Booking ID for each Passengers Booking. Use cases related to Seat Reservation Provides facilities to select date and Flight No. Provides Flight Destination Details. Provides Seat Layout which is used to select seats. Use cases related to Payment Mode Provides Cash and Credit/Debit payment Facilities. Use cases related to e-ticket Used to provide all the necessary information for printing e-ticket Use cases related to Ticket Cancellation Used to Cancel tickets using Booking ID that are provided while booking tickets. Use cases related to Reports Used to provide reports such as contact details, Income Details of Passenger, Passport numbers, Flight Services etc.
2.3 User Characteristics: a) The user should be familiar with the Flight oriented Details and Payment mode specifications. b) The user should know the details of an Online Ticket Reservations.
2.4 Principal Actors: The two principal actors in AirLine e-Ticket Reservation are “Counter Assistant” and “System”.
2.5 General Constraints: a) For full working Airline e-ticket Reservation requires Internet connection. b) It is single-user software. 3 Specific Requirements: 3.1 Functional Requirements: We describe the functional requirements by giving various use cases.
Use case related to web Deployment:
Use Case 1: Installation Primary Actor: Counter Assistant Pre Condition: Internet connection available. Main Scenario : 1. User initiates web deployment files. 2. User is also asked for the initial login and password. 3. User specifies the home directory and login/password. 4. System creates the working files in the specified home directory. Working files contain: a. Web Config files. b. DataBase Structure. c. Images used in the Project. Alternate Scenario: 1. Network failure. 2. Installation aborted.
Use case related to Login:
Use Case 2: Login Primary Actor: Counter Assistant Pre Condition: Nil Main Scenario : 1. Start the application. User prompted for login and password. 2. User gives the login and password. 3. System does authentication. 4. Main screen is displayed. Alternate Scenario :
1(a). Authorization fails (a). Prompt the user that he typed the wrong password (b). Allow him to re-enter the password. Give him 3 chances.
Use case related to Search Flights:
Use Case 3: Search Flight Primary Actor: Counter Assistant Pre Condition: User logged in. Main Scenario: 1. System asks the Journey Date. 2. It also requires Flight no. 3. All the Details regarding flights are displayed which is retrieved from Database. Alternate Scenario: If Flight Services are not available means it will display it will display an information in the screen itself.
Use case related to Passenger Information:
Use Case 4: Passenger Information Primary Actor: Counter Assistant Pre Condition: User logged in. Main Scenario: 1. System asks the Passenger Information who is going to Book tickets 2. It Provides booking id for the Passenger which will used as reference. 3. Other Passenger Details are also collected. Alternate Scenario: If the Information is not provided means it is not possible to precede the next step.
Use case related to Seat Reservation:
Use Case 5: Seat Reservation Primary Actor: Counter Assistant Pre Condition: User logged in. Main Scenario: 1. System Requires information such Journey Date and Flight Service nos. 2. System Provides layout of the seats available in the flight 3. Allow Counter Assistant to select/deselect seats. Alternate Scenario:
Nil
Use case related to Payment Mode:
Use Case 6: Payment Mode Primary Actor: Counter Assistant Pre Condition: Seats Should be reserved. Main Scenario: 1. Provides the Fare Details. 2. System Requires information Cash or credit/debit card details. 3. Collects the details information regarding Payment collection.
Alternate Scenario: Nil
Use case related to e-ticket:
Use Case 6: e-Ticket Primary Actor: Counter Assistant Pre Condition: Payments should be completed successfully. Main Scenario: Provides e-ticket for printing with all the necessary information that require for Passenger Alternate Scenario: Nil
Use case related to Cancellation:
Use Case 7: Ticket Cancellation Primary Actor: Counter Assistant Pre Condition: Nil. Main Scenario: 1. Requires Date and Flight No. 2. Booking ID is necessary Alternate Scenario: If Booking ID is not available means it is not possible to cancel tickets.
Use case related to Reports:
Use Case 7: Reports Primary Actor: Counter Assistant Pre Condition: Logged in. Main Scenario: 1. Requires Date and Flight No. 2. Provides reports regarding Flight Reservation details, Total Income Details, Contact information in case of Emergency. Alternate Scenario: Nil.
3.2 Performance Requirements: (a) Should run on 3.0 GHz Processor, 1 GB RAM machine. (b) 90% of the responses should be within 5 sec. 3.3 Design Constraints: 1. Fault Tolerance: Data should not become corrupted in case of system crash or power failure. 3.4 External Interface Requirements: The user screen is Split into several categories based on the nodules. Appendix B shows the intended user screen. 4. Future Extensions:
1. AirLine e-Ticket Reservation is developed for Stand Alone systems. In the future its capability is extended to cloud computing using sql azure. 2. Moreover Flight routes are provided in GUI interface using Bing Maps.
Appendix: Screens
