Use case Pokok bahasan: Use case Identifikasi use case dan actor

Presentasi berjudul: "Use case Pokok bahasan: Use case Identifikasi use case dan actor"— Transcript presentasi:

1 Use case Pokok bahasan: Use case Identifikasi use case dan actor
Developing Software Woth UML Booch Jacobson Rumbaugh Use case Pokok bahasan: Use case Identifikasi use case dan actor Business use case dan system use case Menggunakan use case Addison-Wesley

2 Membuat model fungsi sistem
SYSTEMS ANALYSYS AND DESIGN METHODS 5TH Edition Whitten Bentley Dittman Membuat model fungsi sistem Use case modeling adalah suatu proses untuk membuat model fungsi-fungsi dari sistem dari kejadian-kejadian bisnis, siapa yang melakukannya, dan bagaimana sistem bereaksi terhadap suatu kejadian. Use case modeling mengidentifikasi dan menjelaskan fungsi-fungsi sistem dari perspektif pengguna eksternal dengan menggunakan tools yang disebut use case. Use case adalah serangkaian langkah-langkah yang saling berhubungan (skenario), baik otomatis maupun manual, dengan tujuan untuk menyelesaikan suatu kegiatan bisnis tunggal. Irwin/McGraw-Hill The Mcgraw-Hill Companies All Right reserved

3 SYSTEMS ANALYSYS AND DESIGN METHODS 5TH Edition
SYSTEMS ANALYSYS AND DESIGN METHODS 5TH Edition Whitten Bentley Dittman Use case menggambarkan fungsi-fungsi sistem dari perspektif pengguna luar. Use case adalah hasil dari dekomposisi lingkup fungsi-fungsi dari sistem menjadi statement-statement yang lebih kecil mengenai fungsional oleh fungsi-fungsi sistem. Pembuatan use case sudah dibuktikan merupakan suatu teknik yang baik untuk mengerti lebih baik dan mendokumentasi kebutuhan sistem. Use case sendiri bukan sebagai kebutuhan fungsional, tetapi ceritanya (skenario) yang diceritakan dari use case menangkap essensi dari satu atau lebih kebutuhan-kebutuhan. Use case diawali atau dipicu oleh pengguna eksternal atau sistem yang disebut actor. Irwin/McGraw-Hill The Mcgraw-Hill Companies All Right reserved

4 SYSTEMS ANALYSYS AND DESIGN METHODS 5TH Edition
SYSTEMS ANALYSYS AND DESIGN METHODS 5TH Edition Whitten Bentley Dittman Actor menggambarkan segala sesuatu yang berinteraksi dengan sistem untuk melakukan pertukaran informasi. Actor adalah pengguna, pemeran (role), yang bisa berupa sistem eksternal maupun orang. Actor menginisiasi aktivitas sistem, dalam bentuk use case, bertujuan untuk melengkapi beberapa kegiatan bisnis. Actor menggambarkan peranan yang dilakukan oleh user yang berinteraksi dengan sistem dan bukan menggambarkan individual jabatan pekerjaan. Irwin/McGraw-Hill The Mcgraw-Hill Companies All Right reserved

5 Sebagai alat yang efektif untuk memvalidasi kebutuhan.
SYSTEMS ANALYSYS AND DESIGN METHODS 5TH Edition Whitten Bentley Dittman Keuntungan Use Case Sebagai dasar untuk membantu mengidentifikasi objek-objek dan hubungan tingkat tinggi dan tanggung jawab masing-masing. Sebagai gambaran dari behavior sistem yang akan dibuat dari sisi pengguna eksternal. Sebagai alat yang efektif untuk memvalidasi kebutuhan. Sebagai alat komunikasi yang efektif Sebagai dasar untuk melakukan perencanaan testing. Sebagai dasar untuk melakukan pembuatan user manual. Irwin/McGraw-Hill The Mcgraw-Hill Companies All Right reserved

