from bm to reqspec - use case

8/11/2019 From BM to ReqSpec - Use Case

1/43

Business Modelingand Requirements

Perancangan Sistem InformasiMTI 2014

Overview


2/43

Tujuan :

Memahami peran software terhadapproses bisnis customers.

Mengumpulkan permasalahan dansolusi yang bisa ditawarkan dengan IT.

Menentukan fitur apa saja yang adadalam sistem.

Menuangkan features ke dalamkebutuhan fungsional dan non-fungsional sistem.


3/43

The Problem Domain

Users +other Stakeholders

Stakeholders: anyone who could be

materially affected by the

implementation of a new system or

application.

Challenge: understandthe problem to be solved

Needs


4/43

Moving Toward the Solution Domain 1

Needs ProblemDomain

Features: a service that the system

provides to fulfill one or more stakeholderneeds.

FEATURES

The system will prevent intruders

The system will have automatic backupWeb-enabled entry for sales orders

Examples:


5/43

Moving Toward the Solution Domain 2

Needs ProblemDomain

FEATURES

Software

Requirements

Solution

Domain

FunctionalNon-Functional Use CaseURPS+


6/43

Problem/Solution Domains

Problem space

Stakeholder Request:Diperlukan mekanisme pelaporan yang

real time dan komprehensif tentang data statistik pasien.

Solution space

FEATURES:

Sistem mampu mendeteksi kekurangan obat yang dalam waktu

dekat akan habis/kedaluwarsa Sistem mampu menampilkan data rekam medis pasien yang

paling up to date

Sistem mampu menyajikan laporan tingkat hunian dan data

statistik pasien dan alokasi dokter unit layanan

RUMAH SAKIT


7/43

Problem/Solution Domains

Solution space

USE CASE:

- Mengupdate data rekam medis pasien

- Melihat informasi ketersediaan layanan RS- Melihat informasi ketersediaan kamar, dokter dan spesialist

- Melihat informasi tagihan

SUPPLEMENTARY:- Response time pelayanan informasi tidak lebih dari 1 menit

- Kompilasi data statistik real-time maximum 1 menit.


8/43

HOSPITAL

Unit Rekam Medis

Use Case Defines System Boundaries

RM

ApplicationPetugas RM

Petugas Medis

Pasien

Keluarga karyawan

Goal:Mengupdate data pasien

Goal:Memeriksa pasien

Goal:Berobat jalan

Goal:Menjalani rawat inap


9/43

Purpose of Business Modeling

To understand the structure and dynamics of

the organization.

To ensure that customers, end users, and

developers have a common understanding of

the organization.


10/43

Business Use Case Model

Business Actor

Enterprise

Business Use Case

Business UC: pelayanan apa saja yang disediakan oleh organisasi

bisnis bagi customers-nya.


11/43

Contoh: Business UC untuk

Sistem Informasi Rumah Sakit

PB Farmasi

Rumah SakitBerobat jalan

Memonitor Kinerja RS

Menjalani rawat inap

Melakukan check-upPasien

DepKes

MemonitorKetersediaan dan

Status Obat


12/43

Business Object Model (BOM)

Business Actor

Business Entity

Business Worker

Enterprise

BOM: interaksi antar komponen organisasi dalam rangka melayani

cutomers.


13/43

Contoh: BOM Berobat Jalan

Pasien

Rekam Medis

Petugas Reservasi

Rumah Sakit

Petugas Unit

Layanan

Bukti Berobat

Kasir


14/43

Activity Diagram Berobat Jalan


15/43

Activity

Diagram

OpenRegistration


16/43

Activity

Diagram

Make anOrder


17/43

Going from Business Models to

SystemsBusiness workers become the actors to the system.

Behaviors described for business workers are things that can

be automated.

Business entities are things we may want the

system to help us maintain entity class in

analysis model.


18/43

Contoh: System Use Case Model

Petugas RM Mengupdate Rekam Medis

Actor

System Application

Boundary Controller

Entity

Analysis & Design


19/43

POST system boundary

Melayani

transaksi

Log In

Melayani refund

POST

Cashier

Repository

System

Systems and their boundaries

Authorization

System


20/43

POST Checkout boundary

Buy Items

Refund Purchased

Items

