1

SYSTEM & ANALYSIS DESIGN (SAD)

Pertemuan 5

System Requirement using Use

Case Diagram (UCD) and Use
Case Scenario (UCS)

Candiwan

Prodi MBTI – Fakultas Ekonomi & Bisnis

 2

OUTLINE

2
 3

1 Business Process Model

3
 4

Business Process Model

Business process model describe the different activities that

when combined together support a business process
Business process typically cut across functional departments
 cut across multiple objects (from oo perspective)
Business process models are powerful tool for
communication the analyst’s current understanding of
requirements with the user.
 5

2 Use Case Diagram

5
 6

Use Case Modelling

Use case – a behaviorally related sequence of steps (scenario), both automated and
manual, for the purpose of completing a single business task.
• Description of system functions from the perspective of external users in terminology they
understand.

Use-case diagram – a diagram that depicts the interactions between the system and
external systems and users.
• graphically describes who will use the system and in what ways the user expects to interact
with the system.

Use-case narrative – a textual description of the business event and how the user will
interact with the system to accomplish the task.

6
 7

Use Case Diagram

Actor
Refers to a particular role of a user of the system
Similar to external entities; they exist outside of the system

Use case symbols

An oval indicating the task of the use case

Connecting lines
Arrows and lines used to diagram behavioral relationships

2-7
 8

Major Steps in Writing Use-Case

Description and Use-case Diagrams

Step 1. Identify the major use-cases

Step 2. Expand the major use-case
Step 3. Confirm the major use-cases
Step 4. Create the use-case diagram
 9

Step 1. Identifying the Major Use-Cases

1. Review the activity diagram or flow chart described business process

2. Identify the system’s boundaries
3. List the primary actors and their goals
4. Identify and write the major use-cases
5. Carefully review use-cases and revise as needed
 Application 10

Example:

Internet Order System – Functional requirements:

1. Maintain CD Information
1.1…… 1.2….. 1.3…..
2. Maintain CD marketing information
2.1…. 2.2…. 2.3….
3. Place CD Orders
3.1 Search CDs from “CD Selection” web site; 3.2 Place orders;
3.3……
4. Maintain Orders
4.1…..4.2…
4.3 Place Instore Hold: If ordered CDs are available in a near store, the CDs are on hold and to be picked
up in the store
4.4. Place Special Order: If ordered CDs is not available in a near store, the ordered CDs will be sent to a
near store and email to the customer when it is available in the near store
 Step 1. Identifying
11

the Major Use-Cases - Example

Review activity diagram of

Internet order System:
Maintain CD
Place CD Maintain CD
marketing
Order Information
information

Maintain
CD Order
 Step 1. Identifying
12

the Major Use-Cases - Example

Identify and write the major (overview) use-cases

Use case name Primary actor Relationship

Association Include Exclude
Maintain marketing Vendor Vendor
information
Maintain CD Distribution Distribution
information system system
Place order Customer Customer Maintain order
Maintain order Customer
 13

Step 2. Expand the Major Use-Cases

6. Choose one major use-case to expand

7. Fill in details on the use-case template
8. Fill in the steps of the normal flow of events
9. Normalize the size of each step (i.e., if the normal flow of events is too
complex or long, decompose into subflows or introduce a new use case)
10. Describe alternate or exceptional flows
11. For each alternate or exceptional flow, list how the actor and/or system should
react
 14
Step 2. Expand
the Major Use-Cases - Example
 15
Step 2. Expand
the Major Use-Cases - Example
 Step 2. Expand 16

the Major Use-Cases - Example

New use case

 Step 2. Expand 17

the Major Use-Cases - Example

New use case

 18

Step 2. Expand
the Major Use - Cases - Example

Expand the major use-case

By writing down the detailed use cases, it is identified that 3 new use cases are
needed
As shown in the last slide, one “include” use case “Check out” for Place Order use
case
Similarly, Two “extend” use cases “Place instore hold” and “Place special order” for
Maintain Order use case
 19
Step 3. Confirm
the Major Use Cases

12. Review the current set of use case, revise as needed