6 Langkah-langkah dalam membuat use case modeling
SYSTEMS ANALYSYS AND DESIGN METHODS 5TH Edition Whitten Bentley Dittman Langkah-langkah dalam membuat use case modeling Mengidentifikasi actor-actor tambahan dan use case-use case Buatlah model Use Case Dokumentasikan kejadian-kejadian dalam Use Case Definisikan Analysis Use Cases Irwin/McGraw-Hill The Mcgraw-Hill Companies All Right reserved

7 Step 1: Identifying Actors and Use Cases
SYSTEMS ANALYSYS AND DESIGN METHODS 5TH Edition Whitten Bentley Dittman Step 1: Identifying Actors and Use Cases Actor Potential Member Club Member Past Member Marketing Time Use Case Name SUBMIT NEW SUBSCRIPTION PLACE NEW MEMBER ORDER MAKE ACCOUNT INQUIRY MAKE PURCHASE INQUIRY MAINTAIN MEMBER ORDER SUBMIT CHANGE OF ADDRESS SUBMIT RESUBSCRIPTION SUBMIT NEW MEMBER SUBSCRIPTION PROGRAM SUBMIT PAST MEMBER RESUBSCRIPTION PROGRAM SUBMIT NEW PROMOTION GENERATE QUARTERLY PROMOTION ANALYSIS GENERATE QUARTERLY SALES ANALYSIS GENERATE QUARTERLY MEMBERSHIP ANALYSIS GENERATE ANNUAL SALES ANALYSIS GENERATE ANNUAL MEMBERSHIP ANALYSIS Use Case Description Potential 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 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. Irwin/McGraw-Hill The Mcgraw-Hill Companies All Right reserved

8 Step 2: Constructing a Use Case Model Diagram
SYSTEMS ANALYSYS AND DESIGN METHODS 5TH Edition Whitten Bentley Dittman Step 2: Constructing a Use Case Model Diagram Operations Subsystem Order Subsystem Promotion Subsystem Subscription Subsystem Submit Past Member Resubscription Program Time Marketing Past Member Club Member Potential Member Generate Annual Sales Analysis Membership Analysis Generate Quarterly Promotion Analysis Submit New Promotion Subscription Submit Submit Change of Address Maintain Member Order Make Purchase Inquiry Make Account Place New Member Order initiates Irwin/McGraw-Hill The Mcgraw-Hill Companies All Right reserved

9 Step 3: Documenting the Use Case Typical Course
SYSTEMS ANALYSYS AND DESIGN METHODS 5TH Edition Whitten Bentley Dittman Step 3: Documenting the Use Case Typical Course Author: S. Shepard Date: 10/05/200 Use Case Name: Submit New Member Order Actor(s): Member Description: This use case describes the process of a member submitting an order for SoundStage products. On completion, the member will be sent a notification that the order was accepted. References: MSS-1.0 Typical Course of Events: 1 System response Step 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. Actor Action Step 1: This use case is initiated when a member submits an order to be processed Step 7: This use case concludes when the member receives the order confirmation notice. 2 Irwin/McGraw-Hill The Mcgraw-Hill Companies All Right reserved

10 Step 3: Documenting the Use Case Typical Course (concluded)
SYSTEMS ANALYSYS AND DESIGN METHODS 5TH Edition Whitten Bentley Dittman 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 the Courses: 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 an order rejection notice to the member. Step 4: If the product number is not valid, send a notification to the member requesting them to submit a valid product number. If the product being ordered is not available, record the ordered 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. Irwin/McGraw-Hill The Mcgraw-Hill Companies All Right reserved

11 Extension and Abstract Use Cases
SYSTEMS ANALYSYS AND DESIGN METHODS 5TH Edition Whitten Bentley Dittman Extension and Abstract Use Cases An extension use case extends 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. Irwin/McGraw-Hill The Mcgraw-Hill Companies All Right reserved

