Note how the relationships in this diagram are also reflected in the Automotive Domain Model Block Definition Diagram, Figure D.15. Source OMG Systems Modeling Language (SysML) 1.6
The associations among the classes may represent abstract conceptual relationships among the entities, which would be refined in subsequent diagrams. Source OMG Systems Modeling Language (SysML) 1.6
Also, a background such as a map can be included to provide additional context. Source OMG Systems Modeling Language (SysML) 1.6
The spatial relationship of the entities on the diagram sometimes conveys understanding as well, although this is not specifically captured in the semantics. Source OMG Systems Modeling Language (SysML) 1.6
The «system» and «external» stereotypes are user defined, not specified in SysML, but help the modeler to identify the system of interest relative to its environment. Source OMG Systems Modeling Language (SysML) 1.6
The entities are conceptual in nature during the initial phase of development, but will be refined as part of the development process. Source OMG Systems Modeling Language (SysML) 1.6
The diagram usage enables the modeler or methodologist to specify a unique usage of a SysML diagram type using the extension mechanism described in Annex A, “Diagrams.” Source OMG Systems Modeling Language (SysML) 1.6
The term “context diagram,” in Figure D.4, refers to a user-defined usage of an internal block diagram, which depicts some of the top level entities in the overall enterprise and their relationships. Source OMG Systems Modeling Language (SysML) 1.6
Figure D.4 - Establishing the Context of the Hybrid SUV System using a User-Defined Context Diagram ARCHIVAL (2023): This content is now considered historical only! Gallery Tutorial TRAIL: The SysML-1.6 Hybrid SUV sample and specification diagrams in MagicDraw/Cameo (with annotations) [UNDERGOING UPDATE to SysML1.7] Section Section: SysML-1.6: HSUV sample Slide kind SysML Internal Block Diagram (IBD)
