0% found this document useful (0 votes)
10 views5 pages

Software Engineering Lab7

The document outlines a lab assignment for CPE 310 Software Engineering at Karabuk University, focusing on requirements modeling through UML use case diagrams. It details the actors and use cases for an Online Flight Reservation System and an Airport Check-In System, highlighting various passenger types and their interactions with the systems. The document includes specific use cases such as booking flights, checking flight status, and different check-in methods.

Uploaded by

cikif83366
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
10 views5 pages

Software Engineering Lab7

The document outlines a lab assignment for CPE 310 Software Engineering at Karabuk University, focusing on requirements modeling through UML use case diagrams. It details the actors and use cases for an Online Flight Reservation System and an Airport Check-In System, highlighting various passenger types and their interactions with the systems. The document includes specific use cases such as booking flights, checking flight status, and different check-in methods.

Uploaded by

cikif83366
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

KARABUK UNIVERSITY

Computer Engineering Department

CPE 310 Software Engineering


Lab#7
Requirements Modeling
Scenario-based methods: User Case Diagrams-II

Hasan Kivrak
Agenda
● Draw a UML use case diagrams for
○ Online Flight Reservation System

○ Airport Check-In System


Online flight reservation system
● Actors are Passenger:
○ Different types of passenger can use the system
■ Child Passenger
■ Passenger with Special Needs (e.g. disabilities)

all playing external roles in relation to airport system.

● Use cases are (main tasks or functions performed by the actor)


○ Book a flight
■ includes the use case Fill details
■ extends use cases Make payment and Select seat
○ Check flight status
○ Manage booking
■ Extends use cases Cancel Flight and Reschedule Flight
○ Check-In
Check in system
● Use cases are
○ Group check in
○ Individual check in

● Counter Check-in, Kiosk Check-in, Online Check-in inherits from the use case Individual check in

○ As a result of the inheritance relationship, a Passenger actor is involved in the execution of


use case Individual check in

● Baggage Handling extend Check-In use cases,

○ because passenger might have no luggage, so baggage handling is optional.


UML use case digrams

You might also like