DISCLAIMER: The lower diagram is a specific modelling experiment "provocation" exploring how effectively (or not) one can use strongly relationship based graphical modelling in SysMLv2. It is NOT a modelling practice recommendation!

Practical modelling concerns are critical for the uptake of SysMLv2, and this topic is very important to me professionally.

In some of the diagrams in this slide trail (and in the Webel SysMLv2 course) including some of the supporting SysMLv2 machinery was educationally helpful (including also relationships from the user model elements to metaclasses and such); here, with this quite complex modelling target, it is not so effective.

Indeed, even the more "minimal" upper diagram is a lot of information for non-SysMLv2 fluent stakeholders to take in, and unfortunately, because AFAICT Cameo 2026xHF2 does not have a compartment for listing basic refs on symbols, one has to use symbols in cases where simply listing the element along with any feature values would suffice and be more concise.

The lower diagram also includes some tips on how one might Divide & Conquer it, including:

Use mostly compartments (but does not work with basic refs in Cameo)
Use separate Views for different aspects.
If you want to explore relationships to specific metaclass of model library elements use separate dedicated non-stakeholder Views.

If you've every attended a Webel SysML course or you've seen any of the online tutorials for SysML, you'll know that I am a HUGE fan of just using black and white styles (no MagicDraw or Cameo colours) and only using colours for special highlights, such as my favourites blue or magenta for symbol outlines.

Webel Best Practice: SysMLv2: STRONGLY recommend black on white style with colours (best only for symbol outlines) only used for special highlighting. [READ FOR INSTRUCTIONS for b/w in Cameo SysMLv2]

That said, not everyone is such a fan of magenta (or may have some irrational fear of things that a "pinkish") but blue and magenta work brilliantly together for contrast.

In any case, overuse of colours is a Modelling Anti-Pattern. One quickly runs out of distinguishing colours (and it can also exclude readers with Colour Deficiency Conditions).

It can also undermine the effectiveness of using the widely recognised orange for warnings and red for errors or bugs.

If you find yourself using lots of different colours it's a hint to Divide & Conquer using separate views of different aspects of the same system!

HINT: Patent Offices require mostly Black & White figures

BTW Most Webel SysMLv2 slides use a different colour policy for KerML metaclasses and SysMLv2 metamodel elements to distinguish them:

Webel SysMv2 modelling convention for tutorials and training. Metaclasses and elements from the KerML and SysMLv2 machinery are white on black or white on strong "darker" colours (blue, magenta, purple etc.) to distinguish them from user model elements

The trend in SysMLv2 is to more compartment oriented representations

For those of use who have used SysML for decades, strongly associative modelling is not only easy to read, it offers some very powerful capabilities that a more "text like" or "code like" approach cannot. But not everyone has used SysML for decades.

In the Webel SysMLv2 course slides a decision was made to mostly indeed use associate modelling with relationships, in order for students to become more familiar with the relationships.

But the wider industry trend is towards more code-like representations, perhaps in part because SysMv2 itself now has a textual representation code.