Prev | Current Page 426 | Next

Tim Weilkiens

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

3.5 Copy Relationship
FIGURE 4-10
Relationship with several source and target elements.
FIGURE 4-11
Example for a copy relationship.
4.3 The Requirement Diagram
req [package] SysML book [multiple satisfy relationship]
?«requirement?»
Requirement 2
?«satisfy?»
?«requirement?»
Requirement 1
?«block?»
Block 2
?«block?»
Block 1
req [package] Legal requirements [CE symbol]
?«requirement?»
Radio
?«legalRequirement?»
RADIO CE symbol
id???R2.7???
text???The CE symbol...???
?«requirement?»
Navigation system
id???R6.2???
text???The CE symbol...???
?«legalRequirement?»
NAV CE symbol ?«copy?»
Defi nition
A copy relationship describes that a requirement is a copy of another
requirement.
It is a stereotype ?«copy?» as a specialization of the UML stereotype ?«trace?».
There is often a need in the requirement model to reuse a requirement in another
context. This can lead to formal problems in connection with the containment
requirement (see discussion in Section 4.3.3). The copy relationship was introduced
for this reason, and to enable the use in different contexts.


Pages:
414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438