bab 6 use case diagram 2010

BAB VI USE CASE

Use Case Model

• Teknik pemodelan untuk mendapatkanfunctional requirement dari sebuah sistem

• Menggambarkan interaksi antara pengguna dan sistem• Menjelaskan secara naratif bagaimana sistem akan

digunakan• Menggunakan skenario untuk menjelaskan

setiap aktivitas yang mungkin terjadi• Kadangkala notasi kurang detail, terutama untuk

beberapa aktivitas tertentu

Kapan Menggunakan Use Case?• Use case sederhana digunakan pada saat

proses requirement analysis- Tidak semua pengguna paham bahasa teknis

• Versi yang lebih detail dibuat sebelumimplementasi rancangan

- Dibuat khusus untuk mempermudah desain sistem

oleh para developer

Skenario• Buy a product scenario

* The customer browses the catalog and adds

desired items to the shopping basket.* When the customer wishes to pay, the customer

describes the shipping and credit card information and confirms the sale

* The system checks the authorization on the credit card and confirms the sale both immediately andwith a follow-up e-mail

• Bagaimana jika proses pembayaranmenggunakan CC gagal atau konsumen lama yang tidak perlu merekam informasi CC?

Buat skenario baru

• Catatan: Proses pada skenario tidak selaluharus berhasil

�Kesimpulan:* USE CASE adalah sekumpulan skenario yang

dihubungkan satu sama lain dengan satutujuan yang sama dari pengguna

* Use Case berisi apa yang dilakukan oleh sistem / apa yang terjadi pada sistem, bukanbagaimana sistem melakukan

Level Use Case Model� Use Case memiliki dua istilah

* System use case : interaksi dengan sistem

* Business use case : interaksi bisnis dengankonsumen atau kejadian nyata

� Cookburn menyarankan adanya pembedaanlevel

* Sea level : interaksi sistem dengan aktor utama

* Fish level: use case yang ada karena include dari

use case sea-level

* Kite level : menggambarkan sea-level use case

untuk interaksi bisnis yang lebih luas

Use Case Mdl. Key Elements

�What actions or procedures exist within a system Use Case

� Who’s involved in those actions Actor� How those actions related to each other in

a system Relationship

Element: Use Case

�Aksi yang terdapat di dalam sistem, melingkupi semua aksi yang harusmaupun dapat terjadi

�Tidak harus berelasi dengan seorang/ sebuah aktor

�Pada umumnya berupa kata kerja

• Actor menggambarkan segala sesuatu yang berinteraksi dengan sistem untuk melakukan pertukaraninformasi. Actor adalah pengguna, pemeran (role), yang bisa berupa sistem eksternal maupun orang.

• Actor menginisiasi aktivitas sistem, dalam bentuk use case, bertujuan untuk melengkapi beberapa kegiatanbisnis.

• Actor menggambarkan peranan yang dilakukan olehuser yang berinteraksi dengan sistem dan bukanmenggambarkan individual jabatan pekerjaan.

SYSTEMS ANALYSYS AND DESIGN METHODS 5TH Edition Whitten Bentley Dittman

Irwin/McGraw-Hill Copyrighth@2000 The Mcgraw-Hill Companies All Right reserved

Element: Actor� Dalam notasi Use Case, pengguna sistem

disebut dengan Actor (role)� Actor bisa berupa manager, pimpinan,

mahasiswa, dan lain sebagainya* Actor tidak harus berupa manusia

* Jika sistem A mengerjakan sebuah fungsiuntuk sistem sistem B, maka sistem B disebut actor

� Satu use case diagram bisa memiliki banyakactor didalamnya

Use Case Models

USE CASE USE CASETEXT DIAGRAM

* lebih detail * lebih abstrakkurang detail

* tidak ada visualisasi * bentuk visual(berbentuk teks) (gambar)

* Cocok bagi * Cocok untukdeveloper berkomunikasi

dengan client

Use Case Text�Pilih salah satu skenario sebagai skenario

utama yang sukses�Tuliskan langkah-langkah untuk menyelesaikan

skenario tersebut

* Setiap langkah menampilkan tujuan dari sang actor

