*** empty log message ***
diff --git a/libraries/EPF_Practices_Library/core.tech.common.base/workproducts/implementation.xmi b/libraries/EPF_Practices_Library/core.tech.common.base/workproducts/implementation.xmi
index b5279b1..9c0a04a 100644
--- a/libraries/EPF_Practices_Library/core.tech.common.base/workproducts/implementation.xmi
+++ b/libraries/EPF_Practices_Library/core.tech.common.base/workproducts/implementation.xmi
@@ -26,7 +26,7 @@
To represent the physical parts that make up the system to be built, organized in a way that is understandable and
manageable.
</p></purpose>
- <impactOfNotHaving>Without this artifact there is no&nbsp;application to be delivered as part of the solution.</impactOfNotHaving>
+ <impactOfNotHaving>Without this artifact there is way to produce the&nbsp;application to be delivered as part of the solution.</impactOfNotHaving>
<reasonsForNotNeeding>The only reason not to produce this artifact is if the actual development of an application is not within the scope of the
solution.</reasonsForNotNeeding>
<representationOptions><p>
diff --git a/libraries/EPF_Practices_Library/core.tech.common.base/workproducts/test_case.xmi b/libraries/EPF_Practices_Library/core.tech.common.base/workproducts/test_case.xmi
index 876e924..ef267a4 100644
--- a/libraries/EPF_Practices_Library/core.tech.common.base/workproducts/test_case.xmi
+++ b/libraries/EPF_Practices_Library/core.tech.common.base/workproducts/test_case.xmi
@@ -1,9 +1,9 @@
<?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:rmc="http://www.ibm.com/rmc" rmc:version="7.2.0" xmlns:epf="http://www.eclipse.org/epf"
- epf:version="1.2.0" xmi:id="_NqYIdKeqEdmKDbQuyzCoqQ"
- name="test_case,_0ZS-0MlgEdmt3adZL5Dmdw" guid="_NqYIdKeqEdmKDbQuyzCoqQ" changeDate="2006-09-20T16:57:14.165-0700"
+ 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="_NqYIdKeqEdmKDbQuyzCoqQ"
+ name="test_case,_0ZS-0MlgEdmt3adZL5Dmdw" guid="_NqYIdKeqEdmKDbQuyzCoqQ" changeDate="2008-08-14T12:46:38.070-0400"
version="7.2.0">
<mainDescription><p>
A test case specifies the conditions which need to be validated to enable an assessment of some particular aspects of
@@ -33,4 +33,15 @@
requirements, or scenario
</li>
</ul></purpose>
+ <impactOfNotHaving><p>
+ <font size="2">Without this artifact it is difficult adequately validate system functionality.&nbsp;&nbsp;Since this
+ artifact is also often used&nbsp;to specify the conditions of acceptance between the stakeholders and the developers,
+ it is more difficult to establish exit criteria and to demonstrate that the exit criteria have been met without
+ it.&nbsp; It is also not possible to do regression testing if the original test cases have not been documented.</font>
+</p></impactOfNotHaving>
+ <reasonsForNotNeeding><p>
+ <font size="2">It may not be necessary to create this artifact for maintenance or small enhancements to existing
+ systems which will likely have existing test assets that can be utilized.&nbsp; Likewise package applications often
+ come with their own set of test cases that would not require a separate instance of this artifact.</font>
+</p></reasonsForNotNeeding>
</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/libraries/EPF_Practices_Library/core.tech.common.base/workproducts/test_script.xmi b/libraries/EPF_Practices_Library/core.tech.common.base/workproducts/test_script.xmi
index f73fcd9..0b2e84c 100644
--- a/libraries/EPF_Practices_Library/core.tech.common.base/workproducts/test_script.xmi
+++ b/libraries/EPF_Practices_Library/core.tech.common.base/workproducts/test_script.xmi
@@ -12,7 +12,9 @@
results are repeatable and any errors discovered can be recreated.&nbsp; It also makes it more difficult to validate that
errors were not caused because of the way in which tests were executed.</impactOfNotHaving>
<reasonsForNotNeeding><p>
- If the tests are very simple in nature or testing is only being done on an ad-hoc basis this artifact may not be
- required
+ This artifact may not be required if&nbsp;the tests are very simple in nature or testing is only being done on an
+ informal basis.&nbsp; However, in order for this approach to be successful, testers need to be disciplined in tracking
+ their processes, as they may have to recreate a problem scenario.&nbsp; Alternatively, automatic capture/playback tools
+ could be put in place to provide a record of such testing.
</p></reasonsForNotNeeding>
</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/libraries/EPF_Practices_Library/practice.tech.continuous_integration.base/workproducts/build.xmi b/libraries/EPF_Practices_Library/practice.tech.continuous_integration.base/workproducts/build.xmi
index 63f25eb..2707d2d 100644
--- a/libraries/EPF_Practices_Library/practice.tech.continuous_integration.base/workproducts/build.xmi
+++ b/libraries/EPF_Practices_Library/practice.tech.continuous_integration.base/workproducts/build.xmi
@@ -1,9 +1,9 @@
<?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" xmi:id="_NqSB0KeqEdmKDbQuyzCoqQ"
- name="build,_0YuXEMlgEdmt3adZL5Dmdw" guid="_NqSB0KeqEdmKDbQuyzCoqQ" changeDate="2007-01-30T12:24:06.639-0800">
+ 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="_NqSB0KeqEdmKDbQuyzCoqQ"
+ name="build,_0YuXEMlgEdmt3adZL5Dmdw" guid="_NqSB0KeqEdmKDbQuyzCoqQ" changeDate="2008-08-14T13:14:28.648-0400">
<mainDescription><p>
This working version of the system is the result of putting the implementation of the system through a build process
(typically an automated build script) that creates an executable version of the system, or one that runs. This
@@ -26,10 +26,11 @@

</p></keyConsiderations>
<purpose>Deliver incremental value to the user and customer, and provide a testable artifact for verification.</purpose>
+ <impactOfNotHaving><p>
+ Without this artifact there is no operational version of the system.
+</p></impactOfNotHaving>
<reasonsForNotNeeding><p>
-
- There will always need to be an&nbsp;operational version of the system.
-
+ This artifact is not needed if the actual development of an application is not within the scope of the solution.
</p></reasonsForNotNeeding>
<representationOptions><p>

