UML based Software

Analysis and Design

UML based Software Analysis and Design
(Sparx Systems EA)

1. Display the boundary of a system and its

major functions using use cases and actors
2. Model the organization’s business process
with activity diagram
3. Illustrate use case realizations with sequence
diagrams
4. Represent a static structure of a system using
class diagrams
5. Reveal the physical implementation
architecture with deployment diagrams
2
UML based Software Analysis and Design (Kendal, 2011)
1. A use case diagram, describing how the system is used.
Analysts start with a use case diagram
2. An activity diagram, illustrating the overall flow of
activities. Each use case may create one activity
diagram
3. Sequence diagrams, showing the sequence of activities
and class relationships. Each use case may create one
or more sequence diagrams
4. Class diagrams, showing the classes and relationships.
Sequence diagrams are used to determine classes
5. Statechart diagrams, showing the state transitions. Each
class may create a statechart diagram, which is useful
for determining class methods
3
 (Kendall and Kendall, 2011)
4
UML based Software Analysis and Design
(Barclay, 2004)

5
UML based Software Analysis and Design
(Wahono, 2009)

1. Systems
2. Systems Design
Analysis
1.1 Identifikasi Proses Bisnis 2.1 Pemodelan Class Diagram
dengan Use Case Diagram
2.2 Pemodelan User Interface
1.2 Pemodelan Proses Bisnis Design
dengan Activity Diagram
atau BPMN
2.3 Pemodelan Data Model
1.3 Realisasi Proses Bisnis
dengan Sequence Diagram 2.4 Pemodelan Deployment
(Boundary - Control - Entity) Diagram

6
7
Studi Kasus: ATM System

8
ATM System

Layar

Kotak Uang Kotak Kartu

Kotak Kuitansi

9
Menu PIN

Masukkan PIN:

Kotak Uang Kotak Kartu

Kotak Kuitansi

10
Menu Utama
1. Mengecek Saldo
2. Mentransfer Uang
3. Mengambil Uang
4. Logout

Kotak Uang Kotak Kartu

Kotak Kuitansi

11
Menu Pengecekan Saldo

1. Saldo anda adalah …

Kotak Uang Kotak Kartu

Kotak Kuitansi

12
Menu Pengiriman Uang

1. No Account Penerima:

Kotak Uang Kotak Kartu

Kotak Kuitansi

13
Menu Pengiriman Uang

1. Jumlah uang yang dikirim:

Kotak Uang Kotak Kartu

Kotak Kuitansi

14
Menu Pengiriman Uang

1. Uang berhasil terkirim

Kotak Uang Kotak Kartu

Kotak Kuitansi

15
Menu Pengambilan Uang

1. Jumlah uang yang diambil:

Kotak Uang Kotak Kartu

Kotak Kuitansi

16
Menu Pengambilan Uang

Uang berhasil diambil

Kotak Uang Kotak Kartu

Kotak Kuitansi

17
2.2 Identifikasi Proses Bisnis dengan Use Case
Diagram

18
UML based Software Analysis and Design
(Wahono, 2009)

1. Systems
2. Systems Design
Analysis
1.1 Identifikasi Proses Bisnis 2.1 Pemodelan Class Diagram
dengan Use Case Diagram
2.2 Pemodelan User Interface
1.2 Pemodelan Proses Bisnis Design
dengan Activity Diagram
atau BPMN
2.3 Pemodelan Data Model
1.3 Realisasi Proses Bisnis
dengan Sequence Diagram 2.4 Pemodelan Deployment
(Boundary - Control - Entity) Diagram

19
Use Case Diagram

• Summarized into a single picture

• All of the use cases for the part of the system
being modeled
• Use case represents the discrete activities
performed by the user
• Use Case Diagram tells what the system will do
• Good for communicating with users

20
Use Case Diagram Syntax
• Actor
• person or system that derives benefit
from and is external to the subject
• Use Case
• Represents a major piece of system
functionality
• Association Relationship
• Include Relationship <<includes>>

• Extend Relationship <<extends>>

• Generalization Relationship

21
Use Case
• A major piece of
system functionality
• Can extend other Use Case
Use Cases
• Placed inside system boundary
• Labeled with descriptive
verb - noun phrase

22
System Boundary
• Includes the name
of the system Boundary
inside or on top
• Represents the
scope of the system
• Actors are outside the scope of the system

23
Actor
• A person or another
system that interacts
with the current system
• A role, not a specific user
• Provides input, actor
receives output, or both Actor/Role

