|Traces [message #563271]
||Mon, 09 November 2009 19:48
| No real name
Registered: November 2009
first, well done, GEF3d look quite amazing.
I have a question about traces and was wondering to what objects are traces associated with?
Say I have a UML Class object in on 2D diagram and another UML Class ojbect in another 2D diagram. it looks like you can relate those two objects using a Trace. It doesn't seem like the Trace belong to or is associated with any of the 2D diagrams. where is it specified?
My apologies if this question is stupid. I'm very new to GEF3D
|Re: Traces [message #563295 is a reply to message #563271]
||Tue, 10 November 2009 04:45
|| Jens von Pilgrim
Registered: July 2009
On 2009-11-10 01:48:34 +0100, <firstname.lastname@example.org> said:
> I have a question about traces and was wondering to what objects are
> traces associated with?
> Say I have a UML Class object in on 2D diagram and another UML Class
> ojbect in another 2D diagram. it looks like you can relate those two
> objects using a Trace. It doesn't seem like the Trace belong to or is
> associated with any of the 2D diagrams. where is it specified?
Actually, this is not really a GEF3D related issue, but a modeling one.
I have explained traces, how they are stored (in a separate model), and
how they are visualized with GEF3D in the following paper:
Pilgrim, Jens von ; Vanhooff, Bert ; Schulz-Gerlach, Immo ; Berbers,
Yolande: Constructing and Visualizing Transformation Chains. In:
Schieferdecker, Ina (Hrsg.) ; Hartman, Alan (Hrsg.): Model Driven
Architecture — Foundations and Applications. 4th European Conference,
ECMDA-FA 2008, Berlin, Germany, June 9-13, Proceedings Bd. 5095.
Springer-Verlag. – ISBN 978–3–540–69095–5, 17–32. URL:
That is, you need three models: UML model 1, UML model 2, and a trace
model. The trace model inter-connects elements of model 1 and 2. In
order to "draw" the connection with GEF3D, two patterns or classes may
help you: the Connected Element Adpater and the
UnidirectConnectionEditPart. The first one is a more sophisticated
pattern which can always be applied, the second one is a class which is
easier to use but it requires the connected edit parts to support
anchors for _any_ connections. I have documented that in the JavaDoc,
see package org.eclipse.gef3d.ext.intermodel. In order to mark your
trace model (or better to say its edit part and figure) as an
inter-model, you can use the interfaces IInterModelRootEditPart and
Regarding traces: As a matter of fact, traces and traceability are
subject of many papers in the area of model driven
development/engineering, and there will even be a special issue of the
"Software and Systems Modeling" journal on traceability (I don't know
when it will be published, I assume in a couple of weeks). If you are
interested in that topic, you may have a look at the workshop series
"ECMDA Traceability Workshop (ECMDA-TW)"
(http://www.modelbased.net/ecmda-traceability/) or "Workshop on
Traceability in Emerging Forms of Software Engineering (TEFSE)"
Powered by FUDForum
. Page generated in 0.01924 seconds