#37 Sparx EA !0 Implements UML::trace Differently

[Nic Plum]

In Sparx Systems EA version 10 and later a change has been made to the way in which EA implements a UML::Trace. It now correctly extends UML::Abstraction in accordance with the UML 2.1.1 specification.

UML version 2 Superstructure Specification Annex C : Standard Stereotypes Standard Profile L2

UML::trace specialises UML::abstraction at UML v 2.1.1 released 5th February 2007 p690

http://www.omg.org/spec/UML/2.1.1/Superstructure/PDF/

«trace» Classes:: Dependencies Abstraction Specifies a trace relationship between model elements or sets of model elements that represent the same concept in different models. Traces are mainly used for tracking requirements and changes across models. Since model changes can occur in both directions, the directionality of the dependency can often be ignored. The mapping specifies the relationship between the two, but it is rarely computable and is usually informal.

Sparx Systems:

Prior to version 10, Enterprise Architect did not implement the Abstraction connector type at all. This meant that Trace, which is a stereotype defined in the UML specification needed to extend from the class that Abstraction is a specialization of. (Dependency) In version 10 we filled this gap. Abstraction is now available and because of that, Trace is now correctly extending abstraction. The specification has this to say about the notation for Abstraction. "An abstraction relationship is shown as a dependency with an «abstraction» keyword attached to it or the specific predefined stereotype name." Earlier it mentioned the predefined stereotypes as the ones in the Standard Profiles ("Abstraction has predefined stereotypes (such as «derive», «refine», and «trace») that are defined in the Standard Profiles clause. ") As a result, we have taken that to mean that the standard stereotypes will override the keyword, while any further stereotypes will not.'

This requires a change to the UML profile for TRAK (see http://sourceforge.net/p/trakumlprofile/bugs/4/) and it will then require changes to the MDG for TRAK, specifically the Common for TRAK toolbox palette and the Quicklinker.

[Nic Plum]

The 'traces to' connector was changed to a UML Abstraction at version 126.