Consider semantics and syntax
Helpful to involve the users

13. Iterate the entire set of steps until all use cases are defined
 20
Step 4. Create
the Use-Case Diagram
1. Draw the system boundary
2. Place the user cases on the diagram (better to put them in order to be
easy to read)
3. Place the actors on the diagram
4. Draw the associations (such as connecting actors to use cases by lines
etc)
 21

3 Use Case Diagram Component

21
 22
Some components of use case diagrams showing actors,
use cases, and relationships for a student enrollment
example
 23

Four Types Of Behavioral Relationships And

The Lines Used To Diagram
 24

4 Use Case Diagram Syntax

24
 25

Use Case Diagram Syntax

It consists of :
-Actor
-Use case
-Relationship link
-System boundary
-Inclusion
-Extation
-Genaralization
-Actor generalization

Source : Claudio De Sio Cesari --- Use Case Diagram Syntax Reference --- htt
p://www.claudiodesio.com
25
 26

5 Use Case Scenario

26
 27

Developing the Use Case Scenarios

The description of the use case

Three main areas:
Use case identifiers and initiators
Steps performed
Conditions, assumptions, and questions
 28

Three Sections In Use Case

6 Scanario

28
 A Use Case Scenario Is Divided into Three 29
Sections
Use case name: Register for Conference UniqueID: Conf RG 003

Area: Conference Planning

Actor(s): Participant

Stakeholder Conference Sponsor, Conference Speakers

Level Blue

Description: Allow conference participant to register online for the conference using a secure Web site.

Triggering Event: Participant uses Conference Registration Web site, enters userID and password, and clicks the logon button.

Trigger type:  External  Temporal

Steps Performed (Main Path) Information for Steps

1. Participant logs in using the secure Web server userID, Password

More steps included here…

12. Successful Registration Confirmation Web page is sent to the participant Registration Record Confirmation Number

Preconditions: Participant has already registered and has created a user account.

Postconditions: Participant has successfully registered for the conference.

Assumptions: Participant has a browser and a valid userID and password.

Success Guarantee: Participant has registered for the conference and is enrolled in all selected sessions.

Minimum Guarantee: Participant was able to logon.

Requirements Met: Allow conference participants to be able to register for the conference using a secure Web site.

Outstanding Issues: How should a rejected credit card be handled?

Priority: High

Risk: Medium
 30

Alternative Scenarios

Extensions or exceptions to the main use case

Number with an integer, decimal point, integer
Steps that may or may not always be used
 31

Benefits of Use Case Modeling

7

31
 32

Benefits of Use Case Modeling

Use cases focus on the users of the system, not the system
itself, thus the real system needs are brought to light early on.
Since a use case consists mainly of narrative text, it is easily
understandable by all stakeholders, including customers, users
and executives, not just developers and testers. By including all
the stakeholders during the early planning stages of a project,
you bring in people who best understand the problems at hand,
promote a sense of buy-in from end users, and eliminate
surprises when the system is deployed.
Source : https://casecomplete.com/use-case-benefits
32
 33

Benefits of use case modeling

Each use case describes one way the system is used, but one
of the big benefits of use case modeling is that it also describes
all of the things that might go wrong. Identifying exceptions to
a successful scenario early in the project saves a lot of time by
finding subtle requirements.
Finally, once a use case model has been developed, it can be
used to drive many other aspects of software development,
including project planning (cost, complexity and timing
estimates), object models, test case definitions, and user
documentation
Source : https://casecomplete.com/use-case-benefits
33
 34

References
Main
Kenneth E. Kendall, Julie E. Kendall (2014), Systems Analysis and Design, 9th Edition,
Prentice Hall

Support
Howard Podeswa (2010), UML for IT Business Analyst, Second Edition, Cengage Learning
Whitten & Bentley (2007) Systems Analysis and Design Methods, 7th Edition, McGraw-Hill
Alan Dennis, Barbara H Wixom, David Tegarden (2005), System Analysis and Design with
UML Version 2.0
https://casecomplete.com/use-case-benefits
 35

THANK YOU

35