Airline Reservation Booking System: System Architecture and Design

This project presents the system architecture of an airline reservation booking system. The system is designed using a three-tier architecture (presentation, business, and data access tiers). The project includes various UML diagrams such as class, activity, sequence, and use case diagrams to illustrate the system's functionality and behavior. The design emphasizes robustness, fault tolerance, scalability, and security. The application is designed to handle hardware failures and ensure data integrity. Furthermore, the system's design addresses recovery time, scalability to support numerous online users, and security measures including encryption to protect sensitive data. The project also includes a detailed bibliography of the sources that have been used.

Running head: SYSTEM ARCHITECTURE
System Architecture
Name of Student-
Name of University-
Author’s Note-

1SYSTEM ARCHITECTURE
Title: Airline Reservation Booking System
Description of the application
The airline reservation booking system that is being proposed in this project helps all its
customer to search the seat availability and the prices of different airline tickets along with the
packages and offers that are available for a particular reservation. The application that is
proposed in this system includes different features like having online registration for the users,
modifying all the details of the website from the management user or administrator, by adding
various users in the system, by deleting the details of the customer or by modifying them. The
fight packages and the flight information are also modified by the administrator. All the other
features similar to other online airline booking system is also included in this system.
Tiers of the System
The main architecture of the Airline Reservation System that is proposed is based on
three-tier architecture that is presentation tier, business tier, and the data access tier.
The presentation tier mainly converts the information and displays the information in
some human legible form. All the information that are shown in this tier includes services such a
searching of flights in the website, purchasing the tickets, membership of the website by sign up,
and many other such details. This layer communicates with other layers by generating the results
to the users tier and the other tiers in the system.
In the second layer that is the business tier layer, the information is exchange from one
interface to another. In this layer, information is exchanged between the user and the data base
associated with the project.

2SYSTEM ARCHITECTURE
The last layer in the system of three layer architecture is the data access tier. This layer
mainly consist of the database servers. All the information that are related to the reservation
system are stored in this system and are retrieved from this particular layer of data access.
Overall structure of Implementation
The application structure of the airline ticket booking system will have two audiences;
end user activities and administrative activities. The customer end have many functionalities
such as registering with the system, log in with the system, book the flights, and book some
packages and many more activities.
Class Diagram
Figure 1: Class Diagram of Airline Booking System
(Source: Created by Author)

3SYSTEM ARCHITECTURE
Activity Diagram
Figure 2: Activity Diagram of Airline Booking System
(Source: Created by Author)

4SYSTEM ARCHITECTURE
Sequence Diagram
Figure 3: Sequence Diagram of Airline Booking System
(Source: Created by Author)

5SYSTEM ARCHITECTURE
Use Case Diagram
Figure 4: Use Case Diagram of Airline Booking System
(Source: Created by Author)

6SYSTEM ARCHITECTURE
User Interface Design
Figure 5: User Interface of Airline Booking System
(Source: Created by Author)
Robustness of the application design
The airline reservation system that is being built up has the ability to restart even when
there is a hardware failure. The system that is being designed is a stable application system and
does not entertain crashing intermittently (Olmsted, 2016). The application has other robustness
property too, that is the application has the capability of have successful start when there is
hardware failure. The data of the application can be saved regularly in case of any failure.
Fault Tolerance of the application design

7SYSTEM ARCHITECTURE
Fault tolerance is basically a property of an application software that helps the system to
continue its work even if there is a failure in some parts of the system.
The application that is being built has fault tolerance property because it has less
probability of failure and has increased reliability (MaIm et al., 2018). There is less failure
chance of the system that is being designed. The system design of the airline booking system has
less complexity design which increases the ability of fault tolerance in the system.
Recovery Time
Recovery of application is an automated continuation of the application after failover.
The application recovery needs careful design to recover its failover (Corda, Brule & Smith,
2015). The airline reservation system that is being designed includes short recovery time in case
of failure. The system has the ability to resubmit the work processing in case of system failure. It
has the capability of detecting the failover in case of any problem in the system.
Scalable
For an application system, it must have the ability to attend numerous number of people
accessing the application online. Scalability refers to support more number of users at a
particular time. As the system of the airline booking application will be done online, the
application should be scalable and have the ability to process number of users at all the time
(Kchaou, Bouassida & Ben-Abdallah, 2017). Scalability also requires adding more number of
hardware with the system and the design of this particular application has the ability to support
more load within the system.
Security of the application design

8SYSTEM ARCHITECTURE
Security of an application is considered as a process of making applications secured by
includes and enhancing more number of security applications in the system (Chen et al., 2017).
The application that is being built for online air ticket booking system includes security tools that
makes the system more secure and safe to use. The system includes encryption technique for
keeping the data safe in the system.

9SYSTEM ARCHITECTURE
Bibliography
Chen, L., Thombre, S., Järvinen, K., Lohan, E. S., Alén-Savikko, A., Leppäkoski, H., ... &
Lindqvist, J. (2017). Robustness, security and privacy in location-based services for
future IoT: A survey. IEEE Access, 5, 8956-8977.
Ciccozzi, F. (2018). On the automated translational execution of the action language for
foundational UML. Software & Systems Modeling, 17(4), 1311-1337.
Corda, A., Brule, D., & Smith, M. (2015). U.S. Patent No. 8,949,937. Washington, DC: U.S.
Patent and Trademark Office.
Fischer, J., Møller-Pedersen, B., & Prinz, A. (2016, February). Modelling of systems for real.
In 2016 4th International Conference on Model-Driven Engineering and Software
Development (MODELSWARD) (pp. 427-434). IEEE.
Granda, M. F., Condori-Fernández, N., Vos, T. E., & Pastor, O. (2016, June). Mutation operators
for UML class diagrams. In International Conference on Advanced Information Systems
Engineering (pp. 325-341). Springer, Cham.
Jolak, R., Vesin, B., & Chaudron, M. R. (2017). Using Voice Commands for UML Modelling
Support on Interactive Whiteboards: Insights and Experiences. In CIbSE (pp. 85-98).
Kchaou, D., Bouassida, N., & Ben-Abdallah, H. (2017). UML models change impact analysis
using a text similarity technique. IET Software, 11(1), 27-37.
MaIm, J., Ciccozzi, F., Gustafsson, J., Lisper, B., & Skoog, J. (2018, September). Static Flow
Analysis of the Action Language for Foundational UML. In 2018 IEEE 23rd

10SYSTEM ARCHITECTURE
International Conference on Emerging Technologies and Factory Automation
(ETFA) (Vol. 1, pp. 161-168). IEEE.
Negri, E., Perotti, S., Fumagalli, L., Marchet, G., & Garetti, M. (2017). Modelling internal
logistics systems through ontologies. Computers in Industry, 88, 19-34.
Olmsted, A. (2016, October). Secure software development through non-functional requirements
modeling. In 2016 international conference on information society (i-Society) (pp. 22-
27). IEEE.