Trace Use of Requirements
Having investigated the representation of requirements in your model, you might review either how they have been used to direct development through the model, or how a particular development was initiated. This is discussed in greater detail in the Traceability topics, but the windows and facilities you might use to follow development from Requirements are briefly described below. The significant feature in tracing Requirements and development is the connectors between the elements.
- Relationships window - quickly identifies every relationship of which a selected Requirement element is a member, and the partner element in that relationship, whether or not the relationship is visible in the current diagram. If the partner element is not in the diagram, you have the option of adding it.
- Traceability window - a very useful tool in showing chains of relationships that include the selected element. The window can show, for example, that a Requirement A is realized by a Use Case X, but Use Case X also realizes Requirement B, which in turn is also realized by Use Case Y. You can control the type and extent of these relationship chains, but as the system checks the connectors and partner elements of every relationship within the limits you impose, the system can take some time to produce the final results.
- Relationship Matrix - a significant tool in mapping the relationships between the Requirements elements in a package and other elements in either that package or a different package. Where a relationship is missing, you can add it; if an existing relationship is misplaced, you can delete it.
- Properties dialog, Requirements tab - for elements other than Requirements (particularly Use Cases), shows all internal responsibilities and external requirement elements attached to the element.
- Scenarios & Requirements window - as for the Properties dialog, shows the Requirements and responsibilities of the selected element, and the scenarios and constraints under which the Requirements are being realized.