1 / 17

Chapter 3

Chapter 3. Use Cases. Use case — an activity that the system performs, usually in response to a request by a user Use cases define functional requirements Analysts decompose the system into a set of use cases (functional decomposition) Two techniques for Identifying use cases

druce
Download Presentation

Chapter 3

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. Chapter 3 Systems Analysis and Design in a Changing World, 6th Edition

  2. Use Cases • Use case— an activity that the system performs, usually in response to a request by a user • Use cases define functional requirements • Analysts decompose the system into a set of use cases (functional decomposition) • Two techniques for Identifying use cases • User goal technique • Event decomposition technique • Name each use case using Verb-Noun Systems Analysis and Design in a Changing World, 6th Edition

  3. User Goal Technique • The most common technique • Identify all of the potential categories of users of the system Systems Analysis and Design in a Changing World, 6th Edition

  4. User Goal TechniqueSome RMO CSMS Users and Goals Systems Analysis and Design in a Changing World, 6th Edition

  5. Event Decomposition Technique • More Comprehensive and Complete • Identify the events that occur to which the system must respond. • For each event, name a use case (verb-noun) that describes what the system does when the event occurs • Event– something that occurs at a specific time and place, can be described, and should be remembered by the system Systems Analysis and Design in a Changing World, 6th Edition

  6. Events and Use Cases Systems Analysis and Design in a Changing World, 6th Edition

  7. Types of Events • External • occurs outside the system, usually initiated by an external agent or actor • Temporal • occurs as a result of reaching a point in time • State • occurs when something happens inside the system that triggers some process • reorder point is reached for inventory item Systems Analysis and Design in a Changing World, 6th Edition

  8. Finding the actual event that affects the system Systems Analysis and Design in a Changing World, 6th Edition

  9. Tracing a sequence of transactions resulting in many events Systems Analysis and Design in a Changing World, 6th Edition

  10. Perfect Technology Assumption Systems Analysis and Design in a Changing World, 6th Edition

  11. Event Decomposition Technique: Benefits • Events are broader than user goal: • Capture temporal and state events • Help decompose at the right level of analysis: • elementary business process (EBP) • EBP is a fundamental business process performed by one person, in one place, in response to a business event Systems Analysis and Design in a Changing World, 6th Edition

  12. Use Cases and CRUD Technique • CRUD • Create, Read/Report, Update, and Delete (archive) Systems Analysis and Design in a Changing World, 6th Edition

  13. Use Cases and CRUD Technique Systems Analysis and Design in a Changing World, 6th Edition

  14. CRUD TechniqueUse Case vs. Domain Class Table Systems Analysis and Design in a Changing World, 6th Edition

  15. Brief Use Case Descriptions Systems Analysis and Design in a Changing World, 6th Edition

  16. Use Case DiagramsDraw for each subsystem Systems Analysis and Design in a Changing World, 6th Edition

  17. Use Case DiagramsThe <<Includes>> relationship • A relationship between use cases where one use case is stereotypically included within the other use case— like a called subroutine. Arrow points to subroutine Systems Analysis and Design in a Changing World, 6th Edition

More Related