AIMS Design Model: In-depth Analysis of Architecture and Sub Systems

This report provides a detailed analysis of the AIMS (Airline Information Management System) design model, encompassing its overall architecture and specific sub-systems. The architectural model illustrates the interaction between users and the main server, highlighting the central database connected to both backend and frontend processes, including ticket confirmation, flight reservation, and HR management. A detailed examination of the ticket booking sub-system identifies administrators and users, outlining their roles in data maintenance and flight booking. The report includes a class diagram that defines classes like Tickets, Flight, AIMS System, Payment, Users, and Admin, detailing their methods and attributes. Communication and sequence diagrams further clarify the interactions and message flows within the system, illustrating how users book tickets and administrators manage the process. The included bibliography lists relevant research articles on enterprise architecture and system design methodologies.

Running head: AIMS
AIMS design model
Name of the Student:
Name of the University:
Author Note

1
AIMS
Table of Contents
Overall Architectural model.......................................................................................................2
Detailed model of Sub System...................................................................................................3
Class Diagram............................................................................................................................4
Communication Diagram...........................................................................................................5
Sequence Diagram.....................................................................................................................6
Bibliography...............................................................................................................................7

2
AIMS
Overall Architectural model
The AIM system is used for the interaction of the users with the main server system of
AIMS, the system consists of a central database system which is connected to the back end
processes and the front end processes. The overall architectural model of the AIMS system
has been discussed above, the main backend procedures of the system are connected by an
integrated system. In addition to this there are other sub-systems in the model such as the
ticket confirmation systems, flights reservation systems, flight warehouse maintenance
system, HR management system. The front end part of the system consists of the registration
system, log in system, tickets booking system, seat reservation system, remote connection
component and remote log in process to the system. All these process fetch the data from the
central database and update the data in the central database of the system.

3
AIMS
Detailed model of Sub System
For the description of the detailed model of the AIM System the ticket booking
system has been selected and the users interacting to the system have been identified as the
Administrator and the Users.
The administrator of the AIM system is responsible of performing the tasks of
maintenance of data in the system, such as the flight details, airport details, flight timings and
the details of the users that would be barding the flights from the airports. On the other hand,
the users are associated with viewing the details of the flight and booking a particular flight

4
AIMS
for themselves. All the data fetched and updated are done on the main server that is located
centrally for the system.
Class Diagram
The class diagram has been created on the sub system of the flight booking sub
system. The class diagram has been used here for the description of the classes and the
methods which are identified in the associated with the sub system of the flight booking
system. The main entities that have been identified in this class diagram are the tickets, flight,
AIM system, Payment, Users and the Admin. The Ticket class contains the details of the
details of the tickets such as the flight number, status of the flight, the number of persons
boarding with the ticket and the type of tickets. The class also contains two methods for a

5
AIMS
new ticket and deleting ticket. The admin class consists of two functions, form cancellation
and form details. The users class is responsible for booking the tickets in the system.
Communication Diagram
The communication diagram provides the details of the interaction among the users,
administrators and tickets systems. The users communicates with the administrator and in
return the administrator communicates with the tickets and provides the tickets to the users.
The users generally searchers for the flight tickets and books the ticket once the desired result
is obtained. The administrator checks the status of the tickets and notifies the user about the
availability of the tickets. The users then confirm the tickets and the administrator adds ticket
to the system and provides in to the users as soon as they make the payment. On making the
payment the printed ticket is made available to the users.

6
AIMS
Sequence Diagram
The sequence diagram displayed above provides the information about the flow of
messages in the system. The user interacts with the AIMS system and sends messages
directly to the administrator. After the logging into the system and providing the details of the
tickets the users books the tickets, the message is forwarded to the administrator from the
system and administrator prints the ticket and provides it to the system where the message is
forwarded to the users in the system.

7
AIMS
Bibliography
Hansen, P. and Hacks, S., 2017. Continuous Delivery for Enterprise Architecture
Maintenance. Full-scale Software Engineering/The Art of Software Testing, 56.
Hinkelmann, K., Gerber, A., Karagiannis, D., Thoenssen, B., Van der Merwe, A. and
Woitsch, R., 2016. A new paradigm for the continuous alignment of business and IT:
Combining enterprise architecture modelling and enterprise ontology. Computers in Industry,
79, pp.77-86.
Plataniotis, G., Ma, Q., Proper, E. and de Kinderen, S., 2015, May. Traceability and modeling
of requirements in enterprise architecture from a design rationale perspective. In Research
Challenges in Information Science (RCIS), 2015 IEEE 9th International Conference on (pp.
518-519). IEEE.
Rouhani, B.D., Mahrin, M.N.R., Nikpay, F., Ahmad, R.B. and Nikfard, P., 2015. A
systematic literature review on Enterprise Architecture Implementation Methodologies.
Information and Software Technology, 62, pp.1-20.