(c) Bruce Powel Douglass, Ph.D. 2019

Apr 30

Shorthand notation representing many composite associations with a single black diamond in Rhapsody

2 comments

Hello!

 

I am quite new to SysML and Rhapsody and I am trying to figure out how to use the compact single black-diamond notation used in figure D. 18 of the SysML 1.4 standard:

 

 

When I create the corresponding diagram in Rhapsody there will be one black diamond per directed composition:

 

 

Also, I am reading in A Practical Guide to SysMLp121 that

 

A shorthand notation can be used to represent a block that has many composite associations by showing a single black diamond with a series of lines connecting to the part ends of each composite association

Do anyone know if this is possible to do in Rhapsody?

 

Many thanks in advance!

Can't do that in Rhapsody. Almost all relations are binary between elements (such as classes); there is an end1 and an end2. So while I can see some advantage to such syntactic sugaring, Rhapsody doesn't support it. Note that Rhapsody does support this with the tree notational style (Line Shape > Tree) for generalization (only). If you look closely, the example in the spec actually looks like it was drawn by carefully overlaying the lines rather than actually employing the notational shorthand of which you speak.

Okay thanks! It really bothered me that I didn't understand how to do this, now I know it's not me.

New Posts
  • Hi Bruce, please can you provide the models of roadrunner Intersection Controller described in "Real-time UML Workshop for Embedded Systems", too? Thank you! Best regards Matthias
  • Dear Bruce, I realized that there is a difference between native dependecies with stereotype "trace" and trace relation between Requirements and UseCases. Both appearing different in the model repository and behave different in queries. In Rhapsody I can change both with change to "dependency " or "trace". I work on object model diagrams with UML profile. Can you explain the difference, because I have trouble with queries and matrix layouts then? By the way: I realized that you use different stereotype as relation between use cases and requirement: trace vs. allocate vs. satisfy Thank you! Best regards Matthias
  • This forum is intended to be a place for folks to discuss Rhapsody usage, concerns, issues, and questions. This is not meant to replace technical support but hopefully a place where people can share ideas and raise questions.