12 Depicting Extension and Abstract Use Cases using UML Notation
SYSTEMS ANALYSYS AND DESIGN METHODS 5TH Edition Whitten Bentley Dittman Depicting Extension and Abstract Use Cases using UML Notation Generate Warehouse Packing Order Calculate Order Subtotal & Sales Tax Place New Member Order Revise Street Address Submit Change of Address Extension use case Abstract use Irwin/McGraw-Hill The Mcgraw-Hill Companies All Right reserved

13 Step 4: Defining the Analysis Use Case
SYSTEMS ANALYSYS AND DESIGN METHODS 5TH Edition Whitten Bentley Dittman 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: REFERENCES TYPICAL COURSE OF EVENTS: Author: S. Shepherd Date: 10/25/2000 ANALYSIS USE CASE Place New Member Order Club Member This 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 9: This use case concludes when the member receives the order confirmation notice. Irwin/McGraw-Hill The Mcgraw-Hill Companies All Right reserved

14 Step 4: Defining the Analysis Use Case (concluded)
SYSTEMS ANALYSYS AND DESIGN METHODS 5TH Edition Whitten Bentley Dittman Step 4: Defining the Analysis Use Case (concluded) ALTERNATE COURSES: 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. Irwin/McGraw-Hill The Mcgraw-Hill Companies All Right reserved

15 Finding and Identifying Business Objects
SYSTEMS ANALYSYS AND DESIGN METHODS 5TH Edition Whitten Bentley Dittman 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 Irwin/McGraw-Hill The Mcgraw-Hill Companies All Right reserved

16 Use Case with Nouns Highlighted
SYSTEMS ANALYSYS AND DESIGN METHODS 5TH Edition Whitten Bentley Dittman Use Case with Nouns Highlighted Author: S. Shepherd Date: 10/25/2000 ANALYSIS USE CASE USE CASE NAME: ACTOR(S): DESCRIPTION: REFERENCES TYPICAL COURSE OF EVENTS: Place New Member Order Club Member This 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 9: This use case concludes when the member receives the order confirmation notice. 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) Irwin/McGraw-Hill The Mcgraw-Hill Companies All Right reserved

17 Use Case with Nouns Highlighted (concluded)
SYSTEMS ANALYSYS AND DESIGN METHODS 5TH Edition Whitten Bentley Dittman Use Case with Nouns Highlighted (concluded) ALTERNATE COURSES: 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. Irwin/McGraw-Hill The Mcgraw-Hill Companies All Right reserved

18 Potential Objects Extracted from Use Case
SYSTEMS ANALYSYS AND DESIGN METHODS 5TH Edition Whitten Bentley Dittman Potential Objects Extracted from Use Case POTENTIAL OBJECT LIST Accounts Receivable Department Amount Due Club Member Credit Card Information Credit Problem Notice Credit Status File Marketing Department Member Address Member Order Member Phone Number Member Services Department Member Services System Order Order Confirmation Notice Order Sales Tax Order Status Order Subtotal Ordered Product Ordered Product Information Ordered Product Quantity Past Member Payments Potential Member Product Product Inventory Product Number Street Address Transaction Warehouse Warehouse Packing Order Irwin/McGraw-Hill The Mcgraw-Hill Companies All Right reserved

19 Analysis of the Potential Objects
SYSTEMS ANALYSYS AND DESIGN METHODS 5TH Edition Whitten Bentley Dittman Analysis of the Potential Objects POTENTIAL OBJECT LIST Accounts Receivable Department Amount Due Club Member Credit Card Information Credit Problem Notice Credit Status File Marketing Department Member Address Member Order Member Phone Number Member Services Department Member Services System Order Order Confirmation Notice Order Sales Tax Order Status Order Subtotal Ordered Product Ordered Product Information Ordered Product Quantity Past Member Payments Potential Member Product Product Inventory Product Number Street Address Transaction Warehouse Warehouse Packing Order Not relevant for current project Attribute of “MEMBER ORDER” Type of “MEMBER” Attribute of “MEMBER” Potential Interface item to be addressed in object-oriented design “MEMBER ORDER” Another name for “MEMBER ORDER” “MEMBER ORDERED PRODUCT” Unclear noun Attribute of “MEMBER ORDERED PRODUCT” Type of “TRANSACTION” “PRODUCT” Attribute of “PRODUCT” “TRANSACTION” REASON x / Irwin/McGraw-Hill The Mcgraw-Hill Companies All Right reserved

