SPARXEA Inconsistency in Implementing Archimate?

[gpanchavati]

Hello, I am a newbie to the Sparx EA, and encountered a modelilng inconsistency with SparxEA implementation of the Archimate modeling notation.  

If you explore the sample file illustrating the usage of archimate template "using-archimate-in-enterprise-architect.eap", this inconsistency is evident.  Here is the link for that file and the short video:

http://www.sparxsystems.com/resources/webinar/partners/archimate/archimate-introduction-hippo.html

If you drill down to the Enterprise Architecture>Layered Viewpoint and open the Layered Viewpoint diagram, it shows the 3 layered view.  The issue is this:

The diagram shows the relationships (arrow directions) exactly as recommended by Archimate convention.  For example, the Order Processing service is realized by the Flower Sales Application which uses the Data Storing Service which in turn is realized by the RDBMS.

But a traceability check on the Order Processing Service reads incorrectly and shows that the Order Processing Service depends on the Record Orders business Process and it is needed by the Flower Sales Application.  It seems like the arrows  should be reversed so the traceability reads correctly.

If you reverse the arrows, the traceability check correctly shows that the Order Processing Service is needed by the Record Orders business process and it is dependent on the the Flower Sales Application component.  

If you reverse the arrows, it contradicts the Archimate representation.  I may have to compromise on this at least for correctness from the traceability standpoint.

Is this a bug?  Any suggestions?

Thanks for the help,

Gopal

[Eve]

The traceability window isn't customized by any profile. Unfortunately ArchiMate uses a reading direction opposite to the base UML connectors, but with terms similar enough to make it sound like the intention was the same.

[gpanchavati]

Thanks Simon.  That helps.