This is an old revision of the document!
Below are instructions for scenario modeling using the scenario-template.
The scenario name should be as concise as possible, and should describe the primary action : the high-level activity being performed (verb) and object of the action (noun).
A summary of the scenario in natural language text. Using an iterative modeling approach, the narrative may be the first and only artifact to be documented. It should include sufficient detail to allow analysts to derive and complete the remaining template details.
The narrative should be traceable to supporting source materials, including primary data from SME interviews or knowledge resources such as research publications, policies and guidelines. Links to all relevant sources should be included at the bottom of the template.
Participants should be identified and enumerated from the narrative summary. Participants may be described by their generic roles, or specifically identified and named actors.
A list of participant roles, consisting of links to items in the roles registry.
Resources are physical or virtual (abstract) entities that are identified within the narrative summary, and are either required or optional elements in the scenario. Resources are listed as links to the resource registry.
Inputs are existing, external resources that are either required or optional to the scenario.
Outputs are new or modified resources that result as an outcome of the scenario, including intended (work) products or residual or waste outputs.
Contexts are the setting(s) within which the scenario takes place. Contexts should be listed as links to the context registry.
Physical contexts are real-world settings, such as generic geographical, environmental, or jurisdictional regions (e.g. lake, forest, city), as well as generic settings within human habitats (e.g. home, farm, hospital). The context may refer to a specific, named, real-world entity where appropriate (e.g. UN Headquarters).
One or more statements of the desired or expected outcomes of the scenario (future state).
Concise statements regarding the state of participants, resources or contexts at the start of the scenario; activities or events either completed or underway concurrently; statements may be grouped using logical operators (not, and, or, xor) to describe compound preconditions.
Flows originating with previous activities or events may be either synchronized (all flows required) or merged (one or more flows required). Previous activities or events have completed.
Concurrent flows have begun and are underway, but have not completed prior to start of the flow.
Sequence of activities or events from start to one or more identified goals or other outcomes.
Activities or events : recursive elaboration of each activity or event as required until fine-grained (atomic) descriptions have been are reached.
Flows when the preconditions have not been met.
Concise statements regarding the state of participants, resources or contexts at the end of the scenario.
Post-conditions that satisfy the scenario goals.
Post-conditions when scenario goals have not been met, such as interruption or cancellation of flows.
Flows that occur following completion of the scenario; these include flows following successful outcomes as well as compensating or terminating flows when attainment of goal-states has not been met. Multiple subsequent flows may either branch (all flows simultaneously) or split (one of multiple flows selected)
Links to supporting documentation, including primary data and knowledge resources