Requirement Allocation Views

Requirement allocation views should allow to specify:

Respectively, there are two Property views dedicated for these purposes: The Requirements Allocation view and the Internal Requirements Allocation view.

Requirements Allocation

The Requirements Allocation view shows all incoming and outgoing relations for an element. This element could be a Requirement, a Capella element or a Diagram. The addition of a relation can be done in three steps as demonstrated with the following example


Internal Requirements Allocation

The Internal Requirements Allocation view shows all relations coming from one Requirement to another Requirement.

Multiple Requirements can be chosen to create new Relations

Technically, relations are stored under the source element of the relation. Also note that relations are technical elements and they are filtered by default. In order to see relations in Capella project explorer, the default filter must be deactivated. Following is an example of Requirements and their relations to/from Capella Elements:

Relations between elements stored in different layers

Certain rules are applied when creating relations between Requirements and Capella elements (and vice versa), especially when they are stored in different layers. In general, a relation is valid if its target comes from the same layer or another upper layer than its source. Therefore,

  1. For outgoing links, target elements are limited to those stored in the current layer and the upper ones
  2. For incoming links, source elements are limited to those stored in the current layer and the lower ones
  3. For internal links, target elements are limited to those stored in the current layer and the upper ones

''Some limitations should be noted for Libraries (see the suitable part of Limitations (online documentation) section).''

The following is an example of creating different types of relations from a Requirement.