Figure D.4 - Establishing the Context of the Hybrid SUV System using a User-Defined Context Diagram

Actually, they aren't, the BDD Figure D.15 only shows non-navigable composition Associations between the Automotive Domain block and the owned Properties, which appear in the IBD Figure D.4 as Property symbols:

SysML-1.6: For the Connectors in Figure D.4 to be typed by the implied anonymous Associations need define them in Figure D.15 (or elsewhere) between 'HybridSUV' and: 'Driver', 'Maintainer', 'Passenger', 'Baggage', 'Environment'.

Such implied anonymous Associations are included explicitly in this trail model.

The Connectors in the spec figure have labels like 'x1:', 'x2:', etc. It was not known yet how to show these:

HSUV trail slide: Figure D.4: IBD: Could not show Connector typed by an anonymous Association as 'connectorName:' with trailing colon

The trailing colon after the Connector label in Figure D.4 has been achieved here with a small HACK , by setting the names to be a single space ' ' (so not actually anonymous):

Also, for now, the Properties of type Actor have been left anonymous.

The call-out format, stereotype properties names, and stereotype keyword for the custom stereotype DiagramDescription are slightly different from the spec sample.

Up next

Figure D.5 - Establishing Top Level Use Cases for the Hybrid SUV

Notes

[CAVEAT] The custom DiagramDescription stereotype is not specified (in SysML1.6)

[ASSERTION, TOOL] SysML: The «system», «subsystem», «external», «domain» and «system context» keywords are for "user defined" block Stereotypes (they are not part of core SysML); they are supported in MagicDraw/Cameo as Non-Normative Extensions.

[CAVEAT, DISPLAY, TOOL] HSUV trail slide: Figure D.4: IBD: Could not show Connector typed by an anonymous Association as 'connectorName:' with trailing colon

[ISSUE] SysML-1.6: For the Connectors in Figure D.4 to be typed by the implied anonymous Associations need define them in Figure D.15 (or elsewhere) between 'HybridSUV' and: 'Driver', 'Maintainer', 'Passenger', 'Baggage', 'Environment'.

[CONVENTION, MODELLING, TIP]{RECOMMENDED} Webel: MBSE: SysMLv1: Prefer a custom «actor» extension of a Block (such as the non-normative External) over UML-style Actor for use as parts in IBDs and on allocation swimlanes. You can also have a Trace from a block-based «actor» to a UML-style Actor.

Snippets (quotes/extracts)

[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.

[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.

[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.