use-case - A collection of possible scenarios between the system under discussion and external actors,
characterized by the goal the primary actor has toward the system's declared responsibilities,
showing how the primary actor’s goal might be delivered or might fail.
A scenario is a sequence of interactions happening under certain conditions, to achieve the
primary actor’s goal, and having a particular result with respect to that goal. The
interactions start from the triggering action and continue until the goal is delivered or abandoned,
and the system completes whatever responsibilities it has with respect to the interaction.
goal - what is to be accomplished by executing the use case
level - level of detail
scope - (part of) the system under discussion
primary-actor - who has a goal requiring the assistance of the system
supporting-actors - who the system needs assistance from to satisfy its goal (also called secondary actors)
stakeholders - who else has interests in this use case (but doesn't participate)
preconditions - what needs to be true for this use case to be able to execute
trigger - what initiates execution of this use case
minimal-guarantees - what is guaranteed to be always true after executing this use case
success-guarantees - what is guaranteed to be true if the main success scenario completes successfully
main-success-scenario - typical, no-exceptions, scenario in which everything goes right and the goal is delivered
without difficulty, so no recovery is needed
extensions - alternative scenarios
technology-and-data-variations - variations regarding different information supplied/retrieved or technology used
related-information - other information that may help explain the use case
stakeholder - someone, other than the primary actor or supporting actors, who has an interest in the use case
interests - the interest of the stakeholder in the use case
name - the name of the stakeholder, i.e. a persona
role - the role the stakeholder plays
step - an interaction in a scenario that is supposed to work (failure is handled by an extension)
extension - alternate scenario that refers to some point inside the main success scenario
step-altered - step in the original scenario where the interaction changes
condition - circumstances under which the alternate scenario applies
step - an interaction in a scenario
variation - different way of executing the use case
step-altered - step in the original scenario where the interaction changes
kind - the type of variation
variation - explanation of how the scenario changes
use-case-level - level of detail of a use case
summary - collections of user goals (kite)
user goal - the goal of the primary actor trying to get work done (sea)
subfunction - a subgoal or step in an outer scenario, below the main level of interest of the users (fish)
step - an interaction in a scenario
see - reference to related information, like another step or another use case
id - identification of the step, for referral purposes
who - who performs the step
href - location where the reference is stored
step - step that is referred to
actor-type - kind of participant