ISYS 2395:Business Systems

Analysis and Desing

Session 5

Expanded use case exercises and

“sample” solutions
Alem Molla
Exercises

Exercise 1: Use case packages for a restaurant CLO1: Critically analyse the
strategic and operational needs of
system an enterprise in a real-world
situation.
Exercise 2: Section 1 of expanded use case CLO2: Address the strategic and
operational needs of an enterprise
Exercise 3: Section 2 of expanded use case by designing appropriate and
relevant technological solutions.

Exercise 4: Section 3 of expanded use case CLO3: Demonstrate a critical

understanding of system analysis
and design methodologies in order
Exercise 5: Transmit/track order expanded use to evaluate the application of
case systems in a business context.

CLO4: Demonstrate a critical

Exercise 6: Budget airline system process and use understanding of the relevant tools
case available and their appropriate
application in the context of the
business environment.
Exercise 7: Mobility service system process and
use case

2
Exercise 1

Continue Discover Identify Develop Organise

Continue with the Discover the Identify actors Develop use Organize the use
restaurant different cases (not UCD) cases into
system example business for the actors packages
from the previous processes
class

3
Exercise 1: Business process
discovery
The reservation The sitting
The order process
process process

The serving/eating
The meal
process (appetizer The payment
preparation
(starter), main process
process
course, dessert)

The checkout
???
process

4
Exercise 1: Restaurant
management information system
actors
Customer

Worker: waiter, chef, assistant, bartender,

receptionist, head waiter, busser, concierge,
cashier, security, purchaser, manager

External: supplier, payment clearing system, etc

Note: The actors and use cases depend on the type of restaurant and the system one is building, i.e., product
vision and project scope.
5
RMIS Functionality Package Display
Make
reservation
<<extend>>
Read
review
Take order <<include>>
menu <<extend>>
<<include>> Choose
<<extend>> <<extend>> Cancel table
Transmit order
reservation
to kitchen Confirm
Customise Change
order order reservation

<<extend>>
Add tip
Track order Pay bill
Review order
Status <<extend>>
Leave
<<include>>
<<extend>> review
Pay
Receive kitchen Calculate split bill
Cancel notification discount
order

Update Review Process

Acknolwedge reservation payment
prepartion
order
status
<<extend>> <<include>> <<include>> Calculate Split
Check discount bill
inventory Receive order

Review
Call robot
reservation

Take Transmit
<<include>>
order order
<<include>>
to kitchen
Customis
Make e order <<include>>
Notify Track
Confirm <<include>> reservation Chef order
reservation Change party Status
<<include>>
Check order status <<include>>
availability <<include>>
Review
<<extend>> Receive
order Process
kitchen
Cancel update bill
<<extend>> notification
reservation availability
Exercise 2

Continue with exercise one

Take a use case (e.g. Take an order) from one of
your packages
Complete all components of the first section of an
expanded use case

7
Exercise 2
Use Case Name Take order (from REMIS)

Scenario Placing an order in a restaurant that provide either a waiter or self order
services
Triggering event A customer wanting a meal

Brief description This describes the process of entering an order either by a waiter (using
handheld device) or customer (using QR)
Actors Customer, waiter, Chef

Related use case Display menu, transmit order to kitchen

Stakeholders Waiter, Cashier, manager, supply department …..

Preconditions A seated customer who read a menu

Postconditions An order entered in the system and sent to the kitchen

Assumptions Customer wants a meal, read the menu, and make selection. Handheld
devices and QR codes are in working order. Customer has a working
mobile device and internet connection

8
Exercise 3

Continue with exercise one and two

Complete the actor-system flow of activities
(Section 2 of expanded use case) for one use
case (e.g. Take an order) of the restaurant

9
Exercise 3: Flow of activities

Flow of Actor action System response

activities
1. Waiter activates the user 2. Order entry user interface
interface on the device appears

3. Waiter enters menu 4. System transmits order to

selection kitchen

10
Exercise 4

Continue with previous exercises

Complete alternative courses/ exceptions (if any)
for one use case (e.g. Take an order) of the
restaurant system

11
Exercise 4:
Exceptions/alternative
Flow of Actor action System response
activities
1. Waiter activates the user 2. Order entry user interface
interface on the device appears

3. Waiter enters menu 4. System transmits order to

selection kitchen

Exception Line 1: Customer scans QR Line 2: system displays menu

conditions code and order cart
Line 3a: customer enters
selection to cart Line 3a.1 System collects
selection
Line 3b: Customer finalise
selection

12
Exercise 5

Take another overall use case (e.g. Transmit order

to kitchen, Track an order) from the restaurant and
develop an expanded use case completing all the
three sections.

13
 Exercise 5
Use Case Change order
Name
Scenario Changing an order transmitted to the kitchen by a waiter
Triggering event Customer order change request
Brief description This describes the process a waiter follows to change an order transmitted to the kitchen
using their handheld device
Actors Customer, waiter
Related use Review order, Transmit order to kitchen, Track order status, Receive kitchen notification
case
Stakeholders Customer, waiter, chef, cashier, etc
Preconditions Placed and transmitted order
Postconditions Acceptance or rejection of order change request
Assumptions An order placed and transmitted to kitchen and the customer wants to change that order. A
database of order per waiter per table number. Waiter has access to handheld device
Flow of Actor Action System response
Activities 1. Customer ask to change order
2. Waiter activities order change
interface 3. List of existing orders placed by waiter