* Tidak perlu menuliskan bagian user interface

�Tulis skenario lain dan sebut sebagai extensions ,variasi dari skenario utama

* Extension bisa sukses atau gagal, tetapi interaksinya harus berbeda dengan skenario utama

* Extension bisa kembali ke skenario utama

1. Sebagai dasar untuk membantu mengidentifikasiobjek-objek dan hubungan tingkat tinggi dantanggung jawab masing-masing.

2. Sebagai gambaran dari behavior sistem yang akandibuat dari sisi pengguna eksternal.

3. Sebagai alat yang efektif untuk memvalidasikebutuhan.

4. Sebagai alat komunikasi yang efektif5. Sebagai dasar untuk melakukan perencanaan

testing.6. Sebagai dasar untuk melakukan pembuatan user

manual.



Keuntungan Use Case

1. Mengidentifikasi actor-actor tambahan dan use case-use case

2. Buatlah model Use Case3. Dokumentasikan kejadian-kejadian dalam Use

Case

4. Definisikan Analysis Use Cases



Langkah-langkah dalam membuat use case modeling



Step 1: Identifying Actors and Use CasesActorPotentialMemberClubMemberClubMemberClubMemberClubMemberClubMemberPastMemberMarketing

Marketing

Marketing

Time

Time

Time

Time

Time

Use Case NameSUBMIT NEWSUBSCRIPTIONPLACE NEW MEMBERORDERMAKE ACCOUNT INQUIRY

MAKE PURCHASE INQUIRY

MAINTAIN MEMBER ORDER

SUBMIT CHANGE OFADDRESSSUBMITRESUBSCRIPTIONSUBMIT NEW MEMBERSUBSCRIPTION PROGRAMSUBMIT PAST MEMBERRESUBSCRIPTIONPROGRAMSUBMIT NEW PROMOTION

GENERATE QUARTERLYPROMOTION ANALYSISGENERATE QUARTERLYSALES ANALYSISGENERATE QUARTERLYMEMBERSHIP ANALYSISGENERATE ANNUAL SALESANALYSISGENERATE ANNUALMEMBERSHIP ANALYSIS

Use Case DescriptionPotential member joins the club by subscribing. (“Take anu 12 CDs for one penny and agree to buy 4 more at regular club prices within two years.”)Club member places order.

Club member wants to examine his or her account history.(90-day time limit)Club member inquires about his/her purchase history.(three-year time limit)Club member wants to revise an order or cancel an order.

Club member changes address.(including e-mail and privacy code)Past member rejoins the club by resubscribing.

Marketing establishes a new membership resubscription plan to entice new members.Marketing establishes a new membership resubscription plan to lure back former members.

Marketing initiates a promotion.(Note: A promotion features specific titles, usually new, that company is trying to sell at a special price. These promotions are integrated into a catalog sent (or communicated) to all members.)Print quarterly promotion analysis report.

Print annual sales analysis report.

Print annual membership analysis report.

Print annual sales analysis report.

Print annual membership analysis report.



Step 2: Constructing a Use Case Model Diagram

Operations Subsystem

Order Subsystem

Promotion Subsystem

Subscription Subsystem

Submit PastMember

ResubscriptionProgram

Time Marketing

Past Member

Club Member

Potential Member

Generate AnnualSales Analysis

Generate AnnualMembership

Analysis

Generate QuarterlyMembership

Analysis

Generate QuarterlySales Analysis

Generate QuarterlyPromotion Analysis

Submit NewPromotion

Submit NewMember

SubscriptionProgram

SubmitResubscription

Submit Change ofAddress

Maintain MemberOrder

Make PurchaseInquiry

Make AccountInquiry

Place NewMember Order

Submit NewSubscription initiates

initiates

initiatesinitiates

initiatesinitiates

initiatesinitiates

initiates

initiates

initiates

initiates

initiates

initiates

initiates



Step 3: Documenting the Use Case Typical CourseAuthor: S. Shepard Date: 10/05/2000

Use Case Name: Submit New Member OrderActor(s): MemberDescription: This use case describes the process of a member submitting an order for

SoundStage products. On completion, the member will be sent a notification thatthe order was accepted.

