Prev | Current Page 494 | Next

Tim Weilkiens

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


Again, there are no hard criteria as to how subsystems are denoted. It is
eventually a project decision.
Defi nitions
A system is an artifact created by humans and consisting of blocks that pursue
a common goal that cannot be achieved by the system??™s individual elements.
A block can be software, hardware, a person, or an arbitrary unit [45].
It is a stereotype ?«system?» as a specialization of the SysML stereotype ?«block?».
A subsystem describes a closed unit within a larger system.
It is a stereotype ?«subsystem?» as a specialization of the SysML stereotype
?«block?» (Figure 5.16).
A block can describe very small elements, but also very large ones. SysML does
not dictate anything in this respect. The largest block in a system is the system
itself. This special role is emphasized by the stereotype ?«system?».
In our approach, we used subsystems in Section 2.7.3.
283
bdd [package] SYSMOD profile [system context element]
?«stereotype?»
OMGSysML::Block
?«stereotype?»
System context
FIGURE 5-17
The stereotype for system context elements.


Pages:
482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506