commit 1cdcbe27fc9ebfe6072284ab57f46100066e0c0b
author bmacisaac <bmacisaac> Mon Mar 28 20:27:29 2011 +0000
committer bmacisaac <bmacisaac> Mon Mar 28 20:27:29 2011 +0000
tree b474f580e478b7c4c2cbbce194947b18394b291b
parent c103655b6188378c5b09003a021f93e7d1441434

Bug 243961

epf_prac_151/practice.tech.evolutionary_design.base/workproducts/design.xmi

diff --git a/epf_prac_151/practice.tech.evolutionary_design.base/workproducts/design.xmi b/epf_prac_151/practice.tech.evolutionary_design.base/workproducts/design.xmi
index aeb823f..7b7d660 100644
--- a/epf_prac_151/practice.tech.evolutionary_design.base/workproducts/design.xmi
+++ b/epf_prac_151/practice.tech.evolutionary_design.base/workproducts/design.xmi
@@ -1,15 +1,17 @@
 <?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="_zxB-QKYcEdmvhNXG0Oc2uA" name="design,_0WuL8slgEdmt3adZL5Dmdw" guid="_zxB-QKYcEdmvhNXG0Oc2uA" changeDate="2008-08-15T00:29:20.000-0700" version="1.0.0">
+<org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="_zxB-QKYcEdmvhNXG0Oc2uA" name="design,_0WuL8slgEdmt3adZL5Dmdw" guid="_zxB-QKYcEdmvhNXG0Oc2uA" changeDate="2011-03-28T13:03:35.495-0700" version="1.0.0">
   <mainDescription>&lt;p>&#xD;
-    This product can describe multiple static and dynamic views of the system for examination. Although various views may&#xD;
-    focus on divergent, seemingly independent issues of how the system will be put together and work, they should fit&#xD;
-    together without contradiction.&#xD;
+    This work product describes the elements that will make up the implemented system. It communicates abstractions of&#xD;
+    particular portions of the implementation.&#xD;
 &lt;/p>&#xD;
 &lt;p>&#xD;
-    It describes the elements that will make up the implemented system. It communicates abstractions of particular portions&#xD;
-    of the implementation and can describe an&amp;nbsp;encapsulated subsystem, a high-level analysis of the system, a view of&#xD;
-    the system in only one context, or other perspectives that explain a solution to a specific problem that needs to be&#xD;
-    communicated.&#xD;
+    While architecture focuses on interfaces, patterns, and key decisions, the design fleshes out the technical details in&#xD;
+    readiness for implementation, or as part of implementation.&#xD;
+&lt;/p>&#xD;
+&lt;p>&#xD;
+    This product can describe multiple static and dynamic views of the system for examination. Although various views may&#xD;
+    focus on divergent, seemingly independent issues of how the system will be put together and work, they should fit&#xD;
+    together without contradiction.&lt;br />&#xD;
 &lt;/p></mainDescription>
   <purpose>&lt;p>&#xD;
     &amp;nbsp;Describe the&amp;nbsp;elements of the system&amp;nbsp;so&amp;nbsp;they can be examined and understood in ways&#xD;