Name < the name is the goal as a short active verb phrase> Goal / Description < a longer statement of the goal in context if needed > Pre-conditions <what we expect is already the state of the world> Success End Condition <the state of the world upon successful completion> Failed End Condition <the state of the world if goal abandoned> Actors <a role name or description for the primary actor> <other systems relied upon to accomplish use case> Trigger <the action upon the system that starts the use case> Description step action 1 <put here the steps of the scenario from trigger to goal delivery, and any cleanup after> 2 <...> 3
representation of the flow of interaction. Create a activity diagram for each use-case. § A list of the different states of a system. Build a state diagram for the system. § They are not mandatory, § They are an option to natural language § They can be combined.
the behaviour of the system in response to external and internal events. § State machine models show system states as nodes and events as arcs between these nodes. When an event occurs, the system moves from one state to another. State ~ Data Event ~ Change in Data
shown as a rectangle with rounded corners and the state name inside the rectangle. § composite state is defined as state that has substates (nested states). § An initial state represents a default vertex that is the source for a single transition. There can be at most one initial vertex. The outgoing transition from the initial vertex may have not a trigger or guard. § Final state is a special kind of state signifying that the enclosing region is completed. § A transition is a directed relationship between a source vertex and a target vertex. § Junctions
Use Case Diagram § Use Case Description (per Oval) § Activity Diagram (where/how many are needed?) § State Machine Diagram (where/how many are needed?)
javiergs@asu.edu Fall 2021 Copyright. These slides can only be used as study material for the class CSE563 at ASU. They cannot be distributed or used for another purpose.