Fase Desain:

Use Case dan

Process Modeling

Maryam S.Kom, M.Eng

Review
“
○ Analysis Phase
○ Requirements
 ○ Modeling system requirements using
traditional approaches and object
Learnig oriented approaches correctly
Outcome
 1. Object Oriented dan UML
Sub-topic 2. Use Case
3. Traditional Approach
4. Data Flow Diagram (DFD)
Pemodelan Kebutuhan Sistem
 7

Object Oriented
dan UML
 ○ Unified Modeling Language (UML) is a
"language" that has become a standard in
UML (1) the industry for visualization designing and
documenting information systems or software
○ UML offers a standard for designing a system
model
○ UML notation is a set of special forms to
describe various software diagrams
UML (2)
UML (3)
 Zachman Framework

System requirements

Use Case Class

Model Diagram

Activity/Sequence State
Diagram Chart

Component Deployment
UML (4) Diagram Diagram

(Dalam Analisis danDesain)

Use Case

12
 ○ Use case diagrams illustrate the expected
functionality of a system. What is emphasized is
"what" the system does, and not "how".
Use Case (1)
○ A use case represents a interaction between actors
and systems.

○ Represents how the system interacts with its

environment by describing the activities carried out by
system users and the response of the system
 ○ The first stage of making Use Case is :
○ identifying the user (user),
○ purpose / user activity in the system and
○ the results of the activity.
Use Case (2)
Use Case(3)
Use Case (6)
: Core Use
Case
Element
Use Case Specification in ATMSystem

Withdraw Money
1. The use case begins when a client inserts a card into the
ATM. The system reads and validates information on the
card.
2. The system prompts for a personal identification number
(PIN). Client enters the PIN. The system validates the PIN.
3. The system asks which operation the client wishes to
perform. Client selects “Withdraw Money”.
4. The system requests the amount of withdrawal. Client
enters amount.
Use Case Specification in ATMSystem

Withdraw Money
5. The system request the account type. Client selects the
account type (checking, saving, credit).
6. The system communicates with the ATM network to validate
the account ID, PIN, and availability of the amount requested.
7. The system asks the Client whether a receipt is desired. This
step is performed only if there is paper available to print the
receipt.
8. The system asks the Client to remove the card. Client
removes the card.
9. The system dispenses the requested amount of cash.
10. The system prints a receipt, if required, which ends theuse
case.
Use Case Specification
Actor Action System Response
1. This use case begin when a
Customer arrives at a POST
checkout with items to pur-
chase.
2. The Cashier records UPC 3. Determines the item price
for each item. and adds the item informa-
tion to the running sales
transaction.
A Common Mistake
with Use Cases
A use case is a relatively large end-to-endprocess
description that typically includes many steps or
transactions; it is not normally an individual stepor
activity in a process, e.g. “printing the receipt”

Identifying use cases differs from process/ function

decomposition
 21

○ Give the name of a use case by using

Naming Use a verb to show a process in the
Case system
○ Example: KRS Input, Input order,
Delete student data
 Contoh Use Case(1)

ATM
Check Balance <<includes>>

<<includes>> login
Client Withdraw Money

<<includes>>
Transfer Money
 Sistem Informasi
Perpustakaan
Mengembalikan <<extends>>
Buku

Menagih Denda
Petugas

Meminjam Buku
24
Library Information System

Browse Catalog
Menambah Koleksi

Meng-konfirmasi
Undergrad Transaksi
Student
Memesan Buku Librarian

Meminjam Buku

Memesan Copy
Lecturer
Postgrad Memperpanjang
Student Pinjaman
Undergrad’s Point of View

Browse Catalog

Undergrad
Student
Memesan Buku Librarian

Meminjam Buku

Lecturer
Postgrad
Student
Postgrad’s Point of View

Browse Catalog

Undergrad
Student
Memesan Buku Librarian

Meminjam Buku

Memesan Copy
Lecturer
Postgrad
Student
Lecturer’s Point of View

Browse Catalog

Meng-konfirmasi
Undergrad Transaksi
Student
Memesan Buku Librarian

Meminjam Buku

Memesan Copy
Lecturer
Postgrad Memperpanjang
Student Pinjaman
Librarian’s Point of View

Browse Catalog
Menambah Koleksi

Meng-konfirmasi
Undergrad Transaksi
Student
Memesan Buku Librarian

Meminjam Buku

Memesan Copy
Lecturer
Postgrad Memperpanjang
Student Pinjaman
UC - Library Information System

Browse Catalog
Menambah Koleksi

Meng-konfirmasi
Undergrad Transaksi
Student
Memesan Buku Librarian

Meminjam Buku

Memesan Copy
Lecturer
Postgrad Memperpanjang
Student Pinjaman
 Traditional
Approach
&
Data Flow
Diagram (DFD)

32
 Describe activities as processes carried
out by people or computers

Traditional
Approach
 • DFD is a graphical system model that
shows all the main requirements for
information systems in one diagram:
Data Flow input and output,
Diagram (DFD) process, and
(1)
data storage.

Emphasized in the data stream.

DFD (2) : DFD Notation / Symbol
DFD (2) :
DFD Notation
/ Symbol
 ○ There is no direct connection between
entities and data! (must go through a
process)
DFD (3) :
ATTENTION!
 ○ Context Diagram = Level 0
Diagram
○ Level 1 diagram
DFD (4) : ○ Level 2 diagram ... etc.
DFD leveling
 Drag one process symbol for the business
process or system that is modeled (number 0
and name for the process or system) --> Level 0
DFD (5) :
Diagram
Context

[1, page196]
 Drag one process symbol for the business
process or system (without a number and name
for the process or system)
DFD (6) :
Diagram
Context

[2, hal 209]

DFD (6) :
Level n diagram
Example DFD
(1)
Contoh DFD
yang salah (2)
 ○ Re-check the system requirements what your team
will develop!
Team Session
○ Make a Use Case diagram and use case spesification
and DFD (Context Diagram (Level 0), Level 1, and
level 2) from the requirements what your team has
defined!
○ CASE Tools
○ Due date : Thursday, March 28 2019 at 11:59 pm
○ Send by schoology and print
○ format:
PSI_TASK2_NIMrepresentativegrup_UseCase+DFD
 1 Dennis, Alan., Barbara Halley Wixom and
Roberta M. Roth. 2012. System Analysis and
Design 5 th Edition. John Willey and Sons, Inc.
New Jersey
Referensi
2 Satzinger, John., Robert Jackson and Stephen
Burd. 2010. System Analysis and Design in
Changing World 5 th Edition. Cengange Learning.
Boston.