24
Association Relationship

• Links actor and the Use Case

• Shows two-way communication
• If one-way, arrows are used

25
Extends Relationship
• Extends Use Case to include Optional
behavior
• Arrow points from the extension Use Case to
the base Use Case

extend

Make Payment extend Make

Arrangement Appointment

26
Include Relationship
• Include one Use Case from within another
• Arrow points from base Use Case to the
included Use Case

include

Make New include Create New

Patient Appointment Patient

27
Generalization Relationship

• A specialized Use Case to a more

generalized Use Case
• Arrow points from specialized to
general Use Case

Make Old Make

Appointment Appointment

28
Use Case Diagram for Appointment System

29
Use Case Diagram with Specialized Actor

30
Extend and Include Relationships

31
Sistem Konsultasi Dokter Rumah Sakit
uc UCD Appointment System

Sistem Konsultasi Dokter Rumah Sakit

Membuat Janj ian Mengatur Cara

Konsultasi «extend» Pembayaran

Membuat Janj ian Membuat Janj ian

Konsultasi untuk Konsultasi untuk Melakukan
Pasien Lama Pasien Baru Persetuj uan Janj ian
Konsultasi
Peraw at
Pasien Lama
«extend» «include»

Mengupdate Data
Membuat Kartu Pasien
Pasien Lama

Menginput Hari dan

Pasien Jam Praktek
Dokter

«include»

Mengelola Jadw al
Praktek Mempublikasikan
«include» Jadw al Praktek

Administrator

Pasien Baru
32
Studi Kasus: Use Case Diagram Sistem
ATM

33
Use Case Diagram Sistem ATM
(versi Sederhana)

uc UCD Sistem ATM Sederhana

Sistem ATM

Memasukan PIN

Mengecek Saldo

Nasabah Mengirim Uang

Mengambil Uang

Melakukan Logout

34
Use Case Diagram Sistem ATM
(Versi Include dan Extends)
uc UCD Sistem ATM Kompleks

Sistem ATM

Memasukan Kartu Memasukan PIN

«include»

Mengupdate Informasi
Kotak Deposit

Mengecek Saldo
Petugas

«extend»

Nasabah Melakukan Transaksi

Perbankan
«extend» Mengambil Uang

Sistem Core Banking

«extend»

Melakukan Logout
Mengirim Uang

35
Use Case Diagram ERP Perbankan
(Sistem Lebih Kompleks)

uc ERP Perbankan

ERP Perbakan

ATM Module Human Resource Module

+ Nasabah + Kepala Divisi

+ Mengambil Uang + Staff
+ Mengecek Saldo + Melakukan Persetujuan Cuti
+ Mengirim Uang + Menganalisis Beban Kerja

Finance Module Proj ect Management Module

uc ATM Module

ATM Module

Mengecek Saldo

Mengirim Uang

Nasabah
Mengambil Uang

36
Use Case Diagram Sistem ATM
(Versi Normal)

uc UCD Sistem ATM

Sistem ATM

Memasukan Kartu Memasukan PIN

«include»

Mengecek Saldo
Mengupdate Informasi
Kotak Deposit
Petugas

Nasabah

Mengambil Uang

Sistem Inti Perbankan

Mengirim Uang

Keluar Sistem

37
38
39
40
41
42
43
44
Contoh Use Case Diagram MusicPedia

45
Use Case Diagram MusicPedia
• Contoh lain:
https://www.uml-diagrams.org/use-case-diagrams-examples.html

46
Exercise: Business Process Identification
1. Buat project baru di Sparx EA, dengan
nama file adalah nama project sesuai
System Request
2. Lihat kembali dan rapikan System Request
yang sudah anda buat
3. Lakukan business process identification
dengan membuatkan Use Case Diagram
untuk System Request tersebut

47
 Exercise: Systems Analysis and Design
• Pilih salah satu aplikasi di bawah (boleh yang lain):

1. Aplikasi Rental Mobil 7. Aplikasi Penjualan Buku Online

2. Aplikasi Pengelolaan Klinik 8. Aplikasi Penjualan Tiket Kereta Online
3. Aplikasi Pengelolaan Apotik 9. Aplikasi Manajemen Universitas Online
4. Aplikasi Pengelolaan Service Mobil 10. Aplikasi Penjualan Laptop Online
5. Aplikasi Penjualan Motor 11. Aplikasi Perpustakaan Digital
6. Aplikasi Pengelolaan Perpustakaan 12. Aplikasi Pengelolaan Project Software

48