The structuring of functional specifications offered by ReqBuilder is reflected in a principle of relationships between the different requirements.

It is the dependencies between the requirements specified in ReqBuilder that ensure the structuring of the functional specifications. For example, a form must be associated with a Data model, a Use case must be associated with a Feature, … etc., all forming a coherent and structured whole.

These relationships are defined automatically by the system from the specification of each requirement. They can also be defined and modified manually.

The example below concerns the Use case “Monitor customer litigations” (1)

The icon above, displayed on the right in the Use case description header, indicates its number of dependencies. The dependencies window displays the following information:

1. The Feature to which the use case is linked.
2. The list of requirements on which the use case depends.
3. A drop-down list for adding a dependency.
4. The list of requirements that depend on the use case.

Note: dependencies are automatically created by ReqBuilder when adding requirement mentions in various description areas: of another requirement, scenario steps, preconditions, postconditions, ... etc.