Books for you

They are the stereotypes ?«weightedSatisfy?» and ?«weightedVerify?», respectively,
as a specialization of the SysML stereotypes ?«satisfy?» and ?«verify?» (Figure 5.9).
bdd [package] SYSMOD profile [domain block]
?«stereotype?»
OMGSysML::Block
?«stereotype?»
Domain
FIGURE 5-8
The ?«domain?» stereotype for blocks.
279
bdd [package] SYSMOD profile [use cases]
?«metaclass?»
UML4SysMLUseCase
?«stereotype?»
Continuous
?«stereotype?»
Secondary
?«metaclass?»
UML4SysML::Activity
FIGURE 5-11
Stereotypes for use cases.
5.7 Continuous and Secondary Use Cases
FIGURE 5-10
Example for a weighted satisfy relationship.
req [package] Functional requirements [card reader cover]
?«functionalRequirement?»
Identify customer
?«block?»
Card reader ?«weightedSatisfy?»
{coverage0.4}
The SysML satisfy relationship merely states that a system element meets a given
requirement. It does not say anything as to whether the requirement is fully or
partially satisfi ed. The coverage of the weighted satisfy relationship describes the
degree of fulfi llment.


Pages:
477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501