Kelompok Enam

Modeling System
Requirements with
Use Case
Imam Lutfi Rahmatullah
Kahfi Del Vieri
 Agenda Style
Introduction to usecase modeling
01 Pengenalan Modeling Use Case

System concepts for usecase modeling

02 Konsep untuk membuat Use Case

The process of requirements use case modeling

03 Proses dalam membuat usecase Modeling

Use cases and project management

04 Usecase dalam pengembangan sebuah proyek
 Introduction to
Kahfi

usecase modeling
 One of the primary challenges is the ability
to elicit the correct and necessary system requirements
from the stakeholders and specify them in a manner
understandable to them so those requirements can be
verified and validated.

The hardest single part of building a software system is deciding pre

cisely what to build. No other part of the conceptual work is a difficu
lt as establishing the detailed technical requirements, including all t
he interfaces to people, to machines, and to other software systems.
No other work so cripples the resulting system if done wrong. No oth
er part is more difficult to rectify later.
An Introduction to
Fred Brooks Use-Case Modeling
IT Development Project
Track Record
Project Success Rate

Succeeded
Project that complete on time and done
very well

Challenged
Over budget, late, or without needed
features

Failed

Project that canceled before completion

User-centered development Use-case modeling
a process of systems the process of modeling a
development based on system’s functions in terms of
understanding the needs of the business events, who initiated
stakeholders and the reasons the events, and how the system
why the system should be responds to those events.
developed. • Use-case modeling has roots
in object-oriented modeling.
• Gaining popularity in non-
object development
environments because of its
usefulness in communicating User-Centered
with users.
• Compliments traditional Development and
modeling tools.
Use-Case Modeling
 Kahfi

System concepts for

usecase modeling
Example of Use-Case Diagram
Benefits of Use-Case Modeling
Provides means of
Provides means of identifying,
communicating with
assigning, tracking, controlling,
users/stakeholders concerning
and management system
system functionality in language
development activities.
they understand.

Provides aid in estimating project

Assists in decomposing system
scope, effort, and schedule.
into manageable pieces.

Provides tool for capturing

Many more…
functional requirements.
 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 Use-case narrative
a diagram that depicts the a textual description of the
interactions between the system business event and how the
and external systems and users. user will interact with the system
• graphically describes who to accomplish the task.
will use the system and in
what ways the user expects
to interact with the system.

System Concepts for

Use-Case Modeling
Sample of Use-Case Narrative
Basic Use-Case Symbols

Use case Actor

subset of the overall system anyone or anything that needs
functionality to interact with the system to
• Represented by a exchange information.
horizontal ellipse with • human, organization,
name another information system,
of use case above, external device, even time.
below, or inside the
ellipse.

Temporal event

Use Case Symbol a system event triggered by time.

• The actor is time.
Four Types of Actors
Primary business actor
• The stakeholder that primarily benefits from the
execution of the use case.
• e.g. the employee receiving the paycheck

Primary system actor

• The stakeholder that directly interfaces with the system
to initiate or trigger the business or system event.
• e.g. the bank teller entering deposit information

External server actor

• The stakeholder that responds to a request from the use
case.
• e.g. the credit bureau authorizing a credit card charge

External receiver actor

• The stakeholder that is not the primary actor but receives
something of value from the use case.
• e.g. the warehouse receiving a packing slip
Use Case Association Relationship
Association
a relationship between an actor and a use case in which an interaction
occurs between them.
• Association modeled as a solid line connecting the actor and the use
case.
• Association with an arrowhead touching the use case indicates that
the use case was initiated by the actor. (1)
• Association lacking arrowhead indicates a receiver actor. (2)
• Associations may be bidirectional or unidirectional.
Use Case Extends Relationship
Extension use case
use case consisting of steps extracted from another use case to sim
plify the original.
• Extends the functionality of the original use case.
• Generally not identified in the requirements phase
• Extends relationship represented as arrow beginning at the e
xtension use case and pointing to use case it is extending.
• Labeled <<extends>>.
Use Case Uses Relationship

Abstract use case

use case that reduces redundancy in two or more other use ca
ses by combining common steps found in both.
• Available by any other use case that requires its functio
nality.
• Generally not identified in requirements phase
• Relationship between abstract use case and use case t
hat uses it is called a uses (or includes) relationship.
• Depicted as arrow beginning at original use case and p
ointing to use case it is using.
• Labeled <<uses>>.
Use Case Depends On Relationship

Depends On
use case consisting of steps extracted from another use case
to simplify the original.
• Can help determine sequence in which use cases nee
d to be developed.
• Depicted as arrow beginning at one use case and poin
ting to use case it depends on.
• Labeled <<depends on>>.
Use Case Inheritance Relationship

Inheritance
a use case relationship in which the common
behavior of two actors initiating the same use
case is extrapolated and assigned to a new
abstract actor to reduce redundancy.
• Other actors can inherit the interactions
of the abstract actor.
• Depicted as an arrow beginning at one
actor and pointing to the abstract actor
whose interactions the first actor inherit
s.
 The process of