References: MSS-1.0Typical Courseof Events: Actor Action

Step 1: This use case isinitiated when a member submits an order to beprocessed

Step 7: This use case concludes when the member receives the order confirmation notice.

System responseStep 2: The member’s personal information such as

address is validated against what is currently recorded in member services.

Step 3: The member’s credit status is checked with Accounts Receivable to make sure no payments are outstanding.

Step 4: For each product being ordered, validate the product number and then check the availability in inventory and record the ordered product information.

Step 5: Create a picking ticket for the member order containing all ordered products that are available and route it to the warehouse for processing.

Step 6: Generate an order confirmation notice indicating the status of the order and send it to the member.

1

2



Step 3: Documenting the Use Case Typical Course (concluded)

Alternate Step 2: If the club member has indicated an address or telephone number change on theCourses: promotion order, update the club member’s record with the new information.

Step 3: If Accounts Receivable returns a credit status that the customer is in arrears, send anorder rejection notice to the member.

Step 4: If the product number is not valid, send a notification to the member requesting them tosubmit a valid product number. If the product being ordered is not available, record theordered product information and mark as “back-ordered.”

Pre-condition: Orders can only be submitted by members.

Post-condition: Member order has been recorded and the picking ticket has been routed to the warehouse.

Assumptions: None at this time.



Extension and Abstract Use Cases

• An extension use caseextends the functionality (typical course) of an original use case. An extension use case can only be invoked by the use case it is extending.

• An abstract use case contains typical course steps that were common to two or more original use cases. An abstract use case reduces redundancy and promotes reuse.



Generate WarehousePacking Order

Calculate Order Subtotal &Sales Tax

Place NewMember Order

Revise StreetAddress

Submit Change of Address

Extension usecase Extension use

case

Abstract usecase

Depicting Extension and Abstract Use Cases using UML Notation



Step 4: Defining the Analysis Use Case

System Response

Step 2: The member’s personal information such as address and phone number is validated against what is currently on file.Step 3: For each product being ordered, validate the product number.Step 4: For each product being ordered, check the availability in inventory and record the ordered product information such as the quantity being ordered.Step 5: Invoke extension use case Calculate Order Subtotal & Sales Tax.Step 6: The member’s credit card information is verified based on the amount due and Accounts Receivable transaction data is checked to make sure no payments are outstanding.Step 7: Invoke extension use case Generate Warehouse Packing Order.Step 8: Generate an order confirmation notice indicating the status of the order and send it to the member.

(continued)

USE CASE NAME:ACTOR(S):DESCRIPTION:

REFERENCESTYPICAL COURSE OF EVENTS:

Author: S. Shepherd Date: 10/25/2000ANALYSIS USE CASE

Place New Member OrderClub MemberThis use case describes the process of a club member submitting a new order for SoundStage products. On completion, the club member will be sent a notification that the order was accepted.MSS-1.0

Actor Action

Step 1: This use case is initiated when a member submits an order to be processed.




Step 4: Defining the Analysis Use Case (concluded)

ALTERNATECOURSES:

PRECONDITION:

POSTCONDITION:

ASSUMPTIONS:

Step 2: If the club member has indicated an address or telephone number change on the order, invoke abstract use case Revise Street Address.Step 3: If the product number is not valid, send a notification to the member requesting the member to submit a valid product number.Step 4: If the product being ordered is not available, record the ordered product information and mark the order as “backordered.”Step 6: If member’s credit card information is invalid or if member is found to be in arrears, a credit problem notice is sent to the member. Modify the order’s status to be “on hold pending payment.”

Orders can only be submitted by members.

Member order has been recorded and the Packing Order has been routed to the Warehouse.

None at this time.



Finding and Identifying Business Objects

• Step 1: Find the Potential Objects– Underlining (or highlighting) the use case nouns

• Step 2: Select the Proposed Objects

– Removing the nouns that represent:• Synonyms

• Nouns outside the scope of the system

• Nouns that are roles without unique behavior or are external roles

• Unclear nouns that need focus

• Nouns that are really actions or attributes



Use Case with Nouns Highlighted