4. Select order to change 5. Display order status

6. Enter order modification 7 Transmits order to kitchen

Exception Line 5: System notifies waiter if the order is changeable
conditions Line 6: Waiter verifies changeability of order, if not changeable reject customer request
Line 7: System rejects unchangeable order request

14
Exercise 6: Budget Airlines

Think of a budget airline. Passengers can book directly online.

Booking can be paid for by Credit Card, PayPal, or Direct Debit
transfer. The airlines has to offer services according to the
bookings. It must source materials and other stuff from suppliers
accordingly

1. Identify the different stakeholders/actors

2. Discover business processes

3. Develop an overall UCD

4. Organize the use case into packages

5. Develop an expanded use case for booking a flight

15
Exercise 6: Business
Processes

Airline reservation (ticketing)

Airline service management
Airline staff allocation
Supply chain management

16
Exercise 6:
Stakeholders/ actors

• Customers/Passengers
• Airline Managers
• Airline Staff (Reservation Staff, Payment
managers)
• External Financial institutes (Banks, PayPal,
Crypto)

17
Exercise 6: UCD

Search Check
<<include>>
for flights availability

Book <<extend>>
Select
a flight add-ons

Customer Paypal
Pay customer
Paypal
Pay
for flight
Pay by
Crad
Card
Choose Pay by customer
seat Crypto

VIP Receive
customer Crypto
eTicket <<extend>> Login/
customer
and invoice register

18
 Exercise 6
Use Case Name Book a flight

Scenario A customer wants to book a flight online

Triggering event A customer initiating an online booking process
Brief description A customer can use a website or app that are available to book for a flight. A customer’s destination is
served by the airline
Actors Customer, website, app
Related use case Extend select add-on
Stakeholders Customer, Finance dept, airline reservation, Bank, Paypal, Insurance
Preconditions Customer is online and visiting the airline website or app,
Postconditions The customer should be asked to make a payment for the reservation
Assumptions The system (app/website) is online and available, flights are available
Flow of Activities Actor action System response
1. Customer searches for flights by 2. System generates a list of flights as per customer search
specifying a date, destination, and point of criteria
departure 4a. System adds the flight to customer itinerary and displays
3. Customer selects a flight from the list price
4b. System displays a list of add-ons (insurance, emission,
catering, luggage weight, entertainment, etc.)
5. Customer selects add-ons 6. System adds add-ons to itinerary and displays updated
price
8. System presents payment options (Paypal, Card
7. Customer opts for check-out payment, Crypto-currency, etc)

Exception 3. Customer decides not go ahead with flight selection and exits the application
conditions 5. Customer decides not to select any add-on, in which she/he can move onto step 7
6. System indicates that particular add-on is not available, in which case the customer has to change
preference for add-ons or move onto step 7
7. Customer may change her/his mind based on the updated flight price, and change preference for add-
ons, in which case she/he reverts back to step 5

19
Exercise 7: Post Class
exercise
Think of a mobility service (such as taxi, Uber, e-
scooter) provider system.
1. Identify the different stakeholders/actors
2. Discover business processes
3. Develop an overall UCD
4. Organize the use case into packages
5. Develop an expanded use case for booking a
trip

20
Exercise 7: Actors

Customer (passenger)
Driver
Vehicle
GPS
Payment system (finance company)

21
Exercise 7: UCD

Register

<<include>>
First time
customer
Driver
Book a ride
<<include>> Choose
Ride

Monitor
arrival
Customer Share
Trip GPS
<<extend>>

Complete <<extend>> Rate trip

journey
<<extend>>

Tip driver

22
 Exercise 6
Use Case Name Book a ride

Scenario A customer wants to book a flight online

Triggering event A passenger intending to book a trip using an app
Brief description A passenger who is or is not register in a mobility service intends to book a ride using an app
Actors Customer (primary), app, driver, GPS, payment system
Related use case Include: register, choose ride
Stakeholders Customer, Finance dept, Bank, Driver,
Preconditions Customer is online and has an app
Postconditions The customer complete a booked trip
Assumptions The app is available, Customer knows how to use the app, has access to payment option (card, mobile
pay) or digital wallet
Flow of Activities Actor action System response
1. Customer activates application 2. System requests pickup and destination address and
3. Customer enters address activates GPS
4a. System sends addresses to GPS.
4b. System receives coordinates and looks at available
vehicle coordinates
4c. System matches Pick-up address with nearest vehicle
4d. System presents nearest vehicle information
4e. System estimates fare
5. Customer confirms ride
6. System notifies customer of vehicle location
Exception Line 1 System notifies Customer to Register (pointing to a Use Case for Register Customer). Process
conditions terminates here and resumes once customer is registered. {violated a pre-condition, which can happen}
Line 4a: System notifies Customer to turn on GPS
Line 4b: System notifies to re-enter addresses (not received coordinates from GPS)
Line5: Customer cancels the booking, in which case:
Line 6: System indicates the termination of the transaction

23