Skip to content

Create and Organize the Requirements Repository

Requirements Hierarchy

You can create a requirements hierarchy by creating a new requirement at the root of an existing requirement. This is what we call parent requirement and children requirements.

You can create a requirements hierarchy from the Requirements workspace. Before, you must select a requirement. This requirement will be the parent requirement of the requirement you will create. Once the child requirement is created, it appears in the tree, under its parent requirement.

You can create multiple requirements at the root of one single parent requirement. A child requirement can then become the parent requirement of a new requirement.

Parent-child requirements hierarchy

This feature enables you to make a requirement more detailed, or to divide a macro requirement into multiple micro requirements.

The block "Linked requirements" enables you to link one or multiple requirements. This feature enables you to highlight a link between two requirements that is not easy to see just by looking at the tree.

On a requirement's consultation page, the block "Linked requirements" enbables you to link one or several requirements to the consulted requirement.
There are two ways of linking requirements:

  • In the library, select then drag and drop one or multiple requirements to the requirements' "Linked requirements" table;
  • Click on the button Add on the top right of the block, then select the requirements to link from the "Requirements repository" using drag-and-drop

You can link requirements belonging to two different projects.

Link a requirement

The popup "Select a type of link" appears and contains, in a drop-down menu, all the types of links you can assign to requirements. The link is defined by a couple of roles: The role of the source requirement (Role 1) - The role of the linked requirement (Role 2).

Select a link type

Once the requirements are linked, the table's "Role" column is updated with the roles of the linked requirements (Role 2). The "Linked requirements" anchor is also updated with the number of linked requirements under its icon.

Requirement role

Back to top