Software Engineering Lab
BCSE301P
Assessment 4
Name- Adnan Rizvi
[Link]. 21BCE3287
1. OO design – Use case Model
This diagram represents the interactions between actors (users) and the
system. It identifies different use cases (functionalities) in the Aircraft
System:
● Passenger: Can search flights, book/cancel tickets, and check flight
status.
● Admin: Manages flight schedules, approves maintenance, and
monitors performance.
● Maintenance Staff: Performs aircraft maintenance and reports
issues.
● Pilot: Accesses and updates flight details.
2. OO design -Class Model
The class diagram defines the structure of the system by representing
the entities and their relationships:
● Aircraft: Stores aircraft details and can assign flights or undergo
maintenance.
● Flight: Contains flight schedule and aircraft assignment.
● Ticket: Holds passenger details, seat number, and booking
operations.
● Passenger: Books/cancels tickets and views flight details.
● Admin: Manages flights and approves maintenance.
● Maintenance Staff: Performs maintenance and reports issues.
● Pilot: Updates and accesses flight status.
Relationships between these classes show how they interact within
the system
3. Sequence Diagram
This diagram shows the step-by-step interaction for the ticket booking
process:
1. The passenger searches for flights.
2. The booking system retrieves available flights from the flight
system.
3. The passenger selects a flight and enters details.
4. The system checks seat availability.
5. If available, the passenger proceeds to payment.
6. The payment system processes the transaction.
7. On success, the booking is confirmed, and a ticket is generated.
8. A confirmation email is sent to the passenger.
4. Activity Diagram
The activity diagram represents the workflow of booking a ticket:
1. The passenger searches and selects a flight.
2. The system checks seat availability.
○ If available → proceeds to payment.
○ If unavailable → shows an error message.
3. The system processes the payment.
○ If successful → booking is confirmed, ticket is generated, and
confirmation email is sent.
○ If failed → an error message is displayed.
THANK YOU