Scenario Definition¶
Description¶
Scenarios combine activity flows to describe various application use cases.
See also ScenarioDefinition
Examples¶
Example 1: Scenario Definition
<!-- Component definition as MPFO-XML mission profile document. -->
<MPFo Id="ID.COMPONENT.0">
...
<!-- Component activity definition: sequence of operating phases -->
<ActivityDefinition>
<!-- Define activities -->
<Activities>
<!-- Operating phase 1 -->
<Activity Id="ID.Activity.0">
<ActionSetRef Ref="ID.ActionSet.0"/>
</Activity>
<!-- Start operating phase 2 after operating phase 1 -->
<Activity Id="ID.Activity.1">
<ActionSetRef Ref="ID.ActionSet.1"/>
</Activity>
</Activities>
<!-- Consider operating phase 2 to start after operating phase 1 -->
<ActivityFlows>
<ActivityFlow Id="ID.Activity.Flow.0">
<ActivityRefs>
<ActivityRef Ref="ID.Activity.0"/>
<ActivityRef Ref="ID.Activity.1"/>
</ActivityRefs>
</ActivityFlow>
</ActivityFlows>
<!-- Define a activity flow set -->
<ActivityFlowSets>
<ActivityFlowSet Id="ID.Activity.FlowSet.0">
<References>
<ActivityFlowRef Ref="ID.Activity.Flow.0"/>
</References>
</ActivityFlowSet>
</ActivityFlowSets>
</ActivityDefinition>
<!-- Define an activity scenario for the component and apply/use it -->
<ScenarioDefinition>
<!-- Define an application scenario with one activity flow -->
<Scenarios>
<Scenario Id="ID.Scenario.0">
<ActivityFlowSetRefs>
<ActivityFlowSetRef Ref="ID.Activity.FlowSet.0"/>
</ActivityFlowSetRefs>
</Scenario>
</Scenarios>
<!-- Apply the scenarios -->
<Application Id="ID.Scenario.Application">
<ScenarioRefs>
<ScenarioRef Ref="ID.Scenario.0"/>
</ScenarioRefs>
</Application>
</ScenarioDefinition>
...
</MPFo>