Remove brief description and main description, and change questions to sentences in the design checklist.
diff --git a/libraries/EPF_Practices_Library/practice.tech.evolutionary_design.base/guidances/checklists/design.xmi b/libraries/EPF_Practices_Library/practice.tech.evolutionary_design.base/guidances/checklists/design.xmi
index b7ac323..927cc71 100644
--- a/libraries/EPF_Practices_Library/practice.tech.evolutionary_design.base/guidances/checklists/design.xmi
+++ b/libraries/EPF_Practices_Library/practice.tech.evolutionary_design.base/guidances/checklists/design.xmi
@@ -1,34 +1,30 @@
<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ContentDescription xmi:version="2.0"
- xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.4/uma.ecore"
- xmlns:epf="http://www.eclipse.org/epf" epf:version="1.2.0" xmi:id="_YIYIYMM1EdmSIPI87WLu3g"
- name="design,_0XSzsMlgEdmt3adZL5Dmdw" guid="_YIYIYMM1EdmSIPI87WLu3g" changeDate="2007-03-18T19:57:27.416-0400"
+ xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.5/uma.ecore"
+ xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmlns:rmc="http://www.ibm.com/rmc"
+ rmc:version="7.5.0" xmi:id="_YIYIYMM1EdmSIPI87WLu3g"
+ name="design,_0XSzsMlgEdmt3adZL5Dmdw" guid="_YIYIYMM1EdmSIPI87WLu3g" changeDate="2008-08-11T14:21:25.062-0700"
version="1.0.0">
- <mainDescription><p> The items in this checklist represent good practices for creating and communicating 
- a robust design. Try to address every item to the greatest extent possible to 
- create the best design. It may not be possible to address every item, and you 
- may be able to address some items to only a limited extent. In these cases, 
- be sure that there are good reasons for only partially addressing an item or 
- not addressing an item at all. </p>
-<p> Design can take place every day. Use this checklist regularly to&nbsp;ensure&nbsp;a 
- robust, consistent, and understandable design. Make the design good enough for 
- the specific goals being addressed by using this checklist to identify areas 
- that have been skipped, ignored, or not sufficiently addressed. </p></mainDescription>
- <sections xmi:id="_sO-NINVUEduaE6F4-SvXzg" name="Is the design understandable?"
- guid="_sO-NINVUEduaE6F4-SvXzg">
+ <sections xmi:id="_sO-NINVUEduaE6F4-SvXzg" name="The design is understandable" guid="_sO-NINVUEduaE6F4-SvXzg">
<sectionDescription><ul>
- <li> Is the design organized in a way that team members can easily find the 
- information that they're looking for? </li>
- <li> Is the design as simple as it can be, while still fulfilling the objectives 
- of the design and giving sufficient direction to implementers? </li>
- <li> Is the design neither too simple nor too advanced? The design sophistication 
- should be appropriate to the experience level of other team members and technical 
- stakeholders. This applies to both the concept and the representation of the 
- design. </li>
- <li> Does the design express what the designer intends to express? </li>
+ <li>
+ Is the design organized in a way that team members can easily find the information that they're looking for?
+ </li>
+ <li>
+ Is the design as simple as it can be, while still fulfilling the objectives of the design and giving sufficient
+ direction to implementers?
+ </li>
+ <li>
+ Is the design neither too simple nor too advanced? The design sophistication should be appropriate to the
+ experience level of other team members and technical stakeholders. This applies to both the concept and the
+ representation of the design.
+ </li>
+ <li>
+ Does the design express what the designer intends to express?
+ </li>
</ul></sectionDescription>
</sections>
- <sections xmi:id="_7DUXMNTQEduaE6F4-SvXzg" name="Is the design consistent?" guid="_7DUXMNTQEduaE6F4-SvXzg">
+ <sections xmi:id="_7DUXMNTQEduaE6F4-SvXzg" name="The design is consistent" guid="_7DUXMNTQEduaE6F4-SvXzg">
<sectionDescription><ul>
<li>
Does the design follow any design standards?
@@ -48,7 +44,7 @@
</li>
</ul></sectionDescription>
</sections>
- <sections xmi:id="_V_LgsNTREduaE6F4-SvXzg" name="Is the design maintainable?" guid="_V_LgsNTREduaE6F4-SvXzg">
+ <sections xmi:id="_V_LgsNTREduaE6F4-SvXzg" name="The design is maintainable" guid="_V_LgsNTREduaE6F4-SvXzg">
<sectionDescription><ul>
<li>
Is the design structured well enough to be maintained?
@@ -62,70 +58,87 @@
</li>
</ul></sectionDescription>
</sections>
- <sections xmi:id="_ySbT4NTREduaE6F4-SvXzg" name="Is the design traceable?" guid="_ySbT4NTREduaE6F4-SvXzg">
+ <sections xmi:id="_ySbT4NTREduaE6F4-SvXzg" name="The design is traceable" guid="_ySbT4NTREduaE6F4-SvXzg">
<sectionDescription><ul>
- <li> Is it clear how the design elements relate to the requirements? This does 
- not need to involve a heavyweight traceability strategy, but is there some 
- way to figure out what part of the design supports a particular requirement? 
- </li>
- <li> It what portions of the implementation support each design element clear? 
- </li>
+ <li>
+ Is it clear how the design elements relate to the requirements? This does not need to involve a heavyweight
+ traceability strategy, but is there some way to figure out what part of the design supports a particular
+ requirement?
+ </li>
+ <li>
+ It what portions of the implementation support each design element clear?
+ </li>
</ul></sectionDescription>
</sections>
- <sections xmi:id="_tywgENTQEduaE6F4-SvXzg" name="Does the design reflect the architectural objectives of the system?"
+ <sections xmi:id="_tywgENTQEduaE6F4-SvXzg" name="The design reflects the architectural objectives of the system"
guid="_tywgENTQEduaE6F4-SvXzg">
<sectionDescription><ul>
- <li> Does the design conform to the architecture as specified? </li>
- <li>Does it apply the architectural patterns appropriately? </li>
- <li> Are Architectural Mechanisms used appropriately? Are they applied in all 
- applicable circumstances? </li>
+ <li>
+ Does the design conform to the architecture as specified?
+ </li>
+ <li>
+ Does it apply the architectural patterns appropriately?
+ </li>
+ <li>
+ Are Architectural Mechanisms used appropriately? Are they applied in all applicable circumstances?
+ </li>
</ul></sectionDescription>
</sections>
- <sections xmi:id="_nMogoNTQEduaE6F4-SvXzg" name="Are the design elements modular?"
+ <sections xmi:id="_nMogoNTQEduaE6F4-SvXzg" name="The design elements are modular"
guid="_nMogoNTQEduaE6F4-SvXzg">
<sectionDescription><ul>
- <li> Do the design elements have high internal cohesion? Does the degree of 
- interaction within the unit demonstrate that all of the internal parts belong 
- together? </li>
- <li> Do the design elements have low coupling? Is there minimal interdependence 
- between design elements? When design elements depend upon one another, is 
- this done as simply as possible and in such a way that the client element 
- will not be affected by changes to the internal parts of the supplier element? 
- </li>
- <li> Are the design elements defined with&nbsp;abstract interfaces in ways that 
- changes can be made to the internal implementation without affecting client 
- design elements? </li>
- <li> Does each design element represent a clearly defined abstraction? </li>
+ <li>
+ Do the design elements have high internal cohesion? Does the degree of interaction within the unit demonstrate that
+ all of the internal parts belong together?
+ </li>
+ <li>
+ Do the design elements have low coupling? Is there minimal interdependence between design elements? When design
+ elements depend upon one another, is this done as simply as possible and in such a way that the client element will
+ not be affected by changes to the internal parts of the supplier element?
+ </li>
+ <li>
+ Are the design elements defined with&nbsp;abstract interfaces in ways that changes can be made to the internal
+ implementation without affecting client design elements?
+ </li>
+ <li>
+ Does each design element represent a clearly defined abstraction?
+ </li>
</ul></sectionDescription>
</sections>
- <sections xmi:id="_19E2INTQEduaE6F4-SvXzg" name="Can the system be implemented from the information in the design?"
+ <sections xmi:id="_19E2INTQEduaE6F4-SvXzg" name="The system can be implemented from the information in the design"
guid="_19E2INTQEduaE6F4-SvXzg">
<sectionDescription><ul>
- <li> Has sufficient detail been included to direct the implementation? </li>
- <li> Does the design constrain the implementation only as much as necessary? 
- Does the design allow freedom for the implementer to implement it appropriately? 
- </li>
- <li> Is the design feasible? Is it a design that can be reasonably implemented 
- by the team by using the technologies selected within the timeframe of the 
- project? </li>
+ <li>
+ Has sufficient detail been included to direct the implementation?
+ </li>
+ <li>
+ Does the design constrain the implementation only as much as necessary? Does the design allow freedom for the
+ implementer to implement it appropriately?
+ </li>
+ <li>
+ Is the design feasible? Is it a design that can be reasonably implemented by the team by using the technologies
+ selected within the timeframe of the project?
+ </li>
</ul></sectionDescription>
</sections>
- <sections xmi:id="_F_AWwNTTEduaE6F4-SvXzg" name="Does the design provide enough information for developer testing?"
+ <sections xmi:id="_F_AWwNTTEduaE6F4-SvXzg" name="The design provide enough information for developer testing"
guid="_F_AWwNTTEduaE6F4-SvXzg">
<sectionDescription><ul>
- <li> Does the design provide enough information for developer test design? Are 
- the expected behavior and constraints on the methods clear? </li>
- <li> Are the collaborations between design elements clear enough to create integration 
- tests? </li>
+ <li>
+ Does the design provide enough information for developer test design? Are the expected behavior and constraints on
+ the methods clear?
+ </li>
+ <li>
+ Are the collaborations between design elements clear enough to create integration tests?
+ </li>
</ul></sectionDescription>
</sections>
- <sections xmi:id="_upZp0NT0EduaE6F4-SvXzg" name="Does the design describe the system at the appropriate level of abstraction?"
+ <sections xmi:id="_upZp0NT0EduaE6F4-SvXzg" name="The design describe the system at the appropriate level of abstraction"
guid="_upZp0NT0EduaE6F4-SvXzg">
- <sectionDescription>Does the design describe the system at the appropriate level of abstraction given 
-the objectives? This usually means that the system is described at several different 
-levels of abstraction and from different perspectives.</sectionDescription>
+ <sectionDescription>Does the design describe the system at the appropriate level of abstraction given the objectives? This usually means that
+the system is described at several different levels of abstraction and from different perspectives.</sectionDescription>
</sections>
- <sections xmi:id="_Nqih0NVREduaE6F4-SvXzg" name="Does the design support a coarse-grained perspective of the system?"
+ <sections xmi:id="_Nqih0NVREduaE6F4-SvXzg" name="The design supports a coarse-grained perspective of the system"
guid="_Nqih0NVREduaE6F4-SvXzg">
<sectionDescription><ul>
<li>
diff --git a/libraries/EPF_Practices_Library/practice.tech.evolutionary_design.base/plugin.xmi b/libraries/EPF_Practices_Library/practice.tech.evolutionary_design.base/plugin.xmi
index b137bd1..ca71007 100644
--- a/libraries/EPF_Practices_Library/practice.tech.evolutionary_design.base/plugin.xmi
+++ b/libraries/EPF_Practices_Library/practice.tech.evolutionary_design.base/plugin.xmi
@@ -2,8 +2,8 @@
<xmi:XMI xmi:version="2.0"
xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.5/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmlns:rmc="http://www.ibm.com/rmc"
+ rmc:version="7.5.0">
<org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_Z20lULPPEduocbW-TPTq7A"
guid="_Z20lULPPEduocbW-TPTq7A">
<resourceDescriptors xmi:id="_nGJZ0vL5Edm6Nvont3uinw" id="_NrC20qeqEdmKDbQuyzCoqQ"
@@ -131,8 +131,7 @@
<presentation xmi:id="-giTBOvJczHXweRzBQEo-7A" href="uma://-giTBOvJczHXweRzBQEo-7A#-giTBOvJczHXweRzBQEo-7A"/>
</contentElements>
<contentElements xsi:type="org.eclipse.epf.uma:Checklist" xmi:id="_0XSzsMlgEdmt3adZL5Dmdw"
- name="design" guid="_0XSzsMlgEdmt3adZL5Dmdw" presentationName="Design"
- briefDescription="This checklist provides questions to verify that the design is created in a consistent and complete manner.">
+ name="design" guid="_0XSzsMlgEdmt3adZL5Dmdw" presentationName="Design">
<presentation xmi:id="_YIYIYMM1EdmSIPI87WLu3g" href="uma://_YIYIYMM1EdmSIPI87WLu3g#_YIYIYMM1EdmSIPI87WLu3g"/>
</contentElements>
<contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="_skRykMuYEdyRPtFYRAKVDg"
