chapter06 - Objectives Detailed Object-Oriented...

Info iconThis preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
2 Object-Oriented Analysis and Design with the Unified Process Objectives  Detailed Object-Oriented Requirements Definitions  System Processes—A Use Case/Scenario View  Identifying Inputs and Outputs—The System Sequence Diagram  Identifying Object Behavior—The Statechart Diagram  Integrating Object-Oriented Models 3 Object-Oriented Analysis and Design with the Unified Process Overview  Refine requirements to threshold of implementation  Apply OOA to use cases and models  Translate process descriptions into working algorithms  Observe that analysis-design boundary is fluid 4 Object-Oriented Analysis and Design with the Unified Process Detailed Object-Oriented Requirements Definitions  System requirements captured with OO models  “Divide and conquer” strategy toward complexity  Two subsets of OO modeling approach ~ Use case driven extending four specific models Use case diagrams, use case descriptions, activity diagrams, system sequence diagrams ~ Object driven extending statechart diagram 5 Object-Oriented Analysis and Design with the Unified Process Figure 6-1 Requirements Diagrams With UML Models 6 Object-Oriented Analysis and Design with the Unified Process Detailed Object-Oriented Requirements Definitions (continued)  Use case diagram: table of contents for business events  System sequence diagrams (SSDs) ~ Define and order sequence of inputs and outputs ~ Information flows referred to as messages  Class diagrams ~ Identify real-world “things” ~ Determine the structure of the programming classes  Statechart diagram describes collection of object states
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
7 Object-Oriented Analysis and Design with the Unified Process System Processes—A Use Case/Scenario View  Define use cases into two tiers: ~ Overview level derived from: Event table and use case diagrams ~ Detailed level derived from combination of: Use case description Activity diagram Sequence diagram 8 Object-Oriented Analysis and Design with the Unified Process Use Cases and Actors  Source ~ Person or thing initiating the business event ~ Must be external to the system  Actor ~ Person or thing that touches the system ~ Lies outside of automation boundary  Identifying actors at the right level of detail ~ Assume actors (even non-human types) have hands ~ Use case is a goal that the actor wants to achieve 9 Object-Oriented Analysis and Design with the Unified Process The Use Case Diagram  Notation for use case diagrams ~ Simple stick figure represents an actor ~ Actor’s hands indicate direct system access ~ Use case itself symbolized by an oval ~ Connecting lines match actors to use cases  Actors may also be other system interfaces ~ May be represented with stick figure or rectangle 10 Object-Oriented Analysis and Design with the Unified Process Figure 6-2 A Simple Use Case with an Actor 11 Object-Oriented Analysis and Design with the Unified Process Automation Boundary and Organization  Expand use case diagrams with other actors and use cases 
Background image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 9

chapter06 - Objectives Detailed Object-Oriented...

This preview shows document pages 1 - 3. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online