Scenarios and use Cases

  • Purpose
    • Describe how an actor interacts with a solution to achieve one or more goals of the actor, or responding to an event
  • Description
    • Scenario describes only one way in which a player can reach a target in particular, through a series of steps performed by the actors
    • Use case describes all possible outcomes of an attempt to achieve a particular goal that supports the solution through various scenarios in the form of primary flow (basic,simplest) and alternative (special situations and exceptions)
  • Elements
    1. Name – Unique inside the project, describes the goal or event which he treats and includes a verb + noun
    2. Actors – A person, system or external event to the system that interacts with the system through the use case, unique name that represents the role, should never be the name of a person
    3. Preconditions – Any fact that the solution must take as true for when the use case begins
    4. Flow of events – Describes what the actor and the system are doing while running the scenario or use case, primary or alternate
    5. Post conditions – Any fact that must be true when the use case is complete
    6. Relationships
      • Associations – Between actors and use cases
      • Stereotypes – Between the use cases. Extension or Inclusion.
  • Usage Considerations
    • Advantages
      • Good to clarify the scope and providing a high-level understanding of the goals of user behavior, normal situations, alternatives or exceptions
    • Disadvantages
      • There are many resources to support the interaction or discovery of elements in common

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s