POST Checkout

Customer

Systems and their boundaries

A ti it Di B b t J l


21/43

Activity Diagram Berobat Jalan


22/43


23/43

Activity

Diagrams(Optional)


24/43

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 Specif icat ion in ATM Sys tem


25/43

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. Thisstep 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 the use

case.

Use Case Specif icat ion in ATM Sys tem


26/43


27/43

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.


28/43

Use Case Specification

Actor Action System Response

If there is more than one of The description and price

the same item, the Cashier of the current item are

can enter the quantity as displayed.

well.

4.On completion of item entry, 5. Calculates and present the sale

the Cashier indicates to the total.

POST that item entry is complete.

6. The Cashier tells the Customer

the total

..


29/43

A Common Mistake

with Use Cases

A use case is a relatively large end-to-end process

description that typically includes many steps or

transactions; it is not normally an individual step or

activity in a process, e.g. printing the receipt

Identifying use cases differs from process/ function

decomposition


30/43

Naming Use Cases

Name a use case starting with a verb in order

to emphasize that it is a process.

Buy Items

Enter an Order

Maintain Customer Profiles


31/43


32/43

Include UC Relationship

Check Balance

Withdraw Money

Transfer Money

ATM

Clientlogin


33/43

Extend UC Relationship

Mengembalikan

Buku

Meminjam Buku

Sistem Informasi

Perpustakaan

PetugasMenagih Denda


34/43

UC Scenario


35/43

Notes on UC Specifications

1. A UC description must include how and when the use case begins andends. Also, consider the possibility of any looping behavior within theuse case.

2. Be specific when defining the activities of an actor. Avoid using adverbs(e.g. very, more, rather).

3. UC should not include technology considerations. Its not solely createdfor user interface specification. A UC should not contain any userinterface information (e.g. radio button, check box, drop-down menu).

4. Verify that all the functional requirements have been addressed in theuse case model. Scrutinize the specification carefully to ensure that allrequirements have been met by the various use cases.

Library Information System


36/43

Library Information System

Browse Catalog

Memesan Buku

Undergrad

Student

Meminjam Buku

Librarian

Memesan Copy

Meng-konfirmasi

Transaksi

Menambah Koleksi

Memperpanjang

Pinjaman

Postgrad

Student

Lecturer

Undergrads Point of View


37/43

Undergrad s Point of View

Browse Catalog

Memesan Buku

Undergrad

Student

Meminjam Buku

Librarian

Postgrad

Student

Lecturer

Postgrads Point of View


38/43

Postgrad s Point of View

Browse Catalog

Memesan Buku

Undergrad

Student

Meminjam Buku

Librarian

Memesan Copy

Postgrad

Student

Lecturer

Lecturers Point of View


39/43

Lecturer s Point of View

Browse Catalog

Memesan Buku

Undergrad

Student

Meminjam Buku

Librarian

Memesan Copy

Meng-konfirmasi

Transaksi

Memperpanjang

Pinjaman

Postgrad

Student

Lecturer

Librarians Point of View


40/43

Librarian s Point of View

Browse Catalog

Memesan Buku

Undergrad

Student

Meminjam Buku

Librarian

Memesan Copy

Meng-konfirmasi

Transaksi

Menambah Koleksi

Memperpanjang

Pinjaman

Postgrad

Student

Lecturer

UC - Library Information System


41/43

UC - Library Information System

Browse Catalog

Memesan Buku

Undergrad

Student

Meminjam Buku

Librarian

Memesan Copy

Meng-konfirmasi

Transaksi

Menambah Koleksi

Memperpanjang

Pinjaman

Postgrad

Student

Lecturer

UC - Library Information System (Revised)


42/43

UC - Library Information System (Revised)

Browse Catalog

Memesan BukuMember

Meminjam Buku

Librarian

Memesan Copy

Meng-konfirmasi

Pinjaman

Menambah Koleksi

Memperpanjang

Pinjaman

Postgrad

Lecturer

Meng-konfirmasi

Perpanjangan


43/43

Kerja kelompok:

Buat Business UC dan BOM untuk topik

masing-masing kelompok.

Buatlah System UC diagram untuk proses

bisnis yang menjadi topik.

from bm to reqspec - use case

Documents