scenarios

Summary

Optional narratives that describe usage, threats, and boundary conditions.

Where it appears

• rqml > scenarios

Content model

• scenario (0..n)
• misuseCase (0..n)
• edgeCase (0..n)

Each scenario-like element has:

• narrative (1)

Attributes

Element	Name	Type	Required	Default	Description
scenario/misuseCase/edgeCase	id	IdType	yes	—	Scenario identifier.
scenario/misuseCase/edgeCase	title	string	yes	—	Scenario title.
scenario/misuseCase/edgeCase	actorRef	IdType	no	—	Reference to an actor (if applicable).

Example (minimal)

<scenarios>
  <scenario id="SCN-1" title="User logs in">
    <narrative>User submits credentials and sees dashboard.</narrative>
  </scenario>
</scenarios>

Example (typical)

<scenarios>
  <scenario id="SCN-CHECKOUT" title="User pays with card" actorRef="ACT-USER">
    <narrative>The user submits card details, receives confirmation within 2 seconds.</narrative>
  </scenario>
  <misuseCase id="SCN-FRAUD" title="Stolen card attempt">
    <narrative>Attacker replays stolen card numbers rapidly to test validity.</narrative>
  </misuseCase>
</scenarios>

Notes / LLM hints

• Keep narrative concise; use trace edges to tie scenarios to goals and requirements.
• Use misuseCase and edgeCase to surface risks and robustness concerns early.