Chapter 4
Chapter 4
Use Case Name: Apt. Owner adds or deletes apartment ID: _1_ Importance Level: High
Primary Actor: Apt. Owner
Short Description: This use case describes how an apt. owner adds or deletes an apartment from the database
of available apartments.
4-1
Chapter 4 Use Case Analysis
Use Case Name: Student Database Search ID: _2_ Importance Level: High
Primary Actor: Student
Short Description: This use case describes how a student searches the database for an apartment
4-2
Chapter 4 Use Case Analysis
Search results
3. Student contacts Apartment Owner(s) for selected apartments.
Apartment Owner contact
information
4-3
Chapter 4 Use Case Analysis
Use Case Name: Promote Tunes ID: _2_ Importance Level: Medium
Primary Actor: Marketing Department Staff
Short Description: This use case handles the periodic creation of targeted promotions.
4. Create email message to promote to promote sales and specials; send Web Promotions
email to customers. Promotional Email message
4-4
Chapter 4 Use Case Analysis
2. The analysts or agents might have researched similar sites to determine that
customers could indeed use the system directly. The team might have conducted a
walk-though with personnel other than agents and analysts, which may have
brought the activity to light.
3. Instead of abandoning a system that worked fairly well, the company might have
optimized it instead. Recognizing that customers use these types of sites, they
might have made this so useful to the customer that the site, and the company
name, became known as the best of place to go when searching for a home.
The purpose of a use case is to illustrate the activities that are performed by the users
of the system, and is often thought of as an external or functional view of a business
process. Use cases are developed during systems analysis activities to help the
analysts better understand the situation and simplify later modeling steps in the
analysis phase.
A use case describes in more detail the key elements of the requirements definition.
Use cases will provide more detail on the processes by which the system is to meet
those requirements and the data the system needs to capture and store.
The basic information section includes use case name, number, a brief description,
and the trigger for the use case.
4. What is the purpose of the input and outputs section of the use case?
The purpose of the inputs and outputs section is to list all inputs and associated
sources, and outputs and associated destinations for the proposed system.
5. What is the purpose of stating the primary actor for the use case?
The purpose of stating the primary actor is to identify the external entity that initiates
the event to which the system responds. The primary actor may be a user, or a system
event, or another system.
The importance level of a use case identifies the relative significance of the use case
in the overall system. Use cases are classified as high, medium, or low. This
classification allows for immediate identification of essential use cases.
4-5
Chapter 4 Use Case Analysis
7. What is the distinction between a temporal trigger and an external trigger? Give two
examples for each.
A temporal trigger is based upon the passage of time. Examples are time to pay a
bill; library book is due. External triggers are things outside the system to which the
system must respond. Examples are a customer placing an order; customer payment
is received.
Steps are outlined in order to determine the sequence of events that must occur to
complete the use case. An outline of the sequence of events aids in ensuring that all
steps are included.
9. What is the purpose of an event-response list in the process of developing use cases?
10. Should a use case be prepared for every item on the event-action list? Why or why
not?
Initially, every event on the event-list should be translated into a use case. This results
in a tentative set of use cases. Use case development can be viewed as an iterative
process, and further analysis may allow the developer to discard or add use cases to
the set.
11. Describe two ways to handle a situation in which there are a large number of use
cases.
One possibility for the large number is that the use cases are not defined at the right
level of detail. If the use cases are too „small‟ we do not need to bother to create a
use case, but simply use the information in the requirements definition itself to build
the process and data models. If there really are more than eight or nine major use
cases, the use cases are grouped together into packages of related use cases. These
packages are then treated as the major processes for the top level of the process model
with the use cases appearing on lower levels. The packages could also be treated as
separate systems and modeled as separate systems.
It is best to develop the major use cases and their basic information first so that no
major events are forgotten. Then, the inputs and outputs are added and the detailed
steps are outlined. As the inputs and outputs associated with each step are identified,
4-6
Chapter 4 Use Case Analysis
more details may be identified. It is not practical to try and get every detail right the
first time through the use case, so we cycle through the steps iteratively until the use
case is complete.
13. Describe the best way to validate the content of use cases.
Role-playing can be useful in confirming the validity of the use case. If the users
execute the steps of the use cases using the written steps of the use cases as a “script”
for actions to take, they will be able to find errors or confirm the correctness of the
use cases.
4-7
Chapter 4 Use Case Analysis
Use Case Name: See eye doctor ID: _1_ Importance Level: High
Primary Actor: Patient
Short Description: This describes how a patient obtains a prescription for new eyeglasses .
4-8
Chapter 4 Use Case Analysis
Use Case Name: Select and order eyeglasses ID: _2_ Importance Level: High
Primary Actor: Patient
Short Description: This describes how a patient chooses and orders new eyeglasses.
Trigger: Patient has new eyeglass prescription and visits eyeglass store.
Type: External / Temporal
Major Inputs: Major Outputs:
Description Source Description Destination
4-9
Chapter 4 Use Case Analysis
Use Case Name: Purchase glasses ID: _3_ Importance Level: High
Primary Actor: Patient
Short Description: This describes how a patient purchases new eyeglasses.
Trigger: New eyeglasses are ready and patient picks them up and pays for them.
Type: External / Temporal
Major Inputs: Major Outputs:
Description Source Description Destination
4-10
Chapter 4 Use Case Analysis
B. Create a set of use cases for the following dentist office system…
Use Case Name: Patient makes or changes an appointment ID: _1_ Importance Level: High
Primary Actor: Patient
Short Description: This describes how a new appointment is made or an existing appointment is changed.
4-11
Chapter 4 Use Case Analysis
Use Case Name: Collect new patient information ID: _2_ Importance Level: High
Primary Actor: Patient
Short Description: This describes how new patient information is collected when a new patient arrives for
appointment.
4-12
Chapter 4 Use Case Analysis
Use Case Name: Send appointment reminder card ID: _3_ Importance Level: Medium
Primary Actor: System
Short Description: This describes how reminder cards are sent to patients two weeks prior to appointment.
4-13
Chapter 4 Use Case Analysis
C. Complete the use cases for the dentist office system in exercise B by identifying the
steps and the data flows within the use cases.
Use Case Name: Patient makes or changes an appointment ID: _1_ Importance Level: High
Primary Actor: Patient
Short Description: This describes how a new appointment is made or an existing appointment is changed.
4-14
Chapter 4 Use Case Analysis
Use Case Name: Collect new patient information ID: _2_ Importance Level: High
Primary Actor: New Patient
Short Description: This describes how new patient information is collected when a new patient arrives for
appointment.
1. When the patient arrives, determine if he/she has been seen before in Patient status
this office. If they have not, have them fill out a patient information
form.
Patient name
2. Use the information on the patient information form to update and Address
complete the patient’s entry in the patient file. Phone number
Medical history
4-15
Chapter 4 Use Case Analysis
Use Case Name: Send appointment reminder card ID: _3_ Importance Level: Medium
Primary Actor: System
Short Description: This describes how reminder cards are sent to patients two weeks prior to appointment.
1. Each day, find the appointments in the Appointment file for the day two Current date
weeks ahead. Scheduled appointments
2. Prepare and mail appointment notification card to all patients having Name
appointments. Address
Appointment
4-16
Chapter 4 Use Case Analysis
Use Case Name: Maintain department course offerings ID: _1_ Importance Level: High
Primary Actor: Department/Staff
Short Description: This describes how department staff reviews course offerings, adds new courses, deletes
existing courses or changes existing course information.
4-17
Chapter 4 Use Case Analysis
Use Case Name: Maintain student enrollments ID: _2_ Importance Level: High
Primary Actor: Student
Short Description: This describes how students review the listing of courses available for enrollment, add and
remove courses from their schedules, and review their schedules.
4-18
Chapter 4 Use Case Analysis
Use Case Name: Course enrollment reports ID: _3_ Importance Level: High
Primary Actor: Staff
Short Description: This describes how department staff prints various reports on courses and enrollments.
4-19
Chapter 4 Use Case Analysis
Use Case Name: Maintain house seller information ID: _1_ Importance Level: High
Primary Actor: Seller
Short Description: This describes how house sellers enter into a contract to sell and provide information on a
house to sell.
4-20
Chapter 4 Use Case Analysis
Use Case Name: Generate Buyer’s Request ID: _2_ Importance Level: High
Primary Actor: Buyer
Short Description: This describes how buyers request and receive information on offered houses.
4-21
Chapter 4 Use Case Analysis
Use Case Name: Maintain Video inventory ID: _1_ Importance Level: High
Primary Actor: Video Supplier
Short Description: This describes how to add and remove videos from video database.
Video descriptive information Video Supplier Video removed from Video file
Damaged video information Manager stock
___________________________ ___________ New video to rent Video file
___________________________ ___________ ________________ _________
___________________________ ___________ ________________ _________
________________ _________
4-22
Chapter 4 Use Case Analysis
Use Case Name: Maintain customer data ID: _2_ Importance Level: High
Primary Actor: Customer
Short Description: This describes how customer information is established and overdue fine status is
eliminated.
1. When a new customer wants to rent a video, he/she provides customer Customer information
information. A record is entered into the customer file and the customer AVS Customer card
is given an AVS customer card.
2. Customer removes overdue/damaged video fee by paying overdue fine. Customer information
Overdue video fee
Overdue fee payment
4-23
Chapter 4 Use Case Analysis
Use Case Name: Maintain video rental data ID: _3_ Importance Level: High
Primary Actor: Customer
Short Description: This describes how video rentals are entered and returns and overdue videos are recorded.
3. Video becomes overdue. An overdue fee is assessed and added to Current date
customer file. Video due date
Overdue fee assessment
Overdue video notice
4. Manager produces report and contacts customers with videos that are two Current Date
or more days overdue. Rented and overdue videos
Customer information for
overdue rentals
4-24
Chapter 4 Use Case Analysis
G. Create a set of use cases for the following health club membership system…
Use Case Name: Maintain members ID: _1_ Importance Level: High
Primary Actor: Member
Short Description: This describes how club records new member information, makes member changes to
member information, and removes members.
4-25
Chapter 4 Use Case Analysis
Use Case Name: Maintain memberships ID: _2_ Importance Level: High
Primary Actor: Manager
Short Description: This describes how to record new memberships and process membership renewals.
2. Contact members one month prior to membership expiration and offer Current Date
renewal terms. Current membership details
Renewal details
Renewal offer
4-26
Chapter 4 Use Case Analysis
Use Case Name: Maintain club usage records ID: _3_ Importance Level: High
Primary Actor: Member
Short Description: This describes how to record and report on member usage of the club.
Trigger: Need to record member visit to club and produce manager's reports.
Type: External / Temporal
Major Inputs: Major Outputs:
Description Source Description Destination
1. Member checks in when using club. Member ID, time, and date of visit are Current Date
recorded. Current Time
Member ID
Visit date
Visit time
2. Manager wants report of heavy users and report of inactive members. Report request
Member visit records
Member information
4-27
Chapter 4 Use Case Analysis
Use Case Name: Establish picnic contracts ID: _1_ Importance Level: High
Primary Actor: Customer
Short Description: This describes how customers receive information and book picnics.
Special request
2. Customer has special request and received owner's cost
Special pricing
estimate.
4-28
Chapter 4 Use Case Analysis
Use Case Name: Maintain picnic contracts ID: _2_ Importance Level: High
Primary Actor: Contracts
Short Description: This describes how customer receives contract information and may confirm contract.
4-29
Chapter 4 Use Case Analysis
Use Case Name: Order supplies ID: _3_ Importance Level: Medium
Primary Actor: System
Short Description: This describes how owner reviews upcoming picnics and orders required supplies.
2. Determine food and supply requirements by reviewing upcoming weekend’s Weekend Picnics
picnics, picnic menus, and food/supply inventory. Standard menus
Standard menu food and
supply needs
Food qty-on-hand
Supply qty-on-hand
4-30
Chapter 4 Use Case Analysis
Use Case Name: Maintain club memberships ID: _1_ Importance Level: High
Primary Actor: Customer
Short Description: This describes how to create, change, and delete members.
4-31
Chapter 4 Use Case Analysis
Use Case Name: Maintain memberships ID: _2_ Importance Level: High
Primary Actor: Member
Short Description: This describes how to add, renew, or delete memberships.
1. Member selects one or more clubs to join and membership in the club(s) is Club request
established. Club details
Membership record
2. Member is sent renewal notice when end of club term nears. Current Date
Membership details
Club term expiration
Renewal notice
4-32
Chapter 4 Use Case Analysis
Use Case Name: Maintain club ID: _3_ Importance Level: Medium
Primary Actor: Management
Short Description: This describes how clubs are added, changed. or deleted.
4-33
Chapter 4 Use Case Analysis
Use Case Name: Maintain books ID: _1_ Importance Level: Medium
Primary Actor: Management
Short Description: This describes how to record owned books and books that are lost or removed due to
damage.
Book(s) to remove
2. Lost or damaged books are removed from
Book to delete
book holdings.
4-34
Chapter 4 Use Case Analysis
Use Case Name: Process borrowed book ID: _2_ Importance Level: High
Primary Actor: Borrower
Short Description: This describes how to check out and return books.
Book to check out Borrower Borrowed book info change Borrowed book file
Borrower ID Borrower Returned book info change Book holdings
Validation information Valid Borrower file Overdue status Overdue file
Overdue book info Overdue file _______________________ ____________
Fine due info Fines file _______________________ ____________
Returned book Borrower _______________________ ____________
Borrowed book info Borrowed book file _______________________ ____________
1. Borrower presents book(s) to check out. ID is checked for validity Book to check out
against valid borrower file. Overdue books and fines are checked. If OK Borrower ID
book is lent to borrower. Validation information
Overdue books info
Fines due info
Borrowed book info
2. Borrower returns book. Book is removed from borrowed file and returned Returned book
to holdings. If overdue, book is removed from overdue file. Borrowed book info
Borrowed book info change
Returned book info change
Overdue file status
4-35
Chapter 4 Use Case Analysis
Use Case Name: Process overdue books. ID: _3_ Importance Level: High
Primary Actor: System
Short Description: This describes how to identify overdue books, notify borrower, assess fines.
1. Borrowed book lending term expires. Entry is made in overdue file. Current date
Book lending term
Overdue status change
2. Borrowed book is more than two weeks overdue. Fine is assessed. Borrowing details
Fine entry
3. Every week, overdue book notices are sent to borrowers. Borrowing details
Overdue book notice
4. Manager specifies fine for lost or damaged book. Book damage entry
Fine entry
4-36
Chapter 4 Use Case Analysis
b. To help us understand your business processes, we utilize a tool called a use case.
The use case represents the activities that are performed by users of your system
and the information needed to accomplish these activities. The use case is
prepared from the perspective of the client, and we will be working closely with
you and your staff to understand the essential activities of your system. We will
meet with you and your staff several times to refine our use cases and to add
appropriate details as our understanding of necessary activities and information
grows richer. Our use cases will form the foundation of our next steps in
analyzing your current system and designing the new system.
Use cases are used to assist the users to represent the business processes in an
informal, verbal way rather than with the formality of data flow diagrams. This
technique can be used to help develop process models of both the As-Is and the
To-Be systems. Use cases use a three-stage process that develops the information
needed to create data flow diagrams. First, the users identify the major activities
that the users perform (referred to as use cases). Then the team works through
several steps to develop a more detailed outline of the activities performed within
each use case and the inputs and outputs needed to perform each step
4-37