Traceability issue with archimate used_by relation

[pano]

Hi all,
There seems to be something weird going on with the tracing in the Traceability window when using an ArchiMate_UsedBy relationship between concepts.

Say, for example, I have the following situation on a Archimate 2.0 Application Layer Diagram:

[Address check service] --used_by--> [Registration service] --used_by--> [Registration form]


If I check the tracing focusing on the [Registration service] i see:

[Registration service]
   - depends on:
      [Registration form]
   - needed by:
      [Address check service]

While what I would expect to see is:

[Registration service]
   - depends on:
      [Address check service]
   - needed by:
      [Registration form]


Am I correct in thinking that this is a bug? Or am I doing something wrong?

[Eve]

No, this is not a bug.

The traceability window doesn't display profiled connector names. What you are seeing is that the ArchiMate used by relationship is based on a dependency relationship, but reads in the opposite direction.

[ducatiross]

No, this is not a bug.

The traceability window doesn't display profiled connector names. What you are seeing is that the ArchiMate used by relationship is based on a dependency relationship, but reads in the opposite direction.

Simon - could the traceability window be changed to use the Profiled connector names ? This would make the window so much more readable and understandable and would stop the potential for people to model 'incorrectly' just to get the relationships to read right in the Traceability window.

This would be a great enhancement.

[pano]

No, this is not a bug.

The traceability window doesn't display profiled connector names. What you are seeing is that the ArchiMate used by relationship is based on a dependency relationship, but reads in the opposite direction.

Ah I see. Thanks for the reply Simon. So the Archimate used by relationship should probably be based on a different relationship.