requirements use case
Imam modeling
Tujuannya adalah untuk memperoleh dan
menganalisis informasi persyaratan yang cukup
untuk menyiapkan model yang:
• Mengkomunikasikan apa yang diperlukan dari
perspektif pengguna.
• Bebas dari rincian spesifik tentang bagaimana
sistem akan diterapkan.

Untuk memperkirakan dan menjadwalkan

proyek secara efektif.
The Process of Requirements
Use-Case Modeling
Apa itu???
Steps
Process Modeling

Documents
Identify business Identify business Construct use-case business
actors. use cases. model diagram. requirements use-
case narratives.

Mendokumentasikan
business
Mengidentifikasikan Mengidentifikasi use
Membuat UCD requirements ke
aktor case
sebuah narasi use
case
STEP 1
Identify Business Actors

• Ketika kita memikirkan aktor, kita harus

QUESTION
menanyakan hal ini :
• Siapa atau apa yang menyediakan input ke sistem?
• Siapa atau apa yang menerima output dari sistem?
• Apakah interface
Aktor harus dibutuhkan
dinamai ke sistem
dengan kata bendayang
ataulain?
• Apakah ada
frasa kata peristiwa yang dipicu secara otomatis
benda
pada waktu yang telah ditentukan?
• Siapa yang akan menyimpan informasi dalam
sistem?
Sample List of Actors
STEP 2
Identify Business Requirements Use Cases

Business Requirements Use Case – adalah

sebuah use case yang dibuat selama analisis
persyaratan (requirement analysis) untuk
menangkap interaksi antara pengguna dan sistem
tanpa rincian teknologi dan implementasi.

 Selama analisis persyaratan, berusahalah

untuk mengidentifikasi dan
mendokumentasikan hanya use case yang
paling critical, kompleks, dan penting, sering
disebut use case esensial.
STEP 2 (lanjutan 1)
Identify Business Use Case

• Ketika kita membuat use case, kita harus

QUESTION
• menanyakan hal ini
Apa tugas utama :
aktor?
• Apa informasi yang dibutuhkan aktor dari sistem?
• Apa informasi yang aktor berikan kepada sistem?
•• Use case
Apakah harusperlu
sistem diberimemberi
nama dengan kataaktor
tahu pada kerja jika
yang menjelaskan
ada perubahan ataugoal dari si (event)
kejadian aktor. yang terjadi?
• Contohnya
Apakah aktor: Kirim
perlu Pesanan Berlangganan
untuk memberi informasi
kepada sistem tentang perubahan atau kejadian
(event) yang terjadi?
Sample Context Diagram
Sample Use-Case Glossary
Sample Use-Case Glossary (1)
Sample Use-Case Glossary (2)
STEP 3
Construct Use-Case Model Diagram
Contoh UCD
UCD = Use Case Diagram
STEP 4 (LAST)
Document Business Requirements Use-Case Narratives

• Dokumentasikan dulu pada level tinggi untuk

dengan cepat mendapatkan pemahaman
tentang peristiwa dan besarnya sistem.

• Kemudian perluas narasi persyaratan bisnis

(business requirement) yang terdokumentasi
lengkap.
UCD LEVELS
Sample High-Level Version
of a Use-Case Narrative
Sample High-Level Version
of a Use-Case Narrative
Sample High-Level Version
of a Use-Case Narrative
Sample High-Level Version
of a Use-Case Narrative
Use cases and project
Imam management
Permodelan Use Case dapat mendorong
seluruh upaya development.

Projek Manager atau System Analyst

menggunakan persyaratan bisnis menggunakan
Use Case untuk memperkirakan dan
menjadwalkan siklus pembuatan proyek.

Untuk menentukan pentingnya Use Case, akan

dibuat:
• Use-case ranking and evaluation matrix Use Cases and Project
• Use-case dependency diagram Management
Apa itu???
 Use-case ranking and priority matrix
alat yang digunakan untuk mengevaluasi kasus penggunaan dan menentukan prioritasnya.

• Evaluasi use case pada skala 1-5 terhadap

enam kriteria.
1. Dampak signifikan pada desain arsitektur.
2. Mudah diimplementasikan tetapi
mengandung fungsionalitas yang signifikan.
3. Termasuk fungsi yang berisiko, kritis
terhadap waktu, atau kompleks.
4. Melibatkan penelitian signifikan atau
teknologi baru atau berisiko.
5. Termasuk fungsi bisnis utama.
6. Akan meningkatkan pendapatan atau
mengurangi biaya.
Sample Use-Case Ranking and Priority Matrix
 Use-case dependency diagram
penggambaran grafis dari ketergantungan antara use case.

• Memberikan manfaat berikut:

1. Penggambaran grafis peristiwa sistem dan
statusnya meningkatkan pemahaman
tentang fungsionalitas sistem.
2. Membantu mengidentifikasi use case yang
hilang.
3. Membantu memfasilitasi manajemen
proyek dengan menggambarkan kasus
penggunaan mana yang lebih kritis.
Sample Use-Case Dependency Diagram
Thank
you
For Your Attention