AIRLINE RESERVATION SYSTEM

SRS
SOMAN AHMAD FA21-BSE-150

ABDUL AZIZ FA21-BSE-058

 PROJECT

1. Introduction ............................................................................................................................................... 3
1.1 Purpose................................................................................................................................................ 3
1.2 Document Conventions ....................................................................................................................... 3
1.3 Project Scope: ..................................................................................................................................... 3
1.4 References:.......................................................................................................................................... 4
2. Overall Description: .................................................................................................................................. 4
2.1 Product Perspective:............................................................................................................................ 4
2.2 User Classes and Characteristics: ....................................................................................................... 4
2.3 Operating Environment:...................................................................................................................... 4
2.4 Design and Implementation Constraints: ............................................................................................ 5
2.5 Assumptions and Dependencies: ........................................................................................................ 5
3. System Features: ....................................................................................................................................... 5
3.1 Description: ......................................................................................................................................... 5
3.2 Functional Requirements: ................................................................................................................... 7
3.3. Non Functional Requirements: ......................................................................................................... 7
4. DATA REQUIRNMENTS: ...................................................................................................................... 8
4.1. LOGICAL DATA MODEL: .............................................................................................................. 8
4.2. DATA DICTIONARY:...................................................................................................................... 8
4.3. Reports: .............................................................................................................................................. 9
4.4. Data Acquisition, Integrity, Retention, and Disposal ........................................................................ 9
5. External Interface Requirements ............................................................................................................... 9
5.1 User Interfaces .................................................................................................................................... 9
5.2 Software Interfaces: .......................................................................................................................... 10
5.3 Hardware Interfaces: ......................................................................................................................... 11
5.4 Communications Interfaces: ............................................................................................................. 11
6. Quality Attributes.................................................................................................................................... 12
6.1. Usability ........................................................................................................................................... 12
6.2. Performance ..................................................................................................................................... 12
4.3. Security: ........................................................................................................................................... 12
6.4. Safety: .............................................................................................................................................. 13
6.5. Sustainability: .................................................................................................................................. 13
7. Internationalization and Localization Requirements: ............................................................................. 13
7.1. Internationalization Requirements ................................................................................................... 13
 PROJECT

7.2. Localization Requirements: ............................................................................................................. 14

8. Appendix A: Glossary: ........................................................................................................................... 14
9. Appendix B: Analysis Models ................................................................................................................ 15
9.1. Use Case Diagram: .......................................................................................................................... 15
9.2. Entity Relationship Diagram:........................................................................................................... 16
9.3. Data Flow Diagram: ........................................................................................................................ 17
9.4. Sequence Diagram: ......................................................................................................................... 17
9.5. STATE TRANSITION DAIGRAM: ............................................................................................... 20
9.6. STATE TABLE: .............................................................................................................................. 20
9.7. DAILOGUE MAP: .......................................................................................................................... 21
9.8. DECISION TABLE: ........................................................................................................................ 22
9.9. DECISION TREE: ........................................................................................................................... 22
 PROJECT

1. Introduction:
The Airline Reservation System is a transformative solution designed to reshape the landscape of
air travel, offering a seamless and efficient experience for both passengers and airline operators.
With a primary focus on simplifying the flight planning, booking, and management processes, the
system aims to enhance operational efficiency, reduce costs, and elevate overall customer
satisfaction. Its objectives include streamlining the booking process, optimizing operational
efficiency through automation, improving user satisfaction through a user-friendly interface,
ensuring secure online transactions, and delivering real-time information on flight details. The
system's scope encompasses a range of features, including flight search, seat availability, booking,
payment processing, and order confirmation, catering to both domestic and international flights.
The benefits of the system include convenience, time efficiency, accuracy, cost-effectiveness, and
global accessibility. Targeting individual travelers, business professionals, and travel agencies, the
system is also tailored for airline staff, including reservation agents and administrators. Regulatory
compliance is a cornerstone, ensuring adherence to industry standards and regulations. In
summary, the Airline Reservation System is poised to revolutionize air travel by providing an
advanced, user-centric, and operationally efficient solution for the modern aviation industry.

1.1 Purpose:
The purpose of the Airline Reservation System (ARS) is to provide a user-friendly platform for
customers to efficiently book and manage flight reservations. This system aims to streamline the
reservation process, reduce manual errors, and enhance the overall experience for both customers
and airline staff.

1.2 Document Conventions:

Naming Conventions:
Utilize camel case for variable and function names (e.g., makeReservation()), and Pascal case for
class names (e.g., UserAuthentication).
Documentation Format:
All documentation will be in Markdown format for consistency and ease of readability.
Versioning:
Adopt Semantic Versioning (SemVer) for version control to communicate changes in the software.