USE CASE NAME:ACTOR(S):DESCRIPTION:

REFERENCESTYPICAL COURSE OF EVENTS:

Author: S. Shepherd Date: 10/25/2000ANALYSIS USE CASE

Place New Member OrderClub MemberThis use case describes the process of a club member submitting a new order for SoundStage products. On completion, the club member will be sent a notification that the order was accepted.MSS-1.0

Actor Action

Step 1: This use case is initiated when a member submits an order to be processed.


System Response

Step 2: The member’s personal information such as address and phone number is validated against what is currently on file.Step 3: For each product being ordered, validate the product number.Step 4: For each product being ordered, check the availability in inventory and record the ordered product information such as the quantity being ordered.Step 5: Invoke extension use case Calculate Order Subtotal & Sales Tax.Step 6: The member’s credit card information is verified based on the amount due and Accounts Receivable transaction data is checked to make sure no payments are outstanding.Step 7: Invoke extension use case Generate Warehouse Packing Order.Step 8: Generate an order confirmation notice indicating the status of the order and send it to the member.

(continued)



Use Case with Nouns Highlighted (concluded)

ALTERNATECOURSES:

PRECONDITION:

POSTCONDITION:

ASSUMPTIONS:

Step 2: If the club member has indicated an address or telephone number change on the order, invoke abstract use case Revise Street Address.Step 3: If the product number is not valid, send a notification to the member requesting the member to submit a valid product number.Step 4: If the product being ordered is not available, record the ordered product information and mark the order as “backordered.”Step 6: If member’s credit card information is invalid or if member is found to be in arrears, a credit problem notice is sent to the member. Modify the order’s status to be “on hold pending payment.”

Orders can only be submitted by members.

Member order has been recorded and the Packing Order has been routed to the Warehouse.

None at this time.



Potential Objects Extracted from Use CasePOTENTIAL OBJECT LISTAccounts Receivable DepartmentAmount DueClub MemberCredit Card InformationCredit Problem NoticeCredit StatusFileMarketing DepartmentMember AddressMember OrderMember Phone NumberMember Services DepartmentMember Services SystemOrderOrder Confirmation NoticeOrder Sales TaxOrder StatusOrder SubtotalOrdered ProductOrdered Product InformationOrdered Product QuantityPast MemberPaymentsPotential MemberProductProduct InventoryProduct NumberStreet AddressTransactionWarehouseWarehouse Packing Order



Analysis of the Potential Objects

POTENTIAL OBJECT LISTAccounts Receivable DepartmentAmount DueClub MemberCredit Card InformationCredit Problem NoticeCredit StatusFileMarketing DepartmentMember AddressMember OrderMember Phone NumberMember Services DepartmentMember Services SystemOrderOrder Confirmation NoticeOrder Sales TaxOrder StatusOrder SubtotalOrdered ProductOrdered Product InformationOrdered Product QuantityPast MemberPaymentsPotential MemberProductProduct InventoryProduct NumberStreet AddressTransactionWarehouseWarehouse Packing Order

Not relevant for current projectAttribute of “MEMBER ORDER”Type of “MEMBER”Attribute of “MEMBER”Potential Interface item to be addressed in object-oriented design Attribute of “MEMBER”Not relevant for current projectNot relevant for current projectAttribute of “MEMBER”“MEMBER ORDER”Attribute of “MEMBER”Not relevant for current projectNot relevant for current projectAnother name for “MEMBER ORDER”Potential Interface item to be addressed in object-oriented design Attribute of “MEMBER ORDER”Attribute of “MEMBER ORDER”Attribute of “MEMBER ORDER”“MEMBER ORDERED PRODUCT”Unclear nounAttribute of “MEMBER ORDERED PRODUCT”Type of “MEMBER”Type of “TRANSACTION”Type of “MEMBER”“PRODUCT”Attribute of “PRODUCT”Attribute of “PRODUCT”Attribute of “MEMBER”“TRANSACTION”Not relevant for current projectPotential Interface item to be addressed in object-oriented design

REASONxx

xxxxxx

xxxxxxxx

xx

xxx

xx

/

////

/

/

/

