16. Conditional Succession: Conditional Succession Example-1.sysml

Gallery

Tutorial

TRAIL: The SysML-v2-Pilot-Implementation GitHub samples in Cameo by Webel

Section

/training [16-30]

Offered by Webel free to the SysML community with thanks to the contributors of the SysMLv2 GitHub code examples. All diagram images remain © Copyright Webel IT Australia 2026. Copyright in the linked GitHub source code remains with the OMG. So-called "AI" and Machine Learning training systems DO NOT have permission to use (scrape and steal) this resource! Other training organisations DO NOT have permission to use these images in their own training.

Members of the OMG Systems Modeling Community (SMC) are welcome to use these images with full attribution to Webel IT Australia in presentations and non-commercial activities of the SMC – please unedited and using full resolution downloads (click on image first then Save As).

This slide trail is NOT a SysMLv2 language tutorial! Slides here are offered as is (some without further explanations) in the hope they may be of interest. To learn SysMLv2 attend the Webel SysMLv2 Seminar Workshop group course. Individuals may instead purchase access to the Webel SysMLv2 Online self-study eLearning course with self-test Quizzes to learn at their own pace.

Tags and keywords

Topic level

ESSENTIAL

Keywords

Click on the image to view it full size

Modelling and style

Webel Best Practice: SysMLv2: VERY STRONG RECOMMENDATION: Prefer Webel "Trust the Type" i/o parameter naming and Webel display conventions over verbose parameter names. To find out how attend the Webel SysMLv2 course!

Webel Best Practice: SysMLv2: Prefer graphically clearer explicit binding connectors from/to context boundary parameters over parameter = binding shorthand (and even if = shorthand binding is convenient in code)

SysML2.0: Webel: Suggest the spec needs to clarify through more examples whether binding to a parameter or port (or a directed feature of such) that has NOT been redefined in the binding connector context (is just inherited) is valid [it is]

SysMLv2: Webel: Redefining a parameter or port (or a directed feature of such) in a binding connector's context provides a "clean" binding target (as opposed to binding to an inherited feature). BUT it's not always necessary (confirmed by SysMLv2 samples)

Modelling: In case you insist on using the = binding shorthand form (perfectly valid but graphically less clear than full binding connectors):

Webel: SysMLv2: OPTION: If using = binding shorthand (instead of binding connectors) from/to context boundary parameters try listing the parameters in compartments with their bound values (rather than as parameter boundary "pin" symbols). Saves space!

You could also just list the parameters of takePicture in the upper version (since they aren't bound with bounding connectors anyway). Listing a parameter in a compartment with its feature value also uses less space than showing the parameter with its feature value as a boundary "pin" symbol:

SysMLv2: Cameo: TIP: For parameters the Show Value symbol style is only enabled by default for parameters listed in compartments but you can enable it also on the little parameter "pin" symbols (on the boundary of the owner symbol).

Up next

16. Conditional Succession: Conditional Succession Example-2.sysml

Notes

[DISPLAY, MODELLING, PATTERN, STYLE, TIP, TOOL]{STRONG} Webel Best Practice: SysMLv2: VERY STRONG RECOMMENDATION: Prefer Webel "Trust the Type" i/o parameter naming and Webel display conventions over verbose parameter names. To find out how attend the Webel SysMLv2 course!

[DISPLAY, MODELLING, PATTERN, STYLE, TIP, TOOL]{RECOMMENDED} Webel Best Practice: SysMLv2: Prefer graphically clearer explicit binding connectors from/to context boundary parameters over parameter = binding shorthand (and even if = shorthand binding is convenient in code)

[ISSUE, PROPOSAL]{PROPOSED} SysML2.0: Webel: Suggest the spec needs to clarify through more examples whether binding to a parameter or port (or a directed feature of such) that has NOT been redefined in the binding connector context (is just inherited) is valid [it is]

[MODELLING, OPTION]{OPTION} SysMLv2: Webel: Redefining a parameter or port (or a directed feature of such) in a binding connector's context provides a "clean" binding target (as opposed to binding to an inherited feature). BUT it's not always necessary (confirmed by SysMLv2 samples)

[DISPLAY, MODELLING, PATTERN, STYLE, TIP, TOOL]{RECOMMENDED} Webel: SysMLv2: OPTION: If using = binding shorthand (instead of binding connectors) from/to context boundary parameters try listing the parameters in compartments with their bound values (rather than as parameter boundary "pin" symbols). Saves space!

[CAPABILITY, DISPLAY, FEATURE, MODELLING, TIP, TOOL]{INFORMATIVE} SysMLv2: Cameo: TIP: For parameters the Show Value symbol style is only enabled by default for parameters listed in compartments but you can enable it also on the little parameter "pin" symbols (on the boundary of the owner symbol).

[NAMING]{EDITORIAL} Webel: SysMLv2: Terminology: in some Webel slides and diagrams the little rectangular parameter boundary symbols with directed feature arrows are INFORMALLY called "pins" (borrowing terminology from SysMLv1) but this is NOT a formal SysMLv2 term.

Snippets (quotes/extracts)