Prev | Current Page 423 | Next

Tim Weilkiens

"Systems Engineering with SysML/UML: Modeling, Analysis, Design"

7 ).
4.3.4 Satisfy Relationship
2 In this case, explicitly drawing the relationship would be clearer.
FIGURE 4-7
Example for a namespace containment.
4.3 The Requirement Diagram
req [package] Usability requirements [usage concepts]
?«usabilityRequirement?»
Usage concept
on-board computer
?«usabilityRequirement?»
Usage concept
key deposit
?«usabilityRequirement?»
Usage concept
card reader
?«usabilityRequirement?»
Usage concept
central unit
Defi nition
A satisfy relationship describes that a design element satisfies a requirement.
It is a stereotype ?«satisfy?» of the UML relationship realization.
Each design element in your model has the direct or indirect purpose of satisfying
a requirement to the system. You could also say: The design element realizes
that requirement. For this reason, ?«satisfy?» is a stereotype for the UML relationship
realization . If this relation is modeled, then it can be seen what effect changes to
the design will have to the requirements. Vice-versa, you can identify the design
elements concerned by changes to the requirements.


Pages:
411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435
bwin 50 euros spolszczenia wciągarki linowe ciekawe zdania drzwi aluminiowe