20 Developing Software Woth UML Booch Jacobson Rumbaugh
Sebuah use case menjelaskan interaksi antara user dengan sistem aplikasi. Sebagai contoh dalam sebuah sistem reservasi peminjaman mobil (rent a car), sebuah use case harus dapat menjelaskan apa yang user lakukan dengan sistem aplikasi dalam sebuah kejadian/event bisnis dalam sebuah proses bisnis. Misalnya reservasi sebuah mobil Ferrari untuk Pak Agus. Sebuah proses dapat dibagi menjadi beberapa use case jika dapat diketahui dengan jelas tiap-tiap kejadiannya atau jika bagian-bagian yang diidentifikasi tersebut dikerjakan oleh orang-orang yang berbeda. Jika diasumsikan sistem yang akan di analisa adalah Sistem Informasi Peminjaman Mobil (Rent a car) maka orang yang akan kita temui adalah: Addison-Wesley

21 Customer service (central telephone operator)
Developing Software Woth UML Booch Jacobson Rumbaugh 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

22 Sebagai contoh objek-objek tersebut adalah:
Developing Software Woth UML Booch Jacobson Rumbaugh Objek-objek yang disebutkan diatas harus dapat diidentifikasi dan diberi nama. Sebagai contoh objek-objek tersebut adalah: Data customer Kontrak Invoice Konfirmasi reservasi Aturan pengembalian mobil Aturan pemarkiran Dokumentasi kendaraan Addison-Wesley

23 Aksesories yang ada dalam mobil Fixed accessories (AC, tape, sun roof)
Developing Software Woth UML Booch Jacobson Rumbaugh 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

24 Identifikasi use case dan actor
Developing Software Woth UML Booch Jacobson Rumbaugh Identifikasi use case dan actor Gambar use case dari kasus diatas dapat dilihat pada gambar 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 dengan Customer, karena calon customer biasanya belum ada datanya (anonymous), karena data mereka belum terdaftar Addison-Wesley

25 Developing Software Woth UML Booch Jacobson Rumbaugh
Addison-Wesley

26 Developing Software Woth UML Booch Jacobson Rumbaugh
Business use case dan System use case Dalam bisnis use case, actor adalah semua peran (role) yang terlibat dalam proses bisnis, sedangkan dalam system use case, mereka dibatasi hanya kepada mereka yang mempunyai kontak langsung dengan sistem aplikasi. Biasanya customer tidak memiliki akses langsung dengan sistem aplikasi, tetapi dalam bisnis use case mereka tetap dicatat. Jika customer dapat melakukan reservasi melalui self-service terminal atau melalui internet, mereka berinteraksi langsung dengan sistem aplikasi dan oleh karena itu mereka harus digambarkan dalam system use case. Addison-Wesley

27 Jika use case car rental agency diatas dikelompokkan, bentuknya :
Developing Software Woth UML Booch Jacobson Rumbaugh Jika use case car rental agency diatas dikelompokkan, bentuknya : Addison-Wesley

28 Developing Software Woth UML Booch Jacobson Rumbaugh
Menggunakan use case Menggambarkan use case dalam bentuk diagram elips adalah langkah pertama, setelah itu yang berikutnya adalah menjelaskannya dalam bentuk lebih detil lagi. Penjelasan detil dari use case adalah tujuan utama dari use case analysis untuk itu ada dua contoh yang menggambarkan use case lebih detil. Addison-Wesley