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
Modelling and style
Modelling: Note how each of the included use cases = binds to only those (here inherited) actors of the owning use case that are relevant. So for example, enter Vehicle binds actors driver and passengers but not environment . (A similar approach applies if an included use case has a different subject, but here it's just vehicle anyway).
SysML2.0: 'Webel Best Practice: SysMLv2: "Trust the Type": When redefining a subject (within any element kind) ALWAYS also include the :Type in the redefinition declaration (even if it's a bit tedious and a bit WET). _SysMLv2 GitHub (2026-06-04): Use Case Usage Example.sysml: Why is the = binding of each of 'passengers', 'driver', and 'environment' inherited from «use case def» 'Provide Transportation' in «use case» 'provide transportation' not invalid recursion?'
Note that in the sample code here the subject of each included use case is made explicit:
use case 'provide transportation' : 'Provide Transportation' {
subject vehicle;
first start;
then include use case 'enter vehicle' : 'Enter Vehicle' {
subject vehicle;
...
Webel recommends the above approach to avoid the following Cameo issue:
Please note also if using the Webel "Trust the Type" modelling recipe:
Notes
[CAPABILITY, DISPLAY, FEATURE, MODELLING, TIP, TOOL]{INFORMATIVE} SysMLv2: Cameo: TIP: The Show Value symbol style is only enabled by default for attributes and parameters (in compartments), but you can Show Value on nearly any feature kind (whether listed in a compartment or displayed as a symbol).