commit 7778715b9f636377812cdb385bc8bfb2904249a6
author jruehlin <jruehlin> Thu Aug 14 15:21:47 2008 +0000
committer jruehlin <jruehlin> Thu Aug 14 15:21:47 2008 +0000
tree 240872e539827ade3ada581999a943c518b5fa35
parent fe61fac5bfab8d0a2e431a2c017be47ffac5b8cd

https://bugs.eclipse.org/bugs/show_bug.cgi?id=240040

libraries/EPF_Practices_Library/practice.tech.evolutionary_design.base/guidances/templates/design.xmi

diff --git a/libraries/EPF_Practices_Library/practice.tech.evolutionary_design.base/guidances/templates/design.xmi b/libraries/EPF_Practices_Library/practice.tech.evolutionary_design.base/guidances/templates/design.xmi
index 85fae34..e5cbaa0 100644
--- a/libraries/EPF_Practices_Library/practice.tech.evolutionary_design.base/guidances/templates/design.xmi
+++ b/libraries/EPF_Practices_Library/practice.tech.evolutionary_design.base/guidances/templates/design.xmi
@@ -3,7 +3,8 @@
     xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.5/uma.ecore"
     xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.0" xmlns:epf="http://www.eclipse.org/epf"
     epf:version="1.5.0" xmi:id="-giTBOvJczHXweRzBQEo-7A"
-    name="new_template,_EOPcMAMUEdylNddAObilIA" guid="-giTBOvJczHXweRzBQEo-7A" changeDate="2008-08-12T18:15:18.342-0700">
+    name="new_template,_EOPcMAMUEdylNddAObilIA" guid="-giTBOvJczHXweRzBQEo-7A" changeDate="2008-08-14T08:20:04.979-0700"
+    version="7.5.0">
   <mainDescription>&lt;p>&#xD;
     This template describes how the design can be organized to be understood from multiple perspectives. It also provides&#xD;
     suggestions for how patterns and descriptions of small, reusable interactions can be used to minimize redundancy.&#xD;
@@ -44,7 +45,7 @@
 &lt;/p>&#xD;
 &lt;p style=&quot;COLOR: #0000ff&quot;>&#xD;
     When capturing dynamic descriptions of behavior, look for reusable chunks of behavior that you can reference to&#xD;
-    simplify the design of the use-case realizations.&#xD;
+    simplify the design of the requirement realizations.&#xD;
 &lt;/p>&#xD;
 &lt;p style=&quot;COLOR: #0000ff&quot;>&#xD;
     You can break this section down into lower-level subsections to describe lower-level, encapsulated subsystems.]&#xD;
@@ -90,21 +91,21 @@
 &lt;/h3>&#xD;
 &lt;p style=&quot;COLOR: #0000ff&quot;>&#xD;
     [Describe the participating design elements from a static perspective, giving details such as behavior, relationships,&#xD;
-    and attributes relevant to this use-case realization.]&#xD;
+    and attributes relevant to this realization.]&#xD;
 &lt;/p>&#xD;
 &lt;h3>&#xD;
     Basic scenario&#xD;
 &lt;/h3>&#xD;
 &lt;p style=&quot;COLOR: #0000ff&quot;>&#xD;
-    [For the main flow, describe how instances of the design elements collaborate to realize the use case. When using UML,&#xD;
-    this can be done with collaboration diagrams (sequence or communication).]&#xD;
+    [For the main flow, describe how instances of the design elements collaborate to realize the requirements. When using&#xD;
+    UML, this can be done with collaboration diagrams (sequence or communication).]&#xD;
 &lt;/p>&#xD;
 &lt;h3>&#xD;
     Additional scenarios&#xD;
 &lt;/h3>&#xD;
 &lt;p style=&quot;COLOR: #0000ff&quot;>&#xD;
-    [For other scenarios that must be described to convey an appropriate amount of information about how the use-case&#xD;
-    behavior will be realized, describe how instances of the design elements collaborate to realize the use case. When&#xD;
+    [For other scenarios that must be described to convey an appropriate amount of information about how the requirement&#xD;
+    behavior will be realized, describe how instances of the design elements collaborate to realize the requirement. When&#xD;
     using UML, you can do this with collaboration diagrams (sequence or communication).]&#xD;
 &lt;/p></mainDescription>
 </org.eclipse.epf.uma:GuidanceDescription>