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

matthias
Jun 28, 2018

dependencies vs. trace

1 comment

Edited: Jun 29, 2018

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

Bruce Douglass
Jul 1, 2018

Trace is a specific kind (stereotype) of dependency, so in some sense it doesn't matter. However, trace is specified in the HarmonySE profile as a new metaclass ("New Term") which means that it can (and, in fact, does) provide tables specifically for that relation. Using the HarmonySE trace means that you can directly create tables / matrices with just that specific kind of dependency and not others which might include Usage. The UML standard identifies about 15 different kinds of dependency. Adding a specific New Term means that I can filter tables or matrices to just show relations of only that kind. The reason why you might want to use the one from the HarmonySE profile is that it comes with pre-defined matrices for that. You can always define your own tables, though.

0
New Posts
  • matthias
    Oct 21

    Roadrunner Model of RTUML Workshop

    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
  • markus.nordstrand
    May 2

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

    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 SysML p121 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!
  • Bruce Douglass
    Mar 7, 2018

    Welcome to the Rhapsody Forum

    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.