slide1 n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Figure 6-1 Requirements Diagrams With UML Models PowerPoint Presentation
Download Presentation
Figure 6-1 Requirements Diagrams With UML Models

Loading in 2 Seconds...

play fullscreen
1 / 20

Figure 6-1 Requirements Diagrams With UML Models - PowerPoint PPT Presentation


  • 87 Views
  • Uploaded on

Figure 6-1 Requirements 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.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

Figure 6-1 Requirements Diagrams With UML Models


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
slide2

Figure 6-1

Requirements Diagrams With UML Models

Object-Oriented Analysis and Design with the Unified Process

how to id use cases
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

Object-Oriented Analysis and Design with the Unified Process

use case detailed descriptions
Use Case Detailed Descriptions
  • Use case descriptions written at (3) levels of detail
    • Brief description
    • Intermediate description
    • Fully Developed Description

Object-Oriented Analysis and Design with the Unified Process

slide5

Figure 6-7

Brief Description of Create New Order Use Case

Object-Oriented Analysis and Design with the Unified Process

slide6

Figure 6-8

Intermediate Description of Telephone Order Scenario for Create New Order Use Case

Object-Oriented Analysis and Design with the Unified Process

slide7

Figure 6-10

Fully Developed Description of Telephone Order Scenario for Create New Order Use Case

Object-Oriented Analysis and Design with the Unified Process

slide8

Figure 6-3

A Use Case Diagram of the Order-Entry Subsystem for RMO, Showing a System Boundary

Object-Oriented Analysis and Design with the Unified Process

slide9

Figure 6-4

A Use Case Diagram of the Customer Support System (by Subsystem)

Object-Oriented Analysis and Design with the Unified Process

locations and the crud matrix
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)

Object-Oriented Analysis and Design with the Unified Process

includes relationships
« 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

Object-Oriented Analysis and Design with the Unified Process

slide12

Figure 6-6

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

Object-Oriented Analysis and Design with the Unified Process

slide13

Figure 6-12

Activity Diagram of the Telephone Order Scenario

Object-Oriented Analysis and Design with the Unified Process

identifying inputs and outputs the system sequence diagram
Identifying Inputs and Outputs —the System Sequence Diagram
  • System sequence diagram (SSD)
    • Describes flow of information
    • Identifies interaction between actors and system
    • Message oriented

Object-Oriented Analysis and Design with the Unified Process

slide15

Figure 6-14

Sample System Sequence Diagram

Object-Oriented Analysis and Design with the Unified Process

identifying the object behavior the statechart diagram
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

Object-Oriented Analysis and Design with the Unified Process

slide17

Figure 6-19

Simple Statechart for a Printer

Object-Oriented Analysis and Design with the Unified Process

guidelines for statecharts
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

Object-Oriented Analysis and Design with the Unified Process

slide19

Figure 6-22

States and Exit Transitions for Orderitem

Object-Oriented Analysis and Design with the Unified Process

slide20

Figure 6-24

Final Statechart for Orderitem

Object-Oriented Analysis and Design with the Unified Process