Software

Engineering

EXPERIMENT -3

USE CASE DESCRIPTION

Topic: Airline Management System

NAME : Tushar Bhatia

ROLL NUMBER -2K20/SE/147

1 | Page
 USE CASE DESCRIPTION

REQUIREMENT ELICITATION

1.Login : Use to provide way to enter through mobile number and

Password

2.Book ticket : Use to view the available flight timings to the

destination. Book the ticket for the passenger. To fully confirm the
booking the passenger has to pay for the ticket using NET Banking,
credit/debit cards through the BANK.

3.Cancel Booking : Cancel Ticket booking after

deducing some amount and refunding the payment

4.Check Flight Status : After booking update the seat availability in

the software. Flight is ready to board status.

1.LOGIN

1.1 INTRODUCTION : This use case describes how a user logs

into the Airline System.

1.2 ACTORS :
(i)Data Entry Operator
(ii)Administrator

2 | Page
1.3 PRE CONDITIONS : None

1.4 POST CONDITIONS : If the use case is successful the user is

logged into the system. If not the system state is unchanged.

1.5 BASIC FLOW : This use case starts when the actor wishes to
login to the Airline Management System.
(i)The system requests the actor to enter the mobile number and
password.
(ii)System validates mobile number and password.

1.6 ALTERNATE FLOW

1.6.1 INVALID MOBILE NUMBER OR OPT

If in the basic flow, the actor enters an invalid mobile number
the system displays error. The actor can either return to the
login again or cancel the login.

2.BOOK TICKET

2.1 INTRODUCTION : This use case allows

passengers to view current flight timings. This can
be viewed after entering the destination. And
then allows the passengers to book the ticket to
their destination after confirmation of payment.

2.2 ACTORS : (i)Passenger (ii)Bank

(iii)Administrator (iv) DOE

2.3 PRE CONDITION : DOE must be logged in.

3 | Page
 2.4 POST CONDITION : If the use case is
successful, the flight ticket is confirmed. Other
wise
the system remains unchanged

2.5 BASIC FLOW :

This use case starts when the passenger wants to book the ticket.

(i)The system requests DEO to specify the function he/she would

like to perform. -Confirm destination
-Pay the ticket amount

2.6 CONFIRM DESTINATION

(i)The system requests the user/passenger to enter the destination.

(ii)Once the destination name matches the names in the data the
destination is added to the system.

2.7 PAY FOR THE TICKET

(i)The system requests the user to pay thought various ways i.e
NET Banking , Credit card, debit card.
(ii)The user provide the bank details and if the transaction is
successful the bank admin confirms the transaction.

2.8 SPECIAL REQUIREMENTS : Payment

Confirmation message

2.9 USE CASE RELATIONSHIP : None

3.CANCEL BOOKING
4 | Page
 3.1 INTRODUCTION : This use case allows the
passenger to cancel the booking made.

3.2 ACTORS : (i)Passenger

(ii)Administrator
(iii)DOE

3.3 PRE CONDITION : DOE must be logged in.

3.4 POST CONDITION : If the use case is

successful, the flight ticket is canceled.

3.5 BASIC FLOW

This use case starts when the passenger wants to cancel the ticket
booking.

(i) The system requires the DEO to provide with the ticket
number.
(ii) If the number matches the one in data the ticket is canceled.
(iii) If the ticket is canceled before checking the airlines will
deduce 800 rupees form the total amount.If the ticket is
cancelled after checkin there will be no refund to the user.

4.Check Flight Status

4.1 INTRODUCTION : This use case allows the user to check the
status of their booked flight.

4.2 ACTORS : (i)Passenger

(ii)Administrator
(iii)DOE
5 | Page
4.3 PRE CONDITION : DOE must be logged in.

4.4 POST CONDITION : If the use case is successful, the use

would be able to view their flight status.

4.5 BASIC FLOW

(i) The system requires the user to enter booking ticket number
(ii) If the flight is delayed due to bad weather or maintenance
that would be updated in flight status

4.6 VIEW FLIGHT STATUS :

(i) Passenger to enter the ticker number.

(ii) System retrieves the real-time flight status.
(iii) The result is displayed.

4.7 ALTERNATE FLOW :

2.6.1 Ticker number not found

Error message displayed

4.8 SPECIAL REQUIREMENTS : None

4.9 USE CASE RELATIONSHIP : None

6 | Page
7 | Page