￿We now examine how the product structure and the product requirements can be related: One of the important consequence of having requirements as

model elements is that it allows the designer to specify which components in the system satisfy a given set of requirements. This is called the allocation process. We show an example of requirement allocation in Figure 7-4,where the part on the left hand side represents some elements of the RSW, and the part on the right hand side is a hierarchy of requirements. One way to perform allocation is to use the <<satisfy>> dependency. In the figure, the Rain Sensing Wiper model element is allocated to the requirement named Automatic Wiping. Any element in SysML can be used to satisfy a requirement.

￿Another way to display allocation is to use a dedicated compartment named requirement related. This compartment displays the status of a set of derived properties related to requirements. In Figure 7-4the element ECU displays this compartment: The ECU element is allocated to the requirement named Use dedicated ECU.

Figure 7-4 Example of requirement allocation

152Model Driven Systems Development with Rational Products

Page 168
Image 168
IBM SG24-7368-00 manual Example of requirement allocation