Adding SysML requirement containment to requirements diagrams

You can use a requirement diagram to add a SysML requirement containment. With elements drawn in the requirements diagram, use a dependency to show a direct relationship in which the function of an element requires the presence of and might change another element. You can also specify the ways in which requirements relate to other requirements and model elements using stereotypes, or use it in use-case diagrams to show how the requirements trace to the use cases.

About this task

Procedure

  1. In the browser, add the low-level requirement to a high-level requirement.
  2. Create a requirements diagram and drag both requirements onto the requirements diagram.
  3. Right-click the low-level requirement and select Layout > Complete Relations > Selected to All.
  4. To define the relationships between requirements with dependencies, click Dependency Dependency button.
  5. Draw a dependency line from one requirement to another.
  6. Right-click on the dependency line and select Features. You might now select derive as the Stereotype or another possible stereotype including trace, extend, refine, allocate, conform, decompose, satisfy, verify, valueBinding, Send, Usage, Friend, or <New>.
  7. Click OK. The product automatically adds the dependency relationships to the browser.
  8. To define the stereotype of a dependency, double-click the dependency between a requirement and a use case, or right-click and select Features.
  9. Select trace from the Stereotype list.
  10. Click OK.
  11. Optional To trace requirements in use-case diagrams select a requirement from the browser and drag it into or next to the use case.
    1. To be certain that the requirement is visible in the diagram, right-click the requirement that you placed in the diagram and select Display Options. The Requirement Display Options window opens.
    2. The Show group box specifies the information to display for the requirement. Select the Name radio button to display the name of the requirement. Click OK.

Results

You can show the relationship between requirements, and between requirements and model elements that use dependencies. You can set the following types of dependency stereotypes:
  • Derive indicates a requirement that is a consequence of another requirement.
  • Trace shows the dependency from the model element to its requirement with the dependency arrow head on the requirement.

A stereotype is a modeling element that extends the semantics of the UML metamodel by typing UML entities.

Rhapsody® includes predefined stereotypes, and you can also define your own stereotypes. Stereotypes are enclosed in guillemets on diagrams, for example, «derive».