Slide 1Today’s ScheduleWhere You Are HeadedModels Created by Analysis ActivitiesModels Used in DesignIdentifying Use Cases Based on User Goals – For each “Actor”Events, Activities, and Use CasesTypes of EventsEvents Affecting a Charge Account Processing System that Lead to Use CasesExternal Event Checklist (Figure 5-8)Temporal Event ChecklistIdentifying EventsSequence of “Transactions” for One Specific Customer Resulting in Many EventsEvents Deferred Until the Design Phase (Figure 5-12)Information about Each Event in an Event Table: Catalog of Information about Each Use CaseNow you try it …For Thursday, February 22Systems Analysis and Design in a Changing World, Tuesday, Feb 202Today’s ScheduleMid-Term Grades are postedEvents and ModelingFor Thursday, February 22Continue Reading Chapter 5, Events and Things (up to page 171)3Where You Are Headed4Models Created by Analysis Activities5Models Used in Design6Identifying Use Cases Based on User Goals – For each “Actor”Use Case An activity the system performs in response to a user request7Events, Activities, and Use CasesTechniques for identifying use casesIdentify user goals–Each goal at the elementary business process (EBP) level is a use case, EBPs are at correct level of analysis for use cases–EBP – a task performed by one user, in one place in response to a business event, that adds measurable business value, and leaves system and data in consistent stateEvent decomposition technique–What events occur that will require the system to respond?–How will the system respond?–Identify business events to decompose system into activities/use cases8Types of EventsExternal–Outside system–Initiated by external agent or actorTemporal –Occur as result of reaching a point in time–Based on system deadlinesState–Something inside system triggers processing need –Ex, inventory reaches threshold, time to reorder9Events Affecting a Charge Account Processing System that Lead to Use Cases10External Event Checklist (Figure 5-8)11Temporal Event Checklist12Identifying EventsCan be difficult to determineOften confused with conditions and responsesMay be useful to trace a transaction’s life cycleCertain events left to design phase–System controls to protect system integrity–Perfect technology assumption defers events13Sequence of “Transactions” for One Specific Customer Resulting in Many Events14Events Deferred Until the Design Phase (Figure 5-12)15Information about Each Event in an Event Table: Catalog of Information about Each Use Case16Now you try it …Identify Users/ActorsSpecify Use CasesWhat are the Activities, what type are they?17For Thursday, February 22Continue Reading Chapter 5, Events and Things (up to page
View Full Document