Requirements Engineering

Lecture: 18
Instructor: Salman Ahmad
Case Study
• Problem statement:
A new system is begin desired for passengers to check-in and get the boarding pass for
their flight. Passengers can also check in their baggage which is optional. Considering the
frequent flyers, check-in would also be possible by clerk on the counter or by using kiosk.
Passengers check-in by verifying their PRN and their identity as a flyer. Young passengers
(below the age of 4 years) do not need to have tickets. There is also provision for special
needs passengers at the airport for the travelers and they can ask for such using the system
like wheel chairs etc.
The baggage that the passengers check-in must be screened by the security before they are
checked-in. There is a limit on the baggage that each passenger can carry. If their baggage
weight is more than 15Kg, additional charges must be paid as per defined charges.
It is assumed that passengers detail, ticketing information, boarding pass create, delete are
already available from an existing system and are out of current scope.
Actors
• Passengers
• Young Passenger (less than 4 years old)
• Passenger with special needs
• Group of passengers
• Check-in clerk
• Kiosk
Actor

Group

Clerk

Young Passenger

Passenger

Kiosk Passenger w/ special needs

Actor - Passenger
• Check In
• Request special need assistance
• Print boarding pass
Actor - Clerk
• Validates PNR
• Validate ID
• Flag Special Needs
• Print boarding pass
Actor - KIOSK
• Check-in Passenger
Use Case of Passenger

Validate
<<include>>
Check- PRN
in

Request
special
assistance
Passenger
Print
boarding
pass
Use Case of Clerk
Validate
PNR

Validate
ID

Flag
Passenger Special
Need
Print
boarding
pass
<<extends>> Calculate
Baggage charge
checkin
Use Case of Kiosk

<<include>> Validate

Check-in PRN

Kiosk
• Abstract
• Validate PNR
• Concrete
• Check-In
• Validate Id
• Flag Special Needs
• Baggage Weight
• Calculate Weight Charge
• Print boarding pass
Validate PRN Use Case
• Name: Validate PRN
• Summary: System validates passenger PRN
• Dependency: None
• Actors: Passenger, Group, Young Passenger, Passenger with special
needs
• Preconditions: Clerk desk is clear, clerk is ready and waiting for
checking-in
Validate PRN Use Case
• Flow of Events: Basic Path
• Passenger presents the PRN number to clerk
• Clerk enters the PRN number
• System checks for PRN validity
• If PRN is valid, clerk is prompted with validity and asks for check-in
• Alternatives:
• If the system does not recognize the PNR, the system prompts an error
message and process stops
• If the PNR is invalid – because clerk made a mistake, the system prompts an
error message and process stops
Validate PRN Use Case
• Postcondition
• PRN is verified and system prompts for next step
Check-In Use Case
• Name: Passenger Check-in
• Summary: System checks-in the passenger
• Dependency: Validate PRN abstract use case
• Actors: Passenger, Group, Young Passenger, Passenger with special
needs
• Preconditions: Clerk desk is clear, clerk is ready and waiting for
checking-in
Passenger Check-in Use Case
• Flow of Events: Basic Path
• Validate PRN abstract use case
• Passenger puts the baggage on tray
• System prints stickers to put on baggage
• Clerk selects check-in
• System confirms the passenger as checked-in
• Alternatives:
• If passenger does not have a baggage, no stickers will be printed,
• If system is unable to confirm the customer system will show an apology
message and stop the process
Request Special Assistance Use Case
• Name: Passenger requests special assistance
• Summary: System accommodates passenger request for special
assistance
• Dependency:
• Actors: Passenger, Group, Young Passenger, Passenger with special
needs
• Preconditions: Clerk desk is clear, clerk is ready and waiting for
checking-in
Request Special Assistance Use Case
• Flow of Events: Basic Path
• Passengers make requests to the clerk
• Clerk marks the request for the passenger in the system
• System checks for availability of the equipment
• If everything is available, request is marked for the passenger
• Alternatives:
• If the requested facility is not available, system will show an error and stop
further processing
• If passenger is not found/identified in the system, it will show an error and
stop further processing
Request Special Assistance Use Case
• Postcondition
• Special request is marked for the passenger
Baggage check-in Use Case
• Name: Clerk checks in passenger baggage
• Summary: System weighs the baggage to tag and check-in for
passenger
• Dependency: None
• Actors: Clerk
• Preconditions: Clerk desk is clear, clerk is ready and waiting for
checking-in
Baggage check-in Use Case
• Flow of Events: Basic Path
1. Passengers puts the baggage on tray
2. System weighs and displays weight of the baggage
3. If weight of baggage is less than or equal to 15 Kgs, system generates sticker
with information of flight, destination, origin and passenger
4. Clerk, sticks the stickers on the baggage
5. System accepts the baggage for cargo
Baggage check-in Use Case
• Alternatives:
3.A.1 If the baggage weight is more than 15 Kgs, system calculates the charge
for additional weight
3.A.2. Passenger makes the payment for additional charge
3.A.3. Clerks receives payment and generate receipts

3.A.1 Calculate Charge* use case (other option)

Baggage check-in Use Case
• Alternatives:
3.A.1 If the baggage units are more than one then system generates stickers for
every unit
4.B.2 Clerk sticks sticker on each baggage unit
Baggage check-in Use Case
• Postcondition
• Passenger baggage is checked in