Lesson 2: Tracing requirements in use cases

Uses cases give you information about both the structure and the behavior of the system.

About this task

Use cases represent expectations of the system from a user perspective. Use cases show specific actions and capabilities of the system. The actions and capabilities produce a valuable result for actors or stakeholders of the system. Your sample project contains one use case diagram that shows the primary uses of the vehicle sensor system. You can see how each of these use cases links to the requirements that you worked with in lesson 1. The Analysis package contains a use case diagram and two primary use cases, as shown here:

1. Double-click the Primary Uses diagram. Note the two requirements Sensor Start and Sensor Toggle with trace stereotypes identified in the diagram as shown:
   
2. Double-click the dependency line that runs from the Control Sensor use case to the Sensor Toggle requirement. This dependency link shows traceability, which is valuable when you perform impact analysis, or create compliance documentation.
3. To open the Features window of the Sensor Toggle requirement, in the General tab, click .
4. Note the description of the Sensor Toggle requirement and click OK.