The document discusses use case modeling and provides details on key elements of use case models including: - A use case describes a task performed by an actor to achieve a goal - Use cases can be at different levels of detail from summary to atomic - Use cases specify basic, alternative, and exception paths to achieving the goal - Use cases are written from both a business and system perspective

1. An Examination of Use Cases Mark Smith Director Operations Support Services Adaptis, Inc. ( [email_address] )

11. Level of detail Illustration taken from Writing Effective Use Cases – Alistair Cockburn Atomic, user level use cases are the goal for system requirements specification Summary User Sub-function Atomic Composite Business process Activity Activity Activity UC UC UC UC UC UC UC UC

27. Some use cases may be sufficiently specified at level II Stop when sufficient detail is achieved Unfolding The use case model and its individual use cases evolve level by level over time Not all use cases of a model will necessarily need to be specified to the same level of detail Alternate & Exception Paths Basic Path Pre- & Post-conditions Name & Description Includes/ Extends Relationships L 1 Level 2 Level 3 Level 4 Level 5

32. Example of use case diagram <<extends>> Limits exceeded Trader Analyze risk Price deal Capture deal Salesperson Valuation <<includes>> <<includes>>

33. Another Use Case Diagram

35. Use Case and High Level Sequence Diagram Find a Claim – Use Case (Design considerations in parenthesis) Basic Path 1. User initiates a claim search per submitted criteria. 2. System returns subset of search results (display of 10 @ a time) 3. User selects claim (click item in upper list pane; item highlighted) 4. System returns claim summary (lower preview pane) 5. User requests full claim detail (link/button from preview pane) 6. System returns full claim detail (pop up -claim header with vertical list of services and encounter details) 7. Repeats process if applicable beginning at step 3 or back to step 1. Alternate Path – Encounter Detail Leaves Basic Path after 4. Returns to Basic Path at 7 1. User requests Encounter detail (encounter hyperlink in claim summary) 2. System returns Encounter detail (pop up -claim header & encounter header with vertical list of service level details) Alternate Path – Claim Detail via Encounter Detail Leaves Basic Path after 4 Returns to Basic Path at 6 1. User requests Encounter detail (encounter hyperlink in claim summary) 2. System returns Encounter detail (claim header & encounter header with vertical list of service level details) 3. User requests full claim detail (link/button from encounter detail screen) Alternate Path – Sort Leaves Basic Path after 2 Returns to Basic Path at 3 1. User sorts list by column heading (i.e. Dates of Service in ascending order) 2. System returns subset of search results in new sort order. (Different set of 10 from full search results) Exception Path - Invalid Search Criteria Leaves Basic Path after 1 1. System returns no records that match criteria 2. System returns error message 3. System directs user back to search page (Can we maintain state from previous search?)

36. Diagramming interaction - Make a phone call Interaction diagram illustrates basic course

38. CRUD Matrix Combining Use Case & Class Views Entity classes Use Cases & Scenarios Use Case Class UC UC UC Class Class Class C U U C D C Use Cases Class Model

39. Modeling Entity State Behavior Use Case Entity UC UC UC Entity Entity Entity C U U C D C Use Cases Entity State Model S 1 S 2 S 3 Class S 1 S 2 S 3