Minor consistency fixes as part of overall review.
diff --git a/libraries/EPF_Practices_Library/core.tech.common.base/guidances/checklists/developer_test.xmi b/libraries/EPF_Practices_Library/core.tech.common.base/guidances/checklists/developer_test.xmi
index efe6de2..5c96f91 100644
--- a/libraries/EPF_Practices_Library/core.tech.common.base/guidances/checklists/developer_test.xmi
+++ b/libraries/EPF_Practices_Library/core.tech.common.base/guidances/checklists/developer_test.xmi
@@ -1,10 +1,11 @@
<?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.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="-zD7XGTc4k1GFe4PvMKlkKA"
- name="new_checklist,_dxaPUF-BEd2T0JdVjRyaQA" guid="-zD7XGTc4k1GFe4PvMKlkKA" changeDate="2008-07-31T21:23:44.406-0700">
- <sections xmi:id="_rZ3pEF-BEd2T0JdVjRyaQA" name="Is the test coverage is acceptable?"
+ 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="-zD7XGTc4k1GFe4PvMKlkKA"
+ name="new_checklist,_dxaPUF-BEd2T0JdVjRyaQA" guid="-zD7XGTc4k1GFe4PvMKlkKA" changeDate="2008-07-31T21:23:44.406-0700"
+ version="7.5.0">
+ <sections xmi:id="_rZ3pEF-BEd2T0JdVjRyaQA" name="The test coverage is acceptable"
guid="_rZ3pEF-BEd2T0JdVjRyaQA">
<sectionDescription><p>
100% test coverage is the ideal, but there may occassionally be places where it's impossible to achieve total coverage.
@@ -12,20 +13,18 @@
on a developer's machine. Every reasonable effort should be made to cover all the code.
</p></sectionDescription>
</sections>
- <sections xmi:id="_7ncD4F-BEd2T0JdVjRyaQA" name="Are developer test names or IDs are consistent with project naming conventions?"
+ <sections xmi:id="_7ncD4F-BEd2T0JdVjRyaQA" name="Developer test names or IDs are consistent with project naming conventions"
guid="_7ncD4F-BEd2T0JdVjRyaQA"/>
- <sections xmi:id="_0nZTIF-CEd2T0JdVjRyaQA" name="Is the test logic is correct?"
- guid="_0nZTIF-CEd2T0JdVjRyaQA">
+ <sections xmi:id="_0nZTIF-CEd2T0JdVjRyaQA" name="The test logic is correct" guid="_0nZTIF-CEd2T0JdVjRyaQA">
<sectionDescription><p>
Assure the test themselves are correct.
</p></sectionDescription>
</sections>
- <sections xmi:id="_KfXE8F-DEd2T0JdVjRyaQA" name="Is the branch coverage is acceptable."
+ <sections xmi:id="_KfXE8F-DEd2T0JdVjRyaQA" name="Branch coverage is acceptable."
guid="_KfXE8F-DEd2T0JdVjRyaQA">
<sectionDescription>Assure conditional logic been tested in all combinations.<br /></sectionDescription>
</sections>
- <sections xmi:id="_UNewEF-DEd2T0JdVjRyaQA" name="Is the test is easy to maintain?"
- guid="_UNewEF-DEd2T0JdVjRyaQA">
+ <sections xmi:id="_UNewEF-DEd2T0JdVjRyaQA" name="The test is easy to maintain" guid="_UNewEF-DEd2T0JdVjRyaQA">
<sectionDescription>Has the test been implemented to account for expected ongoing changes in the application state, such as system date fields,
transaction numbers, and so on?<br /></sectionDescription>
</sections>
diff --git a/libraries/EPF_Practices_Library/core.tech.common.base/guidances/checklists/implementation.xmi b/libraries/EPF_Practices_Library/core.tech.common.base/guidances/checklists/implementation.xmi
index 20fef1d..ec3f32f 100644
--- a/libraries/EPF_Practices_Library/core.tech.common.base/guidances/checklists/implementation.xmi
+++ b/libraries/EPF_Practices_Library/core.tech.common.base/guidances/checklists/implementation.xmi
@@ -1,8 +1,8 @@
<?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" xmlns:rmc="http://www.ibm.com/rmc"
- rmc:version="7.2.0" xmi:id="-cev1w72zE7XqPYsSv19prg"
+ 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="-cev1w72zE7XqPYsSv19prg"
name="new_checklist,_OhJKUNWsEduaE6F4-SvXzg" guid="-cev1w72zE7XqPYsSv19prg" changeDate="2007-07-25T12:48:32.932-0700"
version="1.0.0">
<mainDescription><p>
@@ -20,18 +20,24 @@
Appropriate divergence from the quality criteria described here could be worthy of a comment in the implementation so
that developers examining the code in the future know why the exception occurred.
</p></mainDescription>
- <sections xmi:id="_etwusZ01EdyQ3oTO93enUw" name="Does the implementation conform to the architecture and design?"
+ <sections xmi:id="_etwusZ01EdyQ3oTO93enUw" name="The implementation conforms to the architecture and design"
guid="_etwusZ01EdyQ3oTO93enUw">
<sectionDescription><ul>
- <li> Is the implementation structured as specified in the design? </li>
- <li> Are all of the functions in the design implemented? </li>
- <li> Are all of the interfaces in the design implemented according to their 
- specifications? </li>
- <li> Does the implementation adhere to all design and architectural constraints? 
- </li>
+ <li>
+ Is the implementation structured as specified in the design?
+ </li>
+ <li>
+ Are all of the functions in the design implemented?
+ </li>
+ <li>
+ Are all of the interfaces in the design implemented according to their specifications?
+ </li>
+ <li>
+ Does the implementation adhere to all design and architectural constraints?
+ </li>
</ul></sectionDescription>
</sections>
- <sections xmi:id="_etwutJ01EdyQ3oTO93enUw" name="Is the implementation testable?"
+ <sections xmi:id="_etwutJ01EdyQ3oTO93enUw" name="The implementation is testable"
guid="_etwutJ01EdyQ3oTO93enUw">
<sectionDescription><ul>
<li>
@@ -42,7 +48,7 @@
</li>
</ul></sectionDescription>
</sections>
- <sections xmi:id="_etwutZ01EdyQ3oTO93enUw" name="Is the implementation correct?"
+ <sections xmi:id="_etwutZ01EdyQ3oTO93enUw" name="The implementation is correct"
guid="_etwutZ01EdyQ3oTO93enUw">
<sectionDescription><ul>
<li>
@@ -56,13 +62,14 @@
</li>
</ul></sectionDescription>
</sections>
- <sections xmi:id="_etwus501EdyQ3oTO93enUw" name="Is the implementation understandable?"
+ <sections xmi:id="_etwus501EdyQ3oTO93enUw" name="The implementation is understandable"
guid="_etwus501EdyQ3oTO93enUw">
<sectionDescription><p>
- Is there no redundancy in the implementation? (Identify candidates for refactoring.)
+ Is the logic clearly specified?&nbsp; Have comments been used&nbsp;sparingly to add clarity, and not to make up for
+ unclear code?
</p></sectionDescription>
</sections>
- <sections xmi:id="_etwusp01EdyQ3oTO93enUw" name="Is there no redundancy?" guid="_etwusp01EdyQ3oTO93enUw">
+ <sections xmi:id="_etwusp01EdyQ3oTO93enUw" name="There is no redundancy" guid="_etwusp01EdyQ3oTO93enUw">
<sectionDescription><p>
Is there no redundancy in the implementation? (Identify candidates for refactoring.)
</p></sectionDescription>
diff --git a/libraries/EPF_Practices_Library/core.tech.common.base/guidances/concepts/developer_testing.xmi b/libraries/EPF_Practices_Library/core.tech.common.base/guidances/concepts/developer_testing.xmi
index 17f6673..ba4c47a 100644
--- a/libraries/EPF_Practices_Library/core.tech.common.base/guidances/concepts/developer_testing.xmi
+++ b/libraries/EPF_Practices_Library/core.tech.common.base/guidances/concepts/developer_testing.xmi
@@ -1,9 +1,9 @@
<?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.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="-EOoqKeF2SEXao6XhNXBD-w"
- name=",_ADwlAJRtEdyrdaw_xGakyw" guid="-EOoqKeF2SEXao6XhNXBD-w" changeDate="2008-05-24T15:58:50.691-0700"
+ 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="-EOoqKeF2SEXao6XhNXBD-w"
+ name=",_ADwlAJRtEdyrdaw_xGakyw" guid="-EOoqKeF2SEXao6XhNXBD-w" changeDate="2008-08-11T09:09:21.312-0700"
version="7.2.0">
<mainDescription><p>
Developer testing is the act of regression testing source code by developers. This is sometimes called "unit regression
@@ -33,9 +33,9 @@
you might not be believed.
</li>
<li>
- Test to the risk. The riskier something is, the more it needs to be reviewed and tested. In other words you should
- invest significant effort testing in the algorithm for estimating radiation doses but nowhere near as much effort
- testing the "change font size" function of the same application.
+ Test to the risk. The riskier something is, the more it needs to be reviewed and tested. For example, you should
+ invest significantly more&nbsp;effort testing a safety-critical algorithm for measuring radiation doses, and far
+ less effort testing the "change font size" function of the same application.
</li>
<li>
You can validate all artifacts. You can test all your artifacts, not just your source code, although the focus of
diff --git a/libraries/EPF_Practices_Library/core.tech.common.base/guidances/termdefinitions/architecture.xmi b/libraries/EPF_Practices_Library/core.tech.common.base/guidances/termdefinitions/architecture.xmi
index 1f84a99..94925c4 100644
--- a/libraries/EPF_Practices_Library/core.tech.common.base/guidances/termdefinitions/architecture.xmi
+++ b/libraries/EPF_Practices_Library/core.tech.common.base/guidances/termdefinitions/architecture.xmi
@@ -1,15 +1,13 @@
<?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" xmlns:rmc="http://www.ibm.com/rmc"
- rmc:version="7.2.0" xmi:id="-YMvJ5LwexkcVWWqLdm5-nQ"
- name=",_siyjEEvCEdunZcj9T5hrMQ" guid="-YMvJ5LwexkcVWWqLdm5-nQ" version="7.2.0">
+ 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="-YMvJ5LwexkcVWWqLdm5-nQ"
+ name=",_siyjEEvCEdunZcj9T5hrMQ" guid="-YMvJ5LwexkcVWWqLdm5-nQ" changeDate="2008-08-11T10:02:44.281-0700"
+ version="7.2.0">
<mainDescription><p>
Describes the blueprint for software development, frequently represented using a number of architectural views. It also
- contains the rationale, assumptions, explanations and implications of the decisions that where made in forming the
+ contains the rationale, assumptions, explanations and implications of the decisions that were made in forming the
architecture as well as the global mapping between views.
-</p>
-<p>
- [*** I'm not sure we should mention "views" in this basic definition of architecture. Thoughts? ***]
</p></mainDescription>
</org.eclipse.epf.uma:ContentDescription>
diff --git a/libraries/EPF_Practices_Library/practice.tech.evolutionary_arch.base/guidances/checklists/architecture_notebook.xmi b/libraries/EPF_Practices_Library/practice.tech.evolutionary_arch.base/guidances/checklists/architecture_notebook.xmi
index 97e0509..a140fec 100644
--- a/libraries/EPF_Practices_Library/practice.tech.evolutionary_arch.base/guidances/checklists/architecture_notebook.xmi
+++ b/libraries/EPF_Practices_Library/practice.tech.evolutionary_arch.base/guidances/checklists/architecture_notebook.xmi
@@ -1,21 +1,11 @@
<?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" xmlns:rmc="http://www.ibm.com/rmc"
- rmc:version="7.2.0" xmi:id="_17Ve8Nd6EdmIm-bsRSNCgw"
+ 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="_17Ve8Nd6EdmIm-bsRSNCgw"
name="architecture,_17PYUNd6EdmIm-bsRSNCgw" guid="_17Ve8Nd6EdmIm-bsRSNCgw" authors="Chris Doyle, Mark Dickson"
- changeDate="2008-02-11T11:59:58.984-0500" changeDescription="(Mark Dickson) formatted & applied changes from Chris Doyle "
+ changeDate="2008-08-11T10:07:36.984-0700" changeDescription="(Mark Dickson) formatted & applied changes from Chris Doyle "
version="1.2">
- <mainDescription><p>
- The items in this checklist represent good practices for creating and communicating a robust architecture. 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>
- Architectural revisions can occur every day. Use this checklist regularly to ensure that the results are robust,
- consistent, and understandable. Make the architecture 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="_MN7hMNjcEdydTt3eL7YyCQ" name="Is the architecture understandable?"
guid="_MN7hMNjcEdydTt3eL7YyCQ">
<sectionDescription><ul>
diff --git a/libraries/EPF_Practices_Library/practice.tech.evolutionary_arch.base/guidances/roadmaps/how_to_adopt_evolutionary_arch_practice.xmi b/libraries/EPF_Practices_Library/practice.tech.evolutionary_arch.base/guidances/roadmaps/how_to_adopt_evolutionary_arch_practice.xmi
index b3a19ad..8a40763 100644
--- a/libraries/EPF_Practices_Library/practice.tech.evolutionary_arch.base/guidances/roadmaps/how_to_adopt_evolutionary_arch_practice.xmi
+++ b/libraries/EPF_Practices_Library/practice.tech.evolutionary_arch.base/guidances/roadmaps/how_to_adopt_evolutionary_arch_practice.xmi
@@ -1,9 +1,9 @@
<?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.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="-KXvzdy6aJTFPQRS-UK5dvA"
- name="new_roadmap,_Odpz8NciEdy1nJEYZGzN4A" guid="-KXvzdy6aJTFPQRS-UK5dvA" changeDate="2008-08-08T12:36:43.271-0700"
+ 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="-KXvzdy6aJTFPQRS-UK5dvA"
+ name="new_roadmap,_Odpz8NciEdy1nJEYZGzN4A" guid="-KXvzdy6aJTFPQRS-UK5dvA" changeDate="2008-08-11T10:28:42.656-0700"
version="7.2.0">
<mainDescription><h3>
Getting Started&nbsp;
@@ -66,10 +66,9 @@
more or different information they would like see?&nbsp; Would they like to see less?
</p>
<p>
- Conversely, don't ignore documenting important decisions. Team members may be close by and you may be in constant
- contact with them, but teams change and architects move on to other projects. Failure to document important decisions
- raises the risk of failure at a later date because future team members don't have the benefit of being involved in
- today's collaborative decisions. Consider future team members as collaborators that you&nbsp;don't have the opportunity
- to speak to face-to-face.&nbsp;
+ Document&nbsp;important decisions. Team members may be close by and you may be in constant contact with them, but teams
+ change and architects move on to other projects. Failure to document important decisions raises the risk of failure at
+ a later date because future team members don't have the benefit of being involved in today's collaborative decisions.
+ Consider future team members as collaborators that you&nbsp;don't have the opportunity to speak to face-to-face.&nbsp;
</p></mainDescription>
</org.eclipse.epf.uma:ContentDescription>
diff --git a/libraries/EPF_Practices_Library/practice.tech.evolutionary_arch.base/plugin.xmi b/libraries/EPF_Practices_Library/practice.tech.evolutionary_arch.base/plugin.xmi
index b80c148..070a999 100644
--- a/libraries/EPF_Practices_Library/practice.tech.evolutionary_arch.base/plugin.xmi
+++ b/libraries/EPF_Practices_Library/practice.tech.evolutionary_arch.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="_4ggZgbPREduocbW-TPTq7A"
guid="_4ggZgbPREduocbW-TPTq7A">
<resourceDescriptors xmi:id="_m_D6YPL5Edm6Nvont3uinw" id="_17Ve8Nd6EdmIm-bsRSNCgw"
@@ -141,8 +141,7 @@
<optionalInput href="uma://_-bv0ELXuEduGP_98XMd0fg#_Vux8UEfUEdyiPI8btkmvmw"/>
</contentElements>
<contentElements xsi:type="org.eclipse.epf.uma:Checklist" xmi:id="_17PYUNd6EdmIm-bsRSNCgw"
- name="architecture_notebook" guid="_17PYUNd6EdmIm-bsRSNCgw" presentationName="Architecture Notebook"
- briefDescription="This checklist provides questions to help in evaluating whether architectural decisions have been captured appropriately.">
+ name="architecture_notebook" guid="_17PYUNd6EdmIm-bsRSNCgw" presentationName="Architecture Notebook">
<presentation xmi:id="_17Ve8Nd6EdmIm-bsRSNCgw" href="uma://_17Ve8Nd6EdmIm-bsRSNCgw#_17Ve8Nd6EdmIm-bsRSNCgw"/>
<conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_mzxI0A4LEduibvKwrGxWxA"/>
<conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_jdKSsNpiEdyP58ppo1Ieaw"/>
diff --git a/libraries/EPF_Practices_Library/practice.tech.evolutionary_arch.base/workproducts/arch_notebook.res.xmi b/libraries/EPF_Practices_Library/practice.tech.evolutionary_arch.base/workproducts/arch_notebook.res.xmi
index 970cdd2..ba7f470 100644
--- a/libraries/EPF_Practices_Library/practice.tech.evolutionary_arch.base/workproducts/arch_notebook.res.xmi
+++ b/libraries/EPF_Practices_Library/practice.tech.evolutionary_arch.base/workproducts/arch_notebook.res.xmi
@@ -1,13 +1,7 @@
<?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.4/uma.ecore"
- xmlns:epf="http://www.eclipse.org/epf" epf:version="1.2.0" xmlns:rmc="http://www.ibm.com/rmc"
- rmc:version="7.2.0" xmi:id="-KmIIyuXPr1pe5iREXAoMYw"
+ 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="-KmIIyuXPr1pe5iREXAoMYw"
name="arch_notebook.res,_QHYwcM3jEdyjXslGsagg_w" guid="-KmIIyuXPr1pe5iREXAoMYw"
- changeDate="2008-02-13T19:25:46.828-0500">
- <representation><p>
- See <a class="elementLinkWithType"
- href="./../../practice.tech.evolutionary_arch.base/guidances/templates/architecture_notebook_BCD3507B.html"
- guid="_me8WcAANEdyRS9uciXlZ6g">Template: Architecture Notebook</a>.
-</p></representation>
-</org.eclipse.epf.uma:ArtifactDescription>
+ changeDate="2008-08-11T10:12:15.859-0700" version="7.2.0"/>
diff --git a/libraries/EPF_Practices_Library/practice.tech.test_driven_development.base/guidances/practices/test_driven_dev.xmi b/libraries/EPF_Practices_Library/practice.tech.test_driven_development.base/guidances/practices/test_driven_dev.xmi
index b1829f8..6517282 100644
--- a/libraries/EPF_Practices_Library/practice.tech.test_driven_development.base/guidances/practices/test_driven_dev.xmi
+++ b/libraries/EPF_Practices_Library/practice.tech.test_driven_development.base/guidances/practices/test_driven_dev.xmi
@@ -1,9 +1,10 @@
<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:PracticeDescription xmi:version="2.0"
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="-nV4dgKPmOiwZnl6nUoKqQw"
- name="new_practice,_FUDtMB4mEd2bS8fFOQ7WWA" guid="-nV4dgKPmOiwZnl6nUoKqQw" changeDate="2008-08-07T16:06:31.635-0700">
+ 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="-nV4dgKPmOiwZnl6nUoKqQw"
+ name="new_practice,_FUDtMB4mEd2bS8fFOQ7WWA" guid="-nV4dgKPmOiwZnl6nUoKqQw" changeDate="2008-08-11T09:41:04.953-0700"
+ version="7.5.0">
<additionalInfo><p>
If you're just getting started with TDD or developer testing in general, you'll need to know why developer testing is a
good idea and the basics of what makes good developer tests. A good starting place is this <a
@@ -48,9 +49,9 @@
been regression tested, prior to check-in.
</p>
<p>
- Developers use TDD to create the&nbsp;<a class="elementLink"
- href="./../../../core.tech.slot.base/workproducts/software_implementation_slot_E92F6A39.html"
- guid="_Vux8UEfUEdyiPI8btkmvmw">[Software Implementation]</a> and the <a class="elementLink"
+ Developers use TDD to create the <a class="elementLink"
+ href="./../../../core.tech.common.base/workproducts/implementation_AFFEFC46.html"
+ guid="_JqYbgJ01EdyQ3oTO93enUw">Implementation</a>&nbsp;and the <a class="elementLink"
href="./../../../core.tech.common.base/workproducts/developer_test_6A91CE05.html"
guid="_kh9FcJ02EdyQ3oTO93enUw">Developer Test</a>s.
</p>
diff --git a/libraries/EPF_Practices_Library/practice.tech.test_driven_development.base/guidances/roadmaps/adopt_tdd_practice.xmi b/libraries/EPF_Practices_Library/practice.tech.test_driven_development.base/guidances/roadmaps/adopt_tdd_practice.xmi
index 35fbb35..1f740e8 100644
--- a/libraries/EPF_Practices_Library/practice.tech.test_driven_development.base/guidances/roadmaps/adopt_tdd_practice.xmi
+++ b/libraries/EPF_Practices_Library/practice.tech.test_driven_development.base/guidances/roadmaps/adopt_tdd_practice.xmi
@@ -1,15 +1,15 @@
<?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.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="-CGSI-WD83sE5swSmSDjAYA"
+ 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="-CGSI-WD83sE5swSmSDjAYA"
name="adopt_tdd_practice,_8yG48JRqEdyrdaw_xGakyw" guid="-CGSI-WD83sE5swSmSDjAYA"
- authors="Jim Ruehlin" changeDate="2008-08-09T09:01:00.137-0700" version="7.2.0">
+ authors="Jim Ruehlin" changeDate="2008-08-11T09:38:41.046-0700" version="7.2.0">
<mainDescription><h3>
Getting Started
</h3>
<p>
- If you've just installed the Test Driven Development practice, start by reviewing the concepts of <a
+ If you've just installed the Test Driven Development (TDD) practice, start by reviewing the concepts of <a
class="elementLink" href="./../../../core.tech.common.base/guidances/concepts/developer_testing_FEBDAED6.html"
guid="_ADwlAJRtEdyrdaw_xGakyw">Developer Testing</a>&nbsp;and <a class="elementLink"
href="./../../../practice.tech.test_driven_development.base/guidances/concepts/test_driven_development_FA8E27C2.html"
@@ -20,9 +20,9 @@
guid="_t7IacJRmEdyrdaw_xGakyw">test driven&nbsp;development whitepaper</a>.
</p>
<p>
- If your organization has never done developer testing before, start your adoption by by educating the members of the
- team. Use the resources below for educational and reference materials. Begin to track your performance immediately as
- that will give you quick feedback on how rapidly the team is adopting TDD, even if it's a very low form of adoption at
+ If your organization has never done developer testing before, start your adoption by educating the members of the team.
+ Use the resources below for educational and reference materials. Begin to track your performance immediately as that
+ will give you quick feedback on how rapidly the team is adopting TDD, even if it's a very low form of adoption at
first.
</p>
<p>
@@ -52,19 +52,19 @@
</p>
<p>
Here's one possible scenario for adopting the TDD practice. You may want to add, change, or&nbsp;remove steps to design
- an adoption roadmap more suitable to your environment. Hiring a consulting experienced in TDD will also speed your
+ an adoption roadmap more suitable to your environment. Hiring a consultant experienced in TDD will also speed your
adoption of the practice and help avoid common pitfalls.
</p>
<ol>
<li>
- Educate the team on TDD. Use the presentations and articles referenced on this page as a starting place. It would
- also be helpful for developers to attend a class on developer testing and TDD.
+ Educate the team on TDD. Use the presentations and articles referenced in this practice as a starting place. It
+ would also be helpful for developers to attend a class on developer testing and TDD.
</li>
<li>
Have the team review the material in this practice.
</li>
<li>
- Extend this practice to reflect any important constraints or requirments in your organization. For instance,
+ Extend this practice to reflect any important constraints or requirements in your organization. For instance,
indicate any extra information that may need to be described when checking in system or test code, link to any
materials that describe internal tools your team is required to use, or create a guideline describing how each test
must be documented or structured to conform to corporate standards.
diff --git a/libraries/EPF_Practices_Library/practice.tech.test_driven_development.base/tasks/run_developer_tests.xmi b/libraries/EPF_Practices_Library/practice.tech.test_driven_development.base/tasks/run_developer_tests.xmi
index 2b37b75..e8cca9e 100644
--- a/libraries/EPF_Practices_Library/practice.tech.test_driven_development.base/tasks/run_developer_tests.xmi
+++ b/libraries/EPF_Practices_Library/practice.tech.test_driven_development.base/tasks/run_developer_tests.xmi
@@ -1,15 +1,16 @@
<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:TaskDescription xmi:version="2.0"
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" xmi:id="-H6ob8eA7gz_mOsk8ulSFMQ"
- name=",_R7atwJfIEdyZkIR-s-Y8wQ" guid="-H6ob8eA7gz_mOsk8ulSFMQ" changeDate="2008-03-11T14:16:41.025-0400"
+ 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="-H6ob8eA7gz_mOsk8ulSFMQ"
+ name=",_R7atwJfIEdyZkIR-s-Y8wQ" guid="-H6ob8eA7gz_mOsk8ulSFMQ" changeDate="2008-08-11T09:32:16.421-0700"
version="7.2.0">
<keyConsiderations><p>
It is common to require that code pass all developer tests before it can be delivered in an integrated source code
repository.
</p>
<p>
- Pair with the Tester during all steps of this task to gain insight on testing and quality considerations.
+ Pair with testing experts to gain insight on testing and quality considerations.
</p>
<p>
The&nbsp;<a class="elementLink" href="./../../core.mgmt.slot.base/workproducts/project_work_slot_F12BAC46.html"
