Tags and keywords
Special modelling note. This View deliberately shows here nearly everything in one diagram and for educational purposes employs a heavily relational approach (which is not suitable for stakeholder audience not familiar with SysMLv2 notations).
It serves also as an example of a typical candidate for "Divide & Conquer: strategies. Much shown here is already shown in the related definition-level View of the previous slide. Some of the features could instead be shown just as inherited features. However, the lack of a basic refs compartment in Cameo makes it difficult to show all of the feature values compactly in compartments.
This trail is NOT a SysMLv2 tutorial, but it's worth pointing out a few aspects of the above diagram and the underlying model and code (see also the GitHub link below).
The «individual occurrence def» TestSystem acts as a "mixin", required so that testSystem may be an «individual occurrence». Likewise, each «in individual occurrence» testVehicle1 and testVehicle2 must be feature typed by a corresponding «individual occurrence def» (in this case each specializing Vehicle using subclassification).
These modelling requirements of course make both the code and any views a bit more complicated, but are important aspects of the individuals machinery of SysMLv2, which addresses well many of the shortcomings of SysMLv1 for capturing these concepts.