system-requirements

Requirements with Alternatives


In the project I am currently working in, the requirements is on this form:

  1. The system must ...
  2. The system must ...

It works fine as long as there are no alternative scenario. But how should I write if the system work differently depending on what happens?

if ScenarioA Then do This
elseif ScenarioB Then do That

Solution

  • Why don't you try User Story?

    User Stories (opposed to requirements) are brief statements of intent that describe something the system needs to do for some user.

    As a user closing the application, I want to be prompted to save anything that has changed since the last save so that I can preserve useful work and discard erroneous work.

    1. For scenarioA do this
    2. For scenarioB do that
    1. As a user doing scenarioA, I want this, so that I can open my application.
    2. As a user doing scenarioB, I want that, so that I can close my application.