2Object-Oriented Analysis and Design with the Unified Process Figure 6-1 Requirements Diagrams With UML Models.

2Object-Oriented Analysis and Design with the Unified Process

Figure 6-1Requirements Diagrams With UML Models

How to ID Use Cases

Techniques for identifying use cases

User goal technique - Each goal at the elementary business process (EBP) level is a use case

CRUD analysis technique (create, read, update, delete)

Event decomposition technique

3Object-Oriented Analysis and Design with the Unified Process

4Object-Oriented Analysis and Design with the Unified Process

Use Case Detailed Descriptions

Use case descriptions written at (3) levels of detail

Brief description

Intermediate description

Fully Developed Description

5Object-Oriented Analysis and Design with the Unified Process

Figure 6-7Brief Description of Create New Order Use Case

6Object-Oriented Analysis and Design with the Unified Process

Figure 6-8Intermediate Description of Telephone Order Scenario for Create

New Order Use Case

7Object-Oriented Analysis and Design with the Unified Process

Figure 6-10Fully Developed Description of Telephone Order Scenario for

Create New Order Use Case

8Object-Oriented Analysis and Design with the Unified Process

Figure 6-3A Use Case Diagram of the Order-Entry Subsystem for RMO,

Showing a System Boundary

9Object-Oriented Analysis and Design with the Unified Process

Figure 6-4A Use Case Diagram of the Customer Support System (by Subsystem)

10Object-Oriented Analysis and Design with the Unified Process

Locations and the Crud Matrix

Location diagrams: Shows need for network connections Creates awareness of geographic reach

Use case–location matrix: shows where use cases are performed

Use case–domain class matrix: highlights access requirements  Example: The CRUD (create, read, update, and

delete)

11Object-Oriented Analysis and Design with the Unified Process

« Includes » Relationships «includes» or «uses» relationship

Use case calling services of common subroutine

Common subroutine itself becomes additional use case

Examples: “Validate customer account” and “Look Up Item Availability”

Notation Relationship denoted by connecting line with arrow

Direction of the arrow indicates major/minor cases

12Object-Oriented Analysis and Design with the Unified Process

Figure 6-6An Example of the Order-entry Subsystem With «Includes» Use Cases

13Object-Oriented Analysis and Design with the Unified Process

Figure 6-12Activity Diagram of the Telephone Order Scenario

14Object-Oriented Analysis and Design with the Unified Process

Identifying Inputs and Outputs —the System Sequence Diagram

System sequence diagram (SSD)

Describes flow of information

Identifies interaction between actors and system

Message oriented

15Object-Oriented Analysis and Design with the Unified Process

Figure 6-14Sample System Sequence Diagram

16Object-Oriented Analysis and Design with the Unified Process

Identifying the Object Behavior the Statechart Diagram

A state in a statechart similar to status condition

Spans many business events

Developed for complex problem domain classes

17Object-Oriented Analysis and Design with the Unified Process

Figure 6-19Simple Statechart for a Printer

18Object-Oriented Analysis and Design with the Unified Process

Guidelines for Statecharts

Guidelines to help identify states Check that something can have status conditions Simple states reflect simple conditions such as “On” Complex states labeled with gerunds or verb phrases

◘ Example: “Being shipped” Describe only states of being of the object itself

19Object-Oriented Analysis and Design with the Unified Process

Figure 6-22States and Exit Transitions for Orderitem

20Object-Oriented Analysis and Design with the Unified Process

Figure 6-24Final Statechart for Orderitem