1 / 11

Use Case Overview

09/17/2001. Sue CongerMGT 7378. Why Use Case?". Provides a problem definition that users can understand.Defines all transactions' that are of interest.Defines all interactions of interest.. 09/17/2001. Sue CongerMGT 7378. Use Case Terminology. . Actor: A person or entity external to th

zasha
Download Presentation

Use Case Overview

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. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    1. 09/17/2001 Sue Conger MGT 7378 Use Case Overview

    2. 09/17/2001 Sue Conger MGT 7378 Why “Use Case?” Provides a problem definition that users can understand. Defines all ‘transactions’ that are of interest. Defines all interactions of interest.

    3. 09/17/2001 Sue Conger MGT 7378 Use Case Terminology

    4. 09/17/2001 Sue Conger MGT 7378 Use Case Summary Diagram

    5. 09/17/2001 Sue Conger MGT 7378 Use Case Terminology Use Case: Also, a transaction. A sequence of actions performed by an application with an observable outcome of value to a particular actor. e.g., “Play the game”, “Buy items, pay cash” Scenario: an instance of a use case

    6. 09/17/2001 Sue Conger MGT 7378 Use Case & Scenario Example Use Case: Do card transaction Summary Execute a transaction using the Card Actors Customer, clerk Precondition Card has been activated Description Customer presents the card. Clerk swipes it in register. Card is sensed, read, mag data is validated. App is passed card data & trans amount. DB-Cust Acct is accessed to validate trans amount against current limit. Complete trans or msg to clerk. Normal path Describes the above process using Process-Class names (Scenario 1) from Class structure diagram with linking text to describe their relationships Alternate path 2 to n other normal paths through the process. (Scenario 2) Exception 1 to n exception sequences described, attending to flow of (Scenario 3) processing after exception is handled Requirements Timing, structure, control or inferential Post Condition Outcomes on which other processes depend Outstanding Issues Context specific decisions needed.

    7. 09/17/2001 Sue Conger MGT 7378 Use Case Model The set of all use cases for an application The set of all actors with whom use cases interact … A complete description of application functionality

    8. 09/17/2001 Sue Conger MGT 7378 Use cases define: Timing of the case Sequence of related events System actions

    9. 09/17/2001 Sue Conger MGT 7378 Identifying Use Cases For each actor, identify Needs from the system System interactions Priorities Risks

    10. 09/17/2001 Sue Conger MGT 7378 Relationships between use cases Reusable modules: dbConn, DateValidate <<include>> Conditional situations: Based on if...then…else logic <<extend>>

    11. 09/17/2001 Sue Conger MGT 7378 Actors as classes <<actor>> Player

More Related