{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

chapter05 - Objectives Explain how events can be used to...

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

View Full Document Right Arrow Icon
2 Object-Oriented Analysis and Design with the Unified Process Objectives Explain how events can be used to identify use cases that define requirements Identify and analyze events and resulting use cases Explain how the concept of problem domain classes also defines requirements Identify and analyze domain classes needed in the system 3 Object-Oriented Analysis and Design with the Unified Process Objectives (continued) Read, interpret, and create a Unified Modeling Language (UML) domain model class diagram and design class diagram Use a CRUD matrix to study the relationships between use cases and problem domain classes 4 Object-Oriented Analysis and Design with the Unified Process Overview Objective: refine information gathered Identify use cases and problem domain classes Model problem domain classes with UML notation Introduce use case modeling 5 Object-Oriented Analysis and Design with the Unified Process Events and Use Cases Use case ~ Activity the system carries out ~ Entry point into the modeling process Event decomposition: help identify use cases Elementary business processes (EBPs) ~ Basic unit of analysis ~ Initiated by event occurring at specific time and place ~ Discrete system response that adds business value 6 Object-Oriented Analysis and Design with the Unified Process Figure 5-1 Identifying Use Cases by Focusing on Users and their Goals
Background image of page 1

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

View Full Document Right Arrow Icon
7 Object-Oriented Analysis and Design with the Unified Process Event Decomposition Event decomposition ~ Develops use cases based on system response to events ~ Perceives system as black box interfacing with external environment ~ Keeps focus on EBPs and business requirements Analysts delegated particular events to decompose Result of the decomposition: ~ List of use cases triggered by business events ~ Use cases at the right level of analysis 8 Object-Oriented Analysis and Design with the Unified Process Figure 5-2 Events Affecting a Charge Account Processing System that Lead to Use Cases 9 Object-Oriented Analysis and Design with the Unified Process Types of Events External Events ~ Occur outside the system ~ Usually caused by external agent Temporal Events ~ Occurs when system reaches a point (deadline) in time State Events ~ Asynchronous events responding to system trigger 10 Object-Oriented Analysis and Design with the Unified Process Figure 5-3 External Event Checklist 11 Object-Oriented Analysis and Design with the Unified Process Figure 5-4 Temporal Event Checklist 12 Object-Oriented Analysis and Design with the Unified Process Identifying Events Three rules of thumb Distinguish events from prior conditions ~ Can the transaction complete without interruption? ~ Is the system waiting for next transaction? Trace sequence of events initiated by external agent ~ Isolate events that actually touch the system
Background image of page 2
13 Object-Oriented Analysis and Design with the Unified Process Figure 5-5 Temporal Event Checklist 14 Object-Oriented Analysis and Design with the Unified Process Figure 5-6 The Sequence of “Transactions” for One Specific Customer
Background image of page 3

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

View Full Document Right Arrow Icon
Image of page 4
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}