1.3 Project Scope:

The Airline Reservation System covers the following key features:
User Authentication: Secure login for customers and airline staff.
 PROJECT

Flight Availability: Real-time information on flight schedules, seat availability, and pricing.
Reservation Management: Booking, modification, and cancellation of flight reservations.
Payment Integration: Integration with secure payment gateways for online transactions.
Administrative Tools: Tools for administrators to monitor system activities, manage
configurations, and resolve issues.

1.4 References:
In addition to internal documentation, the system design will adhere to:
International Air Transport Association (IATA) standards for airline industry practices.
Relevant airline industry regulations and guidelines.
A link to the project repository for access to the latest code and documentation.

2. Overall Description:
2.1 Product Perspective:
The Airline Reservation System operates as a standalone system interacting with external entities:
Payment Gateways: For secure and seamless online transactions.
Passenger Databases: To retrieve and update passenger information securely.
Flight Availability APIs: Interfaces with external APIs to provide real-time flight schedules and
availability.
The system ensures data integrity and consistency by interfacing with existing airline
infrastructure.

2.2 User Classes and Characteristics:

Administrator:
Responsibilities: System configuration, monitoring user activities, issue resolution.
Characteristics: High-level access permissions, technical proficiency.
Customer:
Responsibilities: Initiates and manages flight reservations, checks availability, makes
payments.
Characteristics: Varied technical proficiency, focus on user experience.
Airline Staff:
Responsibilities: Handles ticket confirmations, cancellations, manages flight schedules.
Characteristics: System expertise, focus on operational efficiency.

2.3 Operating Environment:

The Airline Reservation System will be hosted on a secure server:
 PROJECT

Access Control: User access controlled by robust authentication mechanisms.

User Interface: Compatible with major web browsers for customer use.
Airline Staff Interface: User-friendly interface for airline staff for efficient reservation
management.

2.4 Design and Implementation Constraints:

Compatibility: The system must adhere to existing reservation systems and industry standards.
Security: Robust encryption and authentication mechanisms to protect user data.
Scalability: Design for scalability to handle a growing number of concurrent users.

2.5 Assumptions and Dependencies:

Assumption: Users have internet access and use standard web browsers.
Dependency: The system relies on external APIs for real-time flight availability and pricing
information.

3. System Features:
3.1 Description:
The Airline Reservation System (ARS) is a comprehensive software solution designed to facilitate
and streamline the process of airline ticket booking and management. This system serves as a
central platform for both customers and airline staff to interact and perform various tasks related
to flight reservations.
User Authentication:
Secure login for customers, airline staff, and administrators.
User account management for password recovery and account details.
Flight Search and Booking:
Real-time access to flight schedules, availability, and pricing.
User-friendly search functionality based on criteria like date, time, and destination.
Booking process with seat selection and fare options.
Reservation Management:
View, modify, and cancel reservations.
Automatic reservation confirmation and e-ticket generation.
Payment Integration:
Seamless integration with secure payment gateways.
Support for multiple payment methods (credit cards, online banking, etc.).
 PROJECT

Seat Selection:
Interactive seat maps for users to choose preferred seats.
Information on available amenities for different seat classes.
Flight Information:
Detailed information about each flight, including duration, layovers, and aircraft type.
Integration with external APIs for real-time updates on flight status.
User Profiles:
Personalized user profiles with travel history and preferences.
Loyalty program integration for frequent flyers.
Administrative Tools:
Dashboard for administrators to manage system configurations.
Monitoring tools to track user activities and system performance.
Issue resolution and customer support functionalities.
Reporting and Analytics:
Generation of reports on reservation statistics, revenue, and other key metrics.
Analytics tools for data-driven decision-making.
Notifications:
Automated notifications for booking confirmations, flight changes, and cancellations.
Alerts for users regarding special promotions or offers.
Multi-language Support:
Support for multiple languages to cater to a diverse user base.
Accessibility:
Accessibility features to ensure the system is usable by individuals with disabilities.
Security Measures:
Secure transmission of sensitive data using encryption.
Robust authentication and authorization mechanisms.
Mobile Responsiveness:
Mobile-friendly interfaces for users on smartphones and tablets.
Integration with External Systems:
Integration with airline databases, third-party reservation systems, and regulatory systems.
 PROJECT

Feedback and Reviews:

Customer feedback and review features to enhance user engagement and improve services.
Dynamic Pricing:
Implementation of dynamic pricing models based on demand, seasonality, and other
factors.
Check-in and Boarding Pass:
Online check-in functionality.
Digital boarding pass generation.

3.2 Functional Requirements:

Search and display available flights: The system should be able to search and display a list
of available flights based on the user's input criteria, such as departure and arrival cities,
dates, and number of passengers.
Book and purchase tickets: The system should allow users to book and purchase tickets for
their desired flights.
Cancel and change reservations: The system should allow users to cancel or change their
existing reservations, as long as it is within the cancellation or change policy of the airline.
Seat selection: The system should allow users to select their preferred seats at the time of
booking or at a later time.
Check-in: The system should allow users to check-in for their flights online, either through
the website or mobile app, and generate their boarding pass.

3.3. Non Functional Requirements:

• Security: The system should ensure the security of personal and payment information
entered by the users.
• Scalability: The system should be able to handle a large number of users and transactions
without experiencing delays or downtime.
• User experience: The system should be easy to use and navigate for the users.
• Performance: The system should be able to perform fast searches and booking transactions.
• Integration: The system should be able to integrate with other systems, such as the
airline's ticketing system, inventory system, and loyalty program.
 PROJECT

4. DATA REQUIRNMENTS:
4.1. LOGICAL DATA MODEL:

4.2. DATA DICTIONARY:

Entity Attributes

User User_ID (PrimaryKey), Username, Password, First_Name, Last_Name,

Email,
Phone_Number.

Flight Flight_ID (Primary Key) Airline_Code, Departure_City, Arrival_City,

Departure_Date, Departure_Time, Arrival_Date, Arrival_Time,
Available_Seats, Ticket_Price.

Reservation Reservation_ID (Primary Key), User_ID (Foreign Key to User),

Flight_ID (Foreign Key to Flight), Reservation_Date,
Status(Confirmed,Pending,Canceled), Total_Price.
 PROJECT

Attributes Description Type

User_ID (Primary Key): A unique identifier assigned Integer
to each user.

Username: The unique name chosen by String

the user for authentication.

Password: The password chosen by the String

user for authentication.

First_Name: The first name of the user. String

Last_Name: The last name of the user. String

Email: The email address of the user. String

Phone_Number: The phone number of the String

user.

4.3. Reports:
Purpose:
The Reports section outlines the types of reports generated by the Airline Reservation System for
monitoring and analysis.
Sample Reports:
Reservation Confirmation Reports:
• Generated when a user successfully completes a reservation.
• Includes details such as User ID, Flight ID, and Confirmation Timestamp.
Flight Availability Reports:
• Provides an overview of available flights based on specified criteria (date, destination).
• Assists in managing seat availability and pricing strategies.

4.4. Data Acquisition, Integrity, Retention, and Disposal

Purpose:
This section outlines the processes and policies related to data management within the Airline
Reservation System.
Components:
 PROJECT

Data Acquisition:
• Flight availability data is acquired in real-time through external APIs.
• User information is collected during the registration and reservation processes.
Data Integrity:
• Implement data validation checks to ensure accuracy and consistency.
• Use referential integrity constraints to maintain relationships between tables.
Data Retention:
• User and reservation data is retained for a specified period, supporting historical
reporting and analysis.
Data Disposal:
• Outdated or unnecessary data is securely disposed of in accordance with data protection
regulations.
• Deletion of canceled reservations and associated data.

5. External Interface Requirements

5.1 User Interfaces
Purpose:
The user interfaces of the Airline Reservation System are designed to provide a seamless and
intuitive experience for users during the booking and management of their flights.
Requirements:
User-Friendly Interface:
• The system should feature a user-friendly interface suitable for users of varying technical
expertise.
• The design should be intuitive and easy to navigate.
Visual Appeal:
• The interface should be visually appealing, using appropriate colors and fonts for the
target audience.
• Design elements should contribute to a positive user experience.
Responsiveness:
• The system should be responsive, ensuring a consistent experience across devices such as
smartphones, tablets, and computers.
Clear Instructions:
• Clear and concise instructions should be provided to guide users through the booking
process and system functionalities.
Feedback Mechanism:
• The system should provide feedback to users, confirming that their actions (e.g.,
reservation, payment) have been successfully processed.
Search Functionality:
 PROJECT

• Users should be able to search for flights based on criteria such as name, date, time, and
destination.
Cart Management:
• Users should be able to add flights to their cart and view the contents of their cart before
confirming the reservation.
Checkout and Payment:
• The system should facilitate a smooth checkout process, allowing users to securely pay for
their reservations.
Order Tracking:
• Users should have access to order tracking information, enabling them to monitor the
status of their reservations.

5.2 Software Interfaces:

Purpose:
The software interfaces of the Airline Reservation System involve interactions with databases,
payment processing systems, and external services.
Requirements:
Database Connection:
• The system should connect to a database containing flight and reservation information.
Secure Payment Processing:
• The system should securely process payments through integration with a reliable
payment gateway.
Order Fulfillment:
• Order information should be sent to a shipping or ticketing system for fulfillment.
Order Status Updates:
• The system should be capable of tracking order status and providing timely updates to
users.

