Recent changes to TraceLink Example

TraceLink Example modified by Andreas Kretschmer

Andreas Kretschmer — Fri, 12 Dec 2014 11:00:38 -0000

TraceLink modified by Andreas Kretschmer

Andreas Kretschmer — Fri, 12 Dec 2014 10:55:43 -0000

--- v3
+++ v4
@@ -31,3 +31,9 @@

 With this change, the resulting graph has a new link
 [[[img src=CheckBalanceView2.jpg]]]
+
+- - - 
+Download
+--------
+[pre Project File](https://sourceforge.net/p/emftrace/wiki/TraceLink/attachment/ModelElementTraceLink.xmi)
+[post Project File](https://sourceforge.net/p/emftrace/wiki/TraceLink/attachment/ModelElementTraceLink%20final.xmi)

TraceLink modified by Andreas Kretschmer

Andreas Kretschmer — Fri, 12 Dec 2014 10:45:30 -0000

--- v2
+++ v3
@@ -3,17 +3,31 @@

 For the illustration there is an example project of a simple bank account system modeled in UML
 [[[img src=Use%20Case.png]]]
+
+
 The model transferred into EMFTrace looks like this:
 [[[img src=ProjectOverview.png]]]
+
 In the model entry you can find all elements from the diagram plus some more from maybe another diagram we want to link here. There are already several *trace links* and *link types* defined in the project which are grouped in container for a better overview.
+
+
 From the diagram we know that it starts with the actor, so right click on this element and select *"show Model Dependencies"*. The view opens with this:
 [[[img src=ActorView.jpg]]]
+
+
 The actor is connected via a trace link that says login to the identify Use Case. A click on it will show us the dependency graph of this element:
 [[[img src=IdentifyView.jpg]]]
+
 The red links are incoming paths over which the element can be accessed or referenced as reference. In this case identify is used only by the Actor and linked to three other Use Cases it allows access to and one fault condition.
+
+
 *Check balance* even has two incoming links and is used by *payout*, also reads the account, but a view in the list of the project shows that there is a class of check balance that isn’t linked here yet. 
 [[[img src=CheckBalanceView.jpg]]][[[img src=CheckBalanceProjectView.jpg]]]
+
+
 So we have to link it. To do so we need a *TraceLink* element. Right click on the Project, select New Model Element and create a *TraceLink* under the *LinkModel* entry. Name the link as you like, but for a better overview choose a name to categories like *“uc check”* for alias the link starts from. The source is the Use Case and target the class it refers to. The description makes the link more clear. Finally the link needs a type displayed in the graph, but the existing are not suitable enough to describe it well. So we create a new one and call it *"implemented by"*
-[[[img src=TraceLinkView1.jpg]]][[[img src=LinkTypes.jpg]]][[[img src=TraceLinkView2.jpg]]]
+[[[img src=TraceLinkView1.jpg]]][[[img src=TraceLinkView2.jpg]]][[[img src=LinkTypes.jpg]]]
+
+
 With this change, the resulting graph has a new link
 [[[img src=CheckBalanceView2.jpg]]]

TraceLink modified by Andreas Kretschmer

Andreas Kretschmer — Fri, 12 Dec 2014 10:40:14 -0000

--- v1
+++ v2
@@ -2,17 +2,18 @@
 ==================

 For the illustration there is an example project of a simple bank account system modeled in UML
-
+[[[img src=Use%20Case.png]]]
 The model transferred into EMFTrace looks like this:
-
+[[[img src=ProjectOverview.png]]]
 In the model entry you can find all elements from the diagram plus some more from maybe another diagram we want to link here. There are already several *trace links* and *link types* defined in the project which are grouped in container for a better overview.
 From the diagram we know that it starts with the actor, so right click on this element and select *"show Model Dependencies"*. The view opens with this:
-
+[[[img src=ActorView.jpg]]]
 The actor is connected via a trace link that says login to the identify Use Case. A click on it will show us the dependency graph of this element:
-
+[[[img src=IdentifyView.jpg]]]
 The red links are incoming paths over which the element can be accessed or referenced as reference. In this case identify is used only by the Actor and linked to three other Use Cases it allows access to and one fault condition.
 *Check balance* even has two incoming links and is used by *payout*, also reads the account, but a view in the list of the project shows that there is a class of check balance that isn’t linked here yet. 
-
+[[[img src=CheckBalanceView.jpg]]][[[img src=CheckBalanceProjectView.jpg]]]
 So we have to link it. To do so we need a *TraceLink* element. Right click on the Project, select New Model Element and create a *TraceLink* under the *LinkModel* entry. Name the link as you like, but for a better overview choose a name to categories like *“uc check”* for alias the link starts from. The source is the Use Case and target the class it refers to. The description makes the link more clear. Finally the link needs a type displayed in the graph, but the existing are not suitable enough to describe it well. So we create a new one and call it *"implemented by"*
-
+[[[img src=TraceLinkView1.jpg]]][[[img src=LinkTypes.jpg]]][[[img src=TraceLinkView2.jpg]]]
 With this change, the resulting graph has a new link
+[[[img src=CheckBalanceView2.jpg]]]

TraceLink modified by Andreas Kretschmer

Andreas Kretschmer — Fri, 12 Dec 2014 10:17:19 -0000

Creating and usage of trace links for model dependencies

For the illustration there is an example project of a simple bank account system modeled in UML

The model transferred into EMFTrace looks like this:

In the model entry you can find all elements from the diagram plus some more from maybe another diagram we want to link here. There are already several trace links and link types defined in the project which are grouped in container for a better overview.
From the diagram we know that it starts with the actor, so right click on this element and select "show Model Dependencies". The view opens with this:

The actor is connected via a trace link that says login to the identify Use Case. A click on it will show us the dependency graph of this element:

The red links are incoming paths over which the element can be accessed or referenced as reference. In this case identify is used only by the Actor and linked to three other Use Cases it allows access to and one fault condition.
Check balance even has two incoming links and is used by payout, also reads the account, but a view in the list of the project shows that there is a class of check balance that isn’t linked here yet.

So we have to link it. To do so we need a TraceLink element. Right click on the Project, select New Model Element and create a TraceLink under the LinkModel entry. Name the link as you like, but for a better overview choose a name to categories like “uc check” for alias the link starts from. The source is the Use Case and target the class it refers to. The description makes the link more clear. Finally the link needs a type displayed in the graph, but the existing are not suitable enough to describe it well. So we create a new one and call it "implemented by"

With this change, the resulting graph has a new link