Figure D.6 - Establishing Operational Use Cases for Drive the Vehicle

Note that once again additional to the spec figure, a non-normative «system» block HybridSUV has been used as the 'subject', and it's the same HybridSUV as in the last diagram, i.e. a UseCase Diagram need not show all relevant UseCases for a given subject Classifier at once.

You might have noticed the use of Operate the vehicle in the previous figure and its packaging. Does it belong under the operational Package shown here? Currently it is at a higher level with similar high-level UseCases shown previously, which might also be better packaged in sub-packages once some finer UseCase for them are known. It's not critical because:

Visual containment of the symbol for a UseCase in the rectangular symbol for a subject Classifier does NOT imply ownership! Packaging (ownership) of UseCases is separate from use within subjects, and a single UseCase may be used in more than one subject.

Up next

Figure D.7 - Elaborating Black Box Behavior for the “Drive the Vehicle” Use Case

Notes

[ASSERTION] Visual containment of the symbol for a UseCase in the rectangular symbol for a subject Classifier does NOT imply ownership! Packaging (ownership) of UseCases is separate from use within subjects, and a single UseCase may be used in more than one subject.

[CAPABILITY, DISPLAY, STYLE] In MagicDraw/Cameo the name and any stereotype keywords of a Classifier subject of a UseCase may be shown in the top-middle (not just top-left)

[GOTCHA, TOOL, WARNING] Webel: SysMLv1/UML: MagicDraw/Cameo: AVOID the the vendor-specific «useCaseModel» stereotype for Model packages, it leads to confusion with the rectangular 'subject' notation

[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] Goal-level Use Cases associated with “Operate the Vehicle” are depicted in the following diagram. These use cases help flesh out the specific kind of goals associated with driving and parking the vehicle.

[SysML-1.6] Maintenance, registration, and insurance of the vehicle would be covered under a separate set of goal-oriented use cases.

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