Shared Requirements

Many times the same requirements are used for multiple projects. Often these requirements must meet specific standards that are precisely described in the requirement description field. Some of these descriptions are very lengthy. Using the shared requirement function, you can share these requirement descriptions among projects. This allows you to easily create, modify and update common requirements while eliminating repetitious typing where errors can be made. Sharing requirements ensures that requirements common to more than one project are consistent from one project to another, or within the same project.

How Shared Requirements Work

The terms mapped and shared are used to define the shared requirements process. A shared requirement is one whose description other requirements use as their own. A mapped requirement is one whose description is linked to a shared requirement.

A typical use of shared requirements is detailed below.

Project A contains a set of frequently used requirements. Projects B and C use some of the requirements defined in Project A. Instead of re-entering or modifying lengthy requirement descriptions in Projects B and C, you can use the shared requirement function to map requirements from Projects B and C to those in Project A. Now changes and updates made to shared requirement descriptions in Project A are automatically made in Projects B and C. The example also shows that Project B is set up to share and map requirements, which allows requirements to map to shared requirements in the same project. Specifically R4 is mapped to R2. Projects B and C show that requirements can map to more than one project.

Rules for shared or mapped requirements

The following rules apply to requirements that are shared or mapped:

  • Only the information contained in the description field of the requirements is shared, not the other attributes, history or traceability data.
  • Description fields of mapped requirements are disabled and you cannot edit them.
  • If mapping is disabled or disconnected, the description becomes independent and you can edit them. In essence, it is no longer a mapped requirement.
  • You cannot share mapped requirements.
  • You cannot map shared descriptions.