5.3 Hardware Interfaces:

Purpose:
The hardware interfaces define the compatibility of the Airline Reservation System with various
hardware devices.
Requirements:
Device Compatibility:
The system should work seamlessly with various hardware devices such as barcode scanners and
payment terminals.
Printer Integration:
 PROJECT

The system should be able to connect to printers for printing tickets, receipts, and other relevant
documents.

5.4 Communications Interfaces:

Purpose:
Communications interfaces involve the exchange of information between the Airline Reservation
System and users.
Requirements:
Push Notifications:
The system should be capable of sending and receiving push notifications to keep users informed
about important updates.
Email Communication:
The system should send emails to users for order confirmations, itinerary details, and other
relevant information.
Analytics and Tracking:
The system should track user interactions and provide analytics data for performance evaluation
and system improvements.

6. Quality Attributes
6.1. Usability
Ease of Use:
The system will feature an intuitive and easy-to-use interface for both novice and experienced
users.
Search Functionality:
A powerful search function will enable users to quickly find and book flights based on various
criteria such as date, time, and destination.
Filtering:
Users will have the ability to filter search results by factors such as price, flight duration, and
class.
Information:
The system will provide detailed information about each flight, including duration, layovers, and
available amenities.
 PROJECT

6.2. Performance
Speed:
The system will be designed to operate with speed and responsiveness, ensuring a seamless user
experience during the booking process.
Reliability:
The system will be reliable, with minimal chances of crashes or freezes, ensuring continuous
availability.
Scalability:
The system will be scalable to accommodate a growing user base and increasing demands on the
platform.
Availability:
The system will be available 24/7 to cater to users across different time zones.

4.3. Security:
Data Protection:
The system will implement robust data protection measures to prevent unauthorized access to
user information.
Payment Security:
Secure payment processing methods will be employed to ensure the safety of users' financial
transactions.
Order Tracking:
Users will have a secure means to track the status of their flight reservations.
6.4. Safety:
Flight Safety:
The system will prioritize the safety of passengers, providing accurate and up-to-date
information about flight safety measures.
Allergen Information:
For in-flight services, the system will provide allergen information for passengers with dietary
restrictions.
Storage Instructions:
The system will offer guidance on storing electronic tickets and boarding passes for a seamless
travel experience.
 PROJECT

6.5. Sustainability:
Eco-friendly Practices:
The system will promote sustainability by providing information about airlines that follow eco-
friendly practices, such as fuel-efficient aircraft and carbon offset programs.
Community Engagement:
The system will offer a platform for users to connect, share travel experiences, and contribute to
a community that values sustainable travel.
Education:
The system will provide educational resources about travel sustainability, including tips on
reducing environmental impact during flights.

7. Internationalization and Localization Requirements:

7.1. Internationalization Requirements
Support for Multiple Languages:
The system will support multiple languages, including but not limited to English, Spanish,
French, German, Chinese, Japanese, Korean, and Arabic.
Support for Different Currencies:
The system will support various currencies, including but not limited to USD, EUR, GBP, JPY,
CNY, KRW, and AED.

7.2. Localization Requirements:

Translation of All Text:
The system's text will be translated into various languages, ensuring a localized experience for
users.
Adaptation of Images and Icons:
Images and icons will be adapted to align with cultural norms and preferences, while maintaining
the functionality of the system features.
Localized Pricing and Currency:
Pricing will be localized, displayed in the local currency (e.g., PKR) and USD for international
users.
Localized Date and Time Formats:
Date and time formats will be adapted to match the local conventions, providing a familiar
experience for users.
Localized Units of Measurement:
 PROJECT

Units of measurement, such as weight and distance, will be localized (e.g., Kilograms, Dozens)
based on the preferences of the region.

8. Appendix A: Glossary:
Internationalization: The process of designing software to be usable by a global audience.

Localization: The process of adapting software to a specific region or language.

Culturalization: The process of adapting software to the cultural norms of a specific region.

Procurement: The process of acquiring goods or services.

 PROJECT

9. Appendix B: Analysis Models

9.1. Use Case Diagram:
 PROJECT

9.2. Entity Relationship Diagram:

 PROJECT

9.3. Data Flow Diagram:

LEVEL 0

9.4. Sequence Diagram:

(Login)
 PROJECT

(Registration)

(Flight Details)
 PROJECT

(Reservation)

(Payment)
 PROJECT

9.5. STATE TRANSITION DAIGRAM:

USECASE: BOOKING

9.6. STATE TABLE:

 PROJECT

9.7. DAILOGUE MAP:

 PROJECT

9.8. DECISION TABLE:

9.9. DECISION TREE: