3.09 - Associate and remove association between requirements versions

In the Linked Requirements unit of requirement consultation page, requirement versions can be linked together.

3.9.1 Associate a requirement version

Prerequisite: Several requirements were created

3.9.1.1 From the association interface

1. Select a requirement

2. In the Linked requirement click on [+]

A level 2 interface shows up. It contains the projects on the left (tree structure), and a table on the right.

3. Click on the arrow in front of the project (or double-click on the item) and the related requirement(s) will show up. Repeat the step if the requirement is in a folder or sub-folder. Select the requirement you wish to associate by clicking once on its name.

4. Click on [>>] OR drag and drop the requirement from the tree structure to the association table.
The requirement shows up in the table, and a 'Link type' pop-up window appears.
The pop-up window contains the names of the two requirements to link, as well as a dropdown list with all the link types that can be assigned to them.

5. Select a link type and click on [Confirm]. The role column is updated with the linked requirement role.

6. Click on [Return]. The Linked Requirement unit is updated (it is also updated for the linked requirement)

FOCUS

The link type is defined by a roles couple as follows: Selected requirement role (Role 1) - Linked requirement role (Role 2).

The default link types are: Related - Related, Parent - Child (or Child - Parent) and Duplicate - Duplicate.

It is possible to add, edit or delete link types with the Requirement link types workspace in the Administration workspace (refer to Administrator Guide for more information).

3.9.1.2 From the Linked Requirements unit

1. On the requirement consultation page, drag and drop one (and only one) requirement from the requirements tree to the Linked Requirements unit. The Link type popup displays.

2. Select a link type and click on [Confirm]. The Linked Requirement unit is updated (the linked requirement is also updated).

FOCUS

A requirement version can be linked to several other requirement versions.

A requirement version cannot be linked multiple times to a requirement version.

A requirement version cannot be linked to a version of its own requirement.

3.9.1.3 Edit the link type

From the association interface or from the Linked Requirements unit, it is possible to edit the link type of each linked requirement.

• 1. Click on [Edit] (symbolized by a pencil icon) on each row of the Linked Requirements unit table. The 'Link Type' pop-up window shows up.

  2. Select a link type and click on [Confirm]. The Linked Requirement unit is updated.

3.9.2 Remove an association

3.9.2.1 From the association interface

Prerequisite: having requirement versions linked together. Being on the level 2 association interface.

1. It is possible to remove association of one or several requirements at a time. On the association table, click on the numbers of the requirement(s) to remove.

2. Click on [<<]. A pop-up window asking to confirm or cancel the removal opens up.

3. Click on [Confirm]. The selected requirements are removed from the association table

4. Click on [Back]. The removed linked requirements do not show up anymore in the Linked requirements unit.

3.9.2.2 From the Linked Requirements unit

There are two ways to remove the requirement(s) association(s) from the Linked Requirements unit:

1. Select one or several requirements and click on [-]. A pop-up window asking to confirm or cancel the removal opens up.

2. Click on [Confirm]. The requirements are removed from the Linked Requirements unit.

OR

1. Click on the deletion button at the end of each table row. A pop-up window asking to confirm or cancel the removal shows up.

2. Click on [Confirm]. The requirements are removed from the Linked Requirements unit.