In the class diagram, we will first design and create the system’s classes, abstract classes, and interfaces. Then, we’ll identify the relationship between classes by all the requirements of the airline management system.

Components of an airline management system

In this section, we’ll define the classes for an airline management system. As mentioned earlier, we will design the system using a bottom-up approach. First, we will create the classes of small components. Next, we will integrate these components and create the class diagram for the entire system.

Account

The Account class identifies the username and ID of an airline management system user. The class definition is represented below:

Person

Person is an abstract class used to store information related to a person like a name, email, phone number, etc. In this class, the Address object type specifies the person’s address. There can be four types of accounts in the system:

• Admin: This class keeps track of the overall system and flight and aircraft records.

• Crew: This class views assigned flights in the system.

• FrontDeskOfficer: This class manages passenger reservations.

• Customer: This class views flight schedule, and reserves or cancels flight reservations.

The relationship diagram for these classes is shown below:

Airline, airport, and aircraft

The Airline class has attributes like a name and an airline code to distinguish the airline from other airlines. It is an essential part of the airline management system.

Each airline operates out of different airports. Therefore, we need the Airport class to keep track of all the airports in the system.

Airlines own or hire aircraft to carry out their flights. The Aircraft class has attributes like name, model, manufacturing year, etc.

Here’s a visual representation of these classes:

Seat and flight seat

The Seat class represents a physical seat in the aircraft. It contains basic information like seat number, seat type, and class. The FlightSeat class is derived from ...