< Previous | Next >

Lesson 2: Tracing requirements in use cases

Uses cases give you information about both the structure and the behavior of the system.
Use cases represent expectations of the system from a user perspective. Use cases show specific actions and capabilities performed by the system. These actions and capabilities produce a result which is of value to one or more actors (external objects that interact with the system) or stakeholders of the system. Your sample project contains one use case diagram depicting the primary uses of the vehicle sensor system. You can see how each of these use cases link 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:The project browser window showing analysis package.

  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:
    Primary uses diagram showing requirements.
  2. Double-click the dependency line that runs from the Control Sensor use case to the Sensor Toggle requirement.
  3. In the Dependency window, click Feature dialog button. The Requirements dialog box displays, showing the description of the Sensor Toggle requirement.
  4. Note the description of the Sensor Toggle requirement and click OK.

Lesson checkpoint

In this lesson, you saw how requirements are traced in use cases. In the next lesson, you prepare to build your model by creating a design package.
< Previous | Next >

Feedback