• Sebuah use case menjelaskan interaksi antara user dengan sistem aplikasi.

• Sebagai contoh dalam sebuah sistem reservasipeminjaman mobil (rent a car), sebuah use case harusdapat menjelaskan apa yang user lakukan dengansistem aplikasi dalam sebuah kejadian/event bisnisdalam sebuah proses bisnis. Misalnya reservasi sebuahmobil Ferrari untuk Pak Agus.

• Sebuah proses dapat dibagi menjadi beberapa use casejika dapat diketahui dengan jelas tiap-tiap kejadiannyaatau jika bagian-bagian yang diidentifikasi tersebutdikerjakan oleh orang-orang yang berbeda.

• Jika diasumsikan sistem yang akan di analisa adalahSistem Informasi Peminjaman Mobil (Rent a car) makaorang yang akan kita temui adalah:

Developing Software Woth UML Booch Jacobson Rumbaugh

Addison-Wesley

• Customer service (central telephone operator)– Information– Reservation

• Customer service (branch office)– Vehicle hand-over– Vehicle return

• Service personnel (branch office, vehicle clerk)• Branch office management• Phone service management• Managing clerks, vehicle transfer staff,

accounting staff (jika diperlukan)


Addison-Wesley

Objek-objek yang disebutkan diatas harus dapatdiidentifikasi dan diberi nama.

Sebagai contoh objek-objek tersebut adalah:• Data customer• Kontrak• Invoice• Konfirmasi reservasi• Aturan pengembalian mobil• Aturan pemarkiran• Dokumentasi kendaraan


Addison-Wesley

• Aksesories yang ada dalam mobil• Fixed accessories (AC, tape, sun roof)• Kunci-kunci kendaraan• File-file customer• Alokasi / lot tempat parkir• Contract condition / aturan kontrak• Dsb.


Addison-Wesley

• Gambar use case dari kasus diatas dapat dilihat padagambar di bawah ini. Disini actor-nya adalah interested party yaitu customer, dan staff untuk reservasi (staff for reservation), penyerahan mobil yang akan dipinjam(vehicle hand-over) dan pengembalian mobil (vehicle return)

• Interested party (Calon customer) berbeda denganCustomer, karena calon customer biasanya belum adadatanya (anonymous), karena data mereka belumterdaftar

Identifikasi use case dan actorDeveloping Software Woth UML Booch Jacobson Rumbaugh

Addison-Wesley

Car Rental Agency

Interested Party

Customer

Driver

Customer

Advise, giveinformation

Reservation Staff

Hand-over staff

Return Staff

reserve

Stipulate contract

Take back vehicle

Handover vehicle

Invoice

<<include>>


Addison-Wesley

Dalam bisnis use case, actor adalah semua peran(role) yang terlibat dalam proses bisnis, sedangkandalam system use case, mereka dibatasi hanyakepada mereka yang mempunyai kontak langsungdengan sistem aplikasi. Biasanya customer tidakmemiliki akses langsung dengan sistem aplikasi, tetapi dalam bisnis use case mereka tetap dicatat. Jika customer dapat melakukan reservasi melaluiself-service terminal atau melalui internet, merekaberinteraksi langsung dengan sistem aplikasi danoleh karena itu mereka harus digambarkan dalamsystem use case.

Business use case dan System use case


Addison-Wesley

Jika use case car rental agency diatas dikelompokkan, bentuknya :

Interested party

Customer

Driver

Customer

Reservation

Vehiclehand-over

Vehiclereturn

Reservation

Advise,give information

Reserve

<<include>>

Rental

Stipulatecontract

Hand overvehicle

Acceptreturn vehicle

Invoicing

Invoice


Addison-Wesley

• Menggambarkan use case dalam bentukdiagram elips adalah langkah pertama, setelahitu yang berikutnya adalah menjelaskannyadalam bentuk lebih detil lagi.

• Penjelasan detil dari use case adalah tujuanutama dari use case analysis untuk itu ada duacontoh yang menggambarkan use case lebihdetil.

Menggunakan use caseDeveloping Software Woth UML Booch Jacobson Rumbaugh

Addison-Wesley

bab 6 use case diagram 2010

Education