chapter3

• User Stories


  A one-sentence description of a work-related task done by a user to achieve some goal or result
• Acceptance Criteria


  Identify the features that must be present at the completion of the task
• User Story Template


  "As a <role> I want to <goal> so that <benefit>"
• Use Case


  An activity that the system performs, usually in response to a request by a user
• Identifying Use Cases


  1. User goal technique

  2. Event decomposition technique
• User Goal Technique


  • Simple and effective
  • Identify all potential categories of users
  • Interview users to find specific goals
• Event Decomposition Technique


  • More comprehensive and complete
  • Identify events that occur to which the system must respond
  • Name a use case for each event
• External Event


  An event that occurs outside the system, usually initiated by an external agent or actor
• Temporal Event


  An event that occurs as a result of reaching a point in time
• State Event


  An event that occurs when something happens inside the system that triggers some process
• Elementary Business Process (EBP)


  A fundamental business process performed by one person, in one place, in response to a business event
• Use Case Description


  A one sentence description showing the main steps in a use case
• Use Case Diagram


  A UML model used to graphically show use cases and their relationships to actors
• Actor


  The UML name for an end user
• Automation Boundary


  The boundary between the computerized portion of the application and the users who operate the application
• <<includes>> Relationship


  A relationship between use cases where one use case is stereotypically included within the other use case
• Creating a Use Case Diagram

  1. Identify stakeholders and users who would benefit

  2. Determine what each needs to review

  3. Select use cases and actors to show

  4. Name the diagram and note how/when to use it
• This chapter focuses on modeling functional requirements as part of systems analysis
• Use cases are the functions identified, the activities the system carries out usually in response to a user request
• The user goal technique begins by identifying end users called actors and asking what specific goals they have when interacting with the system
• The event decomposition technique begins by identifying events that occur that require the system to respond
• The use case diagram shows the actors, the automation boundary, the uses cases that involve each actor, and the <<includes>> relationship