*** empty log message ***
diff --git a/praclib/temp/.project b/praclib/temp/.project
new file mode 100644
index 0000000..3615ec7
--- /dev/null
+++ b/praclib/temp/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>EPFPracLib_20080306</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>org.eclipse.epf.library.project.MethodLibraryProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/configurations/publish.openup.xmi b/praclib/temp/configurations/publish.openup.xmi
new file mode 100644
index 0000000..51c817d
--- /dev/null
+++ b/praclib/temp/configurations/publish.openup.xmi
@@ -0,0 +1,655 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:MethodConfiguration 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.4/uma.ecore" xmlns:epf="http://www.eclipse.org/epf"
+ epf:version="1.2.0" xmi:id="_QN3nQBEHEdyM7Iu0sxfrPA"
+ name="publish.openup" guid="_QN3nQBEHEdyM7Iu0sxfrPA" version="1.0.0">
+ <methodPluginSelection href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPloEFXEdy9ENCpSugIjA"/>
+ <methodPluginSelection href="uma://_iVydgENdEdy245g62lfWcA#_iVydgENdEdy245g62lfWcA"/>
+ <methodPluginSelection href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno4EKmEdyrauqpmnA8jQ"/>
+ <methodPluginSelection href="uma://_A118oMYaEdyXeo04os5BOw#_A118oMYaEdyXeo04os5BOw"/>
+ <methodPluginSelection href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVEMYbEdyXeo04os5BOw"/>
+ <methodPluginSelection href="uma://_WCUhAO8KEdmKSqa_gSYthg#_WCUhAO8KEdmKSqa_gSYthg"/>
+ <methodPluginSelection href="uma://_14Ft0M3pEdyuBO4ZIzcyig#_14Ft0M3pEdyuBO4ZIzcyig"/>
+ <methodPluginSelection href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-gEMXEdyP_Jn83ylwUQ"/>
+ <methodPluginSelection href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPEEKmEdyrauqpmnA8jQ"/>
+ <methodPluginSelection href="uma://_CX-9AM3qEdyuBO4ZIzcyig#_CX-9AM3qEdyuBO4ZIzcyig"/>
+ <methodPluginSelection href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0TmecJ-VEdy3Nc4rvuj7bA"/>
+ <methodPluginSelection href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYucEfUEdyiPI8btkmvmw"/>
+ <methodPluginSelection href="uma://_LdRtkM3qEdyuBO4ZIzcyig#_LdRtkM3qEdyuBO4ZIzcyig"/>
+ <methodPluginSelection href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2AAouEdyhlpBPrduOMw"/>
+ <methodPluginSelection href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0ELXuEduGP_98XMd0fg"/>
+ <methodPluginSelection href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_iNwFsMhNEdygFZkm1d5NtQ"/>
+ <methodPluginSelection href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzAJ6WEdyQN-zRFaRrCQ"/>
+ <methodPluginSelection href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdoL8BEdyWX5Yd-9QZ1A"/>
+ <methodPluginSelection href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_NBRHwMh3EdygFZkm1d5NtQ"/>
+ <methodPluginSelection href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS10J6YEdyQN-zRFaRrCQ"/>
+ <methodPluginSelection href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_40sbAJ6YEdyQN-zRFaRrCQ"/>
+ <methodPluginSelection href="uma://_IItp4MuXEdyLOriywSJkoQ#_IItp4MuXEdyLOriywSJkoQ"/>
+ <methodPluginSelection href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9OMG5KEdyAHIxjZ9kpqw"/>
+ <methodPluginSelection href="uma://_h_9roM3PEdyKkus0T68H3Q#_h_9roM3PEdyKkus0T68H3Q"/>
+ <methodPluginSelection href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExQMktEdygFZkm1d5NtQ"/>
+ <methodPluginSelection href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_GxBjAM2sEdym_ZFqrJcXUg"/>
+ <methodPluginSelection href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS4LPREduocbW-TPTq7A"/>
+ <methodPluginSelection href="uma://_XPLD8MudEdyRPtFYRAKVDg#_XPLD8MudEdyRPtFYRAKVDg"/>
+ <methodPluginSelection href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK0LPPEduocbW-TPTq7A"/>
+ <methodPluginSelection href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_NjNCEMrmEdyd6uFrFHNXhA"/>
+ <methodPluginSelection href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKMLS9EduDY8LNbMCDBA"/>
+ <methodPluginSelection href="uma://_00zMMMt1EdyRPtFYRAKVDg#_00zMMMt1EdyRPtFYRAKVDg"/>
+ <methodPluginSelection href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rEI7-Edy7q8CKc_B8eg"/>
+ <methodPluginSelection href="uma://_HYAA4MriEdyd6uFrFHNXhA#_HYAA4MriEdyd6uFrFHNXhA"/>
+ <methodPluginSelection href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfULPaEduocbW-TPTq7A"/>
+ <methodPluginSelection href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_Z7teANQ1EdyQ89W1tgswSQ"/>
+ <methodPluginSelection href="uma://_4ulTgMg7EdyXeo04os5BOw#_4ulTgMg7EdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPlrUFXEdy9ENCpSugIjA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPlrkFXEdy9ENCpSugIjA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iVydgENdEdy245g62lfWcA#_buz3kENfEdy245g62lfWcA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_iVydgENdEdy245g62lfWcA#_iVydjUNdEdy245g62lfWcA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_iVydgENdEdy245g62lfWcA#_iVydjkNdEdy245g62lfWcA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno7UKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno7kKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_A118oMYaEdyXeo04os5BOw#__0_tgBAYEdyqb5chWQXsPQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_A118oMYaEdyXeo04os5BOw#_A118rcYaEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_A118oMYaEdyXeo04os5BOw#_A118rsYaEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_fRdVEMYbEdyXeo04os5BOw#_w_1EkOFUEdyhmsbt0Xyl8A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVHcYbEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVHsYbEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_WCUhAO8KEdmKSqa_gSYthg#_bJKXUKNbEdyMFYhoCpD11Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_WCUhAO8KEdmKSqa_gSYthg#_eNnSAO8LEdmKSqa_gSYthg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_WCUhAO8KEdmKSqa_gSYthg#_WCguS-8KEdmKSqa_gSYthg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_WCUhAO8KEdmKSqa_gSYthg#_WCguTO8KEdmKSqa_gSYthg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_14Ft0M3pEdyuBO4ZIzcyig#_s1yG8M6FEdyndOCfdhe9bw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_14Ft0M3pEdyuBO4ZIzcyig#_14Ft3c3pEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_14Ft0M3pEdyuBO4ZIzcyig#_14Ft3s3pEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_r7UQIEMXEdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-jUMXEdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-jkMXEdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_VBd6oEMDEdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPHUKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPHkKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_CX-9AM3qEdyuBO4ZIzcyig#_5US4sOGiEdyhmsbt0Xyl8A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_CX-9AM3qEdyuBO4ZIzcyig#_CX-9Dc3qEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_CX-9AM3qEdyuBO4ZIzcyig#_CX-9Ds3qEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_QsmM8J-ZEdywNOckqfsZQg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_lFkpUOFlEdyhmsbt0Xyl8A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_onU40OFlEdyhmsbt0Xyl8A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0TmefZ-VEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0Tmefp-VEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vJYucEfUEdyiPI8btkmvmw#_gxGj0N8-Edyhmsbt0Xyl8A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vJYucEfUEdyiPI8btkmvmw#_xo1MYEfUEdyiPI8btkmvmw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYufUfUEdyiPI8btkmvmw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYufkfUEdyiPI8btkmvmw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_LdRtkM3qEdyuBO4ZIzcyig#_45HpUM3-EdylYe2DrHGiXg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_LdRtkM3qEdyuBO4ZIzcyig#_LdRtnc3qEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_LdRtkM3qEdyuBO4ZIzcyig#_LdRtns3qEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_1MdooMOlEdupeqHTre3HvQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_3AcuwMOlEdupeqHTre3HvQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_qjvdgNZ1EdybtZ_nzDhq6w"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_119G4NPSEduegN_z1rVgJA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_cHHEIBEdEdyM7Iu0sxfrPA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_8oxCIMOlEdupeqHTre3HvQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_9ncVUBEfEdyM7Iu0sxfrPA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_mMbw8NZzEdybtZ_nzDhq6w"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_-87r0BASEdyqb5chWQXsPQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_RhLBwAouEdyhlpBPrduOMw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_Vqf5EMuFEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2DQouEdyhlpBPrduOMw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2DgouEdyhlpBPrduOMw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_-bv0ELXuEduGP_98XMd0fg#_ip7wMJI7Edyk6dG0ehkW5Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_-bv0ELXuEduGP_98XMd0fg#__wRXALXuEduGP_98XMd0fg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0HbXuEduGP_98XMd0fg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0HrXuEduGP_98XMd0fg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_lUsBcMhNEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_iNwFvchNEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_iNwFvshNEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_BwrisJ9WEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_gfuaMOFSEdyhmsbt0Xyl8A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_jRZ5EMOBEdy3nv0ZK8D4GQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_dLzj4MhPEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzDZ6WEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzDp6WEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_fiq3sL8GEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_f4YZsMN_Edy3nv0ZK8D4GQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_B3azkMh5EdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdrb8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_LYTG0OL6EdyM47cGD2jiaQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessComponent" href="uma://_SKnAwOL9EdyM47cGD2jiaQ#_SKnAwOL9EdyM47cGD2jiaQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessComponent" href="uma://_FzchsOL7EdyM47cGD2jiaQ#_FzchsOL7EdyM47cGD2jiaQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdrr8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_2Ve24Mh3EdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_NBRHzch3EdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_NBRHzsh3EdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_hLcgcJ9WEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_q8sJwMOBEdy3nv0ZK8D4GQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS13Z6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS13p6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_VxJAUJ9WEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_idXpgMOAEdy3nv0ZK8D4GQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_40sbDZ6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_40sbDp6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_IItp4MuXEdyLOriywSJkoQ#_Z30okMuaEdy1o5Xnqdh1Tg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_IItp4MuXEdyLOriywSJkoQ#_IItp7cuXEdyLOriywSJkoQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_IItp4MuXEdyLOriywSJkoQ#_IItp7suXEdyLOriywSJkoQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_4GsDkIfxEdy1GthOId7fdw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9OPW5KEdyAHIxjZ9kpqw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9OPm5KEdyAHIxjZ9kpqw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_h_9roM3PEdyKkus0T68H3Q#_fTBSUM3REdyKkus0T68H3Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_h_9roM3PEdyKkus0T68H3Q#_h_9rrc3PEdyKkus0T68H3Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_h_9roM3PEdyKkus0T68H3Q#_h_9rrs3PEdyKkus0T68H3Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_J6WicMktEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExTcktEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExTsktEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_obUd8M2tEdym_ZFqrJcXUg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_GxBjDc2sEdym_ZFqrJcXUg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_GxBjDs2sEdym_ZFqrJcXUg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_xhaxgKtYEdytrdP46hWyHg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#__EXZIKtYEdytrdP46hWyHg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_NInusM3iEdyjXslGsagg_w"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_rA1NMM3lEdyjXslGsagg_w"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS7bPREduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_ejTSsMQOEduMu5zRIJX95g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS7rPREduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_elKkoMueEdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_Ks_WoOCiEdynptYdmll41Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_XPLD_cudEdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_XPLD_sudEdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_8A8e8NPREduegN_z1rVgJA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_PGDx8PisEdmjyaJMRcPDWA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK3bPPEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Wvf0oMQNEduMu5zRIJX95g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK3rPPEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_hBEI8MrmEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_NjNCHcrmEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_NjNCHsrmEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_yBdFENPTEduegN_z1rVgJA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_S6bmYMufEdyTA_Xoy-01eg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_qDsgQMOsEdupeqHTre3HvQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_VbrjsEL-EdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKPbS9EduDY8LNbMCDBA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKPrS9EduDY8LNbMCDBA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_00zMMMt1EdyRPtFYRAKVDg#_LE8eYMt_EdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_00zMMMt1EdyRPtFYRAKVDg#_00zMPct1EdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_00zMMMt1EdyRPtFYRAKVDg#_00zMPst1EdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_iEvlIJMPEdyaRZQqSbPe-w"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rHY7-Edy7q8CKc_B8eg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rHo7-Edy7q8CKc_B8eg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_HYAA4MriEdyd6uFrFHNXhA#_gMspkMriEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_HYAA4MriEdyd6uFrFHNXhA#_HYAA7criEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_HYAA4MriEdyd6uFrFHNXhA#_HYAA7sriEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_LVhzMLPcEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_X-RNUMuXEdyTA_Xoy-01eg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_jAZJYNPCEduegN_z1rVgJA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfXbPaEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfXrPaEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_Z7teDdQ1EdyQ89W1tgswSQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_a0pWkNOEEdyqlogshP8l4g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessComponent" href="uma://_eWxZgNOEEdyqlogshP8l4g#_eWxZgNOEEdyqlogshP8l4g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessComponent" href="uma://_oZgCsNOEEdyqlogshP8l4g#_oZgCsNOEEdyqlogshP8l4g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_OKykANONEdyqlogshP8l4g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessComponent" href="uma://_RQi0ANONEdyqlogshP8l4g#_RQi0ANONEdyqlogshP8l4g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessComponent" href="uma://_aUsVENONEdyqlogshP8l4g#_aUsVENONEdyqlogshP8l4g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessComponent" href="uma://_h0Gs8NONEdyqlogshP8l4g#_h0Gs8NONEdyqlogshP8l4g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessComponent" href="uma://_pzQU0NONEdyqlogshP8l4g#_pzQU0NONEdyqlogshP8l4g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_b_xs8NOEEdyqlogshP8l4g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessComponent" href="uma://_4ouDUNOEEdyqlogshP8l4g#_4ouDUNOEEdyqlogshP8l4g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessComponent" href="uma://_KaeNsNOFEdyqlogshP8l4g#_KaeNsNOFEdyqlogshP8l4g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessComponent" href="uma://_RXGooNOFEdyqlogshP8l4g#_RXGooNOFEdyqlogshP8l4g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessComponent" href="uma://_xxcpgNOEEdyqlogshP8l4g#_xxcpgNOEEdyqlogshP8l4g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessComponent" href="uma://__ZInMNOEEdyqlogshP8l4g#__ZInMNOEEdyqlogshP8l4g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessComponent" href="uma://_buG4sNOFEdyqlogshP8l4g#_buG4sNOFEdyqlogshP8l4g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_Z7teDtQ1EdyQ89W1tgswSQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessComponent" href="uma://_SuWj4NOPEdyqlogshP8l4g#_SuWj4NOPEdyqlogshP8l4g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#__ZzOUMg7EdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_3aT48N4YEdyhmsbt0Xyl8A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_bGjA8OFQEdyhmsbt0Xyl8A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_cxOwQOL0EdyM47cGD2jiaQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_4ulTjcg7EdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_4ulTjsg7EdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPlrEFXEdy9ENCpSugIjA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPloUFXEdy9ENCpSugIjA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPlpUFXEdy9ENCpSugIjA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPlokFXEdy9ENCpSugIjA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPlpEFXEdy9ENCpSugIjA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPlo0FXEdy9ENCpSugIjA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPlp0FXEdy9ENCpSugIjA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPlpkFXEdy9ENCpSugIjA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPlr0FXEdy9ENCpSugIjA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPlqUFXEdy9ENCpSugIjA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPlqEFXEdy9ENCpSugIjA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPlqkFXEdy9ENCpSugIjA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iVydgENdEdy245g62lfWcA#_iVydjENdEdy245g62lfWcA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iVydgENdEdy245g62lfWcA#_iVydgUNdEdy245g62lfWcA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iVydgENdEdy245g62lfWcA#_iVydhUNdEdy245g62lfWcA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iVydgENdEdy245g62lfWcA#_iVydgkNdEdy245g62lfWcA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iVydgENdEdy245g62lfWcA#_iVydhENdEdy245g62lfWcA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iVydgENdEdy245g62lfWcA#_iVydg0NdEdy245g62lfWcA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iVydgENdEdy245g62lfWcA#_iVydh0NdEdy245g62lfWcA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iVydgENdEdy245g62lfWcA#_iVydhkNdEdy245g62lfWcA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_iVydgENdEdy245g62lfWcA#_iVydj0NdEdy245g62lfWcA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iVydgENdEdy245g62lfWcA#_iVydiUNdEdy245g62lfWcA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iVydgENdEdy245g62lfWcA#_iVydiENdEdy245g62lfWcA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iVydgENdEdy245g62lfWcA#_iVydikNdEdy245g62lfWcA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno7EKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno4UKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno5UKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno4kKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno5EKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno40KmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno50KmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno5kKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno70KmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno6UKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno6EKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno6kKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_A118oMYaEdyXeo04os5BOw#_A118rMYaEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_A118oMYaEdyXeo04os5BOw#_A118ocYaEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_A118oMYaEdyXeo04os5BOw#_A118pcYaEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_A118oMYaEdyXeo04os5BOw#_A118osYaEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_A118oMYaEdyXeo04os5BOw#_A118pMYaEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_A118oMYaEdyXeo04os5BOw#_A118o8YaEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_A118oMYaEdyXeo04os5BOw#_A118p8YaEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_A118oMYaEdyXeo04os5BOw#_A118psYaEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_A118oMYaEdyXeo04os5BOw#_A118r8YaEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_A118oMYaEdyXeo04os5BOw#_A118qcYaEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_A118oMYaEdyXeo04os5BOw#_A118qMYaEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_A118oMYaEdyXeo04os5BOw#_A118qsYaEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVHMYbEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVEcYbEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVFcYbEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVEsYbEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVFMYbEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVE8YbEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVF8YbEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVFsYbEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVH8YbEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVGcYbEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVGMYbEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVGsYbEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_WCUhAO8KEdmKSqa_gSYthg#_WCguSu8KEdmKSqa_gSYthg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_WCUhAO8KEdmKSqa_gSYthg#_WCanoO8KEdmKSqa_gSYthg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_WCUhAO8KEdmKSqa_gSYthg#_WCguQ-8KEdmKSqa_gSYthg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_WCUhAO8KEdmKSqa_gSYthg#_WCguQO8KEdmKSqa_gSYthg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_WCUhAO8KEdmKSqa_gSYthg#_WCguQu8KEdmKSqa_gSYthg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_WCUhAO8KEdmKSqa_gSYthg#_WCguQe8KEdmKSqa_gSYthg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_WCUhAO8KEdmKSqa_gSYthg#_WCguRe8KEdmKSqa_gSYthg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_WCUhAO8KEdmKSqa_gSYthg#_WCguRO8KEdmKSqa_gSYthg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_WCUhAO8KEdmKSqa_gSYthg#_WCguTe8KEdmKSqa_gSYthg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_WCUhAO8KEdmKSqa_gSYthg#_WCguR-8KEdmKSqa_gSYthg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_WCUhAO8KEdmKSqa_gSYthg#_WCguRu8KEdmKSqa_gSYthg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_WCUhAO8KEdmKSqa_gSYthg#_WCguSO8KEdmKSqa_gSYthg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_14Ft0M3pEdyuBO4ZIzcyig#_14Ft3M3pEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_14Ft0M3pEdyuBO4ZIzcyig#_14Ft0c3pEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_14Ft0M3pEdyuBO4ZIzcyig#_14Ft1c3pEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_14Ft0M3pEdyuBO4ZIzcyig#_14Ft0s3pEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_14Ft0M3pEdyuBO4ZIzcyig#_14Ft1M3pEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_14Ft0M3pEdyuBO4ZIzcyig#_14Ft083pEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_14Ft0M3pEdyuBO4ZIzcyig#_14Ft183pEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_14Ft0M3pEdyuBO4ZIzcyig#_14Ft1s3pEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_14Ft0M3pEdyuBO4ZIzcyig#_14Ft383pEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_14Ft0M3pEdyuBO4ZIzcyig#_14Ft2c3pEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_14Ft0M3pEdyuBO4ZIzcyig#_14Ft2M3pEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_14Ft0M3pEdyuBO4ZIzcyig#_14Ft2s3pEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-jEMXEdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-gUMXEdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-hUMXEdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-gkMXEdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-hEMXEdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-g0MXEdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-h0MXEdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-hkMXEdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-j0MXEdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-iUMXEdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-iEMXEdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-ikMXEdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPHEKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPEUKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPFUKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPEkKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPFEKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPE0KmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPF0KmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPFkKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPH0KmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPGUKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPGEKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPGkKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_CX-9AM3qEdyuBO4ZIzcyig#_CX-9DM3qEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_CX-9AM3qEdyuBO4ZIzcyig#_CX-9Ac3qEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_CX-9AM3qEdyuBO4ZIzcyig#_CX-9Bc3qEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_CX-9AM3qEdyuBO4ZIzcyig#_CX-9As3qEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_CX-9AM3qEdyuBO4ZIzcyig#_CX-9BM3qEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_CX-9AM3qEdyuBO4ZIzcyig#_CX-9A83qEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_CX-9AM3qEdyuBO4ZIzcyig#_CX-9B83qEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_CX-9AM3qEdyuBO4ZIzcyig#_CX-9Bs3qEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_CX-9AM3qEdyuBO4ZIzcyig#_CX-9D83qEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_CX-9AM3qEdyuBO4ZIzcyig#_CX-9Cc3qEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_CX-9AM3qEdyuBO4ZIzcyig#_CX-9CM3qEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_CX-9AM3qEdyuBO4ZIzcyig#_CX-9Cs3qEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0TmefJ-VEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0TmecZ-VEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0TmedZ-VEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0Tmecp-VEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0TmedJ-VEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0Tmec5-VEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0Tmed5-VEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0Tmedp-VEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0Tmef5-VEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0TmeeZ-VEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0TmeeJ-VEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0Tmeep-VEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYufEfUEdyiPI8btkmvmw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYucUfUEdyiPI8btkmvmw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYudUfUEdyiPI8btkmvmw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYuckfUEdyiPI8btkmvmw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYudEfUEdyiPI8btkmvmw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYuc0fUEdyiPI8btkmvmw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYud0fUEdyiPI8btkmvmw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYudkfUEdyiPI8btkmvmw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYuf0fUEdyiPI8btkmvmw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYueUfUEdyiPI8btkmvmw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYueEfUEdyiPI8btkmvmw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYuekfUEdyiPI8btkmvmw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_LdRtkM3qEdyuBO4ZIzcyig#_LdRtnM3qEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_LdRtkM3qEdyuBO4ZIzcyig#_LdRtkc3qEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_LdRtkM3qEdyuBO4ZIzcyig#_LdRtlc3qEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_LdRtkM3qEdyuBO4ZIzcyig#_LdRtks3qEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_LdRtkM3qEdyuBO4ZIzcyig#_LdRtlM3qEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_LdRtkM3qEdyuBO4ZIzcyig#_LdRtk83qEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_LdRtkM3qEdyuBO4ZIzcyig#_LdRtl83qEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_LdRtkM3qEdyuBO4ZIzcyig#_LdRtls3qEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_LdRtkM3qEdyuBO4ZIzcyig#_LdRtn83qEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_LdRtkM3qEdyuBO4ZIzcyig#_LdRtmc3qEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_LdRtkM3qEdyuBO4ZIzcyig#_LdRtmM3qEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_LdRtkM3qEdyuBO4ZIzcyig#_LdRtms3qEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2DAouEdyhlpBPrduOMw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2AQouEdyhlpBPrduOMw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2BQouEdyhlpBPrduOMw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2AgouEdyhlpBPrduOMw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2BAouEdyhlpBPrduOMw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2AwouEdyhlpBPrduOMw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2BwouEdyhlpBPrduOMw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2BgouEdyhlpBPrduOMw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2DwouEdyhlpBPrduOMw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2CQouEdyhlpBPrduOMw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2CAouEdyhlpBPrduOMw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2CgouEdyhlpBPrduOMw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0HLXuEduGP_98XMd0fg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0EbXuEduGP_98XMd0fg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0FbXuEduGP_98XMd0fg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0ErXuEduGP_98XMd0fg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0FLXuEduGP_98XMd0fg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0E7XuEduGP_98XMd0fg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0F7XuEduGP_98XMd0fg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0FrXuEduGP_98XMd0fg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0H7XuEduGP_98XMd0fg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0GbXuEduGP_98XMd0fg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0GLXuEduGP_98XMd0fg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0GrXuEduGP_98XMd0fg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_iNwFvMhNEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_iNwFschNEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_iNwFtchNEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_iNwFsshNEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_iNwFtMhNEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_iNwFs8hNEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_iNwFt8hNEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_iNwFtshNEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_iNwFv8hNEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_iNwFuchNEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_iNwFuMhNEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_iNwFushNEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzDJ6WEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzAZ6WEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzBZ6WEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzAp6WEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzBJ6WEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzA56WEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzB56WEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzBp6WEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzD56WEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzCZ6WEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzCJ6WEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzCp6WEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdrL8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdob8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdpb8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdor8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdpL8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdo78BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdp78BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdpr8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdr78BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdqb8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdqL8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdqr8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_NBRHzMh3EdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_NBRHwch3EdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_NBRHxch3EdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_NBRHwsh3EdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_NBRHxMh3EdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_NBRHw8h3EdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_NBRHx8h3EdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_NBRHxsh3EdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_NBRHz8h3EdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_NBRHych3EdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_NBRHyMh3EdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_NBRHysh3EdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS13J6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS10Z6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS11Z6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS10p6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS11J6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS1056YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS1156YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS11p6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS1356YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS12Z6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS12J6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS12p6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_40sbDJ6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_40sbAZ6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_40sbBZ6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_40sbAp6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_40sbBJ6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_40sbA56YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_40sbB56YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_40sbBp6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_40sbD56YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_40sbCZ6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_40sbCJ6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_40sbCp6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_IItp4MuXEdyLOriywSJkoQ#_IItp7MuXEdyLOriywSJkoQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_IItp4MuXEdyLOriywSJkoQ#_IItp4cuXEdyLOriywSJkoQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_IItp4MuXEdyLOriywSJkoQ#_IItp5cuXEdyLOriywSJkoQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_IItp4MuXEdyLOriywSJkoQ#_IItp4suXEdyLOriywSJkoQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_IItp4MuXEdyLOriywSJkoQ#_IItp5MuXEdyLOriywSJkoQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_IItp4MuXEdyLOriywSJkoQ#_IItp48uXEdyLOriywSJkoQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_IItp4MuXEdyLOriywSJkoQ#_IItp58uXEdyLOriywSJkoQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_IItp4MuXEdyLOriywSJkoQ#_IItp5suXEdyLOriywSJkoQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_IItp4MuXEdyLOriywSJkoQ#_IItp78uXEdyLOriywSJkoQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_IItp4MuXEdyLOriywSJkoQ#_IItp6cuXEdyLOriywSJkoQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_IItp4MuXEdyLOriywSJkoQ#_IItp6MuXEdyLOriywSJkoQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_IItp4MuXEdyLOriywSJkoQ#_IItp6suXEdyLOriywSJkoQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9OPG5KEdyAHIxjZ9kpqw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9OMW5KEdyAHIxjZ9kpqw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9ONW5KEdyAHIxjZ9kpqw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9OMm5KEdyAHIxjZ9kpqw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9ONG5KEdyAHIxjZ9kpqw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9OM25KEdyAHIxjZ9kpqw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9ON25KEdyAHIxjZ9kpqw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9ONm5KEdyAHIxjZ9kpqw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9OP25KEdyAHIxjZ9kpqw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9OOW5KEdyAHIxjZ9kpqw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9OOG5KEdyAHIxjZ9kpqw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9OOm5KEdyAHIxjZ9kpqw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_h_9roM3PEdyKkus0T68H3Q#_h_9rrM3PEdyKkus0T68H3Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_h_9roM3PEdyKkus0T68H3Q#_h_9roc3PEdyKkus0T68H3Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_h_9roM3PEdyKkus0T68H3Q#_h_9rpc3PEdyKkus0T68H3Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_h_9roM3PEdyKkus0T68H3Q#_h_9ros3PEdyKkus0T68H3Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_h_9roM3PEdyKkus0T68H3Q#_h_9rpM3PEdyKkus0T68H3Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_h_9roM3PEdyKkus0T68H3Q#_h_9ro83PEdyKkus0T68H3Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_h_9roM3PEdyKkus0T68H3Q#_h_9rp83PEdyKkus0T68H3Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_h_9roM3PEdyKkus0T68H3Q#_h_9rps3PEdyKkus0T68H3Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_h_9roM3PEdyKkus0T68H3Q#_h_9rr83PEdyKkus0T68H3Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_h_9roM3PEdyKkus0T68H3Q#_h_9rqc3PEdyKkus0T68H3Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_h_9roM3PEdyKkus0T68H3Q#_h_9rqM3PEdyKkus0T68H3Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_h_9roM3PEdyKkus0T68H3Q#_h_9rqs3PEdyKkus0T68H3Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExTMktEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExQcktEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExRcktEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExQsktEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExRMktEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExQ8ktEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExR8ktEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExRsktEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExT8ktEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExScktEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExSMktEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExSsktEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_GxBjDM2sEdym_ZFqrJcXUg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_GxBjAc2sEdym_ZFqrJcXUg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_GxBjBc2sEdym_ZFqrJcXUg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_GxBjAs2sEdym_ZFqrJcXUg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_GxBjBM2sEdym_ZFqrJcXUg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_GxBjA82sEdym_ZFqrJcXUg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_GxBjB82sEdym_ZFqrJcXUg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_GxBjBs2sEdym_ZFqrJcXUg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_GxBjD82sEdym_ZFqrJcXUg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_GxBjCc2sEdym_ZFqrJcXUg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_GxBjCM2sEdym_ZFqrJcXUg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_GxBjCs2sEdym_ZFqrJcXUg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS7LPREduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS4bPREduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS5bPREduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS4rPREduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS5LPREduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS47PREduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS57PREduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS5rPREduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS77PREduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS6bPREduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS6LPREduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS6rPREduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_XPLD_MudEdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_XPLD8cudEdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_XPLD9cudEdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_XPLD8sudEdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_XPLD9MudEdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_XPLD88udEdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_XPLD98udEdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_XPLD9sudEdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_XPLD_8udEdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_XPLD-cudEdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_XPLD-MudEdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_XPLD-sudEdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK3LPPEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK0bPPEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK1bPPEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK0rPPEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK1LPPEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK07PPEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK17PPEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK1rPPEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK37PPEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK2bPPEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK2LPPEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK2rPPEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_NjNCHMrmEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_NjNCEcrmEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_NjNCFcrmEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_NjNCEsrmEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_NjNCFMrmEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_NjNCE8rmEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_NjNCF8rmEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_NjNCFsrmEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_NjNCH8rmEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_NjNCGcrmEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_NjNCGMrmEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_NjNCGsrmEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKPLS9EduDY8LNbMCDBA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKMbS9EduDY8LNbMCDBA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKNbS9EduDY8LNbMCDBA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKMrS9EduDY8LNbMCDBA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKNLS9EduDY8LNbMCDBA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKM7S9EduDY8LNbMCDBA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKN7S9EduDY8LNbMCDBA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKNrS9EduDY8LNbMCDBA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKP7S9EduDY8LNbMCDBA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKObS9EduDY8LNbMCDBA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKOLS9EduDY8LNbMCDBA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKOrS9EduDY8LNbMCDBA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_00zMMMt1EdyRPtFYRAKVDg#_00zMPMt1EdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_00zMMMt1EdyRPtFYRAKVDg#_00zMMct1EdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_00zMMMt1EdyRPtFYRAKVDg#_00zMNct1EdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_00zMMMt1EdyRPtFYRAKVDg#_00zMMst1EdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_00zMMMt1EdyRPtFYRAKVDg#_00zMNMt1EdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_00zMMMt1EdyRPtFYRAKVDg#_00zMM8t1EdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_00zMMMt1EdyRPtFYRAKVDg#_00zMN8t1EdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_00zMMMt1EdyRPtFYRAKVDg#_00zMNst1EdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_00zMMMt1EdyRPtFYRAKVDg#_00zMP8t1EdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_00zMMMt1EdyRPtFYRAKVDg#_00zMOct1EdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_00zMMMt1EdyRPtFYRAKVDg#_00zMOMt1EdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_00zMMMt1EdyRPtFYRAKVDg#_00zMOst1EdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rHI7-Edy7q8CKc_B8eg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rEY7-Edy7q8CKc_B8eg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rFY7-Edy7q8CKc_B8eg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rEo7-Edy7q8CKc_B8eg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rFI7-Edy7q8CKc_B8eg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rE47-Edy7q8CKc_B8eg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rF47-Edy7q8CKc_B8eg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rFo7-Edy7q8CKc_B8eg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rH47-Edy7q8CKc_B8eg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rGY7-Edy7q8CKc_B8eg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rGI7-Edy7q8CKc_B8eg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rGo7-Edy7q8CKc_B8eg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_HYAA4MriEdyd6uFrFHNXhA#_HYAA7MriEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_HYAA4MriEdyd6uFrFHNXhA#_HYAA4criEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_HYAA4MriEdyd6uFrFHNXhA#_HYAA5criEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_HYAA4MriEdyd6uFrFHNXhA#_HYAA4sriEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_HYAA4MriEdyd6uFrFHNXhA#_HYAA5MriEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_HYAA4MriEdyd6uFrFHNXhA#_HYAA48riEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_HYAA4MriEdyd6uFrFHNXhA#_HYAA58riEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_HYAA4MriEdyd6uFrFHNXhA#_HYAA5sriEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_HYAA4MriEdyd6uFrFHNXhA#_HYAA78riEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_HYAA4MriEdyd6uFrFHNXhA#_HYAA6criEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_HYAA4MriEdyd6uFrFHNXhA#_HYAA6MriEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_HYAA4MriEdyd6uFrFHNXhA#_HYAA6sriEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfXLPaEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfUbPaEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfVbPaEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfUrPaEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfVLPaEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfU7PaEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfV7PaEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfVrPaEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfX7PaEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfWbPaEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfWLPaEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfWrPaEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_Z7teDNQ1EdyQ89W1tgswSQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_Z7teAdQ1EdyQ89W1tgswSQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_Z7teBdQ1EdyQ89W1tgswSQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_Z7teAtQ1EdyQ89W1tgswSQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_Z7teBNQ1EdyQ89W1tgswSQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_Z7teA9Q1EdyQ89W1tgswSQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_Z7teB9Q1EdyQ89W1tgswSQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_Z7teBtQ1EdyQ89W1tgswSQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_Z7teD9Q1EdyQ89W1tgswSQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_Z7teCdQ1EdyQ89W1tgswSQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_Z7teCNQ1EdyQ89W1tgswSQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_Z7teCtQ1EdyQ89W1tgswSQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_4ulTjMg7EdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_4ulTgcg7EdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_4ulThcg7EdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_4ulTgsg7EdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_4ulThMg7EdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_4ulTg8g7EdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_4ulTh8g7EdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_4ulThsg7EdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_4ulTj8g7EdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_4ulTicg7EdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_4ulTiMg7EdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_4ulTisg7EdyXeo04os5BOw"/>
+ <processViews xsi:type="org.eclipse.epf.uma:CustomCategory" href="uma://_4ulTgMg7EdyXeo04os5BOw#_Sq2EYMhAEdygFZkm1d5NtQ"/>
+ <processViews xsi:type="org.eclipse.epf.uma:CustomCategory" href="uma://_4ulTgMg7EdyXeo04os5BOw#_pA1jIMn6EdyuBO4ZIzcyig"/>
+ <defaultView xsi:type="org.eclipse.epf.uma:CustomCategory" href="uma://_4ulTgMg7EdyXeo04os5BOw#_Sq2EYMhAEdygFZkm1d5NtQ"/>
+</org.eclipse.epf.uma:MethodConfiguration>
diff --git a/praclib/temp/configurations/zconstruct.mgmt.risk_value_lifecycle.base.xmi b/praclib/temp/configurations/zconstruct.mgmt.risk_value_lifecycle.base.xmi
new file mode 100644
index 0000000..e7ffb85
--- /dev/null
+++ b/praclib/temp/configurations/zconstruct.mgmt.risk_value_lifecycle.base.xmi
@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:MethodConfiguration 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.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="_U9L9cOL6EdyM47cGD2jiaQ"
+ name="zconstruct.mgmt.risk_value_lifecycle.base" guid="_U9L9cOL6EdyM47cGD2jiaQ"
+ version="1.0.0">
+ <methodPluginSelection href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdoL8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdrb8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_LYTG0OL6EdyM47cGD2jiaQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdrr8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdob8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdrL8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdpb8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdor8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdpL8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdo78BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdp78BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdpr8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdr78BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdqb8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdqL8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdqr8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessComponent" href="uma://_FzchsOL7EdyM47cGD2jiaQ#_FzchsOL7EdyM47cGD2jiaQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessComponent" href="uma://_SKnAwOL9EdyM47cGD2jiaQ#_SKnAwOL9EdyM47cGD2jiaQ"/>
+ <processViews xsi:type="org.eclipse.epf.uma:CustomCategory" href="uma://_4ulTgMg7EdyXeo04os5BOw#_Sq2EYMhAEdygFZkm1d5NtQ"/>
+ <processViews xsi:type="org.eclipse.epf.uma:CustomCategory" href="uma://_4ulTgMg7EdyXeo04os5BOw#_pA1jIMn6EdyuBO4ZIzcyig"/>
+ <defaultView xsi:type="org.eclipse.epf.uma:CustomCategory" href="uma://_4ulTgMg7EdyXeo04os5BOw#_Sq2EYMhAEdygFZkm1d5NtQ"/>
+</org.eclipse.epf.uma:MethodConfiguration>
diff --git a/praclib/temp/configurations/zconstruct.process.openup.xmi b/praclib/temp/configurations/zconstruct.process.openup.xmi
new file mode 100644
index 0000000..84a9880
--- /dev/null
+++ b/praclib/temp/configurations/zconstruct.process.openup.xmi
@@ -0,0 +1,586 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:MethodConfiguration 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.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="_gExDwNQxEdyk9oc_L5Vk0g"
+ name="zconstruct.process.openup" guid="_gExDwNQxEdyk9oc_L5Vk0g" version="1.0.0">
+ <methodPluginSelection href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPloEFXEdy9ENCpSugIjA"/>
+ <methodPluginSelection href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno4EKmEdyrauqpmnA8jQ"/>
+ <methodPluginSelection href="uma://_iVydgENdEdy245g62lfWcA#_iVydgENdEdy245g62lfWcA"/>
+ <methodPluginSelection href="uma://_A118oMYaEdyXeo04os5BOw#_A118oMYaEdyXeo04os5BOw"/>
+ <methodPluginSelection href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVEMYbEdyXeo04os5BOw"/>
+ <methodPluginSelection href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-gEMXEdyP_Jn83ylwUQ"/>
+ <methodPluginSelection href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPEEKmEdyrauqpmnA8jQ"/>
+ <methodPluginSelection href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0TmecJ-VEdy3Nc4rvuj7bA"/>
+ <methodPluginSelection href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYucEfUEdyiPI8btkmvmw"/>
+ <methodPluginSelection href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2AAouEdyhlpBPrduOMw"/>
+ <methodPluginSelection href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0ELXuEduGP_98XMd0fg"/>
+ <methodPluginSelection href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_iNwFsMhNEdygFZkm1d5NtQ"/>
+ <methodPluginSelection href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzAJ6WEdyQN-zRFaRrCQ"/>
+ <methodPluginSelection href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdoL8BEdyWX5Yd-9QZ1A"/>
+ <methodPluginSelection href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_NBRHwMh3EdygFZkm1d5NtQ"/>
+ <methodPluginSelection href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS10J6YEdyQN-zRFaRrCQ"/>
+ <methodPluginSelection href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_40sbAJ6YEdyQN-zRFaRrCQ"/>
+ <methodPluginSelection href="uma://_IItp4MuXEdyLOriywSJkoQ#_IItp4MuXEdyLOriywSJkoQ"/>
+ <methodPluginSelection href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9OMG5KEdyAHIxjZ9kpqw"/>
+ <methodPluginSelection href="uma://_h_9roM3PEdyKkus0T68H3Q#_h_9roM3PEdyKkus0T68H3Q"/>
+ <methodPluginSelection href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExQMktEdygFZkm1d5NtQ"/>
+ <methodPluginSelection href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_GxBjAM2sEdym_ZFqrJcXUg"/>
+ <methodPluginSelection href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS4LPREduocbW-TPTq7A"/>
+ <methodPluginSelection href="uma://_XPLD8MudEdyRPtFYRAKVDg#_XPLD8MudEdyRPtFYRAKVDg"/>
+ <methodPluginSelection href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK0LPPEduocbW-TPTq7A"/>
+ <methodPluginSelection href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_NjNCEMrmEdyd6uFrFHNXhA"/>
+ <methodPluginSelection href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKMLS9EduDY8LNbMCDBA"/>
+ <methodPluginSelection href="uma://_00zMMMt1EdyRPtFYRAKVDg#_00zMMMt1EdyRPtFYRAKVDg"/>
+ <methodPluginSelection href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rEI7-Edy7q8CKc_B8eg"/>
+ <methodPluginSelection href="uma://_HYAA4MriEdyd6uFrFHNXhA#_HYAA4MriEdyd6uFrFHNXhA"/>
+ <methodPluginSelection href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfULPaEduocbW-TPTq7A"/>
+ <methodPluginSelection href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_Z7teANQ1EdyQ89W1tgswSQ"/>
+ <methodPluginSelection href="uma://_4ulTgMg7EdyXeo04os5BOw#_4ulTgMg7EdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPlrUFXEdy9ENCpSugIjA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPlrkFXEdy9ENCpSugIjA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno7UKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno7kKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iVydgENdEdy245g62lfWcA#_buz3kENfEdy245g62lfWcA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_iVydgENdEdy245g62lfWcA#_iVydjUNdEdy245g62lfWcA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_iVydgENdEdy245g62lfWcA#_iVydjkNdEdy245g62lfWcA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_A118oMYaEdyXeo04os5BOw#__0_tgBAYEdyqb5chWQXsPQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_A118oMYaEdyXeo04os5BOw#_A118rcYaEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_A118oMYaEdyXeo04os5BOw#_A118rsYaEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVHcYbEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVHsYbEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_r7UQIEMXEdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-jUMXEdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-jkMXEdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_VBd6oEMDEdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPHUKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPHkKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_QsmM8J-ZEdywNOckqfsZQg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0TmefZ-VEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0Tmefp-VEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vJYucEfUEdyiPI8btkmvmw#_xo1MYEfUEdyiPI8btkmvmw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYufUfUEdyiPI8btkmvmw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYufkfUEdyiPI8btkmvmw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_1MdooMOlEdupeqHTre3HvQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_3AcuwMOlEdupeqHTre3HvQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_119G4NPSEduegN_z1rVgJA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_cHHEIBEdEdyM7Iu0sxfrPA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_8oxCIMOlEdupeqHTre3HvQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_9ncVUBEfEdyM7Iu0sxfrPA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_-87r0BASEdyqb5chWQXsPQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_RhLBwAouEdyhlpBPrduOMw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_Vqf5EMuFEdyuBO4ZIzcyig"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2DQouEdyhlpBPrduOMw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2DgouEdyhlpBPrduOMw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_-bv0ELXuEduGP_98XMd0fg#_ip7wMJI7Edyk6dG0ehkW5Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_-bv0ELXuEduGP_98XMd0fg#__wRXALXuEduGP_98XMd0fg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0HbXuEduGP_98XMd0fg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0HrXuEduGP_98XMd0fg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_lUsBcMhNEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_iNwFvchNEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_iNwFvshNEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_BwrisJ9WEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_jRZ5EMOBEdy3nv0ZK8D4GQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_dLzj4MhPEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzDZ6WEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzDp6WEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_fiq3sL8GEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_f4YZsMN_Edy3nv0ZK8D4GQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_B3azkMh5EdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdrb8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdrr8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_2Ve24Mh3EdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_NBRHzch3EdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_NBRHzsh3EdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_hLcgcJ9WEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_q8sJwMOBEdy3nv0ZK8D4GQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS13Z6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS13p6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_VxJAUJ9WEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_idXpgMOAEdy3nv0ZK8D4GQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_40sbDZ6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_40sbDp6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_IItp4MuXEdyLOriywSJkoQ#_Z30okMuaEdy1o5Xnqdh1Tg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_IItp4MuXEdyLOriywSJkoQ#_IItp7cuXEdyLOriywSJkoQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_IItp4MuXEdyLOriywSJkoQ#_IItp7suXEdyLOriywSJkoQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_4GsDkIfxEdy1GthOId7fdw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9OPW5KEdyAHIxjZ9kpqw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9OPm5KEdyAHIxjZ9kpqw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_h_9roM3PEdyKkus0T68H3Q#_fTBSUM3REdyKkus0T68H3Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_h_9roM3PEdyKkus0T68H3Q#_h_9rrc3PEdyKkus0T68H3Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_h_9roM3PEdyKkus0T68H3Q#_h_9rrs3PEdyKkus0T68H3Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_J6WicMktEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExTcktEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExTsktEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_obUd8M2tEdym_ZFqrJcXUg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_GxBjDc2sEdym_ZFqrJcXUg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_GxBjDs2sEdym_ZFqrJcXUg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_xhaxgKtYEdytrdP46hWyHg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_NInusM3iEdyjXslGsagg_w"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#__EXZIKtYEdytrdP46hWyHg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS7bPREduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_ejTSsMQOEduMu5zRIJX95g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS7rPREduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_elKkoMueEdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_XPLD_cudEdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_XPLD_sudEdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_8A8e8NPREduegN_z1rVgJA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_PGDx8PisEdmjyaJMRcPDWA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK3bPPEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Wvf0oMQNEduMu5zRIJX95g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK3rPPEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_hBEI8MrmEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_NjNCHcrmEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_NjNCHsrmEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_yBdFENPTEduegN_z1rVgJA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_S6bmYMufEdyTA_Xoy-01eg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_qDsgQMOsEdupeqHTre3HvQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_VbrjsEL-EdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKPbS9EduDY8LNbMCDBA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKPrS9EduDY8LNbMCDBA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_00zMMMt1EdyRPtFYRAKVDg#_LE8eYMt_EdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_00zMMMt1EdyRPtFYRAKVDg#_00zMPct1EdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_00zMMMt1EdyRPtFYRAKVDg#_00zMPst1EdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_iEvlIJMPEdyaRZQqSbPe-w"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rHY7-Edy7q8CKc_B8eg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rHo7-Edy7q8CKc_B8eg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_HYAA4MriEdyd6uFrFHNXhA#_gMspkMriEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_HYAA4MriEdyd6uFrFHNXhA#_HYAA7criEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_HYAA4MriEdyd6uFrFHNXhA#_HYAA7sriEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_LVhzMLPcEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_X-RNUMuXEdyTA_Xoy-01eg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_jAZJYNPCEduegN_z1rVgJA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfXbPaEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfXrPaEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_Z7teDdQ1EdyQ89W1tgswSQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_a0pWkNOEEdyqlogshP8l4g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessComponent" href="uma://_eWxZgNOEEdyqlogshP8l4g#_eWxZgNOEEdyqlogshP8l4g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessComponent" href="uma://_oZgCsNOEEdyqlogshP8l4g#_oZgCsNOEEdyqlogshP8l4g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_OKykANONEdyqlogshP8l4g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessComponent" href="uma://_RQi0ANONEdyqlogshP8l4g#_RQi0ANONEdyqlogshP8l4g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessComponent" href="uma://_aUsVENONEdyqlogshP8l4g#_aUsVENONEdyqlogshP8l4g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessComponent" href="uma://_h0Gs8NONEdyqlogshP8l4g#_h0Gs8NONEdyqlogshP8l4g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessComponent" href="uma://_pzQU0NONEdyqlogshP8l4g#_pzQU0NONEdyqlogshP8l4g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_b_xs8NOEEdyqlogshP8l4g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessComponent" href="uma://_4ouDUNOEEdyqlogshP8l4g#_4ouDUNOEEdyqlogshP8l4g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessComponent" href="uma://_KaeNsNOFEdyqlogshP8l4g#_KaeNsNOFEdyqlogshP8l4g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessComponent" href="uma://_RXGooNOFEdyqlogshP8l4g#_RXGooNOFEdyqlogshP8l4g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessComponent" href="uma://_xxcpgNOEEdyqlogshP8l4g#_xxcpgNOEEdyqlogshP8l4g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessComponent" href="uma://__ZInMNOEEdyqlogshP8l4g#__ZInMNOEEdyqlogshP8l4g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessComponent" href="uma://_buG4sNOFEdyqlogshP8l4g#_buG4sNOFEdyqlogshP8l4g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_Z7teDtQ1EdyQ89W1tgswSQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessComponent" href="uma://_SuWj4NOPEdyqlogshP8l4g#_SuWj4NOPEdyqlogshP8l4g"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#__ZzOUMg7EdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_4ulTjcg7EdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_4ulTjsg7EdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPlrEFXEdy9ENCpSugIjA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPloUFXEdy9ENCpSugIjA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPlpUFXEdy9ENCpSugIjA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPlokFXEdy9ENCpSugIjA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPlpEFXEdy9ENCpSugIjA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPlo0FXEdy9ENCpSugIjA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPlp0FXEdy9ENCpSugIjA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPlpkFXEdy9ENCpSugIjA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPlr0FXEdy9ENCpSugIjA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPlqUFXEdy9ENCpSugIjA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPlqEFXEdy9ENCpSugIjA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPlqkFXEdy9ENCpSugIjA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno7EKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno4UKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno5UKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno4kKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno5EKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno40KmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno50KmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno5kKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno70KmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno6UKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno6EKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno6kKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iVydgENdEdy245g62lfWcA#_iVydjENdEdy245g62lfWcA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iVydgENdEdy245g62lfWcA#_iVydgUNdEdy245g62lfWcA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iVydgENdEdy245g62lfWcA#_iVydhUNdEdy245g62lfWcA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iVydgENdEdy245g62lfWcA#_iVydgkNdEdy245g62lfWcA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iVydgENdEdy245g62lfWcA#_iVydhENdEdy245g62lfWcA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iVydgENdEdy245g62lfWcA#_iVydg0NdEdy245g62lfWcA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iVydgENdEdy245g62lfWcA#_iVydh0NdEdy245g62lfWcA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iVydgENdEdy245g62lfWcA#_iVydhkNdEdy245g62lfWcA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_iVydgENdEdy245g62lfWcA#_iVydj0NdEdy245g62lfWcA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iVydgENdEdy245g62lfWcA#_iVydiUNdEdy245g62lfWcA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iVydgENdEdy245g62lfWcA#_iVydiENdEdy245g62lfWcA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iVydgENdEdy245g62lfWcA#_iVydikNdEdy245g62lfWcA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_A118oMYaEdyXeo04os5BOw#_A118rMYaEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_A118oMYaEdyXeo04os5BOw#_A118ocYaEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_A118oMYaEdyXeo04os5BOw#_A118pcYaEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_A118oMYaEdyXeo04os5BOw#_A118osYaEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_A118oMYaEdyXeo04os5BOw#_A118pMYaEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_A118oMYaEdyXeo04os5BOw#_A118o8YaEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_A118oMYaEdyXeo04os5BOw#_A118p8YaEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_A118oMYaEdyXeo04os5BOw#_A118psYaEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_A118oMYaEdyXeo04os5BOw#_A118r8YaEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_A118oMYaEdyXeo04os5BOw#_A118qcYaEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_A118oMYaEdyXeo04os5BOw#_A118qMYaEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_A118oMYaEdyXeo04os5BOw#_A118qsYaEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVHMYbEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVEcYbEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVFcYbEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVEsYbEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVFMYbEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVE8YbEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVF8YbEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVFsYbEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVH8YbEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVGcYbEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVGMYbEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVGsYbEdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-jEMXEdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-gUMXEdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-hUMXEdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-gkMXEdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-hEMXEdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-g0MXEdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-h0MXEdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-hkMXEdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-j0MXEdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-iUMXEdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-iEMXEdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-ikMXEdyP_Jn83ylwUQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPHEKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPEUKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPFUKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPEkKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPFEKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPE0KmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPF0KmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPFkKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPH0KmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPGUKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPGEKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPGkKmEdyrauqpmnA8jQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0TmefJ-VEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0TmecZ-VEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0TmedZ-VEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0Tmecp-VEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0TmedJ-VEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0Tmec5-VEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0Tmed5-VEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0Tmedp-VEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0Tmef5-VEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0TmeeZ-VEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0TmeeJ-VEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0Tmeep-VEdy3Nc4rvuj7bA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYufEfUEdyiPI8btkmvmw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYucUfUEdyiPI8btkmvmw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYudUfUEdyiPI8btkmvmw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYuckfUEdyiPI8btkmvmw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYudEfUEdyiPI8btkmvmw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYuc0fUEdyiPI8btkmvmw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYud0fUEdyiPI8btkmvmw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYudkfUEdyiPI8btkmvmw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYuf0fUEdyiPI8btkmvmw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYueUfUEdyiPI8btkmvmw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYueEfUEdyiPI8btkmvmw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYuekfUEdyiPI8btkmvmw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2DAouEdyhlpBPrduOMw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2AQouEdyhlpBPrduOMw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2BQouEdyhlpBPrduOMw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2AgouEdyhlpBPrduOMw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2BAouEdyhlpBPrduOMw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2AwouEdyhlpBPrduOMw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2BwouEdyhlpBPrduOMw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2BgouEdyhlpBPrduOMw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2DwouEdyhlpBPrduOMw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2CQouEdyhlpBPrduOMw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2CAouEdyhlpBPrduOMw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2CgouEdyhlpBPrduOMw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0HLXuEduGP_98XMd0fg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0EbXuEduGP_98XMd0fg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0FbXuEduGP_98XMd0fg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0ErXuEduGP_98XMd0fg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0FLXuEduGP_98XMd0fg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0E7XuEduGP_98XMd0fg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0F7XuEduGP_98XMd0fg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0FrXuEduGP_98XMd0fg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0H7XuEduGP_98XMd0fg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0GbXuEduGP_98XMd0fg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0GLXuEduGP_98XMd0fg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0GrXuEduGP_98XMd0fg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_iNwFvMhNEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_iNwFschNEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_iNwFtchNEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_iNwFsshNEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_iNwFtMhNEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_iNwFs8hNEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_iNwFt8hNEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_iNwFtshNEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_iNwFv8hNEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_iNwFuchNEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_iNwFuMhNEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_iNwFushNEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzDJ6WEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzAZ6WEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzBZ6WEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzAp6WEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzBJ6WEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzA56WEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzB56WEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzBp6WEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzD56WEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzCZ6WEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzCJ6WEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzCp6WEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdrL8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdob8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdpb8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdor8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdpL8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdo78BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdp78BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdpr8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdr78BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdqb8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdqL8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdqr8BEdyWX5Yd-9QZ1A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_NBRHzMh3EdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_NBRHwch3EdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_NBRHxch3EdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_NBRHwsh3EdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_NBRHxMh3EdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_NBRHw8h3EdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_NBRHx8h3EdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_NBRHxsh3EdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_NBRHz8h3EdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_NBRHych3EdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_NBRHyMh3EdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_NBRHysh3EdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS13J6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS10Z6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS11Z6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS10p6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS11J6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS1056YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS1156YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS11p6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS1356YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS12Z6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS12J6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS12p6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_40sbDJ6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_40sbAZ6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_40sbBZ6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_40sbAp6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_40sbBJ6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_40sbA56YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_40sbB56YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_40sbBp6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_40sbD56YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_40sbCZ6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_40sbCJ6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_40sbCp6YEdyQN-zRFaRrCQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_IItp4MuXEdyLOriywSJkoQ#_IItp7MuXEdyLOriywSJkoQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_IItp4MuXEdyLOriywSJkoQ#_IItp4cuXEdyLOriywSJkoQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_IItp4MuXEdyLOriywSJkoQ#_IItp5cuXEdyLOriywSJkoQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_IItp4MuXEdyLOriywSJkoQ#_IItp4suXEdyLOriywSJkoQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_IItp4MuXEdyLOriywSJkoQ#_IItp5MuXEdyLOriywSJkoQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_IItp4MuXEdyLOriywSJkoQ#_IItp48uXEdyLOriywSJkoQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_IItp4MuXEdyLOriywSJkoQ#_IItp58uXEdyLOriywSJkoQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_IItp4MuXEdyLOriywSJkoQ#_IItp5suXEdyLOriywSJkoQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_IItp4MuXEdyLOriywSJkoQ#_IItp78uXEdyLOriywSJkoQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_IItp4MuXEdyLOriywSJkoQ#_IItp6cuXEdyLOriywSJkoQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_IItp4MuXEdyLOriywSJkoQ#_IItp6MuXEdyLOriywSJkoQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_IItp4MuXEdyLOriywSJkoQ#_IItp6suXEdyLOriywSJkoQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9OPG5KEdyAHIxjZ9kpqw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9OMW5KEdyAHIxjZ9kpqw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9ONW5KEdyAHIxjZ9kpqw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9OMm5KEdyAHIxjZ9kpqw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9ONG5KEdyAHIxjZ9kpqw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9OM25KEdyAHIxjZ9kpqw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9ON25KEdyAHIxjZ9kpqw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9ONm5KEdyAHIxjZ9kpqw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9OP25KEdyAHIxjZ9kpqw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9OOW5KEdyAHIxjZ9kpqw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9OOG5KEdyAHIxjZ9kpqw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9OOm5KEdyAHIxjZ9kpqw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_h_9roM3PEdyKkus0T68H3Q#_h_9rrM3PEdyKkus0T68H3Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_h_9roM3PEdyKkus0T68H3Q#_h_9roc3PEdyKkus0T68H3Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_h_9roM3PEdyKkus0T68H3Q#_h_9rpc3PEdyKkus0T68H3Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_h_9roM3PEdyKkus0T68H3Q#_h_9ros3PEdyKkus0T68H3Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_h_9roM3PEdyKkus0T68H3Q#_h_9rpM3PEdyKkus0T68H3Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_h_9roM3PEdyKkus0T68H3Q#_h_9ro83PEdyKkus0T68H3Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_h_9roM3PEdyKkus0T68H3Q#_h_9rp83PEdyKkus0T68H3Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_h_9roM3PEdyKkus0T68H3Q#_h_9rps3PEdyKkus0T68H3Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_h_9roM3PEdyKkus0T68H3Q#_h_9rr83PEdyKkus0T68H3Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_h_9roM3PEdyKkus0T68H3Q#_h_9rqc3PEdyKkus0T68H3Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_h_9roM3PEdyKkus0T68H3Q#_h_9rqM3PEdyKkus0T68H3Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_h_9roM3PEdyKkus0T68H3Q#_h_9rqs3PEdyKkus0T68H3Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExTMktEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExQcktEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExRcktEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExQsktEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExRMktEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExQ8ktEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExR8ktEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExRsktEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExT8ktEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExScktEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExSMktEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExSsktEdygFZkm1d5NtQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_GxBjDM2sEdym_ZFqrJcXUg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_GxBjAc2sEdym_ZFqrJcXUg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_GxBjBc2sEdym_ZFqrJcXUg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_GxBjAs2sEdym_ZFqrJcXUg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_GxBjBM2sEdym_ZFqrJcXUg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_GxBjA82sEdym_ZFqrJcXUg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_GxBjB82sEdym_ZFqrJcXUg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_GxBjBs2sEdym_ZFqrJcXUg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_GxBjD82sEdym_ZFqrJcXUg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_GxBjCc2sEdym_ZFqrJcXUg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_GxBjCM2sEdym_ZFqrJcXUg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_GxBjCs2sEdym_ZFqrJcXUg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS7LPREduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS4bPREduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS5bPREduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS4rPREduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS5LPREduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS47PREduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS57PREduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS5rPREduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS77PREduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS6bPREduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS6LPREduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS6rPREduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_XPLD_MudEdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_XPLD8cudEdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_XPLD9cudEdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_XPLD8sudEdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_XPLD9MudEdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_XPLD88udEdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_XPLD98udEdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_XPLD9sudEdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_XPLD_8udEdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_XPLD-cudEdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_XPLD-MudEdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_XPLD-sudEdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK3LPPEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK0bPPEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK1bPPEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK0rPPEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK1LPPEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK07PPEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK17PPEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK1rPPEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK37PPEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK2bPPEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK2LPPEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK2rPPEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_NjNCHMrmEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_NjNCEcrmEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_NjNCFcrmEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_NjNCEsrmEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_NjNCFMrmEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_NjNCE8rmEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_NjNCF8rmEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_NjNCFsrmEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_NjNCH8rmEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_NjNCGcrmEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_NjNCGMrmEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_NjNCGsrmEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKPLS9EduDY8LNbMCDBA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKMbS9EduDY8LNbMCDBA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKNbS9EduDY8LNbMCDBA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKMrS9EduDY8LNbMCDBA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKNLS9EduDY8LNbMCDBA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKM7S9EduDY8LNbMCDBA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKN7S9EduDY8LNbMCDBA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKNrS9EduDY8LNbMCDBA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKP7S9EduDY8LNbMCDBA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKObS9EduDY8LNbMCDBA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKOLS9EduDY8LNbMCDBA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKOrS9EduDY8LNbMCDBA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_00zMMMt1EdyRPtFYRAKVDg#_00zMPMt1EdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_00zMMMt1EdyRPtFYRAKVDg#_00zMMct1EdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_00zMMMt1EdyRPtFYRAKVDg#_00zMNct1EdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_00zMMMt1EdyRPtFYRAKVDg#_00zMMst1EdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_00zMMMt1EdyRPtFYRAKVDg#_00zMNMt1EdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_00zMMMt1EdyRPtFYRAKVDg#_00zMM8t1EdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_00zMMMt1EdyRPtFYRAKVDg#_00zMN8t1EdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_00zMMMt1EdyRPtFYRAKVDg#_00zMNst1EdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_00zMMMt1EdyRPtFYRAKVDg#_00zMP8t1EdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_00zMMMt1EdyRPtFYRAKVDg#_00zMOct1EdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_00zMMMt1EdyRPtFYRAKVDg#_00zMOMt1EdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_00zMMMt1EdyRPtFYRAKVDg#_00zMOst1EdyRPtFYRAKVDg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rHI7-Edy7q8CKc_B8eg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rEY7-Edy7q8CKc_B8eg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rFY7-Edy7q8CKc_B8eg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rEo7-Edy7q8CKc_B8eg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rFI7-Edy7q8CKc_B8eg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rE47-Edy7q8CKc_B8eg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rF47-Edy7q8CKc_B8eg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rFo7-Edy7q8CKc_B8eg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rH47-Edy7q8CKc_B8eg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rGY7-Edy7q8CKc_B8eg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rGI7-Edy7q8CKc_B8eg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rGo7-Edy7q8CKc_B8eg"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_HYAA4MriEdyd6uFrFHNXhA#_HYAA7MriEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_HYAA4MriEdyd6uFrFHNXhA#_HYAA4criEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_HYAA4MriEdyd6uFrFHNXhA#_HYAA5criEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_HYAA4MriEdyd6uFrFHNXhA#_HYAA4sriEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_HYAA4MriEdyd6uFrFHNXhA#_HYAA5MriEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_HYAA4MriEdyd6uFrFHNXhA#_HYAA48riEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_HYAA4MriEdyd6uFrFHNXhA#_HYAA58riEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_HYAA4MriEdyd6uFrFHNXhA#_HYAA5sriEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_HYAA4MriEdyd6uFrFHNXhA#_HYAA78riEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_HYAA4MriEdyd6uFrFHNXhA#_HYAA6criEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_HYAA4MriEdyd6uFrFHNXhA#_HYAA6MriEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_HYAA4MriEdyd6uFrFHNXhA#_HYAA6sriEdyd6uFrFHNXhA"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfXLPaEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfUbPaEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfVbPaEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfUrPaEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfVLPaEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfU7PaEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfV7PaEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfVrPaEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfX7PaEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfWbPaEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfWLPaEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfWrPaEduocbW-TPTq7A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_Z7teDNQ1EdyQ89W1tgswSQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_Z7teAdQ1EdyQ89W1tgswSQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_Z7teBdQ1EdyQ89W1tgswSQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_Z7teAtQ1EdyQ89W1tgswSQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_Z7teBNQ1EdyQ89W1tgswSQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_Z7teA9Q1EdyQ89W1tgswSQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_Z7teB9Q1EdyQ89W1tgswSQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_Z7teBtQ1EdyQ89W1tgswSQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_Z7teD9Q1EdyQ89W1tgswSQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_Z7teCdQ1EdyQ89W1tgswSQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_Z7teCNQ1EdyQ89W1tgswSQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_Z7teCtQ1EdyQ89W1tgswSQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_4ulTjMg7EdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_4ulTgcg7EdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_4ulThcg7EdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_4ulTgsg7EdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_4ulThMg7EdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_4ulTg8g7EdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_4ulTh8g7EdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_4ulThsg7EdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_4ulTj8g7EdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_4ulTicg7EdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_4ulTiMg7EdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_4ulTisg7EdyXeo04os5BOw"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_3aT48N4YEdyhmsbt0Xyl8A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_vJYucEfUEdyiPI8btkmvmw#_gxGj0N8-Edyhmsbt0Xyl8A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_Ks_WoOCiEdynptYdmll41Q"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_bGjA8OFQEdyhmsbt0Xyl8A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_gfuaMOFSEdyhmsbt0Xyl8A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_fRdVEMYbEdyXeo04os5BOw#_w_1EkOFUEdyhmsbt0Xyl8A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_lFkpUOFlEdyhmsbt0Xyl8A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_onU40OFlEdyhmsbt0Xyl8A"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ContentPackage" href="uma://_4ulTgMg7EdyXeo04os5BOw#_cxOwQOL0EdyM47cGD2jiaQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessPackage" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_LYTG0OL6EdyM47cGD2jiaQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessComponent" href="uma://_FzchsOL7EdyM47cGD2jiaQ#_FzchsOL7EdyM47cGD2jiaQ"/>
+ <methodPackageSelection xsi:type="org.eclipse.epf.uma:ProcessComponent" href="uma://_SKnAwOL9EdyM47cGD2jiaQ#_SKnAwOL9EdyM47cGD2jiaQ"/>
+ <processViews xsi:type="org.eclipse.epf.uma:CustomCategory" href="uma://_4ulTgMg7EdyXeo04os5BOw#_Sq2EYMhAEdygFZkm1d5NtQ"/>
+ <subtractedCategory xsi:type="org.eclipse.epf.uma:CustomCategory" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_O3UtkMRdEdyD76CYS6Ta7A"/>
+</org.eclipse.epf.uma:MethodConfiguration>
diff --git a/praclib/temp/core.default.cat_def.base/.project b/praclib/temp/core.default.cat_def.base/.project
new file mode 100644
index 0000000..04f06c8
--- /dev/null
+++ b/praclib/temp/core.default.cat_def.base/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>core.default.cat_def.base</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/core.default.cat_def.base/customcategories/resources/report_dgm32.gif b/praclib/temp/core.default.cat_def.base/customcategories/resources/report_dgm32.gif
new file mode 100644
index 0000000..1f86c7e
--- /dev/null
+++ b/praclib/temp/core.default.cat_def.base/customcategories/resources/report_dgm32.gif
Binary files differ
diff --git a/praclib/temp/core.default.cat_def.base/customcategories/resources/report_obj.gif b/praclib/temp/core.default.cat_def.base/customcategories/resources/report_obj.gif
new file mode 100644
index 0000000..c22c85e
--- /dev/null
+++ b/praclib/temp/core.default.cat_def.base/customcategories/resources/report_obj.gif
Binary files differ
diff --git a/praclib/temp/core.default.cat_def.base/customcategories/resources/roles_dgm32.gif b/praclib/temp/core.default.cat_def.base/customcategories/resources/roles_dgm32.gif
new file mode 100644
index 0000000..baa3d33
--- /dev/null
+++ b/praclib/temp/core.default.cat_def.base/customcategories/resources/roles_dgm32.gif
Binary files differ
diff --git a/praclib/temp/core.default.cat_def.base/customcategories/resources/roles_obj.gif b/praclib/temp/core.default.cat_def.base/customcategories/resources/roles_obj.gif
new file mode 100644
index 0000000..90b1aae
--- /dev/null
+++ b/praclib/temp/core.default.cat_def.base/customcategories/resources/roles_obj.gif
Binary files differ
diff --git a/praclib/temp/core.default.cat_def.base/customcategories/resources/template_dgm32.gif b/praclib/temp/core.default.cat_def.base/customcategories/resources/template_dgm32.gif
new file mode 100644
index 0000000..8fab4e8
--- /dev/null
+++ b/praclib/temp/core.default.cat_def.base/customcategories/resources/template_dgm32.gif
Binary files differ
diff --git a/praclib/temp/core.default.cat_def.base/customcategories/resources/template_obj.gif b/praclib/temp/core.default.cat_def.base/customcategories/resources/template_obj.gif
new file mode 100644
index 0000000..ca5f822
--- /dev/null
+++ b/praclib/temp/core.default.cat_def.base/customcategories/resources/template_obj.gif
Binary files differ
diff --git a/praclib/temp/core.default.cat_def.base/disciplines/architecture_discipline.xmi b/praclib/temp/core.default.cat_def.base/disciplines/architecture_discipline.xmi
new file mode 100644
index 0000000..6f62214
--- /dev/null
+++ b/praclib/temp/core.default.cat_def.base/disciplines/architecture_discipline.xmi
@@ -0,0 +1,36 @@
+<?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="-IDdeF_boiqzJJnjpXrdLFQ"
+ name="architecture_discipline,_iGSHsFZ-EdyIUdvDLLUdeg" guid="-IDdeF_boiqzJJnjpXrdLFQ"
+ changeDate="2008-02-09T16:24:59.406-0500" version="7.2.0">
+ <mainDescription><p>
+ The purpose of this discipline is to evolve a robust architecture for the system.
+</p>
+<p>
+ The Architecture discipline is related to other disciplines, as follows:
+</p>
+<ul>
+ <li>
+ The <a class="elementLink"
+ href="./../../core.default.cat_def.base/disciplines/requirements_discipline_9520664.html"
+ guid="_iGSHtVZ-EdyIUdvDLLUdeg">Requirements</a>&nbsp;discipline provides the architecturally significant
+ requirements.
+ </li>
+ <li>
+ The <a class="elementLink"
+ href="./../../core.default.cat_def.base/disciplines/development_discipline_44C02445.html"
+ guid="_iGSHsVZ-EdyIUdvDLLUdeg">Development</a>&nbsp;discipline designs and implements the architecture.
+ </li>
+ <li>
+ The <a class="elementLink" href="./../../core.default.cat_def.base/disciplines/test_discipline_F7EB1A7A.html"
+ guid="_iGSHtlZ-EdyIUdvDLLUdeg">Test</a>&nbsp;discipline verifies the stability and correctness of the architecture.
+ </li>
+ <li>
+ The <a class="elementLink"
+ href="./../../core.default.cat_def.base/disciplines/project_management_discipline_FEB42654.html"
+ guid="_iGSHtFZ-EdyIUdvDLLUdeg">Project Management</a>&nbsp;discipline plans the project, and each iteration.
+ </li>
+</ul></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.cat_def.base/disciplines/configuration_and_change_management_discipline.xmi b/praclib/temp/core.default.cat_def.base/disciplines/configuration_and_change_management_discipline.xmi
new file mode 100644
index 0000000..e2dc2e1
--- /dev/null
+++ b/praclib/temp/core.default.cat_def.base/disciplines/configuration_and_change_management_discipline.xmi
@@ -0,0 +1,58 @@
+<?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="-Jyj---_Uk8ov3TxMK3Iijg"
+ name="configuration_and_change_management_discipline,_iGSHslZ-EdyIUdvDLLUdeg"
+ guid="-Jyj---_Uk8ov3TxMK3Iijg" changeDate="2008-01-18T18:25:39.921-0500">
+ <mainDescription><p>
+ The purpose of this discipline is to:
+</p>
+<ul>
+ <li>
+ Maintain a consistent set of work products as they evolve
+ </li>
+ <li>
+ Maintain consistent builds of the software
+ </li>
+ <li>
+ Provide an efficient means to adapt to changes and issues, and re-plan work accordingly
+ </li>
+ <li>
+ Provide data for measuring progress
+ </li>
+</ul>
+<p>
+ In many organizations, the term "configuration management" implies all of these things.
+</p>
+<p>
+ Within the context of this process, configuration management refers to the ability to maintain <a class="elementLink"
+ href="./resources/version_F3A31B17.html" guid="_eX8K8ElyEducWJcS4yanqg">version</a>s of artifacts and consistent <a
+ class="elementLink" href="./resources/configuration_FE64B3D8.html" guid="__Cw30ElxEducWJcS4yanqg">configuration</a>s of
+ artifacts, addressing the first two objectives listed above. Change Management refers to the process of managing
+ changes to configuration-controlled artifacts, addressing the latter two objectives listed above.
+</p>
+<p>
+ Although it is important to keep up-to-date versions and configurations of all work products, the primary work products
+ of concern are the <a class="elementLinkWithType" href="./resources/implementation_917CA61E.html"
+ guid="_0YoQcMlgEdmt3adZL5Dmdw">Artifact: Implementation</a> and the <a class="elementLinkWithType"
+ href="./resources/build_95D7D8FD.html" guid="_0YuXEMlgEdmt3adZL5Dmdw">Artifact: Build</a>.
+</p>
+<p>
+ Changes are managed via the <a class="elementLinkWithType" href="./resources/request_change_A048C387.html"
+ guid="_0mwzEclgEdmt3adZL5Dmdw">Task: Request Change</a> and subsequent prioritization and disposition of change
+ requests via the <a class="elementLinkWithType"
+ href="./../../practice.mgmt.iterative_dev.base/workproducts/work_items_list_39D03CC8.html"
+ guid="_rGNWsCbSEdqh1LYUOGRh2A">Artifact: Work Items List</a>.
+</p>
+<p>
+ This discipline spans the entire lifecycle. Every other discipline relies upon the configuration and change management
+ discipline to maintain a consistent, up-to-date, set of work products -- and to prioritize and track changes to those
+ work products -- throughout the lifecycle.
+</p>
+<p>
+ Configuration and change management is performed by everyone on the development team. Because of the importance and
+ pervasiveness of this discipline, configuration and change management guidance is associated with tasks and work
+ products in all other disciplines.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.cat_def.base/disciplines/development_discipline.xmi b/praclib/temp/core.default.cat_def.base/disciplines/development_discipline.xmi
new file mode 100644
index 0000000..e36e73c
--- /dev/null
+++ b/praclib/temp/core.default.cat_def.base/disciplines/development_discipline.xmi
@@ -0,0 +1,65 @@
+<?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="-aa7DMnmSG7Hlkpi_-yb3XA"
+ name="development_discipline,_iGSHsVZ-EdyIUdvDLLUdeg" guid="-aa7DMnmSG7Hlkpi_-yb3XA"
+ changeDate="2008-01-18T18:32:10.968-0500">
+ <mainDescription><p>
+ The purpose of this discipline is to:
+</p>
+<ul>
+ <li>
+ Transform the requirements into a design of the system-to-be
+ </li>
+ <li>
+ Adapt the design to match the implementation environment
+ </li>
+ <li>
+ Build the system incrementally
+ </li>
+ <li>
+ Verify that the technical units used to build the system work as specified
+ </li>
+</ul>
+<p>
+ With each iteration, the tasks in this discipline will evolve an ever more capable and ever more stable <a
+ class="elementLink" href="./resources/build_95D7D8FD.html" guid="_0YuXEMlgEdmt3adZL5Dmdw">Build</a>.
+</p>
+<p>
+ When working on the system, the <a class="elementLink"
+ href="./../../core.default.role_def.base/roles/developer_C633AB7.html" guid="_0YDosMlgEdmt3adZL5Dmdw">Developer</a>
+ will both use and be constrained by the architecture.
+</p>
+<p>
+ This discipline is related to the other disciplines in the following ways:
+</p>
+<ul>
+ <li>
+ The <a class="elementLink"
+ href="./../../core.default.cat_def.base/disciplines/requirements_discipline_9520664.html"
+ guid="_iGSHtVZ-EdyIUdvDLLUdeg">Requirements</a> discipline defines what will be designed and implemented.
+ </li>
+ <li>
+ The <a class="elementLink"
+ href="./../../core.default.cat_def.base/disciplines/architecture_discipline_3A224435.html"
+ guid="_iGSHsFZ-EdyIUdvDLLUdeg">Architecture</a> discipline organizes and constrains the design and implementation.
+ </li>
+ <li>
+ The <a class="elementLink" href="./../../core.default.cat_def.base/disciplines/test_discipline_F7EB1A7A.html"
+ guid="_iGSHtlZ-EdyIUdvDLLUdeg">Test</a> discipline validates that system built meets the requirements.
+ </li>
+ <li>
+ The&nbsp;<a class="elementLink"
+ href="./../../core.default.cat_def.base/disciplines/configuration_and_change_management_discipline_3359385B.html"
+ guid="_iGSHslZ-EdyIUdvDLLUdeg">Configuration and Change Management</a> discipline provides the mechanisms to
+ manage changes to the system built.
+ </li>
+ <li>
+ The <a class="elementLink"
+ href="./../../core.default.cat_def.base/disciplines/project_management_discipline_FEB42654.html"
+ guid="_iGSHtFZ-EdyIUdvDLLUdeg">Project Management</a>&nbsp;discipline plans what functionality will be implemented
+ in each iteration.
+ </li>
+</ul></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.cat_def.base/disciplines/project_management_discipline.xmi b/praclib/temp/core.default.cat_def.base/disciplines/project_management_discipline.xmi
new file mode 100644
index 0000000..88abbd2
--- /dev/null
+++ b/praclib/temp/core.default.cat_def.base/disciplines/project_management_discipline.xmi
@@ -0,0 +1,45 @@
+<?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="-JR-x8arulRODu1y2tP928w"
+ name="project_management_discipline,_iGSHtFZ-EdyIUdvDLLUdeg" guid="-JR-x8arulRODu1y2tP928w"
+ changeDate="2008-01-18T18:26:47.265-0500">
+ <mainDescription><p>
+ The purpose of this discipline is to: &nbsp;
+</p>
+<ul>
+ <li>
+ Encourage stakeholder&nbsp;consensus on prioritizing the sequence of work
+ </li>
+ <li>
+ Stimulate team collaboration on creating long term and short term plans for the project.
+ </li>
+ <li>
+ Focus the team on continually delivering tested software for stakeholder evaluation
+ </li>
+ <li>
+ Help create an effective working environment to maximize team productivity
+ </li>
+ <li>
+ Keep stakeholders and the team informed on project progress
+ </li>
+ <li>
+ Provide a framework to manage project risk and continually adapt to change
+ </li>
+</ul>
+<p>
+ Project Management is an umbrella discipline which impacts, and is impacted by, all other disciplines. Project
+ management activities add value to creating a high performance work environment where:
+</p>
+<ul>
+ <li>
+ Stakeholders trust in the team’s ability to successfully deliver value and understand the capabilities and
+ tradeoffs of the technical platform
+ </li>
+ <li>
+ Project team members understand stakeholder intentions and confirm that understanding by continually producing a
+ working software product for evaluation<br />
+ </li>
+</ul></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.cat_def.base/disciplines/requirements_discipline.xmi b/praclib/temp/core.default.cat_def.base/disciplines/requirements_discipline.xmi
new file mode 100644
index 0000000..1b9905d
--- /dev/null
+++ b/praclib/temp/core.default.cat_def.base/disciplines/requirements_discipline.xmi
@@ -0,0 +1,81 @@
+<?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="-i5J2T1z4y0Y1dFcHm78XXg"
+ name="requirements_discipline,_iGSHtVZ-EdyIUdvDLLUdeg" guid="-i5J2T1z4y0Y1dFcHm78XXg"
+ changeDate="2008-01-18T18:27:16.031-0500">
+ <mainDescription><p>
+ The purpose of this discipline is to:
+</p>
+<ul>
+ <li>
+ Understand the problem to be solved
+ </li>
+ <li>
+ Understand stakeholder needs (what users want)
+ </li>
+ <li>
+ Define the requirements for the solution (what the system must do)
+ </li>
+ <li>
+ Define the boundaries (scope) of the system
+ </li>
+ <li>
+ Identify external interfaces for the system
+ </li>
+ <li>
+ Identify technical constraints on the solution
+ </li>
+ <li>
+ Provide the basis for planning iterations
+ </li>
+ <li>
+ Provide the initial basis for estimating cost and schedule
+ </li>
+</ul>
+<p>
+ To achieve these goals, it is important to understand the definition and scope of the problem that you are trying to
+ solve. Identify <a class="elementLinkWithUserText"
+ href="./../../core.default.role_def.base/roles/stakeholder_9FFD4106.html"
+ guid="_dTa6gMAYEdqX-s4mWhkyqQ">Stakeholders</a> and define the problem to be solved.
+</p>
+<p>
+ Having agreed on the problem to be solved, the <a class="elementLink"
+ href="./../../core.tech.slot.base/guidances/concepts/requirements_8006414F.html"
+ guid="_0Wh-sMlgEdmt3adZL5Dmdw">Requirements</a> for the system are elicited, organized, analyzed, validated, and
+ specified.
+</p>
+<p>
+ Throughout the lifecycle, you manage changes to the requirements.
+</p>
+<p>
+ The Requirements discipline is related to the other disciplines in the following ways:
+</p>
+<ul>
+ <li>
+ The <a class="elementLink"
+ href="./../../core.default.cat_def.base/disciplines/architecture_discipline_3A224435.html"
+ guid="_iGSHsFZ-EdyIUdvDLLUdeg">Architecture</a> and <a class="elementLink"
+ href="./../../core.default.cat_def.base/disciplines/development_discipline_44C02445.html"
+ guid="_iGSHsVZ-EdyIUdvDLLUdeg">Development</a>&nbsp;disciplines get&nbsp;their primary input from the Requirements
+ discipline.
+ </li>
+ <li>
+ The <a class="elementLink" href="./../../core.default.cat_def.base/disciplines/test_discipline_F7EB1A7A.html"
+ guid="_iGSHtlZ-EdyIUdvDLLUdeg">Test</a> discipline validates the system against the requirements.
+ </li>
+ <li>
+ The <a class="elementLink"
+ href="./../../core.default.cat_def.base/disciplines/configuration_and_change_management_discipline_3359385B.html"
+ guid="_iGSHslZ-EdyIUdvDLLUdeg">Configuration and Change Management</a> discipline provides the mechanisms to
+ manage changes to the requirements.
+ </li>
+ <li>
+ The <a class="elementLink"
+ href="./../../core.default.cat_def.base/disciplines/project_management_discipline_FEB42654.html"
+ guid="_iGSHtFZ-EdyIUdvDLLUdeg">Project Management</a>&nbsp;discipline plans the project and assigns requirements to
+ each iteration by analyzing the prioritized requirements and assigning work.
+ </li>
+</ul></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.cat_def.base/disciplines/test_discipline.xmi b/praclib/temp/core.default.cat_def.base/disciplines/test_discipline.xmi
new file mode 100644
index 0000000..3f26e96
--- /dev/null
+++ b/praclib/temp/core.default.cat_def.base/disciplines/test_discipline.xmi
@@ -0,0 +1,76 @@
+<?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="-yVQcZlwHTZIT9-i97PVUYQ"
+ name="test_discipline,_iGSHtlZ-EdyIUdvDLLUdeg" guid="-yVQcZlwHTZIT9-i97PVUYQ"
+ changeDate="2008-01-18T18:27:31.062-0500">
+ <mainDescription><p>
+ he purpose of this discipline is to:
+</p>
+<ul>
+ <li>
+ Provide early and frequent <em>feedback</em> that the system satisfies the requirements
+ </li>
+ <li>
+ Objectively measure progress in small increments
+ </li>
+ <li>
+ Identify issues with the solution
+ </li>
+ <li>
+ Provide assurance that changes to the system do not introduce new defects
+ </li>
+ <li>
+ Improve velocity by facilitating the discovery of issues with requirements, designs, and implementations as early
+ as possible
+ </li>
+</ul>
+<p>
+ The Test discipline is iterative and incremental. It applies the strategy of “test early and test often” in order to
+ retire risks as early in the system’s lifecycle as possible.
+</p>
+<p>
+ Testing occurs in each iteration of the lifecycle, beginning with the earliest builds of the system. In fact, it’s
+ common for one iteration to have many test cycles, depending on the frequency of new builds.
+</p>
+<p>
+ Testing asks the question: “What does the Solution have to <em>do</em> in order for us to consider a requirement
+ implemented?” Tests elaborate on the requirements with specific conditions of satisfaction that the Solution must meet.
+</p>
+<p>
+ This discipline challenges the assumptions, risks, and uncertainty inherent in the development of highly technical
+ artifacts, and addresses those concerns using concrete demonstration and impartial evaluation.
+</p>
+<p>
+ The Test discipline relates to the other disciplines in the following ways:
+</p>
+<ul>
+ <li>
+ The <a class="elementLink"
+ href="./../../core.default.cat_def.base/disciplines/requirements_discipline_9520664.html"
+ guid="_iGSHtVZ-EdyIUdvDLLUdeg">Requirements</a> discipline identifies the <em>intent</em> of the system. Testing
+ elaborates on the requirements with detailed tests that measure how the system supports the requirements.
+ </li>
+ <li>
+ The <a class="elementLink"
+ href="./../../core.default.cat_def.base/disciplines/development_discipline_44C02445.html"
+ guid="_iGSHsVZ-EdyIUdvDLLUdeg">Development</a> discipline creates incremental builds of the system that the Test
+ discipline evaluates. In each iteration, testing provides objective feedback. Effective testing enables Developers
+ to focus on implementing new functionality, and improving the design of the system.
+ </li>
+ <li>
+ The <a class="elementLink"
+ href="./../../core.default.cat_def.base/disciplines/project_management_discipline_FEB42654.html"
+ guid="_iGSHtFZ-EdyIUdvDLLUdeg">Project Management</a> discipline plans the overall project, and the scope of work,
+ for each iteration. The Test discipline provides an objective measure of progress, which enables adaptive planning.
+ </li>
+ <li>
+ The <a class="elementLink"
+ href="./../../core.default.cat_def.base/disciplines/configuration_and_change_management_discipline_3359385B.html"
+ guid="_iGSHslZ-EdyIUdvDLLUdeg">Configuration and Change Management</a>&nbsp;discipline controls changes within the
+ project. The test effort verifies that each change to the Solution is tested appropriately. Test assets are kept
+ under configuration management.
+ </li>
+</ul></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.cat_def.base/plugin.xmi b/praclib/temp/core.default.cat_def.base/plugin.xmi
new file mode 100644
index 0000000..cd90bbc
--- /dev/null
+++ b/praclib/temp/core.default.cat_def.base/plugin.xmi
@@ -0,0 +1,124 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_MRPlsUFXEdy9ENCpSugIjA"
+ guid="_MRPlsUFXEdy9ENCpSugIjA">
+ <resourceDescriptors xmi:id="_lZiRIcYcEdyXeo04os5BOw" id="-IDdeF_boiqzJJnjpXrdLFQ"
+ uri="disciplines/architecture_discipline.xmi"/>
+ <resourceDescriptors xmi:id="_KKbmEcYdEdyXeo04os5BOw" id="-Jyj---_Uk8ov3TxMK3Iijg"
+ uri="disciplines/configuration_and_change_management_discipline.xmi"/>
+ <resourceDescriptors xmi:id="_KKlXEMYdEdyXeo04os5BOw" id="-JR-x8arulRODu1y2tP928w"
+ uri="disciplines/project_management_discipline.xmi"/>
+ <resourceDescriptors xmi:id="_KKuhAMYdEdyXeo04os5BOw" id="-i5J2T1z4y0Y1dFcHm78XXg"
+ uri="disciplines/requirements_discipline.xmi"/>
+ <resourceDescriptors xmi:id="_KKuhAcYdEdyXeo04os5BOw" id="-yVQcZlwHTZIT9-i97PVUYQ"
+ uri="disciplines/test_discipline.xmi"/>
+ <resourceDescriptors xmi:id="_K8f8McYdEdyXeo04os5BOw" id="-aa7DMnmSG7Hlkpi_-yb3XA"
+ uri="disciplines/development_discipline.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_MRPloEFXEdy9ENCpSugIjA" name="core.default.cat_def.base"
+ guid="_MRPloEFXEdy9ENCpSugIjA" briefDescription="This plug-in contains the default definitions for the following: Roles, Domains, Disciplines, (Work Product Kinds, if we decide we want them). It also defines custom categories for Formal (and Informal - or is this just at cmr level??) templates."
+ changeDate="2008-01-18T18:14:38.515-0500">
+ <copyrightStatement href="uma://_iVydgENdEdy245g62lfWcA#_cTs20KzREduOqvpk_MDLfQ"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_MRPloUFXEdy9ENCpSugIjA"
+ name="Content" guid="_MRPloUFXEdy9ENCpSugIjA">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_MRPlokFXEdy9ENCpSugIjA"
+ name="Categories" guid="_MRPlokFXEdy9ENCpSugIjA">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_MRPlo0FXEdy9ENCpSugIjA"
+ name="Domains" guid="_MRPlo0FXEdy9ENCpSugIjA">
+ <contentElements xsi:type="org.eclipse.epf.uma:Domain" xmi:id="_1r0bcK80Edy9cPK11VzBuQ"
+ name="architecture_domain" guid="_1r0bcK80Edy9cPK11VzBuQ" briefDescription="This is the list of work products related to architecture domain."
+ presentationName="Architecture"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:Domain" xmi:id="_5JQLoK80Edy9cPK11VzBuQ"
+ name="development_domain" guid="_5JQLoK80Edy9cPK11VzBuQ" briefDescription="This is the list of work products related to development domain."
+ presentationName="Development"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:Domain" xmi:id="_8M6J4K80Edy9cPK11VzBuQ"
+ name="project_management_domain" guid="_8M6J4K80Edy9cPK11VzBuQ" briefDescription="This is the list of work products related to project management domain."
+ presentationName="Project Management"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:Domain" xmi:id="_AIcLUK81Edy9cPK11VzBuQ"
+ name="requirements_domain" guid="_AIcLUK81Edy9cPK11VzBuQ" briefDescription="This is the list of work products related to requirements domain."
+ presentationName="Requirements"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:Domain" xmi:id="_CsgDgK81Edy9cPK11VzBuQ"
+ name="test_domain" guid="_CsgDgK81Edy9cPK11VzBuQ" briefDescription="This is the list of work products related to test domain."
+ presentationName="Test"/>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_MRPlpEFXEdy9ENCpSugIjA"
+ name="Disciplines" guid="_MRPlpEFXEdy9ENCpSugIjA">
+ <contentElements xsi:type="org.eclipse.epf.uma:Discipline" xmi:id="_iGSHsFZ-EdyIUdvDLLUdeg"
+ name="architecture_discipline" guid="_iGSHsFZ-EdyIUdvDLLUdeg" briefDescription="This discipline explains how to create an architecture from architecturally significant requirements. The architecture is built in the Development discipline."
+ presentationName="Architecture">
+ <presentation xmi:id="-IDdeF_boiqzJJnjpXrdLFQ" href="uma://-IDdeF_boiqzJJnjpXrdLFQ#-IDdeF_boiqzJJnjpXrdLFQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Discipline" xmi:id="_iGSHsVZ-EdyIUdvDLLUdeg"
+ name="development_discipline" guid="_iGSHsVZ-EdyIUdvDLLUdeg" briefDescription="This discipline explains how to design and implement a technical solution that conforms to the architecture and supports the requirements."
+ presentationName="Development">
+ <presentation xmi:id="-aa7DMnmSG7Hlkpi_-yb3XA" href="uma://-aa7DMnmSG7Hlkpi_-yb3XA#-aa7DMnmSG7Hlkpi_-yb3XA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Discipline" xmi:id="_iGSHslZ-EdyIUdvDLLUdeg"
+ name="configuration_and_change_management_discipline" guid="_iGSHslZ-EdyIUdvDLLUdeg"
+ briefDescription="This discipline explains how to control changes to artifacts, ensuring synchronized evolution of the set of Work Products composing a software system."
+ presentationName="Configuration and Change Management">
+ <presentation xmi:id="-Jyj---_Uk8ov3TxMK3Iijg" href="uma://-Jyj---_Uk8ov3TxMK3Iijg#-Jyj---_Uk8ov3TxMK3Iijg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Discipline" xmi:id="_iGSHtFZ-EdyIUdvDLLUdeg"
+ name="project_management_discipline" guid="_iGSHtFZ-EdyIUdvDLLUdeg"
+ briefDescription="This discipline explains how to coach, facilitate and support the team, helping it to deal with risk and obstacles found when building software."
+ presentationName="Project Management">
+ <presentation xmi:id="-JR-x8arulRODu1y2tP928w" href="uma://-JR-x8arulRODu1y2tP928w#-JR-x8arulRODu1y2tP928w"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Discipline" xmi:id="_iGSHtVZ-EdyIUdvDLLUdeg"
+ name="requirements_discipline" guid="_iGSHtVZ-EdyIUdvDLLUdeg" briefDescription="This discipline explains how to elicit, analyze, specify, validate, and manage the requirements for the system to be developed."
+ presentationName="Requirements">
+ <presentation xmi:id="-i5J2T1z4y0Y1dFcHm78XXg" href="uma://-i5J2T1z4y0Y1dFcHm78XXg#-i5J2T1z4y0Y1dFcHm78XXg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Discipline" xmi:id="_iGSHtlZ-EdyIUdvDLLUdeg"
+ name="test_discipline" guid="_iGSHtlZ-EdyIUdvDLLUdeg" briefDescription="This discipline explains how to provide feedback about the maturing system by designing, implementing, running, and evaluating tests."
+ presentationName="Test">
+ <presentation xmi:id="-yVQcZlwHTZIT9-i97PVUYQ" href="uma://-yVQcZlwHTZIT9-i97PVUYQ#-yVQcZlwHTZIT9-i97PVUYQ"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_MRPlpUFXEdy9ENCpSugIjA"
+ name="RoleSets" guid="_MRPlpUFXEdy9ENCpSugIjA"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_MRPlpkFXEdy9ENCpSugIjA"
+ name="WP Types" guid="_MRPlpkFXEdy9ENCpSugIjA"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_MRPlp0FXEdy9ENCpSugIjA"
+ name="Tools" guid="_MRPlp0FXEdy9ENCpSugIjA"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_MRPlqEFXEdy9ENCpSugIjA"
+ name="StandardCategories" guid="_MRPlqEFXEdy9ENCpSugIjA"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_MRPlqUFXEdy9ENCpSugIjA"
+ name="CustomCategories" guid="_MRPlqUFXEdy9ENCpSugIjA">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_MRPlqkFXEdy9ENCpSugIjA"
+ name="Hidden" guid="_MRPlqkFXEdy9ENCpSugIjA">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_MRPlq0FXEdy9ENCpSugIjA"
+ name="Custom Categories" guid="_MRPlq0FXEdy9ENCpSugIjA" categorizedElements="_7-mEYMYaEdyXeo04os5BOw _StPmkMYbEdyXeo04os5BOw"/>
+ </childPackages>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_7-mEYMYaEdyXeo04os5BOw"
+ name="discipline_list.disciplines" guid="_7-mEYMYaEdyXeo04os5BOw" variabilityType="contributes"
+ categorizedElements="_iGSHsFZ-EdyIUdvDLLUdeg _iGSHslZ-EdyIUdvDLLUdeg _iGSHsVZ-EdyIUdvDLLUdeg _iGSHtFZ-EdyIUdvDLLUdeg _iGSHtVZ-EdyIUdvDLLUdeg _iGSHtlZ-EdyIUdvDLLUdeg">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_PxzG4MRfEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_StPmkMYbEdyXeo04os5BOw"
+ name="domain_list.domains" guid="_StPmkMYbEdyXeo04os5BOw" variabilityType="contributes"
+ categorizedElements="_1r0bcK80Edy9cPK11VzBuQ _5JQLoK80Edy9cPK11VzBuQ _8M6J4K80Edy9cPK11VzBuQ _AIcLUK81Edy9cPK11VzBuQ _CsgDgK81Edy9cPK11VzBuQ">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_EfGDkMRfEdyD76CYS6Ta7A"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_MRPlrEFXEdy9ENCpSugIjA"
+ name="CoreContent" guid="_MRPlrEFXEdy9ENCpSugIjA"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_MRPlrUFXEdy9ENCpSugIjA"
+ name="CapabilityPatterns" guid="_MRPlrUFXEdy9ENCpSugIjA"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_MRPlrkFXEdy9ENCpSugIjA"
+ name="DeliveryProcesses" guid="_MRPlrkFXEdy9ENCpSugIjA"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_MRPlr0FXEdy9ENCpSugIjA"
+ name="ProcessContributions" guid="_MRPlr0FXEdy9ENCpSugIjA"/>
+ <bases href="uma://_iVydgENdEdy245g62lfWcA#_iVydgENdEdy245g62lfWcA"/>
+ <bases href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno4EKmEdyrauqpmnA8jQ"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/core.default.nav_view.base/.project b/praclib/temp/core.default.nav_view.base/.project
new file mode 100644
index 0000000..b8d0098
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>core.default.nav_view.base</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/navigation_view_generic.xmi b/praclib/temp/core.default.nav_view.base/customcategories/navigation_view_generic.xmi
new file mode 100644
index 0000000..b936055
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/navigation_view_generic.xmi
@@ -0,0 +1,7 @@
+<?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: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="-9Tmr_SLa7cTvE0oKQS0ASA"
+ name="navigation_view_generic,_1-9JoEKmEdyrauqpmnA8jQ" guid="-9Tmr_SLa7cTvE0oKQS0ASA"
+ changeDate="2008-01-16T12:59:29.812-0500" version="7.1.0"/>
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/Artifact.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/Artifact.gif
new file mode 100644
index 0000000..501d219
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/Artifact.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/Deliverable.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/Deliverable.gif
new file mode 100644
index 0000000..9ae222a
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/Deliverable.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/DeliverableL.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/DeliverableL.gif
new file mode 100644
index 0000000..cdfe62e
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/DeliverableL.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/Outcome.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/Outcome.gif
new file mode 100644
index 0000000..4903da3
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/Outcome.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/OutcomeL.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/OutcomeL.gif
new file mode 100644
index 0000000..c673882
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/OutcomeL.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/RoleL.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/RoleL.gif
new file mode 100644
index 0000000..abfa4c6
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/RoleL.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/artifactL.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/artifactL.gif
new file mode 100644
index 0000000..ba1e4fe
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/artifactL.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/bookc.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/bookc.gif
new file mode 100644
index 0000000..7f2ab85
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/bookc.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/bookcL.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/bookcL.gif
new file mode 100644
index 0000000..6c5b064
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/bookcL.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/capabilitypattern16.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/capabilitypattern16.gif
new file mode 100644
index 0000000..15ffbb0
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/capabilitypattern16.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/checklist_dgm32.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/checklist_dgm32.gif
new file mode 100644
index 0000000..08acd0e
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/checklist_dgm32.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/checklist_obj.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/checklist_obj.gif
new file mode 100644
index 0000000..88f6d8b
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/checklist_obj.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/compass.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/compass.gif
new file mode 100644
index 0000000..39f306a
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/compass.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/compassL.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/compassL.gif
new file mode 100644
index 0000000..4117414
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/compassL.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/concept_dgm32.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/concept_dgm32.gif
new file mode 100644
index 0000000..fa195bd
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/concept_dgm32.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/concept_obj.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/concept_obj.gif
new file mode 100644
index 0000000..03af38b
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/concept_obj.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/delproc_lg_dgm32.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/delproc_lg_dgm32.gif
new file mode 100644
index 0000000..3b9c93e
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/delproc_lg_dgm32.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/delproc_obj.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/delproc_obj.gif
new file mode 100644
index 0000000..dcc7373
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/delproc_obj.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/discipline_dgm32.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/discipline_dgm32.gif
new file mode 100644
index 0000000..5c3484d
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/discipline_dgm32.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/discipline_obj.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/discipline_obj.gif
new file mode 100644
index 0000000..51d0e44
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/discipline_obj.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/estimationconsiderations16.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/estimationconsiderations16.gif
new file mode 100644
index 0000000..4fc84e4
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/estimationconsiderations16.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/estimationconsiderations32.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/estimationconsiderations32.gif
new file mode 100644
index 0000000..aed4c3a
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/estimationconsiderations32.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/example_dgm32.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/example_dgm32.gif
new file mode 100644
index 0000000..9699cef
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/example_dgm32.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/example_obj.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/example_obj.gif
new file mode 100644
index 0000000..0e84a3c
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/example_obj.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/false.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/false.gif
new file mode 100644
index 0000000..7b665d7
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/false.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/guide_dgm32.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/guide_dgm32.gif
new file mode 100644
index 0000000..5a9f688
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/guide_dgm32.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/guide_obj.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/guide_obj.gif
new file mode 100644
index 0000000..36866d9
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/guide_obj.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/lib_16.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/lib_16.gif
new file mode 100644
index 0000000..00a311e
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/lib_16.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/lib_32.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/lib_32.gif
new file mode 100644
index 0000000..cae5c19
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/lib_32.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/mic.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/mic.gif
new file mode 100644
index 0000000..0b316db
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/mic.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/micL.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/micL.gif
new file mode 100644
index 0000000..1826cbd
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/micL.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/new.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/new.gif
new file mode 100644
index 0000000..7039631
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/new.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/newL.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/newL.gif
new file mode 100644
index 0000000..74dfffa
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/newL.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/pract_dgm32.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/pract_dgm32.gif
new file mode 100644
index 0000000..f597332
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/pract_dgm32.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/pract_obj.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/pract_obj.gif
new file mode 100644
index 0000000..fe8075a
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/pract_obj.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/reasset_dgm32.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/reasset_dgm32.gif
new file mode 100644
index 0000000..e274ac9
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/reasset_dgm32.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/reasset_obj.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/reasset_obj.gif
new file mode 100644
index 0000000..49227f3
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/reasset_obj.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/report_dgm32.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/report_dgm32.gif
new file mode 100644
index 0000000..1f86c7e
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/report_dgm32.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/report_obj.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/report_obj.gif
new file mode 100644
index 0000000..c22c85e
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/report_obj.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/roadmap16.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/roadmap16.gif
new file mode 100644
index 0000000..7ee9126
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/roadmap16.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/roadmap32.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/roadmap32.gif
new file mode 100644
index 0000000..2fc513b
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/roadmap32.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/role.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/role.gif
new file mode 100644
index 0000000..69ebdf2
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/role.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/roles_dgm32.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/roles_dgm32.gif
new file mode 100644
index 0000000..baa3d33
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/roles_dgm32.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/roles_obj.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/roles_obj.gif
new file mode 100644
index 0000000..90b1aae
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/roles_obj.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/supmat_dgm32.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/supmat_dgm32.gif
new file mode 100644
index 0000000..7bd1a30
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/supmat_dgm32.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/supmat_obj.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/supmat_obj.gif
new file mode 100644
index 0000000..a5a88f6
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/supmat_obj.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/task_dgm32.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/task_dgm32.gif
new file mode 100644
index 0000000..a91ea1c
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/task_dgm32.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/task_obj.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/task_obj.gif
new file mode 100644
index 0000000..7633d58
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/task_obj.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/template_dgm32.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/template_dgm32.gif
new file mode 100644
index 0000000..8fab4e8
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/template_dgm32.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/template_obj.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/template_obj.gif
new file mode 100644
index 0000000..ca5f822
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/template_obj.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/toolment_lg_dgm32.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/toolment_lg_dgm32.gif
new file mode 100644
index 0000000..c6c0098
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/toolment_lg_dgm32.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/toolment_obj.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/toolment_obj.gif
new file mode 100644
index 0000000..ed4c89a
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/toolment_obj.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/white_lg_dgm32.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/white_lg_dgm32.gif
new file mode 100644
index 0000000..7f817f7
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/white_lg_dgm32.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/white_obj.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/white_obj.gif
new file mode 100644
index 0000000..138bdfe
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/white_obj.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/workproduct_dgm32.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/workproduct_dgm32.gif
new file mode 100644
index 0000000..009c9af
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/workproduct_dgm32.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/workproduct_obj.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/workproduct_obj.gif
new file mode 100644
index 0000000..3e58c6f
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/workproduct_obj.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/workproducts_lg_obj.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/workproducts_lg_obj.gif
new file mode 100644
index 0000000..deca591
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/workproducts_lg_obj.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/workproducts_obj.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/workproducts_obj.gif
new file mode 100644
index 0000000..2e097ce
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/workproducts_obj.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/workproductstype_lg_obj.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/workproductstype_lg_obj.gif
new file mode 100644
index 0000000..626c9fd
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/workproductstype_lg_obj.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/customcategories/resources/workproductstype_obj.gif b/praclib/temp/core.default.nav_view.base/customcategories/resources/workproductstype_obj.gif
new file mode 100644
index 0000000..d04a7ad
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/customcategories/resources/workproductstype_obj.gif
Binary files differ
diff --git a/praclib/temp/core.default.nav_view.base/plugin.xmi b/praclib/temp/core.default.nav_view.base/plugin.xmi
new file mode 100644
index 0000000..8271cae
--- /dev/null
+++ b/praclib/temp/core.default.nav_view.base/plugin.xmi
@@ -0,0 +1,184 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_vsno8UKmEdyrauqpmnA8jQ"
+ guid="_vsno8UKmEdyrauqpmnA8jQ">
+ <resourceDescriptors xmi:id="_qGuh8UKnEdyrauqpmnA8jQ" id="-9Tmr_SLa7cTvE0oKQS0ASA"
+ uri="customcategories/navigation_view_generic.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_vsno4EKmEdyrauqpmnA8jQ" name="core.default.nav_view.base"
+ guid="_vsno4EKmEdyrauqpmnA8jQ" briefDescription="Defines the basic building blocks to be used for defining views and a generic view gor general usage. Note that at some point, some of these custom categories may be replaced by smart categories or query based views."
+ changeDate="2008-03-03T16:24:37.745-0500">
+ <copyrightStatement href="uma://_iVydgENdEdy245g62lfWcA#_cTs20KzREduOqvpk_MDLfQ"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_vsno4UKmEdyrauqpmnA8jQ"
+ name="Content" guid="_vsno4UKmEdyrauqpmnA8jQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_vsno4kKmEdyrauqpmnA8jQ"
+ name="Categories" guid="_vsno4kKmEdyrauqpmnA8jQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_vsno40KmEdyrauqpmnA8jQ"
+ name="Domains" guid="_vsno40KmEdyrauqpmnA8jQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_vsno5EKmEdyrauqpmnA8jQ"
+ name="Disciplines" guid="_vsno5EKmEdyrauqpmnA8jQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_vsno5UKmEdyrauqpmnA8jQ"
+ name="RoleSets" guid="_vsno5UKmEdyrauqpmnA8jQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_vsno5kKmEdyrauqpmnA8jQ"
+ name="WP Types" guid="_vsno5kKmEdyrauqpmnA8jQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_vsno50KmEdyrauqpmnA8jQ"
+ name="Tools" guid="_vsno50KmEdyrauqpmnA8jQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_vsno6EKmEdyrauqpmnA8jQ"
+ name="StandardCategories" guid="_vsno6EKmEdyrauqpmnA8jQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_vsno6UKmEdyrauqpmnA8jQ"
+ name="CustomCategories" guid="_vsno6UKmEdyrauqpmnA8jQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_vsno6kKmEdyrauqpmnA8jQ"
+ name="Hidden" guid="_vsno6kKmEdyrauqpmnA8jQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_vsno60KmEdyrauqpmnA8jQ"
+ name="Custom Categories" guid="_vsno60KmEdyrauqpmnA8jQ" categorizedElements="_1-9JoEKmEdyrauqpmnA8jQ _O3UtkMRdEdyD76CYS6Ta7A _QbmjwMRdEdyD76CYS6Ta7A"/>
+ </childPackages>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_1-9JoEKmEdyrauqpmnA8jQ"
+ name="navigation_view_generic" guid="_1-9JoEKmEdyrauqpmnA8jQ" presentationName="Navigation View (Generic)"
+ shapeicon="customcategories/resources/lib_32.gif" nodeicon="customcategories/resources/lib_16.gif"
+ categorizedElements="_WCIHYMRdEdyD76CYS6Ta7A _WCIHYsRdEdyD76CYS6Ta7A _h-lc4MReEdyD76CYS6Ta7A _WCIHY8RdEdyD76CYS6Ta7A _4IC8cMRgEdyD76CYS6Ta7A __O1Y8MRgEdyD76CYS6Ta7A _CXQicMRhEdyD76CYS6Ta7A _qdO80MRhEdyD76CYS6Ta7A _WCIHYcRdEdyD76CYS6Ta7A">
+ <presentation xmi:id="-9Tmr_SLa7cTvE0oKQS0ASA" href="uma://-9Tmr_SLa7cTvE0oKQS0ASA#-9Tmr_SLa7cTvE0oKQS0ASA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_O3UtkMRdEdyD76CYS6Ta7A"
+ name="do_not_publish" guid="_O3UtkMRdEdyD76CYS6Ta7A" briefDescription="Category slot for elements not to be published, should be included as a subtractive category in every configuration"
+ presentationName="Do NOT Publish" nodeicon="customcategories/resources/false.gif"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_QbmjwMRdEdyD76CYS6Ta7A"
+ name="nav_view_building_blocks" guid="_QbmjwMRdEdyD76CYS6Ta7A" briefDescription="Do not include this category, it is just a container for the standard navigational elements"
+ presentationName="Navigation Building Blocks" categorizedElements="_WCIHYMRdEdyD76CYS6Ta7A _WCIHYcRdEdyD76CYS6Ta7A _WCIHYsRdEdyD76CYS6Ta7A _h-lc4MReEdyD76CYS6Ta7A _WCIHZMRdEdyD76CYS6Ta7A _WCR4YMRdEdyD76CYS6Ta7A _WCR4YcRdEdyD76CYS6Ta7A _WCR4YsRdEdyD76CYS6Ta7A _pGt9MMReEdyD76CYS6Ta7A _WCR4Y8RdEdyD76CYS6Ta7A _WCR4ZMRdEdyD76CYS6Ta7A _WCR4ZcRdEdyD76CYS6Ta7A _WCIHY8RdEdyD76CYS6Ta7A _auUD0NQuEdyM_J8-fv54DA _lBrxENQuEdyM_J8-fv54DA _sJd8gMReEdyD76CYS6Ta7A _ZWrWcMRfEdyD76CYS6Ta7A _WCR4ZsRdEdyD76CYS6Ta7A _WCR4Z8RdEdyD76CYS6Ta7A _WCR4acRdEdyD76CYS6Ta7A _Km2E8MRfEdyD76CYS6Ta7A _EfGDkMRfEdyD76CYS6Ta7A _HcVQwMRfEdyD76CYS6Ta7A _PxzG4MRfEdyD76CYS6Ta7A _VTspMMRfEdyD76CYS6Ta7A">
+ <methodElementProperty xmi:id="_Q3xiYMRdEdyD76CYS6Ta7A" name="CategoryElementsSortType"
+ value="Manual"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_WCIHYMRdEdyD76CYS6Ta7A"
+ name="getting_started_list" guid="_WCIHYMRdEdyD76CYS6Ta7A" briefDescription="Background information and additional guidance for new users."
+ presentationName="Getting Started" shapeicon="customcategories/resources/micL.gif"
+ nodeicon="customcategories/resources/mic.gif"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_WCIHYcRdEdyD76CYS6Ta7A"
+ name="release_info" guid="_WCIHYcRdEdyD76CYS6Ta7A" briefDescription="Information regarding what's changed in the content can be found here. This includes a list of version and method managment information including contacts if applicable."
+ presentationName="Release Information" shapeicon="customcategories/resources/newL.gif"
+ nodeicon="customcategories/resources/new.gif"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_WCIHYsRdEdyD76CYS6Ta7A"
+ name="delivery_process_list" guid="_WCIHYsRdEdyD76CYS6Ta7A" briefDescription="This provides a list of delivery processes that have been published."
+ presentationName="Delivery Processes" shapeicon="customcategories/resources/delproc_lg_dgm32.gif"
+ nodeicon="customcategories/resources/delproc_obj.gif"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_WCIHY8RdEdyD76CYS6Ta7A"
+ name="practice_list" guid="_WCIHY8RdEdyD76CYS6Ta7A" briefDescription="Listing of included practices."
+ presentationName="Practices" shapeicon="customcategories/resources/pract_dgm32.gif"
+ nodeicon="customcategories/resources/pract_obj.gif"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_WCIHZMRdEdyD76CYS6Ta7A"
+ name="role_list" guid="_WCIHZMRdEdyD76CYS6Ta7A" briefDescription="Alphabetical list of all included roles."
+ presentationName="All Roles" shapeicon="customcategories/resources/RoleL.gif"
+ nodeicon="customcategories/resources/role.gif"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_WCR4YMRdEdyD76CYS6Ta7A"
+ name="artifact_list" guid="_WCR4YMRdEdyD76CYS6Ta7A" briefDescription="Alphabetical listing of all included artifacts (tangible inputs/outputs)."
+ presentationName="All Artifacts" shapeicon="customcategories/resources/artifactL.gif"
+ nodeicon="customcategories/resources/Artifact.gif">
+ <methodElementProperty xmi:id="_WDLQQMRdEdyD76CYS6Ta7A" name="CategoryElementsSortType"
+ value="Alphabetic"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_WCR4YcRdEdyD76CYS6Ta7A"
+ name="deliverable_list" guid="_WCR4YcRdEdyD76CYS6Ta7A" briefDescription="Alphabetical listing of all included deliverables."
+ presentationName="All Deliverables" shapeicon="customcategories/resources/DeliverableL.gif"
+ nodeicon="customcategories/resources/Deliverable.gif">
+ <methodElementProperty xmi:id="_WDLQQcRdEdyD76CYS6Ta7A" name="CategoryElementsSortType"
+ value="Alphabetic"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_WCR4YsRdEdyD76CYS6Ta7A"
+ name="outcome_list" guid="_WCR4YsRdEdyD76CYS6Ta7A" briefDescription="Alphabetical list of all included outcomes (intangible inputs/outputs)."
+ presentationName="All Outcomes" shapeicon="customcategories/resources/OutcomeL.gif"
+ nodeicon="customcategories/resources/Outcome.gif"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_WCR4Y8RdEdyD76CYS6Ta7A"
+ name="concept_list" guid="_WCR4Y8RdEdyD76CYS6Ta7A" briefDescription="Alphabetical list of included concepts (guidance that provides basic background information)."
+ presentationName="Concepts" shapeicon="customcategories/resources/concept_dgm32.gif"
+ nodeicon="customcategories/resources/concept_obj.gif"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_WCR4ZMRdEdyD76CYS6Ta7A"
+ name="example_list" guid="_WCR4ZMRdEdyD76CYS6Ta7A" briefDescription="Alphabetical list of included examples."
+ presentationName="Examples" shapeicon="customcategories/resources/example_dgm32.gif"
+ nodeicon="customcategories/resources/example_obj.gif"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_WCR4ZcRdEdyD76CYS6Ta7A"
+ name="guideline_list" guid="_WCR4ZcRdEdyD76CYS6Ta7A" briefDescription="Alphabetical list of included guidelines (general guidance on how to perform tasks or create work products)."
+ presentationName="Guidelines" shapeicon="customcategories/resources/guide_dgm32.gif"
+ nodeicon="customcategories/resources/guide_obj.gif"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_WCR4ZsRdEdyD76CYS6Ta7A"
+ name="roadmap_list" guid="_WCR4ZsRdEdyD76CYS6Ta7A" briefDescription="List of included roadmaps (provide guidance on overall process)."
+ presentationName="Roadmaps" shapeicon="customcategories/resources/roadmap32.gif"
+ nodeicon="customcategories/resources/roadmap16.gif"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_WCR4Z8RdEdyD76CYS6Ta7A"
+ name="template_list" guid="_WCR4Z8RdEdyD76CYS6Ta7A" briefDescription="Alphabetical list of included templates."
+ presentationName="Templates" shapeicon="customcategories/resources/template_dgm32.gif"
+ nodeicon="customcategories/resources/template_obj.gif"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_WCR4acRdEdyD76CYS6Ta7A"
+ name="whitepaper_list" guid="_WCR4acRdEdyD76CYS6Ta7A" briefDescription="Alphabetical list of included white papers (formal guidance on additional topics)."
+ presentationName="White Papers" shapeicon="customcategories/resources/white_lg_dgm32.gif"
+ nodeicon="customcategories/resources/white_obj.gif"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_h-lc4MReEdyD76CYS6Ta7A"
+ name="capability_pattern_list" guid="_h-lc4MReEdyD76CYS6Ta7A" presentationName="Capability Patterns"
+ nodeicon="customcategories/resources/capabilitypattern16.gif"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_pGt9MMReEdyD76CYS6Ta7A"
+ name="checklist_list" guid="_pGt9MMReEdyD76CYS6Ta7A" presentationName="Checklists"
+ shapeicon="customcategories/resources/checklist_dgm32.gif" nodeicon="customcategories/resources/checklist_obj.gif"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_sJd8gMReEdyD76CYS6Ta7A"
+ name="report_list" guid="_sJd8gMReEdyD76CYS6Ta7A" presentationName="Reports"
+ shapeicon="customcategories/resources/report_dgm32.gif" nodeicon="customcategories/resources/report_obj.gif"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_EfGDkMRfEdyD76CYS6Ta7A"
+ name="domain_list" guid="_EfGDkMRfEdyD76CYS6Ta7A" presentationName="Domains"
+ shapeicon="customcategories/resources/workproducts_lg_obj.gif" nodeicon="customcategories/resources/workproducts_obj.gif"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_HcVQwMRfEdyD76CYS6Ta7A"
+ name="wp_kind_list" guid="_HcVQwMRfEdyD76CYS6Ta7A" presentationName="WP Kinds"
+ shapeicon="customcategories/resources/workproductstype_lg_obj.gif" nodeicon="customcategories/resources/workproductstype_obj.gif"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_Km2E8MRfEdyD76CYS6Ta7A"
+ name="role_set_list" guid="_Km2E8MRfEdyD76CYS6Ta7A" presentationName="Role Sets"
+ shapeicon="customcategories/resources/roles_dgm32.gif" nodeicon="customcategories/resources/roles_obj.gif"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_PxzG4MRfEdyD76CYS6Ta7A"
+ name="discipline_list" guid="_PxzG4MRfEdyD76CYS6Ta7A" presentationName="Disciplines"
+ shapeicon="customcategories/resources/discipline_dgm32.gif" nodeicon="customcategories/resources/discipline_obj.gif"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_VTspMMRfEdyD76CYS6Ta7A"
+ name="tool_list" guid="_VTspMMRfEdyD76CYS6Ta7A" presentationName="Tools"
+ shapeicon="customcategories/resources/toolment_lg_dgm32.gif" nodeicon="customcategories/resources/toolment_obj.gif"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_ZWrWcMRfEdyD76CYS6Ta7A"
+ name="reusable_asset_list" guid="_ZWrWcMRfEdyD76CYS6Ta7A" presentationName="Reusable Assets"
+ shapeicon="customcategories/resources/reasset_dgm32.gif" nodeicon="customcategories/resources/reasset_obj.gif"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_4IC8cMRgEdyD76CYS6Ta7A"
+ name="roles" guid="_4IC8cMRgEdyD76CYS6Ta7A" presentationName="Roles"
+ shapeicon="customcategories/resources/roles_dgm32.gif" nodeicon="customcategories/resources/roles_obj.gif"
+ categorizedElements="_Km2E8MRfEdyD76CYS6Ta7A _WCIHZMRdEdyD76CYS6Ta7A"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="__O1Y8MRgEdyD76CYS6Ta7A"
+ name="work_products" guid="__O1Y8MRgEdyD76CYS6Ta7A" presentationName="Work Products"
+ shapeicon="customcategories/resources/workproduct_dgm32.gif" nodeicon="customcategories/resources/workproduct_obj.gif"
+ categorizedElements="_EfGDkMRfEdyD76CYS6Ta7A _HcVQwMRfEdyD76CYS6Ta7A _WCR4YMRdEdyD76CYS6Ta7A _WCR4YcRdEdyD76CYS6Ta7A _WCR4YsRdEdyD76CYS6Ta7A"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_CXQicMRhEdyD76CYS6Ta7A"
+ name="tasks" guid="_CXQicMRhEdyD76CYS6Ta7A" presentationName="Tasks"
+ shapeicon="customcategories/resources/discipline_dgm32.gif" nodeicon="customcategories/resources/discipline_obj.gif"
+ categorizedElements="_PxzG4MRfEdyD76CYS6Ta7A"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_qdO80MRhEdyD76CYS6Ta7A"
+ name="guidance" guid="_qdO80MRhEdyD76CYS6Ta7A" presentationName="Guidance"
+ shapeicon="customcategories/resources/bookcL.gif" nodeicon="customcategories/resources/bookc.gif"
+ categorizedElements="_pGt9MMReEdyD76CYS6Ta7A _WCR4Y8RdEdyD76CYS6Ta7A _WCR4ZMRdEdyD76CYS6Ta7A _WCR4ZcRdEdyD76CYS6Ta7A _WCIHY8RdEdyD76CYS6Ta7A _sJd8gMReEdyD76CYS6Ta7A _ZWrWcMRfEdyD76CYS6Ta7A _WCR4ZsRdEdyD76CYS6Ta7A _WCR4Z8RdEdyD76CYS6Ta7A _VTspMMRfEdyD76CYS6Ta7A _WCR4acRdEdyD76CYS6Ta7A"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_auUD0NQuEdyM_J8-fv54DA"
+ name="management_practice_list" guid="_auUD0NQuEdyM_J8-fv54DA" presentationName="Management Practices"
+ shapeicon="customcategories/resources/pract_dgm32.gif" nodeicon="customcategories/resources/pract_obj.gif">
+ <methodElementProperty xmi:id="_e5Ec8NRCEdyM_J8-fv54DA" name="CategoryElementsSortType"
+ value="Alphabetic"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_lBrxENQuEdyM_J8-fv54DA"
+ name="technical_practice_list" guid="_lBrxENQuEdyM_J8-fv54DA" presentationName="Technical Practices"
+ shapeicon="customcategories/resources/pract_dgm32.gif" nodeicon="customcategories/resources/pract_obj.gif">
+ <methodElementProperty xmi:id="_gSxa0NRCEdyM_J8-fv54DA" name="CategoryElementsSortType"
+ value="Alphabetic"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_vsno7EKmEdyrauqpmnA8jQ"
+ name="CoreContent" guid="_vsno7EKmEdyrauqpmnA8jQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_vsno7UKmEdyrauqpmnA8jQ"
+ name="CapabilityPatterns" guid="_vsno7UKmEdyrauqpmnA8jQ"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_vsno7kKmEdyrauqpmnA8jQ"
+ name="DeliveryProcesses" guid="_vsno7kKmEdyrauqpmnA8jQ"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_vsno70KmEdyrauqpmnA8jQ"
+ name="ProcessContributions" guid="_vsno70KmEdyrauqpmnA8jQ"/>
+ <bases href="uma://_iVydgENdEdy245g62lfWcA#_iVydgENdEdy245g62lfWcA"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/core.default.release_copyright.base/.project b/praclib/temp/core.default.release_copyright.base/.project
new file mode 100644
index 0000000..a1d3680
--- /dev/null
+++ b/praclib/temp/core.default.release_copyright.base/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>core.default.release_copyright.base</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/core.default.release_copyright.base/guidances/supportingmaterials/copyright.oup.xmi b/praclib/temp/core.default.release_copyright.base/guidances/supportingmaterials/copyright.oup.xmi
new file mode 100644
index 0000000..bca8f10
--- /dev/null
+++ b/praclib/temp/core.default.release_copyright.base/guidances/supportingmaterials/copyright.oup.xmi
@@ -0,0 +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: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="-PZ0CqCcJHB-nbxs8fbP7bg"
+ name="copyright.oup,_cTs20KzREduOqvpk_MDLfQ" guid="-PZ0CqCcJHB-nbxs8fbP7bg"
+ changeDate="2007-08-10T12:11:51.906-0700" version="1.0.0">
+ <mainDescription><p>
+ <a class="elementLink"
+ href="./../../../core.default.release_copyright.base/guidances/supportingmaterials/openup_copyright_C3031062.html"
+ guid="_UaGfECcTEduSX6N2jUafGA">OpenUP Copyright</a>.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.release_copyright.base/guidances/supportingmaterials/copyright.xmi b/praclib/temp/core.default.release_copyright.base/guidances/supportingmaterials/copyright.xmi
new file mode 100644
index 0000000..9aac2d3
--- /dev/null
+++ b/praclib/temp/core.default.release_copyright.base/guidances/supportingmaterials/copyright.xmi
@@ -0,0 +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: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="_u_Zg4PsDEdmyhNQr5STrZQ"
+ name="copyright,_uuunoPsDEdmyhNQr5STrZQ" guid="_u_Zg4PsDEdmyhNQr5STrZQ" changeDate="2007-01-25T19:10:08.377-0500"
+ version="1.0.0">
+ <mainDescription><p>
+ This program and the accompanying materials are made available under the<br />
+ <a href="http://www.eclipse.org/org/documents/epl-v10.php" target="_blank" >Eclipse Public License v1.0</a> which
+ accompanies this distribution.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.release_copyright.base/guidances/supportingmaterials/openup_copyright.xmi b/praclib/temp/core.default.release_copyright.base/guidances/supportingmaterials/openup_copyright.xmi
new file mode 100644
index 0000000..f9f878d
--- /dev/null
+++ b/praclib/temp/core.default.release_copyright.base/guidances/supportingmaterials/openup_copyright.xmi
@@ -0,0 +1,18 @@
+<?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: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="-RNyaB6jxqoopm9fJU8k9vg"
+ name="new_supporting_material,_UaGfECcTEduSX6N2jUafGA" guid="-RNyaB6jxqoopm9fJU8k9vg"
+ changeDate="2007-01-31T16:45:05.478-0800" version="1.0.0">
+ <mainDescription><p>
+ &copy; Copyright IBM Corp. 1987, 2006. All Rights Reserved.<br />
+ &copy; Copyright Telelogic AB. 2006, 2007. All Rights Reserved.<br />
+ &copy; Copyright Armstrong Process Group, Inc. 2006. All Rights Reserved.<br />
+ &copy; Copyright Number Six Software, Inc. 2006, 2007. All Rights Reserved.<br />
+ &copy; Copyright Xansa plc.2006, 2007. All Rights Reserved.<br />
+</p>
+<p>
+ And others. All Rights Reserved.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.release_copyright.base/guidances/supportingmaterials/resources/copyrite.htm b/praclib/temp/core.default.release_copyright.base/guidances/supportingmaterials/resources/copyrite.htm
new file mode 100644
index 0000000..51edd3a
--- /dev/null
+++ b/praclib/temp/core.default.release_copyright.base/guidances/supportingmaterials/resources/copyrite.htm
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<title>IBM(R) Rational(R) Intellectual Property Notices and Other Licensing Requirements</title>
+</head>
+
+<body>
+NOTICES AND INFORMATION <br />
+<br />
+<p>
+ These Notices apply to portions of this Program. They are not part of the license under which you receive the Program
+ and are provided for informational purposes.
+</p>
+<p>
+About This Content
+</p>
+<p>
+May 2, 2006
+</p>
+<p>
+License
+</p>
+<p>
+The Eclipse Foundation makes available all content in this plug-in ("Content"). Unless otherwise indicated below, the Content is provided to you under the terms and conditions of the Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is available at http://www.eclipse.org/legal/epl-v10.html. For purposes of the EPL, "Program" will mean the Content.
+</p>
+<p>
+If you did not receive this Content directly from the Eclipse Foundation, the Content is being redistributed by another party ("Redistributor") and different terms and conditions may apply to your use of any object code in the Content. Check the RedistributorÂ’s license that was provided with the Content. If no such license exists, contact the Redistributor. Unless otherwise indicated below, the terms and conditions of the EPL still apply to any source code in the Content and such source code may be obtained at http://www.eclipse.org.
+ <br>
+</BODY>
+</HTML>
\ No newline at end of file
diff --git a/praclib/temp/core.default.release_copyright.base/guidances/supportingmaterials/resources/cr_sym_obj.gif b/praclib/temp/core.default.release_copyright.base/guidances/supportingmaterials/resources/cr_sym_obj.gif
new file mode 100644
index 0000000..d1f6a31
--- /dev/null
+++ b/praclib/temp/core.default.release_copyright.base/guidances/supportingmaterials/resources/cr_sym_obj.gif
Binary files differ
diff --git a/praclib/temp/core.default.release_copyright.base/plugin.xmi b/praclib/temp/core.default.release_copyright.base/plugin.xmi
new file mode 100644
index 0000000..5423b3e
--- /dev/null
+++ b/praclib/temp/core.default.release_copyright.base/plugin.xmi
@@ -0,0 +1,73 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_qLz-kUNdEdy245g62lfWcA"
+ guid="_qLz-kUNdEdy245g62lfWcA">
+ <resourceDescriptors xmi:id="_lQP7EKzREduOqvpk_MDLfQ" id="-PZ0CqCcJHB-nbxs8fbP7bg"
+ uri="guidances/supportingmaterials/copyright.oup.xmi"/>
+ <resourceDescriptors xmi:id="_lZIzECcTEduSX6N2jUafGA" id="-RNyaB6jxqoopm9fJU8k9vg"
+ uri="guidances/supportingmaterials/openup_copyright.xmi"/>
+ <resourceDescriptors xmi:id="_vAKV4PsDEdmyhNQr5STrZQ" id="_u_Zg4PsDEdmyhNQr5STrZQ"
+ uri="guidances/supportingmaterials/copyright.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_iVydgENdEdy245g62lfWcA" name="core.default.release_copyright.base"
+ guid="_iVydgENdEdy245g62lfWcA" changeDate="2008-03-03T11:14:03.855-0500">
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iVydgUNdEdy245g62lfWcA"
+ name="Content" guid="_iVydgUNdEdy245g62lfWcA">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iVydgkNdEdy245g62lfWcA"
+ name="Categories" guid="_iVydgkNdEdy245g62lfWcA">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iVydg0NdEdy245g62lfWcA"
+ name="Domains" guid="_iVydg0NdEdy245g62lfWcA"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iVydhENdEdy245g62lfWcA"
+ name="Disciplines" guid="_iVydhENdEdy245g62lfWcA"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iVydhUNdEdy245g62lfWcA"
+ name="RoleSets" guid="_iVydhUNdEdy245g62lfWcA"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iVydhkNdEdy245g62lfWcA"
+ name="WP Types" guid="_iVydhkNdEdy245g62lfWcA"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iVydh0NdEdy245g62lfWcA"
+ name="Tools" guid="_iVydh0NdEdy245g62lfWcA"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iVydiENdEdy245g62lfWcA"
+ name="StandardCategories" guid="_iVydiENdEdy245g62lfWcA"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iVydiUNdEdy245g62lfWcA"
+ name="CustomCategories" guid="_iVydiUNdEdy245g62lfWcA">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iVydikNdEdy245g62lfWcA"
+ name="Hidden" guid="_iVydikNdEdy245g62lfWcA">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_iVydi0NdEdy245g62lfWcA"
+ name="Custom Categories" guid="_iVydi0NdEdy245g62lfWcA"/>
+ </childPackages>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iVydjENdEdy245g62lfWcA"
+ name="CoreContent" guid="_iVydjENdEdy245g62lfWcA">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_buz3kENfEdy245g62lfWcA"
+ name="Open Source Copyright" guid="_buz3kENfEdy245g62lfWcA">
+ <contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="_cTs20KzREduOqvpk_MDLfQ"
+ name="copyright.oup" guid="_cTs20KzREduOqvpk_MDLfQ" variabilityType="contributes"
+ variabilityBasedOnElement="_uuunoPsDEdmyhNQr5STrZQ" supportingMaterials="_UaGfECcTEduSX6N2jUafGA">
+ <presentation xmi:id="-PZ0CqCcJHB-nbxs8fbP7bg" href="uma://-PZ0CqCcJHB-nbxs8fbP7bg#-PZ0CqCcJHB-nbxs8fbP7bg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="_UaGfECcTEduSX6N2jUafGA"
+ name="openup_copyright" guid="_UaGfECcTEduSX6N2jUafGA" briefDescription="OpenUP Copyright Information"
+ presentationName="OpenUP Copyright" shapeicon="guidances/supportingmaterials/resources/cr_sym_obj.gif"
+ nodeicon="guidances/supportingmaterials/resources/cr_sym_obj.gif">
+ <presentation xmi:id="-RNyaB6jxqoopm9fJU8k9vg" href="uma://-RNyaB6jxqoopm9fJU8k9vg#-RNyaB6jxqoopm9fJU8k9vg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="_uuunoPsDEdmyhNQr5STrZQ"
+ name="copyright" guid="_uuunoPsDEdmyhNQr5STrZQ" presentationName="Copyright"
+ shapeicon="guidances/supportingmaterials/resources/cr_sym_obj.gif" nodeicon="guidances/supportingmaterials/resources/cr_sym_obj.gif">
+ <presentation xmi:id="_u_Zg4PsDEdmyhNQr5STrZQ" href="uma://_u_Zg4PsDEdmyhNQr5STrZQ#_u_Zg4PsDEdmyhNQr5STrZQ"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_iVydjUNdEdy245g62lfWcA"
+ name="CapabilityPatterns" guid="_iVydjUNdEdy245g62lfWcA"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_iVydjkNdEdy245g62lfWcA"
+ name="DeliveryProcesses" guid="_iVydjkNdEdy245g62lfWcA"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_iVydj0NdEdy245g62lfWcA"
+ name="ProcessContributions" guid="_iVydj0NdEdy245g62lfWcA"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/core.default.role_def.base/.project b/praclib/temp/core.default.role_def.base/.project
new file mode 100644
index 0000000..98804f8
--- /dev/null
+++ b/praclib/temp/core.default.role_def.base/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>core.default.role_def.base</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/core.default.role_def.base/plugin.xmi b/praclib/temp/core.default.role_def.base/plugin.xmi
new file mode 100644
index 0000000..9325516
--- /dev/null
+++ b/praclib/temp/core.default.role_def.base/plugin.xmi
@@ -0,0 +1,119 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_A1_toMYaEdyXeo04os5BOw"
+ guid="_A1_toMYaEdyXeo04os5BOw">
+ <resourceDescriptors xmi:id="_nDRE8_L5Edm6Nvont3uinw" id="_Fdq-8KX4EdmvhNXG0Oc2uA"
+ uri="roles/project_manager.xmi"/>
+ <resourceDescriptors xmi:id="_m_D6YvL5Edm6Nvont3uinw" id="_NqL7MqeqEdmKDbQuyzCoqQ"
+ uri="roles/developer.xmi"/>
+ <resourceDescriptors xmi:id="_m_KBBvL5Edm6Nvont3uinw" id="_NqYIcKeqEdmKDbQuyzCoqQ"
+ uri="roles/tester.xmi"/>
+ <resourceDescriptors xmi:id="_m-xmhPL5Edm6Nvont3uinw" id="_Nx8icKYdEdmvhNXG0Oc2uA"
+ uri="roles/analyst.xmi"/>
+ <resourceDescriptors xmi:id="_m_D6YfL5Edm6Nvont3uinw" id="_Y6tLEKbXEdm9d-ircVOUCA"
+ uri="roles/architect.xmi"/>
+ <resourceDescriptors xmi:id="_nD2Tw_L5Edm6Nvont3uinw" id="_NqqcUqeqEdmKDbQuyzCoqQ"
+ uri="roles/any_role.xmi"/>
+ <resourceDescriptors xmi:id="_SS_I8cYaEdyXeo04os5BOw" id="-xLl5B3qPPdk8LfLut7r8hQ"
+ uri="rolesets/basic_role_set.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_A118oMYaEdyXeo04os5BOw" name="core.default.role_def.base"
+ guid="_A118oMYaEdyXeo04os5BOw" changeDate="2008-01-18T18:12:05.218-0500">
+ <copyrightStatement href="uma://_iVydgENdEdy245g62lfWcA#_cTs20KzREduOqvpk_MDLfQ"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_A118ocYaEdyXeo04os5BOw"
+ name="Content" guid="_A118ocYaEdyXeo04os5BOw">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_A118osYaEdyXeo04os5BOw"
+ name="Categories" guid="_A118osYaEdyXeo04os5BOw">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_A118o8YaEdyXeo04os5BOw"
+ name="Domains" guid="_A118o8YaEdyXeo04os5BOw"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_A118pMYaEdyXeo04os5BOw"
+ name="Disciplines" guid="_A118pMYaEdyXeo04os5BOw"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_A118pcYaEdyXeo04os5BOw"
+ name="RoleSets" guid="_A118pcYaEdyXeo04os5BOw">
+ <contentElements xsi:type="org.eclipse.epf.uma:RoleSet" xmi:id="_SHN90MYaEdyXeo04os5BOw"
+ name="basic_role_set" guid="_SHN90MYaEdyXeo04os5BOw" briefDescription="This is the list of basic software development roles."
+ presentationName="Basic Roles" roles="_0VxJsMlgEdmt3adZL5Dmdw _0dsWoMlgEdmt3adZL5Dmdw _0X9iEMlgEdmt3adZL5Dmdw _0YDosMlgEdmt3adZL5Dmdw _0a0o0MlgEdmt3adZL5Dmdw _dTa6gMAYEdqX-s4mWhkyqQ _0ZM4MclgEdmt3adZL5Dmdw">
+ <presentation xmi:id="-xLl5B3qPPdk8LfLut7r8hQ" href="uma://-xLl5B3qPPdk8LfLut7r8hQ#-xLl5B3qPPdk8LfLut7r8hQ"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_A118psYaEdyXeo04os5BOw"
+ name="WP Types" guid="_A118psYaEdyXeo04os5BOw"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_A118p8YaEdyXeo04os5BOw"
+ name="Tools" guid="_A118p8YaEdyXeo04os5BOw"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_A118qMYaEdyXeo04os5BOw"
+ name="StandardCategories" guid="_A118qMYaEdyXeo04os5BOw"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_A118qcYaEdyXeo04os5BOw"
+ name="CustomCategories" guid="_A118qcYaEdyXeo04os5BOw">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_A118qsYaEdyXeo04os5BOw"
+ name="Hidden" guid="_A118qsYaEdyXeo04os5BOw">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_A118q8YaEdyXeo04os5BOw"
+ name="Custom Categories" guid="_A118q8YaEdyXeo04os5BOw" categorizedElements="_hcT4gMYaEdyXeo04os5BOw _LgPloMYhEdyXeo04os5BOw"/>
+ </childPackages>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_hcT4gMYaEdyXeo04os5BOw"
+ name="role_set_list.role_set" guid="_hcT4gMYaEdyXeo04os5BOw" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_Km2E8MRfEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_LgPloMYhEdyXeo04os5BOw"
+ name="role_list.roles" guid="_LgPloMYhEdyXeo04os5BOw" variabilityType="contributes"
+ categorizedElements="_0VxJsMlgEdmt3adZL5Dmdw _0dsWoMlgEdmt3adZL5Dmdw _0X9iEMlgEdmt3adZL5Dmdw _0YDosMlgEdmt3adZL5Dmdw _0a0o0MlgEdmt3adZL5Dmdw _dTa6gMAYEdqX-s4mWhkyqQ _0ZM4MclgEdmt3adZL5Dmdw">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCIHZMRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_A118rMYaEdyXeo04os5BOw"
+ name="CoreContent" guid="_A118rMYaEdyXeo04os5BOw">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="__0_tgBAYEdyqb5chWQXsPQ"
+ name="Basic Roles" guid="__0_tgBAYEdyqb5chWQXsPQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:Role" xmi:id="_0VxJsMlgEdmt3adZL5Dmdw"
+ name="analyst" guid="_0VxJsMlgEdmt3adZL5Dmdw" briefDescription="The person in this role represents customer and end-user concerns by gathering input from stakeholders to understand the problem to be solved and by capturing and setting priorities for requirements."
+ presentationName="Analyst">
+ <presentation xmi:id="_Nx8icKYdEdmvhNXG0Oc2uA" href="uma://_Nx8icKYdEdmvhNXG0Oc2uA#_Nx8icKYdEdmvhNXG0Oc2uA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Role" xmi:id="_0dsWoMlgEdmt3adZL5Dmdw"
+ name="any_role" guid="_0dsWoMlgEdmt3adZL5Dmdw" briefDescription="Anyone on a team can fill this role of performing general tasks."
+ presentationName="Any Role">
+ <presentation xmi:id="_NqqcUqeqEdmKDbQuyzCoqQ" href="uma://_NqqcUqeqEdmKDbQuyzCoqQ#_NqqcUqeqEdmKDbQuyzCoqQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Role" xmi:id="_0X9iEMlgEdmt3adZL5Dmdw"
+ name="architect" guid="_0X9iEMlgEdmt3adZL5Dmdw" briefDescription="This role is responsible for defining the software architecture, which includes making the key technical decisions that constrain the overall design and implementation of the system."
+ presentationName="Architect">
+ <presentation xmi:id="_Y6tLEKbXEdm9d-ircVOUCA" href="uma://_Y6tLEKbXEdm9d-ircVOUCA#_Y6tLEKbXEdm9d-ircVOUCA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Role" xmi:id="_0YDosMlgEdmt3adZL5Dmdw"
+ name="developer" guid="_0YDosMlgEdmt3adZL5Dmdw" briefDescription="This role is responsible for developing a part of the system, including designing it to fit into the architecture, possibly prototyping the user-interface, and then implementing, unit-testing, and integrating the components that are part of the solution."
+ presentationName="Developer">
+ <presentation xmi:id="_NqL7MqeqEdmKDbQuyzCoqQ" href="uma://_NqL7MqeqEdmKDbQuyzCoqQ#_NqL7MqeqEdmKDbQuyzCoqQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Role" xmi:id="_0a0o0MlgEdmt3adZL5Dmdw"
+ name="project_manager" guid="_0a0o0MlgEdmt3adZL5Dmdw" briefDescription="Leads the planning of the project, coordinates interactions with the stakeholders, and keeps the project team focused on meeting the project objectives."
+ presentationName="Project Manager">
+ <presentation xmi:id="_Fdq-8KX4EdmvhNXG0Oc2uA" href="uma://_Fdq-8KX4EdmvhNXG0Oc2uA#_Fdq-8KX4EdmvhNXG0Oc2uA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Role" xmi:id="_dTa6gMAYEdqX-s4mWhkyqQ"
+ name="stakeholder" guid="_dTa6gMAYEdqX-s4mWhkyqQ" briefDescription="This role represents interest groups whose needs must be satisfied by the project. It is a role that may be played by anyone who is (or potentially will be) materially affected by the outcome of the project."
+ presentationName="Stakeholder"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:Role" xmi:id="_0ZM4MclgEdmt3adZL5Dmdw"
+ name="tester" guid="_0ZM4MclgEdmt3adZL5Dmdw" briefDescription="This role is responsible for the core activities of the test effort. Those activities include identifying, defining, implementing, and conducting the necessary tests, as well as logging the outcomes of the testing and analyzing the results."
+ presentationName="Tester">
+ <presentation xmi:id="_NqYIcKeqEdmKDbQuyzCoqQ" href="uma://_NqYIcKeqEdmKDbQuyzCoqQ#_NqYIcKeqEdmKDbQuyzCoqQ"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_A118rcYaEdyXeo04os5BOw"
+ name="CapabilityPatterns" guid="_A118rcYaEdyXeo04os5BOw"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_A118rsYaEdyXeo04os5BOw"
+ name="DeliveryProcesses" guid="_A118rsYaEdyXeo04os5BOw"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_A118r8YaEdyXeo04os5BOw"
+ name="ProcessContributions" guid="_A118r8YaEdyXeo04os5BOw"/>
+ <bases href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPloEFXEdy9ENCpSugIjA"/>
+ <bases href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno4EKmEdyrauqpmnA8jQ"/>
+ <bases href="uma://_iVydgENdEdy245g62lfWcA#_iVydgENdEdy245g62lfWcA"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/core.default.role_def.base/roles/analyst.xmi b/praclib/temp/core.default.role_def.base/roles/analyst.xmi
new file mode 100644
index 0000000..36c1f74
--- /dev/null
+++ b/praclib/temp/core.default.role_def.base/roles/analyst.xmi
@@ -0,0 +1,53 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:RoleDescription 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="_Nx8icKYdEdmvhNXG0Oc2uA"
+ name="analyst,_0VxJsMlgEdmt3adZL5Dmdw" guid="_Nx8icKYdEdmvhNXG0Oc2uA" changeDate="2007-01-05T06:44:25.904-0800"
+ version="1.0.0">
+ <skills><p>
+ An analyst needs the following knowledge, skills, and abilities:
+</p>
+<ul>
+ <li>
+ Expertise in identifying and understanding problems and opportunities
+ </li>
+ <li>
+ Ability&nbsp;to articulate the needs that are associated with the key problem to be solved or opportunity to be
+ realized
+ </li>
+ <li>
+ Ability to collaborate effectively with the extended team through collaborative working sessions, workshops, JAD
+ sessions and other techniques.
+ </li>
+ <li>
+ Good communication skills, verbally and in writing
+ </li>
+ <li>
+ Knowledge of the business and technology domains or the ability to quickly absorb and understand such information
+ </li>
+</ul><br /></skills>
+ <assignmentApproaches><p>
+ This role can be assigned in the following ways:
+</p>
+<ul>
+ <li>
+ On small, agile teams this role is often shared among several team members that also perform other roles.&nbsp; See
+ <a class="elementLinkWithType"
+ href="./../../opn.swd.prac.legacy_pm/guidances/guidelines/self_organize_work_assignments_F47FC314.html"
+ guid="_rmBEkJjsEduad8I_c-ogIA">Guideline: Self Organize Work Assignments</a>&nbsp;and <a
+ class="elementLinkWithType"
+ href="./../../opn.swd.prac.legacy_pm/guidances/guidelines/staffing_project_70705561.html"
+ guid="_Jq64EJjsEduad8I_c-ogIA">Guideline: Staffing a Project</a>&nbsp;for more information on this approach.
+ </li>
+ <li>
+ One (or more)&nbsp;team member(s) performs this role exclusively. This commonly adopted approach is suitable for
+ complex requirements that are difficult to gather.
+ </li>
+ <li>
+ One staff (or more) team member(s) performs both this role and the <a class="elementLink"
+ href="./../../opn.tech.roles.openup_role_defs/roles/tester_9859B590.html" guid="_0ZM4MclgEdmt3adZL5Dmdw">Tester</a>
+ role. This is a good option for smaller or resource<font color="#ff0000">-</font>constrained test teams.
+ </li>
+</ul></assignmentApproaches>
+</org.eclipse.epf.uma:RoleDescription>
diff --git a/praclib/temp/core.default.role_def.base/roles/any_role.xmi b/praclib/temp/core.default.role_def.base/roles/any_role.xmi
new file mode 100644
index 0000000..9534703
--- /dev/null
+++ b/praclib/temp/core.default.role_def.base/roles/any_role.xmi
@@ -0,0 +1,24 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:RoleDescription 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="_NqqcUqeqEdmKDbQuyzCoqQ"
+ name="any_role,_0dsWoMlgEdmt3adZL5Dmdw" guid="_NqqcUqeqEdmKDbQuyzCoqQ" changeDate="2006-09-11T11:34:17.153-0700">
+ <mainDescription><p>
+ This role allows anyone on a team to perform general tasks:
+</p>
+<ul>
+ <li>
+ Access artifacts in the configuration control system for development and maintenance
+ </li>
+ <li>
+ Submit change requests for the project
+ </li>
+ <li>
+ Participate in assessments and reviews
+ </li>
+ <li>
+ Volunteer to work on a particular iteration
+ </li>
+</ul></mainDescription>
+</org.eclipse.epf.uma:RoleDescription>
diff --git a/praclib/temp/core.default.role_def.base/roles/architect.xmi b/praclib/temp/core.default.role_def.base/roles/architect.xmi
new file mode 100644
index 0000000..dbf1fa7
--- /dev/null
+++ b/praclib/temp/core.default.role_def.base/roles/architect.xmi
@@ -0,0 +1,103 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:RoleDescription 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="_Y6tLEKbXEdm9d-ircVOUCA"
+ name="architect,_0X9iEMlgEdmt3adZL5Dmdw" guid="_Y6tLEKbXEdm9d-ircVOUCA" changeDate="2008-02-14T11:45:34.468-0500"
+ version="1.0.0">
+ <mainDescription><p>
+ This role leads or coordinates the technical design of the system and has overall responsibility for facilitating the
+ major technical decisions expressed as software architecture. This typically includes identifying and documenting the
+ architecturally significant aspects of the system as views that describe requirements, design, implementation, and
+ deployment.
+</p>
+<p>
+ This role is also responsible for providing the rationale for these decisions, balancing the concerns of the various
+ stakeholders, reducing technical risks, and ensuring that decisions are effectively communicated, validated, and
+ followed.
+</p>
+<p>
+ This role works closely with the&nbsp;<a class="elementLink"
+ href="./../../core.default.role_def.base/roles/project_manager_E657F936.html" guid="_0a0o0MlgEdmt3adZL5Dmdw">Project
+ Manager</a>&nbsp;in staffing and planning the project since it is recommended that the team be organized around the
+ architecture.
+</p>
+<p>
+ This role also works closely with the <a class="elementLink"
+ href="./../../core.default.role_def.base/roles/analyst_39D7C49B.html"
+ guid="_0VxJsMlgEdmt3adZL5Dmdw">Analyst</a>&nbsp;and <a class="elementLink"
+ href="./../../core.default.role_def.base/roles/developer_C633AB7.html"
+ guid="_0YDosMlgEdmt3adZL5Dmdw">Developer</a>&nbsp;to make sure that the architecturally significant <a id="Comment19_"
+ name="Comment19_">requirements are assigned to the proper components of the system.&nbsp;</a>
+</p>
+<p>
+ In addition to the above-listed technical responsibilities, there are a number of non-technical activities that this
+ role is responsible for.&nbsp; For example, acting as a champion for the decisions made, engaging with other
+ stakeholders (notably patrons and customers and project managers) to articulate those decisions and negotiate change.
+</p></mainDescription>
+ <skills><p>
+ Architects must be well-rounded people with maturity, vision, and a depth of experience that allows for grasping issues
+ quickly and making educated, critical judgments in the absence of complete information. Specifically, the person must
+ possess this combination of qualifications:
+</p>
+<ul>
+ <li>
+ <b>Experience</b> <strong>in both problem and software engineering domains</strong>, with evidence of a thorough
+ understanding of the requirements to solve the problem and active participation in software development. If there
+ is a team, this experience can be represented by different team members, but at least one person must be able to
+ describethe overall vision for the project.
+ </li>
+ <li>
+ <b>Leadership ability</b> to motivate and maintain momentum for the technical effort across the various teams and
+ to make critical decisions under pressure, plus make those decisions stick. To be effective, this role must have
+ the authority to make technical decisions. This role cannot lead by decree, but only by the consent of the rest of
+ the project team. To be effective, this&nbsp;person must earn the respect of the team members, the <a
+ class="elementLink" href="./../../core.default.role_def.base/roles/project_manager_E657F936.html"
+ guid="_0a0o0MlgEdmt3adZL5Dmdw">Project Manager</a>, the customer, and the user community, as well as the management
+ team.
+ </li>
+ <li>
+ <b>Excellent communication</b> <strong>skills</strong> to earn trust, persuade, motivate, and mentor.&nbsp; This
+ role must have good communication skills, both verbally and in writing.
+ </li>
+ <li>
+ Critical review skills to make sure that the requirements to be built are clear and consistent, and to make sure
+ that the developed system adheres to the architecture.&nbsp;
+ </li>
+ <li>
+ <b>Goal-oriented and proactive</b> <strong>orientation</strong> with a relentless focus on results.&nbsp;This
+ person is the technical driving force behind the project, not a visionary or dreamer. The career of a successful
+ architect is a long series of sub-optimal decisions made in uncertainty and under pressure. Only those who can
+ focus on doing what needs to be done will be successful.
+ </li>
+</ul>
+<p>
+ From an expertise standpoint, this role also needs to show both design and implementation abilities. However, from the
+ design perspective, the effective architect typically exhibits these traits:
+</p>
+<ul>
+ <li>
+ Tends to be a generalist, rather than a specialist, who knows many technologies at a high level rather than a few
+ technologies at the detail level
+ </li>
+ <li>
+ Makes the broader technical decisions, thereby demonstrating broad knowledge and experience, as well as
+ communication and leadership skills
+ </li>
+</ul></skills>
+ <assignmentApproaches><p>
+ The person in this role should be engaged in the project from start to finish.
+</p>
+<p>
+ For smaller projects, a single person may act as both Architect and <a class="elementLink"
+ href="./../../core.default.role_def.base/roles/project_manager_E657F936.html" guid="_0a0o0MlgEdmt3adZL5Dmdw">Project
+ Manager</a>. However, it is better to have these roles performed by different people to ensure that the pressures of
+ one role does not cause neglect of the other role.&nbsp;The Architect and Project Manager&nbsp;must work together
+ closely.
+</p>
+<p>
+ For systems of scale, it is a common best practice to have an architecture board that is populated by the architects of
+ each system plus one or two chief architects.&nbsp; In such cases, the members of the architecture board collectively
+ play the role of the Architect.
+</p></assignmentApproaches>
+</org.eclipse.epf.uma:RoleDescription>
diff --git a/praclib/temp/core.default.role_def.base/roles/developer.xmi b/praclib/temp/core.default.role_def.base/roles/developer.xmi
new file mode 100644
index 0000000..34159c9
--- /dev/null
+++ b/praclib/temp/core.default.role_def.base/roles/developer.xmi
@@ -0,0 +1,40 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:RoleDescription 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="_NqL7MqeqEdmKDbQuyzCoqQ"
+ name="developer,_0YDosMlgEdmt3adZL5Dmdw" guid="_NqL7MqeqEdmKDbQuyzCoqQ" changeDate="2007-01-14T14:32:58.561-0800"
+ version="1.0.0">
+ <skills><p>
+ This role needs the following knowledge, skills, and abilities:
+</p>
+<ul>
+ <li>
+ Define and create technical solutions in the project's technology
+ </li>
+ <li>
+ Understand and&nbsp;conform to the&nbsp;architecture
+ </li>
+ <li>
+ Identify and build developer tests that cover required behavior of the technical components
+ </li>
+ <li>
+ Communicate the design in a way that other team members understand
+ </li>
+</ul></skills>
+ <assignmentApproaches><p>
+ On small, agile teams this role is often shared among several team members that also perform other roles.&nbsp; See <a
+ class="elementLinkWithType"
+ href="./../../opn.swd.prac.legacy_pm/guidances/guidelines/self_organize_work_assignments_F47FC314.html"
+ guid="_rmBEkJjsEduad8I_c-ogIA">Guideline: Self Organize Work Assignments</a>&nbsp;and <a class="elementLinkWithType"
+ href="./../../opn.swd.prac.legacy_pm/guidances/guidelines/staffing_project_70705561.html"
+ guid="_Jq64EJjsEduad8I_c-ogIA">Guideline: Staffing a Project</a>&nbsp;for more information on this approach.
+</p>
+<p>
+ Even in the smallest team, multiple individuals should be working together to create the technical solution.
+</p>
+<p>
+ A person performing this role can have specialized skills in a particular technical area, but should also have a broad
+ understanding of all the technologies involved to be able to work with other technical team members.
+</p></assignmentApproaches>
+</org.eclipse.epf.uma:RoleDescription>
diff --git a/praclib/temp/core.default.role_def.base/roles/project_manager.xmi b/praclib/temp/core.default.role_def.base/roles/project_manager.xmi
new file mode 100644
index 0000000..5973dfe
--- /dev/null
+++ b/praclib/temp/core.default.role_def.base/roles/project_manager.xmi
@@ -0,0 +1,55 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:RoleDescription 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="_Fdq-8KX4EdmvhNXG0Oc2uA"
+ name="project_manager,_0a0o0MlgEdmt3adZL5Dmdw" guid="_Fdq-8KX4EdmvhNXG0Oc2uA"
+ changeDate="2006-11-01T20:03:02.026-0500" version="1.0.0">
+ <mainDescription><p>
+ This role:
+</p>
+<ul>
+ <li>
+ Coaches the team to drive a succesful outcome of the project and the acceptance of the product by the customer.
+ </li>
+ <li>
+ Is accountable for the outcome of the project and the acceptance of the product by the customer.
+ </li>
+ <li>
+ Is responsible for the evaluation of project's risks, and controling these risks through mitigation
+ strategies.&nbsp;
+ </li>
+ <li>
+ Applies management knowledge, skills, tools and techniques to a broad range of tasks in order to deliver&nbsp;the
+ desired&nbsp;result for a particular project in a timely fashion.
+ </li>
+</ul></mainDescription>
+ <skills><p>
+ A person performing this role needs the following skills:
+</p>
+<ul>
+ <li>
+ Leadership and team building capabilities.
+ </li>
+ <li>
+ Thorough experience in the software development lifecycle to coach, guide and support other team members.
+ </li>
+ <li>
+ Proficient in conflict resolution and problem solving techniques.
+ </li>
+ <li>
+ Good in presentation, facilitation, communication, and negotiation.
+ </li>
+</ul></skills>
+ <assignmentApproaches><p>
+
+ This role is often played by a single person. This role is difficult to share with others, but might not consume all of
+
+ a person’s availability.
+
+</p>
+
+<br />
+
+<br /></assignmentApproaches>
+</org.eclipse.epf.uma:RoleDescription>
diff --git a/praclib/temp/core.default.role_def.base/roles/tester.xmi b/praclib/temp/core.default.role_def.base/roles/tester.xmi
new file mode 100644
index 0000000..14c3dcb
--- /dev/null
+++ b/praclib/temp/core.default.role_def.base/roles/tester.xmi
@@ -0,0 +1,93 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:RoleDescription 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="_NqYIcKeqEdmKDbQuyzCoqQ"
+ name="tester,_0ZM4MclgEdmt3adZL5Dmdw" guid="_NqYIcKeqEdmKDbQuyzCoqQ" changeDate="2006-09-26T13:51:28.608-0700"
+ version="1.0.0">
+ <mainDescription><p>
+ This role is primarily responsible for the following&nbsp;tasks:
+</p>
+<ul>
+ <li>
+ Identify the tests&nbsp;that need to&nbsp;be performed
+ </li>
+ <li>
+ Identify the most appropriate implementation approach for a given test
+ </li>
+ <li>
+ Implement individual tests
+ </li>
+ <li>
+ Set up and execute the tests
+ </li>
+ <li>
+ Log outcomes and verify that the tests have been run
+ </li>
+ <li>
+ Analyze and recover from execution errors
+ </li>
+ <li>
+ Communicate test results to the team
+ </li>
+</ul></mainDescription>
+ <skills><p>
+ A person&nbsp;filling the&nbsp;this role should have the following skills:
+</p>
+<ul>
+ <li>
+ Knowledge of testing approaches and techniques
+ </li>
+ <li>
+ Diagnostic and problem-solving skills
+ </li>
+ <li>
+ Knowledge of the system or application being tested (desirable)
+ </li>
+ <li>
+ Knowledge of networking and system architecture (desirable)
+ </li>
+</ul>
+<p>
+ Where automated testing is required, consider requiring these additional qualifications:
+</p>
+<ul>
+ <li>
+ Training in the appropriate use of test automation tools
+ </li>
+ <li>
+ Experience using test automation tools
+ </li>
+ <li>
+ Programming skills
+ </li>
+ <li>
+ Debugging and diagnostic skills
+ </li>
+</ul>
+<p>
+ <strong>Note:</strong> Specific skill requirements vary depending on the type of testing that you are conducting. For
+ example, the skills needed to successfully use system load testing automation tools are different from those needed for
+ the automation of system functional testing.
+</p></skills>
+ <assignmentApproaches><p>
+ This role can be assigned in the following ways:
+</p>
+<ul>
+ <li>
+ Assign one or more testing staff members to perform this role. This is a fairly standard approach and is
+ particularly suitable for small teams, as well as for teams of any size where the team is made up of an experienced
+ group of testers of relatively equal skill levels.
+ </li>
+ <li>
+ Assign one or more testing staff members to perform only this role.&nbsp;This works well in large teams. It is also
+ useful to separate responsibilities when some of the testing staff has more test automation experience than other
+ team members.
+ </li>
+ <li>
+ Assign one or more team members that is already playing another role in the project to be responsible for the
+ testing of some part of the system’s capabilities.&nbsp;The team member will have to have the appropriate test
+ skills
+ </li>
+</ul></assignmentApproaches>
+</org.eclipse.epf.uma:RoleDescription>
diff --git a/praclib/temp/core.default.role_def.base/rolesets/basic_role_set.xmi b/praclib/temp/core.default.role_def.base/rolesets/basic_role_set.xmi
new file mode 100644
index 0000000..aaafa83
--- /dev/null
+++ b/praclib/temp/core.default.role_def.base/rolesets/basic_role_set.xmi
@@ -0,0 +1,14 @@
+<?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="-xLl5B3qPPdk8LfLut7r8hQ"
+ name="new_role_set,_FBekABAaEdyqb5chWQXsPQ" guid="-xLl5B3qPPdk8LfLut7r8hQ" changeDate="2007-06-01T04:28:48.562-0400"
+ version="7.1.0">
+ <mainDescription><p>
+ This page allows you to navigate the published configuration from the perspective of <a class="elementLinkWithUserText"
+ href="./../../core.default.uma_concepts/guidances/termdefinitions/role_37A0C602.html"
+ guid="_yUefQNnmEdmO6L4XMImrsA">roles</a>. You can see the roles that have been included, and visit each role page to
+ see its definition and relationships to other elements.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.tool_def.base/.project b/praclib/temp/core.default.tool_def.base/.project
new file mode 100644
index 0000000..bbcf85d
--- /dev/null
+++ b/praclib/temp/core.default.tool_def.base/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>core.default.tool_def.base</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/core.default.tool_def.base/guidances/supportingmaterials/resources_for_modifying_methods.xmi b/praclib/temp/core.default.tool_def.base/guidances/supportingmaterials/resources_for_modifying_methods.xmi
new file mode 100644
index 0000000..7088cf1
--- /dev/null
+++ b/praclib/temp/core.default.tool_def.base/guidances/supportingmaterials/resources_for_modifying_methods.xmi
@@ -0,0 +1,177 @@
+<?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: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="-SqArASoV4hTpxAprrWhS1g"
+ name="resources_for_modifying_methods,_omneEMX4EduywMSzPTUUwA" guid="-SqArASoV4hTpxAprrWhS1g"
+ changeDate="2008-02-22T10:00:06.359-0500" version="7.2.0">
+ <mainDescription><p>
+ <strong>[*** This guidline needs refactoring to remove the OpenUP restriction (this should be useful for any open
+ source process content) and to change the terminology used from EPF Composer to just Method Composer.&nbsp;&nbsp;
+ (OpenUP-specific content can be factored out and contributed from process.openup) ***]</strong>
+</p>
+<h3>
+ Customization resources
+</h3>
+<p>
+ There are a number of use scenarios for OpenUP. The simplest&nbsp;is to use the&nbsp;content available from the EPF
+ project (either the available published Web site or the one that you publish from the available library). You can find
+ those resources at&nbsp;<a href="http://www.eclipse.org/epf">www.eclipse.org/epf</a>.
+</p>
+<p>
+ However, you may be&nbsp;looking for&nbsp;adding, removing, suppressing, or modifying method and process elements to
+ make OpenUP&nbsp;more&nbsp;suitable&nbsp;to your teams' needs, while keeping it consistent and understandable.
+</p>
+<p>
+ The following sections introduce a few fundamental concepts about&nbsp;method content and process, as well
+ as&nbsp;descriptions of typical customization scenarios and&nbsp;links to additional information on how to customize
+ methods.
+</p>
+<h4>
+ Method organization
+</h4>
+<p>
+ You can use EPF Composer to write, configure, and publish method and process content. EPF Composer organizes the
+ content in a <a class="elementLinkWithUserText"
+ href="./../../../core.default.uma_concept.base/guidances/termdefinitions/method_library_6E08F9E5.html"
+ guid="_1xELEMaFEduMlb2cQZNTYw">method library</a>. Each method library contains one or more <a
+ class="elementLinkWithUserText"
+ href="./../../../core.default.uma_concept.base/guidances/termdefinitions/method_plugin_190B9F5E.html"
+ guid="_D4TLgMaGEduMlb2cQZNTYw">method plug-ins</a>. Every plug-in consists of two major packages:&nbsp;<a
+ class="elementLinkWithUserText"
+ href="./../../../obsoleted_from_openup/guidances/termdefinitions/content_package_F5C69063.html"
+ guid="_SAWgwMaFEduMlb2cQZNTYw">content packages</a> and <a class="elementLinkWithUserText"
+ href="./../../../obsoleted_from_openup/guidances/termdefinitions/process_package_368B7463.html"
+ guid="_MN1doMaHEduMlb2cQZNTYw">process packages</a>. Content packages contain <a class="elementLinkWithUserText"
+ href="./../../../obsoleted_from_openup/guidances/termdefinitions/content_element_DA3AD029.html"
+ guid="_N8x34B_LEdq6CKKKq4D7YA">content elements</a>, such as <a class="elementLinkWithUserText"
+ href="./../../../core.default.uma_concept.base/guidances/termdefinitions/role_37A0C602.html"
+ guid="_yUefQNnmEdmO6L4XMImrsA">roles</a>, <a class="elementLinkWithUserText"
+ href="./../../../core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html"
+ guid="_x459ktnmEdmO6L4XMImrsA">tasks</a>, <a class="elementLinkWithUserText"
+ href="./../../../core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html"
+ guid="_H4JXwB_SEdq6CKKKq4D7YA">work products</a>, and <a class="elementLinkWithUserText"
+ href="./../../../core.default.uma_concept.base/guidances/termdefinitions/guidance_549AC394.html"
+ guid="_83ttAB_NEdq6CKKKq4D7YA">guidance</a>. Process packages contain <a class="elementLinkWithUserText"
+ href="./../../../core.default.uma_concept.base/guidances/termdefinitions/capability_pattern_F5DDC5F.html"
+ guid="_2RUJACO4EdqaNq6Ptg8uyA">capability patterns</a> and <a class="elementLinkWithUserText"
+ href="./../../../core.default.uma_concept.base/guidances/termdefinitions/delivery_process_BCDF50B7.html"
+ guid="_ZufeMCO3EdqaNq6Ptg8uyA">delivery processes</a>.
+</p>
+<p>
+ Method content and processes are organized in the EPF method library according to how they build logical units for
+ useful <a class="elementLinkWithUserText"
+ href="./../../../core.default.uma_concept.base/guidances/termdefinitions/method_configuration_C2B8FA8A.html"
+ guid="__V7pAMaEEduMlb2cQZNTYw">method configurations</a>. For example, all content belonging to one specific
+ discipline, such as requirements or development, can be found in one content package. Each of these packages might be
+ further divided into sub-packages for specific practices in these disciplines. For example,&nbsp;under
+ Development,&nbsp;you may want to&nbsp;have a package that&nbsp;factors all of the specific information about visual
+ modeling. Thus, you can add or remove&nbsp;visual modeling&nbsp;specifics from&nbsp;Development with just one simple
+ mouse-click by selecting or deselecting the right package.
+</p>
+<p>
+ For more information on method organization, see <b>EPF Composer Overview</b>, <a
+ href="http://www.eclipse.org/epf/general/EPFComposerOverviewPart1.pdf" target="_blank">Part 1</a> and <a
+ href="http://www.eclipse.org/epf/general/EPFComposerOverviewPart2.pdf" target="_blank">Part 2</a>.
+</p>
+<h4>
+ Customization scenarios
+</h4>
+<p>
+ The following sections describe&nbsp;several possible customization scenarios. For step-by-step instructions, see the
+ <a href="http://www.eclipse.org/epf/general/EPFComposer_OpenUP.zip" target="_blank">Customization Scenarios</a>
+ tutorial.
+</p>
+<h5>
+ Use existing plug-ins and packages to build your own process
+</h5>
+<p>
+ This is the most straight-forward customization scenario. Based on the content provided by OpenUP, you can use EPF
+ Composer to pick and choose the packages with the content that you want to have published and made available to your
+ team. Removing a method package removes all references to the content of that package from the published process. For
+ example, you can simplify a process to have it contain a minimal subset of its content by removing packages that
+ contain elements of work that you do not want to perform. You do this by creating a new method configuration (or
+ copying an existing one) into your method library. You can select packages as appropriate without affecting the
+ configuration provided.
+</p>
+<h5>
+ Add&nbsp;method content&nbsp;that your team needs
+</h5>
+<p>
+ Some teams may need to perform a different task that is not contemplated by the out-of-the-box content. Maybe they need
+ to perform an extra step in an existing task, or they may need to add a new guideline for a given technique that they
+ are following. Eventually, they need a new template for a document (or may need to add or remove sections in an
+ existing template).
+</p>
+<p>
+ In such situations, the recommended approach is to create a separate plug-in in your library.&nbsp;It is not a good
+ practice&nbsp;to make changes in the provided OpenUP plug-in (or any plug-in for which you do not have control),
+ because new versions of these plug-ins, when deployed, can override the changes that you have made.
+</p>
+<p>
+ EPF Composer provides a series of mechanisms that allow you to indirectly modify the content in an existing plug-in by
+ using content variability. In your plug-in, you can define an element that contributes, extends, or replaces an element
+ in the existing plug-in. For example, in your plug-in, you can define a task that contributes a new step to an existing
+ task in OpenUP. You can also define a new artifact that replaces one in OpenUP, and this new artifact can have a
+ different name, structure, and associated template, for example.
+</p>
+<p>
+ When you create a new plug-in, it should depend on existing plug-ins to where content will be contributed, extended or
+ replaced. After you have created your plug-in, you add&nbsp;it to a new configuration from which you can finally select
+ the packages with content that you want published. During publication, EPF Composer will resolve the content
+ variability that you defined by adding the new content into the existing content where appropriate, replacing existing
+ content with the content you defined, and so on.
+</p>
+<h5>
+ Define a different development lifecycle
+</h5>
+<p>
+ Both method content and process are created independently from&nbsp;each other. For example, you create tasks in the
+ method content (and define their&nbsp;inputs, outputs, and responsible roles), but you do not necessarily define the
+ lifecycle of your process, meaning the sequence in which the various tasks will be performed. On the process side, you
+ then define the lifecycle (such as phases, iterations, activities, and tasks), as well as the precedence among these
+ elements.
+</p>
+<p>
+ Some teams may find the method content appropriate without any further customization, but they may want to work by
+ following a different software development lifecycle. Some teams may like the four development phases and iterations
+ from OpenUP, but some may want to develop iteratively, without being tied to the phase structure.
+</p>
+<p>
+ You can add, remove and replace elements in the work breakdown structure of an existing process by applying
+ variability. This is called <b>process contribution</b>, which means that differential changes can be applied to an
+ existing process.
+</p>
+<p>
+ As an alternative to tailoring an existing process, you can write a completely new process that reuses activities from
+ one or more existing processes. In cases where you cannot find any reusable material at all, you can also create a
+ completely new process from scratch. In most cases, however, you will start developing your own process by assembling
+ reusable building blocks from method content, as well as predefined process patterns&nbsp;called <a
+ class="elementLinkWithUserText"
+ href="./../../../core.default.uma_concept.base/guidances/termdefinitions/capability_pattern_F5DDC5F.html"
+ guid="_2RUJACO4EdqaNq6Ptg8uyA">capability patterns</a>. The resulting assembled process is called a&nbsp;<a
+ class="elementLinkWithUserText"
+ href="./../../../core.default.uma_concept.base/guidances/termdefinitions/delivery_process_BCDF50B7.html"
+ guid="_ZufeMCO3EdqaNq6Ptg8uyA">delivery process</a>.
+</p>
+<p>
+ This newly created delivery process&nbsp;is part of a configuration that you publish and make available to members of
+ your team.
+</p>
+<h5>
+ Publish the process Web site
+</h5>
+<p>
+ Every customization scenario is finalized by publishing content in a Web site format that can&nbsp;be accessed by
+ practitioners in the project. EPF Composer allows you to publish&nbsp;content based on a given configuration, which
+ will publish all of the content available from the&nbsp;method and process packages selected in that configuration.
+ Another option for publishing is to select only the capability patterns or delivery process of interest. This will make
+ available only the content related to the process packages that you select.
+</p>
+<p>
+ For the published Web site look and feel, you can customize the views and nodes in the directory (tree) browser by
+ defining <a class="elementLinkWithUserText"
+ href="./../../../core.default.uma_concept.base/guidances/termdefinitions/custom_category_554AC4D6.html"
+ guid="_eqw94MaFEduMlb2cQZNTYw">custom categories</a> that will be part of your configuration.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.tool_def.base/plugin.xmi b/praclib/temp/core.default.tool_def.base/plugin.xmi
new file mode 100644
index 0000000..e4c1484
--- /dev/null
+++ b/praclib/temp/core.default.tool_def.base/plugin.xmi
@@ -0,0 +1,74 @@
+<?xml version="1.0" encoding="UTF-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.4/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.2.0" xmlns:epf="http://www.eclipse.org/epf"
+ epf:version="1.2.0">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_fRdVIMYbEdyXeo04os5BOw"
+ guid="_fRdVIMYbEdyXeo04os5BOw">
+ <resourceDescriptors xmi:id="_8n8IwMn-EdyuBO4ZIzcyig" id="-SqArASoV4hTpxAprrWhS1g"
+ uri="guidances/supportingmaterials/resources_for_modifying_methods.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_fRdVEMYbEdyXeo04os5BOw" name="core.default.tool_def.base"
+ guid="_fRdVEMYbEdyXeo04os5BOw" changeDate="2008-02-22T10:01:26.562-0500">
+ <copyrightStatement href="uma://_iVydgENdEdy245g62lfWcA#_cTs20KzREduOqvpk_MDLfQ"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_fRdVEcYbEdyXeo04os5BOw"
+ name="Content" guid="_fRdVEcYbEdyXeo04os5BOw">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_fRdVEsYbEdyXeo04os5BOw"
+ name="Categories" guid="_fRdVEsYbEdyXeo04os5BOw">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_fRdVE8YbEdyXeo04os5BOw"
+ name="Domains" guid="_fRdVE8YbEdyXeo04os5BOw"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_fRdVFMYbEdyXeo04os5BOw"
+ name="Disciplines" guid="_fRdVFMYbEdyXeo04os5BOw"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_fRdVFcYbEdyXeo04os5BOw"
+ name="RoleSets" guid="_fRdVFcYbEdyXeo04os5BOw"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_fRdVFsYbEdyXeo04os5BOw"
+ name="WP Types" guid="_fRdVFsYbEdyXeo04os5BOw"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_fRdVF8YbEdyXeo04os5BOw"
+ name="Tools" guid="_fRdVF8YbEdyXeo04os5BOw">
+ <contentElements xsi:type="org.eclipse.epf.uma:Tool" xmi:id="_hFih0MYbEdyXeo04os5BOw"
+ name="cvs_tool" guid="_hFih0MYbEdyXeo04os5BOw" presentationName="CVS"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:Tool" xmi:id="_mHQIMMYbEdyXeo04os5BOw"
+ name="method_composer_tool" guid="_mHQIMMYbEdyXeo04os5BOw" presentationName="Method Composer"/>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_fRdVGMYbEdyXeo04os5BOw"
+ name="StandardCategories" guid="_fRdVGMYbEdyXeo04os5BOw"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_fRdVGcYbEdyXeo04os5BOw"
+ name="CustomCategories" guid="_fRdVGcYbEdyXeo04os5BOw">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_fRdVGsYbEdyXeo04os5BOw"
+ name="Hidden" guid="_fRdVGsYbEdyXeo04os5BOw">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_fRdVG8YbEdyXeo04os5BOw"
+ name="Custom Categories" guid="_fRdVG8YbEdyXeo04os5BOw" categorizedElements="_qGqkEMYbEdyXeo04os5BOw"/>
+ </childPackages>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_qGqkEMYbEdyXeo04os5BOw"
+ name="tool_list.tools" guid="_qGqkEMYbEdyXeo04os5BOw" variabilityType="contributes"
+ categorizedElements="_hFih0MYbEdyXeo04os5BOw _mHQIMMYbEdyXeo04os5BOw">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_VTspMMRfEdyD76CYS6Ta7A"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_fRdVHMYbEdyXeo04os5BOw"
+ name="CoreContent" guid="_fRdVHMYbEdyXeo04os5BOw">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_w_1EkOFUEdyhmsbt0Xyl8A"
+ name="Method Composer Tool Mentors" guid="_w_1EkOFUEdyhmsbt0Xyl8A">
+ <contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="_omneEMX4EduywMSzPTUUwA"
+ name="resources_for_modifying_methods" guid="_omneEMX4EduywMSzPTUUwA"
+ briefDescription="This supporting material provides guidance on how to customize OpenUP using the Eclipse Process Framework (EPF) composer tool. It introduces some basic customization scenarios and links to additional information on methods customization."
+ presentationName="Resources for Modifying Methods">
+ <presentation xmi:id="-SqArASoV4hTpxAprrWhS1g" href="uma://-SqArASoV4hTpxAprrWhS1g#-SqArASoV4hTpxAprrWhS1g"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_fRdVHcYbEdyXeo04os5BOw"
+ name="CapabilityPatterns" guid="_fRdVHcYbEdyXeo04os5BOw"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_fRdVHsYbEdyXeo04os5BOw"
+ name="DeliveryProcesses" guid="_fRdVHsYbEdyXeo04os5BOw"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_fRdVH8YbEdyXeo04os5BOw"
+ name="ProcessContributions" guid="_fRdVH8YbEdyXeo04os5BOw"/>
+ <bases href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno4EKmEdyrauqpmnA8jQ"/>
+ <bases href="uma://_iVydgENdEdy245g62lfWcA#_iVydgENdEdy245g62lfWcA"/>
+ <bases href="uma://_WCUhAO8KEdmKSqa_gSYthg#_WCUhAO8KEdmKSqa_gSYthg"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/core.default.uma_concept.base/.project b/praclib/temp/core.default.uma_concept.base/.project
new file mode 100644
index 0000000..4de4418
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>core.default.uma_concept.base</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/supportingmaterials/about_base_concepts.xmi b/praclib/temp/core.default.uma_concept.base/guidances/supportingmaterials/about_base_concepts.xmi
new file mode 100644
index 0000000..6e2b113
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/supportingmaterials/about_base_concepts.xmi
@@ -0,0 +1,29 @@
+<?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="-V2B7_NtU_O7-45ldkX0Rrw"
+ name="new_supporting_material,_uvje4D_fEdqDFvujd6NHiA" guid="-V2B7_NtU_O7-45ldkX0Rrw"
+ changeDate="2006-09-27T19:24:54.186-0400" version="1.0.0">
+ <mainDescription><h3>
+ <a id="version" name="version">Version Information</a>
+</h3>
+<p>
+ Version&nbsp;1.0.&nbsp;
+</p>
+<h3>
+ Content
+</h3>
+<p>
+ This plug-in defines the terms&nbsp;from the Unified Method Architecture (UMA).
+</p>
+<p>
+ It is not dependent upon any other plug-ins.
+</p>
+<h3>
+ Legal Statement
+</h3>
+<p class="node">
+ See <a href="./resources/copyrite.htm"><u><font color="#0000ff">Intellectual Property Notices</font></u></a>.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/supportingmaterials/resources/about.gif b/praclib/temp/core.default.uma_concept.base/guidances/supportingmaterials/resources/about.gif
new file mode 100644
index 0000000..1316610
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/supportingmaterials/resources/about.gif
Binary files differ
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/supportingmaterials/resources/bookc.gif b/praclib/temp/core.default.uma_concept.base/guidances/supportingmaterials/resources/bookc.gif
new file mode 100644
index 0000000..7f2ab85
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/supportingmaterials/resources/bookc.gif
Binary files differ
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/supportingmaterials/resources/bookcL.gif b/praclib/temp/core.default.uma_concept.base/guidances/supportingmaterials/resources/bookcL.gif
new file mode 100644
index 0000000..6c5b064
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/supportingmaterials/resources/bookcL.gif
Binary files differ
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/supportingmaterials/resources/copyrite.htm b/praclib/temp/core.default.uma_concept.base/guidances/supportingmaterials/resources/copyrite.htm
new file mode 100644
index 0000000..51edd3a
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/supportingmaterials/resources/copyrite.htm
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<title>IBM(R) Rational(R) Intellectual Property Notices and Other Licensing Requirements</title>
+</head>
+
+<body>
+NOTICES AND INFORMATION <br />
+<br />
+<p>
+ These Notices apply to portions of this Program. They are not part of the license under which you receive the Program
+ and are provided for informational purposes.
+</p>
+<p>
+About This Content
+</p>
+<p>
+May 2, 2006
+</p>
+<p>
+License
+</p>
+<p>
+The Eclipse Foundation makes available all content in this plug-in ("Content"). Unless otherwise indicated below, the Content is provided to you under the terms and conditions of the Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is available at http://www.eclipse.org/legal/epl-v10.html. For purposes of the EPL, "Program" will mean the Content.
+</p>
+<p>
+If you did not receive this Content directly from the Eclipse Foundation, the Content is being redistributed by another party ("Redistributor") and different terms and conditions may apply to your use of any object code in the Content. Check the RedistributorÂ’s license that was provided with the Content. If no such license exists, contact the Redistributor. Unless otherwise indicated below, the terms and conditions of the EPL still apply to any source code in the Content and such source code may be obtained at http://www.eclipse.org.
+ <br>
+</BODY>
+</HTML>
\ No newline at end of file
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/supportingmaterials/resources/cr_sym_obj.gif b/praclib/temp/core.default.uma_concept.base/guidances/supportingmaterials/resources/cr_sym_obj.gif
new file mode 100644
index 0000000..d1f6a31
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/supportingmaterials/resources/cr_sym_obj.gif
Binary files differ
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/supportingmaterials/resources/whats_new.gif b/praclib/temp/core.default.uma_concept.base/guidances/supportingmaterials/resources/whats_new.gif
new file mode 100644
index 0000000..7039631
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/supportingmaterials/resources/whats_new.gif
Binary files differ
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/supportingmaterials/whats_new_base_concepts.xmi b/praclib/temp/core.default.uma_concept.base/guidances/supportingmaterials/whats_new_base_concepts.xmi
new file mode 100644
index 0000000..a58cb11
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/supportingmaterials/whats_new_base_concepts.xmi
@@ -0,0 +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: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="-eyFTMGu83WSs-yJedYCY3g"
+ name="new_supporting_material,_qxY8MEALEdqTMtYjAib0og" guid="-eyFTMGu83WSs-yJedYCY3g"
+ changeDate="2006-01-19T02:07:01.069-0500" version="7.2.0">
+ <mainDescription><p>
+ For a description of this plug-in's contents, refer to <a class="elementLink"
+ href="./../../../core.default.uma_concepts/guidances/supportingmaterials/about_base_concepts_ED50DDAD.html"
+ guid="_uvje4D_fEdqDFvujd6NHiA">About Base Concepts</a>.
+</p>
+<p>
+ The new features and changes from version to version are described below.
+</p>
+<ul>
+ <li>
+ <a href="#2.0" >From&nbsp;2.0 to 2.0.1</a>
+ </li>
+ <li>
+ <a href="#1.0" >1.0</a>
+ </li>
+</ul>
+<h2>
+ <a id="1.0" name="1.0">1.0</a>
+</h2>
+<p>
+ This is the initial release of this plug-in.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/activity.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/activity.xmi
new file mode 100644
index 0000000..49cd813
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/activity.xmi
@@ -0,0 +1,19 @@
+<?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: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="-67u6-WRUmTOB9IdLgQg6aw"
+ name="activity,_yoVhMB_IEdq6CKKKq4D7YA" guid="-67u6-WRUmTOB9IdLgQg6aw" changeDate="2007-12-05T12:58:30.333-0500"
+ version="1.0.0">
+ <mainDescription><p>
+ In the <a class="elementLink" href="./../../../core.default.uma_concepts/guidances/termdefinitions/uma_73BA0C0C.html"
+ guid="_cj6jkB_PEdq6CKKKq4D7YA">UMA</a>&nbsp;, an activity is a <a class="elementLink"
+ href="./../../../core.default.uma_concepts/guidances/termdefinitions/breakdown_element_E6E32412.html"
+ guid="_cvdpEB_LEdq6CKKKq4D7YA">breakdown element</a>&nbsp;which supports the nesting and logical grouping of related
+ process elements such as <a class="elementLink"
+ href="./../../../core.default.uma_concepts/guidances/termdefinitions/descriptor_D52B7BB3.html"
+ guid="_7rS6AB_JEdq6CKKKq4D7YA">descriptor</a>&nbsp;and sub-activities, thus forming <a class="elementLink"
+ href="./../../../core.default.uma_concepts/guidances/termdefinitions/breakdown_structure_C53514C1.html"
+ guid="_95LCoB_QEdq6CKKKq4D7YA">breakdown structure</a>s.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/activity_detail_diagram.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/activity_detail_diagram.xmi
new file mode 100644
index 0000000..9e9bf20
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/activity_detail_diagram.xmi
@@ -0,0 +1,19 @@
+<?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: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="_ycE8HdnmEdmO6L4XMImrsA"
+ name="activity_detail_diagram,_ycE8HNnmEdmO6L4XMImrsA" guid="_ycE8HdnmEdmO6L4XMImrsA"
+ changeDate="2006-09-28T16:40:16.078-0400" version="7.2.0">
+ <mainDescription>Diagram depicting all the <a class="elementLink"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/breakdown_element_E6E32412.html"
+guid="_cvdpEB_LEdq6CKKKq4D7YA">breakdown element</a>s within the scope of the selected process element. This diagram also
+depicts input/output relationships between <a class="elementLink"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/task_6C1FF051.html"
+guid="_x459ktnmEdmO6L4XMImrsA">task</a>s,&nbsp;activities, and <a class="elementLink"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/work_product_826E4C22.html"
+guid="_H4JXwB_SEdq6CKKKq4D7YA">work product</a>s;&nbsp;as well as responsibility relationships between <a
+class="elementLink" href="./../../../core.default.uma_concepts/guidances/termdefinitions/role_37A0C602.html"
+guid="_yUefQNnmEdmO6L4XMImrsA">role</a>s and tasks. Activity detail diagrams are used to provide a complete summary of an
+activity&nbsp;and thus&nbsp;improve their comprehensibility.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/artifact.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/artifact.xmi
new file mode 100644
index 0000000..3c29f02
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/artifact.xmi
@@ -0,0 +1,12 @@
+<?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: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="_x7cUNNnmEdmO6L4XMImrsA"
+ name="artifact,_x7cUM9nmEdmO6L4XMImrsA" guid="_x7cUNNnmEdmO6L4XMImrsA" changeDate="2007-12-05T13:14:47.380-0500"
+ version="7.2.0">
+ <mainDescription>Artifacts are a specialized type of <a class="elementLink"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/work_product_826E4C22.html"
+guid="_H4JXwB_SEdq6CKKKq4D7YA">work product</a> that represents tangible, non-trivial items that are consumed, produced, or
+modified by tasks. Artifacts may be composed of other artifacts and often serve as a basis for defining reusable assets.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/assists.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/assists.xmi
new file mode 100644
index 0000000..b4e999b
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/assists.xmi
@@ -0,0 +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: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="-uMQBRmGsu_0DumDeidK1ig"
+ name=",_2AKO8KNbEdyMFYhoCpD11Q" guid="-uMQBRmGsu_0DumDeidK1ig" changeDate="2007-12-05T12:59:52.770-0500">
+ <mainDescription>Describes roles that may be consulted on task but are not actually assigned to perform the work.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/breakdown_element.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/breakdown_element.xmi
new file mode 100644
index 0000000..cc2e152
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/breakdown_element.xmi
@@ -0,0 +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: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="-7pbyO29v0VnsosWHabeZDQ"
+ name="breakdown_element,_cvdpEB_LEdq6CKKKq4D7YA" guid="-7pbyO29v0VnsosWHabeZDQ"
+ changeDate="2005-09-22T19:07:46.580-0700">
+ <mainDescription>Any element modeled in <a class="elementLink"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/uma_73BA0C0C.html"
+guid="_cj6jkB_PEdq6CKKKq4D7YA">UMA</a>&nbsp;that is part of <a class="elementLink"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/process_68E308B4.html"
+guid="_yQ5m2NnmEdmO6L4XMImrsA">process</a>&nbsp;structure.<!--EndFragment--></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/breakdown_structure.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/breakdown_structure.xmi
new file mode 100644
index 0000000..54f57bf
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/breakdown_structure.xmi
@@ -0,0 +1,16 @@
+<?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: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="-dpUlq7kJXlJBUjvh7lHW7Q"
+ name="breakdown_structure,_95LCoB_QEdq6CKKKq4D7YA" guid="-dpUlq7kJXlJBUjvh7lHW7Q"
+ changeDate="2006-09-28T13:44:00.796-0700">
+ <mainDescription><p>
+ A <a class="elementLink" href="./../../../core.default.uma_concepts/guidances/termdefinitions/uma_73BA0C0C.html"
+ guid="_cj6jkB_PEdq6CKKKq4D7YA">UMA</a>&nbsp;construct that specifies a <a class="elementLink"
+ href="./../../../core.default.uma_concepts/guidances/termdefinitions/process_68E308B4.html"
+ guid="_yQ5m2NnmEdmO6L4XMImrsA">process</a>&nbsp;as the hierarchical composition of <a class="elementLink"
+ href="./../../../core.default.uma_concepts/guidances/termdefinitions/breakdown_element_E6E32412.html"
+ guid="_cvdpEB_LEdq6CKKKq4D7YA">breakdown element</a>s.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/capability_pattern.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/capability_pattern.xmi
new file mode 100644
index 0000000..3ad108d
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/capability_pattern.xmi
@@ -0,0 +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.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="-AY7-wWpxUmZp4c-odX8e7g"
+ name="capability_pattern,_2RUJACO4EdqaNq6Ptg8uyA" guid="-AY7-wWpxUmZp4c-odX8e7g"
+ changeDate="2007-12-05T13:00:44.551-0500" version="1.0.0">
+ <mainDescription><p>
+ <!--StartFragment-->A&nbsp;special type of&nbsp;<a class="elementLink"
+ href="./../../../core.default.uma_concepts/guidances/termdefinitions/process_68E308B4.html"
+ guid="_yQ5m2NnmEdmO6L4XMImrsA">process</a>&nbsp;used to define a stereotypical way of performing work related to a
+ particular subject.&nbsp; Capability Patterns are often used as course grained building blocks to assemble delivery
+ processes.<!--EndFragment-->
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/checklist.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/checklist.xmi
new file mode 100644
index 0000000..6b5762c
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/checklist.xmi
@@ -0,0 +1,10 @@
+<?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: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="-d9uOWrjeHbE_1Xu2RIs-0A"
+ name="new_term_definition,_7vpJsMaCEduMlb2cQZNTYw" guid="-d9uOWrjeHbE_1Xu2RIs-0A"
+ changeDate="2007-02-27T12:01:08.783-0500" version="7.2.0">
+ <mainDescription>A specialized type of guidance that identifies a series of items that need to be completed or verified. Checklists are
+often used in reviews such as walkthroughs or inspections.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/composite_role.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/composite_role.xmi
new file mode 100644
index 0000000..6ed23a1
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/composite_role.xmi
@@ -0,0 +1,12 @@
+<?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: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="-KNw2PnSSEEogCvg4sj1ebg"
+ name="new_term_definition,_PzL7EMaEEduMlb2cQZNTYw" guid="-KNw2PnSSEEogCvg4sj1ebg"
+ changeDate="2007-02-27T09:02:53.638-0800">
+ <mainDescription>A special role descriptor that relates to more than one <a class="elementLinkWithUserText"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/role_37A0C602.html"
+guid="_yUefQNnmEdmO6L4XMImrsA">role</a>. It represents a grouping of roles with the main purpose of reducing the number of
+roles defined in method content for a process.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/concept.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/concept.xmi
new file mode 100644
index 0000000..d8ecde0
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/concept.xmi
@@ -0,0 +1,10 @@
+<?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: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="-5bvXXNVzF7mZf0R7Oez5_g"
+ name="new_term_definition,_wMchYMaEEduMlb2cQZNTYw" guid="-5bvXXNVzF7mZf0R7Oez5_g"
+ changeDate="2007-02-27T12:06:17.781-0500" version="7.2.0">
+ <mainDescription>A specialized type of guidance that outlines key ideas or basic principles that serve as foundation for additional
+information.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/custom_category.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/custom_category.xmi
new file mode 100644
index 0000000..5097e1e
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/custom_category.xmi
@@ -0,0 +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: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="-G9dXZH2IkpWGi4NZK-2vEw"
+ name="new_term_definition,_eqw94MaFEduMlb2cQZNTYw" guid="-G9dXZH2IkpWGi4NZK-2vEw"
+ changeDate="2007-12-05T13:01:49.411-0500" version="7.2.0">
+ <mainDescription>Used to categorize content based on the user's criteria. One important use is for constructing <a
+class="elementLinkWithUserText" href="./../../../core.default.uma_concepts/guidances/termdefinitions/view_953B6A0D.html"
+guid="_GH6WUMaJEduMlb2cQZNTYw">views</a>&nbsp;for publishing.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/deliverable.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/deliverable.xmi
new file mode 100644
index 0000000..396382f
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/deliverable.xmi
@@ -0,0 +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: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="_yFbWodnmEdmO6L4XMImrsA"
+ name="deliverable,_yFbWoNnmEdmO6L4XMImrsA" guid="_yFbWodnmEdmO6L4XMImrsA" changeDate="2007-12-05T13:02:02.005-0500"
+ version="7.2.0">
+ <mainDescription><p>
+ A&nbsp;specialized type of work prodcut&nbsp;used to define the primary outputs that represent value, material or
+ otherwise,&nbsp;to the client, customer or other stakeholders.&nbsp; These are typically the result of packaging
+ other&nbsp;work products for sign-off and delivery.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/delivery_process.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/delivery_process.xmi
new file mode 100644
index 0000000..49bffde
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/delivery_process.xmi
@@ -0,0 +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: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="-IsV3QdyMdwFlqznd4UAYhw"
+ name="delivery_process,_ZufeMCO3EdqaNq6Ptg8uyA" guid="-IsV3QdyMdwFlqznd4UAYhw"
+ changeDate="2007-12-05T13:02:37.458-0500" version="7.2.0">
+ <mainDescription>A delivery process is a special <a class="elementLink"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/process_68E308B4.html"
+guid="_yQ5m2NnmEdmO6L4XMImrsA">process</a> describing a complete and integrated approach for performing a specific project
+type. <!--StartFragment-->It provides a complete end-to-end lifecycle (for it's scope) and can be used as a reference for
+running projects with similar characteristics.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/descriptor.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/descriptor.xmi
new file mode 100644
index 0000000..33412c6
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/descriptor.xmi
@@ -0,0 +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: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="-TI6lqoTE1op3-SnmGa2S9Q"
+ name="descriptor,_7rS6AB_JEdq6CKKKq4D7YA" guid="-TI6lqoTE1op3-SnmGa2S9Q" changeDate="2006-09-28T16:52:03.671-0400"
+ version="7.2.0">
+ <mainDescription>Defines how method content is represented in a process.&nbsp;&nbsp;Descriptors are the key concept for realizing the
+separation of proces&nbsp;from metho content.&nbsp;A&nbsp;descriptor&nbsp;has its own relationships and properties which
+can be modified independent of the default relationships&nbsp;defined in the method content.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/discipline.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/discipline.xmi
new file mode 100644
index 0000000..dc0cfc3
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/discipline.xmi
@@ -0,0 +1,12 @@
+<?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: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="_yGUuitnmEdmO6L4XMImrsA"
+ name="discipline,_yGUuidnmEdmO6L4XMImrsA" guid="_yGUuitnmEdmO6L4XMImrsA" changeDate="2006-09-28T16:52:55.750-0400"
+ version="7.2.0">
+ <mainDescription><p>
+ Primary categorization mechanism for organizing&nbsp;tasks that&nbsp;define&nbsp;a major 'area of concern' and/or
+ cooperation of work effort.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/discipline_grouping.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/discipline_grouping.xmi
new file mode 100644
index 0000000..cc2e018
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/discipline_grouping.xmi
@@ -0,0 +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: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="-JldA7oTinGpXvoc3Tj-3JQ"
+ name="new_term_definition,_V5LO8KNcEdyMFYhoCpD11Q" guid="-JldA7oTinGpXvoc3Tj-3JQ">
+ <mainDescription>A collection of related disciplines defined for a specific usage or context.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/domain.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/domain.xmi
new file mode 100644
index 0000000..08d7f1f
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/domain.xmi
@@ -0,0 +1,12 @@
+<?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: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="_yHEVYtnmEdmO6L4XMImrsA"
+ name="domain,_yHEVYdnmEdmO6L4XMImrsA" guid="_yHEVYtnmEdmO6L4XMImrsA" changeDate="2007-02-27T14:45:19.192-0500"
+ version="7.2.0">
+ <mainDescription><p>
+ Primary catgorization mechanism for organizing work products that have an affinity to each other based on resources,
+ timing, relationships or general subject area.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/estimation_considerations.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/estimation_considerations.xmi
new file mode 100644
index 0000000..68ac2dc
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/estimation_considerations.xmi
@@ -0,0 +1,10 @@
+<?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: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="-uIAjd6ptx9yCso_AZSbTUw"
+ name="estimation_considerations,_cSEDoKNcEdyMFYhoCpD11Q" guid="-uIAjd6ptx9yCso_AZSbTUw"
+ changeDate="2007-12-05T13:04:08.005-0500">
+ <mainDescription>A specialized type&nbsp;of guidance&nbsp;that describes&nbsp;the amount of effort to produce a work product&nbsp;or perform
+a task&nbsp;including any influencing factors.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/example.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/example.xmi
new file mode 100644
index 0000000..ad36498
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/example.xmi
@@ -0,0 +1,12 @@
+<?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: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="-WGi50KpVG9oQbP82Xvk1UA"
+ name="new_term_definition,_nE6fsMaFEduMlb2cQZNTYw" guid="-WGi50KpVG9oQbP82Xvk1UA"
+ changeDate="2007-02-27T12:12:23.699-0500" version="7.2.0">
+ <mainDescription><p>
+ A specialized type&nbsp;of&nbsp; guidance&nbsp;used to include typical samples of the items to be produced, may often
+ only be a partial sample that is intended as further guidance rather than something to be reused.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/guidance.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/guidance.xmi
new file mode 100644
index 0000000..c6f23f5
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/guidance.xmi
@@ -0,0 +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: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="-CTatxBir28UK-VwWwDij-g"
+ name="guidance,_83ttAB_NEdq6CKKKq4D7YA" guid="-CTatxBir28UK-VwWwDij-g" changeDate="2007-12-05T13:04:49.083-0500"
+ version="7.2.0">
+ <mainDescription><p>
+ General term referring to all types of material that provide additional detail on other types of elements.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/guideline.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/guideline.xmi
new file mode 100644
index 0000000..1a2909a
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/guideline.xmi
@@ -0,0 +1,20 @@
+<?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: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="-EEF1Y386HZ1XRsyHmGLE3g"
+ name="new_term_definition,_uK8HMMaFEduMlb2cQZNTYw" guid="-EEF1Y386HZ1XRsyHmGLE3g"
+ changeDate="2007-12-05T13:06:46.442-0500" version="7.2.0">
+ <mainDescription>A specialized type of&nbsp;<a class="elementLinkWithUserText"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/guidance_549AC394.html"
+guid="_83ttAB_NEdq6CKKKq4D7YA">guidance</a>&nbsp;that provides additional detail on how to handle a particular <a
+class="elementLinkWithUserText"
+href="C:/Lib/rework/opn/core.default.uma_concepts/guidances/termdefinitions/content_element_DA3AD029.html"
+guid="_N8x34B_LEdq6CKKKq4D7YA">content element</a>. Guidelines most commonly describe how to perform some set of actions
+related to a <a class="elementLinkWithUserText"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/task_6C1FF051.html"
+guid="_x459ktnmEdmO6L4XMImrsA">tasks</a> or provide additional rules or recommendations related to the representation of <a
+class="elementLinkWithUserText"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/work_product_826E4C22.html"
+guid="_H4JXwB_SEdq6CKKKq4D7YA">work products</a>.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/input.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/input.xmi
new file mode 100644
index 0000000..015451e
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/input.xmi
@@ -0,0 +1,17 @@
+<?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: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="_yK8IydnmEdmO6L4XMImrsA"
+ name="input,_yK8IyNnmEdmO6L4XMImrsA" guid="_yK8IydnmEdmO6L4XMImrsA" changeDate="2007-12-05T13:05:45.005-0500"
+ version="7.2.0">
+ <mainDescription>In the <a class="elementLink" href="./../../../core.default.uma_concepts/guidances/termdefinitions/uma_73BA0C0C.html"
+guid="_cj6jkB_PEdq6CKKKq4D7YA">UMA</a>, input defines the&nbsp;<a class="elementLink"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/work_product_826E4C22.html"
+guid="_H4JXwB_SEdq6CKKKq4D7YA">work product</a>s needed to perform a <a class="elementLink"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/task_6C1FF051.html"
+guid="_x459ktnmEdmO6L4XMImrsA">task</a>.&nbsp; These inputs are further categorized as being optional, mandatory or
+external.&nbsp; Optional inputs may be excluded from the task in some cases without consequences, while without mandatory
+inputs it is typically not possible to complete the task.&nbsp; External inputs are used to defined mandatory inputs that
+are the result of work outside the scope of the defined process.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/iteration.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/iteration.xmi
new file mode 100644
index 0000000..336979c
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/iteration.xmi
@@ -0,0 +1,16 @@
+<?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: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="-FxDDt6uNV4K2c04hoFKBpQ"
+ name="new_term_definition,_5vWoEKNcEdyMFYhoCpD11Q" guid="-FxDDt6uNV4K2c04hoFKBpQ"
+ changeDate="2008-02-22T02:05:21.609-0500" version="7.2.0">
+ <mainDescription><p>
+ <strong>[*** This definition needs rework to make it less specific to UMA itself and more generic. ***]</strong>
+</p>
+<p>
+ A specialized type off activity used to represent repeating items within a work breakdown structure
+ (WBS).&nbsp;&nbsp;<em>(It is included as convenience to represent a standard structuring element, other types of
+ process elements may also be identified as repeatable.)</em>
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/method_architecture.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/method_architecture.xmi
new file mode 100644
index 0000000..74a014d
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/method_architecture.xmi
@@ -0,0 +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: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="-kbyERT7ThI5QD4X7GME9pQ"
+ name="new_term_definition,_A6we0KNdEdyMFYhoCpD11Q" guid="-kbyERT7ThI5QD4X7GME9pQ">
+ <mainDescription>A method architecture defines the concepts, their properties, and relationships for defining methods and processes. It is
+typically compromised of a meta-model, modeling language, or schema (synonyms) that is used for organizing large amounts of
+descriptions for management development methods and processes, such as software engineering, mechanical engineering,
+business transformation, sales cycles etc.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/method_configuration.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/method_configuration.xmi
new file mode 100644
index 0000000..d233850
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/method_configuration.xmi
@@ -0,0 +1,12 @@
+<?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: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="-kzN6-iqn9zDtfnJc7IWkIg"
+ name="new_term_definition,__V7pAMaEEduMlb2cQZNTYw" guid="-kzN6-iqn9zDtfnJc7IWkIg"
+ changeDate="2007-12-05T13:09:22.833-0500" version="7.2.0">
+ <mainDescription>A method configuration specifies the selection of a logical subset of a <a class="elementLinkWithUserText"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/method_library_6E08F9E5.html"
+guid="_1xELEMaFEduMlb2cQZNTYw">method library</a>, defined in terms of selected packages within plug-ins and any necessary
+views.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/method_content.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/method_content.xmi
new file mode 100644
index 0000000..1f20c00
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/method_content.xmi
@@ -0,0 +1,20 @@
+<?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: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="-akU0PqDaad4Ns5MQhVBJ7Q"
+ name="method_content,_Ts2joB_MEdq6CKKKq4D7YA" guid="-akU0PqDaad4Ns5MQhVBJ7Q" changeDate="2007-12-05T13:10:15.692-0500"
+ version="7.2.0">
+ <mainDescription><p>
+ Defines the primary reusable building blocks or reference materials of the method framework that exist outside of any
+ predefined lifecycle.&nbsp;The basic content elements are: <a class="elementLink"
+ href="./../../../core.default.uma_concepts/guidances/termdefinitions/role_37A0C602.html"
+ guid="_yUefQNnmEdmO6L4XMImrsA">role</a>s, <a class="elementLink"
+ href="./../../../core.default.uma_concepts/guidances/termdefinitions/task_6C1FF051.html"
+ guid="_x459ktnmEdmO6L4XMImrsA">task</a>s, <a class="elementLink"
+ href="./../../../core.default.uma_concepts/guidances/termdefinitions/work_product_826E4C22.html"
+ guid="_H4JXwB_SEdq6CKKKq4D7YA">work product</a>s and <a class="elementLink"
+ href="./../../../core.default.uma_concepts/guidances/termdefinitions/guidance_549AC394.html"
+ guid="_83ttAB_NEdq6CKKKq4D7YA">guidance</a>.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/method_library.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/method_library.xmi
new file mode 100644
index 0000000..da42c06
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/method_library.xmi
@@ -0,0 +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.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="-m6mx-VR4CReQNhrf4b8ykQ"
+ name="new_term_definition,_1xELEMaFEduMlb2cQZNTYw" guid="-m6mx-VR4CReQNhrf4b8ykQ"
+ changeDate="2007-02-27T09:13:59.698-0800">
+ <mainDescription>A&nbsp;physical container for <a class="elementLinkWithUserText"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/method_plugin_190B9F5E.html"
+guid="_D4TLgMaGEduMlb2cQZNTYw">method plug-ins</a> and <a class="elementLinkWithUserText"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/method_configuration_C2B8FA8A.html"
+guid="__V7pAMaEEduMlb2cQZNTYw">method configuration</a> definitions. All <a class="elementLinkWithUserText"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/content_element_DA3AD029.html"
+guid="_N8x34B_LEdq6CKKKq4D7YA">method elements</a> are stored in a method library.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/method_plugin.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/method_plugin.xmi
new file mode 100644
index 0000000..518e652
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/method_plugin.xmi
@@ -0,0 +1,14 @@
+<?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: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="-q0ixH8duU7qb8agEywAFHQ"
+ name="new_term_definition,_D4TLgMaGEduMlb2cQZNTYw" guid="-q0ixH8duU7qb8agEywAFHQ"
+ changeDate="2007-02-27T09:15:37.261-0800">
+ <mainDescription>Represents a physical container for method packages. It defines a largest granularity level for the modularization and
+organization of <a class="elementLinkWithUserText"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/content_package_F5C69063.html"
+guid="_SAWgwMaFEduMlb2cQZNTYw">method content</a> and <a class="elementLinkWithUserText"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/process_68E308B4.html"
+guid="_yQ5m2NnmEdmO6L4XMImrsA">processes</a>.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/outcome.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/outcome.xmi
new file mode 100644
index 0000000..040db6d
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/outcome.xmi
@@ -0,0 +1,16 @@
+<?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: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="-SQyJsrOEI73uLZzjRVmSBA"
+ name="outcome,_LNAAcB_iEdqAHrsQ7-jSbw" guid="-SQyJsrOEI73uLZzjRVmSBA" changeDate="2007-12-05T13:13:31.817-0500"
+ version="7.2.0">
+ <mainDescription><p>
+ <!--StartFragment-->Specialized type of <a class="elementLink"
+ href="./../../../core.default.uma_concepts/guidances/termdefinitions/work_product_826E4C22.html"
+ guid="_H4JXwB_SEdq6CKKKq4D7YA">work product</a>s used to descibe intangible items such as the completion of some set of
+ activities, a result or state. A key differentiator for outcomes against artifacts is that outcomes are not candidates
+ for harvesting as reusable assets. Outcomes can not have associated templates or examples and are not possible to reuse
+ as assets on other projects.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/output.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/output.xmi
new file mode 100644
index 0000000..3452cbd
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/output.xmi
@@ -0,0 +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: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="_yPaZGtnmEdmO6L4XMImrsA"
+ name="output,_yPaZGdnmEdmO6L4XMImrsA" guid="_yPaZGtnmEdmO6L4XMImrsA" changeDate="2007-12-05T13:14:15.348-0500"
+ version="7.2.0">
+ <mainDescription>Defines the results of performing some task in terms of the <a class="elementLink"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/work_product_826E4C22.html"
+guid="_H4JXwB_SEdq6CKKKq4D7YA">work product</a>s produced or modifed.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/performer.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/performer.xmi
new file mode 100644
index 0000000..e56bf16
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/performer.xmi
@@ -0,0 +1,10 @@
+<?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: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="-EF5eqKSqgTApRj_uXeG39w"
+ name="new_term_definition,_GL2vkKNeEdyMFYhoCpD11Q" guid="-EF5eqKSqgTApRj_uXeG39w">
+ <mainDescription>Describes the roles that will be executing a task.&nbsp; There are two types of performs roles, a single primary performer
+responsible for the completion of the tasks and additional performers.&nbsp; There may be any number of additional
+performers and both are consided as allocated resources for the purposed of project scheduling.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/phase.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/phase.xmi
new file mode 100644
index 0000000..abdfbfa
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/phase.xmi
@@ -0,0 +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: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="-88Vj7cM5EcVnfesDYaAkww"
+ name="new_term_definition,_K9eecMaGEduMlb2cQZNTYw" guid="-88Vj7cM5EcVnfesDYaAkww"
+ changeDate="2007-12-05T13:15:10.255-0500" version="7.2.0">
+ <mainDescription><p>
+ A specialized type of activity&nbsp;that represents a significant period in a project normally ending with a decision
+ checkpoint, major milestones, or a set of deliverables.&nbsp; Phases typically have well defined objectives and provide
+ the basis for how the project work will be structured.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/practice.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/practice.xmi
new file mode 100644
index 0000000..ff5aa02
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/practice.xmi
@@ -0,0 +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: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="-kxtQBsUei9KRl8Z6tOSQ-g"
+ name="new_term_definition,_wxYvkMaGEduMlb2cQZNTYw" guid="-kxtQBsUei9KRl8Z6tOSQ-g"
+ changeDate="2007-12-05T13:15:29.176-0500" version="7.2.0">
+ <mainDescription>A specialized type&nbsp;of&nbsp;<a class="elementLinkWithUserText"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/guidance_549AC394.html"
+guid="_83ttAB_NEdq6CKKKq4D7YA">guidance</a> that describes&nbsp;a proven way&nbsp;of doing something or common approaches
+and strategies that represent best practices.&nbsp; This is also used to&nbsp;represent standards and policies related to
+methods.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/process.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/process.xmi
new file mode 100644
index 0000000..2900129
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/process.xmi
@@ -0,0 +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: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="_yQ5m2dnmEdmO6L4XMImrsA"
+ name="process,_yQ5m2NnmEdmO6L4XMImrsA" guid="_yQ5m2dnmEdmO6L4XMImrsA" changeDate="2007-12-05T13:19:32.051-0500"
+ version="7.2.0">
+ <mainDescription><p>
+ Describes the assembly of method content&nbsp;in a sequence or workflow that defines how the work will be executed.
+</p><!--EndFragment--><!--EndFragment--></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/report.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/report.xmi
new file mode 100644
index 0000000..eb0981b
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/report.xmi
@@ -0,0 +1,12 @@
+<?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: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="-lEbg0SKqsikKdCRXPVvRmw"
+ name="new_term_definition,_bDCXUMaHEduMlb2cQZNTYw" guid="-lEbg0SKqsikKdCRXPVvRmw"
+ changeDate="2007-12-05T13:20:32.973-0500" version="7.2.0">
+ <mainDescription>A&nbsp;specialized type&nbsp;of&nbsp;&nbsp;<a class="elementLinkWithUserText"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/guidance_549AC394.html"
+guid="_83ttAB_NEdq6CKKKq4D7YA">guidance</a> used to provide guidance on representing the output of an automated tool that
+may be a combination of information from one or more other work products. .</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/reusable_asset.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/reusable_asset.xmi
new file mode 100644
index 0000000..422fb09
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/reusable_asset.xmi
@@ -0,0 +1,14 @@
+<?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: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="-H9RSfWhEhOJscNkDKGPcBA"
+ name="new_term_definition,_kSKZUMaHEduMlb2cQZNTYw" guid="-H9RSfWhEhOJscNkDKGPcBA"
+ changeDate="2007-12-05T13:20:56.098-0500" version="7.2.0">
+ <mainDescription>A specialized type&nbsp;of <a class="elementLinkWithUserText"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/guidance_549AC394.html"
+guid="_83ttAB_NEdq6CKKKq4D7YA">guidance</a> linking to intellectual capital that can be utilized to perform some task or
+leveraged as a starting point for the creation of a solution.&nbsp; This type of guidance&nbsp;is usually represented a
+link to some external source.&nbsp; This may include assets such as source code, templates, patterns, architectural
+frameworks, domain models, and so on - that can be reused in a different contexts.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/roadmap.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/roadmap.xmi
new file mode 100644
index 0000000..4f97a42
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/roadmap.xmi
@@ -0,0 +1,12 @@
+<?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: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="-gCtPvpHU3vmCQKQ1ymqBvw"
+ name="new_term_definition,_19dWYMaHEduMlb2cQZNTYw" guid="-gCtPvpHU3vmCQKQ1ymqBvw"
+ changeDate="2007-12-05T13:21:39.833-0500" version="7.2.0">
+ <mainDescription>A specialized type&nbsp;of&nbsp;<a class="elementLinkWithUserText"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/guidance_549AC394.html"
+guid="_83ttAB_NEdq6CKKKq4D7YA">guidance</a>&nbsp;that is specific to a process that represents a linear walkthrough of
+those items from a particular perspective.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/role.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/role.xmi
new file mode 100644
index 0000000..14a9522
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/role.xmi
@@ -0,0 +1,14 @@
+<?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: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="_yUefQdnmEdmO6L4XMImrsA"
+ name="role,_yUefQNnmEdmO6L4XMImrsA" guid="_yUefQdnmEdmO6L4XMImrsA" changeDate="2008-01-08T07:58:05.386-0500"
+ version="1.0.0">
+ <mainDescription><p>
+ Describes a standard set of responsibilities and corresponding skills necessary to perform a task&nbsp;or create a work
+ product.&nbsp; A Role is <strong>not</strong> a job description the same person may execute several roles
+ simultaneously or during the course of a project and a role may likewise be defined to represent a group such as a
+ review board.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/role_set.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/role_set.xmi
new file mode 100644
index 0000000..44f0c52
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/role_set.xmi
@@ -0,0 +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: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="-gOXu6EqfZHMmtekNk8IDqA"
+ name="new_term_definition,_Fs8HAMaIEduMlb2cQZNTYw" guid="-gOXu6EqfZHMmtekNk8IDqA"
+ changeDate="2007-12-05T13:22:19.208-0500" version="7.2.0">
+ <mainDescription>A specialized type of category used to organize <a class="elementLinkWithUserText"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/role_37A0C602.html"
+guid="_yUefQNnmEdmO6L4XMImrsA">roles</a> by certain commonalities such as type of work, profession or area of knowledge.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/role_set_grouping.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/role_set_grouping.xmi
new file mode 100644
index 0000000..965235b
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/role_set_grouping.xmi
@@ -0,0 +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: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="-0K7iy91rKIS0h8kZfVgBvg"
+ name="new_term_definition,_D8F28KNfEdyMFYhoCpD11Q" guid="-0K7iy91rKIS0h8kZfVgBvg">
+ <mainDescription>A specialized category used to organize role sets.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/step.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/step.xmi
new file mode 100644
index 0000000..73d1a9f
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/step.xmi
@@ -0,0 +1,12 @@
+<?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: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="-KfXoeGTRnQImE1byTBtryQ"
+ name="step,_BqZloB_eEdqAHrsQ7-jSbw" guid="-KfXoeGTRnQImE1byTBtryQ" changeDate="2007-12-05T13:23:34.301-0500"
+ version="7.2.0">
+ <mainDescription>Sub-section of a <a class="elementLink"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/task_6C1FF051.html"
+guid="_x459ktnmEdmO6L4XMImrsA">task</a>&nbsp;used to organize the work to be performed to achieve the overall goal of the
+task. Not all Steps are necessarily performed each time a task is executed in a process.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/supporting_material.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/supporting_material.xmi
new file mode 100644
index 0000000..a1dcbe2
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/supporting_material.xmi
@@ -0,0 +1,12 @@
+<?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: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="-_-iQ4eQyiQVM7YhXcb90-g"
+ name="new_term_definition,_SwvUgMaIEduMlb2cQZNTYw" guid="-_-iQ4eQyiQVM7YhXcb90-g"
+ changeDate="2007-02-27T09:33:31.807-0800">
+ <mainDescription>A&nbsp;<a class="elementLinkWithUserText"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/guidance_549AC394.html"
+guid="_83ttAB_NEdq6CKKKq4D7YA">guidance</a>&nbsp;that is a catch-all for other types of guidance not specifically defined
+elsewhere.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/task.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/task.xmi
new file mode 100644
index 0000000..f2c0be3
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/task.xmi
@@ -0,0 +1,12 @@
+<?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: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="_x459k9nmEdmO6L4XMImrsA"
+ name="task,_x459ktnmEdmO6L4XMImrsA" guid="_x459k9nmEdmO6L4XMImrsA" changeDate="2005-08-12T00:05:04.825-0400"
+ version="7.2.0">
+ <mainDescription><p>
+ Defines a unit of work that needs to be done in order to&nbsp;transfrom inputs into outputs through a series&nbsp;of
+ steps&nbsp;performed by one or more roles&nbsp;independent of a particular work breakdown structure (WBS).
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/team_profile.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/team_profile.xmi
new file mode 100644
index 0000000..8740f81
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/team_profile.xmi
@@ -0,0 +1,12 @@
+<?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: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="-0cxbeJahkc1eqGKztRpcPw"
+ name="new_term_definition,_rZOGIMaIEduMlb2cQZNTYw" guid="-0cxbeJahkc1eqGKztRpcPw"
+ changeDate="2007-02-27T09:34:15.884-0800">
+ <mainDescription>A&nbsp;<a class="elementLinkWithUserText"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/breakdown_element_E6E32412.html"
+guid="_cvdpEB_LEdq6CKKKq4D7YA">breakdown element</a> that groups role descriptors or composite roles, thus defining a
+nested hierarchy of teams and team members.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/template.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/template.xmi
new file mode 100644
index 0000000..7b187f2
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/template.xmi
@@ -0,0 +1,14 @@
+<?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: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="--SOXfR7BTPs3CqtNP8R6Rw"
+ name="new_term_definition,_1MLN8MaIEduMlb2cQZNTYw" guid="--SOXfR7BTPs3CqtNP8R6Rw"
+ changeDate="2007-12-05T13:24:41.411-0500" version="7.2.0">
+ <mainDescription>A specialized type of <a class="elementLinkWithUserText"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/guidance_549AC394.html"
+guid="_83ttAB_NEdq6CKKKq4D7YA">guidance</a>&nbsp;that specifies the structure of a work product by providing a pre-defined
+table of contents, sections, packages, and/or headings, a standardized format, as well as descriptions on how the sections
+and packages are supposed to be used and completed.&nbsp; Often provided as a form or empty instanced of a work product
+that can be used as starting point for the creation of a new one.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/term_definition.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/term_definition.xmi
new file mode 100644
index 0000000..2302dc7
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/term_definition.xmi
@@ -0,0 +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: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="-4JztP2JNqE36rtSC0UoYDw"
+ name="new_term_definition,_6SluIMaIEduMlb2cQZNTYw" guid="-4JztP2JNqE36rtSC0UoYDw"
+ changeDate="2007-12-05T13:25:06.192-0500" version="7.2.0">
+ <mainDescription>A specialized form of&nbsp;<a class="elementLinkWithUserText"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/guidance_549AC394.html"
+guid="_83ttAB_NEdq6CKKKq4D7YA">guidance</a>&nbsp;that provides definitions that are used to build up the glossary</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/tool.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/tool.xmi
new file mode 100644
index 0000000..8c939a6
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/tool.xmi
@@ -0,0 +1,12 @@
+<?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: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="-XnXEM7GkN21zwj7pKPmu3A"
+ name="new_term_definition,_BangwMaJEduMlb2cQZNTYw" guid="-XnXEM7GkN21zwj7pKPmu3A"
+ changeDate="2007-02-27T09:36:33.570-0800">
+ <mainDescription>A&nbsp;standard category used as a container for <a class="elementLinkWithUserText"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/tool_mentor_264766F3.html"
+guid="_yYy-mdnmEdmO6L4XMImrsA">tool mentors</a>. It can also provide general descriptions of the tool and its general
+capabilities.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/tool_mentor.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/tool_mentor.xmi
new file mode 100644
index 0000000..1349098
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/tool_mentor.xmi
@@ -0,0 +1,17 @@
+<?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: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="_yYy-mtnmEdmO6L4XMImrsA"
+ name="tool_mentor,_yYy-mdnmEdmO6L4XMImrsA" guid="_yYy-mtnmEdmO6L4XMImrsA" changeDate="2007-12-05T13:26:37.051-0500"
+ version="7.2.0">
+ <mainDescription>A tool mentor is a type of <a class="elementLink"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/guidance_549AC394.html"
+guid="_83ttAB_NEdq6CKKKq4D7YA">guidance</a>&nbsp;that explains how to appy a specific tool to accomplish a <a
+class="elementLink" href="./../../../core.default.uma_concepts/guidances/termdefinitions/task_6C1FF051.html"
+guid="_x459ktnmEdmO6L4XMImrsA">task</a>, perform&nbsp;or set of&nbsp;<a class="elementLink"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/step_EB040824.html"
+guid="_BqZloB_eEdqAHrsQ7-jSbw">step</a>s or instantiate a particular <a class="elementLink"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/work_product_826E4C22.html"
+guid="_H4JXwB_SEdq6CKKKq4D7YA">work product</a>.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/uma.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/uma.xmi
new file mode 100644
index 0000000..587d8fb
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/uma.xmi
@@ -0,0 +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.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="-QBSZ9hFRr8q6kvRyq1cESQ"
+ name="uma,_cj6jkB_PEdq6CKKKq4D7YA" guid="-QBSZ9hFRr8q6kvRyq1cESQ" changeDate="2005-09-07T11:44:46.648-0700">
+ <mainDescription>Stands for&nbsp;Unified Method&nbsp;Architecture. UMA is a state-of-the-art architecture for the conceiving, specifying,
+and storing of method and process metadata.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/view.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/view.xmi
new file mode 100644
index 0000000..d871fb3
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/view.xmi
@@ -0,0 +1,12 @@
+<?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: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="-dLRBfqnBlgy_0_H13LmV3A"
+ name="new_term_definition,_GH6WUMaJEduMlb2cQZNTYw" guid="-dLRBfqnBlgy_0_H13LmV3A"
+ changeDate="2007-02-27T09:37:06.441-0800">
+ <mainDescription>Structured content collections designed to drive publication and facilitate browsing. They are specified using <a
+class="elementLinkWithUserText"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/custom_category_554AC4D6.html"
+guid="_eqw94MaFEduMlb2cQZNTYw">custom categories</a>.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/white_paper.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/white_paper.xmi
new file mode 100644
index 0000000..bbf9ef2
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/white_paper.xmi
@@ -0,0 +1,14 @@
+<?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: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="-QLPRVsXtlVpWZiWmQPSsnw"
+ name="new_term_definition,_Kc1IIMaJEduMlb2cQZNTYw" guid="-QLPRVsXtlVpWZiWmQPSsnw"
+ changeDate="2007-12-05T13:27:55.661-0500" version="7.2.0">
+ <mainDescription><p>
+ A specialized type of&nbsp;<a class="elementLinkWithUserText"
+ href="./../../../core.default.uma_concepts/guidances/termdefinitions/guidance_549AC394.html"
+ guid="_83ttAB_NEdq6CKKKq4D7YA">guidance</a>&nbsp;for externally&nbsp;published papers&nbsp;that can be read and
+ understood in isolation of other content elements.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/work_product.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/work_product.xmi
new file mode 100644
index 0000000..27a9e90
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/work_product.xmi
@@ -0,0 +1,19 @@
+<?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: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="-dcYwPivhczonAxeyXweyIQ"
+ name="work_product,_H4JXwB_SEdq6CKKKq4D7YA" guid="-dcYwPivhczonAxeyXweyIQ" changeDate="2007-12-05T13:29:03.567-0500"
+ version="7.2.0">
+ <mainDescription><p>
+ Used to define and describe the items needed as input or created as output of one or more&nbsp;<a class="elementLink"
+ href="./../../../core.default.uma_concepts/guidances/termdefinitions/task_6C1FF051.html"
+ guid="_x459ktnmEdmO6L4XMImrsA">task</a>s that are the responsibility of a single role.&nbsp; See: <a
+ class="elementLink" href="./../../../core.default.uma_concepts/guidances/termdefinitions/artifact_F635D25.html"
+ guid="_x7cUM9nmEdmO6L4XMImrsA">artifact</a>, <a class="elementLink"
+ href="./../../../core.default.uma_concepts/guidances/termdefinitions/deliverable_BFE1A5A9.html"
+ guid="_yFbWoNnmEdmO6L4XMImrsA">deliverable</a>, <a class="elementLink"
+ href="./../../../core.default.uma_concepts/guidances/termdefinitions/outcome_797E7695.html"
+ guid="_LNAAcB_iEdqAHrsQ7-jSbw">outcome</a>.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/work_product_kind.xmi b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/work_product_kind.xmi
new file mode 100644
index 0000000..9c18006
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/guidances/termdefinitions/work_product_kind.xmi
@@ -0,0 +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: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="-on4oCT1DzfksdshYPKAqGg"
+ name="new_term_definition,_QWhfYMaJEduMlb2cQZNTYw" guid="-on4oCT1DzfksdshYPKAqGg"
+ changeDate="2007-12-05T13:28:32.598-0500" version="7.2.0">
+ <mainDescription>A specialized type of category used to organized <a class="elementLink"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/work_product_826E4C22.html"
+guid="_H4JXwB_SEdq6CKKKq4D7YA">work product</a>s based on their intended usage&nbsp;or type.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.default.uma_concept.base/plugin.xmi b/praclib/temp/core.default.uma_concept.base/plugin.xmi
new file mode 100644
index 0000000..7e458bb
--- /dev/null
+++ b/praclib/temp/core.default.uma_concept.base/plugin.xmi
@@ -0,0 +1,411 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_nIcf4fL5Edm6Nvont3uinw"
+ guid="_nIcf4fL5Edm6Nvont3uinw">
+ <resourceDescriptors xmi:id="_nIPrkfL5Edm6Nvont3uinw" id="_6B9_MO8KEdmKSqa_gSYthg"
+ uri="customcategories/obsolete.xmi"/>
+ <resourceDescriptors xmi:id="_b7_AgP1XEdmek8CQTQgrOQ" id="_rgwycf1WEdmek8CQTQgrOQ"
+ uri="customcategories/Custom%20Categories.xmi"/>
+ <resourceDescriptors xmi:id="_xy2SAgIsEdqEutyfYo0quQ" id="_xy2SAQIsEdqEutyfYo0quQ"
+ uri="customcategories/guidance%202.xmi"/>
+ <resourceDescriptors xmi:id="_uDU1ogSEEdq61bDkWg1SXw" id="_uDU1oQSEEdq61bDkWg1SXw"
+ uri="customcategories/method_architecture_fundamentals.xmi"/>
+ <resourceDescriptors xmi:id="_4R4fZfIwEdm7AIOuZcqunQ" id="_x459k9nmEdmO6L4XMImrsA"
+ uri="guidances/termdefinitions/task.xmi"/>
+ <resourceDescriptors xmi:id="_4SQ55vIwEdm7AIOuZcqunQ" id="_x7cUNNnmEdmO6L4XMImrsA"
+ uri="guidances/termdefinitions/artifact.xmi"/>
+ <resourceDescriptors xmi:id="_4Ud5VfIwEdm7AIOuZcqunQ" id="_yFbWodnmEdmO6L4XMImrsA"
+ uri="guidances/termdefinitions/deliverable.xmi"/>
+ <resourceDescriptors xmi:id="_4U2T0vIwEdm7AIOuZcqunQ" id="_yGUuitnmEdmO6L4XMImrsA"
+ uri="guidances/termdefinitions/discipline.xmi"/>
+ <resourceDescriptors xmi:id="_4VChEPIwEdm7AIOuZcqunQ" id="_yHEVYtnmEdmO6L4XMImrsA"
+ uri="guidances/termdefinitions/domain.xmi"/>
+ <resourceDescriptors xmi:id="_4WkLEfIwEdm7AIOuZcqunQ" id="_yK8IydnmEdmO6L4XMImrsA"
+ uri="guidances/termdefinitions/input.xmi"/>
+ <resourceDescriptors xmi:id="_4YSCUPIwEdm7AIOuZcqunQ" id="_yPaZGtnmEdmO6L4XMImrsA"
+ uri="guidances/termdefinitions/output.xmi"/>
+ <resourceDescriptors xmi:id="_4cGLVvIwEdm7AIOuZcqunQ" id="_ycE8HdnmEdmO6L4XMImrsA"
+ uri="guidances/termdefinitions/activity_detail_diagram.xmi"/>
+ <resourceDescriptors xmi:id="_4ZzsVvIwEdm7AIOuZcqunQ" id="_yUefQdnmEdmO6L4XMImrsA"
+ uri="guidances/termdefinitions/role.xmi"/>
+ <resourceDescriptors xmi:id="_4bbc8fIwEdm7AIOuZcqunQ" id="_yYy-mtnmEdmO6L4XMImrsA"
+ uri="guidances/termdefinitions/tool_mentor.xmi"/>
+ <resourceDescriptors xmi:id="_4Yqc1fIwEdm7AIOuZcqunQ" id="_yQ5m2dnmEdmO6L4XMImrsA"
+ uri="guidances/termdefinitions/process.xmi"/>
+ <resourceDescriptors xmi:id="__c1VoBTLEdqrUt4zetC1gg" id="__cpIYBTLEdqrUt4zetC1gg"
+ uri="customcategories/base_concepts_view_building_blocks.xmi"/>
+ <resourceDescriptors xmi:id="_m9DnsBUFEdqrUt4zetC1gg" id="_m83acBUFEdqrUt4zetC1gg"
+ uri="guidances/concepts/method_library.xmi"/>
+ <resourceDescriptors xmi:id="_0LCr8RUFEdqrUt4zetC1gg" id="_0LCr8BUFEdqrUt4zetC1gg"
+ uri="guidances/concepts/method_plugin.xmi"/>
+ <resourceDescriptors xmi:id="_Tp7-8BUKEdqrUt4zetC1gg" id="_TpLJ8BUKEdqrUt4zetC1gg"
+ uri="customcategories/uma_diagrams.xmi"/>
+ <resourceDescriptors xmi:id="_7trfoB_JEdq6CKKKq4D7YA" id="-67u6-WRUmTOB9IdLgQg6aw"
+ uri="guidances/termdefinitions/activity.xmi"/>
+ <resourceDescriptors xmi:id="_i_kKoB_KEdq6CKKKq4D7YA" id="-TI6lqoTE1op3-SnmGa2S9Q"
+ uri="guidances/termdefinitions/descriptor.xmi"/>
+ <resourceDescriptors xmi:id="_BRIPMB_MEdq6CKKKq4D7YA" id="-7pbyO29v0VnsosWHabeZDQ"
+ uri="guidances/termdefinitions/breakdown_element.xmi"/>
+ <resourceDescriptors xmi:id="_t5D8YB_NEdq6CKKKq4D7YA" id="-akU0PqDaad4Ns5MQhVBJ7Q"
+ uri="guidances/termdefinitions/method_content.xmi"/>
+ <resourceDescriptors xmi:id="_vOY7IB_OEdq6CKKKq4D7YA" id="-CTatxBir28UK-VwWwDij-g"
+ uri="guidances/termdefinitions/guidance.xmi"/>
+ <resourceDescriptors xmi:id="_wnDhwB_PEdq6CKKKq4D7YA" id="-QBSZ9hFRr8q6kvRyq1cESQ"
+ uri="guidances/termdefinitions/uma.xmi"/>
+ <resourceDescriptors xmi:id="_dYLAIB_REdq6CKKKq4D7YA" id="-dpUlq7kJXlJBUjvh7lHW7Q"
+ uri="guidances/termdefinitions/breakdown_structure.xmi"/>
+ <resourceDescriptors xmi:id="_SqguIB_SEdq6CKKKq4D7YA" id="-dcYwPivhczonAxeyXweyIQ"
+ uri="guidances/termdefinitions/work_product.xmi"/>
+ <resourceDescriptors xmi:id="_eZBtQB_eEdqAHrsQ7-jSbw" id="-KfXoeGTRnQImE1byTBtryQ"
+ uri="guidances/termdefinitions/step.xmi"/>
+ <resourceDescriptors xmi:id="_mWA1IB_iEdqAHrsQ7-jSbw" id="-SQyJsrOEI73uLZzjRVmSBA"
+ uri="guidances/termdefinitions/outcome.xmi"/>
+ <resourceDescriptors xmi:id="_LzRYcB_xEdq5PKe91GlWMA" id="_TpLJ8BUKEdqrUt4zetC1gg"
+ uri="customcategories/uma_diagrams.xmi"/>
+ <resourceDescriptors xmi:id="_8MLCkCACEdqum6ped11dHA" id="_TpLJ8BUKEdqrUt4zetC1gg"
+ uri="customcategories/uma_diagrams.xmi"/>
+ <resourceDescriptors xmi:id="_2RyqIiO4EdqaNq6Ptg8uyA" id="-IsV3QdyMdwFlqznd4UAYhw"
+ uri="guidances/termdefinitions/delivery_process.xmi"/>
+ <resourceDescriptors xmi:id="_b2aiECO5EdqaNq6Ptg8uyA" id="-AY7-wWpxUmZp4c-odX8e7g"
+ uri="guidances/termdefinitions/capability_pattern.xmi"/>
+ <resourceDescriptors xmi:id="_1Uo8gD_fEdqDFvujd6NHiA" id="-V2B7_NtU_O7-45ldkX0Rrw"
+ uri="guidances/supportingmaterials/about_base_concepts.xmi"/>
+ <resourceDescriptors xmi:id="_3AVlUEALEdqTMtYjAib0og" id="-eyFTMGu83WSs-yJedYCY3g"
+ uri="guidances/supportingmaterials/whats_new_base_concepts.xmi"/>
+ <resourceDescriptors xmi:id="_Hq7agMaEEduMlb2cQZNTYw" id="-d9uOWrjeHbE_1Xu2RIs-0A"
+ uri="guidances/termdefinitions/checklist.xmi"/>
+ <resourceDescriptors xmi:id="_XR3TIMaEEduMlb2cQZNTYw" id="-KNw2PnSSEEogCvg4sj1ebg"
+ uri="guidances/termdefinitions/composite_role.xmi"/>
+ <resourceDescriptors xmi:id="_1su6IMaEEduMlb2cQZNTYw" id="-5bvXXNVzF7mZf0R7Oez5_g"
+ uri="guidances/termdefinitions/concept.xmi"/>
+ <resourceDescriptors xmi:id="_OjgmcMaFEduMlb2cQZNTYw" id="-kzN6-iqn9zDtfnJc7IWkIg"
+ uri="guidances/termdefinitions/method_configuration.xmi"/>
+ <resourceDescriptors xmi:id="_lsCBMMaFEduMlb2cQZNTYw" id="-G9dXZH2IkpWGi4NZK-2vEw"
+ uri="guidances/termdefinitions/custom_category.xmi"/>
+ <resourceDescriptors xmi:id="_sOPxAMaFEduMlb2cQZNTYw" id="-WGi50KpVG9oQbP82Xvk1UA"
+ uri="guidances/termdefinitions/example.xmi"/>
+ <resourceDescriptors xmi:id="_zB_VscaFEduMlb2cQZNTYw" id="-EEF1Y386HZ1XRsyHmGLE3g"
+ uri="guidances/termdefinitions/guideline.xmi"/>
+ <resourceDescriptors xmi:id="_6h6D4MaFEduMlb2cQZNTYw" id="-m6mx-VR4CReQNhrf4b8ykQ"
+ uri="guidances/termdefinitions/method_library.xmi"/>
+ <resourceDescriptors xmi:id="_JEMooMaGEduMlb2cQZNTYw" id="-q0ixH8duU7qb8agEywAFHQ"
+ uri="guidances/termdefinitions/method_plugin.xmi"/>
+ <resourceDescriptors xmi:id="_oC-N8MaGEduMlb2cQZNTYw" id="-88Vj7cM5EcVnfesDYaAkww"
+ uri="guidances/termdefinitions/phase.xmi"/>
+ <resourceDescriptors xmi:id="_2bAqgcaGEduMlb2cQZNTYw" id="-kxtQBsUei9KRl8Z6tOSQ-g"
+ uri="guidances/termdefinitions/practice.xmi"/>
+ <resourceDescriptors xmi:id="_jkh3QcaHEduMlb2cQZNTYw" id="-lEbg0SKqsikKdCRXPVvRmw"
+ uri="guidances/termdefinitions/report.xmi"/>
+ <resourceDescriptors xmi:id="_zUUJ4caHEduMlb2cQZNTYw" id="-H9RSfWhEhOJscNkDKGPcBA"
+ uri="guidances/termdefinitions/reusable_asset.xmi"/>
+ <resourceDescriptors xmi:id="_D5S_IcaIEduMlb2cQZNTYw" id="-gCtPvpHU3vmCQKQ1ymqBvw"
+ uri="guidances/termdefinitions/roadmap.xmi"/>
+ <resourceDescriptors xmi:id="_PS1DMMaIEduMlb2cQZNTYw" id="-gOXu6EqfZHMmtekNk8IDqA"
+ uri="guidances/termdefinitions/role_set.xmi"/>
+ <resourceDescriptors xmi:id="_pL22sMaIEduMlb2cQZNTYw" id="-_-iQ4eQyiQVM7YhXcb90-g"
+ uri="guidances/termdefinitions/supporting_material.xmi"/>
+ <resourceDescriptors xmi:id="_vwNUgMaIEduMlb2cQZNTYw" id="-0cxbeJahkc1eqGKztRpcPw"
+ uri="guidances/termdefinitions/team_profile.xmi"/>
+ <resourceDescriptors xmi:id="_45GysMaIEduMlb2cQZNTYw" id="--SOXfR7BTPs3CqtNP8R6Rw"
+ uri="guidances/termdefinitions/template.xmi"/>
+ <resourceDescriptors xmi:id="__wfhQMaIEduMlb2cQZNTYw" id="-4JztP2JNqE36rtSC0UoYDw"
+ uri="guidances/termdefinitions/term_definition.xmi"/>
+ <resourceDescriptors xmi:id="_ERlt4caJEduMlb2cQZNTYw" id="-XnXEM7GkN21zwj7pKPmu3A"
+ uri="guidances/termdefinitions/tool.xmi"/>
+ <resourceDescriptors xmi:id="_JK7bYcaJEduMlb2cQZNTYw" id="-dLRBfqnBlgy_0_H13LmV3A"
+ uri="guidances/termdefinitions/view.xmi"/>
+ <resourceDescriptors xmi:id="_OekfQcaJEduMlb2cQZNTYw" id="-QLPRVsXtlVpWZiWmQPSsnw"
+ uri="guidances/termdefinitions/white_paper.xmi"/>
+ <resourceDescriptors xmi:id="_hXmawcaJEduMlb2cQZNTYw" id="-on4oCT1DzfksdshYPKAqGg"
+ uri="guidances/termdefinitions/work_product_kind.xmi"/>
+ <resourceDescriptors xmi:id="_4kE9MKNbEdyMFYhoCpD11Q" id="-uMQBRmGsu_0DumDeidK1ig"
+ uri="guidances/termdefinitions/assists.xmi"/>
+ <resourceDescriptors xmi:id="_4KxP4aNcEdyMFYhoCpD11Q" id="-JldA7oTinGpXvoc3Tj-3JQ"
+ uri="guidances/termdefinitions/discipline_grouping.xmi"/>
+ <resourceDescriptors xmi:id="_4K7A4KNcEdyMFYhoCpD11Q" id="-uIAjd6ptx9yCso_AZSbTUw"
+ uri="guidances/termdefinitions/estimation_considerations.xmi"/>
+ <resourceDescriptors xmi:id="_JyOZUaNeEdyMFYhoCpD11Q" id="-EF5eqKSqgTApRj_uXeG39w"
+ uri="guidances/termdefinitions/performer.xmi"/>
+ <resourceDescriptors xmi:id="_J0554aNeEdyMFYhoCpD11Q" id="-kbyERT7ThI5QD4X7GME9pQ"
+ uri="guidances/termdefinitions/method_architecture.xmi"/>
+ <resourceDescriptors xmi:id="_J2_kkKNeEdyMFYhoCpD11Q" id="-FxDDt6uNV4K2c04hoFKBpQ"
+ uri="guidances/termdefinitions/iteration.xmi"/>
+ <resourceDescriptors xmi:id="_Nwd7EaNfEdyMFYhoCpD11Q" id="-0K7iy91rKIS0h8kZfVgBvg"
+ uri="guidances/termdefinitions/role_set_grouping.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_WCUhAO8KEdmKSqa_gSYthg" name="core.default.uma_concept.base"
+ guid="_WCUhAO8KEdmKSqa_gSYthg" briefDescription="This plug-in contains basic concepts necessary to use the method composition tooling."
+ authors="IBM Rational" changeDate="2008-01-31T00:28:56.013-0500" changeDescription="This plug-in was base_concepts.|Simplified to just contain term definitions related to UMA."
+ version="1.0.1">
+ <copyrightStatement href="uma://_iVydgENdEdy245g62lfWcA#_uuunoPsDEdmyhNQr5STrZQ"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_WCanoO8KEdmKSqa_gSYthg"
+ name="Content" guid="_WCanoO8KEdmKSqa_gSYthg">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_WCguQO8KEdmKSqa_gSYthg"
+ name="Categories" guid="_WCguQO8KEdmKSqa_gSYthg">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_WCguQe8KEdmKSqa_gSYthg"
+ name="Domains" guid="_WCguQe8KEdmKSqa_gSYthg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_WCguQu8KEdmKSqa_gSYthg"
+ name="Disciplines" guid="_WCguQu8KEdmKSqa_gSYthg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_WCguQ-8KEdmKSqa_gSYthg"
+ name="RoleSets" guid="_WCguQ-8KEdmKSqa_gSYthg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_WCguRO8KEdmKSqa_gSYthg"
+ name="WP Types" guid="_WCguRO8KEdmKSqa_gSYthg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_WCguRe8KEdmKSqa_gSYthg"
+ name="Tools" guid="_WCguRe8KEdmKSqa_gSYthg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_WCguRu8KEdmKSqa_gSYthg"
+ name="StandardCategories" guid="_WCguRu8KEdmKSqa_gSYthg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_WCguR-8KEdmKSqa_gSYthg"
+ name="CustomCategories" guid="_WCguR-8KEdmKSqa_gSYthg">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_WCguSO8KEdmKSqa_gSYthg"
+ name="Hidden" guid="_WCguSO8KEdmKSqa_gSYthg">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_WCguSe8KEdmKSqa_gSYthg"
+ name="Custom Categories" guid="_WCguSe8KEdmKSqa_gSYthg" presentationName="Custom Categories"/>
+ </childPackages>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_WCguSu8KEdmKSqa_gSYthg"
+ name="CoreContent" guid="_WCguSu8KEdmKSqa_gSYthg">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_eNnSAO8LEdmKSqa_gSYthg"
+ name="UMA end-user glossary definitions" guid="_eNnSAO8LEdmKSqa_gSYthg"
+ briefDescription="This Content package concepts and other general guidance related to UMA and related tooling.">
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_x459ktnmEdmO6L4XMImrsA"
+ name="task" guid="_x459ktnmEdmO6L4XMImrsA" presentationName="task">
+ <presentation xmi:id="_x459k9nmEdmO6L4XMImrsA" href="uma://_x459k9nmEdmO6L4XMImrsA#_x459k9nmEdmO6L4XMImrsA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_x7cUM9nmEdmO6L4XMImrsA"
+ name="artifact" guid="_x7cUM9nmEdmO6L4XMImrsA" presentationName="artifact">
+ <presentation xmi:id="_x7cUNNnmEdmO6L4XMImrsA" href="uma://_x7cUNNnmEdmO6L4XMImrsA#_x7cUNNnmEdmO6L4XMImrsA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_yFbWoNnmEdmO6L4XMImrsA"
+ name="deliverable" guid="_yFbWoNnmEdmO6L4XMImrsA" presentationName="deliverable">
+ <presentation xmi:id="_yFbWodnmEdmO6L4XMImrsA" href="uma://_yFbWodnmEdmO6L4XMImrsA#_yFbWodnmEdmO6L4XMImrsA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_yGUuidnmEdmO6L4XMImrsA"
+ name="discipline" guid="_yGUuidnmEdmO6L4XMImrsA" presentationName="discipline">
+ <presentation xmi:id="_yGUuitnmEdmO6L4XMImrsA" href="uma://_yGUuitnmEdmO6L4XMImrsA#_yGUuitnmEdmO6L4XMImrsA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_yHEVYdnmEdmO6L4XMImrsA"
+ name="domain" guid="_yHEVYdnmEdmO6L4XMImrsA" presentationName="domain">
+ <presentation xmi:id="_yHEVYtnmEdmO6L4XMImrsA" href="uma://_yHEVYtnmEdmO6L4XMImrsA#_yHEVYtnmEdmO6L4XMImrsA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_yK8IyNnmEdmO6L4XMImrsA"
+ name="input" guid="_yK8IyNnmEdmO6L4XMImrsA" presentationName="input">
+ <presentation xmi:id="_yK8IydnmEdmO6L4XMImrsA" href="uma://_yK8IydnmEdmO6L4XMImrsA#_yK8IydnmEdmO6L4XMImrsA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_yPaZGdnmEdmO6L4XMImrsA"
+ name="output" guid="_yPaZGdnmEdmO6L4XMImrsA" presentationName="output">
+ <presentation xmi:id="_yPaZGtnmEdmO6L4XMImrsA" href="uma://_yPaZGtnmEdmO6L4XMImrsA#_yPaZGtnmEdmO6L4XMImrsA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_ycE8HNnmEdmO6L4XMImrsA"
+ name="activity_detail_diagram" guid="_ycE8HNnmEdmO6L4XMImrsA" presentationName="activity detail diagram">
+ <presentation xmi:id="_ycE8HdnmEdmO6L4XMImrsA" href="uma://_ycE8HdnmEdmO6L4XMImrsA#_ycE8HdnmEdmO6L4XMImrsA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_yUefQNnmEdmO6L4XMImrsA"
+ name="role" guid="_yUefQNnmEdmO6L4XMImrsA" presentationName="role">
+ <presentation xmi:id="_yUefQdnmEdmO6L4XMImrsA" href="uma://_yUefQdnmEdmO6L4XMImrsA#_yUefQdnmEdmO6L4XMImrsA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_yYy-mdnmEdmO6L4XMImrsA"
+ name="tool_mentor" guid="_yYy-mdnmEdmO6L4XMImrsA" presentationName="tool mentor">
+ <presentation xmi:id="_yYy-mtnmEdmO6L4XMImrsA" href="uma://_yYy-mtnmEdmO6L4XMImrsA#_yYy-mtnmEdmO6L4XMImrsA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_yQ5m2NnmEdmO6L4XMImrsA"
+ name="process" guid="_yQ5m2NnmEdmO6L4XMImrsA" presentationName="process">
+ <presentation xmi:id="_yQ5m2dnmEdmO6L4XMImrsA" href="uma://_yQ5m2dnmEdmO6L4XMImrsA#_yQ5m2dnmEdmO6L4XMImrsA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_yoVhMB_IEdq6CKKKq4D7YA"
+ name="activity" guid="_yoVhMB_IEdq6CKKKq4D7YA" presentationName="activity">
+ <presentation xmi:id="-67u6-WRUmTOB9IdLgQg6aw" href="uma://-67u6-WRUmTOB9IdLgQg6aw#-67u6-WRUmTOB9IdLgQg6aw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_7rS6AB_JEdq6CKKKq4D7YA"
+ name="descriptor" guid="_7rS6AB_JEdq6CKKKq4D7YA" presentationName="descriptor">
+ <presentation xmi:id="-TI6lqoTE1op3-SnmGa2S9Q" href="uma://-TI6lqoTE1op3-SnmGa2S9Q#-TI6lqoTE1op3-SnmGa2S9Q"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_cvdpEB_LEdq6CKKKq4D7YA"
+ name="breakdown_element" guid="_cvdpEB_LEdq6CKKKq4D7YA" presentationName="breakdown element">
+ <presentation xmi:id="-7pbyO29v0VnsosWHabeZDQ" href="uma://-7pbyO29v0VnsosWHabeZDQ#-7pbyO29v0VnsosWHabeZDQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_Ts2joB_MEdq6CKKKq4D7YA"
+ name="method_content" guid="_Ts2joB_MEdq6CKKKq4D7YA" presentationName="method content">
+ <presentation xmi:id="-akU0PqDaad4Ns5MQhVBJ7Q" href="uma://-akU0PqDaad4Ns5MQhVBJ7Q#-akU0PqDaad4Ns5MQhVBJ7Q"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_83ttAB_NEdq6CKKKq4D7YA"
+ name="guidance" guid="_83ttAB_NEdq6CKKKq4D7YA" presentationName="guidance">
+ <presentation xmi:id="-CTatxBir28UK-VwWwDij-g" href="uma://-CTatxBir28UK-VwWwDij-g#-CTatxBir28UK-VwWwDij-g"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_cj6jkB_PEdq6CKKKq4D7YA"
+ name="uma" guid="_cj6jkB_PEdq6CKKKq4D7YA" presentationName="UMA">
+ <presentation xmi:id="-QBSZ9hFRr8q6kvRyq1cESQ" href="uma://-QBSZ9hFRr8q6kvRyq1cESQ#-QBSZ9hFRr8q6kvRyq1cESQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_95LCoB_QEdq6CKKKq4D7YA"
+ name="breakdown_structure" guid="_95LCoB_QEdq6CKKKq4D7YA" presentationName="breakdown structure">
+ <presentation xmi:id="-dpUlq7kJXlJBUjvh7lHW7Q" href="uma://-dpUlq7kJXlJBUjvh7lHW7Q#-dpUlq7kJXlJBUjvh7lHW7Q"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_H4JXwB_SEdq6CKKKq4D7YA"
+ name="work_product" guid="_H4JXwB_SEdq6CKKKq4D7YA" presentationName="work product">
+ <presentation xmi:id="-dcYwPivhczonAxeyXweyIQ" href="uma://-dcYwPivhczonAxeyXweyIQ#-dcYwPivhczonAxeyXweyIQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_BqZloB_eEdqAHrsQ7-jSbw"
+ name="step" guid="_BqZloB_eEdqAHrsQ7-jSbw" presentationName="step">
+ <presentation xmi:id="-KfXoeGTRnQImE1byTBtryQ" href="uma://-KfXoeGTRnQImE1byTBtryQ#-KfXoeGTRnQImE1byTBtryQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_LNAAcB_iEdqAHrsQ7-jSbw"
+ name="outcome" guid="_LNAAcB_iEdqAHrsQ7-jSbw" presentationName="outcome">
+ <presentation xmi:id="-SQyJsrOEI73uLZzjRVmSBA" href="uma://-SQyJsrOEI73uLZzjRVmSBA#-SQyJsrOEI73uLZzjRVmSBA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_ZufeMCO3EdqaNq6Ptg8uyA"
+ name="delivery_process" guid="_ZufeMCO3EdqaNq6Ptg8uyA" presentationName="delivery process">
+ <presentation xmi:id="-IsV3QdyMdwFlqznd4UAYhw" href="uma://-IsV3QdyMdwFlqznd4UAYhw#-IsV3QdyMdwFlqznd4UAYhw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_2RUJACO4EdqaNq6Ptg8uyA"
+ name="capability_pattern" guid="_2RUJACO4EdqaNq6Ptg8uyA" presentationName="capability pattern">
+ <presentation xmi:id="-AY7-wWpxUmZp4c-odX8e7g" href="uma://-AY7-wWpxUmZp4c-odX8e7g#-AY7-wWpxUmZp4c-odX8e7g"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_7vpJsMaCEduMlb2cQZNTYw"
+ name="checklist" guid="_7vpJsMaCEduMlb2cQZNTYw" presentationName="checklist">
+ <presentation xmi:id="-d9uOWrjeHbE_1Xu2RIs-0A" href="uma://-d9uOWrjeHbE_1Xu2RIs-0A#-d9uOWrjeHbE_1Xu2RIs-0A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_PzL7EMaEEduMlb2cQZNTYw"
+ name="composite_role" guid="_PzL7EMaEEduMlb2cQZNTYw" presentationName="composite role">
+ <presentation xmi:id="-KNw2PnSSEEogCvg4sj1ebg" href="uma://-KNw2PnSSEEogCvg4sj1ebg#-KNw2PnSSEEogCvg4sj1ebg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_wMchYMaEEduMlb2cQZNTYw"
+ name="concept" guid="_wMchYMaEEduMlb2cQZNTYw" presentationName="concept">
+ <presentation xmi:id="-5bvXXNVzF7mZf0R7Oez5_g" href="uma://-5bvXXNVzF7mZf0R7Oez5_g#-5bvXXNVzF7mZf0R7Oez5_g"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="__V7pAMaEEduMlb2cQZNTYw"
+ name="method_configuration" guid="__V7pAMaEEduMlb2cQZNTYw" presentationName="method configuration">
+ <presentation xmi:id="-kzN6-iqn9zDtfnJc7IWkIg" href="uma://-kzN6-iqn9zDtfnJc7IWkIg#-kzN6-iqn9zDtfnJc7IWkIg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_eqw94MaFEduMlb2cQZNTYw"
+ name="custom_category" guid="_eqw94MaFEduMlb2cQZNTYw" presentationName="custom category">
+ <presentation xmi:id="-G9dXZH2IkpWGi4NZK-2vEw" href="uma://-G9dXZH2IkpWGi4NZK-2vEw#-G9dXZH2IkpWGi4NZK-2vEw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_nE6fsMaFEduMlb2cQZNTYw"
+ name="example" guid="_nE6fsMaFEduMlb2cQZNTYw" presentationName="example">
+ <presentation xmi:id="-WGi50KpVG9oQbP82Xvk1UA" href="uma://-WGi50KpVG9oQbP82Xvk1UA#-WGi50KpVG9oQbP82Xvk1UA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_uK8HMMaFEduMlb2cQZNTYw"
+ name="guideline" guid="_uK8HMMaFEduMlb2cQZNTYw" presentationName="guideline">
+ <presentation xmi:id="-EEF1Y386HZ1XRsyHmGLE3g" href="uma://-EEF1Y386HZ1XRsyHmGLE3g#-EEF1Y386HZ1XRsyHmGLE3g"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_1xELEMaFEduMlb2cQZNTYw"
+ name="method_library" guid="_1xELEMaFEduMlb2cQZNTYw" presentationName="method library">
+ <presentation xmi:id="-m6mx-VR4CReQNhrf4b8ykQ" href="uma://-m6mx-VR4CReQNhrf4b8ykQ#-m6mx-VR4CReQNhrf4b8ykQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_D4TLgMaGEduMlb2cQZNTYw"
+ name="method_plugin" guid="_D4TLgMaGEduMlb2cQZNTYw" presentationName="method plug-in">
+ <presentation xmi:id="-q0ixH8duU7qb8agEywAFHQ" href="uma://-q0ixH8duU7qb8agEywAFHQ#-q0ixH8duU7qb8agEywAFHQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_K9eecMaGEduMlb2cQZNTYw"
+ name="phase" guid="_K9eecMaGEduMlb2cQZNTYw" presentationName="phase">
+ <presentation xmi:id="-88Vj7cM5EcVnfesDYaAkww" href="uma://-88Vj7cM5EcVnfesDYaAkww#-88Vj7cM5EcVnfesDYaAkww"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_wxYvkMaGEduMlb2cQZNTYw"
+ name="practice" guid="_wxYvkMaGEduMlb2cQZNTYw" presentationName="practice">
+ <presentation xmi:id="-kxtQBsUei9KRl8Z6tOSQ-g" href="uma://-kxtQBsUei9KRl8Z6tOSQ-g#-kxtQBsUei9KRl8Z6tOSQ-g"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_bDCXUMaHEduMlb2cQZNTYw"
+ name="report" guid="_bDCXUMaHEduMlb2cQZNTYw" presentationName="report">
+ <presentation xmi:id="-lEbg0SKqsikKdCRXPVvRmw" href="uma://-lEbg0SKqsikKdCRXPVvRmw#-lEbg0SKqsikKdCRXPVvRmw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_kSKZUMaHEduMlb2cQZNTYw"
+ name="reusable_asset" guid="_kSKZUMaHEduMlb2cQZNTYw" presentationName="reusable asset">
+ <presentation xmi:id="-H9RSfWhEhOJscNkDKGPcBA" href="uma://-H9RSfWhEhOJscNkDKGPcBA#-H9RSfWhEhOJscNkDKGPcBA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_19dWYMaHEduMlb2cQZNTYw"
+ name="roadmap" guid="_19dWYMaHEduMlb2cQZNTYw" presentationName="roadmap">
+ <presentation xmi:id="-gCtPvpHU3vmCQKQ1ymqBvw" href="uma://-gCtPvpHU3vmCQKQ1ymqBvw#-gCtPvpHU3vmCQKQ1ymqBvw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_Fs8HAMaIEduMlb2cQZNTYw"
+ name="role_set" guid="_Fs8HAMaIEduMlb2cQZNTYw" presentationName="role set">
+ <presentation xmi:id="-gOXu6EqfZHMmtekNk8IDqA" href="uma://-gOXu6EqfZHMmtekNk8IDqA#-gOXu6EqfZHMmtekNk8IDqA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_SwvUgMaIEduMlb2cQZNTYw"
+ name="supporting_material" guid="_SwvUgMaIEduMlb2cQZNTYw" presentationName="supporting material">
+ <presentation xmi:id="-_-iQ4eQyiQVM7YhXcb90-g" href="uma://-_-iQ4eQyiQVM7YhXcb90-g#-_-iQ4eQyiQVM7YhXcb90-g"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_rZOGIMaIEduMlb2cQZNTYw"
+ name="team_profile" guid="_rZOGIMaIEduMlb2cQZNTYw" presentationName="team profile">
+ <presentation xmi:id="-0cxbeJahkc1eqGKztRpcPw" href="uma://-0cxbeJahkc1eqGKztRpcPw#-0cxbeJahkc1eqGKztRpcPw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_1MLN8MaIEduMlb2cQZNTYw"
+ name="template" guid="_1MLN8MaIEduMlb2cQZNTYw" presentationName="template">
+ <presentation xmi:id="--SOXfR7BTPs3CqtNP8R6Rw" href="uma://--SOXfR7BTPs3CqtNP8R6Rw#--SOXfR7BTPs3CqtNP8R6Rw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_6SluIMaIEduMlb2cQZNTYw"
+ name="term_definition" guid="_6SluIMaIEduMlb2cQZNTYw" presentationName="term definition">
+ <presentation xmi:id="-4JztP2JNqE36rtSC0UoYDw" href="uma://-4JztP2JNqE36rtSC0UoYDw#-4JztP2JNqE36rtSC0UoYDw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_BangwMaJEduMlb2cQZNTYw"
+ name="tool" guid="_BangwMaJEduMlb2cQZNTYw" presentationName="tool">
+ <presentation xmi:id="-XnXEM7GkN21zwj7pKPmu3A" href="uma://-XnXEM7GkN21zwj7pKPmu3A#-XnXEM7GkN21zwj7pKPmu3A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_GH6WUMaJEduMlb2cQZNTYw"
+ name="view" guid="_GH6WUMaJEduMlb2cQZNTYw" presentationName="view">
+ <presentation xmi:id="-dLRBfqnBlgy_0_H13LmV3A" href="uma://-dLRBfqnBlgy_0_H13LmV3A#-dLRBfqnBlgy_0_H13LmV3A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_Kc1IIMaJEduMlb2cQZNTYw"
+ name="white_paper" guid="_Kc1IIMaJEduMlb2cQZNTYw" presentationName="white paper">
+ <presentation xmi:id="-QLPRVsXtlVpWZiWmQPSsnw" href="uma://-QLPRVsXtlVpWZiWmQPSsnw#-QLPRVsXtlVpWZiWmQPSsnw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_QWhfYMaJEduMlb2cQZNTYw"
+ name="work_product_kind" guid="_QWhfYMaJEduMlb2cQZNTYw" presentationName="work product kind">
+ <presentation xmi:id="-on4oCT1DzfksdshYPKAqGg" href="uma://-on4oCT1DzfksdshYPKAqGg#-on4oCT1DzfksdshYPKAqGg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_2AKO8KNbEdyMFYhoCpD11Q"
+ name="assists" guid="_2AKO8KNbEdyMFYhoCpD11Q" presentationName="assists">
+ <presentation xmi:id="-uMQBRmGsu_0DumDeidK1ig" href="uma://-uMQBRmGsu_0DumDeidK1ig#-uMQBRmGsu_0DumDeidK1ig"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_V5LO8KNcEdyMFYhoCpD11Q"
+ name="discipline_grouping" guid="_V5LO8KNcEdyMFYhoCpD11Q" presentationName="discipline grouping">
+ <presentation xmi:id="-JldA7oTinGpXvoc3Tj-3JQ" href="uma://-JldA7oTinGpXvoc3Tj-3JQ#-JldA7oTinGpXvoc3Tj-3JQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_cSEDoKNcEdyMFYhoCpD11Q"
+ name="estimation_considerations" guid="_cSEDoKNcEdyMFYhoCpD11Q" presentationName="estimation considerations">
+ <presentation xmi:id="-uIAjd6ptx9yCso_AZSbTUw" href="uma://-uIAjd6ptx9yCso_AZSbTUw#-uIAjd6ptx9yCso_AZSbTUw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_5vWoEKNcEdyMFYhoCpD11Q"
+ name="iteration" guid="_5vWoEKNcEdyMFYhoCpD11Q" presentationName="iteration">
+ <presentation xmi:id="-FxDDt6uNV4K2c04hoFKBpQ" href="uma://-FxDDt6uNV4K2c04hoFKBpQ#-FxDDt6uNV4K2c04hoFKBpQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_A6we0KNdEdyMFYhoCpD11Q"
+ name="method_architecture" guid="_A6we0KNdEdyMFYhoCpD11Q" presentationName="method architecture">
+ <presentation xmi:id="-kbyERT7ThI5QD4X7GME9pQ" href="uma://-kbyERT7ThI5QD4X7GME9pQ#-kbyERT7ThI5QD4X7GME9pQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_GL2vkKNeEdyMFYhoCpD11Q"
+ name="performer" guid="_GL2vkKNeEdyMFYhoCpD11Q" presentationName="performer">
+ <presentation xmi:id="-EF5eqKSqgTApRj_uXeG39w" href="uma://-EF5eqKSqgTApRj_uXeG39w#-EF5eqKSqgTApRj_uXeG39w"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_D8F28KNfEdyMFYhoCpD11Q"
+ name="role_set_grouping" guid="_D8F28KNfEdyMFYhoCpD11Q" presentationName="role set grouping">
+ <presentation xmi:id="-0K7iy91rKIS0h8kZfVgBvg" href="uma://-0K7iy91rKIS0h8kZfVgBvg#-0K7iy91rKIS0h8kZfVgBvg"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_bJKXUKNbEdyMFYhoCpD11Q"
+ name="Plug-in Information" guid="_bJKXUKNbEdyMFYhoCpD11Q">
+ <contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="_uvje4D_fEdqDFvujd6NHiA"
+ name="about_base_concepts" guid="_uvje4D_fEdqDFvujd6NHiA" presentationName="About Base Concepts"
+ nodeicon="guidances/supportingmaterials/resources/about.gif">
+ <presentation xmi:id="-V2B7_NtU_O7-45ldkX0Rrw" href="uma://-V2B7_NtU_O7-45ldkX0Rrw#-V2B7_NtU_O7-45ldkX0Rrw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="_qxY8MEALEdqTMtYjAib0og"
+ name="whats_new_base_concepts" guid="_qxY8MEALEdqTMtYjAib0og" presentationName="What's New in Base Concepts"
+ nodeicon="guidances/supportingmaterials/resources/whats_new.gif">
+ <presentation xmi:id="-eyFTMGu83WSs-yJedYCY3g" href="uma://-eyFTMGu83WSs-yJedYCY3g#-eyFTMGu83WSs-yJedYCY3g"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_WCguS-8KEdmKSqa_gSYthg"
+ name="CapabilityPatterns" guid="_WCguS-8KEdmKSqa_gSYthg"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_WCguTO8KEdmKSqa_gSYthg"
+ name="DeliveryProcesses" guid="_WCguTO8KEdmKSqa_gSYthg"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_WCguTe8KEdmKSqa_gSYthg"
+ name="ProcessContributions" guid="_WCguTe8KEdmKSqa_gSYthg"/>
+ <bases href="uma://_iVydgENdEdy245g62lfWcA#_iVydgENdEdy245g62lfWcA"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/core.gen.common.assign/.project b/praclib/temp/core.gen.common.assign/.project
new file mode 100644
index 0000000..1f051de
--- /dev/null
+++ b/praclib/temp/core.gen.common.assign/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>core.gen.common.assign</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/core.gen.common.assign/plugin.xmi b/praclib/temp/core.gen.common.assign/plugin.xmi
new file mode 100644
index 0000000..3f3a375
--- /dev/null
+++ b/praclib/temp/core.gen.common.assign/plugin.xmi
@@ -0,0 +1,65 @@
+<?xml version="1.0" encoding="UTF-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.4/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.2.0" xmlns:epf="http://www.eclipse.org/epf"
+ epf:version="1.2.0">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_141UsM3pEdyuBO4ZIzcyig"
+ guid="_141UsM3pEdyuBO4ZIzcyig"/>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_14Ft0M3pEdyuBO4ZIzcyig" name="core.gen.common.assign"
+ guid="_14Ft0M3pEdyuBO4ZIzcyig">
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_14Ft0c3pEdyuBO4ZIzcyig"
+ name="Content" guid="_14Ft0c3pEdyuBO4ZIzcyig">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_14Ft0s3pEdyuBO4ZIzcyig"
+ name="Categories" guid="_14Ft0s3pEdyuBO4ZIzcyig">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_14Ft083pEdyuBO4ZIzcyig"
+ name="Domains" guid="_14Ft083pEdyuBO4ZIzcyig">
+ <contentElements xsi:type="org.eclipse.epf.uma:Domain" xmi:id="_0Uvy4M6FEdyndOCfdhe9bw"
+ name="requirements_domain.assign" guid="_0Uvy4M6FEdyndOCfdhe9bw" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Domain" href="uma://_MRPloEFXEdy9ENCpSugIjA#_AIcLUK81Edy9cPK11VzBuQ"/>
+ <workProducts xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_Wn7HcNcEEdqz_d2XWoVt6Q"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_14Ft1M3pEdyuBO4ZIzcyig"
+ name="Disciplines" guid="_14Ft1M3pEdyuBO4ZIzcyig"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_14Ft1c3pEdyuBO4ZIzcyig"
+ name="RoleSets" guid="_14Ft1c3pEdyuBO4ZIzcyig"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_14Ft1s3pEdyuBO4ZIzcyig"
+ name="WP Types" guid="_14Ft1s3pEdyuBO4ZIzcyig"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_14Ft183pEdyuBO4ZIzcyig"
+ name="Tools" guid="_14Ft183pEdyuBO4ZIzcyig"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_14Ft2M3pEdyuBO4ZIzcyig"
+ name="StandardCategories" guid="_14Ft2M3pEdyuBO4ZIzcyig"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_14Ft2c3pEdyuBO4ZIzcyig"
+ name="CustomCategories" guid="_14Ft2c3pEdyuBO4ZIzcyig">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_14Ft2s3pEdyuBO4ZIzcyig"
+ name="Hidden" guid="_14Ft2s3pEdyuBO4ZIzcyig">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_14Ft283pEdyuBO4ZIzcyig"
+ name="Custom Categories" guid="_14Ft283pEdyuBO4ZIzcyig"/>
+ </childPackages>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_14Ft3M3pEdyuBO4ZIzcyig"
+ name="CoreContent" guid="_14Ft3M3pEdyuBO4ZIzcyig">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_s1yG8M6FEdyndOCfdhe9bw"
+ name="Roles Assignment" guid="_s1yG8M6FEdyndOCfdhe9bw">
+ <contentElements xsi:type="org.eclipse.epf.uma:Role" xmi:id="_YoFH8MrqEdyWBb8urvOpEA"
+ name="analyst.assign" guid="_YoFH8MrqEdyWBb8urvOpEA" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Role" href="uma://_A118oMYaEdyXeo04os5BOw#_0VxJsMlgEdmt3adZL5Dmdw"/>
+ <responsibleFor xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_Wn7HcNcEEdqz_d2XWoVt6Q"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_14Ft3c3pEdyuBO4ZIzcyig"
+ name="CapabilityPatterns" guid="_14Ft3c3pEdyuBO4ZIzcyig"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_14Ft3s3pEdyuBO4ZIzcyig"
+ name="DeliveryProcesses" guid="_14Ft3s3pEdyuBO4ZIzcyig"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_14Ft383pEdyuBO4ZIzcyig"
+ name="ProcessContributions" guid="_14Ft383pEdyuBO4ZIzcyig"/>
+ <bases href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPloEFXEdy9ENCpSugIjA"/>
+ <bases href="uma://_A118oMYaEdyXeo04os5BOw#_A118oMYaEdyXeo04os5BOw"/>
+ <bases href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-gEMXEdyP_Jn83ylwUQ"/>
+ <bases href="uma://_iVydgENdEdy245g62lfWcA#_iVydgENdEdy245g62lfWcA"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/core.gen.common.base/.project b/praclib/temp/core.gen.common.base/.project
new file mode 100644
index 0000000..d931511
--- /dev/null
+++ b/praclib/temp/core.gen.common.base/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>core.gen.common.base</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/core.gen.common.base/plugin.xmi b/praclib/temp/core.gen.common.base/plugin.xmi
new file mode 100644
index 0000000..3b58f66
--- /dev/null
+++ b/praclib/temp/core.gen.common.base/plugin.xmi
@@ -0,0 +1,69 @@
+<?xml version="1.0" encoding="UTF-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.4/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.2.0" xmlns:epf="http://www.eclipse.org/epf"
+ epf:version="1.2.0">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_jjLggUMXEdyP_Jn83ylwUQ"
+ guid="_jjLggUMXEdyP_Jn83ylwUQ">
+ <resourceDescriptors xmi:id="_VyNPIOz3Edq2wJOsmRwmhg" id="-iOn7_gfX_iELWRNGJ2JKPQ"
+ uri="workproducts/glossary.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_ji3-gEMXEdyP_Jn83ylwUQ" name="core.gen.common.base"
+ guid="_ji3-gEMXEdyP_Jn83ylwUQ" changeDate="2008-02-11T16:00:03.921-0500">
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_ji3-gUMXEdyP_Jn83ylwUQ"
+ name="Content" guid="_ji3-gUMXEdyP_Jn83ylwUQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_ji3-gkMXEdyP_Jn83ylwUQ"
+ name="Categories" guid="_ji3-gkMXEdyP_Jn83ylwUQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_ji3-g0MXEdyP_Jn83ylwUQ"
+ name="Domains" guid="_ji3-g0MXEdyP_Jn83ylwUQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_ji3-hEMXEdyP_Jn83ylwUQ"
+ name="Disciplines" guid="_ji3-hEMXEdyP_Jn83ylwUQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_ji3-hUMXEdyP_Jn83ylwUQ"
+ name="RoleSets" guid="_ji3-hUMXEdyP_Jn83ylwUQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_ji3-hkMXEdyP_Jn83ylwUQ"
+ name="WP Types" guid="_ji3-hkMXEdyP_Jn83ylwUQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_ji3-h0MXEdyP_Jn83ylwUQ"
+ name="Tools" guid="_ji3-h0MXEdyP_Jn83ylwUQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_ji3-iEMXEdyP_Jn83ylwUQ"
+ name="StandardCategories" guid="_ji3-iEMXEdyP_Jn83ylwUQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_ji3-iUMXEdyP_Jn83ylwUQ"
+ name="CustomCategories" guid="_ji3-iUMXEdyP_Jn83ylwUQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_ji3-ikMXEdyP_Jn83ylwUQ"
+ name="Hidden" guid="_ji3-ikMXEdyP_Jn83ylwUQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_ji3-i0MXEdyP_Jn83ylwUQ"
+ name="Custom Categories" guid="_ji3-i0MXEdyP_Jn83ylwUQ" categorizedElements="_wcncwNjjEdyAi9EWyDeJBg"/>
+ </childPackages>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_wcncwNjjEdyAi9EWyDeJBg"
+ name="contributions_to_nav_building_blocks" guid="_wcncwNjjEdyAi9EWyDeJBg"
+ presentationName="Contributions to Navigation Building Blocks" categorizedElements="_V1APgNjkEdyAi9EWyDeJBg"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_V1APgNjkEdyAi9EWyDeJBg"
+ name="artifact_list.assign" guid="_V1APgNjkEdyAi9EWyDeJBg" variabilityType="contributes"
+ categorizedElements="_Wn7HcNcEEdqz_d2XWoVt6Q">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4YMRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_ji3-jEMXEdyP_Jn83ylwUQ"
+ name="CoreContent" guid="_ji3-jEMXEdyP_Jn83ylwUQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_r7UQIEMXEdyP_Jn83ylwUQ"
+ name="General Work Products" guid="_r7UQIEMXEdyP_Jn83ylwUQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_Wn7HcNcEEdqz_d2XWoVt6Q"
+ name="glossary" guid="_Wn7HcNcEEdqz_d2XWoVt6Q" briefDescription="This artifact defines important terms used by the project. The collection of terms clarifies the vocabulary used on the project."
+ presentationName="Glossary">
+ <presentation xmi:id="-iOn7_gfX_iELWRNGJ2JKPQ" href="uma://-iOn7_gfX_iELWRNGJ2JKPQ#-iOn7_gfX_iELWRNGJ2JKPQ"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_ji3-jUMXEdyP_Jn83ylwUQ"
+ name="CapabilityPatterns" guid="_ji3-jUMXEdyP_Jn83ylwUQ"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_ji3-jkMXEdyP_Jn83ylwUQ"
+ name="DeliveryProcesses" guid="_ji3-jkMXEdyP_Jn83ylwUQ"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_ji3-j0MXEdyP_Jn83ylwUQ"
+ name="ProcessContributions" guid="_ji3-j0MXEdyP_Jn83ylwUQ"/>
+ <bases href="uma://_iVydgENdEdy245g62lfWcA#_iVydgENdEdy245g62lfWcA"/>
+ <bases href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno4EKmEdyrauqpmnA8jQ"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/core.gen.common.base/workproducts/glossary.xmi b/praclib/temp/core.gen.common.base/workproducts/glossary.xmi
new file mode 100644
index 0000000..2e7ab16
--- /dev/null
+++ b/praclib/temp/core.gen.common.base/workproducts/glossary.xmi
@@ -0,0 +1,79 @@
+<?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="-iOn7_gfX_iELWRNGJ2JKPQ"
+ name="glossary,_Wn7HcNcEEdqz_d2XWoVt6Q" guid="-iOn7_gfX_iELWRNGJ2JKPQ" changeDate="2007-12-11T15:20:49.853-0800"
+ version="1.0.0">
+ <mainDescription><p>
+ This artifact&nbsp;helps you avoid miscommunication by providing two essential resources:
+</p>
+<ul>
+ <li>
+ A central location to look for terms and abbreviations that are new to development team members
+ </li>
+ <li>
+ Definitions of terms that are used in specific ways within the domain
+ </li>
+</ul>
+<p>
+ Definitions for the glossary terms come from several sources, such as requirements documents, specifications, and
+ discussions with stakeholders and domain experts.
+</p></mainDescription>
+ <keyConsiderations><p>
+ Although listed as an output from, and an input to tasks associated with the requirements discipline, this artifact can
+ be updated at any time, by any role, as new terms are identified.
+</p>
+<p>
+ The terms defined in here should be used according to the recorded definitions in all project documentation so that all
+ stakeholders can clearly see that terms are being used consistently.
+</p>
+<p>
+ One of the primary decisions when developing&nbsp;this artifact&nbsp;is whether to have all terms in a single glossary,
+ or to maintain terms in a number of glossaries, business terms artifacts and/or models.&nbsp;If terms are defined in
+ multiple places, you need to communicate all these sources to the team and decide which take precedence.
+</p>
+<p>
+ It may be important, even in small projects, to reference and use existing broader glossaries, business terms artifacts
+ or data models, where they exist.
+</p>
+<p>
+ Industry and organizational-wide glossaries may be referenced and compliance with such specific chosen standards may be
+ required.
+</p></keyConsiderations>
+ <purpose><p>
+ The purposes of&nbsp;this artifact&nbsp;are:
+</p>
+<ul>
+ <li>
+ To record the terms that are being used on the project so that everyone has a common understanding of them
+ </li>
+ <li>
+ To achieve consistency by promoting the use of common terminology across the project
+ </li>
+ <li>
+ To make explicit different stakeholders' use of the same terms to mean different things or different terms to mean
+ the same thing
+ </li>
+ <li>
+ To provide important terms to the analysis and design team.
+ </li>
+</ul></purpose>
+ <impactOfNotHaving>Misunderstandings about the meanings of data items account for many failed projects. Increased costs and delayed schedules
+are associated with projects which are continuing without a common understanding of the terms being used.</impactOfNotHaving>
+ <reasonsForNotNeeding><p>
+ On small projects (e.g. enhancement projects), which are comprised of a team very familiar with the terms, this
+ artifact may be omitted.
+</p>
+<p>
+ If a project team has access to the glossary terms in some other form, this&nbsp;artifact may be
+ disregarded.&nbsp;&nbsp;<br />
+</p><br /></reasonsForNotNeeding>
+ <briefOutline><p>
+ A project glossary defines the terms used during all phases of the project. There is a short definition for each term.
+</p></briefOutline>
+ <representationOptions><p>
+ This is a simple alphabetized listing of domain terms and their definitions. It can be captured in a spreadsheet,
+ document, or published on a Wiki site to simplify access and maintenance.
+</p></representationOptions>
+</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/praclib/temp/core.gen.slot.base/.project b/praclib/temp/core.gen.slot.base/.project
new file mode 100644
index 0000000..ffb2dfd
--- /dev/null
+++ b/praclib/temp/core.gen.slot.base/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>core.gen.slot.base</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/core.gen.slot.base/guidances/supportingmaterials/resources/humpchart.gif b/praclib/temp/core.gen.slot.base/guidances/supportingmaterials/resources/humpchart.gif
new file mode 100644
index 0000000..33f5623
--- /dev/null
+++ b/praclib/temp/core.gen.slot.base/guidances/supportingmaterials/resources/humpchart.gif
Binary files differ
diff --git a/praclib/temp/core.gen.slot.base/guidances/supportingmaterials/resources/rup_iconL.jpg b/praclib/temp/core.gen.slot.base/guidances/supportingmaterials/resources/rup_iconL.jpg
new file mode 100644
index 0000000..aa2fc8a
--- /dev/null
+++ b/praclib/temp/core.gen.slot.base/guidances/supportingmaterials/resources/rup_iconL.jpg
Binary files differ
diff --git a/praclib/temp/core.gen.slot.base/plugin.xmi b/praclib/temp/core.gen.slot.base/plugin.xmi
new file mode 100644
index 0000000..458aa9c
--- /dev/null
+++ b/praclib/temp/core.gen.slot.base/plugin.xmi
@@ -0,0 +1,59 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_iR3T8EKmEdyrauqpmnA8jQ"
+ guid="_iR3T8EKmEdyrauqpmnA8jQ">
+ <resourceDescriptors xmi:id="_PV6ZcahCEdykUI8qndvuxA" id="-iVLpMTrtFg2MGrsirqzc3g"
+ uri="workproducts/glossary_slot_XXX.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_iRbPEEKmEdyrauqpmnA8jQ" name="core.gen.slot.base"
+ guid="_iRbPEEKmEdyrauqpmnA8jQ" changeDate="2007-12-05T08:29:44.426-0800">
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iRbPEUKmEdyrauqpmnA8jQ"
+ name="Content" guid="_iRbPEUKmEdyrauqpmnA8jQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iRbPEkKmEdyrauqpmnA8jQ"
+ name="Categories" guid="_iRbPEkKmEdyrauqpmnA8jQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iRbPE0KmEdyrauqpmnA8jQ"
+ name="Domains" guid="_iRbPE0KmEdyrauqpmnA8jQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iRbPFEKmEdyrauqpmnA8jQ"
+ name="Disciplines" guid="_iRbPFEKmEdyrauqpmnA8jQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iRbPFUKmEdyrauqpmnA8jQ"
+ name="RoleSets" guid="_iRbPFUKmEdyrauqpmnA8jQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iRbPFkKmEdyrauqpmnA8jQ"
+ name="WP Types" guid="_iRbPFkKmEdyrauqpmnA8jQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iRbPF0KmEdyrauqpmnA8jQ"
+ name="Tools" guid="_iRbPF0KmEdyrauqpmnA8jQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iRbPGEKmEdyrauqpmnA8jQ"
+ name="StandardCategories" guid="_iRbPGEKmEdyrauqpmnA8jQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iRbPGUKmEdyrauqpmnA8jQ"
+ name="CustomCategories" guid="_iRbPGUKmEdyrauqpmnA8jQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iRbPGkKmEdyrauqpmnA8jQ"
+ name="Hidden" guid="_iRbPGkKmEdyrauqpmnA8jQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_iRbPG0KmEdyrauqpmnA8jQ"
+ name="Custom Categories" guid="_iRbPG0KmEdyrauqpmnA8jQ"/>
+ </childPackages>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iRbPHEKmEdyrauqpmnA8jQ"
+ name="CoreContent" guid="_iRbPHEKmEdyrauqpmnA8jQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_VBd6oEMDEdyP_Jn83ylwUQ"
+ name="General Work Product Slots" guid="_VBd6oEMDEdyP_Jn83ylwUQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_XNPOoEMDEdyP_Jn83ylwUQ"
+ name="glossary_slot_XXX" guid="_XNPOoEMDEdyP_Jn83ylwUQ" briefDescription="This artifact defines important terms used by the project. The collection of terms clarifies the vocabulary used on the project."
+ presentationName="[Glossary]_XXX">
+ <presentation xmi:id="-iVLpMTrtFg2MGrsirqzc3g" href="uma://-iVLpMTrtFg2MGrsirqzc3g#-iVLpMTrtFg2MGrsirqzc3g"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_iRbPHUKmEdyrauqpmnA8jQ"
+ name="CapabilityPatterns" guid="_iRbPHUKmEdyrauqpmnA8jQ"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_iRbPHkKmEdyrauqpmnA8jQ"
+ name="DeliveryProcesses" guid="_iRbPHkKmEdyrauqpmnA8jQ"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_iRbPH0KmEdyrauqpmnA8jQ"
+ name="ProcessContributions" guid="_iRbPH0KmEdyrauqpmnA8jQ"/>
+ <bases href="uma://_iVydgENdEdy245g62lfWcA#_iVydgENdEdy245g62lfWcA"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/core.gen.slot.base/workproducts/glossary_slot_XXX.xmi b/praclib/temp/core.gen.slot.base/workproducts/glossary_slot_XXX.xmi
new file mode 100644
index 0000000..8041a34
--- /dev/null
+++ b/praclib/temp/core.gen.slot.base/workproducts/glossary_slot_XXX.xmi
@@ -0,0 +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" xmlns:rmc="http://www.ibm.com/rmc"
+ rmc:version="7.2.0" xmi:id="-iVLpMTrtFg2MGrsirqzc3g"
+ name="glossary_slot,_XNPOoEMDEdyP_Jn83ylwUQ" guid="-iVLpMTrtFg2MGrsirqzc3g" changeDate="2007-12-11T15:38:56.394-0800">
+ <purpose>This artifact is used across business and technical contexts&nbsp;to capture information relevant to the business&nbsp;and
+project.</purpose>
+</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/praclib/temp/core.mgmt.common.assign/.project b/praclib/temp/core.mgmt.common.assign/.project
new file mode 100644
index 0000000..6b5f7e4
--- /dev/null
+++ b/praclib/temp/core.mgmt.common.assign/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>core.mgmt.common.assign</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/core.mgmt.common.assign/plugin.xmi b/praclib/temp/core.mgmt.common.assign/plugin.xmi
new file mode 100644
index 0000000..2123f3d
--- /dev/null
+++ b/praclib/temp/core.mgmt.common.assign/plugin.xmi
@@ -0,0 +1,66 @@
+<?xml version="1.0" encoding="UTF-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.4/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.2.0" xmlns:epf="http://www.eclipse.org/epf"
+ epf:version="1.2.0">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_CX-9EM3qEdyuBO4ZIzcyig"
+ guid="_CX-9EM3qEdyuBO4ZIzcyig"/>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_CX-9AM3qEdyuBO4ZIzcyig" name="core.mgmt.common.assign"
+ guid="_CX-9AM3qEdyuBO4ZIzcyig">
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_CX-9Ac3qEdyuBO4ZIzcyig"
+ name="Content" guid="_CX-9Ac3qEdyuBO4ZIzcyig">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_CX-9As3qEdyuBO4ZIzcyig"
+ name="Categories" guid="_CX-9As3qEdyuBO4ZIzcyig">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_CX-9A83qEdyuBO4ZIzcyig"
+ name="Domains" guid="_CX-9A83qEdyuBO4ZIzcyig">
+ <contentElements xsi:type="org.eclipse.epf.uma:Domain" xmi:id="_SI-xkOFnEdyhmsbt0Xyl8A"
+ name="project_management_domain.assign" guid="_SI-xkOFnEdyhmsbt0Xyl8A"
+ variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Domain" href="uma://_MRPloEFXEdy9ENCpSugIjA#_8M6J4K80Edy9cPK11VzBuQ"/>
+ <workProducts xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_Ckay8Cc_EduIsqH1Q6ZuqA"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_CX-9BM3qEdyuBO4ZIzcyig"
+ name="Disciplines" guid="_CX-9BM3qEdyuBO4ZIzcyig"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_CX-9Bc3qEdyuBO4ZIzcyig"
+ name="RoleSets" guid="_CX-9Bc3qEdyuBO4ZIzcyig"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_CX-9Bs3qEdyuBO4ZIzcyig"
+ name="WP Types" guid="_CX-9Bs3qEdyuBO4ZIzcyig"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_CX-9B83qEdyuBO4ZIzcyig"
+ name="Tools" guid="_CX-9B83qEdyuBO4ZIzcyig"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_CX-9CM3qEdyuBO4ZIzcyig"
+ name="StandardCategories" guid="_CX-9CM3qEdyuBO4ZIzcyig"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_CX-9Cc3qEdyuBO4ZIzcyig"
+ name="CustomCategories" guid="_CX-9Cc3qEdyuBO4ZIzcyig">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_CX-9Cs3qEdyuBO4ZIzcyig"
+ name="Hidden" guid="_CX-9Cs3qEdyuBO4ZIzcyig">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_CX-9C83qEdyuBO4ZIzcyig"
+ name="Custom Categories" guid="_CX-9C83qEdyuBO4ZIzcyig"/>
+ </childPackages>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_CX-9DM3qEdyuBO4ZIzcyig"
+ name="CoreContent" guid="_CX-9DM3qEdyuBO4ZIzcyig">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_5US4sOGiEdyhmsbt0Xyl8A"
+ name="Role Assignments" guid="_5US4sOGiEdyhmsbt0Xyl8A">
+ <contentElements xsi:type="org.eclipse.epf.uma:Role" xmi:id="_8VHlYOGiEdyhmsbt0Xyl8A"
+ name="project_manager.assign_wp" guid="_8VHlYOGiEdyhmsbt0Xyl8A" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Role" href="uma://_A118oMYaEdyXeo04os5BOw#_0a0o0MlgEdmt3adZL5Dmdw"/>
+ <responsibleFor xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_Ckay8Cc_EduIsqH1Q6ZuqA"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_CX-9Dc3qEdyuBO4ZIzcyig"
+ name="CapabilityPatterns" guid="_CX-9Dc3qEdyuBO4ZIzcyig"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_CX-9Ds3qEdyuBO4ZIzcyig"
+ name="DeliveryProcesses" guid="_CX-9Ds3qEdyuBO4ZIzcyig"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_CX-9D83qEdyuBO4ZIzcyig"
+ name="ProcessContributions" guid="_CX-9D83qEdyuBO4ZIzcyig"/>
+ <bases href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPloEFXEdy9ENCpSugIjA"/>
+ <bases href="uma://_A118oMYaEdyXeo04os5BOw#_A118oMYaEdyXeo04os5BOw"/>
+ <bases href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0TmecJ-VEdy3Nc4rvuj7bA"/>
+ <bases href="uma://_iVydgENdEdy245g62lfWcA#_iVydgENdEdy245g62lfWcA"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/core.mgmt.common.base/.project b/praclib/temp/core.mgmt.common.base/.project
new file mode 100644
index 0000000..ff03bd8
--- /dev/null
+++ b/praclib/temp/core.mgmt.common.base/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>core.mgmt.common.base</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/core.mgmt.common.base/guidances/checklists/risk_list.xmi b/praclib/temp/core.mgmt.common.base/guidances/checklists/risk_list.xmi
new file mode 100644
index 0000000..20561b1
--- /dev/null
+++ b/praclib/temp/core.mgmt.common.base/guidances/checklists/risk_list.xmi
@@ -0,0 +1,63 @@
+<?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: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="-gqNN4DnROmJpgKtrdguhpg"
+ name="new_checklist,_7BZa0DIdEduDTv4Y1akVTA" guid="-gqNN4DnROmJpgKtrdguhpg" changeDate="2006-08-22T16:38:14.915-0400"
+ version="7.2.0">
+ <sections xmi:id="_qO41ADIfEduDTv4Y1akVTA" name="Have all potential risks to the project been identified?"
+ guid="_qO41ADIfEduDTv4Y1akVTA">
+ <sectionDescription><ul>
+ <li>
+ Have you identified anything that could deter you on the path to the project success?&nbsp;
+ </li>
+ <li>
+ Have you involved the team and stakeholders in risk identification?
+ </li>
+ <li>
+ Have you made sure that several categories were considered (technical, project management, organizational, and
+ external)?
+ </li>
+</ul>
+<p>
+ List all potential risks, giving a description and type (direct or indirect). See <a class="elementLinkWithType"
+ href="./../../../core.mgmt.common.base/guidances/concepts/risk_AF5840DA.html" guid="_0bsLgMlgEdmt3adZL5Dmdw">Concept:
+ Risk</a>&nbsp;for more information.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_5RiSkDe2EduD7J48kKN20g" name="Have all risks been described without ambiguity?"
+ guid="_5RiSkDe2EduD7J48kKN20g">
+ <sectionDescription>Are risks captured and described in a clear, concise, and unambiguous way? Also follow these rules when describing response
+strategies for risks. This will help you avoid unnecessary work and -- more importantly -- increase the probability that
+risks are effectively identified and managed.</sectionDescription>
+ </sections>
+ <sections xmi:id="_2rpQoDIfEduDTv4Y1akVTA" name="Have all major risks been evaluated?"
+ guid="_2rpQoDIfEduDTv4Y1akVTA">
+ <sectionDescription><ul>
+ <li>
+ Has the team assessed the order of magnitude of&nbsp; each risk (probability x impact)?
+ </li>
+ <li>
+ Have the risks been sorted according to their magnitude? This&nbsp;allows you to address the higher-magnitude risks
+ early in the project.
+ </li>
+ <li>
+ Has a response strategy been chosen for higher-magnitude risks?
+ </li>
+</ul>
+<p>
+ See <a class="elementLinkWithType" href="./../../../core.mgmt.common.base/guidances/concepts/risk_AF5840DA.html"
+ guid="_0bsLgMlgEdmt3adZL5Dmdw">Concept: Risk</a>&nbsp;and&nbsp;<a class="elementLinkWithType"
+ href="./../../../core.mgmt.common.base/guidances/guidelines/managing_risks_B1256EB4.html"
+ guid="_VNxL4ACsEdu8m4dIntu6jA">Guideline: Managing Risks</a> for more information.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_hSFaYDe3EduD7J48kKN20g" name="Are there interdependencies between risks?"
+ guid="_hSFaYDe3EduD7J48kKN20g">
+ <sectionDescription><span style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Make sure that you establish interdependencies between risks as
+appropriate. For example, the consequence of a risk happening may raise the probability of another risk happening or raise
+the impact that another risk could have on the project. If risks depend on each other, you may need a response strategy to
+mitigate&nbsp;all interdependent risks&nbsp;at the same time, or you may need revisit the risk list to update the magnitude
+of dependent risks.</span></sectionDescription>
+ </sections>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.mgmt.common.base/guidances/concepts/iteration.xmi b/praclib/temp/core.mgmt.common.base/guidances/concepts/iteration.xmi
new file mode 100644
index 0000000..332cd8f
--- /dev/null
+++ b/praclib/temp/core.mgmt.common.base/guidances/concepts/iteration.xmi
@@ -0,0 +1,77 @@
+<?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: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="-vi8wxwxVZLY0SMPFxZjD7A"
+ name="new_concept,_lam4ADkBEduxovfWMDsntw" guid="-vi8wxwxVZLY0SMPFxZjD7A" changeDate="2006-10-31T13:46:17.066-0800">
+ <mainDescription><H3>What is an Iteration </H3>
+<P>An iteration is a set period of time within a project in which you produce a stable, executable version of the product, together with any other supporting documentation, install scripts, or similar, necessary to use this release. The executable is demonstrable, allowing the team to demonstrate true progress to stakeholders, get feedback on how they are doing so that they can improve their understanding of what needs to be done, and how to do it, Each iteration builds upon the results of previous iteration, and will produce a product increment one step closer to the final product. Iterations are timeboxed, meaning the schedule for an iteration should be regarded as fixed, and the scope of the iteration's content actively managed to meet that schedule. </P>
+<P>At each iteration, artifacts are updated. It is said that this is a bit like "growing" software. Instead of developing artifacts one after another, in a pipeline fashion, they are evolving across the cycle, although at different rates. </P>
+<P>Iterative development is very disciplined: the iteration length is fixed; the objectives of iterations are carefully planned; the evaluation criteria are established when each iteration is planned; and the tasks and responsibilities of participants are well defined. Additionally, objective measures of progress are captured. Some reworking takes place from one iteration to the next, but this too is done in a structured fashion. </P>
+<P>Each iteration should address the most critical risks, and implement the highest-priority Work Items. This ensures that each iteration adds maximum stakeholder value, while reducing uncertainty. Iterative development is typically combined with frequent or continuous integration: as unit-tested components become available, they are integrated, then a build is produced and subjected to integration testing. In this way, the capability of the integrated software grows as the iteration proceeds, towards the goals set when the iteration was planned. Regular builds, such as daily or more frequent builds, let you break down the integration and test issues and spread them across the development cycle. These issues have often been the downfall of large projects because all problems were discovered at once during the single massive integration step, which occurred very late in the cycle, and where a single problem halts the whole team. </P>
+<H3>What Problem Do Iterations Address? </H3>
+<P>Today’s software applications are too complex to allow you to sequentially define the requirements, come up with an architecture and design, do an implementation, carry out testing, and get it all right. Whether you use waterfall or iterative development approaches, your initial requirements, architecture, design, and code will be suboptimal. With waterfall development, you typically do not get meaningful feedback on what improvements can be made until it is so late in the project that it is too costly to make them. By contrast, dividing the project into a series of time-boxed iterations allows you to deliver capabilities that can be assessed by stakeholders at the end of each iteration. This approach provides rapid and timely feedback loops enabling issues to be addressed and improvements made at a lower cost while budget and time still allow, and before the project has gone so far ahead that major rework is required. </P>
+<H3>Iteration Length </H3>
+<P>Iterations are typically 4 weeks long, although some teams will work with iterations as short as a week or as long as six weeks. For factors driving iteration length, see Table X. </P>
+<P><STRONG><EM>Table X. Factors Impacting Iteration Length.</EM></STRONG><BR>&nbsp;<BR></P>
+<TABLE style="WIDTH: 547px; HEIGHT: 356px" cellSpacing=2 cellPadding=2 width=547 border=1>
+<TBODY>
+<TR>
+<TH scope=col>Factors leading to reduced iteration length&nbsp; </TH>
+<TH scope=col>Factors leading to increased iteration length </TH></TR>
+<TR>
+<TD>Small teams&nbsp; </TD>
+<TD>Large teams </TD></TR>
+<TR>
+<TD>Collocated teams&nbsp; </TD>
+<TD>Distributed teams </TD></TR>
+<TR>
+<TD>Strong configuration management system&nbsp; </TD>
+<TD>Poor configuration management system </TD></TR>
+<TR>
+<TD>Dedicated, full-time resources </TD>
+<TD>Matrixed or part-time resources </TD></TR>
+<TR>
+<TD>Automated testing </TD>
+<TD>Lack of automated testing </TD></TR>
+<TR>
+<TD>Integrated tool environment&nbsp; </TD>
+<TD>Absence of good automation and tool integration </TD></TR>
+<TR>
+<TD>Team experienced with iterative development </TD>
+<TD>Team inexperienced with iterative development </TD></TR>
+<TR>
+<TD>Fast decision making </TD>
+<TD>Policies and bureaucracy preventing fast decision making </TD></TR>
+<TR>
+<TD>Unclear requirements </TD>
+<TD>Well-understood requirements </TD></TR>
+<TR>
+<TD>Unclear or brittle architecture </TD>
+<TD>Well-defined and stable architecture </TD></TR>
+<TR>
+<TD>New and poorly understood technology </TD>
+<TD>Well-understood technology </TD></TR></TBODY></TABLE><BR><BR>
+<H3>Why Iterate? </H3>
+<P>The iterative approach has proven itself superior to the waterfall approach for a number of reasons: </P>
+<UL>
+<LI>You are more likely to build an application that addresses user needs. Early specification of requirements often leads to unused features. The Standish Group has researched thousands of application development projects and has found that more than 45 percent of features are never used, while another 19 percent are used rarely&nbsp; (see Figure 2.3). In other words, typically more than half of the development effort is wasted on developing nonessential capabilities. To avoid this problem, you need to involve the customer in the development project and use an iterative approach that allows you to implement and validate the capabilities deemed most essential in each iteration. This approach allows not only early validation of key capabilities but also addition of new capabilities late in the project.
+<LI>Integration is not one “big bang” at the end of a project. Leaving integration to the end results in time- and budget-consuming rework. To avoid this, an iterative approach breaks a project down into smaller iterations, each evolving executable code that is continuously integrated to enable rapid feedback and minimize later revision.
+<LI>Risks are usually discovered or addressed during early iterations. With the iterative approach, risks are more likely to be identified and addressed in early iterations. As an example, if there is a risk that a stakeholder will not be happy with the functionality you are developing, iterative development will encourage you to&nbsp; implement the most essential capabilities partially and demonstrate them to key stakeholders to make sure that you are on the right track.
+<LI>Your ability to work effectively is fine-tuned. During early iterations, team members are walking through all lifecycle activities, from requirements capture and test definition to development, implementation, and testing. Consequently, they can make sure they have the tools, skills, organizational structure, and so on to work effectively.
+<LI>Management has a way of making tactical changes to the product. Management can make changes to the product along the way—to compete with other new products, for example. Iterative development allows you to evolve partial implementations of the end product quickly and use these for quick release of a reduced-scope product to counter a competitor's move.
+<LI>Reuse is facilitated. It is easier to identify common parts as they are being partially designed or implemented in iterations than to recognize them at the beginning. Discussions and reviews of the design in early iterations allow team members to spot potential opportunities for reuse and then develop a mature common code for these opportunities in subsequent iterations.
+<LI>Defects can be found and corrected over several iterations. This capability results in a robust architecture and a high-quality application. Flaws are detected in early iterations, rather than during a massive testing phase at the end. Performance bottlenecks are discovered while they can still be addressed instead of creating panic on the eve of delivery.
+<LI>Project personnel are better used. Many organizations match their use of a waterfall approach with a pipeline organization: the analysts send the completed requirements to designers, who send a completed design to programmers, who send components to integrators, who send a system to testers. These many handoffs are sources of errors and misunderstandings and make people feel less responsible for the final product. An iterative process encourages widening the scope of expertise of the team members, allowing them to play many roles and thus enabling a project manager to make better use of the available staff and simultaneously remove problematic handoffs.
+<LI>Team members learn along the way. The project members have several opportunities within a development cycle to learn from their mistakes and improve their skills from one iteration to another. More training opportunities can be discovered as a result of assessing the earlier iterations.
+<LI>The development process itself is improved and refined along the way. The end of iteration assessment not only looks at the project status from a product or scheduling perspective but also analyzes what can be improved in the next iteration in both the organization and the process.&nbsp; One technique for doing so is to hold a retrospective. </LI></UL><BR><SPAN class=E1><SPAN style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'; mso-fareast-font-family: 'MS Mincho'; mso-ansi-language: EN-US; mso-fareast-language: JA; mso-bidi-language: AR-SA"><?xml:namespace prefix = v ns = "urn:schemas-microsoft-com:vml" /><v:shapetype id=_x0000_t75 stroked="f" filled="f" path="m@4@5l@4@11@9@11@9@5xe" o:preferrelative="t" o:spt="75" coordsize="21600,21600"><STRONG><IMG height=307 alt="45 percent of featues implemented are never ever used" src="./resources/iteration.gif" width=489></STRONG></v:shapetype></SPAN></SPAN><BR>&nbsp;
+<P><STRONG><EM>Figure 2.3. Most Features Implemented Are Never or Rarely Used.<BR></EM></STRONG><EM>An amazing 45 percent of features implemented are never used, while another 19 percent are used only rarely. If features never used were not implemented in the first place, development time would be cut in about half. Further, since productivity is typically measured in the form of lines of code or functionality delivered, this improvement would not register as a productivity increase using standard productivity measures.<BR></EM>&nbsp; </P>
+<H3>Iteration and Phases </H3>
+<P>The purpose of iterations is to produce an executable which can be assessed so you can get feedback and make course corrections. This executable brings you one step closer to the final product. Phases provide a focus for a team on meeting a certain management objective. OpenUP has four phases, each ending with answering a specific question: </P>
+<UL>
+<LI><STRONG>Inception</STRONG>—Do we agree on the problem we are trying to solve?
+<LI><STRONG>Elaboration</STRONG>—Do we agree on the overall solution, and do we understand risks, costs and schedule parameters reasonably well?
+<LI><STRONG>Construction</STRONG>—Do we agree that we have a system that addresses key stakeholder needs?
+<LI><STRONG>Transition</STRONG>—Do we agree that we can release the system and end the project? </LI></UL>
+<P>Within each phase, you may have one or several iterations, where the iterations aim at producing the results required to answer these questions. As an example, to answer the question for Elaboration, we typically need to implement and test some key aspects of the system so that we understand what architecture we need, what Commercial Off-The-Shelf (COTS) components we may need, what key risks we face and how to address them, the effectiveness of the team, and so on. These needs will steer how we prioritize what is to be done in an Elaboration iteration. </P></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.mgmt.common.base/guidances/concepts/metrics.xmi b/praclib/temp/core.mgmt.common.base/guidances/concepts/metrics.xmi
new file mode 100644
index 0000000..5990109
--- /dev/null
+++ b/praclib/temp/core.mgmt.common.base/guidances/concepts/metrics.xmi
@@ -0,0 +1,149 @@
+<?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: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="_7ygXoMM3EdmSIPI87WLu3g"
+ name="metrics,_0mYYkMlgEdmt3adZL5Dmdw" guid="_7ygXoMM3EdmSIPI87WLu3g" changeDate="2006-08-29T20:19:12.494-0400"
+ version="7.2.0">
+ <mainDescription><h3>
+ <font size="5">What is a Metric?</font>
+</h3>
+<p>
+ We distinguish between measure and metric. To clarify, let’s start by defining what is meant by measure and by metric.
+</p>
+<ul>
+ <li>
+ <b>Measure</b>: A raw data item that is directly measured, and that will be used to calculate a metric.
+ </li>
+ <li>
+ <b>Metric</b>: An interpretation of a measure or a set of measures that you use to guide your project. For example,
+ recording how many test cases have passed and how many have failed are measures. Interpreting what level of quality
+ this indicates and how it reflects the team's progress within the current iteration is a metric.
+ </li>
+</ul>
+<h3>
+ <font size="5">Why Measure?</font>
+</h3>
+<p>
+ Measurements will mainly help you to:
+</p>
+<ul>
+ <li>
+ <b>Communicate effectively</b>. Measurement supports effective communication among team members and project
+ stakeholders.
+ </li>
+ <li>
+ <b>Identify and correct problems early</b>. Measurement enables you to identify and manage potential problems early
+ in the development lifecycle.
+ </li>
+ <li>
+ <b>Make informed trade-offs</b>. Measurement helps objectively assess the impact of decisions, helping&nbsp;the
+ team&nbsp;make trade-off decisions to best meet project goals.
+ </li>
+ <li>
+ <b>Tune estimations</b>. Recording schedule, progress, and expenditures for projects will help team members to make
+ more reliable estimations in the future.
+ </li>
+</ul>
+<h3>
+ <font size="5">Potential Challenges</font>
+</h3>
+<p>
+ There are several dangers when it comes to metrics:
+</p>
+<ul>
+ <li>
+ <div align="left">
+ <b>They can be too costly</b>. The benefit provided by the metric must exceed the cost of collecting it. Keep
+ your measurements simple and easy to collect.
+ </div>
+ </li>
+ <li>
+ <div align="left">
+ <b>They’re a poor substitute for communication</b>. Do not use metrics as a substitute for communication. Team
+ members may help to decide which metrics make sense for the project. Apply metrics not so much to control the
+ project but to help team to collaborate better. Asking people about their progress is a co-dependent way of
+ gaining insight into progress.
+ </div>
+ </li>
+ <li>
+ <div align="left">
+ <b>They can be misleading</b>. No metric or collection of metrics is perfect. Furthermore, the measurements
+ upon which they are based can be manipulated by the people capturing them. Don’t rely simply upon metrics to
+ manage a project.
+ </div>
+ </li>
+</ul>
+<p>
+ Effective metrics programs can be challenging to implement, though typically not because of the statistics and complex
+ analysis often associated with metrics. Rather, the challenge lies in understanding which metrics add value to the
+ project and to the company, and which procedures are most efficient for collecting and using these metrics.
+</p>
+<p>
+ Consider to implement only a handful metrics. Importantly, do not collect metrics unless they help contribute to a goal
+ of improving a defined area of your software development process. If you will not act on a metric, do not collect it.
+ It is much more important to focus on a small number of metrics that are important to what you are trying to achieve
+ right now, versus a larger set of metrics that may be "good to track".&nbsp;
+</p>
+<h3>
+ <font size="5">Example Metrics</font>
+</h3>
+<p>
+ Below are some common measures and associated metrics used in software development projects. These metrics help teams
+ communicate, identify and correct problems early, make informed trade-offs, and tune estimations. Example metrics
+ coverage areas are listed below.
+</p>
+<h4>
+ Software quality
+</h4>
+<ul>
+ <li>
+ Defect backlog: Number of defects discovered respectively resolved per iteration
+ </li>
+ <li>
+ Test case coverage: Number of test cases executed over total number of test cases
+ </li>
+ <li>
+ Code coverage: % of code that have been tested
+ </li>
+</ul>
+<h4>
+ Development productivity
+</h4>
+<ul>
+ <li>
+ Velocity: Number of delivered points by iteration (see <a class="elementLink" href="./../../../openup/guidances/guidelines/agile_estimation_A4EF42B3.html" guid="_CGHskBEdEdqY7JB6N6CW2w">Agile Estimation</a>)
+ </li>
+</ul>
+<h4>
+ Development process effectiveness
+</h4>
+<ul>
+ <li>
+ Responsiveness to quality issues: Number of defects discovered versus resolved per iteration
+ </li>
+ <li>
+ Responsiveness to process improvement proposal: Number of process enhancements proposed versus implemented
+ </li>
+</ul>
+<h4>
+ Cost and schedule estimate and variance
+</h4>
+<ul>
+ <li>
+ Effort: Actual effort spent per iteration
+ </li>
+ <li>
+ Cost: Cost per iteration
+ </li>
+ <li>
+ Effort remaining: Track <a class="elementLink" href="./../../../openup/guidances/reports/project_burndown_206E4670.html" guid="_ePrt8Dj3EduxovfWMDsntw">Project Burndown</a>
+ </li>
+</ul>
+<p>
+ There are many other measures and metrics that may make sense, based on what you are trying to accomplish. As an
+ example, to measure the quality of your architecture, you may for example choose to collect metrics related to coupling
+ between different software packages (groups of related classes) by measuring extensibility, dependency, and
+ responsibility of each package.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.mgmt.common.base/guidances/concepts/resources/iteration.gif b/praclib/temp/core.mgmt.common.base/guidances/concepts/resources/iteration.gif
new file mode 100644
index 0000000..1f1a19b
--- /dev/null
+++ b/praclib/temp/core.mgmt.common.base/guidances/concepts/resources/iteration.gif
Binary files differ
diff --git a/praclib/temp/core.mgmt.common.base/guidances/concepts/risk.xmi b/praclib/temp/core.mgmt.common.base/guidances/concepts/risk.xmi
new file mode 100644
index 0000000..0d8ce58
--- /dev/null
+++ b/praclib/temp/core.mgmt.common.base/guidances/concepts/risk.xmi
@@ -0,0 +1,165 @@
+<?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: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="_u6enMMM1EdmSIPI87WLu3g"
+ name="risk,_0bsLgMlgEdmt3adZL5Dmdw" guid="_u6enMMM1EdmSIPI87WLu3g" changeDate="2007-11-13T10:17:21.218-0500"
+ version="7.2.0">
+ <mainDescription><h1>
+ What is a Risk?
+</h1>
+<p>
+ A risk is an uncertain event or condition that, if it occurs, will have a negative or positive effect on one or more
+ project objectives [<a class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/tech_references_6CCF393.html#PMI04"
+ guid="_9ToeIB83Edqsvps02rpOOg">PMI04</a>]. Project risks may be seen as threats or opportunities. The latter means that
+ taking a calculated risk may bring, for example, competitive advantage for a product or organization. If there are
+ benefits associated with an opportunity, then you can take certain degrees of risk for a project to be successful [<a
+ class="elementLinkWithUserText"
+ href="./../../../core.mgmt.common.base/guidances/supportingmaterials/mgmt_references_D80619F3.html#SEI99"
+ guid="_JlTPUM6aEdyuBO4ZIzcyig">SEI99</a>].
+</p>
+<p>
+ In everyday life a risk is an exposure to loss or injury: A factor, thing, element, or course involving uncertain
+ danger. Similarly, in software development a risk is something that can compromise the success of a project. Examples
+ of potential sources of risk in software development are listed below (see [<a class="elementLinkWithUserText"
+ href="./../../../core.mgmt.common.base/guidances/supportingmaterials/mgmt_references_D80619F3.html#SEI99"
+ guid="_JlTPUM6aEdyuBO4ZIzcyig">SEI99</a>] for more details):
+</p>
+<ul>
+ <li>
+ Requirements
+ </li>
+ <li>
+ Design
+ </li>
+ <li>
+ Development process
+ </li>
+ <li>
+ Work environment
+ </li>
+ <li>
+ Resources
+ </li>
+ <li>
+ Contract
+ </li>
+ <li>
+ Project interdependencies
+ </li>
+ <li>
+ And so on
+ </li>
+</ul>
+<h1>
+ Risk Attributes
+</h1>
+<p>
+ You can record as much information as you like or need about your risks. You will find a list of common risk attributes
+ following.
+</p>
+<ul>
+ <li>
+ <b>Risk Description:</b> A description of the risk detailing the impact for the project if this risk becomes a
+ problem (that is, it becomes a reality).
+ </li>
+ <li>
+ <b>Risk Category</b>: Risk identification is usually more easily done when there is a "mental framework" in place
+ to ensure that potential areas of risk are not overlooked. One way of doing this is to divide risks into categories
+ (such as technical, project management, organizational, and external), to ensure that all aspects of the project
+ which are prone to risk are covered.
+ </li>
+ <li>
+ <b>Risk Type:</b> Used to classify the risk as:
+ </li>
+ <li style="LIST-STYLE-TYPE: none">
+ <ul>
+ <li>
+ <b>Direct risk</b>: A risk that the project has a large degree of control over
+ </li>
+ <li>
+ <b>Indirect risk</b>: A risk with little or no project control
+ </li>
+ </ul>
+ </li>
+ <li>
+ <b>Risk Probability:</b> How likely the risk event will happen. This is usually represented as a scale of values
+ (for example: High, Medium, Low). Probability is one of the most difficult quantities to judge accurately.
+ </li>
+ <li>
+ <b>Risk Impact</b> (level): If this risk becomes a problem, what will the impact on the project be? This is not the
+ actual <b>description</b> of the impact, but the <b>level</b> of impact. As the risk probability, it is usually
+ represented as a scale. This attribute is also sometimes called the <b>severity</b> of the risk.
+ </li>
+ <li>
+ <b>Risk Magnitude</b>: To be able to rank and define which risks need to be mitigate first, the <b>Risk
+ Probability</b> and <b>Risk Impact</b> attributes are often combined in a single <b>Risk</b> <b>Magnitude</b>
+ indicator represented as a scale similar to the combined attributes.
+ </li>
+</ul>
+<h1>
+ Risk Response Strategies
+</h1>
+<p>
+ The risk response should be in line with the significance of the risk. The strategies for handling risk cover two main
+ types: negative risks and positive risks (or opportunities). Common response strategies for negative risks or threats
+ include:
+</p>
+<ul>
+ <li>
+ <b>Avoid</b>: Reorganize the project so that it cannot be affected by that risk (for example, removing work)
+ </li>
+ <li>
+ <b>Mitigate</b>: Define actions to reduce the probability or the impact of the risk, removing it from the top of
+ the list
+ </li>
+ <li>
+ <b>Transfer</b>: Reorganize the project so that someone or something else bears the risk. It simply gives another
+ party responsibility for its management. It doesn't eliminate the risk.
+ </li>
+</ul>
+<p>
+ Common response strategies for positive risks or opportunities include:
+</p>
+<ul class="noindent">
+ <li>
+ <b>Exploit</b>: Add work or reorganize the project to make sure that the opportunity occurs (it is the reverse of
+ avoid)
+ </li>
+ <li>
+ <b>Enhance</b>: Define actions to increase the probability or the positive impact of the risk (this is the reverse
+ of mitigate)
+ </li>
+ <li>
+ <b>Share</b>: Allocate the ownership of the opportunity to a third party who is best able to capture the
+ opportunity for the benefit of the project.
+ </li>
+</ul>
+<p>
+ Another response strategy for both threats or opportunities is to <b>Accept</b>: Decide to live with the risk, and
+ define a contingency plan.
+</p>
+<p>
+ Some scenarios for software development may help to make these concepts more clear:
+</p>
+<ul>
+ <li>
+ You need to use a new framework. A risk avoidance strategy could be to drop this new framework and use another one
+ that is already understood by the team.
+ </li>
+ <li>
+ The application you are developing needs to communicate with a legacy system. A risk transfer strategy would be to
+ have the legacy support team be responsible for providing the APIs to access the legacy system.
+ </li>
+ <li>
+ You need to use new middleware. A risk mitigation strategy could be to build a prototype using this new middleware
+ to validate that it will provide the features you need for your application.
+ </li>
+ <li>
+ Your integrator is the only one who knows how to integrate the different components of your application. A
+ contingency plan could be to identify a resource on another project that you could bring on if your integrator is
+ sick, leaves the company, and so on.
+ </li>
+</ul></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.mgmt.common.base/guidances/guidelines/agile_estimation.xmi b/praclib/temp/core.mgmt.common.base/guidances/guidelines/agile_estimation.xmi
new file mode 100644
index 0000000..d4ca6da
--- /dev/null
+++ b/praclib/temp/core.mgmt.common.base/guidances/guidelines/agile_estimation.xmi
@@ -0,0 +1,139 @@
+<?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: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="_CYRMgBEdEdqY7JB6N6CW2w"
+ name="agile_estimation,_CGHskBEdEdqY7JB6N6CW2w" guid="_CYRMgBEdEdqY7JB6N6CW2w"
+ changeDate="2007-11-13T10:21:06.562-0500" version="7.2.0">
+ <mainDescription><h3>
+ Agile Estimation
+</h3>
+<p>
+ There are three main concepts you need to understand to do agile estimation, see [<a class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/references_6CCF393.html#COH05"
+ guid="_9ToeIB83Edqsvps02rpOOg">COH05</a>] for more information:
+</p>
+<ul>
+ <li>
+ <strong>Estimation of Size</strong> gives a high-level estimate for the work item, typically measured using a
+ neutral unit such as points
+ </li>
+ <li>
+ <strong>Velocity</strong> tells us how many points this project team can deliver within an iteration;
+ </li>
+ <li>
+ <strong>Estimation of Effort</strong> translates the size (measured in points) to a detailed estimate of effort
+ typically using the units of Actual Days or Actual Hours. The estimation of effort indicates how long it will take
+ the team member(s) to complete the assigned the work item(s).
+ </li>
+</ul>
+<h4>
+ Estimation of Size
+</h4>
+<p>
+ Agile estimation of size is typically done using a relative measure called <strong>points</strong>.&nbsp; The team
+ decides how big a point is, and based on that size, determines how many points each work item is. To make estimation go
+ fast, use only full points, 1, 2, 3, 5, 8, and so on, rather than fractions of a point, such 0.25, or 1.65 points. To
+ get started, look at 10 or so representative work items, give the smallest the size of one point, and then go through
+ all other work items and give them a relative point estimate based on that point. Note that points are used for
+ high-level estimates, so do not spend too much time on any one item. This is especially true for work items of lower
+ priority, to avoid wasting effort on things that are unlikely to be addressed within the current iteration.
+</p>
+<p>
+ A key benefit of points is that they are neutral and relative. Let’s say that Ann is 3 times more productive than Jack.
+ If Ann and Jack agree that work item A is worth 1 point, and they both think work item B is roughly 5 times as big,
+ they can rapidly agree that work item B is worth 5 points. Ann may however think work item B can be done in 12 hours,
+ while Jack thinks it can be done in 36 hours. That is fine, they may disagree about the actual effort required to do
+ it, but we do not care at this point in time, we only want the team to agree on the relative size. We will later use
+ Velocity to determine how much ‘size’, or how many points, the team can take on within an iteration.
+</p>
+<p>
+ One project team may say that a work item of a certain size is worth 1 point. Another project team would estimate the
+ same sized work item to be worth 5 points. That is fine, as long as you are consistent within the same project. Make
+ sure that the entire team is involved in assessing size, or at least that the same people are involved in all your size
+ estimates, to ensure consistency within your project. We will see how the concept of velocity will fix also this
+ discrepancy in a point meaning different things to different project teams.
+</p>
+<p>
+ You can also use other measures of size, where the most common alternative is Ideal Days. See for example [<a
+ class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/references_6CCF393.html"
+ guid="_9ToeIB83Edqsvps02rpOOg">COH05</a>] for more information.
+</p>
+<h4>
+ Velocity
+</h4>
+<p>
+ Velocity is a key metric used for iteration planning. It indicates how many points are delivered upon within an
+ iteration for a certain team and project. As an example, a team planned to accomplish 20 points in the first iteration.
+ At the end of the iteration, they noticed that they only delivered upon 14 points, their velocity was hence 14. For the
+ next iteration, they may plan for fewer points, let’s say 18 points, since they think they can do a little better than
+ in previous iteration. In this iteration, they delivered 17 points, giving them a velocity of 17.
+</p>
+<p>
+ Expect the velocity to change from iteration to iteration. Some iterations go smoother than others, and points are not
+ always identical in terms of effort. Some team members are more effective than others, and some problems end up being
+ harder than others. Also, changes to the team structure, learning new skills, changes to the tool environment, better
+ teaming, or more overhead with meetings or tasks external to the project will all impact velocity. In general, velocity
+ typically increases during the project as the team builds skills and becomes more cohesive.
+</p>
+<p>
+ Velocity compensates for differences between teams in terms of how big a point is. Let’s assume that project team Alpha
+ and project team Beta are equally efficient in developing software, and they run the same project in parallel. Team
+ Alpha, however, assesses all work items as being worth 3 times as many points as team Beta's estimates. Team Alpha
+ assesses work item A, B, C, and D to correspond to 30 points, and team Beta estimates the same work items to correspond
+ to 10 points. Both teams deliver upon those 4 work items in the next iteration, giving team Alpha a velocity of 30, and
+ team Beta a velocity of 10. It may sound as if team Alpha is more effective, but let’s look at what happens when they
+ plan the next iteration. They both want to take on work item E-H, which team Alpha has estimated to be 30 points, and
+ team Beta as normal has estimated to be 1/3 as many points, or 10 points. Since a team can typically take on as many
+ points as indicated by their velocity, they can both take on all of E-H. The end result is that it does not matter how
+ big a point is, as long as you are consistent within your team.
+</p>
+<p>
+ Velocity also averages out the efficiency of different team members. Let’s look at an example; Let’s assume that Ann
+ always works 3 times as fast as Jack and Jane. Ann will perhaps deliver 9 points per iteration, and Jack and Jane 3
+ points each per iteration. The velocity of that 3-person team will be 15 points. As mentioned above, Ann and Jack may
+ not agree on how much effort is associated with a work item, but they can agree on how many points it is worth. Since
+ the team velocity is 15, the velocity will automatically translate the point estimate to how much work can be taken on.
+ As you switch team members, or as team members become more or less efficient, your velocity will change, and you can
+ hence take on more or less points. This does however not require you to change the estimate of the size. The size is
+ still the same, and the velocity will help you to calculate how much size you can deliver upon with the team at hand
+ for that iteration.
+</p>
+<h4>
+ Estimation of Effort
+</h4>
+<p>
+ Estimation of Effort translates the size (measured in points) to a detailed estimate of effort typically using the
+ units of Actual Days or Actual Hours. As you plan an iteration, you will take on a work item, such as detail, design,
+ implement and test a scenario, which may be sized to 5 points. Since this is still a reasonably big work item, break it
+ down&nbsp;into a number of smaller work items, such as 4 separate work items for Detailing, Designing, Implementing and
+ Testing Server portion, and Implementing and Testing Client portion of the scenario. Team members are asked to sign up
+ for the tasks, and then detail the&nbsp;estimate of the actual effort, measured in hours or days, for their tasks. In
+ this case, the following actual estimates were done (with person responsible within parenthesis):
+</p>
+<ul>
+ <li>
+ Detailing scenario (Ann): 4 hours
+ </li>
+ <li>
+ Designing scenario (Ann and Jack):&nbsp; 6 hours
+ </li>
+ <li>
+ Implementing and Testing Server portion of scenario (Jack): 22 hours&nbsp;
+ </li>
+ <li>
+ Implementing and Testing Client portion of scenario (Ann): 12 hours
+ </li>
+ <li>
+ <strong>Total Effort Estimate for Scenario:</strong> 44 hours
+ </li>
+</ul>
+<p>
+ If other people would be assigned to the tasks, the estimated actual hours could be quite different. There is hence no
+ point doing detailed estimates until you know who will do the work, and what actual problems you will run into. Often,
+ some level of analysis and design of the work item needs to take place before a reasonable estimate can be done.
+ Remember that estimates are still estimates, and a person assigned to a task should feel free (and be encouraged) to
+ re-estimate the effort required to complete the task, so we have a realistic view of progress within an iteration.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.mgmt.common.base/guidances/guidelines/managing_risks.xmi b/praclib/temp/core.mgmt.common.base/guidances/guidelines/managing_risks.xmi
new file mode 100644
index 0000000..758d71e
--- /dev/null
+++ b/praclib/temp/core.mgmt.common.base/guidances/guidelines/managing_risks.xmi
@@ -0,0 +1,76 @@
+<?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="-HhGIkAPjHSIxnPzI3cyDnQ"
+ name="managing_risks,_VNxL4ACsEdu8m4dIntu6jA" guid="-HhGIkAPjHSIxnPzI3cyDnQ">
+ <mainDescription><h3>
+ Introduction to Risk Management
+</h3>
+<p>
+ Every project contains some measure of uncertainty. <strong>Risk Management</strong>&nbsp;deals with this uncertainty,
+ trying to understand its&nbsp;potential influence on the project. The purpose of Risk Management is to increase the
+ probability and impact of positive events and decrease the probability and impact of events adverse to the project [<a
+ class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/references_6CCF393.html#PMI04"
+ guid="_9ToeIB83Edqsvps02rpOOg">PMI04</a>]. The project manager, team, and stakeholders should be involved in risk
+ management.
+</p>
+<h3>
+ Identify Risks
+</h3>
+<p>
+ Identify risks as soon as the project starts and document them in the <a class="elementLink"
+ href="./../../../practice.mgmt.iterative_dev.base/workproducts/risk_list_C4B6F290.html"
+ guid="_Ckay8Cc_EduIsqH1Q6ZuqA">Risk List</a>.&nbsp;Continue identifying and managing risks throughout the project. A
+ common mistake is to identify risks only at the beginning of the project and then only track the status of these
+ initial risks. The <a class="elementLink"
+ href="./../../../practice.mgmt.iterative_dev.base/workproducts/risk_list_C4B6F290.html"
+ guid="_Ckay8Cc_EduIsqH1Q6ZuqA">Risk List</a>&nbsp; should be revisited weekly, or as a minimum when performing task <a
+ class="elementLink" href="./../../../practice.mgmt.iterative_dev.base/tasks/plan_iteration_957C90DC.html"
+ guid="_0keUEMlgEdmt3adZL5Dmdw">Plan Iteration</a>, to add any newly discovered risks.
+</p>
+<h3>
+ Prioritize Risks
+</h3>
+<p>
+ Prioritize risks for further analysis or action. A good approach for prioritizing risks is to have an attribute called
+ risk magnitude, a combination of the risk probability and the risk impact. Each iteration provides a chance&nbsp;for
+ better understanding of stakeholder needs, the team capabilities, the technology at hand, and so on. Capture, qualify
+ and prioritize risks as they arise. High magnitude risks are&nbsp;attacked first, thus&nbsp;improving the chances of
+ project success and minimizing uncertainty. See <a class="elementLinkWithType"
+ href="./../../../practice.mgmt.iterative_dev.base/guidances/templates/risk_list_33A6AE1E.html"
+ guid="_MIUO0C8FEduzydamRseoUw">Template: Risk List</a>&nbsp;for more information.
+</p>
+<h3>
+ Select Risk Response Strategies
+</h3>
+<p>
+ You are trying to mitigate or tackle the high priority risks as early as possible in the project. In order to achieve
+ this you need to get a good grip on the risks the project is faced with, and have clear strategies on how to mitigate
+ or deal with them.&nbsp; Once you have chosen a set of risks to focus on, develop options and determine actions to
+ enhance opportunities and reduce threats, selecting a strategy, as described in <a class="elementLinkWithType"
+ href="./../../../core.mgmt.common.base/guidances/concepts/risk_AF5840DA.html" guid="_0bsLgMlgEdmt3adZL5Dmdw">Concept:
+ Risk</a>. Sometimes strategies can be determined for each cause, rather than each risk, eliminating many risks at once.
+</p>
+<h3>
+ Plan Risk Response
+</h3>
+<p>
+ For each selected strategy, identify and assign tasks to apply the strategy to the given risk. Place those tasks on the
+ <a class="elementLink" href="./../../../practice.mgmt.iterative_dev.base/workproducts/work_items_list_39D03CC8.html"
+ guid="_rGNWsCbSEdqh1LYUOGRh2A">Work Items List</a>&nbsp;so they can be assigned to iterations. Keep a&nbsp;reference to
+ the risk for traceability. The effort must be appropriate to the magniture of the risk. Avoid spending more preventing
+ a threat than the impact from the risk if it occurs.
+</p>
+<h3>
+ Monitor Risks
+</h3>
+<p id="comment_text_4">
+ Follow up regularly on risk-mitigation/enhancing actions. Risk reviews should be held&nbsp;when performing task <a
+ class="elementLink" href="./../../../practice.mgmt.iterative_dev.base/tasks/assess_results_EC34D88D.html"
+ guid="_0l53cMlgEdmt3adZL5Dmdw">Assess Results</a>&nbsp;to determine whether the information about project risks is up
+ to date, and to assess whether any changes are necessary. The team may decide to try another strategy if the chosen
+ strategy does not reduce/increase the magnitude of a risk.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.mgmt.common.base/guidances/guidelines/resources/work_item_prioritization_diagram.jpg b/praclib/temp/core.mgmt.common.base/guidances/guidelines/resources/work_item_prioritization_diagram.jpg
new file mode 100644
index 0000000..12f9048
--- /dev/null
+++ b/praclib/temp/core.mgmt.common.base/guidances/guidelines/resources/work_item_prioritization_diagram.jpg
Binary files differ
diff --git a/praclib/temp/core.mgmt.common.base/guidances/supportingmaterials/mgmt_references.xmi b/praclib/temp/core.mgmt.common.base/guidances/supportingmaterials/mgmt_references.xmi
new file mode 100644
index 0000000..d6b1ba0
--- /dev/null
+++ b/praclib/temp/core.mgmt.common.base/guidances/supportingmaterials/mgmt_references.xmi
@@ -0,0 +1,59 @@
+<?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="-BUHtqig5wrabMIpZgZChMg"
+ name="new_supporting_material,_JlTPUM6aEdyuBO4ZIzcyig" guid="-BUHtqig5wrabMIpZgZChMg"
+ changeDate="2008-01-29T13:45:58.328-0500">
+ <mainDescription><TABLE width="100%" summary="layout table" border=0>
+<TBODY>
+<TR>
+<TD vAlign=top width="12%"><A>BOE95</A> </TD>
+<TD colSpan=2>Boehm, B. <EM>Anchoring the Software Process</EM>, <a href="http://sunset.usc.edu/publications/TECHRPTS/1995/usccse95-507/ASP.pdf">http://sunset.usc.edu/publications/TECHRPTS/1995/usccse95-507/ASP.pdf</a> </TD></TR></TBODY></TABLE>
+<TABLE width="100%" summary="layout table" border=0>
+<TBODY>
+<TR>
+<TD vAlign=top width="12%">
+<P>BRO95</P></TD>
+<TD colSpan=2>
+<P>Brooks, F.P <EM>The Mythical Man Month: Essays on Software Engineering, 20th Anniversary Edition</EM>.&nbsp;Addison Wesley Professional, 1995. </P></TD></TR></TBODY></TABLE>
+<TABLE width="100%" summary="layout table" border=0>
+<TBODY>
+<TR>
+<TD vAlign=top width="12%"><A>CRO79</A> </TD>
+<TD colSpan=2>Crosby, Philip. <EM>Quality is Free: The Art of Making Quality Certain</EM>, McGraw-Hill, 1979. </TD></TR></TBODY></TABLE>
+<TABLE width="100%" summary="layout table" border=0>
+<TBODY>
+<TR>
+<TD vAlign=top width="12%"><A>KRO03</A> </TD>
+<TD colSpan=2>Kroll, P. and&nbsp;Kruchten, P. <EM>The Rational Unified Process Made Easy</EM>, Addison Wesley, 2003. </TD></TR></TBODY></TABLE>
+<TABLE width="100%" summary="layout table" border=0>
+<TBODY>
+<TR>
+<TD vAlign=top width="12%">KRO05 </TD>
+<TD colSpan=2>Kroll, P. and&nbsp;MacIsaac, B. <EM>Agility and Discipline Made Easy</EM>, Addison Wesley, 2005. </TD></TR></TBODY></TABLE>
+<TABLE width="100%" summary="layout table" border=0>
+<TBODY>
+<TR>
+<TD vAlign=top width="12%"><A>RUP06</A> </TD>
+<TD colSpan=2>IBM Rational 2006. <EM>The Rational Unified Process.</EM> </TD></TR>
+<TR>
+<TD vAlign=top width="12%"></TD>
+<TD width="10%"></TD>
+<TD style="PADDING-BOTTOM: 10px" width="78%">A commercial methodology, also based on the Eclipse Process Framework, and advanced guidance on topics such as business modeling, portfolio management, asset-based development, real-time design, user experience, and so on. </TD></TR></TBODY></TABLE>
+<TABLE width="100%" summary="layout table" border=0>
+<TBODY>
+<TR>
+<TD vAlign=top width="12%"><A>SCH04</A> </TD>
+<TD colSpan=2>Schwaber, K. <EM>Agile Project Management with Scrum.</EM> Microsoft Press 2004. </TD></TR>
+<TR>
+<TD vAlign=top width="12%"></TD>
+<TD width="10%"></TD>
+<TD style="PADDING-BOTTOM: 10px" width="78%">
+<P>An excellent reference by one of the co-inventors of the Scrum project management method. </P></TD></TR></TBODY></TABLE>
+<TABLE width="100%" summary="layout table" border=0 <table &gt;>
+<TBODY>
+<TR>
+<TD vAlign=top width="12%"><A>SEI99</A> </TD>
+<TD colSpan=2>SEI, 1999. <EM>Software Risk Evaluation (SRE) Method Description, v2.0.</EM> <BR><a href="http://www.sei.cmu.edu/pub/documents/99.reports/pdf/99tr029-body.pdf#search=">http://www.sei.cmu.edu/pub/documents/99.reports/pdf/99tr029-body.pdf#search=%22software%20risk%20evaluation%22</a> </TD></TR></TBODY></TABLE></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.mgmt.common.base/guidances/templates/resources/risk_list_tpl.xls b/praclib/temp/core.mgmt.common.base/guidances/templates/resources/risk_list_tpl.xls
new file mode 100644
index 0000000..e3970a2
--- /dev/null
+++ b/praclib/temp/core.mgmt.common.base/guidances/templates/resources/risk_list_tpl.xls
Binary files differ
diff --git a/praclib/temp/core.mgmt.common.base/guidances/templates/risk_list.xmi b/praclib/temp/core.mgmt.common.base/guidances/templates/risk_list.xmi
new file mode 100644
index 0000000..8dd2dfa
--- /dev/null
+++ b/praclib/temp/core.mgmt.common.base/guidances/templates/risk_list.xmi
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:GuidanceDescription 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="-OugFZJszm73z0_KSwRXZPw"
+ name="new_template,_MIUO0C8FEduzydamRseoUw" guid="-OugFZJszm73z0_KSwRXZPw">
+ <attachments>resources/risk_list_tpl.xls</attachments>
+</org.eclipse.epf.uma:GuidanceDescription>
diff --git a/praclib/temp/core.mgmt.common.base/guidances/termdefinitions/agile.xmi b/praclib/temp/core.mgmt.common.base/guidances/termdefinitions/agile.xmi
new file mode 100644
index 0000000..df4b1f1
--- /dev/null
+++ b/praclib/temp/core.mgmt.common.base/guidances/termdefinitions/agile.xmi
@@ -0,0 +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.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="-qZE4XgeMK93LmJMKuQWGFg"
+ name=",_3PJ38EvqEdunZcj9T5hrMQ" guid="-qZE4XgeMK93LmJMKuQWGFg">
+ <mainDescription>A set of values and principles for software development that use lean production techniques to deliver value to
+stakeholders quickly and frequently.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.mgmt.common.base/guidances/termdefinitions/effort.xmi b/praclib/temp/core.mgmt.common.base/guidances/termdefinitions/effort.xmi
new file mode 100644
index 0000000..3f4e7cc
--- /dev/null
+++ b/praclib/temp/core.mgmt.common.base/guidances/termdefinitions/effort.xmi
@@ -0,0 +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: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="-WIgtkwJN71D51FdcQs-TzQ"
+ name=",_nJSDwEvuEdunZcj9T5hrMQ" guid="-WIgtkwJN71D51FdcQs-TzQ" version="7.2.0">
+ <mainDescription><p>
+ Indicates how long it will take the team member(s) assigned to the work item to do the work. Typically uses the units
+ of actual days or actual hours.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.mgmt.common.base/guidances/termdefinitions/milestone.xmi b/praclib/temp/core.mgmt.common.base/guidances/termdefinitions/milestone.xmi
new file mode 100644
index 0000000..3ff4e2a
--- /dev/null
+++ b/praclib/temp/core.mgmt.common.base/guidances/termdefinitions/milestone.xmi
@@ -0,0 +1,10 @@
+<?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="-9fXEOvMc4t7y6s5GscBD1Q"
+ name=",_ByXNcEvqEdunZcj9T5hrMQ" guid="-9fXEOvMc4t7y6s5GscBD1Q">
+ <mainDescription><p>
+ The point at which an iteration or phase formally ends, thus providing a check-point for whether the project is ready
+ to move to the next iteration or phase.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.mgmt.common.base/guidances/termdefinitions/risk.xmi b/praclib/temp/core.mgmt.common.base/guidances/termdefinitions/risk.xmi
new file mode 100644
index 0000000..6a3a666
--- /dev/null
+++ b/praclib/temp/core.mgmt.common.base/guidances/termdefinitions/risk.xmi
@@ -0,0 +1,10 @@
+<?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: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="-hOtatvr8wIjqW8UD0MSGhQ"
+ name="risk,_ii2LUEvGEdunZcj9T5hrMQ" guid="-hOtatvr8wIjqW8UD0MSGhQ" changeDate="2006-09-29T14:58:30.374-0400"
+ version="1.0.0">
+ <mainDescription>A condition that can potentially affect, prevent, or limit a project's success. Project risks may be seen as threats or
+opportunities.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.mgmt.common.base/guidances/termdefinitions/scope.xmi b/praclib/temp/core.mgmt.common.base/guidances/termdefinitions/scope.xmi
new file mode 100644
index 0000000..28d79ab
--- /dev/null
+++ b/praclib/temp/core.mgmt.common.base/guidances/termdefinitions/scope.xmi
@@ -0,0 +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: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="-h1poMaxtQbmg6hD5772oVw"
+ name=",_t7JOkEvtEdunZcj9T5hrMQ" guid="-h1poMaxtQbmg6hD5772oVw" changeDate="2006-09-24T11:22:03.239-0700">
+ <mainDescription>A description of the breadth of a system's behavior, specifying the boundaries of the problem domain or system.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.mgmt.common.base/guidances/termdefinitions/work_breakdown_structure.xmi b/praclib/temp/core.mgmt.common.base/guidances/termdefinitions/work_breakdown_structure.xmi
new file mode 100644
index 0000000..81c3465
--- /dev/null
+++ b/praclib/temp/core.mgmt.common.base/guidances/termdefinitions/work_breakdown_structure.xmi
@@ -0,0 +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.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="-KQTbqDSJXR8KLBxIgGVquA"
+ name=",_RK9nwEvtEdunZcj9T5hrMQ" guid="-KQTbqDSJXR8KLBxIgGVquA">
+ <mainDescription>Breaks the project into individual units of work, or tasks, for which cost, milestones, and activities can be allocated and
+tracked.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.mgmt.common.base/plugin.xmi b/praclib/temp/core.mgmt.common.base/plugin.xmi
new file mode 100644
index 0000000..9dc3e3b
--- /dev/null
+++ b/praclib/temp/core.mgmt.common.base/plugin.xmi
@@ -0,0 +1,194 @@
+<?xml version="1.0" encoding="UTF-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.4/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.2.0" xmlns:epf="http://www.eclipse.org/epf"
+ epf:version="1.2.0">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_0UM7YJ-VEdy3Nc4rvuj7bA"
+ guid="_0UM7YJ-VEdy3Nc4rvuj7bA">
+ <resourceDescriptors xmi:id="_RPuOIEv8EdunZcj9T5hrMQ" id="-h1poMaxtQbmg6hD5772oVw"
+ uri="guidances/termdefinitions/scope.xmi"/>
+ <resourceDescriptors xmi:id="_nGn68PL5Edm6Nvont3uinw" id="_7ygXoMM3EdmSIPI87WLu3g"
+ uri="guidances/concepts/metrics.xmi"/>
+ <resourceDescriptors xmi:id="_wVAzgEvuEdunZcj9T5hrMQ" id="-WIgtkwJN71D51FdcQs-TzQ"
+ uri="guidances/termdefinitions/effort.xmi"/>
+ <resourceDescriptors xmi:id="_VEO_YEvtEdunZcj9T5hrMQ" id="-KQTbqDSJXR8KLBxIgGVquA"
+ uri="guidances/termdefinitions/work_breakdown_structure.xmi"/>
+ <resourceDescriptors xmi:id="_WrOAgDkDEduxovfWMDsntw" id="-vi8wxwxVZLY0SMPFxZjD7A"
+ uri="guidances/concepts/iteration.xmi"/>
+ <resourceDescriptors xmi:id="_nDjY0PL5Edm6Nvont3uinw" id="_u6enMMM1EdmSIPI87WLu3g"
+ uri="guidances/concepts/risk.xmi"/>
+ <resourceDescriptors xmi:id="_5qob4EvqEdunZcj9T5hrMQ" id="-qZE4XgeMK93LmJMKuQWGFg"
+ uri="guidances/termdefinitions/agile.xmi"/>
+ <resourceDescriptors xmi:id="_TsOyAEvqEdunZcj9T5hrMQ" id="-9fXEOvMc4t7y6s5GscBD1Q"
+ uri="guidances/termdefinitions/milestone.xmi"/>
+ <resourceDescriptors xmi:id="_CY764BEdEdqY7JB6N6CW2w" id="_CYRMgBEdEdqY7JB6N6CW2w"
+ uri="guidances/guidelines/agile_estimation.xmi"/>
+ <resourceDescriptors xmi:id="_QFd3MK_OEdy9cPK11VzBuQ" id="-HhGIkAPjHSIxnPzI3cyDnQ"
+ uri="guidances/guidelines/managing_risks.xmi"/>
+ <resourceDescriptors xmi:id="_fEnwQc6dEdyuBO4ZIzcyig" id="-BUHtqig5wrabMIpZgZChMg"
+ uri="guidances/supportingmaterials/mgmt_references.xmi"/>
+ <resourceDescriptors xmi:id="_XcJIYCdCEduIsqH1Q6ZuqA" id="-4VJ_0upihz-bR7VRlm63Vw"
+ uri="workproducts/risk_list.xmi"/>
+ <resourceDescriptors xmi:id="_qjj5oEvrEdunZcj9T5hrMQ" id="-hOtatvr8wIjqW8UD0MSGhQ"
+ uri="guidances/termdefinitions/risk.xmi"/>
+ <resourceDescriptors xmi:id="_JNr6YDIeEduDTv4Y1akVTA" id="-gqNN4DnROmJpgKtrdguhpg"
+ uri="guidances/checklists/risk_list.xmi"/>
+ <resourceDescriptors xmi:id="_dWGwgC8FEduzydamRseoUw" id="-OugFZJszm73z0_KSwRXZPw"
+ uri="guidances/templates/risk_list.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_0TmecJ-VEdy3Nc4rvuj7bA" name="core.mgmt.common.base"
+ guid="_0TmecJ-VEdy3Nc4rvuj7bA" changeDate="2008-02-11T16:02:04.281-0500">
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_0TmecZ-VEdy3Nc4rvuj7bA"
+ name="Content" guid="_0TmecZ-VEdy3Nc4rvuj7bA">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_0Tmecp-VEdy3Nc4rvuj7bA"
+ name="Categories" guid="_0Tmecp-VEdy3Nc4rvuj7bA">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_0Tmec5-VEdy3Nc4rvuj7bA"
+ name="Domains" guid="_0Tmec5-VEdy3Nc4rvuj7bA"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_0TmedJ-VEdy3Nc4rvuj7bA"
+ name="Disciplines" guid="_0TmedJ-VEdy3Nc4rvuj7bA"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_0TmedZ-VEdy3Nc4rvuj7bA"
+ name="RoleSets" guid="_0TmedZ-VEdy3Nc4rvuj7bA"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_0Tmedp-VEdy3Nc4rvuj7bA"
+ name="WP Types" guid="_0Tmedp-VEdy3Nc4rvuj7bA"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_0Tmed5-VEdy3Nc4rvuj7bA"
+ name="Tools" guid="_0Tmed5-VEdy3Nc4rvuj7bA"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_0TmeeJ-VEdy3Nc4rvuj7bA"
+ name="StandardCategories" guid="_0TmeeJ-VEdy3Nc4rvuj7bA"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_0TmeeZ-VEdy3Nc4rvuj7bA"
+ name="CustomCategories" guid="_0TmeeZ-VEdy3Nc4rvuj7bA">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_0Tmeep-VEdy3Nc4rvuj7bA"
+ name="Hidden" guid="_0Tmeep-VEdy3Nc4rvuj7bA">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_0Tmee5-VEdy3Nc4rvuj7bA"
+ name="Custom Categories" guid="_0Tmee5-VEdy3Nc4rvuj7bA" categorizedElements="_pdBX8NjkEdyAi9EWyDeJBg"/>
+ </childPackages>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_pdBX8NjkEdyAi9EWyDeJBg"
+ name="contributions_to_nav_building_blocks" guid="_pdBX8NjkEdyAi9EWyDeJBg"
+ presentationName="Contributions to Navigation Building Blocks" categorizedElements="_r9NcwNjkEdyAi9EWyDeJBg _-_FLMNjkEdyAi9EWyDeJBg _UXEigOGjEdyhmsbt0Xyl8A _bTkakOGjEdyhmsbt0Xyl8A _hHzDAOGjEdyhmsbt0Xyl8A"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_r9NcwNjkEdyAi9EWyDeJBg"
+ name="guideline_list.assign" guid="_r9NcwNjkEdyAi9EWyDeJBg" variabilityType="contributes"
+ categorizedElements="_CGHskBEdEdqY7JB6N6CW2w _VNxL4ACsEdu8m4dIntu6jA">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4ZcRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_-_FLMNjkEdyAi9EWyDeJBg"
+ name="concept_list.assign" guid="_-_FLMNjkEdyAi9EWyDeJBg" variabilityType="contributes"
+ categorizedElements="_lam4ADkBEduxovfWMDsntw _0mYYkMlgEdmt3adZL5Dmdw _0bsLgMlgEdmt3adZL5Dmdw">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4Y8RdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_UXEigOGjEdyhmsbt0Xyl8A"
+ name="artifact_list.assign" guid="_UXEigOGjEdyhmsbt0Xyl8A" variabilityType="contributes"
+ categorizedElements="_Ckay8Cc_EduIsqH1Q6ZuqA">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4YMRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_bTkakOGjEdyhmsbt0Xyl8A"
+ name="checklist_list.assign" guid="_bTkakOGjEdyhmsbt0Xyl8A" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_pGt9MMReEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_hHzDAOGjEdyhmsbt0Xyl8A"
+ name="template_list.assign" guid="_hHzDAOGjEdyhmsbt0Xyl8A" variabilityType="contributes"
+ categorizedElements="_MIUO0C8FEduzydamRseoUw">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4Z8RdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_0TmefJ-VEdy3Nc4rvuj7bA"
+ name="CoreContent" guid="_0TmefJ-VEdy3Nc4rvuj7bA">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_QsmM8J-ZEdywNOckqfsZQg"
+ name="Management Open Source Guidance" guid="_QsmM8J-ZEdywNOckqfsZQg">
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_0mYYkMlgEdmt3adZL5Dmdw"
+ name="metrics" guid="_0mYYkMlgEdmt3adZL5Dmdw" briefDescription="A metric is used to interpret measurements so that team members and stakeholders can know the state of the project."
+ presentationName="Metrics">
+ <presentation xmi:id="_7ygXoMM3EdmSIPI87WLu3g" href="uma://_7ygXoMM3EdmSIPI87WLu3g#_7ygXoMM3EdmSIPI87WLu3g"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_nJSDwEvuEdunZcj9T5hrMQ"
+ name="effort" guid="_nJSDwEvuEdunZcj9T5hrMQ" presentationName="effort">
+ <presentation xmi:id="-WIgtkwJN71D51FdcQs-TzQ" href="uma://-WIgtkwJN71D51FdcQs-TzQ#-WIgtkwJN71D51FdcQs-TzQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_t7JOkEvtEdunZcj9T5hrMQ"
+ name="scope" guid="_t7JOkEvtEdunZcj9T5hrMQ" presentationName="scope">
+ <presentation xmi:id="-h1poMaxtQbmg6hD5772oVw" href="uma://-h1poMaxtQbmg6hD5772oVw#-h1poMaxtQbmg6hD5772oVw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_RK9nwEvtEdunZcj9T5hrMQ"
+ name="work_breakdown_structure" guid="_RK9nwEvtEdunZcj9T5hrMQ" presentationName="work breakdown structure">
+ <presentation xmi:id="-KQTbqDSJXR8KLBxIgGVquA" href="uma://-KQTbqDSJXR8KLBxIgGVquA#-KQTbqDSJXR8KLBxIgGVquA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_lam4ADkBEduxovfWMDsntw"
+ name="iteration" guid="_lam4ADkBEduxovfWMDsntw" briefDescription="An iteration is a set period of time within a project in which you produce a stable, executable version of the product, together with any other supporting documentation, install scripts, or similar, necessary to use this release. Also referred to as a cycle or a timebox."
+ presentationName="Iteration">
+ <presentation xmi:id="-vi8wxwxVZLY0SMPFxZjD7A" href="uma://-vi8wxwxVZLY0SMPFxZjD7A#-vi8wxwxVZLY0SMPFxZjD7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_0bsLgMlgEdmt3adZL5Dmdw"
+ name="risk" guid="_0bsLgMlgEdmt3adZL5Dmdw" briefDescription="A risk is whatever may stand in the way to success, and is currently unknown or uncertain. Usually, a risk is qualified by the probability of occurrence and the impact in the project, if it occurs."
+ presentationName="Risk">
+ <presentation xmi:id="_u6enMMM1EdmSIPI87WLu3g" href="uma://_u6enMMM1EdmSIPI87WLu3g#_u6enMMM1EdmSIPI87WLu3g"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_3PJ38EvqEdunZcj9T5hrMQ"
+ name="agile" guid="_3PJ38EvqEdunZcj9T5hrMQ" presentationName="agile">
+ <presentation xmi:id="-qZE4XgeMK93LmJMKuQWGFg" href="uma://-qZE4XgeMK93LmJMKuQWGFg#-qZE4XgeMK93LmJMKuQWGFg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_ByXNcEvqEdunZcj9T5hrMQ"
+ name="milestone" guid="_ByXNcEvqEdunZcj9T5hrMQ" presentationName="milestone">
+ <presentation xmi:id="-9fXEOvMc4t7y6s5GscBD1Q" href="uma://-9fXEOvMc4t7y6s5GscBD1Q#-9fXEOvMc4t7y6s5GscBD1Q"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_CGHskBEdEdqY7JB6N6CW2w"
+ name="agile_estimation" guid="_CGHskBEdEdqY7JB6N6CW2w" briefDescription="	
This guideline explains the three key concepts of agile estimation and how they relate to each other. It describes agile estimation concepts of size, velocity, and effort."
+ presentationName="Agile Estimation">
+ <presentation xmi:id="_CYRMgBEdEdqY7JB6N6CW2w" href="uma://_CYRMgBEdEdqY7JB6N6CW2w#_CYRMgBEdEdqY7JB6N6CW2w"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_VNxL4ACsEdu8m4dIntu6jA"
+ name="managing_risks" guid="_VNxL4ACsEdu8m4dIntu6jA" briefDescription="This is a fundamental practice that project managers should consider in their projects. Identifying and minimizing risks early in the project lifecycle is key factor for project success."
+ presentationName="Managing Risks">
+ <presentation xmi:id="-HhGIkAPjHSIxnPzI3cyDnQ" href="uma://-HhGIkAPjHSIxnPzI3cyDnQ#-HhGIkAPjHSIxnPzI3cyDnQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="_JlTPUM6aEdyuBO4ZIzcyig"
+ name="mgmt_references" guid="_JlTPUM6aEdyuBO4ZIzcyig" briefDescription="Additional references that may be useful, including books, method plug-ins, and commercial methodology products."
+ presentationName="References">
+ <presentation xmi:id="-BUHtqig5wrabMIpZgZChMg" href="uma://-BUHtqig5wrabMIpZgZChMg#-BUHtqig5wrabMIpZgZChMg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_ii2LUEvGEdunZcj9T5hrMQ"
+ name="risk" guid="_ii2LUEvGEdunZcj9T5hrMQ" presentationName="risk">
+ <presentation xmi:id="-hOtatvr8wIjqW8UD0MSGhQ" href="uma://-hOtatvr8wIjqW8UD0MSGhQ#-hOtatvr8wIjqW8UD0MSGhQ"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_lFkpUOFlEdyhmsbt0Xyl8A"
+ name="Management Open Source Work Products" guid="_lFkpUOFlEdyhmsbt0Xyl8A">
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_Ckay8Cc_EduIsqH1Q6ZuqA"
+ name="risk_list" guid="_Ckay8Cc_EduIsqH1Q6ZuqA" briefDescription="This artifact is a sorted list of known and open risks to the project, sorted in order of importance and associated with specific mitigation or contingency actions. "
+ presentationName="Risk List" conceptsAndPapers="_0bsLgMlgEdmt3adZL5Dmdw"
+ checklists="_7BZa0DIdEduDTv4Y1akVTA">
+ <presentation xmi:id="-4VJ_0upihz-bR7VRlm63Vw" href="uma://-4VJ_0upihz-bR7VRlm63Vw#-4VJ_0upihz-bR7VRlm63Vw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Checklist" xmi:id="_7BZa0DIdEduDTv4Y1akVTA"
+ name="risk_list" guid="_7BZa0DIdEduDTv4Y1akVTA" briefDescription="This checklist provides guidance on assessing that all possible risks in a project have been considered."
+ presentationName="Risk List">
+ <presentation xmi:id="-gqNN4DnROmJpgKtrdguhpg" href="uma://-gqNN4DnROmJpgKtrdguhpg#-gqNN4DnROmJpgKtrdguhpg"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_onU40OFlEdyhmsbt0Xyl8A"
+ name="Management Resources (Templates, Reports, Examples)" guid="_onU40OFlEdyhmsbt0Xyl8A">
+ <contentElements xsi:type="org.eclipse.epf.uma:Template" xmi:id="_MIUO0C8FEduzydamRseoUw"
+ name="risk_list" guid="_MIUO0C8FEduzydamRseoUw" briefDescription="A list or table containing risk attributes. As it is usual to rank risks by priority, spreadsheets may be an alternative to capture risks"
+ presentationName="Risk List" conceptsAndPapers="_0bsLgMlgEdmt3adZL5Dmdw">
+ <presentation xmi:id="-OugFZJszm73z0_KSwRXZPw" href="uma://-OugFZJszm73z0_KSwRXZPw#-OugFZJszm73z0_KSwRXZPw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_m9VsYONLEdyhso0n1lT29w"
+ name="risk_list.tpl" guid="_m9VsYONLEdyhso0n1lT29w" variabilityType="contributes"
+ variabilityBasedOnElement="_Ckay8Cc_EduIsqH1Q6ZuqA" templates="_MIUO0C8FEduzydamRseoUw"/>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_0TmefZ-VEdy3Nc4rvuj7bA"
+ name="CapabilityPatterns" guid="_0TmefZ-VEdy3Nc4rvuj7bA"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_0Tmefp-VEdy3Nc4rvuj7bA"
+ name="DeliveryProcesses" guid="_0Tmefp-VEdy3Nc4rvuj7bA"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_0Tmef5-VEdy3Nc4rvuj7bA"
+ name="ProcessContributions" guid="_0Tmef5-VEdy3Nc4rvuj7bA"/>
+ <bases href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno4EKmEdyrauqpmnA8jQ"/>
+ <bases href="uma://_iVydgENdEdy245g62lfWcA#_iVydgENdEdy245g62lfWcA"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/core.mgmt.common.base/workproducts/risk_list.xmi b/praclib/temp/core.mgmt.common.base/workproducts/risk_list.xmi
new file mode 100644
index 0000000..60c3f87
--- /dev/null
+++ b/praclib/temp/core.mgmt.common.base/workproducts/risk_list.xmi
@@ -0,0 +1,20 @@
+<?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="-4VJ_0upihz-bR7VRlm63Vw"
+ name="risk_list,_Ckay8Cc_EduIsqH1Q6ZuqA" guid="-4VJ_0upihz-bR7VRlm63Vw" changeDate="2008-02-22T17:35:02.281-0500"
+ version="7.2.0">
+ <mainDescription><p>
+ This list identifies, in decreasing order of priority, all the <a class="elementLinkWithUserText" href="./../../openup/guidances/termdefinitions/risk_33255339.html" guid="_ii2LUEvGEdunZcj9T5hrMQ">risks</a> associated to a project.&nbsp;It serves as a focal point for project
+ activities and is the basis around which iterations are organized.
+</p>
+<p>
+ See <a class="elementLinkWithType" href="./../../openup/guidances/concepts/risk_AF5840DA.html" guid="_0bsLgMlgEdmt3adZL5Dmdw">Concept: Risk</a>&nbsp;for more details.<!--EndFragment-->
+</p></mainDescription>
+ <keyConsiderations><p>
+ This list should capture the critical and serious risks. If you find this list extending beyond 20, carefully consider
+ whether they are really serious risks. Tracking more than 20 risks is an onerous task.
+</p></keyConsiderations>
+ <purpose>To&nbsp;capture the perceived risks to the success of the project.</purpose>
+</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/praclib/temp/core.mgmt.slot.base/.project b/praclib/temp/core.mgmt.slot.base/.project
new file mode 100644
index 0000000..db3c67b
--- /dev/null
+++ b/praclib/temp/core.mgmt.slot.base/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>core.mgmt.slot.base</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/core.mgmt.slot.base/guidances/examples/resources/ex_work_items_list.xls b/praclib/temp/core.mgmt.slot.base/guidances/examples/resources/ex_work_items_list.xls
new file mode 100644
index 0000000..234f2a5
--- /dev/null
+++ b/praclib/temp/core.mgmt.slot.base/guidances/examples/resources/ex_work_items_list.xls
Binary files differ
diff --git a/praclib/temp/core.mgmt.slot.base/guidances/guidelines/resources/work_item_prioritization_diagram.jpg b/praclib/temp/core.mgmt.slot.base/guidances/guidelines/resources/work_item_prioritization_diagram.jpg
new file mode 100644
index 0000000..12f9048
--- /dev/null
+++ b/praclib/temp/core.mgmt.slot.base/guidances/guidelines/resources/work_item_prioritization_diagram.jpg
Binary files differ
diff --git a/praclib/temp/core.mgmt.slot.base/plugin.xmi b/praclib/temp/core.mgmt.slot.base/plugin.xmi
new file mode 100644
index 0000000..035c879
--- /dev/null
+++ b/praclib/temp/core.mgmt.slot.base/plugin.xmi
@@ -0,0 +1,78 @@
+<?xml version="1.0" encoding="UTF-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.4/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.2.0" xmlns:epf="http://www.eclipse.org/epf"
+ epf:version="1.2.0">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_vJYugUfUEdyiPI8btkmvmw"
+ guid="_vJYugUfUEdyiPI8btkmvmw"/>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_vJYucEfUEdyiPI8btkmvmw" name="core.mgmt.slot.base"
+ guid="_vJYucEfUEdyiPI8btkmvmw" changeDate="2008-02-14T17:05:35.250-0500">
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_vJYucUfUEdyiPI8btkmvmw"
+ name="Content" guid="_vJYucUfUEdyiPI8btkmvmw">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_vJYuckfUEdyiPI8btkmvmw"
+ name="Categories" guid="_vJYuckfUEdyiPI8btkmvmw">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_vJYuc0fUEdyiPI8btkmvmw"
+ name="Domains" guid="_vJYuc0fUEdyiPI8btkmvmw"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_vJYudEfUEdyiPI8btkmvmw"
+ name="Disciplines" guid="_vJYudEfUEdyiPI8btkmvmw"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_vJYudUfUEdyiPI8btkmvmw"
+ name="RoleSets" guid="_vJYudUfUEdyiPI8btkmvmw"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_vJYudkfUEdyiPI8btkmvmw"
+ name="WP Types" guid="_vJYudkfUEdyiPI8btkmvmw"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_vJYud0fUEdyiPI8btkmvmw"
+ name="Tools" guid="_vJYud0fUEdyiPI8btkmvmw"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_vJYueEfUEdyiPI8btkmvmw"
+ name="StandardCategories" guid="_vJYueEfUEdyiPI8btkmvmw"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_vJYueUfUEdyiPI8btkmvmw"
+ name="CustomCategories" guid="_vJYueUfUEdyiPI8btkmvmw">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_vJYuekfUEdyiPI8btkmvmw"
+ name="Hidden" guid="_vJYuekfUEdyiPI8btkmvmw">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_vJYue0fUEdyiPI8btkmvmw"
+ name="Custom Categories" guid="_vJYue0fUEdyiPI8btkmvmw"/>
+ </childPackages>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_vJYufEfUEdyiPI8btkmvmw"
+ name="CoreContent" guid="_vJYufEfUEdyiPI8btkmvmw">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_xo1MYEfUEdyiPI8btkmvmw"
+ name="Management Work Product Slots" guid="_xo1MYEfUEdyiPI8btkmvmw">
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_RJMUcNpUEdyzZqGyZ7hwdw"
+ name="project_defiinition_and_scope_slot" guid="_RJMUcNpUEdyzZqGyZ7hwdw"
+ briefDescription="This artifact serves as an abstraction of high level artifacts that define the project and its scope. Typical examples of such artifacts could be: project definition, high level project schedule identifying major milestones and major deliverables."
+ presentationName="[Project Definition and Scope]"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_kf7foNpUEdyzZqGyZ7hwdw"
+ name="project_status_slot" guid="_kf7foNpUEdyzZqGyZ7hwdw" briefDescription="This artifact serves as an abstraction for any type of status report or assessment of the project's progress. This includes both internal assessments, as well as those of interest to the project sponsors."
+ presentationName="[Project Status]"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_0TkXgNpUEdyzZqGyZ7hwdw"
+ name="project_risk_slot" guid="_0TkXgNpUEdyzZqGyZ7hwdw" briefDescription="This artifact serves as an abstraction for artifacts that list, track, and manage project risk, such as a risk lists or risk log."
+ presentationName="[Project Risk]"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_1QZI8EfUEdyiPI8btkmvmw"
+ name="project_work_slot" guid="_1QZI8EfUEdyiPI8btkmvmw" briefDescription="This artifact serves as an abstraction for any type of work being done on the project. It could be represented as a work items list, an operational schedule, a work breakdown structure, etc."
+ presentationName="[Project Work]"/>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_gxGj0N8-Edyhmsbt0Xyl8A"
+ name="Management Guidance Slots" guid="_gxGj0N8-Edyhmsbt0Xyl8A">
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_sLQ6AN8-Edyhmsbt0Xyl8A"
+ name="project_planning_guidance_slot" guid="_sLQ6AN8-Edyhmsbt0Xyl8A"
+ briefDescription="This guideline is a collection of additional guidance on project planning, provided by supporting practices."
+ presentationName="[Project Planning Guidance]"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_68JUYN8-Edyhmsbt0Xyl8A"
+ name="collaboration_guidance_slot" guid="_68JUYN8-Edyhmsbt0Xyl8A" briefDescription="This guideline is a collection of additional guidance on collaboration, provided by supporting practices."
+ presentationName="[Collaboration Guidance]"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_BslGYN8_Edyhmsbt0Xyl8A"
+ name="work_assignment_guidance_slot" guid="_BslGYN8_Edyhmsbt0Xyl8A"
+ briefDescription="This guideline is a collection of additional guidance on making work assignments, provided by supporting practices."
+ presentationName="[Work Assignment Guidance]"/>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_vJYufUfUEdyiPI8btkmvmw"
+ name="CapabilityPatterns" guid="_vJYufUfUEdyiPI8btkmvmw"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_vJYufkfUEdyiPI8btkmvmw"
+ name="DeliveryProcesses" guid="_vJYufkfUEdyiPI8btkmvmw"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_vJYuf0fUEdyiPI8btkmvmw"
+ name="ProcessContributions" guid="_vJYuf0fUEdyiPI8btkmvmw"/>
+ <bases href="uma://_iVydgENdEdy245g62lfWcA#_iVydgENdEdy245g62lfWcA"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/core.tech.common.assign/.project b/praclib/temp/core.tech.common.assign/.project
new file mode 100644
index 0000000..e94886c
--- /dev/null
+++ b/praclib/temp/core.tech.common.assign/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>core.tech.common.assign</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/core.tech.common.assign/plugin.xmi b/praclib/temp/core.tech.common.assign/plugin.xmi
new file mode 100644
index 0000000..93eb785
--- /dev/null
+++ b/praclib/temp/core.tech.common.assign/plugin.xmi
@@ -0,0 +1,95 @@
+<?xml version="1.0" encoding="UTF-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.4/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.2.0" xmlns:epf="http://www.eclipse.org/epf"
+ epf:version="1.2.0">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_LdRtoM3qEdyuBO4ZIzcyig"
+ guid="_LdRtoM3qEdyuBO4ZIzcyig"/>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_LdRtkM3qEdyuBO4ZIzcyig" name="core.tech.common.assign"
+ guid="_LdRtkM3qEdyuBO4ZIzcyig">
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_LdRtkc3qEdyuBO4ZIzcyig"
+ name="Content" guid="_LdRtkc3qEdyuBO4ZIzcyig">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_LdRtks3qEdyuBO4ZIzcyig"
+ name="Categories" guid="_LdRtks3qEdyuBO4ZIzcyig">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_LdRtk83qEdyuBO4ZIzcyig"
+ name="Domains" guid="_LdRtk83qEdyuBO4ZIzcyig">
+ <contentElements xsi:type="org.eclipse.epf.uma:Domain" xmi:id="_DBUoYM3_EdylYe2DrHGiXg"
+ name="test_domain.assign" guid="_DBUoYM3_EdylYe2DrHGiXg" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Domain" href="uma://_MRPloEFXEdy9ENCpSugIjA#_CsgDgK81Edy9cPK11VzBuQ"/>
+ <workProducts xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZS-0MlgEdmt3adZL5Dmdw"/>
+ <workProducts xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZfMEMlgEdmt3adZL5Dmdw"/>
+ <workProducts xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZlSsMlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Domain" xmi:id="_OYp2IM6FEdyndOCfdhe9bw"
+ name="requirements_domain.assign" guid="_OYp2IM6FEdyndOCfdhe9bw" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Domain" href="uma://_MRPloEFXEdy9ENCpSugIjA#_AIcLUK81Edy9cPK11VzBuQ"/>
+ <workProducts xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0WVxcMlgEdmt3adZL5Dmdw"/>
+ <workProducts xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_BVh9cL-CEdqb7N6KIeDL8Q"/>
+ <workProducts xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_W2SgEDR5EdutE_HNDTJk5Q"/>
+ <workProducts xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0VGbUMlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Domain" xmi:id="_w9y1MNj5EdyzZqGyZ7hwdw"
+ name="development_domain.assign" guid="_w9y1MNj5EdyzZqGyZ7hwdw" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Domain" href="uma://_MRPloEFXEdy9ENCpSugIjA#_5JQLoK80Edy9cPK11VzBuQ"/>
+ <workProducts xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_JqYbgJ01EdyQ3oTO93enUw"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_LdRtlM3qEdyuBO4ZIzcyig"
+ name="Disciplines" guid="_LdRtlM3qEdyuBO4ZIzcyig"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_LdRtlc3qEdyuBO4ZIzcyig"
+ name="RoleSets" guid="_LdRtlc3qEdyuBO4ZIzcyig"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_LdRtls3qEdyuBO4ZIzcyig"
+ name="WP Types" guid="_LdRtls3qEdyuBO4ZIzcyig"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_LdRtl83qEdyuBO4ZIzcyig"
+ name="Tools" guid="_LdRtl83qEdyuBO4ZIzcyig"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_LdRtmM3qEdyuBO4ZIzcyig"
+ name="StandardCategories" guid="_LdRtmM3qEdyuBO4ZIzcyig"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_LdRtmc3qEdyuBO4ZIzcyig"
+ name="CustomCategories" guid="_LdRtmc3qEdyuBO4ZIzcyig">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_LdRtms3qEdyuBO4ZIzcyig"
+ name="Hidden" guid="_LdRtms3qEdyuBO4ZIzcyig">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_LdRtm83qEdyuBO4ZIzcyig"
+ name="Custom Categories" guid="_LdRtm83qEdyuBO4ZIzcyig"/>
+ </childPackages>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_LdRtnM3qEdyuBO4ZIzcyig"
+ name="CoreContent" guid="_LdRtnM3qEdyuBO4ZIzcyig">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_45HpUM3-EdylYe2DrHGiXg"
+ name="Role Assignments" guid="_45HpUM3-EdylYe2DrHGiXg">
+ <contentElements xsi:type="org.eclipse.epf.uma:Role" xmi:id="_cDTBoMuaEdy1o5Xnqdh1Tg"
+ name="tester.assign_wp" guid="_cDTBoMuaEdy1o5Xnqdh1Tg" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Role" href="uma://_A118oMYaEdyXeo04os5BOw#_0ZM4MclgEdmt3adZL5Dmdw"/>
+ <responsibleFor xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZS-0MlgEdmt3adZL5Dmdw"/>
+ <responsibleFor xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZlSsMlgEdmt3adZL5Dmdw"/>
+ <responsibleFor xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZfMEMlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Role" xmi:id="_m0HpgMriEdyd6uFrFHNXhA"
+ name="analyst.assign_wp" guid="_m0HpgMriEdyd6uFrFHNXhA" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Role" href="uma://_A118oMYaEdyXeo04os5BOw#_0VxJsMlgEdmt3adZL5Dmdw"/>
+ <responsibleFor xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_BVh9cL-CEdqb7N6KIeDL8Q"/>
+ <responsibleFor xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_W2SgEDR5EdutE_HNDTJk5Q"/>
+ <responsibleFor xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0VGbUMlgEdmt3adZL5Dmdw"/>
+ <responsibleFor xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0WVxcMlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Role" xmi:id="_3GIscNj5EdyzZqGyZ7hwdw"
+ name="developer.assign_wp" guid="_3GIscNj5EdyzZqGyZ7hwdw" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Role" href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
+ <responsibleFor xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_JqYbgJ01EdyQ3oTO93enUw"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_LdRtnc3qEdyuBO4ZIzcyig"
+ name="CapabilityPatterns" guid="_LdRtnc3qEdyuBO4ZIzcyig"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_LdRtns3qEdyuBO4ZIzcyig"
+ name="DeliveryProcesses" guid="_LdRtns3qEdyuBO4ZIzcyig"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_LdRtn83qEdyuBO4ZIzcyig"
+ name="ProcessContributions" guid="_LdRtn83qEdyuBO4ZIzcyig"/>
+ <bases href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPloEFXEdy9ENCpSugIjA"/>
+ <bases href="uma://_A118oMYaEdyXeo04os5BOw#_A118oMYaEdyXeo04os5BOw"/>
+ <bases href="uma://_iVydgENdEdy245g62lfWcA#_iVydgENdEdy245g62lfWcA"/>
+ <bases href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2AAouEdyhlpBPrduOMw"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/core.tech.common.base/.project b/praclib/temp/core.tech.common.base/.project
new file mode 100644
index 0000000..1471450
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>core.tech.common.base</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/checklists/actor.xmi b/praclib/temp/core.tech.common.base/guidances/checklists/actor.xmi
new file mode 100644
index 0000000..b024df6
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/checklists/actor.xmi
@@ -0,0 +1,44 @@
+<?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="_KEldgMM1EdmSIPI87WLu3g"
+ name="actor,_0VrDEMlgEdmt3adZL5Dmdw" guid="_KEldgMM1EdmSIPI87WLu3g" changeDate="2005-07-07T01:18:05.000-0700"
+ version="7.2.0">
+ <sections xmi:id="_ytiigAYQEdubLa3RRn5f4A" name="Have you found all the actors"
+ guid="_ytiigAYQEdubLa3RRn5f4A">
+ <sectionDescription>Have you accounted for all roles in the systems environment?&nbsp; See <a class="elementLinkWithType"
+href="./../../../opn.tech.prac.rqmts_with_use_cases/guidances/guidelines/find_and_outline_actors_and_ucs_BB5516A9.html"
+ guid="_eyL0wCu-EdqSxKAVa9kmvA">Guideline: *Find and Outline Actors and Use Cases</a>&nbsp;for some questions that may help
+identify actors.</sectionDescription>
+ </sections>
+ <sections xmi:id="_AcjQMAYREdubLa3RRn5f4A" name="Is each actor involved with at least one use case"
+ guid="_AcjQMAYREdubLa3RRn5f4A">
+ <sectionDescription>If you cannot identify a use case associated with a given actor perhaps the actor should be removed, or perhaps you are
+missing a use case.</sectionDescription>
+ </sections>
+ <sections xmi:id="_P3mo8AYREdubLa3RRn5f4A" name="Can you identify at least two people, or external systems, that would play the role of a particular actor"
+ guid="_P3mo8AYREdubLa3RRn5f4A">
+ <sectionDescription>If you cannot, check if the role that the actor represents is part of another actor.&nbsp; If that is the case, you should
+merge the actors.</sectionDescription>
+ </sections>
+ <sections xmi:id="_b640oAYREdubLa3RRn5f4A" name="Will a particular actor use the system in several completely different ways"
+ guid="_b640oAYREdubLa3RRn5f4A">
+ <sectionDescription><p>
+ If true, you should probably have more than one actor.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_iOHtQAYREdubLa3RRn5f4A" name="Does the actor have several completely different purposes for using the system"
+ guid="_iOHtQAYREdubLa3RRn5f4A">
+ <sectionDescription>If true, there may be more than one actor.</sectionDescription>
+ </sections>
+ <sections xmi:id="_ptfB0AYREdubLa3RRn5f4A" name="Have you considered maintenance and administrative roles"
+ guid="_ptfB0AYREdubLa3RRn5f4A">
+ <sectionDescription>It is common to focus on the daily users of the system, and forget about administrative and maintenance roles such as
+setting up user accounts, managing access rights, performing backups, etc.&nbsp; Ensure you have captured these actors.</sectionDescription>
+ </sections>
+ <sections xmi:id="_2i_UoAYREdubLa3RRn5f4A" name="Does each actor have a clear description of its role"
+ guid="_2i_UoAYREdubLa3RRn5f4A">
+ <sectionDescription>Each actor should have a short description of the role and the main goal the actor has in using the system.</sectionDescription>
+ </sections>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/checklists/design.xmi b/praclib/temp/core.tech.common.base/guidances/checklists/design.xmi
new file mode 100644
index 0000000..2671b76
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/checklists/design.xmi
@@ -0,0 +1,135 @@
+<?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: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="_YIYIYMM1EdmSIPI87WLu3g"
+ name="design,_0XSzsMlgEdmt3adZL5Dmdw" guid="_YIYIYMM1EdmSIPI87WLu3g" changeDate="2006-09-15T12:28:43.942-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
+ some items may only be able to be addressed to 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 be performed every day. Use this checklist regularly to assure the design is robust, consistent, and
+ understandable. 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="_cKSvsD6SEduAL-bCqar_dg" name="General" guid="_cKSvsD6SEduAL-bCqar_dg">
+ <sectionDescription><p>
+ Do separate design elements have low coupling? Does each design element have high internal cohesion?
+</p>
+<p>
+ Does the design reflect the architectural objectives of the system?
+</p>
+<p>
+ Can the system be implemented from the information in the design? Has sufficient detail been included?
+</p>
+<p>
+ Is the design consistent? Does any part of the design contradict another part of it in such a way that puts the project
+ at risk?
+</p>
+<p>
+ Is the design able to accommodate future changes?
+</p>
+<p>
+ Is the design appropriate to the experience level of other team members and stakeholders, neither too simple nor too
+ advanced?
+</p>
+<p>
+ Is the design written in such a way, and is it structured well enough, so it can be maintained easily?
+</p>
+<p>
+ Does the design constrain the implementation only as much as is necessary?
+</p>
+<p>
+ Does the design describe all the behavior of the system for the requirements that are currently being addressed?
+</p>
+<p>
+ Can all parts of the design be traced back to the requirements? Can the requirements (for the current iteration) be
+ traced to design elements?
+</p>
+<p>
+ Is there an unambiguous place or places&nbsp;in the design where each behavior exists?
+</p>
+<p>
+ Are the use case flows that are currently being addressed described in the design?
+</p>
+<p>
+ Are&nbsp;complex flows outside the Basic Flow&nbsp;addressed, including exceptional cases?
+</p>
+<p>
+ Has the behavior described in the requirements that are currently being addressed&nbsp;been distributed to the correct
+ design elements?
+</p>
+<p>
+ Does the design provide enough information for test design? For example, are the collaborations between design elements
+ clear enough to create integration tests?
+</p>
+<p>
+ Have redundant areas of the design been removed so the Implementation does not contain redundant code?
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="__4O2AD6WEduAL-bCqar_dg" name="Organization and Clarity" guid="__4O2AD6WEduAL-bCqar_dg">
+ <sectionDescription><p>
+ Does the design describe the system at the appropriate level of abstraction, given the objectives? This usually means
+ the system is described at a number of different levels of&nbsp;abstraction and perspectives.
+</p>
+<p>
+ Does the design use common vocabulary and terms from the business and technical domains?
+</p>
+<p>
+ Does the design describe the behavior of the elements unambiguously to the extent that developer tests can be created
+ toverify the implementation?
+</p>
+<p>
+ Are the design's constructs, vocabulary, and semantics appropriate to the problem being solved? This usually means the
+ customer's vocabulary is used, and elements of the design are referenced in a consistent manner.
+</p>
+<p>
+ Is the design organized in a way that team members can easily find the information they're looking for?
+</p>Is the notation used to&nbsp;describe the design&nbsp;used consistently?<br />
+<p>
+ Is the design organized in a way that helps team members modify it without contending for the same part of the design?
+ That is, can mulitple people work on the design in parallel?
+</p>
+<p>
+ Are the names of elements within the design consistent and easy to interpret?
+</p>
+<p>
+ Does each design element represent a clearly defined abstraction?
+</p>
+<p>
+ Is the design as simple as it can be while fulfilling the objectives of the design and giving sufficient direction to
+ implementers?
+</p>
+<p>
+ Is the design clear enough and contain enough detail so it can be implemented?
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_dahBcD6SEduAL-bCqar_dg" name="Architecture" guid="_dahBcD6SEduAL-bCqar_dg">
+ <sectionDescription><p>
+ Is the architecture clearly called out in the design ? Can team members and stakeholders clearly identify the portion
+ of the design that is the architecture?
+</p>
+<p>
+ Are architectural mechanisms (patterns) clearly defined in the design so they're reusable and understandable?
+</p>
+<p>
+ Are architectural mechanisms used appropriately? Are they applied in all applicable circumstances?
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_kWnQ4D6SEduAL-bCqar_dg" name="Subsystems" guid="_kWnQ4D6SEduAL-bCqar_dg">
+ <sectionDescription><p>
+ Do all elements within a subsystem have private visibility? In other words, is the subsystem interface the&nbsp;only
+ way to access the behavior of elements inside the subsystem?
+</p>
+<p>
+ Is the interface for each subsystem clearly defined in the design?
+</p>
+<p>
+ Are the subsystem dependencies documented?&nbsp;
+</p></sectionDescription>
+ </sections>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/checklists/general_requirements.xmi b/praclib/temp/core.tech.common.base/guidances/checklists/general_requirements.xmi
new file mode 100644
index 0000000..ed6a521
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/checklists/general_requirements.xmi
@@ -0,0 +1,89 @@
+<?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="-2o1pXjHpSEPN_rohLce5jA"
+ name="good_requirements_1,_jxn9EO0HEdqHTdbLTmC5IQ" guid="-2o1pXjHpSEPN_rohLce5jA"
+ authors="Chris Sibbald" changeDate="2006-04-10T08:07:04.000-0700" changeDescription="Added checklist for good requirements in accordance with Feb. 23, 2006 minutes of RM SIG."
+ version="0.1">
+ <sections xmi:id="_jxuDsu0HEdqHTdbLTmC5IQ" name="Is the requirement correct?" guid="_jxuDsu0HEdqHTdbLTmC5IQ">
+ <sectionDescription><p>
+ Does the requirement specify a true need, desire, or obligation?
+</p>
+<p>
+ Have you identified the "root cause" for the requirement?
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_jxuDs-0HEdqHTdbLTmC5IQ" name="Is the requirement complete?" guid="_jxuDs-0HEdqHTdbLTmC5IQ">
+ <sectionDescription><p>
+ Is the requirement stated as a complete sentence?
+</p>
+<p>
+ Is the requirement stated entirely in one place, in a manner that does not force the reader to look at additional
+ information to understand the requirement?
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_jxuDse0HEdqHTdbLTmC5IQ" name="Is the requirement clear?" guid="_jxuDse0HEdqHTdbLTmC5IQ">
+ <sectionDescription><p>
+ Is the requirement unambiguous and not confusing?
+</p>
+<p>
+ Does everyone agree on the meaning of the requirement?
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_jxuDt-0HEdqHTdbLTmC5IQ" name="Is the requirement consistent"
+ guid="_jxuDt-0HEdqHTdbLTmC5IQ">
+ <sectionDescription><p>
+ Is the requirement in conflict with other requirements?
+</p>
+<p>
+ Is the terminology used consistent with other requirements and glossary terms?
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_jxuDte0HEdqHTdbLTmC5IQ" name="Is the requirement verifiable?"
+ guid="_jxuDte0HEdqHTdbLTmC5IQ">
+ <sectionDescription><p>
+ Can we determine whether the system satisfies the requirement?
+</p>
+<p>
+ Is it possible to define a clear, unambiguous&nbsp;pass/fail criterion?
+</p>
+<p>
+ Is it possible to determine if the requirement has been met via inspection, analysis, demonstration or test?
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_jxuDtu0HEdqHTdbLTmC5IQ" name="Is the requirement traceable?"
+ guid="_jxuDtu0HEdqHTdbLTmC5IQ">
+ <sectionDescription><p>
+ Is the requirement uniquely identified so it can be unambiguously referenced?
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_jxuDtO0HEdqHTdbLTmC5IQ" name="Is the requirement feasible?" guid="_jxuDtO0HEdqHTdbLTmC5IQ">
+ <sectionDescription><p>
+ Can the requirement be satisfied within cost and on schedule?
+</p>
+<p>
+ Is the requirement technically feasible with current technology?
+</p>
+<p>
+ Is the requirement physically achievable?
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_jxuDsO0HEdqHTdbLTmC5IQ" name="Is the requirement design independent?"
+ guid="_jxuDsO0HEdqHTdbLTmC5IQ">
+ <sectionDescription><p>
+ Are all requirements that impose constraints on the design, limiting design options,&nbsp;justified?
+</p>
+<p>
+ Is the requirement stated in such that there is more than one way that it can be satisfied?
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_gRb_IJEvEdui_vx06Mo1eg" name="Is the requirement atomic?" guid="_gRb_IJEvEdui_vx06Mo1eg">
+ <sectionDescription><p>
+ Does the requirement statement define exactly one requirement?
+</p>
+<p>
+ Is the requirement statement free of conjunctions (and, or, but) that may indicate multiple requirements?
+</p></sectionDescription>
+ </sections>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/checklists/system_wide_requirements.xmi b/praclib/temp/core.tech.common.base/guidances/checklists/system_wide_requirements.xmi
new file mode 100644
index 0000000..f0563b6
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/checklists/system_wide_requirements.xmi
@@ -0,0 +1,111 @@
+<?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="-kw2vYHKDkWv2tZrDMrBPNA"
+ name="new_checklist,_Vael8CGMEdu3VKXZx45D3A" guid="-kw2vYHKDkWv2tZrDMrBPNA" version="1.0.0">
+ <sections xmi:id="_kTZiACGMEdu3VKXZx45D3A" name="Have global functional requirements been captured and validated?"
+ guid="_kTZiACGMEdu3VKXZx45D3A">
+ <sectionDescription><ul>
+ <li>
+ Are functional requirements that affect multiple use cases identified? For example, all use cases may be subject to
+ access control, audit trails, general responses to abnormal situations (overflow, communication facilities, error
+ handling and recovery and so on).
+ </li>
+ <li>
+ For each of these requirements, are they behavioral and could be better captured in a common use case?
+ </li>
+ <li>
+ For each of these functions, is it clear how input and shared data generate output and shared data?
+ </li>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_-eJXoCGMEdu5QMD9IAHRNg" name="Have usability requirements been captured and validated?"
+ guid="_-eJXoCGMEdu5QMD9IAHRNg">
+ <sectionDescription><ul>
+ <li>
+ Have the efficiency and usability factors of user tasks been considered?&nbsp;
+ </li>
+ <li>
+ Are the requirements specified in a way that is verifiable, including metrics and target values?
+ </li>
+ <li>
+ Have&nbsp;novice as well as expert users been considered?
+ </li>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_QCbtwCGNEdubdKsr57an1g" name="Have reliability requirements been captured and validated?"
+ guid="_QCbtwCGNEdubdKsr57an1g">
+ <sectionDescription><ul>
+ <li>
+ Have reliability requirements been specified as measurable requirements or prioritized design goals?
+ </li>
+ <li>
+ Is error checking and recovery required?
+ </li>
+ <li>
+ Are undesired events considered and their required responses specified?
+ </li>
+ <li>
+ Are initial or special states considered (such as cold starts or abnormal termination)?
+ </li>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_e3pOgCGNEdubdKsr57an1g" name="Have performance requirements been captured and validated?"
+ guid="_e3pOgCGNEdubdKsr57an1g">
+ <sectionDescription><ul>
+ <li>
+ Have the resource and performance margin requirements been stated (for example speed, response time, recovery time
+ of various software functions)?
+ </li>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_l8CeUCGNEdubdKsr57an1g" name="Have supportability requirements been captured and validated?"
+ guid="_l8CeUCGNEdubdKsr57an1g">
+ <sectionDescription><ul>
+ <li>
+ Are there any requirements that will enhance the supportability or maintainability of the system being built?
+ </li>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_wIttsCGNEdubdKsr57an1g" name="Have constraints been captured and validated?"
+ guid="_wIttsCGNEdubdKsr57an1g">
+ <sectionDescription><ul>
+ <li>
+ Are there any required standards in effect, implementation language, policies for database integrity, resource
+ limits, operating environments, and so forth?
+ </li>
+ <li>
+ Has the use of inherited design or code or pre-selected tools been specified?
+ </li>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_5j6c0CGNEdubdKsr57an1g" name="Have external interfaces been identified?"
+ guid="_5j6c0CGNEdubdKsr57an1g">
+ <sectionDescription><ul>
+ <li>
+ Is it clear how the software interacts with people, the system's hardware, other hardware, and other software?
+ </li>
+ <li>
+ Have all critical data elements that cross system boundaries been identified for those scenarios that will be
+ implemented&nbsp;next?
+ </li>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_H052MCGOEdubdKsr57an1g" name="Have business rules been captured and validated?"
+ guid="_H052MCGOEdubdKsr57an1g">
+ <sectionDescription><ul>
+ <li>
+ Are the rules relevant to the use cases identified (data validation rules, formulas, flow decisions)?
+ </li>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_NBM78CGOEdubdKsr57an1g" name="Have applicable standards and regulatory compliance requirements been identified?"
+ guid="_NBM78CGOEdubdKsr57an1g">
+ <sectionDescription><ul>
+ <li>
+ Have all requirements derived from existing standard and regulations been specified?
+ </li>
+</ul></sectionDescription>
+ </sections>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/checklists/test_case.xmi b/praclib/temp/core.tech.common.base/guidances/checklists/test_case.xmi
new file mode 100644
index 0000000..ad2067c
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/checklists/test_case.xmi
@@ -0,0 +1,58 @@
+<?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: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="_kwHAgMPbEdmbOvqy4O0adg"
+ name="test_case,_0Zxf8MlgEdmt3adZL5Dmdw" guid="_kwHAgMPbEdmbOvqy4O0adg" changeDate="2005-07-07T13:45:15.861-0700"
+ version="1.0.0">
+ <sections xmi:id="_yXujsLcOEduFFo_97woSMw" name="General" guid="_yXujsLcOEduFFo_97woSMw">
+ <sectionDescription><ul>
+ <li>
+ Does the Test Case identify the requirement it evaluates?&nbsp; This linking might be informal through a naming
+ convention or formalized through a requirements traceability matrix.
+ </li>
+ <li>
+ Does the Test Case reference the preconditions and postconditions that apply to it?
+ </li>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_Hv2n0BBbEduXULqRagzBHA" name="Name" guid="_Hv2n0BBbEduXULqRagzBHA">
+ <sectionDescription><ul>
+ <li>
+ Is the&nbsp;Test Case name unique?
+ </li>
+ <li>
+ Does&nbsp;the name express a test condition or&nbsp;an expected result?
+ </li>
+ <li>
+ Is&nbsp;it unambiguous to a stakeholder?
+ </li>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_3i-gkLcOEduFFo_97woSMw" name="Brief Description" guid="_3i-gkLcOEduFFo_97woSMw">
+ <sectionDescription><ul class="noindent">
+ <li>
+ Is the logical test condition clearly identified in the description?
+ </li>
+ <li>
+ Does the description clearly&nbsp;state the expected result?
+ </li>
+ <li>
+ Is the expected result stated as a concrete&nbsp;outcome?
+ </li>
+ <li>
+ Can a casual reader distinguish this Test Case from a similar one?
+ </li>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_4uresLcOEduFFo_97woSMw" name="Test Data Needs" guid="_4uresLcOEduFFo_97woSMw">
+ <sectionDescription><ul>
+ <li>
+ Does the Test Case note the kinds of test data required to implement a detailed Test Script?
+ </li>
+ <li>
+ Are&nbsp;the test data type, uniqueness, and quality sufficiently explained?
+ </li>
+</ul></sectionDescription>
+ </sections>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/checklists/test_data.xmi b/praclib/temp/core.tech.common.base/guidances/checklists/test_data.xmi
new file mode 100644
index 0000000..f4453d6
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/checklists/test_data.xmi
@@ -0,0 +1,21 @@
+<?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: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="-GNUrr3mpSwOOaOKWSuftMg"
+ name="new_checklist,_KZQJMBhBEduxCP6DVVLxsA" guid="-GNUrr3mpSwOOaOKWSuftMg">
+ <sections xmi:id="_U06PwBhBEduxCP6DVVLxsA" name="Has test data been provided for the test cases to be implemented"
+ guid="_U06PwBhBEduxCP6DVVLxsA"/>
+ <sections xmi:id="_XBmw0BhBEduxCP6DVVLxsA" name="Does the test data support boundary testing"
+ guid="_XBmw0BhBEduxCP6DVVLxsA"/>
+ <sections xmi:id="_Yvo_8BhBEduxCP6DVVLxsA" name="Has the system under test been tested under conditions with sufficient data, insufficient data, and the wrong type of data"
+ guid="_Yvo_8BhBEduxCP6DVVLxsA"/>
+ <sections xmi:id="_a6tJUBhBEduxCP6DVVLxsA" name="Has test data been organized into production and generated data"
+ guid="_a6tJUBhBEduxCP6DVVLxsA"/>
+ <sections xmi:id="_cqj9YBhBEduxCP6DVVLxsA" name="Has test data been updated to apply to the appropriate iteration"
+ guid="_cqj9YBhBEduxCP6DVVLxsA"/>
+ <sections xmi:id="_eoWfwBhBEduxCP6DVVLxsA" name="Is the test data complete for the given test effort"
+ guid="_eoWfwBhBEduxCP6DVVLxsA"/>
+ <sections xmi:id="_h7coMBhBEduxCP6DVVLxsA" name="Has data been identified for input numeric variables, output numeric variables, arrays, and vectors"
+ guid="_h7coMBhBEduxCP6DVVLxsA"/>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/checklists/test_script.xmi b/praclib/temp/core.tech.common.base/guidances/checklists/test_script.xmi
new file mode 100644
index 0000000..5579e27
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/checklists/test_script.xmi
@@ -0,0 +1,35 @@
+<?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: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="_4LuPMMPcEdmbOvqy4O0adg"
+ name="test_script,_0Z9tMMlgEdmt3adZL5Dmdw" guid="_4LuPMMPcEdmbOvqy4O0adg" changeDate="2005-07-26T13:21:21.082-0700"
+ version="1.0.0">
+ <sections xmi:id="_DiPTsE_cEduqM_QlWBlZ_g" name="Does the test script conform to the related test case"
+ guid="_DiPTsE_cEduqM_QlWBlZ_g">
+ <sectionDescription>Ensure that the test script conforms to the specification established in the test case if one is associated with the test
+script.&nbsp; The test case captures the intent of the test; the test script must conform to this intent.</sectionDescription>
+ </sections>
+ <sections xmi:id="_KS930Bg9EduxCP6DVVLxsA" name="Is the test script testable" guid="_KS930Bg9EduxCP6DVVLxsA"/>
+ <sections xmi:id="_H-q58Bg9EduxCP6DVVLxsA" name="Is the test script reusable" guid="_H-q58Bg9EduxCP6DVVLxsA">
+ <sectionDescription>Ensure that your test scripts can be reused by designing your test scripts to maximize reuse.&nbsp; Promoting reuse takes
+different forms depending on whether you are generating, programming, or recording test scripts.</sectionDescription>
+ </sections>
+ <sections xmi:id="_5_92wE_cEduqM_QlWBlZ_g" name="Is the test script prescriptive and unambiguous"
+ guid="_5_92wE_cEduqM_QlWBlZ_g">
+ <sectionDescription>Ensure that the test script represents clear instructions on how the test must be run and how the results should be
+analyzed.&nbsp; While non-automated tests can be written in such a way that the tester can have leeway in how the test is
+precisely run, there is no room for creativity in how the test results are to be analyzed for success or failure.</sectionDescription>
+ </sections>
+ <sections xmi:id="_La5wQBg9EduxCP6DVVLxsA" name="Is the test script named consistently with your other test work products"
+ guid="_La5wQBg9EduxCP6DVVLxsA">
+ <sectionDescription>Ensure that the naming of your test scripts is consistent with other test-related work products.&nbsp; For example, if you
+are creating test classes for each of your test cases, ensure that the naming represents this relationship.&nbsp;
+Alternatively, if you are building test scripts inside of a library, use a consistent naming convention to reflect the
+library or libraries.</sectionDescription>
+ </sections>
+ <sections xmi:id="_Ng5zcBg9EduxCP6DVVLxsA" name="Does your test script provide test coverage"
+ guid="_Ng5zcBg9EduxCP6DVVLxsA">
+ <sectionDescription>Ensure that your test scripts provide test coverage consistent with the system under test.</sectionDescription>
+ </sections>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/checklists/use_case.xmi b/praclib/temp/core.tech.common.base/guidances/checklists/use_case.xmi
new file mode 100644
index 0000000..a37cf33
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/checklists/use_case.xmi
@@ -0,0 +1,123 @@
+<?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="-T2IeqdOunweffIDgL-aM0w"
+ name="use_case,_0Vk8cMlgEdmt3adZL5Dmdw" guid="-T2IeqdOunweffIDgL-aM0w" authors="Paul Bramble"
+ changeDate="2006-05-01T10:13:56.264-0700" version="0.1">
+ <copyrightStatement href="uma://_iVydgENdEdy245g62lfWcA#_uuunoPsDEdmyhNQr5STrZQ"/>
+ <sections xmi:id="_663wMNk1Edq2Q8qZoWbvGA" name="Is the use-case name meaningful and un-ambiguous?"
+ guid="_663wMNk1Edq2Q8qZoWbvGA">
+ <sectionDescription><p>
+ Does the use case have a unique name?
+</p>
+<p>
+ Is the name a verb + noun phrase (for example, Withdraw Cash)?
+</p>
+<p>
+ Does the name accurately&nbsp;summarize the&nbsp;main goal&nbsp;of the use case?
+</p>
+<p>
+ Is the name "actor independent"?
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_ZTA8QJznEduBcbjYtLtItQ" name="Does the brief description clearly describe the primary goal of the use case?"
+ guid="_ZTA8QJznEduBcbjYtLtItQ">
+ <sectionDescription><p>
+ Is it clear from the brief description what the main purpose of the use case is?
+</p>
+<p>
+ Is the "observable result of value" obvious?
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_4wJRgJznEduBcbjYtLtItQ" name="Are associated actors and information exchanged clearly defined?"
+ guid="_4wJRgJznEduBcbjYtLtItQ">
+ <sectionDescription><p>
+ Is the use case associated with one or more actors?
+</p>
+<p>
+ Is the primary, or initiating actor, defined?
+</p>
+<p>
+ Is it clear who wishes to perform the use case?
+</p>
+<p>
+ Is all information exchanged between the actor(s) and the system clearly specified?
+</p>
+<p>
+ If a "time" actor is used, are you sure you did not miss an important actor and associated use cases (such as
+ administrative or maintenance personnel that define schedule events)?
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_Qys_INk2Edq2Q8qZoWbvGA" name="Are the pre-conditions specified?"
+ guid="_Qys_INk2Edq2Q8qZoWbvGA">
+ <sectionDescription><p>
+ Does each pre-condition represent a tangible&nbsp;state&nbsp;of&nbsp;the system (for example, the Withdraw Cash use
+ case for an automated teller machine has a precondition that the user has an account)?
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_q3qV0Nk2Edq2Q8qZoWbvGA" name="Are the Basic Flow and Alternate Flows complete, correct and consistent?"
+ guid="_q3qV0Nk2Edq2Q8qZoWbvGA">
+ <sectionDescription><p>
+ Is it clear how the use case is started?
+</p>
+<p>
+ Is the triggering event clearly described?
+</p>
+<p>
+ Does the flow have a definite ending?
+</p>
+<p>
+ Does&nbsp;each step in the scenario contain&nbsp;the same level of abstraction?&nbsp;&nbsp;
+</p>
+<p>
+ Does each step in the scenario describe something that can actually happen and that the system can reasonably detect?
+</p>
+<p>
+ Does each step make&nbsp;progress towards the goal?
+</p>
+<p>
+ Are there any missing steps? Is it clear how to go from one step to the next? Does the sequence of communication
+ between the actors and the use case conform to the user's expectations?
+</p>
+<p>
+ Does each step describe how the step helps the actor achieve their goal?
+</p>
+<p>
+ Is each step technology independent? Is it free of technical details, and design decisions?
+</p>
+<p>
+ Are the steps correctly numbered?
+</p>
+<p>
+ For each alternate flow is the condition(s) for initiation of the flow clearly defined?
+</p>
+<p>
+ For each alternate flow is it clear how the use case ends or where in the basic flow that the use case resumes?
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_dnLXMNk2Edq2Q8qZoWbvGA" name="Are the post-conditions specified?"
+ guid="_dnLXMNk2Edq2Q8qZoWbvGA">
+ <sectionDescription><p>
+ If "Minimal Guarantees" are present, do they always happen when the use case completes, regardless of success? (A
+ Minimal Guarantee represents&nbsp;a condition&nbsp;that will be true when the use case ends, regardless of how it
+ terminates.)
+</p>
+<p>
+ If "Success Guarantees" are present, do they always happen when the use case completes successfully? (A Success
+ Guarantee represents a condition that will be true when the use case ends successfully, regardless of which path it
+ takes.)
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_vkbMAJzrEduBcbjYtLtItQ" name="Are applicable non-functional requirements captured?"
+ guid="_vkbMAJzrEduBcbjYtLtItQ">
+ <sectionDescription><p>
+ Are non-functional requirements (such as performance criteria) that are&nbsp;applicable to the&nbsp;use case captured
+ in the use case?
+</p>
+<p>
+ Are these non-functional requirements applicable to many use cases?&nbsp; It they are, consider capturing them in the
+ system-wide requirements specification to simplify maintenance.
+</p></sectionDescription>
+ </sections>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/checklists/use_case_model.xmi b/praclib/temp/core.tech.common.base/guidances/checklists/use_case_model.xmi
new file mode 100644
index 0000000..b8a22c4
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/checklists/use_case_model.xmi
@@ -0,0 +1,100 @@
+<?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="_MqODAMM1EdmSIPI87WLu3g"
+ name="uc_model,_0U6OEMlgEdmt3adZL5Dmdw" guid="_MqODAMM1EdmSIPI87WLu3g" changeDate="2005-07-07T11:50:06.005-0700"
+ version="1.0.0">
+ <sections xmi:id="_rLdVMAeREduWycDgioo5rg" name="Is it easy to understand what the system does by reviewing the model?"
+ guid="_rLdVMAeREduWycDgioo5rg">
+ <sectionDescription><ul>
+ <li>
+ Does the use-case model provide a clear, concise overview of the purpose and functionality of the system?
+ </li>
+ <li>
+ Are there no long chains of <i>include</i> relationships, such as when an included use case&nbsp;includes other use
+ cases? These can obscure comprehension.
+ </li>
+ <li>
+ Are&nbsp;included use cases independent of the use cases that include them?
+ </li>
+ <li>
+ If several use cases contain similar&nbsp;subflows, have you investigated whether factoring this&nbsp;common
+ behavior into an included use case will simplify the model?
+ </li>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="__kgR8AeREduWycDgioo5rg" name="Have all use cases been identified?"
+ guid="__kgR8AeREduWycDgioo5rg">
+ <sectionDescription><ul>
+ <li>
+ Do the use cases identified collectively account for all required behavior of the system?
+ </li>
+ <li>
+ Have all features identified in the vision document been addressed by at least one use case?
+ </li>
+ <li>
+ Have all nonfunctional requirements that must be satisfied by a specific use case been captured in that use case?
+ </li>
+ <li>
+ Have you verified that the use-case model contains no superfluous behavior (known as "gold-plating")?
+ </li>
+ <li>
+ Is each concrete use case associated with at least one actor, as it should be?
+ </li>
+ <li>
+ Is every actor associated with at least one use case?
+ </li>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_fknU0Jz1EduBcbjYtLtItQ" name="Is the model consistent?" guid="_fknU0Jz1EduBcbjYtLtItQ">
+ <sectionDescription><ul>
+ <li>
+ Is the system behavior consistent under the same conditions and with the same input?
+ </li>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_KowpkAeSEduWycDgioo5rg" name="Are all relationships between use cases required?"
+ guid="_KowpkAeSEduWycDgioo5rg">
+ <sectionDescription><ul>
+ <li>
+ Does each included use case make the model easier to understand, implement, and maintain?
+ </li>
+ <li>
+ Is each concrete use case (not an included use case) independent of other use cases?<br />
+ </li>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_jyHeMAeTEduWycDgioo5rg" name="Are use-case packages used appropriately?"
+ guid="_jyHeMAeTEduWycDgioo5rg">
+ <sectionDescription><ul>
+ <li>
+ Have cross-package dependencies been reduced or eliminated to prevent model ownership conflicts
+ </li>
+ <li>
+ Is packaging intuitive?&nbsp;Does the packaging make the model easier to understand and implement?&nbsp;&nbsp;
+ </li>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_i-S-ADeKEdu6VLD0YaVLog" name="Do all model elements have appropriate names?"
+ guid="_i-S-ADeKEdu6VLD0YaVLog">
+ <sectionDescription><ul>
+ <li>
+ Have you verified that no two use cases have the same name?
+ </li>
+ <li>
+ Does each actor have a name that effectively describes that person's role?
+ </li>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_IYRUkJz2EduBcbjYtLtItQ" name="Are individual use cases properly specified?"
+ guid="_IYRUkJz2EduBcbjYtLtItQ">
+ <sectionDescription><ul>
+ <li>
+ Have you reviewed the quality of each&nbsp;use-case specification using the&nbsp;<a class="elementLinkWithType"
+ href="./../../../practice.tech.use_case_driven_dev.base/guidances/checklists/use_case_C5362874.html"
+ guid="_0kNwINk1Edq2Q8qZoWbvGA">Checklist: *Use Case</a>?
+ </li>
+</ul></sectionDescription>
+ </sections>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/checklists/vision.xmi b/praclib/temp/core.tech.common.base/guidances/checklists/vision.xmi
new file mode 100644
index 0000000..30b3850
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/checklists/vision.xmi
@@ -0,0 +1,63 @@
+<?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="_qktWQMM0EdmSIPI87WLu3g"
+ name="vision,_0WoFUMlgEdmt3adZL5Dmdw" guid="_qktWQMM0EdmSIPI87WLu3g" changeDate="2005-07-07T01:30:32.000-0700"
+ version="1.0.0">
+ <sections xmi:id="_VwoioAeiEduWycDgioo5rg" name="Have you fully explored what the problem behind the problem is?"
+ guid="_VwoioAeiEduWycDgioo5rg">
+ <sectionDescription><p>
+ Make sure that you have found the root cause of the Stakeholder's problem or need. Often, Stakeholders define solutions
+ rather than stating the problem that they are experiencing or the pain they are experiencing. Subsequently, they may
+ not have identified the problem correctly or the correct solution for it.
+</p>
+<p>
+ For example, "We can't support customers who want to buy online" is better than "We need an on-line purchasing system".
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_dBs8gAeiEduWycDgioo5rg" name="Is the problem statement correctly formulated?"
+ guid="_dBs8gAeiEduWycDgioo5rg">
+ <sectionDescription>Make sure that you have agreement on the problem to be solved.</sectionDescription>
+ </sections>
+ <sections xmi:id="_jGUxYAeiEduWycDgioo5rg" name="Is the list of Stakeholders complete and correct?"
+ guid="_jGUxYAeiEduWycDgioo5rg">
+ <sectionDescription>Make sure you didn't miss any Stakeholders. If you did, you probably do not yet have all of the perspectives that you need
+to consider.</sectionDescription>
+ </sections>
+ <sections xmi:id="_s-be8AeiEduWycDgioo5rg" name="Does everyone agree on the definition of the system boundaries?"
+ guid="_s-be8AeiEduWycDgioo5rg">
+ <sectionDescription>Define what is <strong>in</strong> and what is <strong>out</strong> of system boundaries. This is a critical step in
+defining the scope of work.</sectionDescription>
+ </sections>
+ <sections xmi:id="_z1uG4AeiEduWycDgioo5rg" name="Have you sufficiently explored constraints to put on the system?"
+ guid="_z1uG4AeiEduWycDgioo5rg">
+ <sectionDescription>Don't forget about the non-functional requirements and constraints. These are often the largest cost of development.</sectionDescription>
+ </sections>
+ <sections xmi:id="_7KzeEAeiEduWycDgioo5rg" name="Have you covered all kinds of constraints, including political, economic, and environmental?"
+ guid="_7KzeEAeiEduWycDgioo5rg">
+ <sectionDescription><p>
+ These non-technical constraints often lead to problems later.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_DymaUAejEduWycDgioo5rg" name="Have all key features of the system been identified and defined?"
+ guid="_DymaUAejEduWycDgioo5rg">
+ <sectionDescription>Do a completeness check, comparing the features with the problem statement, to make sure that you didn't miss a critical
+feature.</sectionDescription>
+ </sections>
+ <sections xmi:id="_LRX5AAejEduWycDgioo5rg" name="Will the features solve the problems that are identified?"
+ guid="_LRX5AAejEduWycDgioo5rg">
+ <sectionDescription>Are all the features really necessary?&nbsp; Perhaps you can reduce the scope.</sectionDescription>
+ </sections>
+ <sections xmi:id="_UGRdIAejEduWycDgioo5rg" name="Are the features consistent with constraints that you've identified?"
+ guid="_UGRdIAejEduWycDgioo5rg">
+ <sectionDescription><p>
+ Check that conflicting requirements do not exist. If you find conflicts, resolve them now.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_5y4uAAhUEduRe8TeoBmuGg" name="Can someone who is not familiar with the project understand what you hope the project will achieve by reading the Vision document?"
+ guid="_5y4uAAhUEduRe8TeoBmuGg">
+ <sectionDescription>The purpose of the Vision document is to describe the objectives of the project in terms that non-technical people, who are
+not closely involved with the project, can understand.</sectionDescription>
+ </sections>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/actor.xmi b/praclib/temp/core.tech.common.base/guidances/concepts/actor.xmi
new file mode 100644
index 0000000..14ba7d9
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/actor.xmi
@@ -0,0 +1,58 @@
+<?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="-aN0zy068ovKHgmkkoYqoYQ"
+ name=",_zGqO0MDpEduTGJ8i4u8TMw" guid="-aN0zy068ovKHgmkkoYqoYQ" changeDate="2007-02-20T05:56:57.000-0800"
+ version="7.2.0">
+ <mainDescription><p>
+ To fully understand the system's purpose, you must know who the system is for, that is: Who will use the system? The
+ answer to this question is: the Actors.
+</p>
+<p>
+ An Actor is a role that a person or external system plays&nbsp;when interacting with the system.&nbsp; Instances of an
+ Actor can be an individual or an external system, however each Actor&nbsp;provides a
+ unique&nbsp;and&nbsp;important&nbsp;perspective on the system that is shared by every instance of the Actor.
+</p>
+<p>
+ This difference between an actor and an instance of an actor is illustrated below.&nbsp;&nbsp;Figure 1 shows a case in
+ which Ivar and Mark are operators of a recycling machine. When they are using the machine in this capacity, each is
+ represented by an instance of the actor called Operator that expects certain functionality of the system (Print Daily
+ Reports in this example).
+</p>
+<p>
+ <img height="322" alt="" src="./resources/md_acto2.gif" width="396" />&nbsp;
+</p>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p>
+ <strong>Figure 1:&nbsp;Example Actor with multiple instances</strong>&nbsp;
+ </p>
+</blockquote>
+<p>
+ Conversely, the same user can act as several actors (that is, the same person can take on different roles). In Figure
+ 2, Charlie uses the Depot-Handling System primarily as Depot Manager, but sometimes he also uses the Depot-Handling
+ System as an ordinary Depot Staff member. Each of these actors expects different functionality of the system.
+</p>
+<p>
+ <img height="139" alt="" src="./resources/md_acto3.gif" width="367" />
+</p>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p>
+ <strong>Figure 2: Example of user playing different roles</strong><br />
+ </p>
+</blockquote>
+<p>
+ Actors help you to identify external interfaces and to determine the scope the system (what is in the system, vs. what
+ is outside the system boundary).&nbsp; Each&nbsp;Actor has associated use cases which describe what that
+ particular&nbsp;actor expects of the system.&nbsp; It will be very difficult, if not impossible,&nbsp;to assess the
+ completeness of the set of Use Cases without the context provided by the associated Actors. Furthermore, missing an
+ actor may result in&nbsp;missing important stakeholder perspectives, resulting&nbsp;in a solution that does not meet
+ all&nbsp;stakeholder needs.
+</p>
+<p>
+ Hence, identifying the Actors for the system&nbsp;should be done early in the lifecycle.&nbsp;&nbsp;Actors are
+ captured, including their names, brief descriptions, and relationships to use cases,&nbsp;in the <a
+ class="elementLinkWithType" href="./../../../core.tech.common.base/workproducts/use_case_model_85965D1B.html"
+ guid="_W2SgEDR5EdutE_HNDTJk5Q">Artifact: *Use-Case Model</a>.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/analysis_mechanism.xmi b/praclib/temp/core.tech.common.base/guidances/concepts/analysis_mechanism.xmi
new file mode 100644
index 0000000..745aac3
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/analysis_mechanism.xmi
@@ -0,0 +1,76 @@
+<?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="_S8KCcMP2EdmWKcx6ixEiwg"
+ name="analysis_mechanism,_0gvqoMlgEdmt3adZL5Dmdw" guid="_S8KCcMP2EdmWKcx6ixEiwg"
+ changeDate="2008-02-09T16:19:23.718-0500" version="1.0.0">
+ <mainDescription><p>
+ An Analysis Mechanism is a conceptual representation of an <a class="elementLink"
+ href="./../../../core.tech.common.base/guidances/concepts/architectural_mechanism_2932DFB6.html"
+ guid="_mzxI0A4LEduibvKwrGxWxA">Architectural Mechanism</a>. Over time, Analysis Mechanisms are refined into <a
+ class="elementLink" href="./../../../core.tech.common.base/guidances/concepts/design_mechanism_CE197B4E.html"
+ guid="_w2ACwA4LEduibvKwrGxWxA">Design Mechanism</a>s&nbsp;and, later, into <a class="elementLink"
+ href="./../../../core.tech.common.base/guidances/concepts/implementation_mechanism_C92E670B.html"
+ guid="_0LcUkA4LEduibvKwrGxWxA">Implementation Mechanism</a>s.
+</p>
+<p>
+ Analysis Mechanisms&nbsp;allow the developer to focus on understanding the requirements without getting distracted by
+ the specifics of a complex implementation. They are a way of abstracting away the complexity of the solution, so people
+ can better comprehend the problem.
+</p>
+<p>
+ Analysis Mechanisms are described in simple terms:
+</p>
+<ul>
+ <li>
+ <strong>Name:</strong> Identifies the mechanism.
+ </li>
+ <li>
+ <strong>Basic attributes:</strong> Define the requirements of the mechanism.
+ </li>
+</ul>
+<p>
+ You can identify Analysis Mechanisms top-down, from previous knowledge, or bottom-up, meaning that you discover them as
+ you proceed.
+</p>
+<p>
+ In the top-down mode, you are guided by experience -- you know that certain problems are present in the domain and will
+ require certain kinds of solutions. Examples of common architectural problems that might be expressed as mechanisms
+ during analysis are: persistence, transaction management, fault management, messaging, and inference engines. The
+ common aspect of all of these is that each is a general capability of a broad class of systems, and each provides
+ functionality that interacts with or supports the basic application functionality. The Analysis Mechanisms support
+ capabilities required in the basic functional requirements of the system, regardless of the platform that it is
+ deployed upon or the implementation language. Analysis Mechanisms also can be designed and implemented in different
+ ways. Generally, there will be more than one design mechanism that corresponds with each Analysis Mechanism. There may
+ also be more than one way of implementing each design mechanism.
+</p>
+<p>
+ The bottom-up approach is where Analysis Mechanisms ultimately originate. They are created as the you see, perhaps
+ faintly at first, a common theme emerging from a set of solutions to various problems. For example: There is a need to
+ provide a way for elements in different threads to synchronize their clocks, and there is a need for a common way of
+ allocating resources. <a class="elementLink"
+ href="./../../../core.tech.common.base/guidances/concepts/analysis_mechanism_8369C159.html"
+ guid="_0gvqoMlgEdmt3adZL5Dmdw">Analysis Mechanism</a>s, which simplify the language of analysis, emerge from these
+ patterns.
+</p>
+<p>
+ Identifying an Analysis Mechanism means that you identify a common, perhaps implicit&nbsp;subproblem, and you give it a
+ name. Initially, the name might be all that exists. For example, the system will require a persistence
+ mechanism.&nbsp;Ultimately, this mechanism will be implemented through the collaboration of various classes, some of
+ which do not deliver application functionality directly, but exist only to support it. Very often these support classes
+ are located in the middle or lower layers of a layered architecture, thereby providing a common support service to all
+ application-level classes.
+</p>
+<p>
+ If the subproblem that you identify is common enough, perhaps a pattern exists from which the mechanism can be
+ instantiated, probably by binding existing classes and implementing new ones, as required by the pattern. An Analysis
+ Mechanism produced this way will be abstract, and it will require further refinement throughout design and
+ implementation work.
+</p>
+<p>
+ You can see examples of how Architectural Mechanisms can be represented in <a class="elementLinkWithType"
+ href="./../../../core.tech.common.base/guidances/examples/architectural_mechanism_attributes_B0ECA2F7.html"
+ guid="_eQ_s8Om5Edupia_tZIXEqg">Example: Architectural Mechanism Attributes</a>.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/arch_constraints.xmi b/praclib/temp/core.tech.common.base/guidances/concepts/arch_constraints.xmi
new file mode 100644
index 0000000..0daca16
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/arch_constraints.xmi
@@ -0,0 +1,42 @@
+<?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="-je0zRqgX0Tg_761Z77cIkg"
+ name="arch_constraints,_jdKSsNpiEdyP58ppo1Ieaw" guid="-je0zRqgX0Tg_761Z77cIkg"
+ changeDate="2008-02-13T13:37:37.359-0500" version="7.2.0">
+ <mainDescription><p>
+ A variety of factors may place constraints on the architecture being developed:
+</p>
+<div style="MARGIN-LEFT: 2em">
+ <ul>
+ <li>
+ Network topology
+ </li>
+ <li>
+ Use of a given database vendor or an existing database
+ </li>
+ <li>
+ Web environment (server configurations, firewall, DMZs, and so forth)
+ </li>
+ <li>
+ Servers (hardware model, operating system)
+ </li>
+ <li>
+ Use of third-party software or a particular technology
+ </li>
+ <li>
+ Compliance with existing standards
+ </li>
+ </ul>
+</div>
+<p>
+ For example, if the company uses only one type of database, you will probably try to use it as much as possible to
+ leverage&nbsp;the existing database administration skills, rather than introducing a new one.
+</p>
+<p>
+ These architectural constraints, combined with the requirements, help you define&nbsp;an appropriate&nbsp;candidate for
+ the system architecture. Capturing these constraints will ease integration with the environment; and may reduce risk,
+ cost and duplication of solution elements.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/arch_goals.xmi b/praclib/temp/core.tech.common.base/guidances/concepts/arch_goals.xmi
new file mode 100644
index 0000000..657b47b
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/arch_goals.xmi
@@ -0,0 +1,35 @@
+<?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="-Mm7s8vlK5CaZZ_Msx8reCQ"
+ name="new_concept,_HlRqANpbEdyP58ppo1Ieaw" guid="-Mm7s8vlK5CaZZ_Msx8reCQ" version="7.2.0">
+ <mainDescription><p>
+ Architectural goals provide the motivation and rationale&nbsp;for decisions. These goals are&nbsp;often driven
+ by&nbsp;the software requirements, particularly system-wide requirements [<a class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/tech_references_6CCF393.html"
+ guid="_9ToeIB83Edqsvps02rpOOg">ALL02</a>].
+</p>
+<p>
+ Architectural goals define how the system needs to respond to change over time. Architectural goals tend to address the
+ following questions:
+</p>
+<ul>
+ <li>
+ What is the expected lifespan of the system?
+ </li>
+ <li>
+ Will the system need to respond to technological changes over that time, such as new versions of middleware or
+ other products?
+ </li>
+ <li>
+ How&nbsp;frequently is&nbsp;the system&nbsp;expected to adapt to change?
+ </li>
+ <li>
+ What changes can we anticipate in the future, and how can we make them easier to accommodate?
+ </li>
+</ul>
+<p>
+ These considerations will have a significant effect on the structure of the system.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/arch_mechanism.xmi b/praclib/temp/core.tech.common.base/guidances/concepts/arch_mechanism.xmi
new file mode 100644
index 0000000..823062d
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/arch_mechanism.xmi
@@ -0,0 +1,232 @@
+<?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="-SJrpVySJ2npYs8NwGvnHjw"
+ name="arch_mechanism,_mzxI0A4LEduibvKwrGxWxA" guid="-SJrpVySJ2npYs8NwGvnHjw" authors="Mark Dickson"
+ changeDate="2008-02-15T09:35:53.109-0500" changeDescription="Simplified text explaining mechanism concept"
+ version="1.0.0">
+ <mainDescription><h3>
+ What are Architectural Mechanisms?
+</h3>
+<p>
+ Architectural Mechanisms are common solutions to common problems that can be used during development to minimize
+ complexity.&nbsp; They represent key technical concepts that&nbsp;will be standardized across the solution.&nbsp;
+ Architecture mechanisms facilitate the evolution of architecturally significant aspects of the system. They allow the
+ team to maintain a cohesive architecture whilst enabling implementation details to be deferred until they really need
+ to be made.
+</p>
+<p>
+ Architectural Mechanisms are&nbsp;used to satisfy architecturally significant requirements.&nbsp;When fully described,
+ Architectural Mechanisms show patterns of structure and behavior in the software. They&nbsp;form the basis
+ of&nbsp;common software&nbsp;that will be&nbsp;consistently applied&nbsp;across the product being developed. They also
+ form the basis for standardizing the way that the software works; therefore, they are an important element of the
+ overall software architecture. The definition of architecture mechanisms also enable decisions on whether existing
+ software components can be leveraged to provide the required behaviour; or whether new software should be bought or
+ built.
+</p>
+<p>
+ Defining architectural mechanisms is all about making choices about *what* technology will be used to satisfy
+ architecturally significant requirements. It is not about producing detailed design or software. This is a common
+ misunderstanding. The creation of detailed design and&nbsp;software that&nbsp;shows&nbsp;*how* specific
+ mechanisms&nbsp;are satisfied&nbsp;is&nbsp;a development task.
+</p>
+<p>
+ The value in defining architecture mechanisms is that they:
+</p>
+<ol>
+ <li>
+ Explicitly call out&nbsp;aspects of the solution mechanics that are common across the system. This helps you plan.
+ </li>
+ <li>
+ Put down markers for the developers to build those aspects of the system once and then re-use them. This reduces
+ the workload.
+ </li>
+ <li>
+ Promote the development of a consistent set of services. This makes the system easier to maintain.
+ </li>
+</ol>
+<p>
+ An&nbsp;Architectural Mechanism can have three states: Analysis, Design and Implementation.&nbsp;These
+ categories&nbsp;reflect the maturity of the mechanism's description. The state changes as successive levels of detail
+ are uncovered during when you refine <a class="elementLink"
+ href="./../../../core.tech.common.base/guidances/concepts/arch_significant_requirements_1EE5D757.html"
+ guid="_HrZGIA4MEduibvKwrGxWxA">Architecturally Significant Requirements</a>&nbsp;into working software. The categories
+ are summarized in the table that follows.
+</p><strong>States of an Architectural Mechanism</strong> 
+<table style="WIDTH: 806px; HEIGHT: 228px" cellspacing="0" cellpadding="2" width="806"
+summary="Types of Architectural Mechanism" border="1">
+ <tbody valign="top">
+ <tr>
+ <th scope="col">
+ State
+ </th>
+ <th scope="col">
+ Description
+ </th>
+ </tr>
+ <tr>
+ <td>
+ Analysis
+ </td>
+ <td>
+ <p>
+ A conceptual solution to a common technical problem. For example,&nbsp;persistence is an abstract
+ solution to the common requirement to store data. The purpose of this category is simply to identify
+ the need for an Architectural Mechanism to be designed and implemented; and capture basic attributes
+ for that mechanism.
+ </p>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Design
+ </td>
+ <td>
+ <p>
+ A refinement of an Analysis Mechanism into a concrete technology (for example, RDBMS). The purpose of
+ this category is to guide precise product or technology selection.
+ </p>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Implementation
+ </td>
+ <td>
+ <p>
+ A further refinement from a design mechanism into a specification for the software. This can be
+ presented as a design pattern or example code.
+ </p>
+ </td>
+ </tr>
+ </tbody>
+</table><br />
+<p>
+ For more information on these different types of mechanisms, see the attached concepts.
+</p>
+<p>
+ Be aware that these states are frequently referred to themselves as Analysis, Design and Implementation
+ mechanisms.&nbsp;These are synonyms and merely represent the architecture mechanisms in different states of
+ development. The transition from one state to another&nbsp;can often be obvious or intuitive. Therefore, it can be
+ achieved in a matter of seconds. It can also require more considered analysis and design, thus take longer.&nbsp;The
+ important point here is that these categories of mechanisms apply to the same concept in different states. The only
+ difference between them is one of refinement or detail.
+</p>
+<p>
+ The following diagram illustrates the transition of Architectural Mechanisms from one state to another.
+</p>
+<p>
+ <strong>State Machine for Architectural Mechanisms</strong>
+</p>
+<p>
+ <img style="WIDTH: 876px; HEIGHT: 115px" height="113" alt="Architectural Mechanism States"
+ src="./resources/ArchMechStates.JPG" width="600" />&nbsp;
+</p>
+<p>
+ See <a class="elementLinkWithType"
+ href="./../../../core.tech.common.base/guidances/examples/architectural_mechanisms_415C32A3.html"
+ guid="_O39h0O9pEdu635i_iQ5Jag">Example: Architectural Mechanisms</a>&nbsp;for a list of typical mechanisms.
+</p>
+<h3>
+ What Information Should be Captured for Architectural Mechanisms?
+</h3>
+<p>
+ The information captured for each architectural mechanism category/state is different (though the information can be
+ seen as refinements of each other):
+</p>
+<ul>
+ <li>
+ <strong>Analysis Mechanisms</strong>, which give the mechanism a name, brief description and some basic
+ attributes&nbsp;derived from&nbsp;the project requirements
+ </li>
+ <li>
+ <strong>Design Mechanisms</strong>, which are more concrete and assume some details of the implementation
+ environment
+ </li>
+ <li>
+ <strong>Implementation Mechanisms</strong>, which specify the&nbsp;exact implementation of&nbsp;each mechanism
+ </li>
+</ul>
+<p>
+ When&nbsp;a mechanism is&nbsp;initially identified, it can be considered a marker that says to the team, "We are going
+ to handle this aspect of the system in a standard way. We'll figure out the details later." As the project proceeds,
+ the architectural mechanisms are gradually refined until they become part of the software.
+</p>
+<h4>
+ Analysis Mechanisms
+</h4>
+<p>
+ Analysis mechanisms&nbsp;are the initial state for an architectural mechanism. They are identified early in the project
+ and represent&nbsp;bookmarks for future software development. They allow the&nbsp;team to focus on understanding the
+ requirements without getting distracted by the specifics of a complex implementation. Analysis mechanisms are
+ discovered by surveying the requirements and looking for recurrent technical concepts.&nbsp;Security, persistence and
+ legacy interface are some examples of these. In effect, the analysis mechanism is where the requirements that
+ describe&nbsp;architecturally significant topics&nbsp;are collated and brought&nbsp;together in a single list. This
+ makes them easier to manage.
+</p>
+<p>
+ Analysis mechanisms are described in simple terms:
+</p>
+<ul>
+ <li>
+ <strong>Name:</strong> Identifies the mechanism.
+ </li>
+ <li>
+ <strong>Basic attributes:</strong> Define the requirements of the mechanism. These attributes can vary depending
+ upon the mechanism being analyzed. Refer to <a class="elementLinkWithType"
+ href="./../../../core.tech.common.base/guidances/examples/architectural_mechanism_attributes_B0ECA2F7.html"
+ guid="_eQ_s8Om5Edupia_tZIXEqg">Example: Architectural Mechanism Attributes</a>&nbsp;for more guidance.
+ </li>
+</ul>
+<p>
+ Once the list of analysis mechanisms has been defined it can be prioritized and the mechanisms refined in line
+ with&nbsp;iteration&nbsp;objectives. It is not necessary to develop the entire set of architecture mechanisms into
+ working software in a single pass. It is often more sensible to develop only those mechanisms required to support the
+ functionality to be delivered in the current iteration.
+</p>
+<h4>
+ Design Mechanisms
+</h4>
+<p>
+ Design mechanisms&nbsp;represent decisions about the concrete technologies that are going to be used to&nbsp;develop
+ architectural mechanisms. For example, the decision to use an RDBMS for persistence. It's often no more complicated
+ than that (though of course, the effort involved in making the decision can sometimes be quite complex).
+</p>
+<p>
+ The decision on when to refine an architectural mechanism from an analysis state to a design state is largely
+ arbitrary. Often there will be constraints on the project that&nbsp;force the decision on some of these issues. For
+ example, there may be a corporate standard for databases which mean that the decision&nbsp;for the&nbsp;persistence
+ mechanism can be made on day 1 of the project.
+</p>
+<p>
+ On other occasions the decision may point to products that the project team has not yet acquired.&nbsp;If so,&nbsp;the
+ decision needs to be made in time to enable the required products to be made available to the team.
+</p>
+<p>
+ It can often be useful to develop some prototype code to prove that these decisions are sound. The <a
+ class="elementLink" href="./../../../core.default.role_def.base/roles/architect_E7A12309.html"
+ guid="_0X9iEMlgEdmt3adZL5Dmdw">Architect</a> should be confident that the technologies being selected are able to
+ fulfill the requirements. The attributes captured against the corresponding analysis mechanisms should be used as
+ criteria to prove the validity of the decisions.
+</p>
+<h4>
+ Implementation Mechanism
+</h4>
+<p>
+ An implementation mechanism&nbsp;specifies the actual implementation for the architectural mechanism (hence the
+ name).&nbsp;It can be modeled as a design pattern or presented as&nbsp;example code.
+</p>
+<p>
+ The best time to&nbsp;produce the&nbsp;implementation mechanism is usually when the first piece of functionality that
+ needs it is scheduled for development. The <a class="elementLink"
+ href="./../../../core.default.role_def.base/roles/architect_E7A12309.html" guid="_0X9iEMlgEdmt3adZL5Dmdw">Architect</a>
+ and <a class="elementLink" href="./../../../core.default.role_def.base/roles/developer_C633AB7.html"
+ guid="_0YDosMlgEdmt3adZL5Dmdw">Developer</a> work together to develop this.
+</p>
+<p>
+ For examples of the kinds of information that you might capture for a mechanism, see <a class="elementLinkWithType"
+ href="./../../../core.tech.common.base/guidances/examples/architectural_mechanism_attributes_B0ECA2F7.html"
+ guid="_eQ_s8Om5Edupia_tZIXEqg">Example: Architectural Mechanism Attributes</a>.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/arch_significant_requirements.xmi b/praclib/temp/core.tech.common.base/guidances/concepts/arch_significant_requirements.xmi
new file mode 100644
index 0000000..b604278
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/arch_significant_requirements.xmi
@@ -0,0 +1,84 @@
+<?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="-EytH4BCNGiHF6pZrp8ISCw"
+ name="new_concept,_eFElAOK2EdqHEo0wLIc5jg" guid="-EytH4BCNGiHF6pZrp8ISCw" authors="Mark Dickson"
+ changeDate="2008-02-15T09:10:19.062-0500" changeDescription="First Draft" version="1.0">
+ <mainDescription><p>
+ Architecturally significant requirements are those requirements that play an important role in determining the
+ architecture of the system.&nbsp; Such requirements require special attention. Not all requirements have equal
+ significance with regards to the architecture.
+</p>
+<p>
+ Architecturally significant requirements&nbsp;are a subset of the requirements that need to be satisfied before the
+ architecture can be considered "stable". Typically, these are requirements that are technically challenging,
+ technically constraining, or central to the system's purpose. Furthermore, the system will generally be more sensitive
+ to changes&nbsp;against architecturally significant requirements, so identifying and communicating this subset will
+ help others understand the potential implications of change.
+</p>
+<p>
+ Requirements can be explicitly or implicitly architecturally significant. Explicitly significant requirements are often
+ overtly technical in nature, such as performance targets; the need to interface to other systems; the number of users
+ that must be supported; or security requirements. Implicitly significant requirements may define the essence of the
+ functional behaviour of the system (for example, making a purchase from an on-line store).
+</p>
+<p>
+ Deciding whether a specific requirement is architecturally significant is often a matter of judgment. The selection of
+ requirements that are considered "architecturally significant" is driven by several key driving factors:
+</p>
+<ul>
+ <li>
+ The benefit of the requirement to stakeholders: critical, <b>important</b>, or <b>useful</b>.
+ </li>
+ <li>
+ The architectural impact of the requirement: <b>none</b>, <b>extends</b>, or <b>modifies</b>. There may be critical
+ requirements that have little or no impact on the architecture and low-benefit requirements that have a big impact.
+ Low-benefit requirements with big architectural impacts should be reviewed by the project manager for possible
+ removal from the scope of the project.
+ </li>
+ <li>
+ The risks to be mitigated: performance, availability of a product, and suitability of a component.
+ </li>
+ <li>
+ The completion of the coverage of the architecture.
+ </li>
+ <li>
+ Other tactical objectives or constraints, such as demonstration to the user, and so on.
+ </li>
+</ul>
+<p>
+ There may be two requirements that hit the same components and address similar risks. If you implement A first, then B
+ is not architecturally significant. If you implement B first, then A is not architecturally significant. Thus these
+ attributes can depend on the order the requirements are realized, and should be re-evaluated when the order changes, as
+ well as when the requirements themselves change.
+</p>
+<p>
+ The following are good examples of Architecturally Significant Requirements:
+</p>
+<ul>
+ <li>
+ The system must record every modification to customer records for audit purposes.
+ </li>
+ <li>
+ The system must respond within 5 seconds.
+ </li>
+ <li>
+ The system must&nbsp;deploy on Microsoft Windows XP and Linux.
+ </li>
+ <li>
+ The system must encrypt all network traffic.
+ </li>
+ <li>
+ The ATM system must dispense cash on&nbsp;demand&nbsp;to validated account holders with sufficient cleared funds.
+ </li>
+</ul>
+<p>
+ Architecturally significant requirements also describe key behaviors that the system needs to perform.&nbsp; Such
+ scenarios represent the important interactions between key abstractions.and should be identifed as architecturally
+ significant requirements. For example, for an on-line book store describing the way the software handles the scenarios
+ for ordering a book and checking out the shopping cart are often enough to communicate the essence of the architecture.
+</p><br />
+<br />
+<br /></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/arch_views_viewpoints.xmi b/praclib/temp/core.tech.common.base/guidances/concepts/arch_views_viewpoints.xmi
new file mode 100644
index 0000000..32bf063
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/arch_views_viewpoints.xmi
@@ -0,0 +1,53 @@
+<?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="-QB0WnHnpcK1VJbdJJ5QJ5A"
+ name="new_concept,_kgtcoNc8Edyd7OybSySFxg" guid="-QB0WnHnpcK1VJbdJJ5QJ5A" changeDate="2008-02-15T09:03:09.296-0500"
+ version="7.2.0">
+ <mainDescription><p>
+ Architecture can be represented from a variety of viewpoints, all of which can be combined to create a holistic view of
+ the system. Each architectural view addresses some specific set of concerns, specific to stakeholders in the
+ development process: users, designers, managers, system engineers, maintainers, and so on.
+</p>
+<p>
+ The views capture the major structural design decisions by showing how the software architecture is decomposed into
+ components, and how components are connected by connectors to produce useful forms <a class="elementlinkwithusertext"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/tech_references_6CCF393.html#DEW92"
+ guid="_9ToeIB83Edqsvps02rpOOg">[DEW92]</a>. These design choices must be tied to the requirements -- functional and
+ supplementary -- and other constraints. But these choices in turn put further constraints on the requirements, and on
+ future design decisions at a lower level.&nbsp;
+</p>
+<p>
+ In essence, architectural views are abstractions, or simplifications, of the entire design, in which important
+ characteristics are made more visible by leaving details aside. These characteristics are important when reasoning
+ about:
+</p>
+<ul>
+ <li>
+ System evolution-going to the next development cycle.
+ </li>
+ <li>
+ Reuse of the architecture, or parts of it, in the context of a product line.
+ </li>
+ <li>
+ Assessment of supplementary qualities, such as performance, availability, portability, and safety.
+ </li>
+ <li>
+ Assignment of development work to teams or subcontractors.
+ </li>
+ <li>
+ Decisions about including off-the-shelf components.
+ </li>
+ <li>
+ Insertion in a wider system.&nbsp;
+ </li>
+</ul>
+<p>
+ To choose the appropriate set of views,&nbsp;identify the stakeholders who depend on software architecture
+ documentation and the information that they need. For an example of a set of views that have been used to represent
+ architecture, see <a class="elementLinkWithType"
+ href="./../../../core.tech.common.base/guidances/examples/four_plus_one_view_of_arch_9A93ACE5.html"
+ guid="_4bC4cNs_EdyEW4klSH3vRA">Example: 4+1 Views of Software Architecture</a>.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/business_pattern.xmi b/praclib/temp/core.tech.common.base/guidances/concepts/business_pattern.xmi
new file mode 100644
index 0000000..43b0844
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/business_pattern.xmi
@@ -0,0 +1,25 @@
+<?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="-Of51hmgdsO_U2-pnbJ67Cg"
+ name="new_concept,_RoSdMBWYEduCK502eDgjUQ" guid="-Of51hmgdsO_U2-pnbJ67Cg" changeDate="2008-02-10T22:39:04.750-0500"
+ version="7.2.0">
+ <mainDescription><p>
+ Business Patterns are a form of Design Pattern&nbsp;(see <a class="elementLinkWithType"
+ href="./../../../core.tech.common.base/guidances/concepts/pattern_10BE6D96.html"
+ guid="_0YJvUMlgEdmt3adZL5Dmdw">Concept: Pattern</a>) and are the business-domain counterpart of <a
+ class="elementLinkWithType"
+ href="./../../../core.tech.common.base/guidances/concepts/architectural_mechanism_2932DFB6.html"
+ guid="_mzxI0A4LEduibvKwrGxWxA">Concept: Architectural Mechanism</a>. Just as similar problems in the technical domain
+ may be solved by using Architecture Mechanisms, similar problems in the business domain can be solved by using Business
+ Patterns.
+</p>
+<p>
+ Business Patterns are often found in COTS products. For example, packaged applications that support Enterprise Resource
+ Planning or Customer Relationship Management ship with functionality to support a variety of generic business
+ processes. Similarly, it is frequently possible to identify related or similar behavior in the Use
+ Case&nbsp;Scenarios&nbsp;and thereby derive generic designs that you can use in the design of the system. These
+ elements of generic behavior can be&nbsp;expressed as Design&nbsp;Patterns and applied to the system design.
+</p><br /></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/component.vm.xmi b/praclib/temp/core.tech.common.base/guidances/concepts/component.vm.xmi
new file mode 100644
index 0000000..a904d05
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/component.vm.xmi
@@ -0,0 +1,104 @@
+<?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="-zfl87vJBFdinDB02ArLXOQ"
+ name="new_concept,_HZGFsKrPEdu6T6WyNqBzqQ" guid="-zfl87vJBFdinDB02ArLXOQ" changeDate="2008-02-14T08:48:12.640-0500"
+ version="7.2.0">
+ <mainDescription><h3 align="left">
+ Modeling Components
+</h3>
+<p align="left">
+ The UML component is a modeling construct that provides the following capabilities:
+</p>
+<div align="left">
+ <ul>
+ <li>
+ Group classes to define a larger granularity part of a system
+ </li>
+ <li>
+ Separate the visible interfaces from internal implementation
+ </li>
+ <li>
+ Execute instances run-time
+ </li>
+ </ul>
+</div>
+<p align="left">
+ A component includes <strong>provided</strong> and <strong>required</strong> interfaces that form the basis for wiring
+ components together. A <strong>provided interface</strong> is one that is either implemented directly by the component
+ or one of its realizing classes or subcomponents, or it is the type of a provided port of the component. A
+ <strong>required interface</strong> is designated by a usage dependency of the component or one of its realizing
+ classes or subcomponents, or it is the type of a required port.
+</p>
+<p align="left">
+ A component has an external view (or <em>black box</em> view) through its publicly visible properties and operations
+ .Optionally, a behavior such as a protocol state machine may be attached to an interface, a port, and the component
+ itself to define the external view more precisely by making dynamic constraints in the sequence of operation calls
+ explicit. The wiring between components in a system or other context can be structurally defined by using dependencies
+ between component interfaces (typically on component diagrams).
+</p>
+<p align="left">
+ Optionally, you can make a more detailed specification of the structural collaboration by using parts and connectors in
+ composite structures to specify the role or instance-level collaboration between components. That is the component's
+ internal view (or <em>white-box</em> view) through its private properties and realizing classes or subcomponents. This
+ view shows how the external behavior is realized internally. The mapping between external and internal views is by
+ dependencies on components diagrams or delegation connectors to internal parts on composite structure diagrams.
+</p>
+<p align="left">
+ A number of UML standard stereotypes exist that apply to components, including &lt;&lt;subsystem&gt;&gt; to model
+ large-scale components, and &lt;&lt;specification&gt;&gt; and &lt;&lt;realization&gt;&gt; to model components with
+ distinct specification and realization definitions, where one specification may have multiple realizations.&nbsp;
+</p>
+<p align="left">
+ The recommendation is to&nbsp;use components as the representation for design subsystems.
+</p>
+<h3 align="left">
+ UML Definitions -- A History
+</h3>
+<p align="left">
+ The definition of <em>component</em> with the UML has changed over time with the release of different versions. The
+ version of UML you use may be constrained by the capabilities of the modeling tools you use. That is why the
+ definitions from 1.3 to 2.0 are provided here.
+</p>
+<p align="left">
+ UML 2.0 defined <em>component</em> as the following:
+</p>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <blockquote>
+ <p align="left">
+ ...a modular part of a system that encapsulates its contents and whose manifestation is replaceable within its
+ environment.
+ </p>
+ <p align="left">
+ A component defines its behavior in terms of provided and required interfaces. As such, a component serves as a
+ type whose conformance is defined by these provided and required interfaces (encompassing both their static as
+ well as dynamic semantics).
+ </p>
+ </blockquote>
+</blockquote>
+<p align="left">
+ UML 1.5 defined <em>component</em> as the following:
+</p>
+<blockquote>
+ <blockquote>
+ <div align="left">
+ A modular, deployable, and replaceable part of a system that encapsulates implementation and exposes a set of
+ interfaces. A component is typically specified by one or more classes or subcomponents that reside on it and
+ may be implemented by one or more artifacts (e.g., binary, executable, or script files).
+ </div>
+ <div align="left">
+ <p>
+ In UML 1.3 and earlier versions of the UML, the component notation was used to represent files in the
+ implementation. Files are no longer considered components by the latest UML definitions. However, many
+ tools and UML profiles still use the component notation to represent files.
+ </p>
+ <p>
+ <br />
+ <br />
+ &nbsp;
+ </p>
+ </div>
+ </blockquote>
+</blockquote></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/component.xmi b/praclib/temp/core.tech.common.base/guidances/concepts/component.xmi
new file mode 100644
index 0000000..f4d5526
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/component.xmi
@@ -0,0 +1,128 @@
+<?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="_TZiasMM1EdmSIPI87WLu3g"
+ name="component,_0YP18MlgEdmt3adZL5Dmdw" guid="_TZiasMM1EdmSIPI87WLu3g" changeDate="2008-02-16T14:28:21.109-0500"
+ version="1.0.0">
+ <mainDescription><p align="left">
+ The software industry and literature use the term <strong>componen</strong>t to refer to many different things. It is
+ often used in the broad sense to mean a constituent part. It is also frequently used in a narrow sense to denote
+ specific characteristics that enable replacement and assembly in larger systems.
+</p>
+<p align="left">
+ The Unified Modeling Language [<a class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/tech_references_6CCF393.html"
+ guid="_9ToeIB83Edqsvps02rpOOg">UML05</a>] defines <em>component</em> as follows:
+</p>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <blockquote>
+ <p>
+ A modular part of a system that encapsulates its contents and whose manifestation is replaceable within its
+ environment. A component defines its behavior in terms of provided and required interfaces. As such, a
+ component serves as a type, whose conformance is defined by these provided and required interfaces
+ (encompassing both their static as well as dynamic semantics).
+ </p>
+ <p>
+ A <em>component</em> is defined as a subtype of structured class. Therefore, a component has attributes and
+ operations, is able to participate in associations and generalizations, and has internal structure and ports.
+ </p>
+ </blockquote>
+</blockquote>
+<p align="left">
+ Here, we use&nbsp;the term <em>component&nbsp;</em>in a&nbsp;broader way than the UML definition. Rather than defining
+ components as having characteristics, such as modularity, deployability, and replaceability, we instead recommend these
+ as desirable characteristics of components. We use <em>component</em> to mean <strong>an encapsulated part of a
+ system</strong> that is nontrivial, nearly independent, and replaceable part of a system that fulfils a clear function
+ in the context of well-defined architecture. This includes two types of components:
+</p>
+<ul>
+ <li>
+ <div align="left">
+ <p>
+ <strong>Design component.</strong> A significant encapsulated part of the design that includes design
+ subsystems and, sometimes, significant design classes and design packages.
+ </p>
+ </div>
+ </li>
+ <li>
+ <div align="left">
+ <p>
+ <strong>Implementation component.</strong> A significant encapsulated part of the implementation, generally
+ code that implements a design component.
+ </p>
+ </div>
+ </li>
+</ul>
+<p align="left">
+ Ideally, the design reflects the implementation; therefore, you can simply refer to <em>components</em>, with each
+ component having a design and an implementation.
+</p>
+<p align="left">
+ Components interact through interfaces&nbsp;and&nbsp;may be composed of successively smaller components and interfaces.
+</p>
+<h3 align="left">
+ Component replaceability
+</h3>
+<p align="left">
+ In UML terminology, components should be replaceable. However, this may mean only that the component exposes a set of
+ interfaces that hide an underlying implementation.
+</p>
+<p align="left">
+ There are other, stronger, kinds of replaceability: .
+</p>
+<div align="left">
+ <ul>
+ <li>
+ <p>
+ <strong>Source file replaceability:</strong> If two classes are implemented in a single source code file,
+ then those classes cannot usually be separately versioned and controlled. However, if a set of files fully
+ implements a single component (and no other component), then the component source files are replaceable.
+ This characteristic makes it easier to use version control, to use the file as a baseline, and to reuse the
+ source file.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Deployment replaceability:</strong> If two classes are deployed in a single executable file, then
+ each class is not independently replaceable in a deployed system. It is desirable for larger-granularity
+ components to be replaceable during deployment, which allows new versions of the component to be deployed
+ without having to rebuild the other components. This usually means that there is one file or one set of
+ files that deploy the component, and no other component.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Run-time replaceability:</strong> If a component can be redeployed into a running system, then it
+ is referred to as <em>run-time replaceable</em>. This enables you to upgrade software without loss of
+ availability.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Location transparency:</strong> Components with network-addressable interfaces are referred to as
+ having <em>location transparency</em>. This allows components to be relocated to other servers or to be
+ replicated on multiple servers to support fault tolerance, load balancing, and so on. These kinds of
+ components are often referred to as <em>distributed</em> or <em>distributable</em> components.
+ </p>
+ </li>
+ </ul>
+</div>
+<h3 align="left">
+ Component instantiation
+</h3>
+<p align="left">
+ A component may or may not be directly instantiated at run time.
+</p>
+<p align="left">
+ An indirectly instantiated component is implemented, or realized, by a set of classes, subcomponents, or parts. The
+ component itself does not appear in the implementation; it merely serves as a design that an implementation must
+ follow. The set of realizing classes, subcomponents, or parts must cover the entire set of operations specified in the
+ provided interface of the component. The manner of implementing the component is the responsibility of the implementer.
+</p>
+<p align="left">
+ A directly instantiated component specifies its own encapsulated implementation. It is instantiated as an addressable
+ object, which means that a design component has a corresponding construct in the implementation language; therefore, it
+ can be referenced explicitly.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/continuous_integration.xmi b/praclib/temp/core.tech.common.base/guidances/concepts/continuous_integration.xmi
new file mode 100644
index 0000000..ff76e51
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/continuous_integration.xmi
@@ -0,0 +1,55 @@
+<?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="-dhAMzNZNWufBnW0fPYQtBA"
+ name="continuous_integration,_NApSVdtxEdq7ovUqqSoGBQ" guid="-dhAMzNZNWufBnW0fPYQtBA"
+ changeDate="2007-11-15T10:06:18.000-0500" version="7.2.0">
+ <mainDescription><p>
+ Continuous integration is an implementation practice where team members integrate their work with completed&nbsp;<a
+ class="elementLink" href="./../../../opn.swd.prac.legacy_pm/guidances/concepts/change_set_430BF233.html"
+ guid="_1QU9MAIoEdyLh7vsrHZ4YA">Change Set</a>s from other developers, and test the application, before making their
+ work available to others. This&nbsp;enables detection of&nbsp;integration errors&nbsp;as&nbsp;early as possible, either
+ from compiler errors,&nbsp;configuration management&nbsp;system notifications,&nbsp;or&nbsp;failures reported by the
+ test suite. Ideally the integration is done automatically prior to <a class="elementLink"
+ href="./../../../core.tech.slot.base/guidances/guidelines/promoting_changes_9087B764.html"
+ guid="_SM4YIL6dEdqti4GwqTkbsQ">Promoting Builds</a>.
+</p>
+<p>
+ Continuous integration provides the following benefits:
+</p>
+<ol>
+ <li>
+ Improved feedback. Continuous integration shows constant and demonstrable progress.
+ </li>
+ <li>
+ Improved error detection. Continuous integration enables you to detect and address errors early, often minutes
+ after they’ve been injected into the product. Effective continuous integration requires automated unit testing with
+ appropriate code coverage.
+ </li>
+ <li>
+ Improved collaboration. Continuous integration enables team members to work together safely. They know that they
+ can make a change to their code, integrate the system, and determine very quickly whether or not their change
+ conflicts with others.
+ </li>
+ <li>
+ Improved system integration. By integrating continuously throughout your project you know that you can actually
+ build the system, thereby mitigating integration surprises at the end of the lifecycle.
+ </li>
+ <li>
+ Reduced&nbsp;number of parallel changes that need to be merged and tested.
+ </li>
+ <li>
+ Reduced number of errors found during system testing. All conflicts&nbsp;are resolved prior to making new change
+ sets available, by the person who is in the best position to resolve them.
+ </li>
+ <li>
+ Reduced technical risk. You always have an up-to-date system against which to test.
+ </li>
+ <li>
+ Reduced management risk. By continuously integrating your system you know exactly how much functionality that
+ you’ve built to date, improving your ability to predict when and if you’re actually going to be able to deliver the
+ necessary functionality.
+ </li>
+</ol></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/design_mechanism.xmi b/praclib/temp/core.tech.common.base/guidances/concepts/design_mechanism.xmi
new file mode 100644
index 0000000..342906c
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/design_mechanism.xmi
@@ -0,0 +1,29 @@
+<?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: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="-EG22TRyJ5TDKW6U88AXfhw"
+ name="design_mechanism,_hNXugOUuEdqGCpzGJ4tJOw" guid="-EG22TRyJ5TDKW6U88AXfhw"
+ changeDate="2007-08-14T11:55:16.468-0700" version="1.0.0">
+ <mainDescription><p align="left">
+ A Design Mechanism is a concrete representation of an&nbsp;<a class="elementLink"
+ href="./../../../core.tech.slot.base/guidances/concepts/arch_mech_2932DFB6.html"
+ guid="_mzxI0A4LEduibvKwrGxWxA">Architectural Mechanism</a>. It is refined from an <a class="elementLink"
+ href="./../../../core.tech.slot.base/guidances/concepts/analysis_mechanism_8369C159.html"
+ guid="_0gvqoMlgEdmt3adZL5Dmdw">Analysis Mechanism</a>&nbsp;and is further refined into an <a class="elementLink"
+ href="./../../../core.tech.slot.base/guidances/concepts/implementation_mechanism_C92E670B.html"
+ guid="_0LcUkA4LEduibvKwrGxWxA">Implementation Mechanism</a>&nbsp;as the design becomes more detailed.
+</p>
+<p align="left">
+ Design Mechanisms can be&nbsp;represented as specific design patterns and frameworks&nbsp;in the <a class="elementLink"
+ href="./../../../practice.tech.evolutionary_design.base/workproducts/design_D677D182.html"
+ guid="_0WuL8slgEdmt3adZL5Dmdw">Design</a>. They are used&nbsp;to guide development Design Mechanisms should still be
+ relatively independent of implementation but provide enough detailed information for implementation choices to be made
+ and software to be developed with confidence.
+</p>
+<p align="left">
+ See <a class="elementLink"
+ href="./../../../core.tech.common.base/guidances/guidelines/example_design_mechanisms_7762C0FB.html"
+ guid="_4k_Hsg4LEduibvKwrGxWxA">Example: Design Mechanisms</a>.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/executable_arch.xmi b/praclib/temp/core.tech.common.base/guidances/concepts/executable_arch.xmi
new file mode 100644
index 0000000..3ff4973
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/executable_arch.xmi
@@ -0,0 +1,49 @@
+<?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="-0R8BZWlcCQ3Rj84jY2M3Kw"
+ name="new_concept,_O1kAANvfEduv2KOT-Teh6w" guid="-0R8BZWlcCQ3Rj84jY2M3Kw" changeDate="2007-05-01T11:48:59.365-0400"
+ version="1.0.0">
+ <mainDescription><p>
+ An executable architecture is an implementation that realizes the <a class="elementLink"
+ href="./../../../core.tech.common.base/guidances/concepts/software_architecture_59A08DE0.html"
+ guid="__O7tAMVvEduLYZUGfgZrkQ">Software Architecture</a>. It is used to validate that the <a class="elementLink"
+ href="./../../../core.tech.common.base/guidances/concepts/arch_significant_requirements_1EE5D757.html"
+ guid="_HrZGIA4MEduibvKwrGxWxA">Architecturally Significant Requirements</a>&nbsp;are correctly implemented. It
+ validates the architecture as an integrated whole through integration tests. The team gains feedback about the
+ architecture from the customer or stakeholder by providing the executable architecture for verification. This way the
+ executable architecture helps to assure that the core functionality is stable enough to build the remainder of the
+ system.
+</p>
+<p>
+ An executable architecture is not a work product. It’s an identification or attribute of the implementation,
+ indicating&nbsp;that the implementation&nbsp;contains stable architecturally significant functionality.
+</p>
+<p>
+ Each version of an executable architecture should be more complete and robust than previous versions. The final
+ executable architecture contains all the elements that make up the architecture and should validate all architecturally
+ significant requirements. There may be rare exceptions where a portion of the architecture can't practically be
+ implemented until later due to uncontrollable circumstances such as constraints with third part software or unique
+ resources that are unavailable.&nbsp;Delaying any part of the architecture should be avoided as it raises significant
+ technical risk later in the project. But if circumstances dictate that some architectural risk can't be mitigated
+ until&nbsp;later in development, a&nbsp;conscious decision can be made to carry this risk forward until the
+ architecture can be fully implemented.
+</p>
+<p>
+ It's also possible to include non-architectural elements into an executable architecture. This will most likely happen
+ when addressing high risk issues early in the development cycle, which is an excellent practice. Two examples of
+ non-technical risks are resource risks and competitive risks. It may be desireable to obtain a difficult-to-get
+ resource early so they can work on a unique piece of the software now, rather than hoping the resource will be
+ available later. Or it may be useful to implement and deploy some early features to maintain market share against a
+ competitor. Think of the executable architecture as a way to mitigate architectural risk, which is the most significant
+ technical risk in a project. From this perspective, it's appropriate to mitigate other risks in the executable
+ architecture.
+</p>
+<p>
+ The difference between the executable architecture and the implementation later in the development cycle is that the
+ executable architecture is the result of a period of development (for example&nbsp;an iteration) that's dedicated to
+ elaborating the architecture. Later iterations build onto the executable architecture but are not flagged as an
+ executable architecture because they extend the system's functionality beyond the architectural framework.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/failure_analysis_rpt_creation.xmi b/praclib/temp/core.tech.common.base/guidances/concepts/failure_analysis_rpt_creation.xmi
new file mode 100644
index 0000000..dc22dcb
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/failure_analysis_rpt_creation.xmi
@@ -0,0 +1,81 @@
+<?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: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="-9gUpkUYqONF3x8UWwAO_zw"
+ name="failure_analysis_rpt_creation,_0jhR0MlgEdmt3adZL5Dmdw" guid="-9gUpkUYqONF3x8UWwAO_zw"
+ changeDate="2006-09-29T13:52:52.340-0700" version="1.0.0">
+ <mainDescription><h3>
+ Introduction
+</h3>
+<p>
+ During testing, you will encounter failures related to the execution of your tests in different forms, such as code
+ defects, user errors, program malfunctions, and general problems. This&nbsp;concept discusses some ways to conduct
+ failure analysis and then to report your findings.
+</p>
+<h3>
+ Failure Analysis
+</h3>
+<p>
+ After you have run your tests, it is good practice to identify inputs for review of the results of the testing effort.
+ Some likely sources are defects that occurred during the execution of test scripts, change request metrics, and test
+ log details.
+</p>
+<p>
+ Running test scripts results in errors of different kinds such as uncovered defects, unexpected behavior, or general
+ failure of the test script to run properly. When you run test scripts, one of the most important things to do is to
+ identify causes and effects of failure. It is important to differentiate failures in the system under test&nbsp;from
+ those related to the tests themselves.
+</p>
+<p>
+ Change request metrics are useful in analyzing and correcting failures in the testing. Select metrics that will
+ facilitate creation of incident reports from a collection of change requests.
+</p>
+<p>
+ Change request metrics that you may find useful in your failure analysis include:
+</p>
+<ul>
+ <li>
+ test coverage
+ </li>
+ <li>
+ priority
+ </li>
+ <li>
+ impact
+ </li>
+ <li>
+ defect trends
+ </li>
+ <li>
+ density
+ </li>
+</ul>
+<p>
+ Finally, one of the most critical sources of your failure analysis is the test log. Start by gathering the test log's
+ output during the implementation and execution of the tests. Relevant logs might come from many sources; they might be
+ captured by the tools you use (both test execution and diagnostic tools), generated by custom-written routines your
+ team has developed, output from the target test items themselves, and recorded manually be the tester. Gather all of
+ the available test log sources and examine their content. Check that all the scheduled testing executed to completion,
+ and that all the needed tests&nbsp;have been scheduled.
+</p>
+<h3>
+ Self-Documenting Tests
+</h3>
+<p>
+ For automated tests it is a best practice for the test itself to examine the results and clearly report itself as
+ passing or failing. This provides the most efficient way to run tests such that whole suites of tests can be run with
+ each test in turn determining whether it has passed or failed without the need for human intervention. When authoring
+ self-documenting tests, take extra care to ensure that the analysis of the results considers all possibilities.
+</p>
+<h3>
+ Recording Your Findings
+</h3>
+<p>
+ Once you have conducted your failure analysis, you may decide to formalize the results of this analysis by recording
+ your findings in a report. There are several factors that go into deciding whether to record your failure analysis in a
+ report. Some of the key factors include: level of testing formality, complexity of the testing effort, and the need to
+ communicate the testing results to the entire development team. In less formal environments, it may be sufficient to
+ record your failure analysis in&nbsp;a test evaluation summary.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/implementation_mechanism.xmi b/praclib/temp/core.tech.common.base/guidances/concepts/implementation_mechanism.xmi
new file mode 100644
index 0000000..120f687
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/implementation_mechanism.xmi
@@ -0,0 +1,45 @@
+<?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: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="-Rex8oOBv985RruZNrCW0rg"
+ name="implementation_mechanisms,_3ANskOK5EdqHEo0wLIc5jg" guid="-Rex8oOBv985RruZNrCW0rg"
+ changeDate="2006-09-25T13:09:13.255-0700" version="1.0.0">
+ <mainDescription><p>
+ An Implementation Mechanism is a refinement of a corresponding Design Mechanism that uses, for example, a particular
+ programming language and other implementation technology (such as a particular vendor's middleware product). An
+ Implementation Mechanism may instantiate one or more idioms or implementation patterns.
+</p>
+<p>
+ Review these points when you are considering Implementation Mechanisms:
+</p>
+<ul>
+ <li>
+ <p>
+ <b>Determine the ranges of characteristics.</b> Take the characteristics that you identified for the Design
+ Mechanisms into consideration to determine reasonable, economical, or feasible ranges of values to use in the
+ Implementation Mechanism candidate.
+ </p>
+ </li>
+ <li>
+ <p>
+ <b>Consider the cost of purchased components</b>. For Implementation Mechanism candidates, consider the cost of
+ licensing, the maturity of the product, your history or relationship with the vendor, support, and so forth in
+ addition to purely technical criteria.
+ </p>
+ </li>
+ <li>
+ <p>
+ <b>Conduct a search for the right components, or build the components.</b> You will often find that there is no
+ apparently suitable Implementation Mechanism for a particular Design Mechanism. This will either trigger a
+ search for the right product or make the need for in-house development apparent. You may also find that some
+ Implementation Mechanisms are not used at all.<br />
+ <br />
+ The choice of Implementation Mechanisms is based not only on a good match for the technical characteristics,
+ but also on the non-technical characteristics, such as cost. Some of the choices may be provisional. Almost all
+ have some risks attached to them. Performance, robustness, and scalability are nearly always concerns and must
+ be validated by evaluation, exploratory prototyping, or inclusion in the architectural prototype.
+ </p>
+ </li>
+</ul></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/key_abstractions.xmi b/praclib/temp/core.tech.common.base/guidances/concepts/key_abstractions.xmi
new file mode 100644
index 0000000..55c6117
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/key_abstractions.xmi
@@ -0,0 +1,25 @@
+<?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="-HJbvivaRmrZ6rdQcdFd78Q"
+ name="new_concept,_pLEGUNqGEdy88NBoQgfGyg" guid="-HJbvivaRmrZ6rdQcdFd78Q">
+ <mainDescription><p>
+ Key abstractions are the key concepts and abstractions that the system needs to handle. They are those things that,
+ without which, you could not describe the system.
+</p>
+<p>
+ The requirements are good sources for key abstractions. These abstractions are often easily identified because they
+ represent things that are significant to the business. For example, Customer and Account are typical key abstractions
+ in the banking business.
+</p>
+<p>
+ Each key abstraction should have a short description.&nbsp; The are usually not described in detail as they will change
+ and evolve&nbsp;during the course of the project (as they are refined into actual design elements).&nbsp;
+</p>
+<p>
+ The value of defining the key abstractions (and any obvious relationships between them) is that they establish a common
+ understanding of the key concepts amongst the team, thereby enabling them to develop a&nbsp;coherant solution that
+ handles them consistently.&nbsp;
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/pattern.xmi b/praclib/temp/core.tech.common.base/guidances/concepts/pattern.xmi
new file mode 100644
index 0000000..2c209ba
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/pattern.xmi
@@ -0,0 +1,293 @@
+<?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: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="_QvmkAMM1EdmSIPI87WLu3g"
+ name="patterns,_0YJvUMlgEdmt3adZL5Dmdw" guid="_QvmkAMM1EdmSIPI87WLu3g" changeDate="2007-02-26T01:45:45.531-0800"
+ version="1.0.0">
+ <mainDescription><h4>
+ Origins
+</h4>
+<p>
+ The idea of patterns as it is now applied to software design comes from the work of Christopher Alexander. He has
+ written widely on the subject of applying patterns to the design and construction of towns and buildings. Two of his
+ books, <em>A Pattern Language</em> [<a class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/references_6CCF393.html"
+ guid="_9ToeIB83Edqsvps02rpOOg">ALE77</a>] and <em>The Timeless Way of Building</em> [<a class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/references_6CCF393.html"
+ guid="_9ToeIB83Edqsvps02rpOOg">ALE79</a>] have had the greatest impact on the software community and the adoption of
+ software patterns for the design of software. His concepts of patterns and pattern language provide a model for the
+ capture of software design expertise in a form that can then be reapplied in recurring situations.
+</p>
+<h4>
+ A definition of patterns
+</h4>
+<p>
+ Today, the most commonly used definition of software patterns is from [<a class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/references_6CCF393.html"
+ guid="_9ToeIB83Edqsvps02rpOOg">GAM95</a>]:
+</p>
+<blockquote>
+ <p>
+ "A design pattern describes the problem, a solution to the problem consisting of a general arrangement of objects
+ and classes, when to apply the solution, and the consequences of applying the solution."
+ </p>
+</blockquote>
+<p>
+ This definition often serves only as a starting point, however. A richer definition, based on Alexander’s work, is
+ offered by Gabriel in his book, <em>A Timeless Way of Hacking</em> [<a class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/references_6CCF393.html"
+ guid="_9ToeIB83Edqsvps02rpOOg">ALU03</a>], in which each pattern is a three-part rule that expresses relationships
+ among a certain context, a certain system of forces that occur repeatedly in that context, and a certain software
+ configuration that allows these forces to resolve themselves.
+</p>
+<h4>
+ Describing patterns
+</h4>
+<p>
+ It is commonplace to describe patterns&nbsp;using the&nbsp;format made popular by Erich Gamma and his three colleagues
+ [<a class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/references_6CCF393.html"
+ guid="_9ToeIB83Edqsvps02rpOOg">GAM95</a>]. They have come to be known as the Gang of Four (GoF); therefore, their
+ description is known as the <strong>GoF format</strong>. The GoF format uses the following keywords to describe
+ object-oriented design patterns:
+</p>
+<ul>
+ <li>
+ <p>
+ <strong>Pattern name and classification:</strong> Naming the pattern allows design to work at a higher level of
+ abstraction, using a vocabulary of patterns. Gamma says that finding a good name is one of the hardest problems
+ of developing a catalogue of patterns (see <strong>Pattern catalogues</strong> later in this section).
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Intent:</strong> An answer to questions such as: What does the pattern do? What problem does it
+ address?
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Also known as:</strong> Other names for the pattern.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Motivation:</strong> A concrete scenario that illustrates a design problem and how the pattern solves
+ the problem.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Applicability:</strong> Instructions for how you can recognize situations in which patterns are
+ applicable.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Structure:</strong> A graphical representation of the classes in the pattern.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Participants:</strong> The responsibilities of the classes and objects that participate in the pattern.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Collaborations:</strong> How participants collaborate to fulfil their responsibilities.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Consequences:</strong> The results, side effects and trade offs caused by using the pattern.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Implementation:</strong> Guidance on the implementation of the pattern.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Sample code:</strong> Code fragments that illustrate the pattern’s implementation.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Known uses:</strong> Where to find real-world examples of the pattern.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Related patterns:</strong> Synergies, differences, and other pattern relationships.
+ </p>
+ </li>
+</ul>
+<p>
+ Although the GoF format is specifically intended for object-oriented development, you can use it, with slight
+ modification, to address other software patterns. A more general keyword format for software patterns based on
+ Alexander’s principles uses keywords such as <em>problem</em>, <em>context</em>, <em>forces</em> and <em>solution</em>.
+</p>
+<h4>
+ Pattern catalogs
+</h4>
+<p>
+ To assist with the identification and selection of patterns, various classification schemes have been proposed. One of
+ the early schemes, proposed by Buschmann and his associates, [<a class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/references_6CCF393.html"
+ guid="_9ToeIB83Edqsvps02rpOOg">BUS96</a>] uses three classifiers: granularity, functionality, and structured
+ principles. Of those three classifiers, it is their granularity classifier that has remained popular. Granularity
+ classifies patterns into three levels of abstraction:
+</p>
+<ul>
+ <li>
+ <p>
+ <strong>Architectural patterns:</strong> Architectural patterns express the fundamental structure of a software
+ scheme. Examples of architectural pattern include: layers, pipes and filters, and the model view controller
+ pattern.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Design patterns:</strong> Software architecture usually consists of smaller architectural units that
+ are described by design patterns. The GoF pattern is an example of a design pattern.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Idioms.</strong> An idiom is the lowest-level pattern, and it is specific to a programming language.
+ </p>
+ </li>
+</ul>
+<p>
+ Buschmann and his colleagues introduced four groups for categorizing architectural patterns:
+</p>
+<ul>
+ <li>
+ Structure
+ </li>
+ <li>
+ Distributed systems
+ </li>
+ <li>
+ Interactive systems
+ </li>
+ <li>
+ Adaptable systems
+ </li>
+</ul>
+<p>
+ The following table shows the categorization of their architectural patterns.
+</p>
+<table cellspacing="0" cellpadding="2" width="85%" summary="Categories for Architectural Patterns [BUS96]" border="1"
+valign="top">
+ <caption>
+ <strong>Categories for Architectural Patterns<br />
+ </strong>
+ </caption>
+ <tbody>
+ <tr>
+ <th scope="col">
+ <div align="center">
+ <strong>Category</strong>
+ </div>
+ </th>
+ <th scope="col">
+ <div align="center">
+ <strong>Pattern</strong>
+ </div>
+ </th>
+ </tr>
+ <tr>
+ <td>
+ Structure
+ </td>
+ <td>
+ <p>
+ Layers<br />
+ Pipes and filters<br />
+ Blackboard
+ </p>
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Distributed systems
+ </td>
+ <td>
+ Broker
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Interactive systems
+ </td>
+ <td>
+ Model view controller<br />
+ Presentation abstraction control
+ </td>
+ </tr>
+ <tr>
+ <td>
+ <p>
+ Adaptable systems
+ </p>
+ </td>
+ <td>
+ <p>
+ Reflection<br />
+ Micro kernel
+ </p>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<p>
+ For design patterns, Gamma's group categorized their design patterns by purpose, using three categories:
+</p>
+<ul>
+ <li>
+ Creational
+ </li>
+ <li>
+ Structural
+ </li>
+ <li>
+ Behavioral
+ </li>
+</ul>
+<h4>
+ Pattern languages
+</h4>
+<p>
+ In addition to the concept of patterns, Alexander also gave the software community the concept of a pattern language.
+ The purpose of developing a pattern language was to provide a vocabulary of design principles (patterns) that would
+ allow those who work, study, or live in buildings to communicate effectively with the planners and designers of those
+ buildings. Alexander explains that when using a pattern language:
+</p>
+<blockquote>
+ <p>
+ We always use it as a sequence, going through the patterns, moving always from the larger patterns to the smaller,
+ always from the ones that create structure to the ones which then embellish those structures, and then to those
+ that embellish the embellishments.
+ </p>
+</blockquote>
+<p>
+ In applying patterns in this way, Alexander advocated the use of generative pattern languages, ones that, given an
+ initial context, would always lead to good design.&nbsp; Alexander&nbsp;states:
+</p>
+<blockquote>
+ <p>
+ Thus, as in the case of natural languages, the pattern language is generative. It not only tells us the rules of
+ arrangement, but shows us how to construct arrangements — as many as we want — which satisfies the rules.
+ </p>
+</blockquote>
+<p>
+ In the application of software patterns, pattern names provide a vocabulary for the communication of software ideas.
+ The sequential application of patterns finds application in software design processes, both waterfall and iterative,
+ that successively apply architectural patterns, and then design patterns, and, finally, idioms to design and implement
+ a software system. Software processes, however, rely on the skills of the Architect and Developer roles to guide the
+ application of patterns, rather than a generative pattern language.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/refactoring.xmi b/praclib/temp/core.tech.common.base/guidances/concepts/refactoring.xmi
new file mode 100644
index 0000000..3abca21
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/refactoring.xmi
@@ -0,0 +1,85 @@
+<?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="-fj_9xjbrpaYNSETyCz5yJg"
+ name="refactoring,_Poc7IPDzEdqYgerqi84oCA" guid="-fj_9xjbrpaYNSETyCz5yJg" changeDate="2008-01-16T20:54:37.531-0500"
+ version="1.0.0">
+ <mainDescription><p>
+ Refactoring is a disciplined way to restructure code when small changes are made to the code to improve its design. An
+ important aspect of a refactoring is that it improves the design while not changing the behavior of the design; a
+ refactoring neither adds nor removes functionality.
+</p>
+<p>
+ Refactoring enables you to evolve the code slowly over time, to take an iterative and incremental approach to
+ implementation.
+</p>
+<p>
+ These are the types of refactoring:
+</p>
+<ol>
+ <li>
+ Code refactoring. Often referred to simply as refactoring, this is the refactoring of programming source code.
+ Examples of code refactorings include Rename Method, Encapsulate Field, Extract Class, Introduce Assertion, and
+ Pushdown Method.
+ </li>
+ <li>
+ Database refactoring. A database refactoring is a simple change to a database schema that improves its design while
+ retaining both its behavioral and informational semantics. Examples of database refactorings include Rename Column,
+ Split Table, Move Method to Database, Replace LOB with Table, Introduce Column Constraint, and Use Official Data
+ Source.
+ </li>
+ <li>
+ User interface (UI) refactoring. A UI refactoring is a simple change to the UI which retains its semantics.
+ Examples of UI refactorings include Align Entry Fields, Apply Common Button Size, Apply Common Font, Indicate
+ Format, Reword in Active Voice, and Increase Color Contrast.
+ </li>
+</ol>
+<p>
+ Martin Fowler [<a class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/references_6CCF393.html#FOW99"
+ guid="_9ToeIB83Edqsvps02rpOOg">FOW99</a>] identifies four key reasons to refactor:
+</p>
+<ul>
+ <li>
+ Refactoring improves the design of software
+ </li>
+ <li>
+ Refactoring makes software easier to understand
+ </li>
+ <li>
+ Refactoring helps you find bugs
+ </li>
+ <li>
+ Refactoring helps you program faster
+ </li>
+</ul>
+<p>
+ Refactoring can improve the design of existing code, but it does not take the place of considering the design before
+ writing code. Refactoring instead changes the role of up-front design, allowing the strictly design work to be more
+ abstract. Small-scale, very tactical decisions can be made during the implementation of the solution with confidence
+ that refactoring will ensure a quality implementation at that level. The designing of the solution before
+ implementation will be more lightweight and focused on broad factors that will drive the implementation.
+</p>
+<p>
+ There is an additional benefit of refactoring: it changes the way a developer thinks about the implementation when not
+ refactoring. The basic task of implementing a solution becomes solely about getting the solution to pass its developer
+ tests in the simplest way possible. Then the design of that solution can be examined and refactored separately. Even if
+ these two things -- implementation of the solution and then improvement -- are just a minute apart, it can be freeing
+ for a developer to single-mindedly create code that causes a test to pass, and then separately single-mindedly improve
+ that code.
+</p>
+<p>
+ These are some additional resources:
+</p>
+<ul>
+ <li>
+ <a href="http://www.refactoring.com/" target="_blank" ><u><font
+ color="#0000ff">http://www.refactoring.com/</font></u></a>
+ </li>
+ <li>
+ <a href="http://www.agiledata.org/essays/databaseRefactoring.html" ><u><font
+ color="#0000ff">http://www.agiledata.org/essays/databaseRefactoring.html</font></u></a>
+ </li>
+</ul></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/requirement_attributes.xmi b/praclib/temp/core.tech.common.base/guidances/concepts/requirement_attributes.xmi
new file mode 100644
index 0000000..e6a44e3
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/requirement_attributes.xmi
@@ -0,0 +1,72 @@
+<?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="-fCBrf_5JlrmuKgyrCaKGOA"
+ name="requirement_attributes_1,_VQ268O0KEdqHTdbLTmC5IQ" guid="-fCBrf_5JlrmuKgyrCaKGOA"
+ authors="Chris Sibbald" changeDate="2006-09-20T11:41:34.000-0700" version="0.2">
+ <mainDescription><p>
+ Attributes are a very important source of requirements information. Just as every person has attributes (age, hair
+ color, gender), each requirement has a source, a relative importance, and time it was created. Attributes do more than
+ simply clarify a&nbsp;requirement.&nbsp; If created properly, they can yield significant information about the state of
+ the system. Just as you can run a database query to find all men with brown hair over age 30, given our human example,
+ you can run queries on the status of requirements to find&nbsp;all high-priority requirements from the customer in the
+ last 30 days. <a href="./../../../core.tech.common.base/guidances/supportingmaterials/references_6CCF393.html"
+ guid="_9ToeIB83Edqsvps02rpOOg">[TEL06]</a>
+</p>
+<h4>
+ Examples of attributes
+</h4>
+<p>
+ Listed below is a partial list of some common attributes and a brief description of their meaning. Some attributes are
+ best described as a number, date, Boolean (true or false) or a text field for entering free format comments. Other
+ attributes can be expressed as lists. For instance, priority type is a list of high, medium, and low; Weekday is a list
+ which includes Monday, Tuesday, and so on.
+</p>
+<p>
+ <em>Source</em> - Person, document or other origin of a given requirement.&nbsp; This is&nbsp;useful&nbsp;for
+ determining whom to call for questions or for grouping&nbsp;requirements according to the person making the demands.
+</p>
+<p>
+ <em>Priority</em> - Statement of relative importance of the requirement, either to the system (mandatory, critical,
+ optional) or to other requirements (high, medium, low). It is good to track the mandatory or high-priority
+ items&nbsp;as an indication of how well the system will meet the greatest needs or for compliance-related metrics.
+</p>
+<p>
+ <em>Assigned to</em> - Who in the organization is responsible for making sure the requirement is met (person's name or
+ organizational name).
+</p>
+<p>
+ <em>Comments</em> - Reviewer's or writer's comments on a requirement.
+</p>
+<p>
+ <em>Difficulty</em> - An indication of the level of effort needed or how hard it will be to implement the requirement
+ (high, medium, low).
+</p>
+<p>
+ <em>Status</em> - Degree of completeness (completed, partial, not started).
+</p>
+<p>
+ <em>Risk</em> - Confidence measure on the likelihood of meeting (or not meeting) a requirement. Could be high, medium,
+ low or the integers one through ten.
+</p>
+<p>
+ <em>Due By</em> - Date the requirement must be provided.
+</p>
+<p>
+ <em>Method of verification</em> - Qualification type to be used to verify that a requirement has been met: analysis,
+ demonstration, inspection, test, and walkthrough.
+</p>
+<p>
+ <em>Level of Test</em> - Describes the verification lifecycle stage at which the requirement is determined to be met:
+ unit test, component, system or product.
+</p>
+<p>
+ <em>Subsystem Allocation</em> - Name of system or subsystem a requirement is to be assigned to (for instance, flight
+ control module, wing assembly, passenger cabin).
+</p>
+<p>
+ <em>Test Number</em> - Identification of a specific test or other method of verification.
+</p><br />
+<br /></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/requirements.xmi b/praclib/temp/core.tech.common.base/guidances/concepts/requirements.xmi
new file mode 100644
index 0000000..e67bc9c
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/requirements.xmi
@@ -0,0 +1,58 @@
+<?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="_eUfzwMMyEdmdo9HxCRR_Gw"
+ name="requirements,_0Wh-sMlgEdmt3adZL5Dmdw" guid="_eUfzwMMyEdmdo9HxCRR_Gw" changeDate="2008-02-11T14:03:51.917-0800"
+ version="1.0.0">
+ <mainDescription><p>
+ Requirements are the project team's to-do list.
+</p>
+<p>
+ Requirements define what is needed and focus the project team. They are the primary method used to communicate the
+ goals of the project to everyone on the team.
+</p>
+<p>
+ Requirements define:
+</p>
+<ul>
+ <li>
+ What the stakeholders need; and
+ </li>
+ <li>
+ What the system must include to satisfy the stakeholder needs.
+ </li>
+</ul>
+<p>
+ Requirements are the basis for capturing and communicating needs, managing expectations, prioritizing and assigning
+ work, verifying and validating the system (acceptance), and managing the scope of the project.
+</p>
+<p>
+ Requirements may take different forms, including use cases and scenarios, unstructured text, structured text, or a
+ combination, and they may be stated at different levels of granularity. At the highest level of granularity,
+ features&nbsp;define the services that the system must provide to solve the customer's problem. These are captured as
+ structured or unstructured text in the project vision. At the next level of granularity, use cases can be used to
+ define the functionality that the system must provide to deliver the required features.&nbsp;Use cases&nbsp;describe
+ the sequence of actions performed by the system to yield an observable result of value.
+</p>
+<p>
+ As mentioned, a&nbsp;system must perform according to the behavior that can be specified as use cases. However, there
+ are system requirements that do not represent a specific behavior, also&nbsp;known as system-wide requirements,
+ including:
+</p>
+<ul>
+ <li>
+ Legal and regulatory requirements, as well as application standards
+ </li>
+ <li>
+ Quality attributes of the system to be built, including usability, reliability, performance, and supportability
+ requirements
+ </li>
+ <li>
+ Interface requirements to be able to communicate with external systems
+ </li>
+ <li>
+ Design constraints, such as those for operating systems and environments and for compatibility with other software
+ </li>
+</ul></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/resources/4plus1_2.jpg b/praclib/temp/core.tech.common.base/guidances/concepts/resources/4plus1_2.jpg
new file mode 100644
index 0000000..24cfc97
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/resources/4plus1_2.jpg
Binary files differ
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/resources/ATMUCdiagram.GIF b/praclib/temp/core.tech.common.base/guidances/concepts/resources/ATMUCdiagram.GIF
new file mode 100644
index 0000000..c3428b5
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/resources/ATMUCdiagram.GIF
Binary files differ
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/resources/ArchMechStates.JPG b/praclib/temp/core.tech.common.base/guidances/concepts/resources/ArchMechStates.JPG
new file mode 100644
index 0000000..a1b1f17
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/resources/ArchMechStates.JPG
Binary files differ
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/resources/im_uc.gif b/praclib/temp/core.tech.common.base/guidances/concepts/resources/im_uc.gif
new file mode 100644
index 0000000..f271c09
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/resources/im_uc.gif
Binary files differ
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/resources/iteration_1.GIF b/praclib/temp/core.tech.common.base/guidances/concepts/resources/iteration_1.GIF
new file mode 100644
index 0000000..1f1a19b
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/resources/iteration_1.GIF
Binary files differ
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/resources/md_acto2.gif b/praclib/temp/core.tech.common.base/guidances/concepts/resources/md_acto2.gif
new file mode 100644
index 0000000..29ede3a
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/resources/md_acto2.gif
Binary files differ
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/resources/md_acto3.gif b/praclib/temp/core.tech.common.base/guidances/concepts/resources/md_acto3.gif
new file mode 100644
index 0000000..43fbf21
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/resources/md_acto3.gif
Binary files differ
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/resources/ucprepst.gif b/praclib/temp/core.tech.common.base/guidances/concepts/resources/ucprepst.gif
new file mode 100644
index 0000000..5f9e869
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/resources/ucprepst.gif
Binary files differ
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/resources/ucstrct.gif b/praclib/temp/core.tech.common.base/guidances/concepts/resources/ucstrct.gif
new file mode 100644
index 0000000..4458bcb
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/resources/ucstrct.gif
Binary files differ
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/resources/visual.gif b/praclib/temp/core.tech.common.base/guidances/concepts/resources/visual.gif
new file mode 100644
index 0000000..6f4674c
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/resources/visual.gif
Binary files differ
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/software_architecture.xmi b/praclib/temp/core.tech.common.base/guidances/concepts/software_architecture.xmi
new file mode 100644
index 0000000..727ecd6
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/software_architecture.xmi
@@ -0,0 +1,311 @@
+<?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="-UQ_e8kozIP11Xu008RJd-A"
+ name="new_concept,__O7tAMVvEduLYZUGfgZrkQ" guid="-UQ_e8kozIP11Xu008RJd-A" changeDate="2008-02-14T15:52:08.453-0500"
+ version="7.2.0">
+ <mainDescription><h3>
+ Introduction
+</h3>
+<p>
+ Software architecture is a concept that is easy to understand, and that most engineers intuitively feel, especially
+ with a little experience, but it is hard to define precisely. In particular, it is difficult to draw a sharp line
+ between design and architecture-architecture is one aspect of design that concentrates on some specific features.
+</p>
+<p>
+ In An Introduction to Software Architecture, David Garlan and Mary Shaw suggest that software architecture is a level
+ of design concerned with issues: "Beyond the algorithms and data structures of the computation; designing and
+ specifying the overall system structure emerges as a new kind of problem. Structural issues include gross organization
+ and global control structure; protocols for communication, synchronization, and data access; assignment of
+ functionality to design elements; physical distribution; composition of design elements; scaling and performance; and
+ selection among design alternatives." <a class="elementlinkwithusertext"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/tech_references_6CCF393.html"
+ guid="_9ToeIB83Edqsvps02rpOOg">[GAR93]</a>
+</p>
+<p>
+ But there is more to architecture than just structure; the IEEE Working Group on Architecture defines it as "the
+ highest-level concept of a system in its environment" <a class="elementlinkwithusertext"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/tech_references_6CCF393.html"
+ guid="_9ToeIB83Edqsvps02rpOOg">[IEP1471]</a>. It also encompasses the "fit" with system integrity, with economical
+ constraints, with aesthetic concerns, and with style. It is not limited to an inward focus, but takes into
+ consideration the system as a whole in its user environment and its development environment - an outward focus.
+</p>
+<p>
+ The architecture focuses on specific aspects of the overall system design, concentrating on structure, essential
+ elements, key scenarios and those aspects that have a lasting impact on system qualities such as performance,
+ reliability, adaptability and cost. It also defines the set of <a class="elementLink"
+ href="./../../../core.tech.common.base/guidances/concepts/arch_mechanism_2932DFB6.html"
+ guid="_mzxI0A4LEduibvKwrGxWxA">Architectural Mechanism</a>s, <a class="elementLink"
+ href="./../../../core.tech.common.base/guidances/concepts/pattern_10BE6D96.html"
+ guid="_0YJvUMlgEdmt3adZL5Dmdw">Pattern</a>s and styles that will guide the rest of the design, assuring its integrity.
+</p>
+<h3>
+ Purpose of Architecture
+</h3>
+<p>
+ The architecture can be used for many things:
+</p>
+<ul>
+ <li>
+ <strong>To describe the essential structure of the system and the decisions guiding the structure of the
+ system</strong> so the integrity and understandability of the system is assured.
+ </li>
+ <li>
+ <a id="Comment71_" name="Comment71_"><strong>To identify and attack risks to the system</strong> (using the
+ architecture as an artifact of governance)</a>
+ </li>
+ <li>
+ <strong>To provide context and guidance for developers</strong> to construct the system by describing the
+ motivations behind the architectural decisions so those decisions can be robustly implemented. The architecture
+ servces as the blueprint for development.&nbsp;For example, the architect may place constraints on how data is
+ packaged and communicated between different parts of the system. This may appear to be a burden, but the
+ justification in the Architecture Notebook can explain that there is a significant performance bottleneck when
+ communicating with a legacy system. The rest of the system must adapt to this bottleneck by following a specific
+ data packaging scheme.
+ </li>
+ <li>
+ <strong>To provide an overview of the system to whoever must maintain the architecture</strong>, as well as an
+ understanding of the motivation behind the important technical decisions.&nbsp; Team members who were not involved
+ in those architectural decisions need to understand the reasoning behind the&nbsp;context of the architecture so
+ they can best address the needs of the system.
+ </li>
+ <li>
+ <strong>To define the project structure and team organization.</strong> Architectural elements make excellent units
+ of implementation, unit testing, integration, configuration management and&nbsp;documentation.&nbsp;&nbsp; They can
+ also be used to define&nbsp; so that managers can plan the project.
+ </li>
+</ul>
+<h3>
+ Architecture Description
+</h3>
+<p>
+ To speak and reason about software architecture, you must first define an architectural representation, a way of
+ describing important aspects of an architecture.
+</p>
+<p>
+ The following is some information that is worth capturing as part of the software architecture:
+</p>
+<ul>
+ <li>
+ Architectural goals (see <a class="elementLinkWithType"
+ href="./../../../core.tech.common.base/guidances/concepts/arch_goals_CB41D8AE.html"
+ guid="_HlRqANpbEdyP58ppo1Ieaw">Concept: Architectural Goals</a>)
+ </li>
+ <li>
+ References to architecturally significant requirements and how the architecture addresses those requirements,
+ including&nbsp;key scenarios that describe critical behavior of the system (see <a class="elementLinkWithType"
+ href="./../../../core.tech.common.base/guidances/concepts/arch_significant_requirements_1EE5D757.html"
+ guid="_HrZGIA4MEduibvKwrGxWxA">Concept: Architecturally Significant Requirements</a>)
+ </li>
+ <li>
+ Contraints on the architecture and how the architecture addressess those constraints (see <a
+ class="elementLinkWithType"
+ href="./../../../core.tech.common.base/guidances/concepts/arch_constraints_AE56B662.html"
+ guid="_jdKSsNpiEdyP58ppo1Ieaw">Concept: Architectural Constraints</a>)
+ </li>
+ <li>
+ Key abstractions (see <a class="elementLinkWithType"
+ href="./../../../core.tech.common.base/guidances/concepts/key_abstractions_1474DBF2.html"
+ guid="_pLEGUNqGEdy88NBoQgfGyg">Concept: Key Abstractions</a>)
+ </li>
+ <li>
+ <a class="elementLink" href="./../../../core.tech.common.base/guidances/concepts/arch_mechanism_2932DFB6.html"
+ guid="_mzxI0A4LEduibvKwrGxWxA">Architectural Mechanism</a>s and where they should be applied (see <a
+ class="elementLinkWithType" href="./../../../core.tech.common.base/guidances/concepts/arch_mechanism_2932DFB6.html"
+ guid="_mzxI0A4LEduibvKwrGxWxA">Concept: Architectural Mechanism</a>).
+ </li>
+ <li>
+ Description of the partitioning approach, as well as a description of the key partitions.&nbsp; For example,
+ Layering&nbsp;(see <a class="elementLinkWithType"
+ href="./../../../core.tech.common.base/guidances/guidelines/layering_F169CF07.html"
+ guid="_0gpkAMlgEdmt3adZL5Dmdw">Guideline: Layering</a>)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+ </li>
+ <li>
+ Description of the deployment approach, as well as how key components are allocated to deployment
+ nodes.&nbsp;&nbsp;&nbsp;&nbsp;
+ </li>
+ <li>
+ References to architecturally significant design elements (see <a class="elementLinkWithType"
+ href="./../../../core.tech.common.base/guidances/concepts/component_CB167D48.html"
+ guid="_0YP18MlgEdmt3adZL5Dmdw">Concept: Component</a>)&nbsp;
+ </li>
+ <li>
+ Critical system interfaces (see <a class="elementLinkWithType"
+ href="./../../../core.tech.common.base/guidances/guidelines/repres_interfaces_to_ext_systems_51A34F6E.html"
+ guid="_0gjdYMlgEdmt3adZL5Dmdw">Guideline: Representing Interfaces to External Systems</a>)
+ </li>
+ <li>
+ Assets that have been reused and/or assets that have been developed to be reused (for more information, see <a
+ class="elementLinkWithType"
+ href="./../../../core.tech.common.base/guidances/guidelines/software_reuse_B6B04C26.html"
+ guid="_vO2uoO0OEduUpsu85bVhiQ">Guideline: Software Reuse</a>)
+ </li>
+ <li>
+ Guidance, decisions, and constraints the developers must follow in building the system, along with justification
+ </li>
+</ul>
+<p>
+ The architecture can contain any information and references that are appropriate in communicating how developers should
+ build the system.
+</p>
+<h4>
+ Architectural Representation
+</h4>
+<p>
+ The architecture can be represented in many forms and from many viewpoints, depending on the needs of the project and
+ the preferences of the project team. It need not be a formal document. The essence of the architecture can often be
+ communicated through a series of simple diagrams on a whiteboard; or as a list of decisions. The illustration just
+ needs to show the nature of the proposed solution, convey the governing ideas, and represent the major building blocks
+ to make it easier to communicate the architecture to the project team and stakeholders.
+</p>
+<p>
+ If a more complex system is required, then the architecture can be represented as a more comprehensive set
+ of&nbsp;views that describe the architecture from a number of viewpoints. For more information, see <a
+ class="elementLinkWithType"
+ href="./../../../core.tech.common.base/guidances/concepts/arch_views_viewpoints_7A6CD31.html"
+ guid="_kgtcoNc8Edyd7OybSySFxg">Concept: Architectural Views and Viewpoints</a>.
+</p>
+<p>
+ The architecture can be expressed as a simple metaphor or as a comparison to a predefined architectural style or set of
+ styles. It may be a precise set of models or documents that describe the various aspects of the system's key elements.
+ Expressing it as skeletal implementation is another option - although this may need to be baselined and preserved to
+ ensure that the essence of the system can be understood as the system grows. Choose the medium that best meets the
+ needs of the project.
+</p>
+<h3>
+ Architectural Patterns
+</h3>
+<p>
+ Architectural <a class="elementLink" href="./../../../core.tech.common.base/guidances/concepts/pattern_10BE6D96.html"
+ guid="_0YJvUMlgEdmt3adZL5Dmdw">Pattern</a>s are ready-made forms that solve recurring architectural problems. An
+ architectural framework or an architectural infrastructure (middleware) is a set of components on which you can build a
+ certain kind of architecture. Many of the major architectural difficulties should be resolved in the framework or in
+ the infrastructure, usually targeted to a specific domain: command and control, MIS, control system, and so on.
+</p>
+<p>
+ <a class="elementlinkwithusertext"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/tech_references_6CCF393.html"
+ guid="_9ToeIB83Edqsvps02rpOOg">[BUS96]</a> groups architectural patterns according to the characteristics of the
+ systems in which they are most applicable, with one category dealing with more general structuring issues. The table
+ shows the categories presented in <a class="elementlinkwithusertext"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/tech_references_6CCF393.html"
+ guid="_9ToeIB83Edqsvps02rpOOg">[BUS96]</a> and the patterns they contain.
+</p>
+<div align="center">
+ <table
+ style="BORDER-RIGHT: rgb(128,128,128) 1px solid; BORDER-TOP: rgb(128,128,128) 1px solid; BORDER-LEFT: rgb(128,128,128) 1px solid; BORDER-BOTTOM: rgb(128,128,128) 1px solid"
+ cellspacing="0" bordercolordark="#808080" cellpadding="4" width="85%" bordercolorlight="#808080" border="1">
+ <tbody>
+ <tr>
+ <th id="col1" width="50%">
+ Category
+ </th>
+ <th id="col2" width="50%">
+ Pattern
+ </th>
+ </tr>
+ <tr>
+ <th id="row2" align="left" headers="col1" width="50%" rowspan="3">
+ Structure
+ </th>
+ <td headers="row2 col2" width="50%">
+ Layers
+ </td>
+ </tr>
+ <tr>
+ <td headers="row2 col2" width="50%">
+ Pipes and Filters
+ </td>
+ </tr>
+ <tr>
+ <td headers="row2 col2" width="50%">
+ Blackboard
+ </td>
+ </tr>
+ <tr>
+ <th id="row3" align="left" headers="col1" width="50%">
+ Distributed Systems
+ </th>
+ <td headers="row3 col2" width="50%">
+ Broker
+ </td>
+ </tr>
+ <tr>
+ <th id="row4" align="left" headers="col1" width="50%" rowspan="2">
+ Interactive Systems
+ </th>
+ <td headers="row4 col2" width="50%">
+ Model-View-Controller
+ </td>
+ </tr>
+ <tr>
+ <td headers="row4 col2" width="50%">
+ Presentation-Abstraction-Control
+ </td>
+ </tr>
+ <tr>
+ <th id="row5" align="left" headers="col1" width="50%" rowspan="2">
+ Adaptable Systems
+ </th>
+ <td headers="row5 col2" width="50%">
+ Reflection
+ </td>
+ </tr>
+ <tr>
+ <td headers="row5 col2" width="50%">
+ Microkernel
+ </td>
+ </tr>
+ </tbody>
+ </table><br />
+</div>
+<p>
+ Refer to <a class="elementlinkwithusertext"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/tech_references_6CCF393.html"
+ guid="_9ToeIB83Edqsvps02rpOOg">[BUS96]</a> for a complete description of these patterns.
+</p>
+<h3>
+ <a id="Architectural Style" name="Architectural Style">Architectural Style</a>
+</h3>
+<p>
+ A software architecture (or an architectural view) may have an attribute called <b>architectural style</b>, which
+ reduces the set of possible forms to choose from, and imposes a certain degree of uniformity to the architecture. The
+ style may be defined by a set of patterns, or by the choice of specific components or connectors as the basic building
+ blocks.
+</p>
+<h3>
+ Architectural Timing
+</h3>
+<p>
+ Teams should expect to spend more time on architectural issues early in the project.&nbsp; This allows the team to
+ reduce risk associated to technology early in the project, hence allowing the team to more rapidly reduce the variance
+ in their estimate on what they can deliver at what time, Examples of architectural issues that needs to be resolved
+ early on include
+</p>
+<ul>
+ <li>
+ Component and their major interfaces
+ </li>
+ <li>
+ Major technology choices (platform, languages, architecture frameworks / reference architectures, etc.)
+ </li>
+ <li>
+ Interfaces to external systems
+ </li>
+ <li>
+ Common services (persistency mechanisms, logging mechanisms, garbage collection, etc.)
+ </li>
+ <li>
+ Key patterns
+ </li>
+</ul>
+<h3>
+ Validating the Architecture
+</h3>
+<p>
+ The best way to validate the architecture is to actually implement it.&nbsp; For more information, see <a
+ class="elementLink" href="./../../../core.tech.common.base/guidances/concepts/executable_arch_D4E68CBD.html"
+ guid="_O1kAANvfEduv2KOT-Teh6w">Executable Architecture</a>.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/system_wide_requirements.xmi b/praclib/temp/core.tech.common.base/guidances/concepts/system_wide_requirements.xmi
new file mode 100644
index 0000000..96fddd9
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/system_wide_requirements.xmi
@@ -0,0 +1,103 @@
+<?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="-3SXuKijeVOZalgLPgWRyFA"
+ name="supporting_requirements_1,_VXZ5wO0IEdqHTdbLTmC5IQ" guid="-3SXuKijeVOZalgLPgWRyFA"
+ authors="Chris Sibbald" changeDate="2008-02-11T13:54:28.636-0800" version="0.2">
+ <mainDescription><h3>
+ Definition
+</h3>
+<p>
+ System-wide requirements are requirements that&nbsp;define necessary system quality attributes&nbsp;such as
+ performance, usability and reliability, as well as global functional requirements&nbsp;that are not captured in
+ behavioral requirements artifacts such as use cases.
+</p>
+<h3>
+ System-wide&nbsp;Requirements Categories
+</h3>
+<p>
+ System-wide&nbsp;requirements are categorized according to the FURPS+ model (Functional, Usability, Reliability,
+ Performance, Supportability + constraints). Constraints&nbsp;include design, implementation, interfaces, physical
+ constraints, and business rules. A description of each of these types of requirements follows.
+</p>
+<p>
+ System-wide requirements and use cases, together, define the requirements of the system. These requirements support the
+ features listed in the vision statement. Each requirement should&nbsp;support at least one feature, and each feature
+ should be supported by at least one requirement.
+</p>
+<p>
+ In general, <strong>functional</strong> requirements describe behavior and can be captured as&nbsp;use cases.
+ <strong>Non-functional</strong> requirements are captured in a system-wide requirements specification.&nbsp;However,
+ nonfunctional requirements that are closely associated with a particular use case are often captured within the
+ use-case specification itself to simplify communication and maintenance.&nbsp;Similarly, there are global, or
+ system-wide functional requirements that are often captured among the system-wide requirements for the same
+ reasons.&nbsp;
+</p>
+<h4>
+ Functional requirements
+</h4>
+<p>
+ Functional requirements include all the overarching, system-wide functional requirements that are not expressed as use
+ cases. These functional requirements represent the main system features that are familiar within the business domain or
+ technically oriented requirements such as auditing, licensing, localization, e-mail, online help, printing, reporting,
+ security, system management, or workflow.
+</p>
+<h4>
+ Usability requirements
+</h4>
+<p>
+ Usability requirements include requirements based on human factors and user-interface issues such as accessibility,
+ interface aesthetics, and consistency within the user interface.
+</p>
+<h4>
+ Reliability requirements
+</h4>
+<p>
+ Reliability requirements include aspects such as availability, accuracy, predictability, frequency of failure or
+ recoverability of the system from shut-down failure.
+</p>
+<h4>
+ Performance requirements
+</h4>
+<p>
+ Performance requirements address concerns such as throughput of information through the system, system response time
+ and resource usage.
+</p>
+<h4>
+ Supportability requirements
+</h4>
+<p>
+ Supportability requirements include&nbsp;requirements such as compatibility and the abilities to test, adapt, maintain,
+ configure, install, scale, and localize the system.
+</p>
+<h4>
+ + Constraints
+</h4>
+<p>
+ The <strong>+</strong> of the FURPS+ acronym allows you to specify constraints, such as design, implementation,
+ interfaces, physical constraints, and business rules:
+</p>
+<ul>
+ <li>
+ <strong>Design constraints</strong> limit the design and state requirements on the approach that should be taken in
+ developing the system.
+ </li>
+ <li>
+ <strong>Implementation constraints</strong> put limits on coding or construction (required standards, languages,
+ tools, or platform)
+ </li>
+ <li>
+ <strong>Interface constraints</strong> are requirements to interact with external systems, describing protocols or
+ the nature of the information that is passed across that interface.
+ </li>
+ <li>
+ <strong>Physical constraints</strong> affect the hardware or packaging housing the system (shape, size, and
+ weight).
+ </li>
+ <li>
+ <strong>Business rules</strong> are policies or decisions that govern how the business operates. They may constrain
+ the steps described in the us-case flow.
+ </li>
+</ul></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/test_ideas.xmi b/praclib/temp/core.tech.common.base/guidances/concepts/test_ideas.xmi
new file mode 100644
index 0000000..7a154f8
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/test_ideas.xmi
@@ -0,0 +1,41 @@
+<?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: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="_uqL2gMM3EdmSIPI87WLu3g"
+ name="test_ideas,_0jnYcMlgEdmt3adZL5Dmdw" guid="_uqL2gMM3EdmSIPI87WLu3g" changeDate="2006-07-20T15:10:39.401-0700">
+ <mainDescription><p>
+ <strong>Test Ideas List</strong> - A list of brief statements identifying tests that are potentially useful to conduct.
+</p>
+<p>
+ <strong>Test Ideas Catalog</strong> - A catalog of common faults and mistakes done when developing software.
+</p>
+<ul>
+ <li>
+ Test Ideas will describe any of the elements of an executable test.&nbsp;
+ </li>
+ <li>
+ Test ideas ensure the important ideas are not forgotten and are detailed later in test cases.&nbsp;&nbsp;
+ </li>
+ <li>
+ Test Ideas are to be captured at a less-specific level in an intermediate form.
+ </li>
+ <li>
+ Test ideas are more reviewable and understandable then complete tests.&nbsp; Making the reasoning behind the test
+ idea clearer.&nbsp;
+ </li>
+ <li>
+ Test ideas support more powerful test, by not constraining the tester.&nbsp; Making it easier to create tests that
+ validate more then just the defined requirements.
+ </li>
+ <li>
+ Test Ideas are often based on explicit and implicit fault modules, to include but not limited to Booleans,
+ boundaries and method calls.&nbsp; Test Ideas Lists will contain test ideas from many faults models derived for one
+ or many work products.
+ </li>
+</ul>
+<p>
+ Creating test ideas before testing for review and inspection of design work products assists in discovering design or
+ analysis errors.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/traceability.xmi b/praclib/temp/core.tech.common.base/guidances/concepts/traceability.xmi
new file mode 100644
index 0000000..51020be
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/traceability.xmi
@@ -0,0 +1,74 @@
+<?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="-TksCtMgc0b4QqzwzniGvIw"
+ name="traceability_1,_eYtQQO0KEdqHTdbLTmC5IQ" guid="-TksCtMgc0b4QqzwzniGvIw" authors="Chris Sibbald"
+ changeDate="2006-05-01T03:37:44.000-0700" changeDescription="Added concept in accordance with Feb 23, 2006 minutes of RM SIG meeting."
+ version="0.1">
+ <mainDescription><p align="left">
+ Traceability is about understanding how high-level requirements (objectives, goals, aims, aspirations, expectations,
+ needs) are transformed into low-level requirements, how they are implemented, and how they are verified.
+</p>
+<p>
+ Using traceability can provide the following benefits <a class="elementlinkwithusertext"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/references_6CCF393.html#HUL05"
+ guid="_9ToeIB83Edqsvps02rpOOg">[HUL05]</a>:
+</p>
+<ul>
+ <li>
+ <strong>Greater confidence in meeting objectives</strong>
+ </li>
+</ul>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p>
+ Establishing traceability engenders greater reflection on how objectives are satisfied.&nbsp; Traceability permits
+ coverage analysis to ensure that everything you have done everything that you agreed to do and only what you agreed
+ to do.
+ </p>
+</blockquote>
+<ul>
+ <li>
+ <strong>Ability to assess the impact of change</strong>
+ </li>
+</ul>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p>
+ Traceability permits various forms of impact analysis that can be used to assess the impact of a proposed change on
+ the cost, schedule, and technical aspects of the project.
+ </p>
+</blockquote>
+<ul>
+ <li>
+ <strong>Improved accountability</strong>
+ </li>
+</ul>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p>
+ Traceability provides greater clarity about how work contributes to the whole.
+ </p>
+</blockquote>
+<ul>
+ <li>
+ <strong>Ability to track progress</strong>
+ </li>
+</ul>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p>
+ It is notoriously difficult to measure progress when all that you are doing is creating and revising artifacts.
+ Traceability processes allow precise measures of progress, such as: Is there a design artifact for each
+ requirement? Is there a test case for each requirement?.
+ </p>
+</blockquote>
+<ul>
+ <li>
+ <strong>Ability to balance cost against benefit</strong>
+ </li>
+</ul>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p>
+ Relating product components to the requirements allows you to compare benefits to costs.
+ </p>
+</blockquote><br dir="ltr" />
+<br /></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/types_of_test.xmi b/praclib/temp/core.tech.common.base/guidances/concepts/types_of_test.xmi
new file mode 100644
index 0000000..9e7ebb5
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/types_of_test.xmi
@@ -0,0 +1,152 @@
+<?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: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="_y-_PIMPdEdmbOvqy4O0adg"
+ name="types_of_test,_0aJ6cMlgEdmt3adZL5Dmdw" guid="_y-_PIMPdEdmbOvqy4O0adg" changeDate="2006-09-20T15:37:14.071-0700">
+ <mainDescription><h3>
+ Introduction
+</h3>
+<p>
+ There is much more to testing computer software than simply evaluating the functions, interface, and response-time
+ characteristics of a target-of-test.&nbsp;Additional tests must focus on characteristics and attributes, such as the
+ target-of-test.
+</p>
+<ul>
+ <li>
+ integrity (resistance to failure)
+ </li>
+ <li>
+ ability to be installed and executed on different platforms
+ </li>
+ <li>
+ ability to handle many requests simultaneously
+ </li>
+</ul>
+<p>
+ To achieve this, many different types of tests are implemented and executed.&nbsp;Each test type has a specific
+ objective and support technique.&nbsp;Each technique focuses on testing one or more characteristics or attributes of
+ the target-of-test.
+</p>
+<p>
+ The following sections list the types of test based on the most obvious <strong>quality dimensions</strong> they
+ address.
+</p>
+<h3>
+ Quality Dimension: Functionality
+</h3>
+<h4>
+ Types of Test
+</h4>
+<p>
+ <strong>Function test:</strong>&nbsp;Tests focused on validating the target-of-test functions as intended, providing
+ the required services, methods, or use cases. This test is implemented and executed against different targets-of-test,
+ including units, integrated units, applications, and systems.
+</p>
+<p>
+ <strong>Security test:</strong>&nbsp;Tests focused on ensuring the target-of-test data (or systems) are accessible only
+ to those actors for which they are intended. This test is implemented and executed on various targets-of-test.
+</p>
+<p>
+ <strong>Volume test:</strong>&nbsp;Tests focused on verifying the target-of-test's ability to handle large amounts of
+ data, either as input and output or resident within the database.&nbsp;Volume testing includes test strategies such as
+ creating queries that would return the entire contents of the database, or that would have so many restrictions that no
+ data is returned, or where the data entry has the maximum amount of data for each field.
+</p>
+<h3>
+ Quality Dimension:&nbsp;Usability
+</h3>
+<h4>
+ Types of Test
+</h4>
+<p>
+ <strong>Usability test:</strong>&nbsp;Tests that focus on:
+</p>
+<ul>
+ <li>
+ human factors
+ </li>
+ <li>
+ esthetics
+ </li>
+ <li>
+ consistency in the user interface
+ </li>
+ <li>
+ online and context-sensitive help
+ </li>
+ <li>
+ wizards and agents
+ </li>
+ <li>
+ user documentation
+ </li>
+ <li>
+ training materials
+ </li>
+</ul>
+<p>
+ <strong>Integrity test:</strong>&nbsp;Tests that focus on assessing the target-of-test's robustness (resistance to
+ failure), and technical compliance to language, syntax, and resource usage.&nbsp;This test is implemented and executed
+ against different targets-of-tests, including units and integrated units.
+</p>
+<p>
+ <strong>Structure test</strong>: Tests that focus on assessing the target-of-test's adherence to its design and
+ formation.&nbsp;Typically, this test is done for Web-enabled applications ensuring that all links are connected,
+ appropriate content is displayed, and no content is orphaned.
+</p>
+<h3>
+ Quality Dimension: Reliability
+</h3>
+<h4>
+ Types of Test
+</h4>
+<p>
+ <strong>Stress test:</strong>&nbsp; A type of reliability test that focuses on evaluating how the system responds under
+ abnormal conditions.&nbsp;Stresses on the system could include extreme workloads, insufficient memory, unavailable
+ services and hardware, or limited shared resources.&nbsp;These tests are often performed to gain a better understanding
+ of how and in what areas the system will break, so that contingency plans and upgrade maintenance can be planned and
+ budgeted for well in advance.
+</p>
+<p>
+ <strong>Benchmark test:</strong>&nbsp; A type of performance test that compares the performance of a new or unknown
+ target-of-test to a known reference-workload and system.
+</p>
+<p>
+ <strong>Contention test:</strong>&nbsp; Tests focused on validating the target-of-test's ability to acceptably handle
+ multiple actor demands on the same resource (data records, memory, and so on).
+</p>
+<h3>
+ Quality Dimension: Performance
+</h3>
+<h4>
+ Types of Test
+</h4>
+<p>
+ <strong>Load test:</strong>&nbsp; A type of performance test used to validate and assess acceptability of the
+ operational limits of a system under varying workloads while the system-under-test remains constant.&nbsp;In some
+ variants, the workload remains constant and the configuration of the system-under-test is varied.&nbsp; Measurements
+ are usually taken based on the workload throughout and in-line transaction response time.&nbsp;The variations in
+ workload usually include emulation of average and peak workloads that occur within normal operational tolerances.
+</p>
+<p>
+ <strong>Performance profile:</strong> A test in which the target-of-test's timing profile is monitored, including
+ execution flow, data access, function and system calls to identify and address both performance bottlenecks and
+ inefficient processes.
+</p>
+<p>
+ <strong>Configuration test:</strong>&nbsp; Tests focused on ensuring the target-of-test functions as intended on
+ different hardware and software configurations.&nbsp;This test might also be implemented as a system performance test.
+</p>
+<h3>
+ Quality Dimension: Supportability
+</h3>
+<h4>
+ Types of Test
+</h4>
+<p>
+ <strong>Installation test:</strong>&nbsp; Tests focused on ensuring the target-of-test installs as intended on
+ different hardware and software configurations, and under different conditions (such as insufficient disk space or
+ power interruptions).&nbsp;This test is implemented and executed against applications and systems.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/use_case.xmi b/praclib/temp/core.tech.common.base/guidances/concepts/use_case.xmi
new file mode 100644
index 0000000..77b30dd
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/use_case.xmi
@@ -0,0 +1,787 @@
+<?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="-BQLZ5GRUNrMdU6XeZAfe9Q"
+ name="use_case,_KudM0NcJEdqz_d2XWoVt6Q" guid="-BQLZ5GRUNrMdU6XeZAfe9Q" changeDate="2008-01-04T15:23:18.580-0800"
+ version="7.2.0">
+ <mainDescription><h3>
+ <a id="Definitions" name="Definitions">Definitions</a>
+</h3>
+<h4>
+ Use Case
+</h4>
+<p>
+ A use case instance defines a sequence of actions performed by the system that yields an observable result of value to
+ a particular actor. There are several key words in this definition:
+</p>
+<ul>
+ <li>
+ <b>"use case instance"</b> The sequence referred to in the definition is actually a specific flow of events through
+ the system, or an instance. Many flows of events are possible, and many may be very similar. To make a use-case
+ understandable, you should group similar flows of events into one use case. Therefore, identifying and describing a
+ use case really means identifying and describing a group of related flows of events.
+ </li>
+ <li>
+ <strong>"actions"</strong> An action is a computational or algorithmic procedure. It is invoked either when the
+ actor provides a signal to the system or when the system gets a time event. An action may imply signal
+ transmissions to either the invoking actor or other actors. An action is atomic, which means it is performed either
+ entirely or not at all.
+ </li>
+ <li>
+ <b>"performed by the system"</b> This means that the system provides the use case. An actor communicates with a
+ use-case instance of the system.
+ </li>
+ <li>
+ <b>"an observable result of value"</b> You can put a value on a successfully performed use case. A use case should
+ make sure that an actor can perform a task that has an identifiable value. This is very important in determining
+ the correct level or granularity for a use case. <em>Correct level</em> refers to achieving use cases that are not
+ too small.&nbsp;&nbsp;
+ </li>
+ <li>
+ <b>"a&nbsp;particular actor"</b> The actor is key to finding the correct use case, especially because the actor
+ helps you avoid use cases that are too large. As an example, consider a visual modeling tool. There are really two
+ actors&nbsp;in this application: a developer, who develops systems using the tool as support; and a system
+ administrator, who manages the tool. Each of these actors has his own demands on the system, and will therefore
+ require his own set of use cases.
+ </li>
+</ul>
+<p>
+ The functionality of a system is defined by different use cases, each of which represents a specific goal (observable
+ result of value) for a particular actor. The description of a use case defines what happens in the system when the use
+ case is performed.
+</p>
+<p class="picturecenter" align="center">
+ <img height="173" alt="Diagram described in caption." src="./resources/im_uc.gif" width="325" />
+</p>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p class="picturetext">
+ Figure 1: ATM use case example.
+ </p>
+ </blockquote>
+ </blockquote>
+ </blockquote>
+</blockquote>
+<p>
+ In an automated teller machine the client can, for instance, withdraw money from an account, transfer money to an
+ account, or check the balance of an account. These correspond to specific goals that the actor has in using the system.
+</p>
+<p>
+ Each use case has a task of its own to perform. The collected use cases constitute all the possible ways of using the
+ system. You should be able to&nbsp;determine the goal&nbsp;of a use-case task simply by observing its name.&nbsp;&nbsp;
+</p>
+<h4>
+ <a id="A Use-Case has Many Possible Instances" name="A Use-Case has Many Possible Instances">Use-Case</a>
+ Instance&nbsp;
+</h4>
+<p>
+ A use-case can follow an almost unlimited, but enumerable, number of paths. These paths represent the choices open to
+ the use-case in the description of its flow of events. The path chosen depends on events. Types of events include:
+</p>
+<ul>
+ <li>
+ <strong>Input from an actor&nbsp;</strong>
+ </li>
+</ul>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p class="exampleheading">
+ <strong>Example</strong>
+ </p>
+ <p class="example">
+ For example, an actor can decide, from several options, what to do next. In the use case Recycle Items in the
+ Recycling-Machine System the Customer always has two options: insert another deposit item or get the
+ receipt&nbsp;for returned items.
+ </p>
+</blockquote>
+<ul>
+ <li>
+ <strong>A check of values or types of an internal object or attribute</strong>
+ </li>
+</ul>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p class="exampleheading">
+ <strong>Example</strong>
+ </p>
+ <p class="example">
+ For example, the flow of events may differ if a value is greater or less than a certain value.&nbsp;In the use case
+ Withdraw Money in an automated teller machine system, the flow of events will differ if the Client asks for more
+ money than he has in his account. In that situation, the use-case instance follows a&nbsp;different path.
+ </p>
+</blockquote>
+<h4>
+ Scenario
+</h4>
+<p>
+ A scenario is a specific sequence of actions that illustrates a behavior.&nbsp; A scenario may be used to illustrate a
+ use-case instance and to specify test cases.
+</p>
+<h4>
+ Use-Case Realization
+</h4>
+<p>
+ A use case describes what happens in the system when an actor interacts with the system. The use case does not define
+ how the system&nbsp;performs its tasks, in terms of collaborating objects. This is left for the use-case realizations
+ to show.
+</p>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p class="exampleheading">
+ <strong>Example</strong>
+ </p>
+ <p class="example">
+ In the telephone example, the use case would indicate (among other things) that the system issues a signal when the
+ actor lifts the receiver,&nbsp; and that the system then receives digits, finds the receiving party, rings his
+ telephone, connects the call, transmits speech, and so on.
+ </p>
+</blockquote>
+<p>
+ In a running&nbsp;system, an instance of a use case does not correspond to any particular object in the implementation
+ model (for example, an instance of a class in the code). Instead, it corresponds to a specific flow of events that is
+ invoked by an actor and&nbsp;performed as a sequence of events among a set of objects. In other words, instances of use
+ cases correspond to communicating instances of implemented objects. We call this the <strong>realization of the use
+ case</strong>. Often, the same objects participate in realizations of more than one use case. For example, both the use
+ cases Deposit and Withdrawal in a banking system may use a certain account object in their realization. This does not
+ mean that the two use cases communicate, but only that they use the same object in their realization.
+</p>
+<p>
+ You can&nbsp;think of&nbsp;a flow of events as consisting of several subflows that,&nbsp;taken together, yield the
+ total flow of events. You can reuse the description of a subflow in other flows of events for other use cases. Subflows
+ in the description of one use case's flow of events may be common to those of other use cases. In the design you should
+ have the same objects perform this common behavior for all the relevant use cases. That is, only one set of objects
+ should perform this behavior no matter which use case is running.
+</p>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p class="exampleheading">
+ <strong>Example</strong>
+ </p>
+ <p class="example">
+ In an automated teller machine system, the initial subflow is the same in the flow of events of the use cases
+ Withdraw Money and Check Balance. The flow of events of both use cases start by checking the identity of the card
+ and the client's personal access code.
+ </p>
+</blockquote>
+<h3>
+ Properties of Use Cases
+</h3>
+<h4>
+ <a id="Name" name="Name">Name</a>
+</h4>
+<p>
+ Each use case should have a name that indicates what is achieved by its interaction with the actors. The name may have
+ to be several words to be understood. Note: No two use cases can have the same name.
+</p>
+<blockquote>
+ <p class="exampleheading">
+ <strong>Example</strong>
+ </p>
+ <p class="example">
+ These are examples of variations of the name for the use case Recycle Items in the Recycling Machine example:
+ </p>
+ <ul>
+ <li>
+ Return Deposit Items
+ </li>
+ <li>
+ Deposit Items
+ </li>
+ </ul>
+</blockquote>
+<h4>
+ <a id="Brief Description" name="Brief Description">Brief Description</a>
+</h4>
+<p>
+ The brief description of the use case should reflect its purpose. As you write the description, refer to the actors
+ involved in the use case and the glossary.&nbsp;If you need to, define new concepts.
+</p>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p class="exampleheading">
+ <strong>Example</strong>
+ </p>
+ <p class="example">
+ Following are sample brief descriptions of the use cases Recycle Items and Add New Bottle Type in the
+ Recycling-Machine system.
+ </p>
+ <p class="example">
+ <b>Recycle Items</b>: The user uses this machine to automatically have all the return items (bottles, cans, and
+ crates) counted, and receives a receipt. The receipt is to be cashed at a cash register (another machine).
+ </p>
+ <p class="example">
+ <b>Add New Bottle Type</b>: The manager can add options for the user to return new kinds of bottles can be added to
+ the machine by starting it in <em>learning</em> mode and inserting 5 samples, just&nbsp;as when the customers
+ return items. The machine can measure the bottles and learns to identify them. The manager specifies the refund
+ value for the new bottle type.
+ </p>
+</blockquote>
+<h4>
+ Flow of Events
+</h4>
+<h5>
+ <a id="XE_use_case__flow_of_events" name="XE_use_case__flow_of_events"></a><a id="XE_flow_of_events__guidelines_for"
+ name="XE_flow_of_events__guidelines_for"></a><a id="Flow of Events - Contents" name="Flow of Events - Contents">Flow of
+ Events - Contents</a>
+</h5>
+<p>
+ The f<b>low of events</b> of a use case contains the most important information derived from use-case modeling work. It
+ should describe the use case's flow of events clearly enough for an outsider to easily understand. Remember, the flow
+ of events should represent <em>what</em> the system does, not <em>how</em> the system is design to perform the required
+ behavior.
+</p>
+<p>
+ Follow these guidelines for the contents of the flow of events:
+</p>
+<ul>
+ <li>
+ Describe how the use case starts and ends.
+ </li>
+ <li>
+ Describe what data is exchanged between the actor and the use case.
+ </li>
+ <li>
+ Do not describe the details of the user interface, unless it is necessary to understand the behavior of the system.
+ For example, it is often good to use a limited set of web-specific terminology when it is known beforehand that the
+ application is going to be web-based. Otherwise, your run the risk that the use-case text is being perceived as too
+ abstract. Words to include in your terminology could be "navigate", "browse", "hyperlink" "page", "submit", and
+ "browser". However, it is not advisable to include references to "frames" or "web pages" in such a way that you are
+ making assumptions about the boundaries between them; this is a critical design decision.&nbsp;
+ </li>
+ <li>
+ Describe the flow of events, not only the functionality. To enforce this, start every action with "When the actor
+ ... ".
+ </li>
+ <li>
+ Describe only the events that belong to the use case, and not what happens in other use cases or outside of the
+ system.
+ </li>
+ <li>
+ Avoid vague terminology.
+ </li>
+ <li>
+ Detail the flow of events. Specify what happens when, for each action. Remember this text will be used to identify
+ test cases.
+ </li>
+</ul>
+<p>
+ If you have used certain terms in other use cases, be sure to use the exact same terms in this use case, and
+ that&nbsp;the meaning of the terms is consistent. To manage common terms, put them in a glossary.
+</p>
+<h5>
+ <a id="Flow of Events - Structure" name="Flow of Events - Structure">Flow of Events - Structure</a>
+</h5>
+<p>
+ The two main parts of the flow of events are <b>basic flow of events</b> and <a
+ id="XE_flow_of_events__alternative_flow" name="XE_flow_of_events__alternative_flow"></a><b>alternative flows of
+ events</b>. The basic flow of events should cover what "normally" happens when the use case is performed. The
+ alternative flows of events cover behavior of optional or exceptional character in relation to the normal behavior, and
+ also variations of the normal behavior. You can think of the alternative flows of events as detours from the basic flow
+ of events, some of which will return to the basic flow of events and some of which will end the execution of the use
+ case.
+</p>
+<p align="center">
+ <img height="212" alt="Diagram described in caption." src="./resources/ucstrct.gif" width="231" />
+</p>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p class="picturetext">
+ Figure 2: Typical structure of a use case flow of events
+ </p>
+ </blockquote>
+ </blockquote>
+</blockquote>
+<p class="picturetext">
+ The straight arrow in Figure 2 represents the basic flow of events, and the curves represent alternative paths in
+ relation to the normal. Some alternative paths return to the basic flow of events, whereas,&nbsp;others end the use
+ case.
+</p>
+<p>
+ Both the basic and alternative flows should be further structured into steps or subflows. In doing this, your main goal
+ should be readability of the text (see the <em>Flow of Events - Style</em> section, which follows). A&nbsp;guideline is
+ that a subflow should be a segment of behavior within the use case that has a clear purpose, and is "atomic" in the
+ sense that you do either all or none of the actions described. You may need to have several levels of subflows,
+ but&nbsp;avoid that if you can,&nbsp;since it makes the text more complex and harder to understand.
+</p>
+<p>
+ The nature of this type of written text, structured into consecutive subsections,&nbsp;implies to the reader that there
+ is a sequence between the subflows. To avoid misunderstandings, you should always point out whether the order of the
+ subflows is fixed or not. Considerations of this kind are often related to factors such as:
+</p>
+<ul>
+ <li>
+ <strong>Business rules</strong>. For example, the user has to be authorized before the system can make certain data
+ available.
+ </li>
+ <li>
+ <strong>User-interface design.</strong> For example, the system should not enforce a certain sequence of behavior
+ that may be intuitive to some but not to other users.
+ </li>
+</ul>
+<p>
+ To clarify where an alternative flow of events fits in the structure, you need to describe the following for each
+ detour to the basic flow of events:
+</p>
+<ul>
+ <li>
+ Where the alternative flow can be inserted in the basic flow of events.
+ </li>
+ <li>
+ The condition that needs to be fulfilled for the alternative behavior to start.
+ </li>
+ <li>
+ How and where the basic flow of events is resumed, or how the use case ends.
+ </li>
+</ul>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p class="exampleheading">
+ <strong>Example</strong>
+ </p>
+ <p class="example">
+ This is an alternative subflow in the use case Return Items in the Recycling-Machine System.
+ </p>
+ <p class="example">
+ 2.1. Bottle Stuck
+ </p>
+ <p class="example">
+ If in section 1.5, Insert Deposit Items, a bottle gets stuck in the gate, the sensors around the gate and the
+ measuring gate will detect this problem. The conveyer belt is stopped and the machine issues an alarm to call for
+ the operator. The machine will wait for the operator to indicate that the problem has been fixed. The machine then
+ continues in section 1.9 of the basic flow.
+ </p>
+</blockquote>
+<p dir="ltr">
+ In the example above, the alternative flow of events is inserted at a specific location in the basic flow of events.
+ There are also alternative flow of events that can be inserted at more than one location, some can even be inserted at
+ any location in the basic flow of events.
+</p>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p class="exampleheading">
+ <strong>Example</strong>
+ </p>
+ <p class="example">
+ This is an alternative subflow in the use case Return Items in the Recycling-Machine System.
+ </p>
+ <p>
+ 2.2. Front Panel is Removed
+ </p>
+ <p class="example">
+ If somebody removes the front panel to the Recycling machine, the can compression is deactivated. It will not be
+ possible to start the can compression with the front panel off. The removal will also activate an
+ alarm&nbsp;for&nbsp;operator attention. When the front panel is closed again, the machine resumes operation from
+ the point where it stopped in&nbsp;the basic flow of events.
+ </p>
+</blockquote>
+<p>
+ It might be tempting, if the alternative flow of events is very simple, to just describe it in the basic flow of events
+ section (using some informal "if-then-else" construct). This should be avoided. Too many alternatives will make the
+ normal behavior difficult to see. Also, including alternative paths in the basic flow of events section will make the
+ text more pseudo-code like and harder to read.
+</p>
+<p>
+ In general, extracting parts of the flow of events and describing these parts separately, can increase the readability
+ of the basic flow of events and improve the structure of the use case and the use-case model. You can model extracted
+ parts as the situation requires:
+</p>
+<ul>
+ <li>
+ An <strong>alternative</strong> flow of events within the base use case if it is a simple variant, option, or
+ exception to the basic flow of events.
+ </li>
+ <li>
+ As an <strong>explicit</strong> inclusion in the base use case, if it is something that you wish to encapsulate so
+ that it can be reused by other use cases.
+ </li>
+ <li>
+ As an <strong>implicit</strong> inclusion in the base use case, if the basic flow of events of the base use case is
+ complete, that is, has a defined beginning and end. The nature of the extending flow should be such that you prefer
+ to conceal it in the description of the base use case to render it less complex.
+ </li>
+ <li>
+ A <strong>subflow</strong> in the basic flow of events, possibly as another option, if none of the above
+ alternatives applies. For example, in a Maintain Employee Information use case, there may be separate subflows for
+ adding, deleting and modifying employee information.
+ </li>
+</ul>
+<h5>
+ <a id="Flow of Events - Style" name="Flow of Events - Style">Flow of Events - Style</a>
+</h5>
+<p>
+ You can describe use cases in many styles. As an example we show the basic flow of events of the use case Administer
+ Order described in three different styles, varying primarily in how formal they are.
+</p>
+<p>
+ The first style, shown in Example 1, is the recommended one, because it is easy to understand, and the order in which
+ things happen is clearly evident. The text is divided into numbered and named subsections. Numbers are there to make it
+ easy to refer to a subsection. Names of subsections will let the reader get a quick overview of the flow of events by
+ browsing through the text reading only the headers.
+</p>
+<p>
+ In Example 2, the description of the flow of events fails to clarify the order in which things happen. If you write in
+ this style, you and others might miss important things that concern the system.
+</p>
+<p>
+ Example 3 below shows a yet another style, which can be useful if you find it difficult to express the sequence of
+ events clearly. This pseudo-code style is more precise, but the text is hard to read and absorb for a non-technical
+ person, especially if you want to grasp the flow of events quickly.
+</p>
+<p>
+ Finally,&nbsp;Example 4&nbsp;provides an example of a complete description of a use case flow of events.&nbsp;
+</p>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p>
+ <a id="Example 1:" name="Example 1:"><strong>Example 1:</strong></a> <strong>Recommended style for describing a use
+ case</strong>
+ </p>
+ <p>
+ In this style, the text is easy to read and the flow of events is easy to follow.
+ </p>
+</blockquote>
+<div align="center">
+ <table
+ style="BORDER-RIGHT: rgb(128,128,128) 1px solid; BORDER-TOP: rgb(128,128,128) 1px solid; BORDER-LEFT: rgb(128,128,128) 1px solid; BORDER-BOTTOM: rgb(128,128,128) 1px solid"
+ cellspacing="0" bordercolordark="#808080" cellpadding="4" width="85%" bordercolorlight="#808080" border="1">
+ <tbody>
+ <tr>
+ <td width="100%">
+ <b>1.1. Start of Use Case</b> 
+ <p>
+ This use case starts when the actor Operator tells the system to create a measurement order. The
+ system will then retrieve all Network Element actors, their measurement objects and corresponding
+ measurement functions that are available to this particular Operator. Available Network Elements
+ are those that are in operation, and that the Operator has the authority to access. The
+ availability of measurement functions depends on what has been set up for a particular type of
+ measurement object.
+ </p>
+ <p>
+ <b>1.2. Configure Measurement Order</b>
+ </p>
+ <p>
+ The system allows the actor Operator to select which Network Elements to measure and then shows
+ which measurement objects are available for the selected Network Elements. The system allows the
+ Operator to select from the measurement objects, and then select which measurement functions to set
+ up for each measurement object.
+ </p>
+ <p>
+ The system allows the Operator to enter a textual comment on the measurement order.
+ </p>
+ <p>
+ The Operator tells the system to complete the measurement order. The system will respond by
+ generating a unique name for the measurement order and setting up default values for when, how
+ often, and for how long the measurement should be made. The default values are unique to each
+ Operator. The system then allows the Operator to edit these default values.
+ </p>
+ <p>
+ <b>1.3. Initialize Order</b>
+ </p>
+ <p>
+ The Operator tells the system to initialize the measurement order. The system will then record the
+ identity of the creating Operator, the date of creation, and the "Scheduled" status of the
+ measurement order.
+ </p>
+ <p>
+ <b>1.4. Use Case Ends</b>
+ </p>
+ <p>
+ The system confirms initialization of the measurement order to the Operator, and the measurement
+ order is made available for other actors to view.
+ </p>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div>
+<div align="center">
+ <br />
+</div>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p>
+ <a id="Example 2:" name="Example 2:"><strong>Example 2:</strong></a> <strong>Alternative way of describing a use
+ case</strong>
+ </p>
+ <p>
+ This style is readable, but there is no clear flow of events.
+ </p>
+</blockquote>
+<div align="center">
+ <table
+ style="BORDER-RIGHT: rgb(128,128,128) 1px solid; BORDER-TOP: rgb(128,128,128) 1px solid; BORDER-LEFT: rgb(128,128,128) 1px solid; BORDER-BOTTOM: rgb(128,128,128) 1px solid"
+ cellspacing="0" bordercolordark="#808080" cellpadding="4" width="85%" bordercolorlight="#808080" border="1">
+ <tbody>
+ <tr>
+ <td width="100%">
+ Orderers can create Orders to collect measurement data from the Network Elements. 
+ <p>
+ The system will assign the Order a unique name as well as default values that indicate the length
+ and time of the measurement and also how often it is to be repeated. The Orderer will be able to
+ edit these values.
+ </p>
+ <p>
+ The Orderer must further specify which measurement function, network element and measurements
+ objects are applicable. The Orderer can also add a personal comment to the order.
+ </p>
+ <p>
+ When the necessary information had been defined, a new Order is created and initialized with the
+ defined attributes, the name of the creator, and the date of creation. The status of the order will
+ be set to "scheduled". (Possible values for the status are: Scheduled, Executing, Completed,
+ Canceled, and Erroneous.)
+ </p>
+ <p>
+ The user interface is then notified that a new Order has been created and receives a reference to
+ the new Order so that it can be displayed.
+ </p>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p>
+ <a id="Example 3:" name="Example 3:"><strong>Example 3:</strong></a> <strong>Another way of describing a use
+ case</strong>
+ </p>
+ <p>
+ Here the writer has chosen a formal style using pseudocode. This style makes it hard to quickly grasp the process
+ steps, but can be useful if the flow of events is difficult to capture precisely.
+ </p>
+</blockquote>
+<div align="center">
+ <table
+ style="BORDER-RIGHT: rgb(128,128,128) 1px solid; BORDER-TOP: rgb(128,128,128) 1px solid; BORDER-LEFT: rgb(128,128,128) 1px solid; BORDER-BOTTOM: rgb(128,128,128) 1px solid"
+ cellspacing="0" bordercolordark="#808080" cellpadding="4" width="50%" bordercolorlight="#808080" border="1">
+ <tbody>
+ <tr>
+ <td width="100%">
+<pre>
+<font size="2">
+<small>
+'Administrate order' (User identity) 
+REPEAT
+&lt;='Show administer order menu'
+IF (=&gt; 'Creating an Order' (Measurement function, network element, measurement object)) THEN
+The system finds a unique name, default values for when and how long the measurement should be executed. 
+&lt;= 'Show order' (Default attributes)
+REPEAT
+IF (=&gt; 'Edit order' (Attribute to change, New value of attribute)) THEN
+&lt;= 'Update screen' (New attributes)
+ELSIF (=&gt; 'Save order' (Order identity, Attributes)) THEN
+The order is created and initialized in the system with
+the defined attributes, the name of the creator,
+date of creation and the status 'scheduled'.
+&lt;= 'New order created' (The order)
+ENDIF
+UNTIL (=&gt; 'Quit') 
+ENDIF 
+UNTIL 'Quit administer order'</small>
+</font>
+</pre>
+ </td>
+ </tr>
+ </tbody>
+ </table>
+</div>
+<h5>
+ <a id="Example 3:" name="Example 3:">Example 4:</a>&nbsp;Complete description fo the flow of events&nbsp;
+</h5>
+<p>
+ The complete description of the flow of events of the use case Administer Order, including its alternative flows, could
+ look like the example that follows:
+</p>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p>
+ <b>1.&nbsp;BASIC FLOW&nbsp;OF EVENTS</b>&nbsp;
+ </p>
+ <p>
+ <b>1.1. Start use case</b>
+ </p>
+ <p>
+ This use case starts when the actor Operator tells the system to create a measurement order. The system will then
+ retrieve all Network Element actors, their measurement objects and corresponding measurement functions that are
+ available to this particular Operator. Available Network Elements are those that are in operation, and that the
+ Operator has the authority to access. The availability of measurement functions depends on what has been set up for
+ a particular type of measurement object.
+ </p>
+ <p>
+ <b>1.2. Configure measurement order</b>
+ </p>
+ <p>
+ The system allows the actor Operator to select which Network Elements to measure and then shows which measurement
+ objects are available for the selected Network Elements. The system allows the Operator to select from these
+ measurement objects, and then select which measurement functions to set up for each measurement object.
+ </p>
+ <p>
+ The system allows the Operator to enter a textual comment on the measurement order.
+ </p>
+ <p>
+ The Operator tells the system to complete the measurement order. The system will respond by generating a unique
+ name for the measurement order and setting up default values for when, how often, and for how long the measurement
+ should be made. The default values are unique to each Operator. The system then allows the Operator to edit these
+ default values.
+ </p>
+ <p>
+ <b>1.3. Initialize order</b>
+ </p>
+ <p>
+ The Operator tells the system to initialize the measurement order. The system will then record the identity of the
+ creating Operator, the date of creation, and the "Scheduled" status of the measurement order.
+ </p>
+ <p>
+ <b>1.4. End use case</b>
+ </p>
+ <p>
+ The system confirms initialization of the measurement order to the Operator, and the measurement order is made
+ available for other actors to view.
+ </p>
+ <p>
+ <b>2.&nbsp;ALTERNATIVE FLOW OF EVENTS</b>&nbsp;
+ </p>
+ <p>
+ <b>2.1. No network elements available</b>
+ </p>
+ <p>
+ If in 1.1, Start use case, it turns out that no Network Elements are available to measure for this Operator, the
+ system will inform the Operator. The use case then ends.
+ </p>
+ <p>
+ <b>2.2. No measurement functions available</b>
+ </p>
+ <p>
+ If in 1.2, Configure measurement order, no measurement functions are available for the selected Network Elements,
+ the system will inform the Operator and allow the Operator to select other Network elements.
+ </p>
+ <p>
+ <b>2.3. Cancel measurement order</b>
+ </p>
+ <p>
+ The system will allow the Operator to cancel all actions at any point during the execution of the use case. The
+ system will then return to the state it was in before the use case was started, and end the use case.
+ </p>
+</blockquote>
+<h4>
+ <a id="XE_use_case__flow_of_events" name="XE_use_case__flow_of_events"></a><a id="XE_flow_of_events__guidelines_for"
+ name="XE_flow_of_events__guidelines_for"></a><a id="Special Requirements" name="Special Requirements">Special
+ Requirements</a>
+</h4>
+<p>
+ In the Special Requirements of a use case, you describe all the requirements on the use case that are not covered by
+ the flow of events. These are non-functional requirements that will influence the design model. See also the discussion
+ on non-functional requirements in <a class="elementLinkWithType"
+ href="./../../../core.tech.slot.base/guidances/concepts/requirements_8006414F.html"
+ guid="_0Wh-sMlgEdmt3adZL5Dmdw">Concept: Requirements</a>. You could organize these requirements in categories such as
+ Usability, Reliability, Performance, and Substitutability, but normally there are so few of them that such grouping is
+ not particularly value-adding.
+</p>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <h5>
+ Example
+ </h5>
+ <p class="example">
+ In the Recycling-Machine System, a special requirement of the Return Deposit Items use case could be:
+ </p>
+ <blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p class="example">
+ The machine has to be able to recognize deposit items with a reliability of more than 95 percent.
+ </p>
+ </blockquote>
+</blockquote>
+<h4>
+ <a id="XE_postcondition__guidelines_for" name="XE_postcondition__guidelines_for"></a><a
+ id="XE_precondition__guidelines_for" name="XE_precondition__guidelines_for"></a><a
+ id="preconditions and Postconditions" name="preconditions and Postconditions">Preconditions and Post-conditions</a>
+</h4>
+<p>
+ A <strong>precondition</strong> is the state of the system and its surroundings that is required before the use case
+ can be started.&nbsp;Post-Conditions are&nbsp;the states the system can be in after the use case has ended. It can
+ be&nbsp;helpful to use the&nbsp;concepts of <b>precondition</b> and <b>post-condition</b> to clarify how the flow of
+ events starts and ends. However, only use them only if the audience for the description of the use case agrees that it
+ is helpful.
+</p>
+<p align="center">
+ <img height="278" alt="Diagram described in caption." src="./resources/ucprepst.gif" width="344" />
+</p><br class="picturetext" />
+<br />
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p>
+ Figure 3: Illustration of preconditions and resulting post-conditions
+ </p>
+ </blockquote>
+ </blockquote>
+</blockquote>
+<p>
+ Consider the following when specifying preconditions and post-conditions:
+</p>
+<ul>
+ <li>
+ The states described by pre- or post-conditions should be states that the user can observe. "The user has logged on
+ to the system" or "The user has opened the document" are examples of observable states.
+ </li>
+ <li>
+ A precondition is a constraint on when a use case can start. It is not the event that starts the use case.
+ </li>
+ <li>
+ A precondition for a use case is not a precondition for only one subflow, although you can define preconditions and
+ post-conditions at the subflow level.
+ </li>
+ <li>
+ A post-condition for a use case should be true regardless of which alternative flows were executed; it should not
+ be true only for the main flow. If something could fail, you would cover that in the post-condition by saying "The
+ action is completed, or if something failed, the action is not performed", rather than just "The action is
+ completed".
+ </li>
+ <li>
+ When you use post-conditions together with <em>extend</em> relationships, you should take care that the extending
+ use case does not introduce a subflow that violates the post-condition in the base use case.
+ </li>
+ <li>
+ Post-conditions can be a powerful tool for describing use cases. You first define what the use case is supposed to
+ achieve, which is the post-condition. You can then describe the necessary flow of events, or how to reach this
+ condition.
+ </li>
+</ul>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p class="exampleheading">
+ Examples
+ </p>
+ <p class="example">
+ <strong>A precondition for the use case Cash Withdrawal in the ATM machine:</strong> The customer has a personally
+ issued card that fits in the card reader, has been issued a PIN number, and is registered with the banking system.
+ </p>
+ <p class="example">
+ <strong>A pos-tcondition for the use case Cash Withdrawal in the ATM machine:</strong> At the end of the use case,
+ all account and transaction logs are balanced, communication with the banking system is reinitialized and the card
+ is returned to the customer.
+ </p>
+</blockquote>
+<h4>
+ <a id="Extension Points" name="Extension Points">Extension Points</a>
+</h4>
+<p>
+ An <b>extension point</b> opens up the use case to the possibility of an extension. It has a name and a list of
+ references to one or more locations within the flow of events of the use case. An extension point may reference a
+ single location between two behavior steps within the use case. It may also reference a set of discrete locations.
+</p>
+<p>
+ Using&nbsp;named extension points will help you separate the specification of the behavior of the extending use case
+ from the internal details of the base use case. The base use case can be modified or rearranged, as long as the names
+ of the extension points remain the same, it will not affect the extending use case. At the same time, you are not
+ complicating the text describing the flow of events of the base use case with details of where behavior might be
+ extended into it.
+</p>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p class="exampleheading">
+ <strong>Example</strong>
+ </p>
+ <p class="example">
+ In a phone system, the use case Place Call can be extended by the abstract use case Show Caller Identity. This is
+ an optional service, often referred to as "Caller ID", that may or may not have been requested by the receiving
+ party. A description of the extension point in the use case Place Call could look like the following:
+ </p>
+ <p class="example">
+ <b>Name</b>: Show Identity
+ </p>
+ <p class="example">
+ <b>Location</b>: After section 1.9 Ring Receiving Party's Telephone.
+ </p>
+</blockquote></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/use_case_model.xmi b/praclib/temp/core.tech.common.base/guidances/concepts/use_case_model.xmi
new file mode 100644
index 0000000..f7ebb7d
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/use_case_model.xmi
@@ -0,0 +1,172 @@
+<?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="-yEWkrWZ3VUcjZPhq6bvScg"
+ name="new_concept,_2jyfUAhVEduRe8TeoBmuGg" guid="-yEWkrWZ3VUcjZPhq6bvScg" changeDate="2008-01-03T16:44:34.070-0800"
+ version="1.0.0">
+ <mainDescription><h3>
+ Explanation
+</h3>
+<p>
+ A use-case model is a model of how different types of users interact with the system to solve a problem.&nbsp; As such,
+ it describes the goals of the users, the interactions between the users and the system, and the required behavior of
+ the system in satisfying these goals.
+</p>
+<p>
+ A use-case model consists of a number of model elements.&nbsp; The most important model elements are: use cases, actors
+ and the relationships between them.
+</p>
+<p>
+ A use-case diagram is used to graphically depict a subset of the model to simplify communications.&nbsp; There will
+ typically be several use-case diagrams associated with a given model, each showing a subset of the model elements
+ relevant for a particular purpose.&nbsp; The same model element may be shown on several use-case diagrams, but each
+ instance must be consistent.&nbsp; If tools are used to maintain the use-case model, this consistency constraint is
+ automated so that any changes to the model element (changing the name for example) will be automatically reflected on
+ every use-case diagram that shows that element.
+</p>
+<p>
+ The use-case model may contain packages that are used to structure the model to simplify analysis, communications,
+ navigation, development, maintenance and planning.
+</p>
+<p>
+ Much of the use-case model is in fact textual, with the text captured in the&nbsp;use-case specifications&nbsp;that are
+ associated with each use-case model element.&nbsp;These specifications describe the flow of events of the use case.
+</p>
+<p>
+ The use-case model serves as a unifying thread throughout system development. It is used as the primary specification
+ of the functional requirements for the system, as the basis for analysis and design, as an input to iteration planning,
+ as the basis of defining test cases and as the basis for user documentation&nbsp;&nbsp;
+</p>
+<h3>
+ Basic model elements
+</h3>
+<p>
+ The use-case model contains, as a minimum, the following basic model elements.
+</p>
+<h4>
+ Actor
+</h4>
+<p>
+ A model element representing&nbsp;each actor. Properties include the actors name and brief description. See&nbsp;<a
+ class="elementLinkWithType" href="./../../../core.tech.common.base/guidances/concepts/actor_411726C.html"
+ guid="_zGqO0MDpEduTGJ8i4u8TMw">Concept: Actor</a> for more information.
+</p>
+<h4>
+ Use Case
+</h4>
+<p>
+ A model element representing&nbsp;each use case. Properties include the use case name and use case specification. See
+ <a class="elementLinkWithType" href="./../../../core.tech.common.base/workproducts/use_case_22BE66E2.html"
+ guid="_0VGbUMlgEdmt3adZL5Dmdw">Artifact: Use Case</a> and <a class="elementLinkWithType"
+ href="./../../../core.tech.common.base/guidances/concepts/use_case_BB199D1B.html"
+ guid="_KudM0NcJEdqz_d2XWoVt6Q">Concept: Use Case</a> for more information.
+</p>
+<h4>
+ Associations
+</h4>
+<p>
+ Associations are used to describe the relationships between actors and the use cases they participate in. This
+ relationship is commonly known as a “communicates-association”.
+</p>
+<h3>
+ Advanced model elements
+</h3>
+<p>
+ The use-case model may also contain the following advanced model elements.
+</p>
+<h4>
+ Subject
+</h4>
+<p>
+ A model element that represents the boundary of the system of interest.&nbsp;&nbsp;
+</p>
+<h4>
+ Use-Case Package
+</h4>
+<p>
+ A model element used to structure the use case model to simplify analysis, communications, navigation, and
+ planning.&nbsp; If there are many use cases or actors, you can use use-case packages to further structure the use-case
+ model in much the same manner you use folders or directories to structure the information on your hard-disk.
+</p>
+<p>
+ You can partition a use-case model into use-case packages for several reasons, including:
+</p>
+<ul>
+ <li>
+ To reflect the order, configuration, or delivery units in the finished system thus supporting iteration planning.
+ </li>
+ <li>
+ To support parallel development by dividing the problem into bite-sized pieces.
+ </li>
+ <li>
+ To simplify communication with different stakeholders by creating packages for containing use cases and actors
+ relevant to a particular stakeholder.
+ </li>
+</ul>
+<h4>
+ Generalizations
+</h4>
+<p>
+ A relationship&nbsp;between actors to support re-use of common properties.
+</p>
+<h4>
+ Dependencies
+</h4>
+<p>
+ A number of dependency types between use cases are defined in UML. In particular, &lt;&lt;extend&gt;&gt; and
+ &lt;&lt;include&gt;&gt;.
+</p>
+<p>
+ &lt;&lt;extend&gt;&gt; is used to include optional behavior from an extending use case in an extended use case.
+</p>
+<p>
+ &lt;&lt;include&gt;&gt; is used to include common behavior from an included use case into a base use case in order to
+ support re-use of common behavior.
+</p>
+<p>
+ The latter is the most widely used dependency and is useful for:
+</p>
+<ul>
+ <li>
+ Factoring out behavior from the base use case that is not necessary for the understanding of the primary purpose of
+ the use case to simplify communications.
+ </li>
+ <li>
+ Factoring out behavior that is in common for two or more use cases to maximize re-use, simplify maintenance and
+ ensure consistency.
+ </li>
+</ul>
+<h3>
+ Example Use-Case Diagram
+</h3>
+<p>
+ Figure 1 shows a use-case diagram from an Automated Teller Machine (ATM) use-case model.
+</p>
+<p>
+ &nbsp;<img height="410" alt="Figure 1: ATM Use-Case Diagram" src="./resources/ATMUCdiagram.GIF" width="565" />
+</p>
+<p>
+ Figure 1: ATM Use-Case Diagram
+</p>
+<p>
+ This diagram shows the subject (atm:ATM), four actors (Bank Customer, Bank, Cahier and Maintenance Person), five use
+ cases (Withdraw Cash, Transfer Funds, Deposit Funds, Refill Machine and Validate User), three &lt;&lt;includes&gt;&gt;
+ dependencies, and the associations between the performing actors and the use cases.
+</p>
+<p>
+ The use cases Withdraw Cash, Deposit Funds, and Transfer Funds all need to include how the customer is identified to
+ the system. This behavior can be extracted to a new inclusion use case called Validate User, which the three base use
+ cases &lt;&lt;include&gt;&gt;. The base use cases are independent of the method used for identification, and it is
+ therefore encapsulated in the inclusion use case. From the perspective of the base use cases, it does not matter
+ whether the method for identification is to read a magnetic bank card, or perform a retinal scan. They only depend on
+ the result of Validate Customer.
+</p>
+<p>
+ Note that Figure 1 is only a partial view of the use-case model. The complete use-case model also includes descriptions
+ of each actor, descriptions of each use case, and use-case specifications for each use case.&nbsp; For a more complete
+ example of this use case model see <a class="elementLink"
+ href="./../../../core.tech.common.base/guidances/examples/uc_model_evolve_9A14A952.html"
+ guid="_jAHCkLpeEdyfAY9BXNFkDg">Evolution of the Use-Case Model</a>.<br />
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/concepts/visual_modeling.xmi b/praclib/temp/core.tech.common.base/guidances/concepts/visual_modeling.xmi
new file mode 100644
index 0000000..cb858c1
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/concepts/visual_modeling.xmi
@@ -0,0 +1,153 @@
+<?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="_SB1n8MM1EdmSIPI87WLu3g"
+ name="visual_modeling,_0XY6UMlgEdmt3adZL5Dmdw" guid="_SB1n8MM1EdmSIPI87WLu3g"
+ changeDate="2008-02-14T07:58:00.031-0500" version="1.0.0">
+ <mainDescription><p align="center">
+ <img height="229" alt="visual modelling" src="./resources/visual.gif" width="447" />
+</p>
+<p align="center">
+ Visual modeling raises the level of abstraction
+</p>
+<p>
+ Visual modeling is the use of semantically rich, graphical and textual design notations to capture software designs. A
+ notation, such as UML, allows the level of abstraction to be raised, while maintaining rigorous syntax and semantics.
+ In this way, it improves communication in the design team, as the design is formed and reviewed, allowing the reader to
+ reason about the design, and it provides an unambiguous basis for implementation.
+</p>
+<h3>
+ How visual models help
+</h3>
+<p>
+ A model is a simplified view of a system. It shows the essentials of the system from a particular perspective and hides
+ the nonessential details. Visual models help you:
+</p>
+<ul>
+ <li>
+ Increase understanding of complex systems
+ </li>
+ <li>
+ Explore and compare design alternatives at a low cost
+ </li>
+ <li>
+ Form a foundation for implementation
+ </li>
+ <li>
+ Capture requirements precisely
+ </li>
+ <li>
+ Communicate decisions unambiguously
+ </li>
+</ul>
+<h4>
+ Increase understanding of complex systems
+</h4>
+<p>
+ The importance of models increases as systems become more complex. For example, you can build a doghouse without
+ blueprints. However, as you progress to building houses and then to skyscrapers, your need for blueprints becomes
+ pronounced.
+</p>
+<p>
+ Similarly, a small application built by one person in a few days may be easily understood in its entirety. However, an
+ e&nbsp;-&nbsp;commerce system with tens of thousands of source lines of code (SLOCs) or an air traffic control system
+ with hundreds of thousands of SLOCs can no longer be easily understood by one person. Constructing models allows a
+ developer to focus on the big picture, understand how components interact, and identify fatal flaws.&nbsp;
+</p>
+<p>
+ Among the various types of models are these examples:
+</p>
+<ul>
+ <li>
+ Use cases to specify behavior unambiguously
+ </li>
+ <li>
+ Class diagrams and data model diagrams to capture design
+ </li>
+ <li>
+ State transition diagrams to model dynamic behavior
+ </li>
+</ul>
+<p>
+ Modeling is important because it helps the team visualize, construct, and document the structure and behavior of the
+ system without getting lost in complexity.
+</p>
+<h4>
+ Explore and compare design alternatives at a low cost
+</h4>
+<p>
+ You can create and modify simple models inexpensively to explore design alternatives. Innovative ideas can be captured
+ and reviewed by other developers before investing in costly code development. When coupled with iterative development,
+ visual modeling helps developers assess design changes and communicate these changes to the entire development team.
+</p>
+<h4>
+ Form a foundation for implementation
+</h4>
+<p>
+ Today, many projects employ object-oriented programming languages to build reusable, change-tolerant, and stable
+ systems. To get these benefits, it is even more important to use object technology in design.
+</p>
+<p>
+ The creation of visual models, whether&nbsp;on paper; around a whiteboard; or in a modeling tool,&nbsp;can help a team
+ to gain agreement on key aspects of the system before investing time&nbsp;in proving&nbsp;their ideas&nbsp;with code.
+ Having a shared model of the system promotes collaboration within the team, encouraging everyone to work towards the
+ same goal.
+</p>
+<p>
+ With the support of appropriate tools, you can use a design model to generate an initial code for implementation. This
+ is referred to as <strong>forward engineering</strong> or <strong>code generation</strong>. You can also enhance design
+ models to include enough information to build the system.
+</p>
+<p>
+ <strong>Reverse engineering</strong> may also be applied to generate design models from existing implementations. You
+ can use this method to evaluate existing implementations.&nbsp;&nbsp;
+</p>
+<p>
+ <strong>Round-trip engineering</strong> combines both forward and reverse engineering techniques to ensure consistent
+ design and code. Combined with an iterative process and the right tools, round-trip engineering allows you to
+ synchronize the design and code during each iteration.
+</p>
+<h4>
+ Capture requirements precisely
+</h4>
+<p>
+ Before building a system, it's critical to capture the requirements. Specifying the requirements using a precise and
+ unambiguous model helps to ensure that all stakeholders can understand and agree on the requirements.
+</p>
+<p>
+ A model that separates the external behavior of the system from the implementation of it helps you focus on the
+ intended use of the system, without getting bogged down in implementation details.
+</p>
+<h4>
+ Communicate decisions unambiguously
+</h4>
+<p>
+ The Unified Modeling Language (UML) is&nbsp;a consistent notation that can be applied for system engineering, as well
+ as for business engineering. According to these excerpts from the UML specification, a standard notation::
+</p>
+<ul>
+ <li>
+ <p>
+ Serves as a language for communicating decisions that are not obvious or cannot be inferred from the code
+ itself.
+ </p>
+ </li>
+ <li>
+ <p>
+ Provides semantics that are rich enough to capture all important strategic and tactical decisions.
+ </p>
+ </li>
+ <li>
+ <p>
+ Offers a form concrete enough for humans to reason [about] and for tools to manipulate.
+ </p>
+ </li>
+</ul>
+<p>
+ UML represents the convergence of the best practice in software modeling throughout the object-technology industry. For
+ more information on the UML, see <a class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/tech_references_6CCF393.html"
+ guid="_9ToeIB83Edqsvps02rpOOg">[UML05]</a>.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/examples/architectural_mechanism_attributes.xmi b/praclib/temp/core.tech.common.base/guidances/examples/architectural_mechanism_attributes.xmi
new file mode 100644
index 0000000..67e9d79
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/examples/architectural_mechanism_attributes.xmi
@@ -0,0 +1,86 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:GuidanceDescription 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="-8LfKJab2khAUjdmnImaXPA"
+ name="architecture_mechanism_attributes,_eQ_s8Om5Edupia_tZIXEqg" guid="-8LfKJab2khAUjdmnImaXPA"
+ changeDate="2008-02-15T09:07:30.734-0500">
+ <mainDescription><p>
+ The following shows an example of how to capture information for <a class="elementLink"
+ href="./../../../core.tech.common.base/guidances/concepts/arch_mechanism_2932DFB6.html"
+ guid="_mzxI0A4LEduibvKwrGxWxA">Architectural Mechanism</a>s. The attributes of two possible mechanisms are shown:
+ Persistence and Communication.
+</p>
+<h1>
+ Persistence
+</h1>
+<p>
+ For all classes with instances that may become persistent, you need to identify:
+</p>
+<ul>
+ <li>
+ <p>
+ <b>Granularity</b><b>:</b> What is the range of size of the objects to keep persistent?
+ </p>
+ </li>
+ <li>
+ <p>
+ <b>Volume</b><b>:</b> How many objects (number) do you need to keep persistent?
+ </p>
+ </li>
+ <li>
+ <p>
+ <b>Duration</b><b>:</b> How long does the object typically need to be kept?
+ </p>
+ </li>
+ <li>
+ <p>
+ <b>Retrieval mechanism</b><b>:</b> How is a given object uniquely identified and retrieved?
+ </p>
+ </li>
+ <li>
+ <p>
+ <b>Update frequency</b><b>:</b> Are the objects more or less constant? Are they permanently updated?
+ </p>
+ </li>
+ <li>
+ <p>
+ <b>Reliability</b><b>:</b> Do the objects need to survive a crash of the process, the processor, or the whole
+ system?
+ </p>
+ </li>
+</ul>
+<h1>
+ Communication
+</h1>
+<p>
+ For all model elements that need to communicate with components or services that are running in other processes or
+ threads, you need to identify:
+</p>
+<ul>
+ <li>
+ <p>
+ <b>Latency</b><b>:</b> How fast must processes communicate with another?
+ </p>
+ </li>
+ <li>
+ <p>
+ <b>Synchronicity</b><b>:</b> Asynchronous communication
+ </p>
+ </li>
+ <li>
+ <p>
+ <b>Size of message</b><b>:</b> A spectrum might be more appropriate than a single number
+ </p>
+ </li>
+ <li>
+ <p>
+ <b>Protocol:</b> Flow control, buffering, and so on
+ </p>
+ </li>
+</ul>
+<p>
+ Notice that there is no design-level information or specification here. Instead, this is more about collating and
+ refining architecturally significant requirements.
+</p></mainDescription>
+</org.eclipse.epf.uma:GuidanceDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/examples/architectural_mechanisms.xmi b/praclib/temp/core.tech.common.base/guidances/examples/architectural_mechanisms.xmi
new file mode 100644
index 0000000..f24c8cc
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/examples/architectural_mechanisms.xmi
@@ -0,0 +1,252 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:GuidanceDescription 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="-V6Hddpuwu3wvd9R0l4fL7Q"
+ name="new_example,_O39h0O9pEdu635i_iQ5Jag" guid="-V6Hddpuwu3wvd9R0l4fL7Q" changeDate="2007-04-20T11:03:28.709-0700">
+ <mainDescription><p>
+ Here are some examples of commonly encountered architectural mechanisms.<br />
+ <br />
+</p>
+<table cellspacing="0" cellpadding="2" width="85%" summary="Example Architectural Mechanisms" border="1" valign="top">
+ <caption>
+ <strong>Example Architectural Mechanisms</strong>
+ </caption>
+ <tbody>
+ <tr>
+ <th scope="col">
+ Architectural Mechanism
+ </th>
+ <th scope="col">
+ Description
+ </th>
+ </tr>
+ <tr>
+ <td>
+ Availability
+ </td>
+ <td>
+ The percentage of time that the system must be available for use, including planned outages.
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Archiving
+ </td>
+ <td>
+ Provides a means to move data from active storage when it has reached a specific state.
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Auditing
+ </td>
+ <td>
+ Provides audit trails of system execution.
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Communication
+ </td>
+ <td>
+ A mechanism for handling inter-process communication.
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Debugging
+ </td>
+ <td>
+ Provides elements to support application debugging.
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Disaster Recovery
+ </td>
+ <td>
+ Provides facilities to recover systems, application, data and networks.
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Error Management
+ </td>
+ <td>
+ Allows errors to be detected, propagated, and reported.
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Event Management
+ </td>
+ <td>
+ Supports the use of asynchronous events within a system.
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Graphics
+ </td>
+ <td>
+ Supports user interface services, such as 3D rendering.
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Information Exchange
+ </td>
+ <td>
+ Supports information interchange across technical and organizational boundaries with appropriate semantic
+ and format translations.
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Licensing
+ </td>
+ <td>
+ Provides services for acquiring, installing, tracking, and monitoring license usage. Might be required as
+ part of authorizing corporatebodies.
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Localization / Internationalization</td>
+ <td>
+ Provides facilities for supporting multiple human languages and rendering the language preferred bythe
+ user.
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Mail
+ </td>
+ <td>
+ Services that allow applications to send and receive electronic mail.
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Mega-data
+ </td>
+ <td>
+ Support for handling very large amounts of data.
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Memory Management
+ </td>
+ <td>
+ Services for abstracting how memory is allocated and freed.
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Meta-data
+ </td>
+ <td>
+ Supports the runtime introspection of components and data.
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Online help
+ </td>
+ <td>
+ Provides online help capability
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Persistence
+ </td>
+ <td>
+ Services to handle the reading and writing of stored data.
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Printing
+ </td>
+ <td>
+ Provides facilities for interfacing with printers.
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Process Management
+ </td>
+ <td>
+ Provides support for the management of processes and threads.
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Reporting
+ </td>
+ <td>
+ Provides flexible reporting facilities
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Resource Management
+ </td>
+ <td>
+ Provides support for the management of expensive resources, such as database connections.
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Scheduling
+ </td>
+ <td>
+ Provides the ability to execute tasks at a specified time.
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Security
+ </td>
+ <td>
+ Provides services to protect access to certain resources or information.
+ </td>
+ </tr>
+ <tr>
+ <td>
+ System Management
+ </td>
+ <td>
+ Services that facilitate management of applications in an operational environment.
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Time
+ </td>
+ <td>
+ Services to synchronize time on a network, and to translate times into different time zones.
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Transaction Management
+ </td>
+ <td>
+ A mechanism for handling ACID transactions.
+ </td>
+ </tr>
+ <tr>
+ <td>
+ Workflow
+ </td>
+ <td>
+ Support for the movement of documents and other items of work, typically through an organization.</td>
+ </tr>
+ </tbody>
+</table>
+<br /></mainDescription>
+</org.eclipse.epf.uma:GuidanceDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/examples/four_plus_one_view_of_arch.xmi b/praclib/temp/core.tech.common.base/guidances/examples/four_plus_one_view_of_arch.xmi
new file mode 100644
index 0000000..e38c97b
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/examples/four_plus_one_view_of_arch.xmi
@@ -0,0 +1,70 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:GuidanceDescription 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="-sKBCb98PYCcliL0zVljcyQ"
+ name="new_example,_4bC4cNs_EdyEW4klSH3vRA" guid="-sKBCb98PYCcliL0zVljcyQ" changeDate="2008-02-15T09:14:05.812-0500"
+ version="7.2.0">
+ <mainDescription><p>
+ You may want to consider the following views (not all views are relevant to all systems or all the stakeholders). This
+ set of views is known as the 4+1 Views of Software Architecture [<a class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/tech_references_6CCF393.html"
+ guid="_9ToeIB83Edqsvps02rpOOg">KRU95</a>].
+</p>
+<p>
+ <img height="254" alt="4+1 Views of Software Architecture" src="./resources/4plus1_2.jpg" width="405" />
+</p>
+<ul>
+ <li>
+ <p>
+ <strong>Use-case view</strong>: Describes functionality of the system, its external interfaces, and its
+ principal users. This view is mandatory when using the 4+1 Views, because all elements of the architecture
+ should be derived from requirements.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Logical view</strong>: Describes how the system is structured in terms of units of implementation. The
+ elements are packages, classes, and interfaces. The relationship between elements shows dependencies, interface
+ realizations, part-whole relationships, and so forth. Note: This view is mandatory when using the 4+1 Views of
+ Software Architecture.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Implementation view</strong>: Describes how development artifacts are organized in the file system. The
+ elements are files and directories (any configuration items). This includes development artifacts and
+ deployment artifacts. This view is optional when using the 4+1 Views.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Process view</strong>: Describes how the run-time system is structured as a set of elements that have
+ run-time behavior and interactions. Run-time structure often bears little resemblance to the code structure. It
+ consists of rapidly changing networks of communication objects. The elements are components that have run-time
+ presence (processes, threads, Enterprise JavaBeans&trade; (EJB&trade;), servlets, DLLs, and so on), data stores, and
+ complex connectors, such as queues. Interaction between elements varies, based on technology. This view is
+ useful for thinking about run-time system quality attributes, such as performance and reliability. This view is
+ optional when using the 4+1 Views.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Deployment view</strong>: Describe how the system is mapped to the hardware. This view is optional when
+ using the 4+1 Views.
+ </p>
+ </li>
+</ul>
+<p>
+ In addition, you may wish to represent the following,
+</p>
+<ul>
+ <li>
+ <p>
+ <strong>Data view</strong>: A specialization of the logical view. Use this view if persistence is a significant
+ aspect of the system, and the translation from the design model to the data model is not done automatically by
+ the persistence mechanism.
+ </p>
+ </li>
+</ul></mainDescription>
+</org.eclipse.epf.uma:GuidanceDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/examples/resources/4plus1_2.jpg b/praclib/temp/core.tech.common.base/guidances/examples/resources/4plus1_2.jpg
new file mode 100644
index 0000000..24cfc97
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/examples/resources/4plus1_2.jpg
Binary files differ
diff --git a/praclib/temp/core.tech.common.base/guidances/examples/resources/atm_uc_model_elaboration.doc b/praclib/temp/core.tech.common.base/guidances/examples/resources/atm_uc_model_elaboration.doc
new file mode 100644
index 0000000..c1c6442
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/examples/resources/atm_uc_model_elaboration.doc
Binary files differ
diff --git a/praclib/temp/core.tech.common.base/guidances/examples/resources/atm_uc_model_inception.doc b/praclib/temp/core.tech.common.base/guidances/examples/resources/atm_uc_model_inception.doc
new file mode 100644
index 0000000..d6cb7d3
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/examples/resources/atm_uc_model_inception.doc
Binary files differ
diff --git a/praclib/temp/core.tech.common.base/guidances/examples/resources/deposit_funds_outline.doc b/praclib/temp/core.tech.common.base/guidances/examples/resources/deposit_funds_outline.doc
new file mode 100644
index 0000000..69abe36
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/examples/resources/deposit_funds_outline.doc
Binary files differ
diff --git a/praclib/temp/core.tech.common.base/guidances/examples/resources/transfer_funds_outline.doc b/praclib/temp/core.tech.common.base/guidances/examples/resources/transfer_funds_outline.doc
new file mode 100644
index 0000000..e1e26f6
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/examples/resources/transfer_funds_outline.doc
Binary files differ
diff --git a/praclib/temp/core.tech.common.base/guidances/examples/resources/use_case_spec_validate_user.doc b/praclib/temp/core.tech.common.base/guidances/examples/resources/use_case_spec_validate_user.doc
new file mode 100644
index 0000000..3c4ec9e
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/examples/resources/use_case_spec_validate_user.doc
Binary files differ
diff --git a/praclib/temp/core.tech.common.base/guidances/examples/resources/use_case_spec_withdraw_cash.doc b/praclib/temp/core.tech.common.base/guidances/examples/resources/use_case_spec_withdraw_cash.doc
new file mode 100644
index 0000000..a2d147c
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/examples/resources/use_case_spec_withdraw_cash.doc
Binary files differ
diff --git a/praclib/temp/core.tech.common.base/guidances/examples/resources/withdraw_cash_outline.doc b/praclib/temp/core.tech.common.base/guidances/examples/resources/withdraw_cash_outline.doc
new file mode 100644
index 0000000..bd23ee1
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/examples/resources/withdraw_cash_outline.doc
Binary files differ
diff --git a/praclib/temp/core.tech.common.base/guidances/examples/uc_model_evolve.xmi b/praclib/temp/core.tech.common.base/guidances/examples/uc_model_evolve.xmi
new file mode 100644
index 0000000..c94fe57
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/examples/uc_model_evolve.xmi
@@ -0,0 +1,103 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:GuidanceDescription 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="-JviMIao63C7w9C8W6iPJrw"
+ name="new_example,_t4QdAMNqEdu2IdAIaWZyAw" guid="-JviMIao63C7w9C8W6iPJrw" authors="Chris Sibbald"
+ changeDate="2008-01-07T16:45:37.422-0800">
+ <mainDescription><h1>
+ Introduction
+</h1>
+<p>
+ This example illustrates how the use-case model and associated use-case specification will evolve during the lifecycle.
+ It shows the state of the use case model at two points in the lifecycle: early inception and towards the end of
+ elaboration. The purpose is to illustrate how one would identify, outline and detail requirements so as to maximize
+ stakeholder value and minimize risk early in the project, as well as to minimize re-work later.
+</p>
+<p>
+ The example uses an Automated Teller Machine as the example system, because it is familiar to most people. This
+ familiarity simplifies understanding the principles without getting lost in domain specific terminology.
+</p>
+<h2>
+ Early inception
+</h2>
+<p>
+ Assume you have just started on the project as the Analyst. You have identified the key stakeholders and met with them
+ to discuss their needs. During your meetings, you identified a number of key actors, use cases, and supporting
+ requirements for the ATM system. You captured the use cases and actors, with names and brief descriptions only, in the
+ use-case model. An example of this work is given in the document <strong>ATM UC Model Inception</strong>.
+</p>
+<p>
+ Prior to committing significant time to detailing these use cases now, you recognize that a “breadth before depth”
+ approach can save you valuable time and permit you to identify the highest value and highest risk items so that you can
+ concentrate on those first.
+</p>
+<p>
+ You hold a brainstorming session with the stakeholders and outline the basic flow of each of the main use cases. As you
+ are working through, you may identify some additional alternative flows. Fight the urge to “dive-in” to the details on
+ these alternative flows at this point, simply list them and come back later when you have a better understanding of the
+ “big picture”.
+</p>
+<p>
+ Examples of the notes you took during this exercise are attached (<strong>Withdraw Cash Outline</strong>,
+ <strong>Deposit Funds Outline</strong> and <strong>Transfer</strong> <strong>Funds Outline</strong>).<br />
+ <b>Note:</b> the choice of font is intentional to illustrate that these are notes, not formal documents.
+</p>
+<p>
+ Reviewing your notes, you recognize that there is some behavior that is common to most of the use cases, namely the
+ steps required to validate the Bank Customer. Factoring this behavior out into an &lt;&lt;included&gt;&gt; use case
+ will simplify communications, iteration planning, and maintenance.
+</p>
+<p>
+ You update the use case model accordingly: <strong>ATM UC Model Elaboration</strong>.
+</p>
+<h2>
+ Elaboration
+</h2>
+<p>
+ With a better understanding of the system, you can now prioritize your effort to maximize value and minimize risk. You
+ start by detailing the common behavior captured in the use case: Validate User. This use case captures key
+ architectural requirements that will exercise a significant portion of the system (communications with the Bank, card
+ reader interface, and so on). Implementing this one key scenario will go a long way to reducing risk.
+</p>
+<p>
+ An example of the Validate User use-case specification is attached: <strong>Use Case Spec - Validate User.</strong>
+</p>
+<p>
+ Note that there may still be some un-answered questions, but that’s OK. Capture these directly in the use-case
+ specification and get them answered (see Section 5.6 of the <strong>Validate User UC Specification</strong>, for an
+ example).
+</p>
+<p>
+ Continuing with another architecturally significant thread, you detail the basic flow and some key alternative flows of
+ the use case: Withdraw Cash. You know that if the team can implement this, much of the other functionality will be low
+ risk.
+</p>
+<p>
+ An example of the Withdraw Cash use-case specification is attached:&nbsp;<strong>Use Case Spec - Withdraw
+ Cash</strong>.
+</p>
+<h1>
+ Summary
+</h1>
+<p>
+ By following a breadth before depth approach to outlining and detailing use cases, you can make better decisions on
+ priorities. Start by identifying actors. Then for each actor, ask “What is the main purpose this actor would like to
+ use the system?”. This will lead to the identification of the use cases. Capture the actors and use cases in the
+ use-case model along with a brief description.
+</p>
+<p>
+ Prioritize the use cases, and then draft the main scenario or basic flow. As you are working through this you may
+ identify alternate flows (what can go wrong, what options are available, and so on). Capture these, along with a brief
+ description.
+</p>
+<p>
+ Review the use-case model and reprioritize and assess risk. For the high priority (based on value to the stakeholders)
+ or high risk use cases,&nbsp;detail the main scenario and the critical alternate flows.
+</p>
+<p>
+ If you follow this approach, you will increase the likelihood of delivering value early, minimizing risk, and
+ minimizing re-work.<br />
+</p></mainDescription>
+ <attachments>resources/atm_uc_model_inception.doc|resources/withdraw_cash_outline.doc|resources/deposit_funds_outline.doc|resources/transfer_funds_outline.doc|resources/atm_uc_model_elaboration.doc|resources/use_case_spec_validate_user.doc|resources/use_case_spec_withdraw_cash.doc</attachments>
+</org.eclipse.epf.uma:GuidanceDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/examples/use_case_spec.xmi b/praclib/temp/core.tech.common.base/guidances/examples/use_case_spec.xmi
new file mode 100644
index 0000000..f50e698
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/examples/use_case_spec.xmi
@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:GuidanceDescription 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="-qq-9Brh5oa6H3lsdp-m8mQ"
+ name=",_JLOiIMNvEdu2IdAIaWZyAw" guid="-qq-9Brh5oa6H3lsdp-m8mQ" changeDate="2008-01-25T14:02:15.777-0800"
+ version="7.2.0">
+ <mainDescription><p>
+ The attached document provides an example of a use-case specification for an Automated Teller Machine (ATM). The ATM
+ was selected as an example system because it is familiar to most people. This familiarity simplifies understanding the
+ principles without getting lost in domain-specific terminology.
+</p>
+<p>
+ A companion example, <a class="elementLink"
+ href="./../../../core.tech.common.base/guidances/examples/uc_model_evolve_960F136B.html"
+ guid="_t4QdAMNqEdu2IdAIaWZyAw">Evolution of the Use-Case Model</a>, shows how the use-case model as a whole evolves
+ over time.<br />
+</p></mainDescription>
+ <attachments>resources/use_case_spec_withdraw_cash.doc</attachments>
+</org.eclipse.epf.uma:GuidanceDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/guidelines/abstract_away_complexity.vm.xmi b/praclib/temp/core.tech.common.base/guidances/guidelines/abstract_away_complexity.vm.xmi
new file mode 100644
index 0000000..af695d7
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/guidelines/abstract_away_complexity.vm.xmi
@@ -0,0 +1,21 @@
+<?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="-OcMsciNn-UtD9fTHj26LGA"
+ name="new_guideline,_34jWsLcIEduRNaXpzCOLXQ" guid="-OcMsciNn-UtD9fTHj26LGA" changeDate="2008-02-14T08:04:57.765-0500"
+ version="1.0.0">
+ <mainDescription><h3>
+ Model key perspectives
+</h3>
+<p>
+ Modeling helps raise the level of abstraction because you simplify complex ideas and represent them visually, as
+ illustrations. Good models can convey information that helps the team visualize, specify, construct, and document
+ software.
+</p>
+<p>
+ For more information, see <a class="elementLinkWithType"
+ href="./../../../core.tech.common.base/guidances/guidelines/using_visual_modeling_DA1CA6E4.html"
+ guid="_0SsecNr8EdyXE6np2_hUMA">Guideline: Using Visual Modeling</a>.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/guidelines/abstract_away_complexity.xmi b/praclib/temp/core.tech.common.base/guidances/guidelines/abstract_away_complexity.xmi
new file mode 100644
index 0000000..f549276
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/guidelines/abstract_away_complexity.xmi
@@ -0,0 +1,59 @@
+<?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="-X7QSjItNBz7w8603yBCv0Q"
+ name="abstract_away_complexity,_we3F4ACpEdu8m4dIntu6jA" guid="-X7QSjItNBz7w8603yBCv0Q"
+ changeDate="2008-02-14T08:10:01.156-0500" version="1.0.0">
+ <mainDescription><p>
+ Software&nbsp;development is a pursuit characterized by complexity. This can take many forms, such as accommodating
+ complex requirements, technology, or team dynamics. Elevating the level of abstraction helps you manage this complexity
+ and make measurable progress, despite the inherent difficulty of the task.
+</p>
+<p>
+ Suggestions for several strategies that help abstract away complexity follow.
+</p>
+<h3>
+ Leverage patterns
+</h3>
+<p>
+ Patterns help you take advantage of proven techniques for solving common problems. You can benefit from the experience
+ of seasoned practitioners and avoid "re-inventing the wheel," as the saying goes. The use of patterns is a crucial
+ aspect of an architecture-centric approach to development, because it helps reduce the novelty and diversity of a
+ solution, thus improves quality.
+</p>
+<p>
+ See <a class="elementLinkWithType" href="./../../../core.tech.common.base/guidances/concepts/pattern_10BE6D96.html"
+ guid="_0YJvUMlgEdmt3adZL5Dmdw">Concept: Pattern</a>&nbsp;for more information.
+</p>
+<h3>
+ Design the architecture with components and services
+</h3>
+<p>
+ This strategy helps manage software complexity through&nbsp;partitioning&nbsp;a system into a set of loosely coupled
+ and highly cohesive components. The benefits of this approach include the ability to organize the team around a set of
+ smaller, more manageable objectives, and the ability to substitute parts of the system without disturbing the overall
+ cohesion of the system. Exposing services encourages re-use by making the functionality of the system easier to
+ comprehend. Focusing on services makes it possible to understand what the system does from a technical perspective
+ without necessarily having to understand the details of how the system works.
+</p>
+<p>
+ See <a class="elementLinkWithType" href="./../../../core.tech.common.base/guidances/concepts/component_CB167D48.html"
+ guid="_0YP18MlgEdmt3adZL5Dmdw">Concept: Component</a>&nbsp;for more information. [*** Seems like we should have a
+ Concept: Service, as well.&nbsp; Thoughts?&nbsp;***]
+</p>
+<h3>
+ Actively promote reuse
+</h3>
+<p>
+ Incorporating existing software into an overall architecture helps reduce cost and improve quality by reusing proven
+ working software, rather than developing from scratch. It also helps reduce the burden of maintenance by eliminating
+ duplication in the software. Although often difficult to manage, a project or enterprise can reap significant benefits
+ from a well-executed re-use strategy.
+</p>
+<p>
+ See <a class="elementLinkWithType"
+ href="./../../../practice.tech.evolutionary_design.base/guidances/guidelines/software_reuse_B6B04C26.html"
+ guid="_vO2uoO0OEduUpsu85bVhiQ">Guideline: Software Reuse</a>&nbsp;for more information.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/guidelines/continuous_integration.xmi b/praclib/temp/core.tech.common.base/guidances/guidelines/continuous_integration.xmi
new file mode 100644
index 0000000..6c235c5
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/guidelines/continuous_integration.xmi
@@ -0,0 +1,97 @@
+<?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="-DlaqJu4sEqMPk84qhJ6IEA"
+ name="continuous_integration,_i8bUEL6cEdqti4GwqTkbsQ" guid="-DlaqJu4sEqMPk84qhJ6IEA"
+ changeDate="2006-05-31T06:26:30.000-0400" version="7.2.0">
+ <mainDescription><p>
+ Continuous integration is a software development practice that completely rebuilds and tests the application frequently
+ -- ideally, every time a change is introduced. This approach provides many benefits as outlined in <a
+ class="elementLinkWithType" href="./../../../core.tech.slot.base/guidances/concepts/continuous_integration_87682D06.html"
+ guid="_B3xkEPD0EdqYgerqi84oCA">Concept: Continuous Integration</a> and in <a class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/references_6CCF393.html#WIKP-CI"
+ guid="_9ToeIB83Edqsvps02rpOOg">[WIKP-CI]</a>.
+</p>
+<h1>
+ Basic steps
+</h1>
+<p>
+ The detailed application of continuous integration depends on which tools you use (configuration management system,
+ automated build tool, automated test tool, and so forth). However, these are the basic steps:
+</p>
+<ol>
+ <li>
+ A developer, let’s call her Jane, selects a&nbsp;work item&nbsp;to work on.
+ </li>
+ <li>
+ Jane updates her <a class="elementLink"
+ href="./../../../opn.swd.prac.legacy_pm/guidances/concepts/workspace_722BBA90.html"
+ guid="_0cEmAMlgEdmt3adZL5Dmdw">Workspace</a> to include the most recent <a class="elementLink"
+ href="./../../../opn.swd.prac.legacy_impl/workproducts/implementation_917CA61E.html"
+ guid="_0YoQcMlgEdmt3adZL5Dmdw">Implementation</a> from the integration workspace.
+ </li>
+ <li>
+ Jane makes her changes in her workspace to both her developer tests and to the implementation, and then she tests
+ the changes.
+ </li>
+ <li>
+ Before committing the changes, Jane updates her workspace again (because other developers may have introduced
+ conflicting changes) and reruns her developer tests.
+ </li>
+ <li>
+ If these tests are successful, the changes are promoted (see <a class="elementLinkWithType"
+ href="./../../../core.tech.slot.base/guidances/guidelines/promoting_changes_9087B764.html"
+ guid="_SM4YIL6dEdqti4GwqTkbsQ">Guideline: Promoting Builds</a>) to&nbsp;the&nbsp;integration workspace.
+ </li>
+ <li>
+ A complete <a class="elementLink"
+ href="./../../../opn.swd.prac.legacy_impl/workproducts/build_95D7D8FD.html"
+ guid="_0YuXEMlgEdmt3adZL5Dmdw">Build</a> of the application is performed by using the implementation from the
+ integration workspace, and the entire suite of developer tests is run on this build.
+ </li>
+ <li>
+ If any of these tests fail, the team is notified, and the failed test should be addressed as soon as possible.
+ </li>
+ <li>
+ This process repeats as the team develops and continuously integrates and tests functionality in small increments.
+ </li>
+</ol>
+<h1>
+ Constraints
+</h1>
+<p>
+ Conceptually, continuous integration can be performed manually (see <a class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/references_6CCF393.html#SHO06"
+ guid="_9ToeIB83Edqsvps02rpOOg">[SHO06]</a> for example). However, in practice, there are several constraints that must
+ be respected for it to be effective:
+</p>
+<ol>
+ <li>
+ All changes must be introduced into a tested configuration that you know to be good.
+ </li>
+ <li>
+ The integrate-build-test cycle must be fast enough so that it can be completed quickly and the team notified of the
+ results. Many published guidelines promote a 10-minute cycle.
+ </li>
+ <li>
+ Keep the <a class="elementLink"
+ href="./../../../opn.swd.prac.legacy_pm/guidances/concepts/change_set_430BF233.html"
+ guid="_1QU9MAIoEdyLh7vsrHZ4YA">Change Set</a>s&nbsp;small enough so that the work can be completed and integration
+ performed several times per day. Many published guidelines promote a 2- to 4-hour cycle between integrations.
+ </li>
+</ol>
+<p>
+ These constraints imply the need for a configuration management (CM) repository to maintain configuration information
+ (Item 1 listed previously), automated build and test tools to meet the turnaround constraints (Item 2), and proper
+ planning and discipline by developers to ensure that their work items and change sets are small enough to complete
+ quickly (Item 3).
+</p>
+<p>
+ For a more detailed description of continuous integration, see <a class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/references_6CCF393.html#FOW06"
+ guid="_9ToeIB83Edqsvps02rpOOg">[FOW06]</a> or <a class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/references_6CCF393.html#WIKP-CI"
+ guid="_9ToeIB83Edqsvps02rpOOg">[WIKP-CI]</a>.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/guidelines/effective_req_reviews.xmi b/praclib/temp/core.tech.common.base/guidances/guidelines/effective_req_reviews.xmi
new file mode 100644
index 0000000..4d1bf4c
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/guidelines/effective_req_reviews.xmi
@@ -0,0 +1,130 @@
+<?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="-pNA0DbSdSoUqnjQIiOeHcQ"
+ name="achieving_concurrence,_E-dPIL-GEdqb7N6KIeDL8Q" guid="-pNA0DbSdSoUqnjQIiOeHcQ"
+ changeDate="2006-09-22T06:09:40.000-0700" version="1.0.0">
+ <mainDescription><p>
+ The cost of correcting errors increases exponentially throughout the development lifecycle <a
+ class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/references_6CCF393.html"
+ guid="_9ToeIB83Edqsvps02rpOOg">[BOE88]</a>. Therefore, it is important to discover problems early enough to solve them
+ quickly and inexpensively.
+</p>
+<p>
+ Requirements reviews are intended to discover problems with the <a class="elementLink"
+ href="./../../../core.tech.slot.base/guidances/concepts/requirements_8006414F.html"
+ guid="_0Wh-sMlgEdmt3adZL5Dmdw">Requirements</a>&nbsp;before you spend significant time and work in implementing the
+ wrong thing. This is not to say that you must have a complete set of requirements before implementation, but be sure to
+ review, internally and with stakeholders, those that are selected for implementation in the early iterations and those
+ that will have a broad impact on the system (often called <a class="elementLink"
+ href="./../../../core.tech.slot.base/guidances/concepts/architecturally_significant_requirements_1EE5D757.html"
+ guid="_HrZGIA4MEduibvKwrGxWxA">Architecturally Significant Requirements</a>) to ensure everyone's concurrence before
+ investing significant effort in implementation.
+</p>
+<h4>
+ Informal reviews
+</h4>
+<p>
+ Requirements reviews can be informal, such as simply showing draft requirements to your colleagues or demonstrating a
+ prototype.
+</p>
+<p>
+ These informal reviews are excellent for getting the structure of the requirements correct and removing obvious
+ mistakes. By keeping the review team small, it is easier to make rapid progress. However, informal reviews can miss
+ important perspectives&nbsp;of&nbsp;critical stakeholders.
+</p>
+<h4>
+ Formal reviews
+</h4>
+<p>
+ Requirement reviews can be formal meetings. Start with careful preparation, so that you receive and organize comments
+ before the meeting. The meeting itself should produce decisions on all review items. After the meeting, you must pursue
+ the review actions to completion. If these actions involve a substantial amount of work or require a change to an
+ artifact that is under configuration control, consider submitting <a class="elementLink"
+ href="./../../../opn.swd.prac.legacy_pm/guidances/concepts/change_requests_AD4868FE.html"
+ guid="_6jdvECb3Edqh1LYUOGRh2A">Change Requests</a> to prioritize and track the work. See&nbsp;<a
+ class="elementLinkWithType" href="./../../../opn.swd.prac.legacy_pm/tasks/request_change_A048C387.html"
+ guid="_0mwzEclgEdmt3adZL5Dmdw">Task: Request Change</a>&nbsp;and the associated&nbsp;<a class="elementLinkWithType"
+ href="./../../../opn.swd.prac.legacy_pm/guidances/guidelines/submitting_change_requests_7A1FE1A6.html"
+ guid="_fnZj0NVXEdqy9sbRhejO5Q">Guideline: Submitting Change Requests</a>&nbsp;for more information on change requests.
+</p>
+<p>
+ Formal reviews are more wide-ranging and expensive. They provide for more balanced reviews from multiple
+ perspectives.&nbsp; However, formal reviews involve more people, which makes them more difficult to coordinate (thus
+ the need for formality) and expensive in terms of work hours.
+</p>
+<h4>
+ Two-tier reviews
+</h4>
+<p>
+ One technique to get the best of both worlds is to use staged, or "two-tier", reviews&nbsp;<a
+ class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/references_6CCF393.html"
+ guid="_9ToeIB83Edqsvps02rpOOg">[ADO03]</a>. The&nbsp;first tier is informal and performed by a smaller team, possibly
+ many times. The second&nbsp;tier is more formal and performed by the complete group, perhaps only once.
+</p>
+<p>
+ <strong>First-tier review:</strong> The authors of the requirements and the development team&nbsp;review the
+ requirements during the first-tier reviews to ensure that they are&nbsp;unambiguous, complete&nbsp;and
+ consistent.&nbsp; It is important to include testers and developers to ensure that the requirements are verifiable and
+ feasible.&nbsp;These reviews&nbsp;determine whether the requirements are ready for the larger community to
+ review.&nbsp; First-tier reviews may be informal, formal, or a combination of the two.
+</p>
+<p>
+ <strong>Second-tier review:</strong> Involve the larger group during the higher-tier review to get more minds working
+ on the problem and to achieve concurrence that the requirements are suitable for implementation and validation.&nbsp;
+ It is best to have one formal requirement review at the Lifecycle Objective (LCO) milestone and, optionally, one at the
+ Lifecycle Architecture (LCA) milestone if significant changes have occurred that introduce unacceptable risk.
+</p>
+<p>
+ At both stages, these two resources will be helpful: <a class="elementLinkWithType"
+ href="./../../../opn.tech.prac.basic_tech_rqmts_def/guidances/checklists/general_requirements_594ACCBD.html"
+ guid="_jxn9EO0HEdqHTdbLTmC5IQ">Checklist: *General Requirements</a>&nbsp;and <a class="elementLinkWithType"
+ href="./../../../opn.tech.prac.rqmts_with_use_cases/guidances/checklists/use_case_C5362874.html"
+ guid="_0kNwINk1Edq2Q8qZoWbvGA">Checklist: *Use Case</a>
+</p>
+<p>
+ Tiered reviews offer several benefits:
+</p>
+<ol>
+ <li>
+ Eliminate the noise caused by minor edits during the first-tier reviews, allowing subsequent reviews to focus on
+ functionality
+ </li>
+ <li>
+ Provide a professional look to the requirements, presenting both the requirements and their authors in the best
+ possible light
+ </li>
+ <li>
+ Safeguard the time of stakeholders who are reviewing the requirements, thus preventing "review burnout", or
+ diminished effectiveness from overload and stress
+ </li>
+ <li>
+ Provide the best opportunity for full, effective reviews.
+ </li>
+</ol>
+<h4>
+ Golden rules of reviewing
+</h4>
+<p>
+ Follow these golden&nbsp;rules of reviewing <a class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/references_6CCF393.html"
+ guid="_9ToeIB83Edqsvps02rpOOg">[TEL06]</a>:
+</p>
+<ol>
+ <li>
+ <strong>Encourage criticism:</strong> Remember that people are improving the requirements, not criticizing you.
+ Even the harshest criticism often contains a grain of truth. Adopt the attitude that every suggestion is a gift.
+ </li>
+ <li>
+ <strong>Choose your best reviewers:</strong> A few specific people make the best reviewers, time and again.
+ Cultivate them.
+ </li>
+ <li>
+ <strong>Allow adequate time:</strong> It's not over until you have agreed upon and made the corrections.<br />
+ &nbsp;
+ </li>
+</ol></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/guidelines/entity_control_boundary_pattern.xmi b/praclib/temp/core.tech.common.base/guidances/guidelines/entity_control_boundary_pattern.xmi
new file mode 100644
index 0000000..cd55c8a
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/guidelines/entity_control_boundary_pattern.xmi
@@ -0,0 +1,210 @@
+<?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="-awaQ_2dwhGyKRoVKQ-esPQ"
+ name="finding_analysis_classes,_uF-QYEAhEdq_UJTvM1DM2Q" guid="-awaQ_2dwhGyKRoVKQ-esPQ"
+ changeDate="2008-02-15T09:22:39.015-0500" version="1.0.0">
+ <mainDescription><p>
+ When identifying the elements for a scenario of system behavior, you can align each participating element with one of
+ three key perspectives: <b>Entity</b>, <b>Control</b>, or <b>Boundary</b>. Although specifics of languages, frameworks,
+ and heuristics of quality design will drive the final design, a first cut that covers required system behavior can
+ always be assembled with elements of these three perspectives.
+</p>
+<p>
+ This pattern is similar to the Model View Controller pattern (described here [<a class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/tech_references_6CCF393.html#BUS96"
+ guid="_9ToeIB83Edqsvps02rpOOg">BUS96</a>] and here [<a class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/tech_references_6CCF393.html#WIKP-MVC"
+ guid="_9ToeIB83Edqsvps02rpOOg">WIKP-MVC</a>], among other places), but the Entity Control Boundary (ECB) pattern is not
+ solely appropriate for dealing with user interfaces, and it gives the controller a slightly different role to play.
+</p>
+<h4 align="left">
+ ECB&nbsp;pattern example
+</h4>
+<p>
+ &nbsp;<img alt="" src="./resources/ebc_diagram.JPG" />
+</p>
+<h1>
+ Entity elements
+</h1>
+<p>
+ An entity is a long-lived, passive element that is responsible for some meaningful chunk of information. This is not to
+ say that entities are "data," while other design elements are "function." Entities perform behavior organized around
+ some cohesive amount of data.
+</p>
+<p>
+ An example of an entity for a customer service application is a Customer entity that manages all information about a
+ customer. A design element for&nbsp;this entity would include data about the customer, behavior to manage the data,
+ behavior to validate customer information&nbsp;and to perform other business calculations, such as "Is this customer
+ allowed to purchase product X?"
+</p>
+<p>
+ The identification of the entities as part of this pattern can be done many times at different levels of abstraction
+ from the code, at different levels of granularity in size, and from the perspectives of different contexts. For
+ example, you could do an analysis pass on a scenario of creating a marketing campaign and identify the customer element
+ with various customer data elements, such as name and address, plus various required behaviors, such as the management
+ of the name and address data and the ability to rate the customer based on some algorithm (such an application of this
+ pattern would be abstract from code, coarse-grained, and have no specific context). Later, you could do a pass on the
+ same scenario applying an architectural mechanism for database access that breaks the address out as its own element,
+ moves the responsibility for storing and retrieving customers to a new control element, and identifies specific
+ database decisions, such as the use of primary keys in the entities. (Such an application of this pattern would be
+ closer to the code, finer-grained, and aligned with a database&nbsp;context.)
+</p>
+<h1>
+ Control elements
+</h1>
+<p>
+ A control element manages the flow of interaction of the scenario. A control element could manage the end-to-end
+ behavior of a scenario. or it could manage the interactions between a subset of the elements. Behavior and business
+ rules relating to the information relevant to the scenario should be assigned to the entities; the control elements are
+ responsible only for the flow of the scenario.
+</p>
+<p>
+ CreateMarketingCapmpaign is an example of a control element for a customer service application. This design element
+ would&nbsp;be responsive to certain frontend boundary elements and would collaborate with other entities,
+ control&nbsp;elements, and backend boundary elements to support the creation of a marketing campaign.
+</p>
+<p>
+ As with the entity example here, there might be many passes over the identification of control elements. A first pass
+ might be an analysis pass that identifies one control element for a scenario, with behavior to make sure that the
+ design can support the flow of events. A&nbsp;subsequent pass might find controllers to manage reusable collaborations
+ of low-level elements that will map to a specific code&nbsp;unit to be written.
+</p>
+<h1>
+ Boundary elements
+</h1>
+<p>
+ A boundary element lies on the periphery of a system or subsystem, but within it. For any scenario being considered
+ either across the whole system or within some subsystem, some boundary elements will be "front end" elements that
+ accept input from outside of the area under design, and other elements will be "back end," managing communication to
+ supporting elements outside of the system or subsystem.
+</p>
+<p>
+ Two examples of boundary elements for a customer service application might be a front end MarketingCampaignForm and a
+ back end BugdetSystem element. The MarketingCampaignForm would manage the exchange of information between a user and
+ the system, and the BugdetSystem would manage the exchange of information between the system and an external system
+ that manages budgets.
+</p>
+<p>
+ If the system communicates with another system (where that system could be anything from software to hardware units
+ that the current system will use, such as printers, terminals, alarm devices, and sensors).&nbsp; An analysis pass
+ could identify one boundary element for each external relevant to a scenario.
+</p>
+<p>
+ Example:
+</p>
+<blockquote>
+ <p>
+ An automated teller machine (ATM) must communicate with the ATM network to ascertain whether a customer's bank
+ number and PIN are correct, and whether the customer has sufficient funds to withdrawal the requested amount. The
+ ATM network is an external system (from the perspective of the ATM); therefore, you would use a
+ <strong>boundary</strong> class to represent it in a use-case analysis.
+ </p>
+</blockquote>
+<p>
+ Subsequently, these could be broken down into multiple boundary elements or small communities made up of collaborating
+ elements of all three stereotypes. If the interfaces with the system are simple and well-defined, a single class may be
+ sufficient to represent the external system. Often, however, these interfaces are too complex to be represented by
+ using a single class; they often require complex collaborations of many classes. Moreover, interfaces between systems
+ are often highly reusable across applications. As a result, in many cases, a component models the system interfaces
+ more appropriately.&nbsp; The use of a component allows the interface to the external system to be defined and
+ stabilized, while leaving the design details of the system interface hidden as the system evolves.
+</p>
+<h1>
+ Walking through the scenario
+</h1>
+<p>
+ You can walk through a scenario initiated by something outside of the boundaries of the system or subsystem being
+ designed and distribute the responsibility to perform behavior supporting the scenario to the elements identified of
+ each type. The appropriate design element responsible for each action in the scenario will be as described in the
+ definition of each of the element types described here previously.
+</p>
+<p>
+ In addition to identifying the behavior necessary to perform the scenario, the initiation of this behavior from design
+ element to design element identifies the necessary relationships. There are certain appropriate relations between the
+ participating elements. An element can communicate with other elements of the same kind. Control elements can
+ communicate with each of the other two kinds, but entities and boundary elements should not communicate directly.
+</p>
+<p>
+ This table shows appropriate links between design elements.
+</p>
+<table cellspacing="2" cellpadding="2" width="400" summary="Appropriate Links" border="1">
+ <tbody>
+ <tr>
+ <td>
+ </td>
+ <th scope="col">
+ <center>
+ Entity
+ </center>
+ </th>
+ <th scope="col">
+ <center>
+ Boundary
+ </center>
+ </th>
+ <th scope="col">
+ <center>
+ Control
+ </center>
+ </th>
+ </tr>
+ <tr>
+ <th scope="row">
+ Entity
+ </th>
+ <td>
+ <center>
+ X
+ </center>
+ </td>
+ <td>
+ </td>
+ <td>
+ <center>
+ X
+ </center>
+ </td>
+ </tr>
+ <tr>
+ <th scope="row">
+ Boundary
+ </th>
+ <td>
+ </td>
+ <td>
+ </td>
+ <td>
+ <center>
+ X
+ </center>
+ </td>
+ </tr>
+ <tr>
+ <th scope="row">
+ Control
+ </th>
+ <td>
+ <center>
+ X
+ </center>
+ </td>
+ <td>
+ <center>
+ X
+ </center>
+ </td>
+ <td>
+ <center>
+ X
+ </center>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<p>
+ By applying this pattern, you can put a robust design together that identifies the elements, behavior, and
+ relationships necessary to support a scenario.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/guidelines/example_design_mechanisms.xmi b/praclib/temp/core.tech.common.base/guidances/guidelines/example_design_mechanisms.xmi
new file mode 100644
index 0000000..2b80370
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/guidelines/example_design_mechanisms.xmi
@@ -0,0 +1,389 @@
+<?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: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="-mAo18f36rZ1R98kpZX7HMw"
+ name="new_guideline,_K32gYAoBEdu0OeEVPFogVA" guid="-mAo18f36rZ1R98kpZX7HMw" changeDate="2006-07-10T15:11:18.051-0700"
+ version="1.0.0">
+ <mainDescription><h3>
+ Design Mechanism Characteristics and Mapping
+</h3>
+<p>
+ Consider the analysis mechanism for <strong>persistence</strong>.
+</p>
+<ul>
+ <li>
+ There might be a need for many (2,000) small objects (200 bytes each) to be stored for a few seconds, with no need
+ for them to survive thereafter.
+ </li>
+ <li>
+ There might be a need for several very large objects to be stored permanently on disk for several months, never
+ updated, but with sophisticated means of retrieval.
+ </li>
+</ul>
+<p>
+ These objects require different support for persistency. The best option depends on the characteristics of the design
+ mechanism:
+</p>
+<ul>
+ <li>
+ <b>In-memory storag</b><strong>e:</strong> For up to 1 Mb total (size x volume); very fast access for read, write,
+ update.
+ </li>
+ <li>
+ <b>Flash card</b><strong>:</strong> For up to 8 Mb; slow update and write access; moderate read access.
+ </li>
+ <li>
+ <b>Binary file</b><strong>:</strong> For 100 Kb to 200 Mb; slow update; slow read-and-write access.
+ </li>
+ <li>
+ <b>Database management system (DBMS)</b><strong>:</strong> For 100 Kb and upward (essentially no upper limit); even
+ slower update and read-and-write access.
+ </li>
+</ul>
+<p>
+ Note that these speeds are rated as slow only as compared to in-memory storage. Obviously, in some environments,
+ caching can improve apparent access times. (See Figure 1.)
+</p>
+<blockquote>
+ <p align="center">
+ <img height="221" title="Figure 1. Mapping Analysis Mechanisms to Design Mechanisms and Classes"
+ alt="Mapping Analyis Mechanisms to Design Mechanisms and Classes" src="./resources/co_dmec1.gif" width="372" />
+ </p>
+</blockquote>
+<div align="center">
+ <p>
+ <strong>Figure 1. Mapping Analysis Mechanisms to Design Mechanisms and Classes</strong>
+ </p>
+ <h3 align="left">
+ Mapping Design Mechanisms to Implementation Mechanisms
+ </h3>
+ <p align="left">
+ The <b>persistence</b> design mechanisms can be mapped to implementation mechanisms as Figure 2 shows:
+ </p>
+ <p align="center">
+ <img height="216" title="Figure 2. How persistence design mechanism map to implementation mechanism"
+ alt="How persistence design mechanism map to implementation mechanism" src="./resources/co_dmec2.gif"
+ width="325" />
+ </p>
+ <p align="center">
+ <strong>Figure 2. How persistence design mechanism map to implementation mechanism</strong>
+ </p>
+ <p align="left">
+ A possible mapping between analysis mechanisms and design mechanisms. Dotted arrows mean "is specialized by,"
+ implying that the characteristics of the design mechanisms are inherited from the analysis mechanisms but that they
+ will be specialized and refined.
+ </p>
+ <p align="left">
+ After you have finished optimizing the mechanisms, the following mappings exist (see Figure 3):
+ </p>
+ <blockquote>
+ <p align="center">
+ <img height="110" title="Figure 3. Mapping structure after optimizing the mechanisms"
+ alt="Illustration of mapping structure after optimizing the mechanisms" src="./resources/co_dmec3.gif"
+ width="418" />
+ </p>
+ <p align="center" class="picturetext">
+ <strong>Figure 3. Mapping structure after optimizing the mechanisms</strong>
+ </p>
+ <p align="left" class="picturetext">
+ The design decisions for a client class in terms of mappings between mechanisms. The <font
+ face="Courier New, Courier, mono">Flight</font> class needs two forms of persistency<strong>:</strong>
+ <strong>in-memory storage</strong>, implemented by a predefined library routine, and <strong>a
+ database,</strong> implemented with an off-the-shelf ObjectStorage product.
+ </p>
+ </blockquote>
+ <p align="left">
+ The map must be navigable in both directions to make it easy to determine client classes when changing
+ implementation mechanisms.
+ </p>
+ <h4 align="left">
+ Refining the mapping between design and implementation mechanisms
+ </h4>
+</div>
+<p>
+ Initially, the mapping between design mechanisms and implementation mechanisms is likely to be less than optimal, but
+ it will get the project running, identify unforeseen risks, and trigger further investigations and evaluations. As the
+ project continues and you gain more knowledge, you will need to refine the mapping.
+</p>
+<p>
+ Proceed iteratively to refine the mapping between design and implementation mechanisms. Eliminate redundant paths,
+ working both top-down and bottom-up.
+</p>
+<p>
+ <b>Working top-down:</b> When working top-down (from top to bottom), new and refined use-case realizations will put new
+ requirements on the necessary design mechanisms through the analysis mechanisms that you need. These new requirements
+ might uncover additional characteristics of a design mechanism, forcing a split between mechanisms. A compromise
+ between the system's complexity and its performance is also necessary:
+</p>
+<ul>
+ <li>
+ Too many different design mechanisms make the system too complex.
+ </li>
+ <li>
+ Too few design mechanisms can create performance problems for implementation mechanisms that stretch the limits of
+ the reasonable ranges of the values of their characteristics.
+ </li>
+</ul>
+<p>
+ <b>Working bottom-up:</b> When working bottom-up (from bottom to top) and investigating the available implementation
+ mechanisms, you might find products that satisfy several design mechanisms at once, but force some adaptation or
+ repartitioning of your design mechanisms. You want to minimize the number of implementation mechanisms you use, but too
+ few of them can also lead to performance problems.
+</p>
+<p>
+ After you decide to use a DBMS to store class A objects, you might be tempted to use it to store all objects in the
+ system. This could be very inefficient or very cumbersome. Not all objects that require persistency need to be stored
+ in the DBMS. Some objects may be persistent, but one application may access them frequently, while other applications
+ access them only infrequently. A hybrid strategy, in which the object is read from the DBMS into memory and
+ periodically synchronized, may be the best approach.
+</p>
+<blockquote>
+ <p class="example">
+ <b>Example</b>
+ </p>
+ <p class="example">
+ A flight can be stored both in memory for fast access and in a DBMS for long-term persistency. However, this
+ triggers a need for a mechanism to synchronize both.
+ </p>
+</blockquote>
+<p>
+ It is not uncommon to have more than one design mechanism associated with a client class as a compromise between
+ different characteristics.
+</p>
+<p>
+ Because implementation mechanisms often come in bundles in off-the-shelf components (operating systems and middleware
+ products), some optimization based on cost, impedance mismatch, or uniformity of style needs to occur. Also, mechanisms
+ are often interdependent, which makes clear separation of services into design mechanisms difficult.
+</p>
+<blockquote>
+ <p class="example">
+ <b>Examples</b>
+ </p>
+ <ul>
+ <li>
+ The notification mechanism can be based on the inter-process communication mechanism.
+ </li>
+ <li>
+ The error reporting mechanism can be based on the persistency mechanism.
+ </li>
+ </ul>
+</blockquote>
+<p>
+ Refinement continues over the whole Elaboration phase, and is always a compromise between:
+</p>
+<ul>
+ <li>
+ An exact fit with the requirements of the clients of the design mechanism, in terms of the expected
+ characteristics.
+ </li>
+ <li>
+ The cost and complexity of having too many different implementation mechanisms to acquire and integrate.
+ </li>
+</ul>
+<p>
+ The overall goal is always to have a simple, clean set of mechanisms that give conceptual integrity, simplicity, and
+ elegance to a large system.
+</p>
+<h3>
+ Describing Design Mechanisms
+</h3>
+<p>
+ As with analysis mechanisms, design mechanisms can be modeled using a collaboration, which may instantiate one or more
+ architectural or design patterns (see <a class="elementLinkWithType"
+ href="./../../../legacy.legacy.obsoleted_from_openup/guidances/guidelines/using_patterns_31FFED10.html"
+ guid="_0cr7cACrEdu8m4dIntu6jA">Guideline: Using Patterns</a>).
+</p>
+<blockquote>
+ <p>
+ <strong>Example: A persistence mechanism</strong>
+ </p>
+ <p>
+ This example uses an instance of a pattern for RDBMS-based persistency drawn from <a
+ href="http://java.sun.com/products/jdbc/index.html" target="_blank"><u>Java&trade; Database Connectivity (JDBC)</u></a>.
+ Although we present the design here, JDBC supplies actual code for some of the classes. Therefore, it is a short
+ step from what is presented here to an implementation mechanism.
+ </p>
+</blockquote>
+<p>
+ Figure 4, titled <strong>JDBC: Static view,</strong> shows the classes (actually, the classifier roles) in the
+ collaboration.
+</p>
+<p align="center">
+ <img height="382" title="Figure 4. JDBC: Static View"
+ alt="Diagram of the figure titled Static View: JDBC shows the classes (actually, the classifier roles) in the collaboration. "
+ src="./resources/jdbc1.gif" width="571" />
+</p>
+<p align="center">
+ <strong>Figure 4. JDBC: Static view</strong>
+</p>
+<p align="left">
+ The yellow classes are the ones that were supplied. The others, in tan (<font
+ face="Courier New, Courier, mono">myDBClass</font> and so on), were bound by the designer to create the mechanism.
+</p>
+<p align="left">
+ In a Java database class, a client will work with a <b>DBClass</b> to read and write persistent data. The <font
+ face="Courier New, Courier, mono">DBClass</font> is responsible for accessing the JDBC database, using the
+ <b>DriverManager</b> class. Once a database <b>connection</b> is open, the <font
+ face="Courier New, Courier, mono">DBClass</font> can then create SQL statements that will be sent to the underlying
+ RDBMS and executed using the <b>Statement</b> class. The <font face="Courier New, Courier, mono">Statement</font> class
+ is what communicates with the database. The result of the SQL query is returned in a <b>ResultSet</b> object.<span
+ style="mso-spacerun: yes">&nbsp;</span>
+</p>
+<p align="left">
+ The <b>DBClass</b> is responsible for making another class instance persistent. It understands the OO-to-RDBMS mapping
+ and can interface with the RDBMS. The <font face="Courier New, Courier, mono">DBClass</font> flattens the object,
+ writes it to the RDBMS, and then reads the object data from the RDBMS and builds the object. Every class that is
+ persistent has a corresponding <font face="Courier New, Courier, mono">DBClass</font>.&nbsp;
+</p>
+<p align="left">
+ The <b>PersistentClassList</b> is used to return a set of persistent objects as a result of a database query, for
+ example: <font face="Courier New, Courier, mono">DBClass.read()</font>.
+</p>
+<p align="left">
+ A series of dynamic views follow, in Figures 5 thorough 9, to show how the mechanism actually works.
+</p>
+<p align="center">
+ <img height="146" title="Figure 5. JDBC: Initialize" alt="Diagram of JDBC: Initialize" src="./resources/jdbc2.gif"
+ width="285" />
+</p>
+<p align="center">
+ <b>Figure5. JDBC: Initialize</b>
+</p>
+<p>
+ Initialization must occur before any persistent class can be accessed.
+</p>
+<p>
+ To initialize the connection to the database, the <font face="Courier New, Courier, mono">DBClass</font> must load the
+ appropriate driver by calling the <font face="Courier New, Courier, mono">DriverManager getConnection()</font>
+ operation with a URL, user, and password.
+</p>
+<p>
+ The operation <font face="Courier New, Courier, mono">getConnection()</font> attempts to establish a connection to the
+ given database URL. The driver manager attempts to select an appropriate driver from the set of registered JDBC
+ drivers.
+</p>
+<blockquote>
+ <p>
+ <strong>Parameters</strong>
+ </p>
+ <blockquote>
+ <p>
+ <b>URL</b><strong>:</strong> A database URL in the form <font
+ face="Courier New, Courier, mono">jdbc:subprotocol:subname</font>. This URL is used to locate the actual
+ database server and is not Web-related, in this instance.
+ </p>
+ <p>
+ <b>user</b><strong>:</strong> The database user who is making the connection.
+ </p>
+ <p>
+ <b>pass</b><strong>:</strong> The user's password
+ </p>
+ </blockquote>
+ <p>
+ <strong>Returns</strong>
+ </p>
+ <blockquote>
+ <p>
+ A connection to the URL.
+ </p>
+ </blockquote>
+</blockquote>
+<p align="center">
+ <img height="253" title="Figure 6. JDBC: Create" alt="Diagram of JDBC: Crreate" src="./resources/jdbc3.gif"
+ width="478" />
+</p>
+<p align="center">
+ <b>Figure 6. JDBC: Create</b>
+</p>
+<p align="left">
+ To create a new class, the persistency client asks the <font face="Courier New, Courier, mono">DBClass</font> to create
+ the new class. The <font face="Courier New, Courier, mono">DBClass</font> creates a new instance of <font
+ face="Courier New, Courier, mono">PersistentClass</font> with default values. The <font
+ face="Courier New, Courier, mono">DBClass</font> then creates a new <font
+ face="Courier New, Courier, mono">Statement</font> using the <font face="Courier New, Courier, mono">Connection class
+ createStatement()</font> operation. The <font face="Courier New, Courier, mono">Statement</font> runs, and the data is
+ added to the database.
+</p>
+<p align="center">
+ <img height="352" title="Figure 7. JDBC: Read" alt="Diagram of JDBC: Read" src="./resources/jdbc4.gif" width="600" />
+</p>
+<p align="center">
+ <b>Figure 7. JDBC: Read</b>
+</p>
+<p>
+ To read a persistent class, the persistency client asks the <font face="Courier New, Courier, mono">DBClass</font> to
+ read. The <font face="Courier New, Courier, mono">DBClass</font> creates a new <font
+ face="Courier New, Courier, mono">Statement</font> using the <font face="Courier New, Courier, mono">Connection class
+ createStatement()</font> operation. The Statement is executed, and the data is returned in a <font
+ face="Courier New, Courier, mono">ResultSet</font> object. The <font face="Courier New, Courier, mono">DBClass</font>
+ then creates a new instance of the <font face="Courier New, Courier, mono">PersistentClass</font> and populates it with
+ the retrieved data. The data is returned in a collection object, an instance of the <font
+ face="Courier New, Courier, mono">PersistentClassList</font> class.
+</p>
+<p>
+ <strong>Note:</strong>
+</p>
+<p>
+ The string passed to <font face="Courier New, Courier, mono">executeQuery()</font> is not necessarily exactly the same
+ string as the one passed into the <font face="Courier New, Courier, mono">read()</font>. The <font
+ face="Courier New, Courier, mono">DBClass</font> will build the SQL query to retrieve the persistent data from the
+ database, using the criteria passed into the <font face="Courier New, Courier, mono">read()</font>. This is because it
+ is not useful for the client of the <font face="Courier New, Courier, mono">DBClass</font> to know the internal
+ structure of the database to create a valid query. This knowledge is encapsulated within <font
+ face="Courier New, Courier, mono">DBClass</font>.
+</p>
+<p align="center">
+ <img height="255" title="Figure 8. JDBC: Update" alt="Diagram of JDBC: Update" src="./resources/jdbc5.gif"
+ width="473" />
+</p>
+<p align="center">
+ <b>Figure 8. JDBC: Update</b>
+</p>
+<p>
+ To update a class, the persistency client asks the <font face="Courier New, Courier, mono">DBClass</font> to update.
+ The <font face="Courier New, Courier, mono">DBClass</font> retrieves the data from the given <font
+ face="Courier New, Courier, mono">PersistentClass</font> object, and creates a new <font
+ face="Courier New, Courier, mono">Statement</font> using the <font face="Courier New, Courier, mono">Connection class
+ createStatement()</font> operation. Once the <font face="Courier New, Courier, mono">Statement</font> is built, the
+ database is updated with the new data from the class.
+</p>
+<p>
+ <strong>Remember:</strong> It is the job of the <font face="Courier New, Courier, mono">DBClass</font> to flatten the
+ <font face="Courier New, Courier, mono">PersistentClass</font> and write it to the database. That is why it must be
+ retrieved from the given <font face="Courier New, Courier, mono">PersistentClass</font> before creating the SQL <font
+ face="Courier New, Courier, mono">Statement</font>.
+</p>
+<p>
+ <strong>Note:</strong>
+</p>
+<p>
+ In the above mechanism, the <font face="Courier New, Courier, mono">PersistentClass</font> must provide access routines
+ for all persistent data so that <font face="Courier New, Courier, mono">DBClass</font> can access them. This provides
+ external access to certain persistent attributes that would have been private otherwise. This is a price you have to
+ pay to pull the persistence knowledge out of the class that encapsulates the data.
+</p>
+<p align="center">
+ <img height="255" title="Figure 9. JDBC: Delete" alt="Diagram of JDBC: Delete" src="./resources/jdbc6.gif"
+ width="473" />
+</p>
+<p align="center">
+ <b>Figure 9. JDBC: Delete</b>
+</p>
+<p align="left">
+ To delete a class, the persistency client asks the <font face="Courier New, Courier, mono">DBClass</font> to delete the
+ <font face="Courier New, Courier, mono">PersistentClass</font>. The <font
+ face="Courier New, Courier, mono">DBClass</font> creates a new <font face="Courier New, Courier, mono">Statement</font>
+ using the <font face="Courier New, Courier, mono">Connection class createStatement()</font> operation. The <font
+ face="Courier New, Courier, mono">Statement</font> is executed and the data is removed from the database.
+</p>
+<p align="left">
+ In the actual implementation of this design, you would make some decisions about the mapping of <font
+ face="Courier New, Courier, mono">DBClass</font> to the persistent classes, such as having one <font
+ face="Courier New, Courier, mono">DBClass</font> per persistent class and allocating them to appropriate packages.
+ These packages will depend on the supplied java.sql file (see <a
+ href="http://java.sun.com/products/jdbc/index.jsp">JDBC: API Documentation</a>) package that contains the supporting
+ classes <font face="Courier New, Courier, mono">DriverManager, Connection, Statement</font>, and <font
+ face="Courier New, Courier, mono">ResultSet</font>.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/guidelines/layering.xmi b/praclib/temp/core.tech.common.base/guidances/guidelines/layering.xmi
new file mode 100644
index 0000000..fb29149
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/guidelines/layering.xmi
@@ -0,0 +1,142 @@
+<?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="_lbGQwMM3EdmSIPI87WLu3g"
+ name="layering,_0gpkAMlgEdmt3adZL5Dmdw" guid="_lbGQwMM3EdmSIPI87WLu3g" changeDate="2008-02-11T13:31:51.453-0500"
+ version="1.0.0">
+ <mainDescription><p>
+ Layering&nbsp; is&nbsp;one of the most&nbsp;commonly used&nbsp;approaches for structuring and decomposing systems.
+ Layering logically partitions the system into sets of components with certain rules regarding how relationships can be
+ formed between them. Layering provides a way to restrict inter-subsystem dependencies, with the result that the system
+ is more loosely coupled and more easily maintained.
+</p>
+<p>
+ Consider the number and purpose of the layers carefully. Do not over-complicate the solution by defining more layers
+ than are needed to meet the needs of the solution. More layers can always be added in the future to meet new
+ requirements. Removing layers is not always as easy and may introduce risks into the project.
+</p>
+<p>
+ The criteria for grouping elements into layers follows a few patterns:
+</p>
+<ul>
+ <li>
+ <b>Visibility</b><strong>:</strong> Elements may depend only on components in the same layer and the next-lower
+ layer.
+ </li>
+ <li>
+ <b>Volatility</b><strong>:</strong> 
+ <ul>
+ <li>
+ <b>In the highest layers</b>, put elements that vary when user requirements change.
+ </li>
+ <li>
+ <b>In the lowest layers</b>, put elements that vary when the implementation platform changes (hardware,
+ language, operating system, database, and so forth).
+ </li>
+ <li>
+ <strong>Sandwiched in the middle</strong>, put elements that are generally applicable across wide ranges of
+ systems and implementation environments.
+ </li>
+ <li>
+ <strong>Add layers</strong> when additional partitions within these broad categories help to organize the
+ model.
+ </li>
+ </ul>
+ </li>
+ <li>
+ <b>Generality</b><strong>:</strong> Abstract elements tend to be placed in the lower layers. If not
+ implementation-specific, they tend to gravitate toward the middle layers.
+ </li>
+ <li>
+ <b>Number of layers.</b> For a small system, three layers are typically sufficient.&nbsp;A three-layer architecture
+ of&nbsp;Presentation, Business, and Data layers is very common in information systems.&nbsp; For a complex system,
+ five to seven layers could be appropriate. For any degree of complexity, more than 10 layers should be viewed with
+ suspicion that increases with the number of layers.
+ </li>
+</ul>
+<p>
+ Failure to restrict dependencies according to the visibility criteria mentioned above can cause architectural
+ degradation and make the system difficult to extend and maintain.
+</p>
+<p>
+ Allowable exceptions to the visibility rule include cases where components need direct access to lower-layer services
+ beyond the next-lower layer. Make a decision about how to handle primitive services that are needed throughout the
+ system, such as printing, sending messages, and so forth. There is little value in restricting messages to lower layers
+ if the solution is to effectively implement call pass-throughs in the intermediate layers.&nbsp;&nbsp;This usage of a
+ less strict rule on dependencies down through the layers is sometimes called a Relaxed Layered Architecture (<a
+ class="elementlinkwithusertext"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/tech_references_6CCF393.html#BUS96"
+ guid="_9ToeIB83Edqsvps02rpOOg">[BUS96]</a>).
+</p>
+<h4>
+ <a id="PartitioningPatterns" name="PartitioningPatterns">Partitioning patterns</a>
+</h4>
+<p>
+ Within the top layers of the system, additional partitioning may help organize the model. The following guidelines for
+ partitioning present different issues to consider:
+</p>
+<p>
+ <b>User organization</b><strong>:</strong> Elements may be organized along lines that mirror the organization of
+ functionality in the business organization (partitioning occurs along departmental or user role lines). This
+ partitioning often occurs early in the design&nbsp;due to&nbsp;an existing enterprise model that is strongly
+ partitioned according to the structure of the organization. This pattern usually affects only the top few layers of
+ application-specific services and can often disappear as the design evolves.
+</p>
+<ul>
+ <li>
+ <p>
+ Partitioning along user-organization lines can be a good starting point for the model.
+ </p>
+ </li>
+ <li>
+ <p>
+ The structure of the user organization is not stable over a long period of time because business
+ reorganizations occur; therefore, it is not a good long-term basis for system partitioning. The internal
+ organization of the system should enable the system to evolve and be maintained independently of the
+ organization of the business that it supports.
+ </p>
+ </li>
+</ul>
+<p>
+ <b>Areas of competence and skills:</b> Elements may be organized to partition responsibilities among different groups
+ within the development organization. Typically, this occurs in the middle and lower layers of the system, and reflects
+ the need for specialization in skills during the development and support of an infrastructure based on complex
+ technology. Examples of such technologies include network and distribution management, database management,
+ communication management, and process control, among others. Partitioning along competence lines may also occur in
+ upper layers, where special competency in the problem domain is required to understand and support key business
+ functionality. Examples include telecommunication call management, securities trading, insurance claims processing, and
+ air traffic control, to name a few.
+</p>
+<p>
+ <b>System distribution:</b> Within any of the layers of the system, the layers may be further partitioned horizontally,
+ so to speak, to reflect the distribution of functionality.
+</p>
+<ul>
+ <li>
+ <p>
+ Partitioning to reflect distribution of functionality can help you visualize the network communication that
+ will occur as the system runs.
+ </p>
+ </li>
+ <li>
+ <p>
+ Partitioning to reflect distribution can also, however, make the system more difficult to change if the
+ deployment model changes significantly.
+ </p>
+ </li>
+</ul>
+<p>
+ <b>Secrecy areas</b><strong>:</strong> Some applications, especially those requiring special security clearance to
+ develop or support, require additional partitioning according to security access privileges. Software that controls
+ access to secrecy areas must be developed and maintained by personnel with appropriate clearance. If the number of
+ people with this background on the project is limited, the functionality requiring special clearance must be
+ partitioned into subsystems that will be developed independently from other subsystems, with the interfaces to the
+ secrecy areas the only visible aspect of these subsystems.
+</p>
+<p>
+ <b>Variability areas:</b> Functionality that is likely to be optional, and therefore delivered only in some variants of
+ the system, should be organized into independent components that are developed and delivered independently from the
+ mandatory functionality of the system.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/guidelines/maintaining_automated_test_suite.xmi b/praclib/temp/core.tech.common.base/guidances/guidelines/maintaining_automated_test_suite.xmi
new file mode 100644
index 0000000..8e3256d
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/guidelines/maintaining_automated_test_suite.xmi
@@ -0,0 +1,109 @@
+<?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: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="_8ngBgMPdEdmbOvqy4O0adg"
+ name="maintaining_automated_test_suite,_0kF5kMlgEdmt3adZL5Dmdw" guid="_8ngBgMPdEdmbOvqy4O0adg"
+ changeDate="2006-09-26T11:31:15.615-0700">
+ <mainDescription><h3>
+ Introduction
+</h3>
+<p>
+ At some point in your test effort, you may find it necessary to manage your test effort by creating test suites for
+ your test assets.&nbsp;Maintaining test suites can take many different forms. To facilitate your testing, you may want
+ to introduce some&nbsp;level of&nbsp;automation of your test suites.&nbsp;The fact that you've automated your test
+ suites does not necessarily make your testing easier however. It may actually increase the maintenance burden of your
+ suites.
+</p>
+<p>
+ This guideline introduces you to useful heuristics on how to facilitate the maintenance of your automated test suites.
+</p>
+<h4>
+ Plan your test&nbsp;suites
+</h4>
+<p>
+ Automating your testing without planning increases&nbsp;the chances that testing will be ineffective
+ and&nbsp;inefficient.&nbsp;Some level of planning should take place whether implicit or explicit.&nbsp;An essential
+ part of any test plan is the definition of a strategy for test automation.&nbsp;Use your plan to articulate to the
+ development team how you plan to maintain your test assets.&nbsp;In many cases, this is never done.&nbsp;The rest of
+ the development team may be unaware of how you intend to maintain your tests.&nbsp;It is also a good practice to get
+ the rest of the development team to understand that this maintenance can be a substantial part of the overall
+ development effort.&nbsp;Use your test tooling to capture this information and treat this plan just like you would
+ treat any other test asset in your test repository.
+</p>
+<h4>
+ Centrally locate your test assets
+</h4>
+<p>
+ To facilitate the maintenance of your automated test suites, locate your test assets in a repository that can be
+ accessed by the development team.&nbsp;Many test automation environments provide test management tools that make it
+ easier to organize and access your test assets by maintaining the test assets (test cases, test scripts, and test
+ suites) in a common repository.
+</p>
+<p>
+ In addition, some form of access control is enforced by the automation test tool.&nbsp;This eases the maintenance
+ burden by ensuring the integrity of your test suites.&nbsp;You may choose to grant stakeholders and managers read-only
+ access, whereas developers and testers at the practitioner level may have read/write access.
+</p>
+<h4>
+ Treat your test assets like any other software
+</h4>
+<p>
+ Software must be maintained.&nbsp;This also applies to the software in your test suites.&nbsp;Test cases and their
+ associated test scripts, whether recorded or programmed, should be maintained.&nbsp;And just as software has different
+ kinds of maintenance (e.g., corrective, preventative, or adaptive) so too do the assets in your automated test suites.
+ As you lifecycle your test suites, identify, if only informally,&nbsp;how&nbsp;you plan to disposition the test suite
+ corrective maintenance (e.g., syntactical errors in your scripts),&nbsp;preventative maintenance (e.g., where possible
+ to write generalized test scripts), and adaptive maintenance (e.g., how you&nbsp;can use your test tooling to re-assign
+ test&nbsp;assets within one suite to&nbsp;another suite or suites).&nbsp;This can be captured, as described in the
+ section <strong>Plan Your Test Suites</strong> above, in your test plan.
+</p>
+<h4>
+ Improve the testability of your test suites through collaboration with developers
+</h4>
+<p>
+ It's one thing to say that your test suites will need to be maintained due to changes in the application, changes in
+ the testing target, etc.&nbsp;It's quite another thing to actually determine whether a test suite needs to be
+ revamped&nbsp;and, if it does, what test assets within it need to be addressed.
+</p>
+<p>
+ One way to facilitate this is to use test suites as a way to communicate test decision to the developers.&nbsp;One way
+ to perform continuous perfective maintenance of test suites is to think of your test suites as assets that belong to
+ the development team rather than just the testers.&nbsp; You can perform a kind of perfective maintenance on test in
+ the following ways:
+</p>
+<ul>
+ <li>
+ use test suites to raise the level of abstraction
+ </li>
+ <li>
+ use test suites to provide focus for the developer
+ </li>
+ <li>
+ use test suites to articulate areas that the developers would like testers to focus on
+ </li>
+ <li>
+ make the construction and maintenance&nbsp;of test suites more efficient&nbsp;by understanding what area(s)
+ developers want to focus on
+ </li>
+ <li>
+ use test suites to clarify test targets with developers
+ </li>
+</ul>
+<h4>
+ Don't be afraid to clean up your suites
+</h4>
+<p>
+ Your test assets will evolve just as the application under test will.&nbsp;As requirements to the system change, the
+ application will change as well.&nbsp;To maintain your test suites, you should continually&nbsp;check whether test
+ assets are valid.&nbsp;If possible, validity checks should be performed after each new release of the software,
+ preferably more frequently.&nbsp;Keeping your test suites relevant is a full-time job.&nbsp;Assume that changes in the
+ software will lead to some degree of invalid tests within your test suites.&nbsp;Once these test assets have been
+ identified as invalid, get rid of them.&nbsp;This will make the maintenance burden much more tolerable.&nbsp;Some
+ automated test tooling environments make this task easier by providing ways to package outdated or invalid
+ tests.&nbsp;In some cases, you may not be absolutely sure whether you want to completely get rid of tests within your
+ test suite or even of getting rid of test suites altogether.&nbsp; To alleviate this burden, you can create packages
+ for obsolete tests or test suites and dispose of tests or test suites by putting them in packages labeled for this
+ purpose.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/guidelines/programming_automated_tests.xmi b/praclib/temp/core.tech.common.base/guidances/guidelines/programming_automated_tests.xmi
new file mode 100644
index 0000000..824971f
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/guidelines/programming_automated_tests.xmi
@@ -0,0 +1,78 @@
+<?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: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="_vuwC4MPcEdmbOvqy4O0adg"
+ name="programming_automated_tests,_0j5sUMlgEdmt3adZL5Dmdw" guid="_vuwC4MPcEdmbOvqy4O0adg"
+ changeDate="2006-12-07T13:06:38.445-0800" version="1.0.0">
+ <mainDescription><h3>
+ Introduction
+</h3>
+<p>
+ Although the programming of automated tests should contribute to the overall test effort, it usually does not make up
+ the entire test effort. In fact, test environments that are based on a complete automation approach end up spending
+ more time on test automation than on testing. Before you begin developing automated test scripts, consider first
+ whether it is more efficient to perform manual testing. Some aspects of an application are more efficiently tested
+ manually (for example, GUI testing versus data-drive testing). If you decide to program automated test scripts, examine
+ what aspects of your test scripting can be automated and begin designing your scripts.
+</p>
+<h3>
+ Design your automated tests
+</h3>
+<p>
+ Without some level of design of your automated tests, introducing automation into your testing effort can lead to more
+ problems than it solves. You should consider developing your automated tests according to a lifecycle with automation
+ test requirements, design, testing of the automation tests, and implementation of the automation tests. This approach
+ can be informal or formal depending on your project needs. By designing the programming of your automated tests, you
+ can avoid spending time programming the wrong tests, re-working programmed tests, deciphering different coding styles
+ in the programming of the tests, etc.
+</p>
+<h3>
+ Recorded versus programmed scripts
+</h3>
+<p>
+ Although there are clear benefits to recorded scripts (for example, ease of creation or ability for novice testers to
+ learn a scripting language), recorded scripts also present their own problems. The disadvantages of playback scripts
+ are well known. They are deceptively easy to create but very difficult to update. Problems with script reliability,
+ hard-coded data values, or changes to the application under test and the need to re-record are well-documented. On the
+ other hand, programming scripts can present difficulties of their own: they are difficult for the novice tester to
+ create, they can require substantial time and effort to develop, and they can be difficult to debug. Most test tooling
+ makes these issues less problematic by providing the tester script support functions, such as ways to establish target
+ of test lists, systematic ways to program verification point, point to datapools, build commands into the script (for
+ example, sleeper commands), comment the script, and document the script. Another major advantage, which is often
+ overlooked, of using testing tooling to mitigate these risks is the ability to add to an existing script in the form of
+ making corrections to an existing script, testing new features of a test target or application under test, or resuming
+ a recording after an interruption.
+</p>
+<h3>
+ Functional and performance test scripts
+</h3>
+<p>
+ When discussing automating test scripts, it is important to distinguish between functional and performance tests. Most
+ discussions of programming automated test scripts focus on testing the functionality of an application. This is not
+ inappropriate, since a lot of automated testing focuses on functional testing. Performance test scripting, however, has
+ its unique characteristics. Performance test automation provides you with the ability to programmatically set workloads
+ by adding user groups to test loads under group usage, setting think time behavior, running tests randomly or at set
+ rates, or setting the duration of a run. Performance test automation also allows you to create and maintain schedules
+ for your tests.
+</p>
+<h3>
+ Testing test scripts
+</h3>
+<p>
+ When testing your test scripts, keep in mind whether you are testing recorded or programmed test scripts. For recorded
+ scripts, much of the debugging of the script consists of errors that are introduced due to changes in the test target
+ or test environment. When you run a recorded test script, consider the test target of the script. Some test automation
+ tools capture this information as a part of the test script. Debugging a recorded script consists largely of
+ determining whether changes in the target have created error conditions in the script. In general, there are two main
+ categories to examine here: changes in the UI and test session sensitive data (for example, date stamped data). In most
+ cases, discrepancies between recording and playback cause errors in your recorded test scripts.
+</p>
+<p>
+ Testing programmed test scripts involves many of the same debugging techniques you would apply to debugging an
+ application. Consider both the flow control logic and the data aspects of your script. Automated testing tools provide
+ you with test script debugging IDEs as well as datapool management features that facilitate this type of testing.
+ During execution of test scripts, a test that uses a datapool can replace values in the programmed test with variable
+ test data that is stored in the datapool.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/guidelines/repres_interfaces_to_ext_systems.xmi b/praclib/temp/core.tech.common.base/guidances/guidelines/repres_interfaces_to_ext_systems.xmi
new file mode 100644
index 0000000..646bf66
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/guidelines/repres_interfaces_to_ext_systems.xmi
@@ -0,0 +1,24 @@
+<?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="_iCwb8MM3EdmSIPI87WLu3g"
+ name="repres_interfaces_to_ext_systems,_0gjdYMlgEdmt3adZL5Dmdw" guid="_iCwb8MM3EdmSIPI87WLu3g"
+ changeDate="2008-02-15T09:15:49.453-0500" version="1.0.0">
+ <mainDescription><p>
+ Interfaces with external systems should be consistently handled throughout the system, so markers need to be identified
+ in the architecture to make sure that the team develops the coherant software. The architecture need not include a
+ specific, detailed design for each system interface. It is often enough to simply identify the existence of the
+ interface as a significant part of the architecture and create a <a class="elementLink"
+ href="./../../../core.tech.common.base/guidances/concepts/component_CB167D48.html"
+ guid="_0YP18MlgEdmt3adZL5Dmdw">Component</a>&nbsp;to encapsulate the detail, so that it can be developed later.
+</p>
+<p>
+ The <a class="elementLink"
+ href="./../../../core.tech.common.base/guidances/guidelines/entity_control_boundary_pattern_C4047897.html"
+ guid="_uF-QYEAhEdq_UJTvM1DM2Q">Entity-Control-Boundary Pattern</a>&nbsp;provides the basis for a useful technique to
+ support this.&nbsp;Specifically, if the system communicates with another system, define one or more components to
+ describe the communication protocol.&nbsp; The use of a component allows the interface to the external system to be
+ defined and stabilized, while leaving the design details of the system interface hidden as the system evolves.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/guidelines/req_gathering_techniques.xmi b/praclib/temp/core.tech.common.base/guidances/guidelines/req_gathering_techniques.xmi
new file mode 100644
index 0000000..09309a4
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/guidelines/req_gathering_techniques.xmi
@@ -0,0 +1,354 @@
+<?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="_On0agNSAEdmLhZ9H5Plxyw"
+ name="req_gathering_techniques,_OnoNQNSAEdmLhZ9H5Plxyw" guid="_On0agNSAEdmLhZ9H5Plxyw"
+ changeDate="2006-09-22T07:27:44.000-0700" version="7.2.0">
+ <mainDescription><h3>
+ Sources of Requirements
+</h3>
+<p>
+ Good requirements start with good sources. Finding those quality sources is an important task and, fortunately, one
+ that&nbsp;takes few&nbsp;resources. Examples of sources of requirements include:
+</p>
+<ul>
+ <li>
+ Customers
+ </li>
+ <li>
+ Users
+ </li>
+ <li>
+ Administrators and maintenance&nbsp;staff
+ </li>
+ <li>
+ Partners
+ </li>
+ <li>
+ Domain Experts
+ </li>
+ <li>
+ Industry Analysts
+ </li>
+ <li>
+ Information about competitors&nbsp;
+ </li>
+</ul>
+<h3>
+ Requirements Gathering Techniques
+</h3>
+<p>
+ After you have identified these sources, there are a number of techniques that may be used to gather requirements. The
+ following will describe the various techniques, followed by a brief discussion of when to use each technique.
+</p>
+<p>
+ To get the requirements down on paper, you&nbsp;can to do one or more of the following:
+</p>
+<ul>
+ <li>
+ Conduct a brainstorming session
+ </li>
+ <li>
+ Interview users
+ </li>
+ <li>
+ Send questionnaires
+ </li>
+ <li>
+ Work in the target environment
+ </li>
+ <li>
+ Study analogous systems
+ </li>
+ <li>
+ Examine suggestions and problem reports
+ </li>
+ <li>
+ Talk to support teams
+ </li>
+ <li>
+ Study improvements made by users
+ </li>
+ <li>
+ Look at unintended uses
+ </li>
+ <li>
+ Conduct workshops
+ </li>
+ <li>
+ Demonstrate prototypes to stakeholders
+ </li>
+</ul>
+<p>
+ The best idea is to get the requirements down quickly and then to encourage the users to correct and improve them. Put
+ in those corrections, and repeat the cycle. Do it now, keep it small, and correct it at once. Start off with the best
+ structure you can devise, but expect to keep on correcting it throughout the process.&nbsp; Success tips: Do it now,
+ keep it small, and correct it immediately.
+</p>
+<h4>
+ Conduct a brainstorming session
+</h4>
+<p>
+ Brainstorming is a short group session where everyone is allowed to say whatever they feel is important to the topic of
+ discussion. After that, a facilitator leads the group in organizing and prioritizing the results.&nbsp; The following
+ basic rules for brainstorming&nbsp;ensures better results:
+</p>
+<ul>
+ <li>
+ Start out by clearly stating the objective of the brainstorming session.
+ </li>
+ <li>
+ Generate as may ideas as possible.
+ </li>
+ <li>
+ Let your imagination soar.
+ </li>
+ <li>
+ Do not allow criticism or debate while you are gathering information.
+ </li>
+ <li>
+ Once information is gathered,&nbsp;reshape and combine ideas.
+ </li>
+</ul>
+<h4>
+ Interview users
+</h4>
+<p>
+ Face-to-face contact with users through individual interviewing is the primary source of requirements and an important
+ way you gather and validate their requirements. Remember that it is not the only possible technique, and that you can
+ conduct interviews many different ways. Develop a repertoire of styles to&nbsp;fit different situations. Unless you use
+ the system yourself, you will need to make an effort to understand and experience the user's problem to describe it
+ clearly and correctly.
+</p>
+<h4>
+ Send Questionnaires
+</h4>
+<p>
+ If face-to-face meetings are possible, they are always preferable, because they provide a better means of uncovering
+ the problem behind the problem. Sometimes, though,&nbsp;face-to-face meetings with stakeholders are not feasible (when
+ developing products for the consumer market, for example). In those situations, consider using questionnaires.&nbsp;
+ Send a set of questions, possibly with multiple choice responses, to the relevant stakeholders, and ask them to
+ complete it and return it to you.&nbsp; Success&nbsp;tips: Keep it short and given them a deadline.&nbsp;
+</p>
+<p>
+ This technique has the advantage of providing a lot of information for statistical analysis. However, the questions
+ must be well designed to be clear and to avoid so-called "leading questions", which bias the responses.&nbsp;
+</p>
+<h4>
+ Work in the target environment
+</h4>
+<p>
+ Experience the work of the users for yourself. Working with users helps you understand problems that have resisted
+ previous solutions. Familiar systems developed in this way inevitably include tools for programmers, such as
+ interactive editors and compilers, as the developers naturally have both the expertise in the subject area, and the
+ desire to solve their own problems. It would be good to see the same dedication devoted to solving problems in other
+ areas too. Where the work cannot easily be experienced in this way, it may still be possible to do a bit more than just
+ sit quietly and observe. Users can give you a commentary on what they are doing, what the problems are, and what they
+ would like to have to make the work easier.
+</p>
+<h4>
+ Study analogous systems
+</h4>
+<p>
+ The starting point for many projects is often a similar or an existing system. Sometimes, comparable products and
+ systems contain working versions of good ideas for solving user problems. You can save the time lost in reinventing the
+ wheel by looking at systems already on the market, whether they are systems installed at the user's site or products
+ made by rival organizations. Even if they are trying to solve slightly different problems, they often&nbsp;provide
+ valuable clues as to what you need to do.
+</p>
+<p>
+ Listen when a customer asks why a product couldn't do something that the customer wants, and keep a list of these
+ suggestions. Later, use it to start discussions with other users. You should be able to obtain some requirements
+ directly this way. If not, capture and store suggestions for future use.
+</p>
+<p>
+ You can describe to users selected features of other products. Explain that the system is designed for&nbsp;another
+ purpose&nbsp;but contains an interesting feature, and you wonder it or something similar&nbsp;would help them.
+ Sometimes these systems are described in documents, such as a contract from another organization or a report written
+ for management. Often, these documents were never intended as formal requirements, and were written merely to
+ communicate a stream-of-consciousness idea. Define a process of going from disorganized to organized information.
+</p>
+<p>
+ Such a process might involve the following activities:
+</p>
+<ul>
+ <li>
+ Read the document from end to end (several times) to comprehend what the customer wants and what actually has been
+ written.
+ </li>
+ <li>
+ Classify all of the types of information in the document. (user, system requirements, design elements, plans,
+ background material, irrelevant detail)
+ </li>
+ <li>
+ Mark up the original text to separate out such requirements.
+ </li>
+ <li>
+ Find a good structure for each of the different types of information such as: a scenario for the user requirements,
+ functional breakdown for the system requirements, and architecture for the design.
+ </li>
+ <li>
+ Organize the information to show gaps and overlaps. Feel free to add missing elements, but confirm these decisions
+ with the users.
+ </li>
+ <li>
+ Create traceability links between these information elements to show the designers exactly what the users want.
+ </li>
+ <li>
+ Convince the customer to accept the new information as the basis for the contract.
+ </li>
+</ul>
+<h4>
+ Examine suggestions and problem reports
+</h4>
+<p>
+ Requirements can come from change suggestions and user problems. A direct road to finding requirements is to look at
+ suggestions and problems as first described. Most organizations have a form for reporting system problems or software
+ defects. You can ask to look through the reports (and there will probably be many). Sort them into groups so you can
+ identify the key areas that are troubling users. Ask users some questions about these areas to clarify the users'
+ actual needs.
+</p>
+<h4>
+ Talk to support teams
+</h4>
+<p>
+ Most large sales organizations have a help desk that keeps a log of problems and fixes, and support engineers who do
+ the fixing. Many organizations have similar facilities to support their own operations. Talking to the help desk staff
+ and the support engineers may give you good leads into the requirements, and save you time. Also talk to the training
+ team and installation teams about what users find to be&nbsp;difficult.
+</p>
+<h4>
+ Study improvements made by users
+</h4>
+<p>
+ This is an excellent source of requirements. Users of a standard company spreadsheet may have added a few fields, or
+ related different sheets together, or drawn a graph, that exactly meets their individual needs. You need only ask: Why
+ did you add that? Their answers help you&nbsp;get to the heart of the actual requirement. This applies also to hardware
+ and non-computer devices. For example, a lathe operator may have manufactured a special clamp, or an arm that prevents
+ movement of the tool beyond a certain point. Any such modification points to something wrong with the existing product,
+ which makes it&nbsp;a valid&nbsp;requirement for the new version.
+</p>
+<h4>
+ Look at unintended uses
+</h4>
+<p>
+ People often use things for purposes for which they were not designed.&nbsp; This is&nbsp;a good way to get new ideas
+ and to think of innovations. For example, an observant product manager noticed that an engineer was staying in the
+ office late to use an advanced computer-aided design system to design a new kitchen layout for his home. Inexpensive
+ commercial products are now widely available for home use.
+</p>
+<h4>
+ Conduct workshops
+</h4>
+<p>
+ Workshops can rapidly pull together a good set of requirements. In two to five days, you can create a set of
+ requirements, and then review and improve them. If everyone in a workshop tries to estimate the cost and value of each
+ requirement, the document becomes much more useful and cost-effective.
+</p>
+<p>
+ Workshops are quicker and better at discovering requirements than other techniques, such as sending questionnaires. You
+ are bringing the right collection of people together, and getting them to correct and improve on their requirements
+ document.
+</p>
+<p>
+ A workshop is inherently expensive because of the number of people involved, but it saves a large amount of time. If
+ you can define the product right the first time and cut three months off the requirements gathering, the savings could
+ be enormous. The workshop has to be thoroughly organized to take advantage of people's time.
+</p>
+<p>
+ Choose a quiet location for the workshop so that people are not disturbed by day-to-day business. Mobile phones should
+ be discouraged; arrange to take messages externally. Take advantage of informal interactions by choosing a site so that
+ people don't go home at night or go out separately. The example&nbsp;in Figure 1&nbsp;shows the logic of a requirements
+ workshop. Note that the workshop provides the environment in which to apply other requirements-gathering techniques
+ such as brainstorming.
+</p>
+<p>
+ <img height="381" alt="" src="./resources/Workshop%20Activity%20Diagram.GIF" width="542" />
+</p>
+<p>
+ <strong>Figure 1: Conducting Workshops</strong>
+</p>
+<h4>
+ Demonstrate prototypes to stakeholders
+</h4>
+<p>
+ Prototypes allow us to immediately see some aspects of the system. Showing users a simple prototype can
+ provoke&nbsp;them into giving good requirements information or changing their mind about existing requirements. The
+ techniques described here help you gather ideas for requirements. Prototypes and models are an excellent way of
+ presenting ideas to users. They can illustrate how an approach might work, or give users a glimpse of what they might
+ be able to do. More requirements are likely to emerge when users see what you are suggesting.
+</p>
+<p>
+ A presentation can use a sequence of slides, storyboard, an artist's impression, or even an animation to give users a
+ vision of the possibilities. When prototyping software, make a mock-up of the user interface screens, emphasizing that
+ there is no code and that the system has not been designed or even specified yet (fair warning: there are dangers here
+ for the unwary).
+</p>
+<p>
+ This prototyping aims to get users to express (missing) requirements. You are not trying to sell users an idea or
+ product, you are finding out what they actually want. Seeing a prototype, which invariably is wrong in some ways and
+ right in others, is a powerful stimulus to users to start saying what they want. They may point out plenty of problems
+ with the prototype! This is excellent,&nbsp;because each problem leads to a new requirement.
+</p>
+<h3>
+ Which Technique to Apply?
+</h3>
+<p>
+ Which technique to apply depends on a number of factors, such as:
+</p>
+<ul>
+ <li>
+ Availability and location of stakeholders
+ </li>
+ <li>
+ Development team knowledge of the problem domain
+ </li>
+ <li>
+ Customers' and users' knowledge of the problem domain
+ </li>
+ <li>
+ Customers' and users' knowledge of the development process and methods
+ </li>
+</ul>
+<p>
+ If the stakeholders are not co-located or readily available, for example in the case of a product being developed for
+ mass market,&nbsp;techniques such as brainstorming, interviews and workshops that require face-to-face contact with the
+ stakeholders may be difficult or impossible.
+</p>
+<p>
+ If the stakeholders are available for face-to-face meetings, this is a much better situation and almost all of the
+ techniques described, or combination of them, may be applied. In this case, the domain and development experience of
+ oth the stakeholders and the development team are critical factors in selecting the appropriate technique.
+</p>
+<p>
+ Figure 2, adapted from <a
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/references_6CCF393.html"
+ guid="_9ToeIB83Edqsvps02rpOOg">[HIC03]</a>, provides a framework for determining the appropriate techniques. It defines
+ four main categories of customer or user experience and development team experience: "Fuzzy problem",
+ "Selling/Teaching", "Catch up", and "Mature".
+</p>
+<p>
+ <img height="470" alt="" src="./resources/Which%20Req%20Gathering%20Technique.gif" width="514" />
+</p>
+<p>
+ <strong>Figure 2: Selection of Techniques</strong>
+</p>
+<p>
+ There is no "right answer", but these guidelines may help you decide which method to use:
+</p>
+<ul>
+ <li>
+ Catch-up: Interviews, work in target environment
+ </li>
+ <li>
+ Fuzzy: Brainstorming, workshops
+ </li>
+ <li>
+ Mature: Questionnaires, workshops, prototypes
+ </li>
+ <li>
+ Selling/Teaching: prototypes
+ </li>
+</ul></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/guidelines/requirement_pitfalls.xmi b/praclib/temp/core.tech.common.base/guidances/guidelines/requirement_pitfalls.xmi
new file mode 100644
index 0000000..a2a8242
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/guidelines/requirement_pitfalls.xmi
@@ -0,0 +1,257 @@
+<?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="-Q72-dNdHnZ93aRXAB_d34A"
+ name="requirement_pitfalls_1,_1AOsMO0JEdqHTdbLTmC5IQ" guid="-Q72-dNdHnZ93aRXAB_d34A"
+ authors="Chris Sibbald" changeDate="2006-09-27T10:14:43.000-0700" version="0.2">
+ <mainDescription><p>
+ Explanations and examples follow for each of the following common pitfalls to avoid in defining and writing
+ requirements (for more information, see <a
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/references_6CCF393.html"
+ guid="_9ToeIB83Edqsvps02rpOOg">[TEL06]</a>):
+</p>
+<ul>
+ <li>
+ Avoid ambiguity
+ </li>
+ <li>
+ Don't make multiple requirements
+ </li>
+ <li>
+ Never use let-out or escape words
+ </li>
+ <li>
+ Don't ramble
+ </li>
+ <li>
+ Resist designing the system
+ </li>
+ <li>
+ Avoid mixing different kinds of requirements
+ </li>
+ <li>
+ Do not speculate
+ </li>
+ <li>
+ Do not use vague, undefined terms
+ </li>
+ <li>
+ Do not express possibilities
+ </li>
+ <li>
+ Avoid wishful thinking
+ </li>
+</ul>
+<h4>
+ Avoid ambiguity
+</h4>
+<p>
+ Avoidance of ambiguity is one of the subtlest and most difficult issues in writing requirements. Try to write as
+ clearly and explicitly as possible. Be specific. Remember, though, that if you carry this too far, the text becomes
+ dull and unreadable, which makes it difficult for other people to review. Although this guideline emphasizes
+ structured, written expression of requirements, informal text, diagrams, conversations, and phone calls are excellent
+ ways of removing ambiguity.
+</p>
+<p>
+ Some constructions (such as the use of or and unless in requirements) allow different groups of readers to understand
+ different things from the same wording. Developers could use this technique deliberately, so as to postpone, until too
+ late, any possibility of the customer's asking for what was truly wanted. This is dangerous and could easily backfire.
+</p>
+<p>
+ The only approach that works is for developers to make requirements as clear as possible, and for all stakeholders to
+ co-operate. In the long run, project success is in everybody's interest.
+</p>
+<p>
+ Dangerous ambiguities can be caused by the word <strong>or</strong> and also by many more-subtle errors.
+</p>
+<h5>
+ Example
+</h5>
+<p>
+ <em>The same subsystem shall also be able to generate a visible or audible caution/warning signal for the attention of
+ the co-pilot or navigator.</em>
+</p>
+<p>
+ Which subsystem? Is the signal to be visible, audible, or both? Is it both caution and warning, just caution, or just
+ warning? Is it for both the co-pilot and the navigator, or just one of them? If just one of them, which one and under
+ what conditions?
+</p>
+<h4>
+ Don't make multiple requirements
+</h4>
+<p>
+ Requirements which contain conjunctions (words that join independent clauses together) are dangerous. Problems arise
+ when readers try to figure out which part applies, especially if the different clauses seem to conflict, or if the
+ individual parts apply separately. Multiple requirements also make verification more complex.
+</p>
+<p>
+ Dangerous conjunctions include: and, or, but
+</p>
+<h5>
+ Example
+</h5>
+<p>
+ <em>The battery low warning lamp shall light up when the voltage drops below 3.6 Volts, and the current workspace or
+ input data shall be saved.</em>
+</p>
+<p>
+ Should the battery low warning lamp light up when the voltage drops and the workspace is saved? Should the battery low
+ warning lamp light up and the workspace be saved when the voltage drops?
+</p>
+<h4>
+ Never use let-out or escape words
+</h4>
+<p>
+ Requirements that include options or exceptions are dangerous. They seem to ask for something definite, but at the last
+ moment they back down and allow for other options. Problems arise when the requirements are to be tested, and someone
+ has to decide what (if anything) could prove the requirement was met.
+</p>
+<p>
+ Dangerous words that imply exceptions include: if, when, but, except, unless, although.
+</p>
+<h5>
+ Examples
+</h5>
+<p>
+ <em>The forward passenger doors shall open automatically when the aircraft has halted, except when the rear ramp is
+ deployed.</em>
+</p>
+<p>
+ <em>The fire alarm shall always be sounded when smoke is detected, unless the alarm is being tested or the engineer has
+ suppressed the alarm.</em>
+</p>
+<p>
+ The latter sentence is a truly dangerous requirement!
+</p>
+<h4>
+ Don't ramble
+</h4>
+<p>
+ Long rambling sentences, especially when combined with arcane language, references to unreachable documents, and other
+ defects of writing, quickly lead to confusion and error.
+</p>
+<h5>
+ Example
+</h5>
+<p>
+ <em>Provided that the designated input signals from the specified devices are received in the correct order where the
+ system is able to differentiate the designators, the output signal shall comply with the required framework of section
+ 3.1.5 to indicate the desired input state.</em>
+</p>
+<h4>
+ Resist designing the system
+</h4>
+<p>
+ Requirements should specify the design envelope without unnecessary constraints on a specific design. If we supply too
+ much detail we start to design the system. Going too far is tempting for designers, especially when they come to their
+ favorite bits.
+</p>
+<p>
+ Danger signs include names of components, materials, software objects/procedures, and database fields.
+</p>
+<h5>
+ Example
+</h5>
+<p>
+ <em>The antenna shall be capable of receiving FM signals, using a copper core with nylon covering and a waterproof
+ hardened rubber shield.</em>
+</p>
+<p>
+ Specifying design rather than actual need increases the cost of systems by placing needless constraints on development
+ and manufacture. Often knowing why is much better than knowing what.
+</p>
+<h4>
+ Avoid mixing different kinds of requirements
+</h4>
+<p>
+ The user requirements form a complete model of what users want. They need to be organized coherently to show gaps and
+ overlaps. The same applies to system requirements, which form a complete functional model of the proposed system. A
+ quick road to confusion is to mix up requirements for users, systems, and how the system should be designed, tested, or
+ installed.
+</p>
+<p>
+ Danger signs are any references to system, design, testing, or installation.
+</p>
+<h5>
+ Example
+</h5>
+<p>
+ <em>The user shall be able to view the currently selected channel number which shall be displayed in 14pt Swiss type on
+ an LCD panel tested to Federal Regulation Standard 567-89 and mounted with shockproof rubber washers.</em>
+</p>
+<h4>
+ Do not speculate
+</h4>
+<p>
+ Requirements are part of a contract between customer and developer. There is no room for wish lists, meaning general
+ terms about things that somebody probably wants.
+</p>
+<p>
+ Danger signs include vagueness about which type of user is speaking, and generalization such as: usually, generally,
+ often, normally, typically
+</p>
+<h5>
+ Example
+</h5>
+<p>
+ <em>Users normally require early indication of intrusion into the system.</em>
+</p>
+<h4>
+ Do not use vague, undefined terms
+</h4>
+<p>
+ Many words used informally to indicate system quality are too vague for use in requirements. Vague terms include, among
+ others: user-friendly, versatile, flexible, approximately, as possible
+</p>
+<p>
+ Requirements using these terms are unverifiable because there is no definite test to show whether the system has the
+ indicated property.
+</p>
+<h5>
+ Examples
+</h5>
+<p>
+ <em>The print dialog shall be versatile and user-friendly.</em>
+</p>
+<p>
+ <em>The OK status indicator lamp shall be illuminated as soon as possible after the system self-check is
+ completed.</em>
+</p>
+<h4>
+ Do not express possibilities
+</h4>
+<p>
+ Suggestions that are not explicitly stated as requirements are invariably ignored by developers.
+</p>
+<p>
+ "Possible options" are indicated with terms such as: may, might, should, ought, could, perhaps, probably
+</p>
+<h5>
+ Example
+</h5>
+<p>
+ <em>The reception subsystem probably ought to be powerful enough to receive a signal inside a steel-framed
+ building.</em>
+</p>
+<h4>
+ Avoid wishful thinking
+</h4>
+<p>
+ Engineering is a real-world activity. No system or component is perfect. Wishful thinking means asking for the
+ impossible.
+</p>
+<p>
+ Wishful-thinking terms include: reliable, safe, handle all unexpected failures, please all users, run on all platforms,
+ never fail, upgradeable to all future situations
+</p>
+<h5>
+ Examples
+</h5>
+<p>
+ <em>The gearbox shall be 100% safe in normal operation.</em>
+</p>
+<p>
+ <em>The network shall handle all unexpected errors without crashing.</em>
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/guidelines/resources/Which Req Gathering Technique.gif b/praclib/temp/core.tech.common.base/guidances/guidelines/resources/Which Req Gathering Technique.gif
new file mode 100644
index 0000000..10b6366
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/guidelines/resources/Which Req Gathering Technique.gif
Binary files differ
diff --git a/praclib/temp/core.tech.common.base/guidances/guidelines/resources/Workshop Activity Diagram.GIF b/praclib/temp/core.tech.common.base/guidances/guidelines/resources/Workshop Activity Diagram.GIF
new file mode 100644
index 0000000..228f102
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/guidelines/resources/Workshop Activity Diagram.GIF
Binary files differ
diff --git a/praclib/temp/core.tech.common.base/guidances/guidelines/resources/ebc_diagram.JPG b/praclib/temp/core.tech.common.base/guidances/guidelines/resources/ebc_diagram.JPG
new file mode 100644
index 0000000..67970fe
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/guidelines/resources/ebc_diagram.JPG
Binary files differ
diff --git a/praclib/temp/core.tech.common.base/guidances/guidelines/resources/icon_introL.gif b/praclib/temp/core.tech.common.base/guidances/guidelines/resources/icon_introL.gif
new file mode 100644
index 0000000..1826cbd
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/guidelines/resources/icon_introL.gif
Binary files differ
diff --git a/praclib/temp/core.tech.common.base/guidances/guidelines/resources/mic.gif b/praclib/temp/core.tech.common.base/guidances/guidelines/resources/mic.gif
new file mode 100644
index 0000000..0b316db
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/guidelines/resources/mic.gif
Binary files differ
diff --git a/praclib/temp/core.tech.common.base/guidances/guidelines/resources/wil_overview.bmp b/praclib/temp/core.tech.common.base/guidances/guidelines/resources/wil_overview.bmp
new file mode 100644
index 0000000..920106d
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/guidelines/resources/wil_overview.bmp
Binary files differ
diff --git a/praclib/temp/core.tech.common.base/guidances/guidelines/software_reuse.xmi b/praclib/temp/core.tech.common.base/guidances/guidelines/software_reuse.xmi
new file mode 100644
index 0000000..743a3db
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/guidelines/software_reuse.xmi
@@ -0,0 +1,243 @@
+<?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="-Vp61zQMUoP-Icm5jgDar7A"
+ name="new_guideline,_vO2uoO0OEduUpsu85bVhiQ" guid="-Vp61zQMUoP-Icm5jgDar7A" changeDate="2008-02-15T08:30:27.031-0500"
+ version="1.0.0">
+ <mainDescription><p>
+ Maximizing reuse has always been an important goal of software development. It's better to re-use than to expend the
+ cost of creating something new, testing it, and releasing it for the first time with the risk of hidden problems that
+ all new software has. Languages, particularly object-oriented ones, have been developed to make reuse easier. But a
+ language alone isn't enough to provide cost effective reuse. The bulk of reusable software comes from skilled
+ developers and architects who are able to identify and leverage reuse opportunities.
+</p>
+<h3>
+ What is a Reusable Asset?
+</h3>
+<p>
+ The following are some examples of reusable software assets:
+</p>
+<ul>
+ <li>
+ Architectural frameworks
+ </li>
+ <li>
+ Architectural mechanisms
+ </li>
+ <li>
+ Architectural decisions
+ </li>
+ <li>
+ Constraints
+ </li>
+ <li>
+ Applications
+ </li>
+ <li>
+ Components
+ </li>
+ <li>
+ COTS software&nbsp;
+ </li>
+</ul>
+<h3>
+ Identifying Reuse Opportunities
+</h3>
+<p>
+ There are three perspectives to look at when reusing software: code (implementation), design, and framework or
+ architecture.&nbsp; Architects should look to reuse significant application frameworks such as layers that can be
+ applied to many different types of applications (for more information, see <a class="elementLinkWithType"
+ href="./../../../core.tech.common.base/guidances/guidelines/layering_F169CF07.html"
+ guid="_0gpkAMlgEdmt3adZL5Dmdw">Guideline: Layering</a>. Developers should look to designs and <a class="elementLink"
+ href="./../../../core.tech.common.base/guidances/concepts/pattern_10BE6D96.html"
+ guid="_0YJvUMlgEdmt3adZL5Dmdw">Pattern</a>s that can be reused to produce desired behavior or robust structures. They
+ should also look at how to reduce the amount of code that needs to be written by leveraging stable components and code
+ that has been proven in production environments.
+</p>
+<p>
+ The best way to enable a team to find opportunities for reuse is to exercise excellent design and coding practices.
+ It's difficult to find code and design that can be reused when dealing with large classes, classes that don't have a
+ clearly defined focus, or classes with relationships that are difficult to understand. Classes should be small, easy to
+ understand, and highly cohesive to make it easier to identify reuse opportunities. Any functionality that can be
+ reasonably separated into another class should be. Another way of saying this is that any concept that could be applied
+ to more than one type of class should be its own class.
+</p>
+<p>
+ For example, if some calculations are added to an existing class, it may make sense to then refactor those calculations
+ into a new helper class. Those calculations can&nbsp;then be re-used in any number of other classes without the burden
+ of having to know about the functionality of the original class.
+</p>
+<p>
+ The simplest but least efficient way to identify reuse opportunities is to "smell" similar code. A developer may recall
+ doing something similar to what they're designing or implementing now. Once the previous implementation has been
+ discovered or recalled it can be reused. Developers will always find reuse opportunities this way. But the unstructured
+ nature of it won't maximize the potential areas for reuse.
+</p>
+<p>
+ Collaboration is a good technique for identifying reuse opportunities. It provides a structure where identifying reuse
+ - instead of writing code - is the goal of the exercise. And the more brains that are looking for reuse opportunities,
+ the more likely it is that they'll be found. A brainstorming or review meeting that focuses on identifying reuse
+ opportunities would be useful to support this.
+</p>
+<p>
+ Patterns are good ways to find reuse opportunities in designs and frameworks. See <a class="elementLinkWithType"
+ href="./../../../core.tech.common.base/guidances/concepts/pattern_10BE6D96.html"
+ guid="_0YJvUMlgEdmt3adZL5Dmdw">Concept: Pattern</a>&nbsp;for more information.
+</p>
+<p>
+ Analyzing behavior is another good way to identify potential areas for reuse. Analyze how classes need to collaborate
+ in order to deliver some specific functionality such as a requirement or feature. This collaboration can be documented
+ in sequence (behavior) and class (structure) diagrams and can be reused in similar circumstances.
+</p>
+<p>
+ After looking for similar behavior and returned values, then look for similarity of parameters. If their
+ interfaces&nbsp;are not an exact match for the component interfaces being proposed, you can modify the
+ proposed&nbsp;signatures to increase the degree of reuse. Some design mechanisms, such as performance or security
+ requirements, may disqualify a component from reuse even when there is&nbsp;a perfect match between operation
+ signatures.
+</p>
+<p align="left">
+ A common set of components may exist that provides many of the <a class="elementLink"
+ href="./../../../core.tech.common.base/guidances/concepts/arch_mechanism_2932DFB6.html"
+ guid="_mzxI0A4LEduibvKwrGxWxA">Architectural Mechanism</a> that you need&nbsp;for the new system. These components may
+ be available either because they were developed or purchased previously for&nbsp;similar systems. Given their
+ suitability and compatibility within the software architecture, there may be a need to reverse-engineer these
+ components to represent them in a design model and reuse them in a project.
+</p>
+<p align="left">
+ Similar thinking applies to&nbsp;existing databases. Part of the information to be used by the application under
+ development may already reside in a database. You may be able to get the classes that represent the database structures
+ that hold this information by reverse-engineering the database.
+</p>
+<p>
+ <a class="elementLink" href="./../../../core.tech.common.base/guidances/concepts/refactoring_1B63BA3B.html"
+ guid="_Poc7IPDzEdqYgerqi84oCA">Refactoring</a> should always be considered when reusing code. Code (or design) is often
+ not originally written for re-use, or reusable code may not be a perfect fit for a new situation.
+</p>
+<h3>
+ Assessing and Selecting Assets to Reuse
+</h3>
+<p>
+ To assess and select assets to reuse on your project, you need to understand the requirements of the system's
+ environment. You also need to understand the scope and general functionality of the system that the stakeholders
+ require. There are several types of assets to consider, including (but not limited to): reference architectures;
+ frameworks; patterns; analysis mechanisms; classes; and experience. You can search asset&nbsp;repositories (internal or
+ external to your organization) and industry literature to identify assets or similar projects.
+</p>
+<p>
+ You need to assess whether available assets contribute to solving the key challenges of the current project and whether
+ they are compatible with the project's architectural constraints. You also need to analyze the extent of the fit
+ between assets and requirements, considering whether any of the requirements are negotiable (to enable use of the
+ asset). Also, assess whether the asset could be modified or extended to satisfy requirements, as well as what the
+ tradeoffs in adopting it are, in terms of cost, risk, and functionality.
+</p>
+<p>
+ Leverage reuse of existing components by evaluating their interfaces and the behavior that they provide. Reuse
+ components when their interfaces are similar or match the interfaces of components you would need to develop from
+ scratch. If not similar, modify the newly identified interfaces so you improve the fit with existing components
+ interfaces. Work with developers to gain consensus on the suitability of using existing components.
+</p>
+<p>
+ Finally, decide, in principle, whether to use one or more assets, and record the rationale for this decision.
+</p>
+<h3>
+ Reuse Techniques
+</h3>
+<p>
+ Reuse can be performed differently depending on the capabilities of the implementation environment. The simplest
+ technique is to copy the code from one place to another. This isn't advisable because it's not really reuse. Multiple
+ copies of source code are difficult to maintain and can eventually diverge from each other. Reuse is about using the
+ same code to perform similar tasks as a way to increase quality and reduce overhead.
+</p>
+<p>
+ Some languages, such as C++, support templates. Templates, sometimes referred to as parameterized code, are a precursor
+ to patterns. Templates are code with parameters that are applied just when the code's needed, at compile time. The C++
+ Standard Template Library (STL) is one example. It provides many types of reusable containers (lists, sets, safe
+ arrays, etc) that don't have some of the drawbacks of inheritance. Templates such as these are also useful as mix-in
+ classes in languages like C++ that support multiple inheritance. Because mix-ins are implemented as templates, they
+ allow for a type of multiple inheritance without the baggage.
+</p>
+<h3>
+ Inheritance and Aggregation
+</h3>
+<p>
+ Inheritance (also known as generalization) is an easy way to implement polymorphism and has been used as the primary
+ mechanism for reuse in modern object-oriented languages. This is unfortunate, as inheritance imposes a rigid structure
+ on the software's design that is difficult to change. Any inheritance hierarchy that shares code from parents to
+ children will have problems when it grows to be three or more levels deep. Too many exceptions occur to maintain a pure
+ "is-a" relationship between parents and children, where children are always considered to have all the properties and
+ behaviors of the parents. Inheritance should be used to share definitions (interfaces), not implementations. Years of
+ difficulties with inheriting implementations have made this practice a primary object-oriented design principle.
+</p>
+<p>
+ Whenever inheritance is used, it is best to have only the last child class (leaf node) of the inheritance hierarchy be
+ instantiated. All parent classes should be abstract. This is because a class that tries to be both reusable and
+ concrete - to provide reusable and specific behavior at the same time - almost always fails to fulfill either goal.
+ This is a dimension of cohesiveness. One thing that makes a class cohesive is that it's dedicated to reuse or dedicated
+ to a specific implementation, but not both.
+</p>
+<p>
+ Aggregation is a technique that collects or aggregates functionality into larger elements of functionality. It provides
+ a structure that's far more flexible and reusable than inheritance. It's better to reuse implementation and design by
+ aggregating small pieces of functionality together rather than trying to inherit the functionality from a parent.
+</p>
+<p>
+ You may also find reuse opportunities by reviewing interfaces. If interfaces describe similar behavior it may be
+ possible to eliminate one of the interfaces, have just one implementation realize both interfaces, or refactor the
+ interfaces to put redundant content in a new, simpler interface.
+</p>
+<h3>
+ Finding Reusable Code
+</h3>
+<p>
+ There are many sources of reusable code beyond what the developers are writing for a specific project. Other places
+ from which to harvest code include the following:
+</p>
+<ul>
+ <li>
+ Internal (corporate) code libraries
+ </li>
+ <li>
+ Third party libraries
+ </li>
+ <li>
+ Built-in language libraries
+ </li>
+ <li>
+ Code samples from tutorials, examples, books, etc.
+ </li>
+ <li>
+ Local code guru or knowledgeable colleague
+ </li>
+ <li>
+ Existing system code
+ </li>
+ <li>
+ Open source products (be sure to follow any licensing agreements)
+ </li>
+</ul>
+<p>
+ Also, many tools that generate code will generate comprehensive code based on minimal specification. For example, a
+ design tool might generate the member variable plus a get and a set operation when the designer specifies an attribute.
+ Other more sophisticated tools with knowledge of a specific framework can generate voluminous code to ensure that a
+ class conforms to the framework. An example of this would be a tool that generates significant additional code when a
+ class is marked as a Java entity bean. This sort of consistent transformation from a specification (the design) to an
+ implementation (the code) could be considered a form of code reuse as well.
+</p>
+<h3>
+ Don't Reuse Everything
+</h3>
+<p>
+ Reuse makes code and design cheap to use but expensive to build. It requires experience and thoughtful consideration to
+ create an implementation or design that's abstract enough for others to re-use, but concrete enough to be truly useful.
+ Reusable code must also be maintained. Many organizations have difficulty assigning responsibility for maintaining
+ reusable code if they don't have a group dedicated to reuse.
+</p>
+<p>
+ It's usually not a good idea to create code or designs for reuse unless you know it's going to be reused. It's better
+ to refactor software to be more reusable after it's discovered that they can be reused. One rule of thumb is to write
+ for reuse only when you know you'll use it at least 3 times. Otherwise the cost of building and maintaining that part
+ of the software will not be recovered by reduced overhead in other areas of development.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/guidelines/test_ideas.xmi b/praclib/temp/core.tech.common.base/guidances/guidelines/test_ideas.xmi
new file mode 100644
index 0000000..7ad2885
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/guidelines/test_ideas.xmi
@@ -0,0 +1,149 @@
+<?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: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="_y3rxsMM3EdmSIPI87WLu3g"
+ name="test_ideas,_0jzlsMlgEdmt3adZL5Dmdw" guid="_y3rxsMM3EdmSIPI87WLu3g" changeDate="2006-09-29T09:37:59.292-0700"
+ version="1.0.0">
+ <mainDescription><h3>
+ Introduction
+</h3>
+<p>
+ Test ideas are used to generate tests.&nbsp;Test ideas can come from many different sources.&nbsp;In general, they can
+ be derived in different ways depending on the given development domain, the kind of application being developed, and
+ the sophistication of the testers.&nbsp;Although test ideas are derived in many different ways, there are some useful
+ categories for generating them.&nbsp;This guideline will describe some of these categories as well as some general
+ heuristics for creating good test ideas.
+</p>
+<h4>
+ Test Ideas and Functions
+</h4>
+<p>
+ Below are some test ideas to calculate the square root:
+</p>
+<ol>
+ <li>
+ A number that's barely less than zero as input
+ </li>
+ <li>
+ Zero as the input
+ </li>
+ <li>
+ Number that's a perfect square, like 4 or 16 (is the result exactly 2 or 4?)
+ </li>
+ <li>
+ Print to a LaserJet IIIp
+ </li>
+ <li>
+ Test with database full
+ </li>
+</ol>
+<p>
+ The first&nbsp;3 test ideas validate input while the last 2 address environmental issues.&nbsp; Even though these
+ statements are very incomplete they ensure that an idea is not forgotten.
+</p>
+<h4>
+ Test Ideas and Boundaries
+</h4>
+<p>
+ Test ideas are often based on fault models.&nbsp; Consider boundaries. It's safe to assume the square root function can
+ be implemented something like this:<br />
+ double sqrt(double x) {<br />
+ &nbsp;&nbsp;&nbsp; if (x &lt; 0)<br />
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // signal error<br />
+ &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ...<br />
+ It's also plausible that the &lt; will be incorrectly typed as &lt;=. People often make that kind of mistake, so it's
+ worth checking. The fault cannot be detected with X having the value 2, because both the incorrect expression (x&lt;=0)
+ and the correct expression (x&lt;0) will take the same branch of the if statement. Similarly, giving X the value -5
+ cannot find the fault. The only way to find it is to give X the value 0, which justifies the second test idea.
+</p>
+<h4>
+ Test Idea and Methods
+</h4>
+<p>
+ Let's suppose you're designing tests for a method that searches for a string in a sequential collection. It can either
+ obey case or ignore case in its search, and it returns the index of the first match found or -1 if no match is
+ found.<br />
+ int Collection.find(String string, Boolean ignoreCase);
+</p>
+<p>
+ Here are some test ideas for this method, each of which could be implemented as a test.&nbsp;
+</p>
+<ol>
+ <li>
+ Match found in the first position
+ </li>
+ <li>
+ Match found in the last position
+ </li>
+ <li>
+ No match found
+ </li>
+ <li>
+ Two or more matches found in the collection
+ </li>
+ <li>
+ Case is ignored; match found, but it wouldn't match if case was obeyed
+ </li>
+ <li>
+ Case is obeyed; an exact match is found
+ </li>
+ <li>
+ Case is obeyed; a string that would have matched if case were ignored is skipped
+ </li>
+</ol>
+<p>
+ However, different test ideas can be combined into a single test; for example, the following test satisfies test ideas
+ 2, 6, and 7:
+</p>
+<p>
+ <strong>Setup:</strong> Collection initialized to ["dawn", "Dawn"]<br />
+ <strong>Invocation:</strong> Collection.find("Dawn", false)<br />
+ <strong>Expected result:</strong> Return value is 1 (it would be 0 if "dawn" were not skipped)
+</p>
+<h4>
+ Test Idea Simplicity and Complexity
+</h4>
+<p>
+ Making test ideas nonspecific makes them easier to combine.<br />
+ Creating many several small tests that satisfy a few test ideas makes it simpler to:
+</p>
+<ul>
+ <li>
+ "Copy and Tweak" the tests to meet other test idea
+ </li>
+ <li>
+ Easy of debugging - if you have test that covers 2 test ideas then you know the fault is one or two area, but if
+ the test covers 7 test ideas you will spend more time debugging the issue.&nbsp;
+ </li>
+</ul>
+<p>
+ If the test ideas list were complete, with a test idea for every fault in the program, it wouldn't matter how you wrote
+ the tests. But the list is always missing some test ideas that could find bugs. Smaller more complex tests increase the
+ chance the test will satisfy a test idea that you didn't know you needed.
+</p>
+<h4>
+ Complex Tests
+</h4>
+<p>
+ Sometimes when you're creating more complex tests, new test ideas come to mind. However, there are reasons for not
+ creating complex tests.
+</p>
+<ul>
+ <li>
+ Complex test are more difficult to debug because they usually cover multiple test ideas
+ </li>
+ <li>
+ Complex tests are more difficult to understand and maintain. The intent of the test is less obvious.
+ </li>
+ <li>
+ Complex tests are more difficult to create.
+ </li>
+</ul>
+<p>
+ Constructing a test that satisfies five test ideas often takes more time than constructing five tests that each
+ satisfies one. Moreover, it's easier to make mistakes - to think you're satisfying all five when you're only satisfying
+ four.<br />
+ In practice, find a reasonable balance between complexity and simplicity.<br />
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/guidelines/test_suite.xmi b/praclib/temp/core.tech.common.base/guidances/guidelines/test_suite.xmi
new file mode 100644
index 0000000..71b12b5
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/guidelines/test_suite.xmi
@@ -0,0 +1,168 @@
+<?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: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="_s60KoMM3EdmSIPI87WLu3g"
+ name="test_suite,_0aDz0MlgEdmt3adZL5Dmdw" guid="_s60KoMM3EdmSIPI87WLu3g" changeDate="2006-09-29T09:48:57.425-0700"
+ version="1.0.0">
+ <mainDescription><h3>
+ Introduction
+</h3>
+<p>
+ The test suite provides a means of managing the complexity of the test implementation. Many system test efforts fail
+ because the team gets lost in the minutia of all of the detailed tests, and subsequently loses control of the test
+ effort. Similar to UML packages, test suites provide a hierarchy of encapsulating containers to help manage the test
+ implementation. They provide a means of managing the strategic aspects of the test effort by collecting tests together
+ in related groups that can be planned, managed, and assessed in a meaningful way.
+</p>
+<p>
+ The test suite represents a container for organizing arbitrary collections of related test scripts. This may be
+ realized (implemented) as one or more automated regression test suites, but the test suite can also be a work plan for
+ the implementation of a group of related manual test scripts. Note also that test suites can be nested hierarchically,
+ therefore one test suite may be enclosed within another.
+</p>
+<p>
+ Sometimes these groups of tests will relate directly to a subsystem or other system design element, but other times
+ they'll relate directly to things such as quality dimensions, core "mission critical" functions, requirements
+ compliance, standards adherence, and many others concerns that are organized based on requirements and therefore cut
+ across the internal system elements.
+</p>
+<p>
+ Consider creating test suites that arrange the available test scripts, in addition to other test suites, in many
+ different combinations: the more variations you have, the more you'll increase coverage and the potential for finding
+ errors. Give thought to a variety of test suites that will cover the breadth and depth of the target test items.
+ Remember the corresponding implication that a single test script (or test suite) may appear in many different test
+ suites.
+</p>
+<p>
+ Some test automation tools provide the ability to automatically generate or assemble test suites. There are also
+ implementation techniques that enable automated test suites to dynamically select all or part of their component test
+ scripts for each test cycle run.
+</p>
+<p>
+ Test suites can help you maintain your test assets and impose a level of organization that facilitates the entire
+ testing effort.&nbsp; Like physical objects, tests can break. It's not that they wear down, it's that something changed
+ in their environment. Perhaps they've been ported to a new operating system. Or, more likely, the code they exercise
+ has changed in a way that correctly causes the test to fail. Suppose you're working on version 2.0 of an e-banking
+ application. In version 1.0, this method was used to log in:
+</p>
+<p class="codeSample">
+ public boolean login (String username);
+</p>
+<p>
+ In version 2.0, the marketing department has realized that password protection might be a good idea. So the method is
+ changed to this:
+</p>
+<p class="codeSample">
+ public boolean login (String username, String password);
+</p>
+<p>
+ Any test that uses the first form of the login will fail. It won't even compile. In this example you could find that,
+ not many useful tests can be written that don't use login. You might be faced with hundreds or thousands of failing
+ tests.
+</p>
+<p>
+ These tests can be fixed by using a global search-and-replace tool that finds every instance of login(something) and
+ replaces it with login(something, "dummy password"). Then arrange for all the testing accounts to use that password,
+ and you're on your way.
+</p>
+<p>
+ Then, when marketing decides that passwords should not be allowed to contain spaces, you get to do it all over again.
+</p>
+<p>
+ This kind of thing is a wasteful burden, especially when, as is often the case, the test changes aren't so easily made.
+ There is a better way.
+</p>
+<p>
+ Suppose that the test scripts originally did not call the product's login method. Rather, they called a library method
+ that does whatever it takes to get the test logged in and ready to proceed. Initially, that method might look like
+ this:
+</p>
+<p class="codeSample">
+ public boolean testLogin (String username) {<br />
+ &nbsp; return product.login(username);<br />
+ }
+</p>
+<p>
+ When the version 2.0 change happens, the utility library is changed to match:
+</p>
+<p class="codeSample">
+ public Boolean testLogin (String username) {<br />
+ &nbsp; return product.login(username, "dummy password");<br />
+ }
+</p>
+<p>
+ Instead of a changing a thousand tests, you change one method.
+</p>
+<p>
+ Ideally, all the needed library methods would be available at the beginning of the testing effort. In practice, they
+ can't all be anticipated-you might not realize you need a testLogin utility method until the first time the product
+ login changes. So test utility methods are often "factored out" of existing tests as needed. It is very important that
+ you perform this ongoing test repair, even under schedule pressure. If you do not, you will waste much time dealing
+ with an ugly and un-maintainable test suite. You might well find yourself throwing it away, or being unable to write
+ the needed numbers of new tests because all your available testing time is spent maintaining old ones.
+</p>
+<p>
+ Note: the tests of the product's login method will still call it directly. If its behavior changes, some or all of
+ those tests will need to be updated. (If none of the login tests fail when its behavior changes, they're probably not
+ very good at detecting defects.)
+</p>
+<h3>
+ Abstraction helps manage complexity
+</h3>
+<p>
+ The previous example showed how tests can abstract away from the concrete application. Most likely you can do
+ considerably more abstraction. You might find that a number of tests begin with a common sequence of method calls: they
+ log in, set up some state, and navigate to the part of the application you're testing. Only then does each test do
+ something different. All this setup could-and should-be contained in a single method with an evocative name such as
+ readyAccountForWireTransfer. By doing that, you're saving considerable time when new tests of a particular type are
+ written, and you're also making the intent of each test much more understandable.
+</p>
+<p>
+ Understandable tests are important. A common problem with old test suites is that no one knows what the tests are doing
+ or why. When they break, the tendency is to fix them in the simplest possible way. That often results in tests that are
+ weaker at finding defects. They no longer test what they were originally intended to test.
+</p>
+<h3>
+ Throwing away tests
+</h3>
+<p>
+ Even with utility libraries, a test might periodically be broken by behavior changes that have nothing to do with what
+ it checks. Fixing the test doesn't stand much of a chance of finding a defect due to the change; it's something you do
+ to preserve the chance of the test finding some other defect someday. But the cost of such a series of fixes might
+ exceed the value of the tests hypothetically finding a defect. It might be better to simply throw the test away and
+ devote the effort to creating new tests with greater value.
+</p>
+<p>
+ Most people resist the notion of throwing away a test, at least until they're so overwhelmed by the maintenance burden
+ that they throw all the tests away. It is better to make the decision carefully and continuously, test by test, asking:
+</p>
+<ul>
+ <li>
+ How much work will it be to fix this test well, perhaps adding to the utility library?
+ </li>
+ <li>
+ How else might the time be used?
+ </li>
+ <li>
+ How likely is it that the test will find serious defects in the future? What's been the track record of it and
+ related tests?
+ </li>
+ <li>
+ How long will it be before the test breaks again?
+ </li>
+</ul>
+<p>
+ The answers to these questions will be rough estimates or even guesses. But asking them will yield better results than
+ simply having a policy of fixing all tests.
+</p>
+<p>
+ Another reason to throw away tests is that they are now redundant. For example, early in development, there might be a
+ multitude of simple tests of basic parse-tree construction methods (the LessOp constructor and the like). Later, during
+ the writing of the parser, there will be a number of parser tests. Since the parser uses the construction methods, the
+ parser tests will also indirectly test them. As code changes break the construction tests, it's reasonable to discard
+ some of them as being redundant. Of course, any new or changed construction behavior will need new tests. They might be
+ implemented directly (if they're hard to test thoroughly through the parser) or indirectly (if tests through the parser
+ are adequate and more maintainable).
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/guidelines/using_visual_modeling.xmi b/praclib/temp/core.tech.common.base/guidances/guidelines/using_visual_modeling.xmi
new file mode 100644
index 0000000..2c0ac4d
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/guidelines/using_visual_modeling.xmi
@@ -0,0 +1,47 @@
+<?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="-QklqSGB4aD07vUpfubpMJg"
+ name="new_guideline,_0SsecNr8EdyXE6np2_hUMA" guid="-QklqSGB4aD07vUpfubpMJg" changeDate="2008-02-14T08:06:27.531-0500">
+ <mainDescription><p>
+ When applying visual modeling, you can use various techniques:
+</p>
+<ul>
+ <li>
+ <strong>Identify the key perspectives:</strong> Focus on modeling the things that count. Few (if any) projects
+ benefit from modeling the entire design to a great level of detail. Make sure that you understand why you are
+ modeling something and who will benefit.
+ </li>
+ <li>
+ <strong>Communicate key architectural perspectives:</strong> Even if you choose to model very little&nbsp;of your
+ design, it is often advantageous to produce diagrams that communicate the key architectural aspects of the system.
+ Conveying the "big picture" to the rest of the team helps them understand the overall approach and develop cohesive
+ software.&nbsp;
+ </li>
+ <li>
+ <strong>Sketch the design:</strong> Not all models need to be detailed completely and presented in a software
+ modeling tool. It is often perfectly acceptable (if not desirable) to produce hand-drawn sketches on paper or on a
+ whiteboard when you are exploring and communicating the architecture and design with your team. You can use a
+ digital camera or an electronic whiteboard to capture these diagrams and share them. For many small projects, this
+ is often all you need. See <a href="http://www.agilemodeling.com/">http://www.agilemodeling.com/</a> for more
+ information.
+ </li>
+ <li>
+ <strong>Use a modeling tool as needed</strong>:&nbsp;If the team members are changing models throughout the
+ project, sharing patterns/structure, debugging design, describing behavior, etc., then static photos or paper will
+ become difficult to work with. The team may want to capture design in a software modeling tool. Other than
+ communicating the design to the team, another benefit of a such a tool is the&nbsp;generation of structural code
+ from the models. Many software development tools allow you to view the code as models, making it easier to
+ comprehend static and dynamic aspects of a complex code base.
+ </li>
+ <li>
+ <strong>Agree on a standard notation:</strong> In a team environment, it is important that others can understand
+ your diagrams without much explanation. Choosing a standard notation enables others to quickly comprehend your
+ diagrams without ambiguity. The Unified Modeling Language (UML) provides an industry-standard approach to software
+ modeling and is an example of a widely understood notation.
+ </li>
+</ul>For more information, see <a class="elementLinkWithType"
+href="./../../../core.tech.common.base/guidances/concepts/visual_modeling_2C089766.html"
+guid="_0XY6UMlgEdmt3adZL5Dmdw">Concept: Visual Modeling</a>.<br /></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/guidelines/writing_good_requirements.xmi b/praclib/temp/core.tech.common.base/guidances/guidelines/writing_good_requirements.xmi
new file mode 100644
index 0000000..334b30d
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/guidelines/writing_good_requirements.xmi
@@ -0,0 +1,141 @@
+<?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="-AJQLv2ldVv5KN9eUbdQe_g"
+ name="new_guideline,_6jXzYNcKEdqz_d2XWoVt6Q" guid="-AJQLv2ldVv5KN9eUbdQe_g" changeDate="2006-05-01T03:33:21.000-0700"
+ version="7.1.0">
+ <mainDescription><p>
+ To write a good requirement, you must write it as a complete sentence, with a subject and a predicate (usually a verb).
+ The subject&nbsp;is an Actor, a stakeholder, the system under development, or a design entity that is related to the
+ requirement. The predicate specifies a condition, action, or intended result that is done for, by, with, or to the
+ subject.
+</p>
+<p>
+ Consistent use of the verb <strong>to be</strong> solidifies the link between the subject and the predicate. Thus, you
+ can analyze a requirement from a grammatical point of view.
+</p>
+<p>
+ Beware of lists, bullets, and words such as <strong>all</strong>, <strong>every</strong>. and <strong>some</strong>.
+ For example:
+</p>
+<blockquote>
+ <p>
+ The order entry clerk must be able to complete 10 customer orders in less than two hours.
+ </p>
+</blockquote>
+<p>
+ This requirement has a subject (the order entry clerk, who is an Actor), a specific and measurable end state (10
+ customer orders completed), and a performance criterion (in less than two hours).
+</p>
+<p>
+ Follow these simple guidelines in writing any requirement. For consistency, these examples are all in the context of
+ an aircraft. [[WAS: is used throughout.]] <a class="elementlinkwithusertext"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/references_6CCF393.html"
+ guid="_9ToeIB83Edqsvps02rpOOg">[TEL06]</a>
+</p>
+<ul>
+ <li>
+ Define one requirement at a time.
+ <blockquote>
+ <p>
+ The pilot shall be able to control the aircraft's angle of climb with one hand.
+ </p>
+ </blockquote>
+ </li>
+</ul>
+<blockquote>
+ <blockquote>
+ <p>
+ The pilot shall be able to feel the angle of climb from the climb control.
+ </p>
+ </blockquote>
+</blockquote>
+<ul>
+ <li>
+ Avoid conjunctions (and, or) that make multiple requirements.
+ </li>
+</ul>
+<blockquote>
+ <blockquote>
+ <p>
+ The navigator shall be able to view the aircraft's position relative to the route's radio beacons.
+ </p>
+ <p>
+ The navigator shall be able to view the aircraft's position as estimated by inertial guidance.
+ </p>
+ </blockquote>
+</blockquote>
+<ul>
+ <li>
+ Avoid let-out clauses or words that imply options or exceptions (unless, except, if necessary, but).
+ </li>
+ <li style="list-style: none">
+ <blockquote>
+ <p>
+ The design shall provide a rear-facing seat for each cabin crew member.
+ </p>
+ </blockquote>
+ </li>
+ <li>
+ Use simple, direct sentences.
+ </li>
+</ul>
+<ul>
+ <li style="list-style: none">
+ <blockquote>
+ <p>
+ The pilot shall be able to see the airspeed indicator.
+ </p>
+ </blockquote>
+ </li>
+ <li>
+ Use a limited (500-word) vocabulary, especially if your audience is international.
+ <blockquote>
+ <p>
+ The airline shall be able to convert the aircraft from business to holiday charter use in less than 12
+ hours
+ </p>
+ </blockquote>
+ </li>
+ <li style="list-style: none">
+ <blockquote>
+ <p>
+ <strong>Note:</strong> There is no need to use words such as <strong>reconfigured.</strong>
+ </p>
+ </blockquote>
+ </li>
+ <li>
+ Identify the type of user who needs each requirement.
+ </li>
+</ul>
+<ul>
+ <li style="list-style: none">
+ <blockquote>
+ <p>
+ The navigator shall be able to...
+ </p>
+ </blockquote>
+ </li>
+ <li>
+ Focus on stating what result you will provide for that type of user.
+ </li>
+</ul>
+<ul>
+ <li style="list-style: none">
+ <blockquote>
+ <p>
+ ...view storm clouds by radar...
+ </p>
+ </blockquote>
+ </li>
+ <li>
+ Define verifiable criteria
+ <blockquote>
+ <p>
+ ...at least 100 miles ahead.
+ </p>
+ </blockquote>
+ </li>
+</ul></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/roadmaps/resources/openup-basic_lifecycle.jpg b/praclib/temp/core.tech.common.base/guidances/roadmaps/resources/openup-basic_lifecycle.jpg
new file mode 100644
index 0000000..4719cad
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/roadmaps/resources/openup-basic_lifecycle.jpg
Binary files differ
diff --git a/praclib/temp/core.tech.common.base/guidances/supportingmaterials/resources/openup-basic_lifecycle.jpg b/praclib/temp/core.tech.common.base/guidances/supportingmaterials/resources/openup-basic_lifecycle.jpg
new file mode 100644
index 0000000..4719cad
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/supportingmaterials/resources/openup-basic_lifecycle.jpg
Binary files differ
diff --git a/praclib/temp/core.tech.common.base/guidances/supportingmaterials/tech_references.xmi b/praclib/temp/core.tech.common.base/guidances/supportingmaterials/tech_references.xmi
new file mode 100644
index 0000000..d0c830c
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/supportingmaterials/tech_references.xmi
@@ -0,0 +1,644 @@
+<?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="-aCI9T-9TIe8D35yXBU6qvg"
+ name="references,_9ToeIB83Edqsvps02rpOOg" guid="-aCI9T-9TIe8D35yXBU6qvg" changeDate="2008-02-21T10:18:46.919-0800"
+ version="1.0.0">
+ <mainDescription>&nbsp; 
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>ADO03</a>
+ </td>
+ <td colspan="2">
+ Adolph, Bramble, Cockburn, and Pols <em>Patterns for Effective Use Cases</em>, Addison Wesley, 2003.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>ADO04</a>
+ </td>
+ <td colspan="2">
+ Adolph, Bramble, Cockburn, and Pols <em>Tutorial 17: Patterns for Writing Effective Use Cases</em>,
+ presented at the 19th Annual Conference on Object-Oriented Programming, Systems, Languages and
+ Applications, 2004.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>ALE77</a>
+ </td>
+ <td colspan="2">
+ Alexander, C. <em>A Pattern Language</em>, Oxford University Press, 1977
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>ALE79</a>
+ </td>
+ <td colspan="2">
+ Alexander, C., <em>A Timeless Way of Building</em>, Oxford University Press, 1979
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>ALL02</a>
+ </td>
+ <td colspan="2">
+ Allamaraju, S. <em>Architecture Paradox</em>, <a
+ href="http://www.sei.cmu.edu/architecture/essays.html">http://www.sei.cmu.edu/architecture/essays.html</a>.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>ALU03</a>
+ </td>
+ <td colspan="2">
+ <p>
+ Alur, D., Crupi, J., Malks, D., <em>Core J2EE Patterns: Best Practices and Design Strategies</em>,
+ Prentice Hall/Sun Press, 2001.
+ </p>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>AMB02</a>
+ </td>
+ <td colspan="2">
+ <p>
+ Ambler, S.W. <em>Agile Modeling: Effective Practices for Extreme Programming and Unified Process</em>.
+ Wiley Publishing, 2002.
+ </p>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>AMB03</a>
+ </td>
+ <td colspan="2">
+ <p>
+ Ambler, S.W. <em>Agile Database Techniques: Effective Strategies for the Agile Software
+ Developer</em>.&nbsp; Wiley Publishing, 2003.
+ </p>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>AMB04</a>
+ </td>
+ <td colspan="2">
+ <p>
+ Ambler, S.W. <em>The Object Primer 3rd Edition: Agile Model Driven Development with UML 2</em>.
+ Cambridge University Press, 2004.
+ </p>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>AMB06</a>
+ </td>
+ <td colspan="2">
+ <p>
+ Ambler, S.W. and Sadalage, P.J. <em>Refactoring Databases: Evolutionary Database Design</em>.&nbsp;
+ Addison Wesley, 2006.
+ </p>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>BER04</a>
+ </td>
+ <td colspan="2">
+ <p>
+ Bergström, S. and Råberg, L., <em>Adopting the Rational Unified Process</em>, Success with the RUP,
+ Addison- Wesley, 2004.
+ </p>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>BOE88</a>
+ </td>
+ <td colspan="2">
+ <p>
+ Boehm, B., Papaccio, C. <em>Understanding and Controlling Software Cost</em>, IEEE Trans. on Software
+ Engineering, Oct. 1988.
+ </p>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>BOE91</a>
+ </td>
+ <td colspan="2">
+ Boehm, B., <em>Software Risk Management: Principles and Practices</em>, IEEE Software. vol. 8, no. 1, pp.
+ 32-41, 1991.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>BOE03a</a>
+ </td>
+ <td colspan="2">
+ Boehm, B. and Turner, R., <em>Balancing Agility and Discipline: A Guide for the Perplexed</em>,
+ Addison-Wesley Professional, 2003.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>BOE03b</a>
+ </td>
+ <td colspan="2">
+ Boehm, B. and Turner, R., <em>Using Risk to Balance Agile and Plan-Driven Methods</em>, IEEE Computer. vol.
+ 36, no. 6, pp. 57-66, 2003.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>BOO05</a>
+ </td>
+ <td colspan="2">
+ Booch, G., Rumbaugh, J., Jacobson, I.<em>The Unified Modeling Language User Guide</em>, Addison-Wesley
+ Professional, 2005
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>BRO95</a>
+ </td>
+ <td colspan="2">
+ Brooks, F. P., <em>The Mythical Man-Month</em>, Essays on Software Engineering Anniversary Edition,
+ Addison-Wesley, 1995.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>BUS96</a>
+ </td>
+ <td colspan="2">
+ Buschmann, F., Meunier, R., Rohnert, H.,Sommerlad, P., Stal, M., <em>Pattern-Oriented Software Architecture
+ -- A System of Patterns</em>, Wiley, 1996.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>COC01</a>
+ </td>
+ <td colspan="2">
+ Cockburn, A.,<em>Agile Software Development</em>, Addison-Wesley, 2001.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <p>
+ <a>COH05</a>&nbsp;
+ </p>
+ <p>
+ <a>COP95</a>
+ </p>
+ </td>
+ <td colspan="2">
+ <p>
+ Cohn, M. <em>Agile Estimation and Planning</em>, Addison Wesley Longman, 2005
+ </p>Coplien, J., Schmidt, D., <em>Pattern Languages of Program Design</em>,Addison-Wesley Professional,
+ 1995
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>COP95</a>
+ </td>
+ <td colspan="2">
+ Coplien, J., Schmidt, D., <em>Pattern Languages of Program Design</em>,Addison-Wesley Professional, 1995
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>GAM95</a>
+ </td>
+ <td colspan="2">
+ Gamma, E., Helm, R., Johnson, R., Vlissides, J., <em>Design Patterns: Elements of Reusable Object-Oriented
+ Software</em>, Addison-Wesley Professional; 1995
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>GAB98</a>
+ </td>
+ <td colspan="2">
+ Gabriel, Richard P., <em>Patterns of Software: Tales from the Software Community</em>, Oxford University
+ Press, 1998.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="GAM95" name="GAM95">GAM95</a>
+ </td>
+ <td colspan="2">
+ Gamma, E., Helm, R., Johnson, R., Vlissides, J., <em>Design Patterns: Elements of Reusable Object-Oriented
+ Software</em>, Addison-Wesley Professional; 1995
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>GAR93</a>
+ </td>
+ <td colspan="2">
+ David Garlan and Mary Shaw. <em>An Introduction to Software Architecture</em>,&nbsp; SEI Technical Report
+ CMU/SEI-94-TR-21.&nbsp;
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>HAN99</a>
+ </td>
+ <td colspan="2">
+ Hansen, M.T., Nohria, N., and Tierney, T., <em>What’s Your Strategy for Managing Knowledge?</em>, Harvard
+ Business Review, pp. 106-16, Mar.- Apr. 1999.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>HIC03</a>
+ </td>
+ <td colspan="2">
+ Hickey A., Davis, A. <em>Elicitation Technique Selection: How Do the Experts Do It?</em>, International
+ Conference on Requirements Engineering (RE03), Los Alamitos, California: IEEE Computer Society Press, Sep.
+ 2003.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>HUL05</a>
+ </td>
+ <td colspan="2">
+ Hull, E., Jackson, K. and&nbsp;Dick, J. <em>Requirements Engineering</em>, Second Edition. Springer, 2005.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>IE610.12</a>
+ </td>
+ <td colspan="2">
+ IEEE <em>Standard Glossary of Software Engineering Terminology</em>, Corrected Edition, IEEE Std 610.12,
+ Feb. 1991.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>IEP1471</a>
+ </td>
+ <td colspan="2">
+ IEEE <em>Recommended Practice for Architectural Description</em>, IEEE Std P1471, 2000.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>KAZ00</a>
+ </td>
+ <td colspan="2">
+ Kazman, R., Carriere, S. J., Woods, S. G.&nbsp;<a
+ href="http://www.sei.cmu.edu/staff/rkazman/annals-scenario.pdf">Toward a Discipline of Scenario-Based
+ Architectural Engineering</a>, <a href="http://manta.cs.vt.edu./ase/">Annals of Software Engineering</a>,
+ Vol. 9, 2000, 5-33.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>KAZ04</a>
+ </td>
+ <td colspan="2">
+ Kazman, R., Kruchten, P., Nord, R., Tomayko, J.&nbsp;<em>Integrating Software-Architecture-Centric Methods
+ into the Rational Unified Process</em>, CMU-SEI Technical Reports, 2004.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>KRU95</a>
+ </td>
+ <td colspan="2">
+ Kruchten, Phillipe B.,&nbsp; <em>The 4+1 View Model of Architecture</em>, IEEE Software, vol. 12, no. 6, pp
+ 42-50, Nov. 1995&nbsp;
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>MAR03</a>&nbsp;
+ </td>
+ <td colspan="2">
+ Marick, B., <em>Exploration Through Example</em>, <a
+ href="http://www.testing.com/cgi-bin/blog/2003/08/21#agile-testing-project-1">http://www.testing.com/cgi-bin/blog/2003/08/21#agile-testing-project-1</a>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="MEY97" name="MEY97">MEY97</a>&nbsp;
+ </td>
+ <td colspan="2">
+ Meyer, B., <em>Object-Oriented Software Construction</em>, Prentice Hall, 1997
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>NBG01</a>
+ </td>
+ <td colspan="2">
+ Eric J. Naiburg and Robert A. Maksimchuk. <em>UML for Database Design</em>, New York, NY: Addison Wesley,
+ 2001
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>OLS00</a>
+ </td>
+ <td colspan="2">
+ Olson, G. M. and Olson J. S., <em>Distance Matters</em>, Human-Computer Interaction, vol. 15, pp. 139 –
+ 178, 2000.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>OOP96</a>
+ </td>
+ <td colspan="2">
+ The 1996 ACM Conference on Object-Oriented Programs, Systems, Languages and Applications (OOPSLA), <em>The
+ Origins of Pattern Theory, the Future of the Theory, And The Generation of a Living World.</em>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top" width="12%">
+ </td>
+ <td width="10%">
+ </td>
+ <td style="PADDING-BOTTOM: 10px" width="78%">
+ See <a
+ href="http://www.patternlanguage.com/archive/ieee/ieeetext.htm">http://www.patternlanguage.com/archive/ieee/ieeetext.htm</a>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>PW92</a>
+ </td>
+ <td colspan="2">
+ Dewayne E. Perry and Alexander L. Wolf. <em>Foundations for the Study of Software Architecture</em>. ACM
+ SIGSOFT Software Engineering Notes, 17(4):40-52, Oct. 1992.
+ </td>
+ </tr>
+ <tr>
+ <td valign="top" width="12%">
+ </td>
+ <td width="10%">
+ </td>
+ <td style="PADDING-BOTTOM: 10px" width="78%">
+ <p>
+ An excellent reference by one of the co-inventors of the Scrum project management method.
+ </p>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>ROD99</a>
+ </td>
+ <td colspan="2">
+ Rodhain, F., <em>Tacit to Explicit: Transforming Knowledge through Cognitive Mapping – An Experiment</em>,
+ Proceedings of the 1999 ACM SIGCPR Conference on Computer Personnel Research, pp. 51-56, New Orleans,
+ Louisiana, 1999.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="SHA05" name="SHA05">SHA05</a>
+ </td>
+ <td colspan="2">
+ Shalloway, J., Trott, J. <em>Design Patterns Explained</em> A New Perspective on Object-Oriented Design,
+ Second Edition, Addison Wesley, 2005
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>TEL06</a>
+ </td>
+ <td colspan="2">
+ Telelogic, 2006. <em>Get It Right the First Time: Writing Better Requirements.</em>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>THA00</a>
+ </td>
+ <td colspan="2">
+ Thayer, Richard H.&nbsp;and Dorfman, Merlin&nbsp;<em>Software Requirements Engineering Second Edition</em>,
+ IEEE Computer Society, 2000
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>UML05</a>
+ </td>
+ <td colspan="2">
+ OMG, 2005. <em>Unified Modeling Language 2.0: Superstructure.</em><br />
+ <a href="http://www.omg.org/docs/formal/05-07-04.pdf">http://www.omg.org/docs/formal/05-07-04.pdf</a>
+ </td>
+ </tr>
+ </tbody>
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>WIB04</a>
+ </td>
+ <td colspan="2">
+ Wiborg-Weber, D., Vignaud, J. L. <em>A Framework for Managing Component Based Development</em>, Telelogic
+ Whitepaper, 2004<br />
+ <a
+ href="http://www.telelogic.com/download/index.cfm?id=4423">http://www.telelogic.com/download/index.cfm?id=4423</a>
+ </td>
+ </tr>
+ </tbody>
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a>WIKP-MVC</a>
+ </td>
+ <td colspan="2">
+ Wikipedia <em>Model-view-controller</em><br />
+ <a
+ href="http://en.wikipedia.org/wiki/Model-view-controller">http://en.wikipedia.org/wiki/Model-view-controller</a>
+ </td>
+ </tr>
+ </tbody>
+</table></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/templates/manual_test_script.xmi b/praclib/temp/core.tech.common.base/guidances/templates/manual_test_script.xmi
new file mode 100644
index 0000000..6d39f84
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/templates/manual_test_script.xmi
@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:GuidanceDescription 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="-PHKmXwkVhDR81vcyAQAkxQ"
+ name="new_template,_yZtgQI5gEdyO5aWob1UGDA" guid="-PHKmXwkVhDR81vcyAQAkxQ" version="7.2.0">
+ <attachments>resources/test_script_tpl.dot</attachments>
+</org.eclipse.epf.uma:GuidanceDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/templates/resources/systemwide_req_spec.dot b/praclib/temp/core.tech.common.base/guidances/templates/resources/systemwide_req_spec.dot
new file mode 100644
index 0000000..dd5c720
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/templates/resources/systemwide_req_spec.dot
Binary files differ
diff --git a/praclib/temp/core.tech.common.base/guidances/templates/resources/test_cases.dot b/praclib/temp/core.tech.common.base/guidances/templates/resources/test_cases.dot
new file mode 100644
index 0000000..1b5a40b
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/templates/resources/test_cases.dot
Binary files differ
diff --git a/praclib/temp/core.tech.common.base/guidances/templates/resources/test_script_tpl.dot b/praclib/temp/core.tech.common.base/guidances/templates/resources/test_script_tpl.dot
new file mode 100644
index 0000000..a4ed50b
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/templates/resources/test_script_tpl.dot
Binary files differ
diff --git a/praclib/temp/core.tech.common.base/guidances/templates/resources/uc_specification_tpl.dot b/praclib/temp/core.tech.common.base/guidances/templates/resources/uc_specification_tpl.dot
new file mode 100644
index 0000000..0f28b64
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/templates/resources/uc_specification_tpl.dot
Binary files differ
diff --git a/praclib/temp/core.tech.common.base/guidances/templates/resources/vision_tpl.dot b/praclib/temp/core.tech.common.base/guidances/templates/resources/vision_tpl.dot
new file mode 100644
index 0000000..c8ce673
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/templates/resources/vision_tpl.dot
Binary files differ
diff --git a/praclib/temp/core.tech.common.base/guidances/templates/systemwide_requirements_specification.xmi b/praclib/temp/core.tech.common.base/guidances/templates/systemwide_requirements_specification.xmi
new file mode 100644
index 0000000..e130c98
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/templates/systemwide_requirements_specification.xmi
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:GuidanceDescription 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="-13wK-dfNa9N1G8Ob27m-Og"
+ name="new_template,_m7p-AI5fEdyO5aWob1UGDA" guid="-13wK-dfNa9N1G8Ob27m-Og" changeDate="2008-02-11T15:48:39.089-0800"
+ version="7.2.0">
+ <mainDescription>This template provides a starting point for capturing system-wide requirements in a consistent manner and to provide a
+useful checklist when determining the types of requirements that may apply. It is not expected that one would complete
+every section of this template in all circumstances. Tailor as you see fit for your particular circumstances.</mainDescription>
+ <attachments>resources/systemwide_req_spec.dot</attachments>
+</org.eclipse.epf.uma:GuidanceDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/templates/test_case.xmi b/praclib/temp/core.tech.common.base/guidances/templates/test_case.xmi
new file mode 100644
index 0000000..7dbe05b
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/templates/test_case.xmi
@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:GuidanceDescription 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="-JrYzWdOXPOZBIVGWibK1Bw"
+ name="test_case,_yWaKEI5fEdyO5aWob1UGDA" guid="-JrYzWdOXPOZBIVGWibK1Bw">
+ <attachments>resources/test_cases.dot</attachments>
+</org.eclipse.epf.uma:GuidanceDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/templates/use_case_specification.xmi b/praclib/temp/core.tech.common.base/guidances/templates/use_case_specification.xmi
new file mode 100644
index 0000000..8d36524
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/templates/use_case_specification.xmi
@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:GuidanceDescription 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="-zGnAaKUwKnn2pPANr7E0MQ"
+ name="new_template,_3Y3XUI5fEdyO5aWob1UGDA" guid="-zGnAaKUwKnn2pPANr7E0MQ">
+ <attachments>resources/uc_specification_tpl.dot</attachments>
+</org.eclipse.epf.uma:GuidanceDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/templates/vision.xmi b/praclib/temp/core.tech.common.base/guidances/templates/vision.xmi
new file mode 100644
index 0000000..e3aba3d
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/templates/vision.xmi
@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:GuidanceDescription 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="-DUD2tbhBn23i6Jm6gcoN9Q"
+ name="new_template,_DtlRQI5gEdyO5aWob1UGDA" guid="-DUD2tbhBn23i6Jm6gcoN9Q">
+ <attachments>resources/vision_tpl.dot</attachments>
+</org.eclipse.epf.uma:GuidanceDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/termdefinitions/architectural_mechanism.xmi b/praclib/temp/core.tech.common.base/guidances/termdefinitions/architectural_mechanism.xmi
new file mode 100644
index 0000000..33660b7
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/termdefinitions/architectural_mechanism.xmi
@@ -0,0 +1,10 @@
+<?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: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="-Vvwb6EupIB9kfSQ_mhjURA"
+ name="architectural_mechanism,_VHFGkEvCEdunZcj9T5hrMQ" guid="-Vvwb6EupIB9kfSQ_mhjURA"
+ changeDate="2006-09-24T05:46:41.881-0700">
+ <mainDescription>Architectural mechanisms represent common concrete solutions to frequently encountered problems. They may be patterns of
+structure, patterns of behavior, or both.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/termdefinitions/architectural_view.xmi b/praclib/temp/core.tech.common.base/guidances/termdefinitions/architectural_view.xmi
new file mode 100644
index 0000000..627ce76
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/termdefinitions/architectural_view.xmi
@@ -0,0 +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.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="-0vih7gB84YYDheaH7jeYFQ"
+ name="new_term_definition,_n7GmQEvCEdunZcj9T5hrMQ" guid="-0vih7gB84YYDheaH7jeYFQ"
+ version="7.2.0">
+ <mainDescription>A view of the&nbsp;architecture from a given perspective.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/termdefinitions/architecture.xmi b/praclib/temp/core.tech.common.base/guidances/termdefinitions/architecture.xmi
new file mode 100644
index 0000000..1f84a99
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/termdefinitions/architecture.xmi
@@ -0,0 +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.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">
+ <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
+ 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/praclib/temp/core.tech.common.base/guidances/termdefinitions/build.xmi b/praclib/temp/core.tech.common.base/guidances/termdefinitions/build.xmi
new file mode 100644
index 0000000..9934c3b
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/termdefinitions/build.xmi
@@ -0,0 +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.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="-Wh-byAGHoy_gGry0Jq6VaA"
+ name=",_Z-AukEvpEdunZcj9T5hrMQ" guid="-Wh-byAGHoy_gGry0Jq6VaA">
+ <mainDescription>An operational version of a system or part of a system that demonstrates a subset of the capabilities to be provided in the
+final product</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/termdefinitions/component.xmi b/praclib/temp/core.tech.common.base/guidances/termdefinitions/component.xmi
new file mode 100644
index 0000000..e167af7
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/termdefinitions/component.xmi
@@ -0,0 +1,12 @@
+<?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="-BWZsh3vKrqSOzfkBJmDTLA"
+ name=",_d82_AEvDEdunZcj9T5hrMQ" guid="-BWZsh3vKrqSOzfkBJmDTLA" version="7.2.0">
+ <mainDescription><p>
+ An encapsulated part of the system that is nontrivial, nearly independent, and replaceable and that fulfils a clear
+ function in the context of well-defined architecture. A component conforms to and provides the realization of a set of
+ interfaces.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/termdefinitions/furps.xmi b/praclib/temp/core.tech.common.base/guidances/termdefinitions/furps.xmi
new file mode 100644
index 0000000..ba0db3d
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/termdefinitions/furps.xmi
@@ -0,0 +1,10 @@
+<?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="-vq2pL6yQuqGhql9Wo_Av4w"
+ name=",_ZH6M0EvEEdunZcj9T5hrMQ" guid="-vq2pL6yQuqGhql9Wo_Av4w" changeDate="2008-02-11T15:46:42.702-0800"
+ version="1.0.0">
+ <mainDescription>Functional, usability, reliability, performance, supportability&nbsp;and others. This acronym represents categories that
+can be used in the definition of product requirements.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/termdefinitions/pattern.xmi b/praclib/temp/core.tech.common.base/guidances/termdefinitions/pattern.xmi
new file mode 100644
index 0000000..152c101
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/termdefinitions/pattern.xmi
@@ -0,0 +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="-VJBtRm2brEKpRlnLWNF8_g"
+ name=",_ctrEgEvCEdunZcj9T5hrMQ" guid="-VJBtRm2brEKpRlnLWNF8_g" version="7.2.0">
+ <mainDescription>Generalized solution that can be implemented and applied in a problem situation (a context)</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/guidances/termdefinitions/requirement.xmi b/praclib/temp/core.tech.common.base/guidances/termdefinitions/requirement.xmi
new file mode 100644
index 0000000..ed3d0e1
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/guidances/termdefinitions/requirement.xmi
@@ -0,0 +1,20 @@
+<?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="-0sCBiohjw_wBDKk0WEeDJQ"
+ name="new_term_definition,_feKVQLULEdqI644ssJaKYg" guid="-0sCBiohjw_wBDKk0WEeDJQ"
+ authors="Chris Sibbald" changeDate="2006-12-22T06:19:44.000-0800" changeDescription="Added term definition for "requirement"."
+ version="0.2">
+ <mainDescription><ol>
+ <li>
+ A capability needed by the user to solve a problem [in order to] to achieve an objective
+ </li>
+ <li>
+ A capability that must be met or possessed by a system or system component to satisfy a contract, standard,
+ specification, or other formally imposed documentation <a class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/references_6CCF393.html"
+ guid="_9ToeIB83Edqsvps02rpOOg">[THA00]</a><br />
+ </li>
+</ol></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/core.tech.common.base/plugin.xmi b/praclib/temp/core.tech.common.base/plugin.xmi
new file mode 100644
index 0000000..f9a693c
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/plugin.xmi
@@ -0,0 +1,716 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_OOK_8AouEdyhlpBPrduOMw"
+ guid="_OOK_8AouEdyhlpBPrduOMw">
+ <resourceDescriptors xmi:id="_m-xmhfL5Edm6Nvont3uinw" id="_zHTQUKYSEdmvhNXG0Oc2uA"
+ uri="workproducts/vision.xmi"/>
+ <resourceDescriptors xmi:id="_2soicNb2Edq_LtLvi4w2yw" id="-_dNuyh-0q5vpCiIiLfbj6w"
+ uri="workproducts/system_wide_requirements.xmi"/>
+ <resourceDescriptors xmi:id="_m-SeUPL5Edm6Nvont3uinw" id="_zHZW8qYSEdmvhNXG0Oc2uA"
+ uri="workproducts/use_case.xmi"/>
+ <resourceDescriptors xmi:id="_zdSc0dPGEduegN_z1rVgJA" id="-kQg7MSGPB3RPjrplyxwimQ"
+ uri="workproducts/use_case_model.xmi"/>
+ <resourceDescriptors xmi:id="_m_QHo_L5Edm6Nvont3uinw" id="_NqePEKeqEdmKDbQuyzCoqQ"
+ uri="workproducts/test_log.xmi"/>
+ <resourceDescriptors xmi:id="_lXzjoOz6Edq2wJOsmRwmhg" id="-BQLZ5GRUNrMdU6XeZAfe9Q"
+ uri="guidances/concepts/use_case.xmi"/>
+ <resourceDescriptors xmi:id="_m-3tIvL5Edm6Nvont3uinw" id="_qktWQMM0EdmSIPI87WLu3g"
+ uri="guidances/checklists/vision.xmi"/>
+ <resourceDescriptors xmi:id="_-KDQoAhWEduRe8TeoBmuGg" id="-yEWkrWZ3VUcjZPhq6bvScg"
+ uri="guidances/concepts/use_case_model.xmi"/>
+ <resourceDescriptors xmi:id="_nuo9MPL5Edm6Nvont3uinw" id="_On0agNSAEdmLhZ9H5Plxyw"
+ uri="guidances/guidelines/req_gathering_techniques.xmi"/>
+ <resourceDescriptors xmi:id="_BW4HgNcLEdqz_d2XWoVt6Q" id="-AJQLv2ldVv5KN9eUbdQe_g"
+ uri="guidances/guidelines/writing_good_requirements.xmi"/>
+ <resourceDescriptors xmi:id="_1kU3wO0JEdqHTdbLTmC5IQ" id="-Q72-dNdHnZ93aRXAB_d34A"
+ uri="guidances/guidelines/requirement_pitfalls.xmi"/>
+ <resourceDescriptors xmi:id="_BwXDIMDqEduTGJ8i4u8TMw" id="-aN0zy068ovKHgmkkoYqoYQ"
+ uri="guidances/concepts/actor.xmi"/>
+ <resourceDescriptors xmi:id="_m-xmg_L5Edm6Nvont3uinw" id="_KEldgMM1EdmSIPI87WLu3g"
+ uri="guidances/checklists/actor.xmi"/>
+ <resourceDescriptors xmi:id="_4mOd0A4LEduibvKwrGxWxA" id="-mAo18f36rZ1R98kpZX7HMw"
+ uri="guidances/guidelines/example_design_mechanisms.xmi"/>
+ <resourceDescriptors xmi:id="_3uSHEH3fEdyCW99nbuTKkA" id="-fCBrf_5JlrmuKgyrCaKGOA"
+ uri="guidances/concepts/requirement_attributes.xmi"/>
+ <resourceDescriptors xmi:id="_3vLe8H3fEdyCW99nbuTKkA" id="-2o1pXjHpSEPN_rohLce5jA"
+ uri="guidances/checklists/general_requirements.xmi"/>
+ <resourceDescriptors xmi:id="_wNmVIH3lEdyCW99nbuTKkA" id="-pNA0DbSdSoUqnjQIiOeHcQ"
+ uri="guidances/guidelines/effective_req_reviews.xmi"/>
+ <resourceDescriptors xmi:id="_nGbtsfL5Edm6Nvont3uinw" id="_uqL2gMM3EdmSIPI87WLu3g"
+ uri="guidances/concepts/test_ideas.xmi"/>
+ <resourceDescriptors xmi:id="_nC-xEfL5Edm6Nvont3uinw" id="_4LuPMMPcEdmbOvqy4O0adg"
+ uri="guidances/checklists/test_script.xmi"/>
+ <resourceDescriptors xmi:id="_nDE3sPL5Edm6Nvont3uinw" id="_y-_PIMPdEdmbOvqy4O0adg"
+ uri="guidances/concepts/types_of_test.xmi"/>
+ <resourceDescriptors xmi:id="_nt4IMfL5Edm6Nvont3uinw" id="_s60KoMM3EdmSIPI87WLu3g"
+ uri="guidances/guidelines/test_suite.xmi"/>
+ <resourceDescriptors xmi:id="_nu7REPL5Edm6Nvont3uinw" id="_y3rxsMM3EdmSIPI87WLu3g"
+ uri="guidances/guidelines/test_ideas.xmi"/>
+ <resourceDescriptors xmi:id="_ieTdoBhBEduxCP6DVVLxsA" id="-GNUrr3mpSwOOaOKWSuftMg"
+ uri="guidances/checklists/test_data.xmi"/>
+ <resourceDescriptors xmi:id="_hwX4sE_8Edu-kbBL8pBzSQ" id="-9gUpkUYqONF3x8UWwAO_zw"
+ uri="guidances/concepts/failure_analysis_rpt_creation.xmi"/>
+ <resourceDescriptors xmi:id="_nC4qcPL5Edm6Nvont3uinw" id="_kwHAgMPbEdmbOvqy4O0adg"
+ uri="guidances/checklists/test_case.xmi"/>
+ <resourceDescriptors xmi:id="_m_QHovL5Edm6Nvont3uinw" id="_NqYIcqeqEdmKDbQuyzCoqQ"
+ uri="workproducts/test_script.xmi"/>
+ <resourceDescriptors xmi:id="_m_QHoPL5Edm6Nvont3uinw" id="_NqYIdKeqEdmKDbQuyzCoqQ"
+ uri="workproducts/test_case.xmi"/>
+ <resourceDescriptors xmi:id="_nu7REfL5Edm6Nvont3uinw" id="_vuwC4MPcEdmbOvqy4O0adg"
+ uri="guidances/guidelines/programming_automated_tests.xmi"/>
+ <resourceDescriptors xmi:id="_nu7REvL5Edm6Nvont3uinw" id="_8ngBgMPdEdmbOvqy4O0adg"
+ uri="guidances/guidelines/maintaining_automated_test_suite.xmi"/>
+ <resourceDescriptors xmi:id="_kIZk4bUNEdqI644ssJaKYg" id="-0sCBiohjw_wBDKk0WEeDJQ"
+ uri="guidances/termdefinitions/requirement.xmi"/>
+ <resourceDescriptors xmi:id="_pyUo0CGMEdu3VKXZx45D3A" id="-kw2vYHKDkWv2tZrDMrBPNA"
+ uri="guidances/checklists/system_wide_requirements.xmi"/>
+ <resourceDescriptors xmi:id="_e_SvIO0KEdqHTdbLTmC5IQ" id="-TksCtMgc0b4QqzwzniGvIw"
+ uri="guidances/concepts/traceability.xmi"/>
+ <resourceDescriptors xmi:id="_beLg0UvpEdunZcj9T5hrMQ" id="-Wh-byAGHoy_gGry0Jq6VaA"
+ uri="guidances/termdefinitions/build.xmi"/>
+ <resourceDescriptors xmi:id="_i5pNMDFYEduMqpUNhaTSRA" id="-fj_9xjbrpaYNSETyCz5yJg"
+ uri="guidances/concepts/refactoring.xmi"/>
+ <resourceDescriptors xmi:id="_m_D6Y_L5Edm6Nvont3uinw" id="_QvmkAMM1EdmSIPI87WLu3g"
+ uri="guidances/concepts/pattern.xmi"/>
+ <resourceDescriptors xmi:id="_0XXQsA4LEduibvKwrGxWxA" id="-Rex8oOBv985RruZNrCW0rg"
+ uri="guidances/concepts/implementation_mechanism.xmi"/>
+ <resourceDescriptors xmi:id="_xCNSwA4LEduibvKwrGxWxA" id="-EG22TRyJ5TDKW6U88AXfhw"
+ uri="guidances/concepts/design_mechanism.xmi"/>
+ <resourceDescriptors xmi:id="_hQyYcEvEEdunZcj9T5hrMQ" id="-vq2pL6yQuqGhql9Wo_Av4w"
+ uri="guidances/termdefinitions/furps.xmi"/>
+ <resourceDescriptors xmi:id="_HKvSQUvoEdunZcj9T5hrMQ" id="-YMvJ5LwexkcVWWqLdm5-nQ"
+ uri="guidances/termdefinitions/architecture.xmi"/>
+ <resourceDescriptors xmi:id="_m_D6ZPL5Edm6Nvont3uinw" id="_TZiasMM1EdmSIPI87WLu3g"
+ uri="guidances/concepts/component.xmi"/>
+ <resourceDescriptors xmi:id="_kGVesUvDEdunZcj9T5hrMQ" id="-BWZsh3vKrqSOzfkBJmDTLA"
+ uri="guidances/termdefinitions/component.xmi"/>
+ <resourceDescriptors xmi:id="_YI8eEMVxEduLYZUGfgZrkQ" id="-UQ_e8kozIP11Xu008RJd-A"
+ uri="guidances/concepts/software_architecture.xmi"/>
+ <resourceDescriptors xmi:id="_Z7gJgBapEduSTJywppIxVQ" id="-Of51hmgdsO_U2-pnbJ67Cg"
+ uri="guidances/concepts/business_pattern.xmi"/>
+ <resourceDescriptors xmi:id="_WK10YUvoEdunZcj9T5hrMQ" id="-VJBtRm2brEKpRlnLWNF8_g"
+ uri="guidances/termdefinitions/pattern.xmi"/>
+ <resourceDescriptors xmi:id="_g5NaAB85Edqsvps02rpOOg" id="-aCI9T-9TIe8D35yXBU6qvg"
+ uri="guidances/supportingmaterials/tech_references.xmi"/>
+ <resourceDescriptors xmi:id="_KYamMJ01EdyQ3oTO93enUw" id="-HPCdXGOQ2SGSCHZaDEKJRg"
+ uri="workproducts/implementation.xmi"/>
+ <resourceDescriptors xmi:id="_0nV8oNk1Edq2Q8qZoWbvGA" id="-T2IeqdOunweffIDgL-aM0w"
+ uri="guidances/checklists/use_case.xmi"/>
+ <resourceDescriptors xmi:id="_mvi3tvL5Edm6Nvont3uinw" id="_MqODAMM1EdmSIPI87WLu3g"
+ uri="guidances/checklists/use_case_model.xmi"/>
+ <resourceDescriptors xmi:id="_rhMooJI3EdyQN4nDrVqPtw" id="-awaQ_2dwhGyKRoVKQ-esPQ"
+ uri="guidances/guidelines/entity_control_boundary_pattern.xmi"/>
+ <resourceDescriptors xmi:id="_WES08O0IEdqHTdbLTmC5IQ" id="-3SXuKijeVOZalgLPgWRyFA"
+ uri="guidances/concepts/system_wide_requirements.xmi"/>
+ <resourceDescriptors xmi:id="_9DG9UY5fEdyO5aWob1UGDA" id="-zGnAaKUwKnn2pPANr7E0MQ"
+ uri="guidances/templates/use_case_specification.xmi"/>
+ <resourceDescriptors xmi:id="_vA3xoI5fEdyO5aWob1UGDA" id="-13wK-dfNa9N1G8Ob27m-Og"
+ uri="guidances/templates/systemwide_requirements_specification.xmi"/>
+ <resourceDescriptors xmi:id="_WG7AEY5gEdyO5aWob1UGDA" id="-DUD2tbhBn23i6Jm6gcoN9Q"
+ uri="guidances/templates/vision.xmi"/>
+ <resourceDescriptors xmi:id="_CPn-wMNrEdu2IdAIaWZyAw" id="-JviMIao63C7w9C8W6iPJrw"
+ uri="guidances/examples/uc_model_evolve.xmi"/>
+ <resourceDescriptors xmi:id="_7KWL4MNvEdu2IdAIaWZyAw" id="-qq-9Brh5oa6H3lsdp-m8mQ"
+ uri="guidances/examples/use_case_spec.xmi"/>
+ <resourceDescriptors xmi:id="_ovE-8A4LEduibvKwrGxWxA" id="-SJrpVySJ2npYs8NwGvnHjw"
+ uri="guidances/concepts/arch_mechanism.xmi"/>
+ <resourceDescriptors xmi:id="_HsocQA4MEduibvKwrGxWxA" id="-EytH4BCNGiHF6pZrp8ISCw"
+ uri="guidances/concepts/arch_significant_requirements.xmi"/>
+ <resourceDescriptors xmi:id="_m-3tIfL5Edm6Nvont3uinw" id="_eUfzwMMyEdmdo9HxCRR_Gw"
+ uri="guidances/concepts/requirements.xmi"/>
+ <resourceDescriptors xmi:id="_nGPgcvL5Edm6Nvont3uinw" id="_S8KCcMP2EdmWKcx6ixEiwg"
+ uri="guidances/concepts/analysis_mechanism.xmi"/>
+ <resourceDescriptors xmi:id="_ZtB40NvfEduv2KOT-Teh6w" id="-0R8BZWlcCQ3Rj84jY2M3Kw"
+ uri="guidances/concepts/executable_arch.xmi"/>
+ <resourceDescriptors xmi:id="_nuo9MvL5Edm6Nvont3uinw" id="_iCwb8MM3EdmSIPI87WLu3g"
+ uri="guidances/guidelines/repres_interfaces_to_ext_systems.xmi"/>
+ <resourceDescriptors xmi:id="_DLM38ColEduK2emCyq5fBw" id="-X7QSjItNBz7w8603yBCv0Q"
+ uri="guidances/guidelines/abstract_away_complexity.xmi"/>
+ <resourceDescriptors xmi:id="_q-5HYUvCEdunZcj9T5hrMQ" id="-0vih7gB84YYDheaH7jeYFQ"
+ uri="guidances/termdefinitions/architectural_view.xmi"/>
+ <resourceDescriptors xmi:id="_aenL8UvCEdunZcj9T5hrMQ" id="-Vvwb6EupIB9kfSQ_mhjURA"
+ uri="guidances/termdefinitions/architectural_mechanism.xmi"/>
+ <resourceDescriptors xmi:id="_m-9zxPL5Edm6Nvont3uinw" id="_SB1n8MM1EdmSIPI87WLu3g"
+ uri="guidances/concepts/visual_modeling.xmi"/>
+ <resourceDescriptors xmi:id="_WFzxwKrPEdu6T6WyNqBzqQ" id="-zfl87vJBFdinDB02ArLXOQ"
+ uri="guidances/concepts/component.vm.xmi"/>
+ <resourceDescriptors xmi:id="_VPIPILcJEduRNaXpzCOLXQ" id="-OcMsciNn-UtD9fTHj26LGA"
+ uri="guidances/guidelines/abstract_away_complexity.vm.xmi"/>
+ <resourceDescriptors xmi:id="_AtgW0O0PEduUpsu85bVhiQ" id="-Vp61zQMUoP-Icm5jgDar7A"
+ uri="guidances/guidelines/software_reuse.xmi"/>
+ <resourceDescriptors xmi:id="_nuo9M_L5Edm6Nvont3uinw" id="_lbGQwMM3EdmSIPI87WLu3g"
+ uri="guidances/guidelines/layering.xmi"/>
+ <resourceDescriptors xmi:id="_w-OGMdc8Edyd7OybSySFxg" id="-QB0WnHnpcK1VJbdJJ5QJ5A"
+ uri="guidances/concepts/arch_views_viewpoints.xmi"/>
+ <resourceDescriptors xmi:id="_En710Om-Edupia_tZIXEqg" id="-8LfKJab2khAUjdmnImaXPA"
+ uri="guidances/examples/architectural_mechanism_attributes.xmi"/>
+ <resourceDescriptors xmi:id="_cUTLIO9pEdu635i_iQ5Jag" id="-V6Hddpuwu3wvd9R0l4fL7Q"
+ uri="guidances/examples/architectural_mechanisms.xmi"/>
+ <resourceDescriptors xmi:id="_fMP7UNpbEdyP58ppo1Ieaw" id="-Mm7s8vlK5CaZZ_Msx8reCQ"
+ uri="guidances/concepts/arch_goals.xmi"/>
+ <resourceDescriptors xmi:id="_BCNE8dpjEdyP58ppo1Ieaw" id="-je0zRqgX0Tg_761Z77cIkg"
+ uri="guidances/concepts/arch_constraints.xmi"/>
+ <resourceDescriptors xmi:id="_ysEigNqGEdy88NBoQgfGyg" id="-HJbvivaRmrZ6rdQcdFd78Q"
+ uri="guidances/concepts/key_abstractions.xmi"/>
+ <resourceDescriptors xmi:id="_rcCKUdr9EdyXE6np2_hUMA" id="-QklqSGB4aD07vUpfubpMJg"
+ uri="guidances/guidelines/using_visual_modeling.xmi"/>
+ <resourceDescriptors xmi:id="_EV_AcdtAEdyEW4klSH3vRA" id="-sKBCb98PYCcliL0zVljcyQ"
+ uri="guidances/examples/four_plus_one_view_of_arch.xmi"/>
+ <resourceDescriptors xmi:id="_4QxaQY5gEdyO5aWob1UGDA" id="-PHKmXwkVhDR81vcyAQAkxQ"
+ uri="guidances/templates/manual_test_script.xmi"/>
+ <resourceDescriptors xmi:id="_GsJCYOGJEdyXPePcD0t0WQ" id="-JrYzWdOXPOZBIVGWibK1Bw"
+ uri="guidances/templates/test_case.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_OOB2AAouEdyhlpBPrduOMw" name="core.tech.common.base"
+ guid="_OOB2AAouEdyhlpBPrduOMw" briefDescription="This plug-in serves as a collection point for commonly used work products."
+ changeDate="2008-02-11T13:07:32.437-0800">
+ <copyrightStatement href="uma://_iVydgENdEdy245g62lfWcA#_cTs20KzREduOqvpk_MDLfQ"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_OOB2AQouEdyhlpBPrduOMw"
+ name="Content" guid="_OOB2AQouEdyhlpBPrduOMw">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_OOB2AgouEdyhlpBPrduOMw"
+ name="Categories" guid="_OOB2AgouEdyhlpBPrduOMw">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_OOB2AwouEdyhlpBPrduOMw"
+ name="Domains" guid="_OOB2AwouEdyhlpBPrduOMw"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_OOB2BAouEdyhlpBPrduOMw"
+ name="Disciplines" guid="_OOB2BAouEdyhlpBPrduOMw"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_OOB2BQouEdyhlpBPrduOMw"
+ name="RoleSets" guid="_OOB2BQouEdyhlpBPrduOMw"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_OOB2BgouEdyhlpBPrduOMw"
+ name="WP Types" guid="_OOB2BgouEdyhlpBPrduOMw"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_OOB2BwouEdyhlpBPrduOMw"
+ name="Tools" guid="_OOB2BwouEdyhlpBPrduOMw"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_OOB2CAouEdyhlpBPrduOMw"
+ name="StandardCategories" guid="_OOB2CAouEdyhlpBPrduOMw"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_OOB2CQouEdyhlpBPrduOMw"
+ name="CustomCategories" guid="_OOB2CQouEdyhlpBPrduOMw">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_OOB2CgouEdyhlpBPrduOMw"
+ name="Hidden" guid="_OOB2CgouEdyhlpBPrduOMw">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_OOB2CwouEdyhlpBPrduOMw"
+ name="Custom Categories" guid="_OOB2CwouEdyhlpBPrduOMw" presentationName="Custom Categories"
+ categorizedElements="_Z7vl8NjlEdyAi9EWyDeJBg"/>
+ </childPackages>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_Z7vl8NjlEdyAi9EWyDeJBg"
+ name="contributions_to_nav_building_blocks" guid="_Z7vl8NjlEdyAi9EWyDeJBg"
+ presentationName="Contributions to Navigation Building Blocks" categorizedElements="_cXwVYNjlEdyAi9EWyDeJBg _cXwVYdjlEdyAi9EWyDeJBg _6GVeINjlEdyAi9EWyDeJBg _CqGO8NjmEdyAi9EWyDeJBg _J6IHANjmEdyAi9EWyDeJBg _Q1R7QNjmEdyAi9EWyDeJBg"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_cXwVYNjlEdyAi9EWyDeJBg"
+ name="guideline_list.assign" guid="_cXwVYNjlEdyAi9EWyDeJBg" variabilityType="contributes"
+ categorizedElements="_0kF5kMlgEdmt3adZL5Dmdw _0j5sUMlgEdmt3adZL5Dmdw _0jzlsMlgEdmt3adZL5Dmdw _0aDz0MlgEdmt3adZL5Dmdw _E-dPIL-GEdqb7N6KIeDL8Q _OnoNQNSAEdmLhZ9H5Plxyw _1AOsMO0JEdqHTdbLTmC5IQ _6jXzYNcKEdqz_d2XWoVt6Q _uF-QYEAhEdq_UJTvM1DM2Q _4k_Hsg4LEduibvKwrGxWxA _0gpkAMlgEdmt3adZL5Dmdw _0gjdYMlgEdmt3adZL5Dmdw _we3F4ACpEdu8m4dIntu6jA _vO2uoO0OEduUpsu85bVhiQ _0SsecNr8EdyXE6np2_hUMA">
+ <methodElementProperty xmi:id="_x8ykINjlEdyAi9EWyDeJBg" name="CategoryElementsSortType"
+ value="Alphabetic"/>
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4ZcRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_cXwVYdjlEdyAi9EWyDeJBg"
+ name="concept_list.assign" guid="_cXwVYdjlEdyAi9EWyDeJBg" variabilityType="contributes"
+ categorizedElements="_zGqO0MDpEduTGJ8i4u8TMw _0jhR0MlgEdmt3adZL5Dmdw _VQ268O0KEdqHTdbLTmC5IQ _VXZ5wO0IEdqHTdbLTmC5IQ _0jnYcMlgEdmt3adZL5Dmdw _0aJ6cMlgEdmt3adZL5Dmdw _KudM0NcJEdqz_d2XWoVt6Q _2jyfUAhVEduRe8TeoBmuGg _0Wh-sMlgEdmt3adZL5Dmdw _eYtQQO0KEdqHTdbLTmC5IQ _0LcUkA4LEduibvKwrGxWxA _Poc7IPDzEdqYgerqi84oCA _w2ACwA4LEduibvKwrGxWxA _HZGFsKrPEdu6T6WyNqBzqQ _0gvqoMlgEdmt3adZL5Dmdw _HrZGIA4MEduibvKwrGxWxA _mzxI0A4LEduibvKwrGxWxA _kgtcoNc8Edyd7OybSySFxg _0YP18MlgEdmt3adZL5Dmdw _O1kAANvfEduv2KOT-Teh6w __O7tAMVvEduLYZUGfgZrkQ _0XY6UMlgEdmt3adZL5Dmdw _Z53x0BapEduSTJywppIxVQ _0YJvUMlgEdmt3adZL5Dmdw _jdKSsNpiEdyP58ppo1Ieaw _HlRqANpbEdyP58ppo1Ieaw _pLEGUNqGEdy88NBoQgfGyg">
+ <methodElementProperty xmi:id="_242OcNjlEdyAi9EWyDeJBg" name="CategoryElementsSortType"
+ value="Alphabetic"/>
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4Y8RdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_6GVeINjlEdyAi9EWyDeJBg"
+ name="checklist_list.assign" guid="_6GVeINjlEdyAi9EWyDeJBg" variabilityType="contributes"
+ categorizedElements="_0VrDEMlgEdmt3adZL5Dmdw _jxn9EO0HEdqHTdbLTmC5IQ _Vael8CGMEdu3VKXZx45D3A _0Zxf8MlgEdmt3adZL5Dmdw _KZQJMBhBEduxCP6DVVLxsA _0Z9tMMlgEdmt3adZL5Dmdw _0kNwINk1Edq2Q8qZoWbvGA _0U6OEMlgEdmt3adZL5Dmdw _0WoFUMlgEdmt3adZL5Dmdw">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_pGt9MMReEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_CqGO8NjmEdyAi9EWyDeJBg"
+ name="example_list.assign" guid="_CqGO8NjmEdyAi9EWyDeJBg" variabilityType="contributes"
+ categorizedElements="_eQ_s8Om5Edupia_tZIXEqg _O39h0O9pEdu635i_iQ5Jag _t4QdAMNqEdu2IdAIaWZyAw _JLOiIMNvEdu2IdAIaWZyAw _4bC4cNs_EdyEW4klSH3vRA">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4ZMRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_J6IHANjmEdyAi9EWyDeJBg"
+ name="template_list.assign" guid="_J6IHANjmEdyAi9EWyDeJBg" variabilityType="contributes"
+ categorizedElements="_m7p-AI5fEdyO5aWob1UGDA _3Y3XUI5fEdyO5aWob1UGDA _DtlRQI5gEdyO5aWob1UGDA">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4Z8RdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_Q1R7QNjmEdyAi9EWyDeJBg"
+ name="artifact_list.assign" guid="_Q1R7QNjmEdyAi9EWyDeJBg" variabilityType="contributes"
+ categorizedElements="_JqYbgJ01EdyQ3oTO93enUw _BVh9cL-CEdqb7N6KIeDL8Q _0ZS-0MlgEdmt3adZL5Dmdw _0ZlSsMlgEdmt3adZL5Dmdw _0ZfMEMlgEdmt3adZL5Dmdw _0VGbUMlgEdmt3adZL5Dmdw _W2SgEDR5EdutE_HNDTJk5Q _0WVxcMlgEdmt3adZL5Dmdw">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4YMRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_OOB2DAouEdyhlpBPrduOMw"
+ name="CoreContent" guid="_OOB2DAouEdyhlpBPrduOMw">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_RhLBwAouEdyhlpBPrduOMw"
+ name="Technical Open Source Work Products" guid="_RhLBwAouEdyhlpBPrduOMw">
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_0WVxcMlgEdmt3adZL5Dmdw"
+ name="vision" guid="_0WVxcMlgEdmt3adZL5Dmdw" briefDescription="This artifact contains the definition of the stakeholders' view of the technical solution to be developed, specified in terms of the stakeholders' key needs and features. It contains an outline of the envisioned core requirements for the system."
+ presentationName="Vision" checklists="_0WoFUMlgEdmt3adZL5Dmdw">
+ <presentation xmi:id="_zHTQUKYSEdmvhNXG0Oc2uA" href="uma://_zHTQUKYSEdmvhNXG0Oc2uA#_zHTQUKYSEdmvhNXG0Oc2uA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_BVh9cL-CEdqb7N6KIeDL8Q"
+ name="system_wide_requirements" guid="_BVh9cL-CEdqb7N6KIeDL8Q" briefDescription="This artifact captures quality attributes and constraints that have system-wide scope. It also captures system-wide functional requirements."
+ presentationName="System-Wide Requirements" guidelines="_6jXzYNcKEdqz_d2XWoVt6Q">
+ <presentation xmi:id="-_dNuyh-0q5vpCiIiLfbj6w" href="uma://-_dNuyh-0q5vpCiIiLfbj6w#-_dNuyh-0q5vpCiIiLfbj6w"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_0VGbUMlgEdmt3adZL5Dmdw"
+ name="use_case" guid="_0VGbUMlgEdmt3adZL5Dmdw" briefDescription="This artifact captures system behavior that yields an observable result of value to those interacting with the system. "
+ presentationName="Use Case" conceptsAndPapers="_KudM0NcJEdqz_d2XWoVt6Q"
+ checklists="_0kNwINk1Edq2Q8qZoWbvGA">
+ <presentation xmi:id="_zHZW8qYSEdmvhNXG0Oc2uA" href="uma://_zHZW8qYSEdmvhNXG0Oc2uA#_zHZW8qYSEdmvhNXG0Oc2uA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_W2SgEDR5EdutE_HNDTJk5Q"
+ name="use_case_model" guid="_W2SgEDR5EdutE_HNDTJk5Q" briefDescription="This artifact captures a model of the system's intended functions and its environment, and serves as a contract between the customer and the team."
+ presentationName="Use-Case Model" conceptsAndPapers="_KudM0NcJEdqz_d2XWoVt6Q _2jyfUAhVEduRe8TeoBmuGg _zGqO0MDpEduTGJ8i4u8TMw"
+ checklists="_0U6OEMlgEdmt3adZL5Dmdw">
+ <presentation xmi:id="-kQg7MSGPB3RPjrplyxwimQ" href="uma://-kQg7MSGPB3RPjrplyxwimQ#-kQg7MSGPB3RPjrplyxwimQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_KudM0NcJEdqz_d2XWoVt6Q"
+ name="use_case" guid="_KudM0NcJEdqz_d2XWoVt6Q" briefDescription="A use case describes what the system must do to provide value to the stakeholders."
+ presentationName="Use Case">
+ <presentation xmi:id="-BQLZ5GRUNrMdU6XeZAfe9Q" href="uma://-BQLZ5GRUNrMdU6XeZAfe9Q#-BQLZ5GRUNrMdU6XeZAfe9Q"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Checklist" xmi:id="_0WoFUMlgEdmt3adZL5Dmdw"
+ name="vision" guid="_0WoFUMlgEdmt3adZL5Dmdw" briefDescription="This check list provides questions to verify that the Vision is described in a consistent and complete manner."
+ presentationName="Vision">
+ <presentation xmi:id="_qktWQMM0EdmSIPI87WLu3g" href="uma://_qktWQMM0EdmSIPI87WLu3g#_qktWQMM0EdmSIPI87WLu3g"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_2jyfUAhVEduRe8TeoBmuGg"
+ name="use_case_model" guid="_2jyfUAhVEduRe8TeoBmuGg" briefDescription="This artifact is a model of the system's intended functions and its surroundings, and serves as a contract between the customer and the project team."
+ presentationName="Use-Case Model">
+ <presentation xmi:id="-yEWkrWZ3VUcjZPhq6bvScg" href="uma://-yEWkrWZ3VUcjZPhq6bvScg#-yEWkrWZ3VUcjZPhq6bvScg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_zGqO0MDpEduTGJ8i4u8TMw"
+ name="actor" guid="_zGqO0MDpEduTGJ8i4u8TMw" briefDescription="An Actor is a role that a person or external system plays when interacting with a system. Instances of an Actor can be an individual or an external system."
+ presentationName="Actor">
+ <presentation xmi:id="-aN0zy068ovKHgmkkoYqoYQ" href="uma://-aN0zy068ovKHgmkkoYqoYQ#-aN0zy068ovKHgmkkoYqoYQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Checklist" xmi:id="_0VrDEMlgEdmt3adZL5Dmdw"
+ name="actor" guid="_0VrDEMlgEdmt3adZL5Dmdw" briefDescription="This check list provides questions to help ensure that all actors, and only valid actors, have been identified and described correctly."
+ presentationName="Actor">
+ <presentation xmi:id="_KEldgMM1EdmSIPI87WLu3g" href="uma://_KEldgMM1EdmSIPI87WLu3g#_KEldgMM1EdmSIPI87WLu3g"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_VQ268O0KEdqHTdbLTmC5IQ"
+ name="requirement_attributes" guid="_VQ268O0KEdqHTdbLTmC5IQ" briefDescription="Requirements attributes capture additional information, such as risk, planned iteration, source of requirement, about each requirement. This additional information is used to manage the project."
+ presentationName="Requirement Attributes">
+ <presentation xmi:id="-fCBrf_5JlrmuKgyrCaKGOA" href="uma://-fCBrf_5JlrmuKgyrCaKGOA#-fCBrf_5JlrmuKgyrCaKGOA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Checklist" xmi:id="_jxn9EO0HEdqHTdbLTmC5IQ"
+ name="general_requirements" guid="_jxn9EO0HEdqHTdbLTmC5IQ" briefDescription="This checklist provides guidance on assessing the quality of requirements."
+ presentationName="General Requirements">
+ <presentation xmi:id="-2o1pXjHpSEPN_rohLce5jA" href="uma://-2o1pXjHpSEPN_rohLce5jA#-2o1pXjHpSEPN_rohLce5jA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_0jhR0MlgEdmt3adZL5Dmdw"
+ name="failure_analysis_rpt_creation" guid="_0jhR0MlgEdmt3adZL5Dmdw"
+ briefDescription="This concept addresses how to conduct failure analysis based on the execution of tests. The result of this analysis can take the form of a failure analysis report."
+ presentationName="Failure Analysis and Report Creation">
+ <presentation xmi:id="-9gUpkUYqONF3x8UWwAO_zw" href="uma://-9gUpkUYqONF3x8UWwAO_zw#-9gUpkUYqONF3x8UWwAO_zw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_0jnYcMlgEdmt3adZL5Dmdw"
+ name="test_ideas" guid="_0jnYcMlgEdmt3adZL5Dmdw" briefDescription="A list of test ideas sorted in decreasing order of importance and associated with specific testing strategies used to create executable tests."
+ presentationName="Test Ideas">
+ <presentation xmi:id="_uqL2gMM3EdmSIPI87WLu3g" href="uma://_uqL2gMM3EdmSIPI87WLu3g#_uqL2gMM3EdmSIPI87WLu3g"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_0aJ6cMlgEdmt3adZL5Dmdw"
+ name="types_of_test" guid="_0aJ6cMlgEdmt3adZL5Dmdw" briefDescription="Testing is applied to different types of targets, in different stages or levels of work effort. This Concept introduces various types of test."
+ presentationName="Types of Test">
+ <presentation xmi:id="_y-_PIMPdEdmbOvqy4O0adg" href="uma://_y-_PIMPdEdmbOvqy4O0adg#_y-_PIMPdEdmbOvqy4O0adg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Checklist" xmi:id="_0Zxf8MlgEdmt3adZL5Dmdw"
+ name="test_case" guid="_0Zxf8MlgEdmt3adZL5Dmdw" briefDescription="This checklist provides questions to verify that test cases are created in a consistent and complete manner."
+ presentationName="Test Case">
+ <presentation xmi:id="_kwHAgMPbEdmbOvqy4O0adg" href="uma://_kwHAgMPbEdmbOvqy4O0adg#_kwHAgMPbEdmbOvqy4O0adg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Checklist" xmi:id="_KZQJMBhBEduxCP6DVVLxsA"
+ name="test_data" guid="_KZQJMBhBEduxCP6DVVLxsA" briefDescription="This checklist provides questions to verify that test data is created in a consistent and complete manner."
+ presentationName="Test Data">
+ <presentation xmi:id="-GNUrr3mpSwOOaOKWSuftMg" href="uma://-GNUrr3mpSwOOaOKWSuftMg#-GNUrr3mpSwOOaOKWSuftMg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Checklist" xmi:id="_0Z9tMMlgEdmt3adZL5Dmdw"
+ name="test_script" guid="_0Z9tMMlgEdmt3adZL5Dmdw" briefDescription="This checklist provides questions to verify that tests are created in a consistent and complete manner."
+ presentationName="Test Script">
+ <presentation xmi:id="_4LuPMMPcEdmbOvqy4O0adg" href="uma://_4LuPMMPcEdmbOvqy4O0adg#_4LuPMMPcEdmbOvqy4O0adg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_0ZS-0MlgEdmt3adZL5Dmdw"
+ name="test_case" guid="_0ZS-0MlgEdmt3adZL5Dmdw" briefDescription="This artifact is the specification of a set of test inputs, execution conditions, and expected results, identified for the purpose of making an evaluation of some particular aspect of a scenario."
+ presentationName="Test Case" conceptsAndPapers="_0aJ6cMlgEdmt3adZL5Dmdw"
+ checklists="_0Zxf8MlgEdmt3adZL5Dmdw">
+ <presentation xmi:id="_NqYIdKeqEdmKDbQuyzCoqQ" href="uma://_NqYIdKeqEdmKDbQuyzCoqQ#_NqYIdKeqEdmKDbQuyzCoqQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_0ZfMEMlgEdmt3adZL5Dmdw"
+ name="test_script" guid="_0ZfMEMlgEdmt3adZL5Dmdw" briefDescription="This artifact contains the step-by-step instructions that realize a test, enabling its execution. These may take the form of either documented textual instructions that are executed manually or computer readable instructions that enable automated test execution."
+ presentationName="Test Script" checklists="_KZQJMBhBEduxCP6DVVLxsA _0Z9tMMlgEdmt3adZL5Dmdw"
+ guidelines="_0aDz0MlgEdmt3adZL5Dmdw _0j5sUMlgEdmt3adZL5Dmdw _0kF5kMlgEdmt3adZL5Dmdw">
+ <presentation xmi:id="_NqYIcqeqEdmKDbQuyzCoqQ" href="uma://_NqYIcqeqEdmKDbQuyzCoqQ#_NqYIcqeqEdmKDbQuyzCoqQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_0ZlSsMlgEdmt3adZL5Dmdw"
+ name="test_log" guid="_0ZlSsMlgEdmt3adZL5Dmdw" briefDescription="This artifact collects raw output captured during a unique execution of one or more tests for a single test cycle run."
+ presentationName="Test Log">
+ <presentation xmi:id="_NqePEKeqEdmKDbQuyzCoqQ" href="uma://_NqePEKeqEdmKDbQuyzCoqQ#_NqePEKeqEdmKDbQuyzCoqQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_JqYbgJ01EdyQ3oTO93enUw"
+ name="implementation" guid="_JqYbgJ01EdyQ3oTO93enUw" briefDescription="Software code files, data files, and supporting files such as online help files that represent the raw parts of a system that can be built."
+ presentationName="Implementation">
+ <presentation xmi:id="-HPCdXGOQ2SGSCHZaDEKJRg" href="uma://-HPCdXGOQ2SGSCHZaDEKJRg#-HPCdXGOQ2SGSCHZaDEKJRg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Checklist" xmi:id="_Vael8CGMEdu3VKXZx45D3A"
+ name="system_wide_requirements" guid="_Vael8CGMEdu3VKXZx45D3A" briefDescription="This check list is used to verify that all types of system-wide requirements are considered."
+ presentationName="System-Wide Requirements">
+ <presentation xmi:id="-kw2vYHKDkWv2tZrDMrBPNA" href="uma://-kw2vYHKDkWv2tZrDMrBPNA#-kw2vYHKDkWv2tZrDMrBPNA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Checklist" xmi:id="_0kNwINk1Edq2Q8qZoWbvGA"
+ name="use_case" guid="_0kNwINk1Edq2Q8qZoWbvGA" briefDescription="This checklist provides questions to verify that use cases are described in a consistent and complete manner."
+ presentationName="Use Case" variabilityType="replaces">
+ <presentation xmi:id="-T2IeqdOunweffIDgL-aM0w" href="uma://-T2IeqdOunweffIDgL-aM0w#-T2IeqdOunweffIDgL-aM0w"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Checklist" xmi:id="_0U6OEMlgEdmt3adZL5Dmdw"
+ name="use_case_model" guid="_0U6OEMlgEdmt3adZL5Dmdw" briefDescription="This checklist provides questions to verify that the use-case model is described in a consistent and complete manner."
+ presentationName="Use-Case Model">
+ <presentation xmi:id="_MqODAMM1EdmSIPI87WLu3g" href="uma://_MqODAMM1EdmSIPI87WLu3g#_MqODAMM1EdmSIPI87WLu3g"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_VXZ5wO0IEdqHTdbLTmC5IQ"
+ name="system_wide_requirements" guid="_VXZ5wO0IEdqHTdbLTmC5IQ" briefDescription="This concept describes the system-wide requirements"
+ presentationName="System-Wide Requirements [needs wording work]">
+ <presentation xmi:id="-3SXuKijeVOZalgLPgWRyFA" href="uma://-3SXuKijeVOZalgLPgWRyFA#-3SXuKijeVOZalgLPgWRyFA"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_1MdooMOlEdupeqHTre3HvQ"
+ name="Technical Open Source Guidance" guid="_1MdooMOlEdupeqHTre3HvQ" briefDescription="Included guidance applies to the elements in any context">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_9ncVUBEfEdyM7Iu0sxfrPA"
+ name="Test Guidance" guid="_9ncVUBEfEdyM7Iu0sxfrPA">
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_0kF5kMlgEdmt3adZL5Dmdw"
+ name="maintaining_automated_test_suite" guid="_0kF5kMlgEdmt3adZL5Dmdw"
+ briefDescription="This guideline explains ways to maintain automated test suites - collection of tests performed together for breadth and depth coverage."
+ presentationName="Maintaining Automated Test Suite">
+ <presentation xmi:id="_8ngBgMPdEdmbOvqy4O0adg" href="uma://_8ngBgMPdEdmbOvqy4O0adg#_8ngBgMPdEdmbOvqy4O0adg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_0j5sUMlgEdmt3adZL5Dmdw"
+ name="programming_automated_tests" guid="_0j5sUMlgEdmt3adZL5Dmdw"
+ briefDescription="This guideline discusses ways of structuring, recording, entering data, executing and handling errors in automated tests."
+ presentationName="Programming Automated Tests">
+ <presentation xmi:id="_vuwC4MPcEdmbOvqy4O0adg" href="uma://_vuwC4MPcEdmbOvqy4O0adg#_vuwC4MPcEdmbOvqy4O0adg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_0jzlsMlgEdmt3adZL5Dmdw"
+ name="test_ideas" guid="_0jzlsMlgEdmt3adZL5Dmdw" briefDescription="This guideline identifies common faults and mistakes done when developing software. It shows how to create test ideas from method calls, and from boolean and relational expressions."
+ presentationName="Test Ideas">
+ <presentation xmi:id="_y3rxsMM3EdmSIPI87WLu3g" href="uma://_y3rxsMM3EdmSIPI87WLu3g#_y3rxsMM3EdmSIPI87WLu3g"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_0aDz0MlgEdmt3adZL5Dmdw"
+ name="test_suite" guid="_0aDz0MlgEdmt3adZL5Dmdw" briefDescription="This guideline discusses how to maintain automated test suites."
+ presentationName="Test Suite">
+ <presentation xmi:id="_s60KoMM3EdmSIPI87WLu3g" href="uma://_s60KoMM3EdmSIPI87WLu3g#_s60KoMM3EdmSIPI87WLu3g"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_8oxCIMOlEdupeqHTre3HvQ"
+ name="Requirements Guidance" guid="_8oxCIMOlEdupeqHTre3HvQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_eYtQQO0KEdqHTdbLTmC5IQ"
+ name="traceability" guid="_eYtQQO0KEdqHTdbLTmC5IQ" briefDescription="Traceability is a term used to describe the establishment and maintenance of relationships between artifacts, such as a requirement and a design class or a requirement and a test case, so that you can track the completeness of work <strong> </strong>and assess the impact of changes."
+ presentationName="Traceability">
+ <presentation xmi:id="-TksCtMgc0b4QqzwzniGvIw" href="uma://-TksCtMgc0b4QqzwzniGvIw#-TksCtMgc0b4QqzwzniGvIw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_feKVQLULEdqI644ssJaKYg"
+ name="requirement" guid="_feKVQLULEdqI644ssJaKYg" presentationName="Requirements">
+ <presentation xmi:id="-0sCBiohjw_wBDKk0WEeDJQ" href="uma://-0sCBiohjw_wBDKk0WEeDJQ#-0sCBiohjw_wBDKk0WEeDJQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_ZH6M0EvEEdunZcj9T5hrMQ"
+ name="furps" guid="_ZH6M0EvEEdunZcj9T5hrMQ" presentationName="FURPS+">
+ <presentation xmi:id="-vq2pL6yQuqGhql9Wo_Av4w" href="uma://-vq2pL6yQuqGhql9Wo_Av4w#-vq2pL6yQuqGhql9Wo_Av4w"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_E-dPIL-GEdqb7N6KIeDL8Q"
+ name="effective_req_reviews" guid="_E-dPIL-GEdqb7N6KIeDL8Q" briefDescription="This guideline discusses how to conduct reviews with relevant stakeholders to ensure agreement, assess quality, and identify changes required."
+ presentationName="Effective Requirement Reviews">
+ <presentation xmi:id="-pNA0DbSdSoUqnjQIiOeHcQ" href="uma://-pNA0DbSdSoUqnjQIiOeHcQ#-pNA0DbSdSoUqnjQIiOeHcQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_OnoNQNSAEdmLhZ9H5Plxyw"
+ name="req_gathering_techniques" guid="_OnoNQNSAEdmLhZ9H5Plxyw" briefDescription="This guideline describes various techniques for gathering requirements."
+ presentationName="Requirements Gathering Techniques">
+ <presentation xmi:id="_On0agNSAEdmLhZ9H5Plxyw" href="uma://_On0agNSAEdmLhZ9H5Plxyw#_On0agNSAEdmLhZ9H5Plxyw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_1AOsMO0JEdqHTdbLTmC5IQ"
+ name="requirement_pitfalls" guid="_1AOsMO0JEdqHTdbLTmC5IQ" briefDescription="This guideline describes common pitfalls to avoid in defining and writing requirements. In some cases these are the inverse of the guidelines for writing good requirements, however, by showing examples of what NOT to do makes the explanation of what TO DO clearer."
+ presentationName="Requirement Pitfalls">
+ <presentation xmi:id="-Q72-dNdHnZ93aRXAB_d34A" href="uma://-Q72-dNdHnZ93aRXAB_d34A#-Q72-dNdHnZ93aRXAB_d34A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_6jXzYNcKEdqz_d2XWoVt6Q"
+ name="writing_good_requirements" guid="_6jXzYNcKEdqz_d2XWoVt6Q" briefDescription="This guideline describes ways of writing good requirements."
+ presentationName="Writing Requirements Statements">
+ <presentation xmi:id="-AJQLv2ldVv5KN9eUbdQe_g" href="uma://-AJQLv2ldVv5KN9eUbdQe_g#-AJQLv2ldVv5KN9eUbdQe_g"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_0Wh-sMlgEdmt3adZL5Dmdw"
+ name="requirements" guid="_0Wh-sMlgEdmt3adZL5Dmdw" briefDescription="This concept page provides an informal definition of requirements."
+ presentationName="Requirements">
+ <presentation xmi:id="_eUfzwMMyEdmdo9HxCRR_Gw" href="uma://_eUfzwMMyEdmdo9HxCRR_Gw#_eUfzwMMyEdmdo9HxCRR_Gw"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_cHHEIBEdEdyM7Iu0sxfrPA"
+ name="Implementation Guidance" guid="_cHHEIBEdEdyM7Iu0sxfrPA">
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_Z-AukEvpEdunZcj9T5hrMQ"
+ name="build" guid="_Z-AukEvpEdunZcj9T5hrMQ" presentationName="build">
+ <presentation xmi:id="-Wh-byAGHoy_gGry0Jq6VaA" href="uma://-Wh-byAGHoy_gGry0Jq6VaA#-Wh-byAGHoy_gGry0Jq6VaA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_0LcUkA4LEduibvKwrGxWxA"
+ name="implementation_mechanism" guid="_0LcUkA4LEduibvKwrGxWxA" briefDescription="A representation of an Architecture Mechanism that uses a specific programming language or product."
+ presentationName="Implementation Mechanism">
+ <presentation xmi:id="-Rex8oOBv985RruZNrCW0rg" href="uma://-Rex8oOBv985RruZNrCW0rg#-Rex8oOBv985RruZNrCW0rg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_1fu-oNvTEdyrWIQpneun6w"
+ name="arch_mechanism.impl" guid="_1fu-oNvTEdyrWIQpneun6w" variabilityType="contributes"
+ variabilityBasedOnElement="_mzxI0A4LEduibvKwrGxWxA" conceptsAndPapers="_0LcUkA4LEduibvKwrGxWxA"/>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_119G4NPSEduegN_z1rVgJA"
+ name="Design Guidance" guid="_119G4NPSEduegN_z1rVgJA">
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_w2ACwA4LEduibvKwrGxWxA"
+ name="design_mechanism" guid="_w2ACwA4LEduibvKwrGxWxA" briefDescription="A Design Mechanism is a concrete representation of an Architectural Mechanism."
+ presentationName="Design Mechanism">
+ <presentation xmi:id="-EG22TRyJ5TDKW6U88AXfhw" href="uma://-EG22TRyJ5TDKW6U88AXfhw#-EG22TRyJ5TDKW6U88AXfhw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_4k_Hsg4LEduibvKwrGxWxA"
+ name="example_design_mechanisms" guid="_4k_Hsg4LEduibvKwrGxWxA" briefDescription="Examples that show how to describe design mechanisms"
+ presentationName="Example: Design Mechanisms">
+ <presentation xmi:id="-mAo18f36rZ1R98kpZX7HMw" href="uma://-mAo18f36rZ1R98kpZX7HMw#-mAo18f36rZ1R98kpZX7HMw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_herrINvTEdyrWIQpneun6w"
+ name="arch_mechanism.design" guid="_herrINvTEdyrWIQpneun6w" variabilityType="contributes"
+ variabilityBasedOnElement="_mzxI0A4LEduibvKwrGxWxA" conceptsAndPapers="_w2ACwA4LEduibvKwrGxWxA"
+ guidelines="_4k_Hsg4LEduibvKwrGxWxA"/>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_3AcuwMOlEdupeqHTre3HvQ"
+ name="Architecture Guidance" guid="_3AcuwMOlEdupeqHTre3HvQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_qjvdgNZ1EdybtZ_nzDhq6w"
+ name="Arch with Visual Modeling" guid="_qjvdgNZ1EdybtZ_nzDhq6w" briefDescription="This content package adds visual modeling content to the base architecture elements. This package should only be included in a confinguration if the visual modeling package is included.">
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_HZGFsKrPEdu6T6WyNqBzqQ"
+ name="component.vm" guid="_HZGFsKrPEdu6T6WyNqBzqQ" variabilityType="contributes"
+ variabilityBasedOnElement="_0YP18MlgEdmt3adZL5Dmdw">
+ <presentation xmi:id="-zfl87vJBFdinDB02ArLXOQ" href="uma://-zfl87vJBFdinDB02ArLXOQ#-zfl87vJBFdinDB02ArLXOQ"/>
+ </contentElements>
+ </childPackages>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_siyjEEvCEdunZcj9T5hrMQ"
+ name="architecture" guid="_siyjEEvCEdunZcj9T5hrMQ" presentationName="architecture">
+ <presentation xmi:id="-YMvJ5LwexkcVWWqLdm5-nQ" href="uma://-YMvJ5LwexkcVWWqLdm5-nQ#-YMvJ5LwexkcVWWqLdm5-nQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="__O7tAMVvEduLYZUGfgZrkQ"
+ name="software_architecture" guid="__O7tAMVvEduLYZUGfgZrkQ" briefDescription="The software architecture represents the structure or structures of the system, which consists of software components, the externally visible properties of those components, and the relationships among them."
+ presentationName="Software Architecture" conceptsAndPapers="_0YJvUMlgEdmt3adZL5Dmdw _kgtcoNc8Edyd7OybSySFxg _O1kAANvfEduv2KOT-Teh6w _jdKSsNpiEdyP58ppo1Ieaw _HlRqANpbEdyP58ppo1Ieaw _mzxI0A4LEduibvKwrGxWxA _HrZGIA4MEduibvKwrGxWxA _0YP18MlgEdmt3adZL5Dmdw _pLEGUNqGEdy88NBoQgfGyg"
+ guidelines="_0gpkAMlgEdmt3adZL5Dmdw _0gjdYMlgEdmt3adZL5Dmdw _vO2uoO0OEduUpsu85bVhiQ">
+ <presentation xmi:id="-UQ_e8kozIP11Xu008RJd-A" href="uma://-UQ_e8kozIP11Xu008RJd-A#-UQ_e8kozIP11Xu008RJd-A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_d82_AEvDEdunZcj9T5hrMQ"
+ name="component" guid="_d82_AEvDEdunZcj9T5hrMQ" presentationName="component">
+ <presentation xmi:id="-BWZsh3vKrqSOzfkBJmDTLA" href="uma://-BWZsh3vKrqSOzfkBJmDTLA#-BWZsh3vKrqSOzfkBJmDTLA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_0YP18MlgEdmt3adZL5Dmdw"
+ name="component" guid="_0YP18MlgEdmt3adZL5Dmdw" briefDescription="This concept describes components as they are applied within this process."
+ presentationName="Component">
+ <presentation xmi:id="_TZiasMM1EdmSIPI87WLu3g" href="uma://_TZiasMM1EdmSIPI87WLu3g#_TZiasMM1EdmSIPI87WLu3g"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_mzxI0A4LEduibvKwrGxWxA"
+ name="arch_mechanism" guid="_mzxI0A4LEduibvKwrGxWxA" briefDescription="This concept describes what architectural mechanisms are and what they are used for."
+ presentationName="Architectural Mechanism" conceptsAndPapers="_0gvqoMlgEdmt3adZL5Dmdw _HrZGIA4MEduibvKwrGxWxA _0YJvUMlgEdmt3adZL5Dmdw"
+ examples="_O39h0O9pEdu635i_iQ5Jag _eQ_s8Om5Edupia_tZIXEqg">
+ <presentation xmi:id="-SJrpVySJ2npYs8NwGvnHjw" href="uma://-SJrpVySJ2npYs8NwGvnHjw#-SJrpVySJ2npYs8NwGvnHjw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_0gvqoMlgEdmt3adZL5Dmdw"
+ name="analysis_mechanism" guid="_0gvqoMlgEdmt3adZL5Dmdw" briefDescription="An Analysis Mechanism is a conceptual representation of an Architectural Mechanism."
+ presentationName="Analysis Mechanism" conceptsAndPapers="_mzxI0A4LEduibvKwrGxWxA _w2ACwA4LEduibvKwrGxWxA _0LcUkA4LEduibvKwrGxWxA"
+ examples="_eQ_s8Om5Edupia_tZIXEqg">
+ <presentation xmi:id="_S8KCcMP2EdmWKcx6ixEiwg" href="uma://_S8KCcMP2EdmWKcx6ixEiwg#_S8KCcMP2EdmWKcx6ixEiwg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_O1kAANvfEduv2KOT-Teh6w"
+ name="executable_arch" guid="_O1kAANvfEduv2KOT-Teh6w" briefDescription="An executable architecture is an implementation that realizes a set of validated architecturally significant requirements."
+ presentationName="Executable Architecture" conceptsAndPapers="_HrZGIA4MEduibvKwrGxWxA __O7tAMVvEduLYZUGfgZrkQ">
+ <presentation xmi:id="-0R8BZWlcCQ3Rj84jY2M3Kw" href="uma://-0R8BZWlcCQ3Rj84jY2M3Kw#-0R8BZWlcCQ3Rj84jY2M3Kw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_0gjdYMlgEdmt3adZL5Dmdw"
+ name="repres_interfaces_to_ext_systems" guid="_0gjdYMlgEdmt3adZL5Dmdw"
+ briefDescription="This guideline introduces system level interfaces."
+ presentationName="Representing Interfaces to External Systems" conceptsAndPapers="_0YP18MlgEdmt3adZL5Dmdw"
+ guidelines="_uF-QYEAhEdq_UJTvM1DM2Q">
+ <presentation xmi:id="_iCwb8MM3EdmSIPI87WLu3g" href="uma://_iCwb8MM3EdmSIPI87WLu3g#_iCwb8MM3EdmSIPI87WLu3g"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_VHFGkEvCEdunZcj9T5hrMQ"
+ name="architectural_mechanism" guid="_VHFGkEvCEdunZcj9T5hrMQ" presentationName="architectural mechanism">
+ <presentation xmi:id="-Vvwb6EupIB9kfSQ_mhjURA" href="uma://-Vvwb6EupIB9kfSQ_mhjURA#-Vvwb6EupIB9kfSQ_mhjURA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_n7GmQEvCEdunZcj9T5hrMQ"
+ name="architectural_view" guid="_n7GmQEvCEdunZcj9T5hrMQ" presentationName="architectural view">
+ <presentation xmi:id="-0vih7gB84YYDheaH7jeYFQ" href="uma://-0vih7gB84YYDheaH7jeYFQ#-0vih7gB84YYDheaH7jeYFQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_kgtcoNc8Edyd7OybSySFxg"
+ name="arch_views_viewpoints" guid="_kgtcoNc8Edyd7OybSySFxg" briefDescription="This concept describes the important concepts of views and viewpoints in the context of architecture."
+ presentationName="Architectural Views and Viewpoints" examples="_4bC4cNs_EdyEW4klSH3vRA">
+ <presentation xmi:id="-QB0WnHnpcK1VJbdJJ5QJ5A" href="uma://-QB0WnHnpcK1VJbdJJ5QJ5A#-QB0WnHnpcK1VJbdJJ5QJ5A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Example" xmi:id="_eQ_s8Om5Edupia_tZIXEqg"
+ name="architectural_mechanism_attributes" guid="_eQ_s8Om5Edupia_tZIXEqg"
+ briefDescription="This example illustrates how to represent attributes for Architecture Mechanisms."
+ presentationName="Architectural Mechanism Attributes">
+ <presentation xmi:id="-8LfKJab2khAUjdmnImaXPA" href="uma://-8LfKJab2khAUjdmnImaXPA#-8LfKJab2khAUjdmnImaXPA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Example" xmi:id="_O39h0O9pEdu635i_iQ5Jag"
+ name="architectural_mechanisms" guid="_O39h0O9pEdu635i_iQ5Jag" briefDescription="This example illustrates the commonly encountered architectural mechanisms."
+ presentationName="Architectural Mechanisms">
+ <presentation xmi:id="-V6Hddpuwu3wvd9R0l4fL7Q" href="uma://-V6Hddpuwu3wvd9R0l4fL7Q#-V6Hddpuwu3wvd9R0l4fL7Q"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_HrZGIA4MEduibvKwrGxWxA"
+ name="arch_significant_requirements" guid="_HrZGIA4MEduibvKwrGxWxA"
+ briefDescription="This concept describes what architecturally significant requirements are and why they are important."
+ presentationName="Architecturally Significant Requirements">
+ <presentation xmi:id="-EytH4BCNGiHF6pZrp8ISCw" href="uma://-EytH4BCNGiHF6pZrp8ISCw#-EytH4BCNGiHF6pZrp8ISCw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_HlRqANpbEdyP58ppo1Ieaw"
+ name="arch_goals" guid="_HlRqANpbEdyP58ppo1Ieaw" briefDescription="This concept describes what architectural goals are and why they are important."
+ presentationName="Architectural Goals">
+ <presentation xmi:id="-Mm7s8vlK5CaZZ_Msx8reCQ" href="uma://-Mm7s8vlK5CaZZ_Msx8reCQ#-Mm7s8vlK5CaZZ_Msx8reCQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_jdKSsNpiEdyP58ppo1Ieaw"
+ name="arch_constraints" guid="_jdKSsNpiEdyP58ppo1Ieaw" briefDescription="This concept describes those things that may constrain the architecture of a system."
+ presentationName="Architectural Constraints">
+ <presentation xmi:id="-je0zRqgX0Tg_761Z77cIkg" href="uma://-je0zRqgX0Tg_761Z77cIkg#-je0zRqgX0Tg_761Z77cIkg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_pLEGUNqGEdy88NBoQgfGyg"
+ name="key_abstractions" guid="_pLEGUNqGEdy88NBoQgfGyg" briefDescription="This concept describes what key abstractions are and the role they play in the architecture"
+ presentationName="Key Abstractions">
+ <presentation xmi:id="-HJbvivaRmrZ6rdQcdFd78Q" href="uma://-HJbvivaRmrZ6rdQcdFd78Q#-HJbvivaRmrZ6rdQcdFd78Q"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Example" xmi:id="_4bC4cNs_EdyEW4klSH3vRA"
+ name="four_plus_one_view_of_arch" guid="_4bC4cNs_EdyEW4klSH3vRA" briefDescription="This example describes a possible set of views for describing a software architecture."
+ presentationName="4+1 Views of Software Architecture">
+ <presentation xmi:id="-sKBCb98PYCcliL0zVljcyQ" href="uma://-sKBCb98PYCcliL0zVljcyQ#-sKBCb98PYCcliL0zVljcyQ"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_mMbw8NZzEdybtZ_nzDhq6w"
+ name="Visual Modeling Guidance" guid="_mMbw8NZzEdybtZ_nzDhq6w" briefDescription="This package contains all common guidance related to visual modeling.">
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_0XY6UMlgEdmt3adZL5Dmdw"
+ name="visual_modeling" guid="_0XY6UMlgEdmt3adZL5Dmdw" briefDescription="This concept introduces what visual modeling is and its benefits."
+ presentationName="Visual Modeling">
+ <presentation xmi:id="_SB1n8MM1EdmSIPI87WLu3g" href="uma://_SB1n8MM1EdmSIPI87WLu3g#_SB1n8MM1EdmSIPI87WLu3g"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_34jWsLcIEduRNaXpzCOLXQ"
+ name="abstract_away_complexity.vm" guid="_34jWsLcIEduRNaXpzCOLXQ"
+ variabilityType="contributes" variabilityBasedOnElement="_we3F4ACpEdu8m4dIntu6jA"
+ guidelines="_0SsecNr8EdyXE6np2_hUMA">
+ <presentation xmi:id="-OcMsciNn-UtD9fTHj26LGA" href="uma://-OcMsciNn-UtD9fTHj26LGA#-OcMsciNn-UtD9fTHj26LGA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_0SsecNr8EdyXE6np2_hUMA"
+ name="using_visual_modeling" guid="_0SsecNr8EdyXE6np2_hUMA" briefDescription="This guideline provides recommendations on how to use visual modeling when building a system."
+ presentationName="Using Visual Modeling" conceptsAndPapers="_0XY6UMlgEdmt3adZL5Dmdw">
+ <presentation xmi:id="-QklqSGB4aD07vUpfubpMJg" href="uma://-QklqSGB4aD07vUpfubpMJg#-QklqSGB4aD07vUpfubpMJg"/>
+ </contentElements>
+ </childPackages>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_we3F4ACpEdu8m4dIntu6jA"
+ name="abstract_away_complexity" guid="_we3F4ACpEdu8m4dIntu6jA" presentationName="Abstract Away Complexity"
+ conceptsAndPapers="_0YJvUMlgEdmt3adZL5Dmdw _0YP18MlgEdmt3adZL5Dmdw"
+ guidelines="_vO2uoO0OEduUpsu85bVhiQ">
+ <presentation xmi:id="-X7QSjItNBz7w8603yBCv0Q" href="uma://-X7QSjItNBz7w8603yBCv0Q#-X7QSjItNBz7w8603yBCv0Q"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_ctrEgEvCEdunZcj9T5hrMQ"
+ name="pattern" guid="_ctrEgEvCEdunZcj9T5hrMQ" presentationName="pattern">
+ <presentation xmi:id="-VJBtRm2brEKpRlnLWNF8_g" href="uma://-VJBtRm2brEKpRlnLWNF8_g#-VJBtRm2brEKpRlnLWNF8_g"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_Z53x0BapEduSTJywppIxVQ"
+ name="business_pattern" guid="_Z53x0BapEduSTJywppIxVQ" briefDescription="A re-usable portion of design that can be applied to multiple domain-specific activities. "
+ presentationName="Business Pattern" conceptsAndPapers="_mzxI0A4LEduibvKwrGxWxA _0YJvUMlgEdmt3adZL5Dmdw">
+ <presentation xmi:id="-Of51hmgdsO_U2-pnbJ67Cg" href="uma://-Of51hmgdsO_U2-pnbJ67Cg#-Of51hmgdsO_U2-pnbJ67Cg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_0YJvUMlgEdmt3adZL5Dmdw"
+ name="pattern" guid="_0YJvUMlgEdmt3adZL5Dmdw" briefDescription="A generalized solution that can be implemented and applied in a problem situation (a context) and thereby eliminate one or more of the inherent problems."
+ presentationName="Pattern">
+ <presentation xmi:id="_QvmkAMM1EdmSIPI87WLu3g" href="uma://_QvmkAMM1EdmSIPI87WLu3g#_QvmkAMM1EdmSIPI87WLu3g"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_vO2uoO0OEduUpsu85bVhiQ"
+ name="software_reuse" guid="_vO2uoO0OEduUpsu85bVhiQ" briefDescription="This guideline describes how to re-use software and design elements."
+ presentationName="Software Reuse" conceptsAndPapers="_0YJvUMlgEdmt3adZL5Dmdw _Poc7IPDzEdqYgerqi84oCA"
+ guidelines="_0gpkAMlgEdmt3adZL5Dmdw">
+ <presentation xmi:id="-Vp61zQMUoP-Icm5jgDar7A" href="uma://-Vp61zQMUoP-Icm5jgDar7A#-Vp61zQMUoP-Icm5jgDar7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_uF-QYEAhEdq_UJTvM1DM2Q"
+ name="entity_control_boundary_pattern" guid="_uF-QYEAhEdq_UJTvM1DM2Q"
+ briefDescription="This guideline describes a rapid way to build a design that is robust enough to realize the functional requirements."
+ presentationName="Entity-Control-Boundary Pattern">
+ <presentation xmi:id="-awaQ_2dwhGyKRoVKQ-esPQ" href="uma://-awaQ_2dwhGyKRoVKQ-esPQ#-awaQ_2dwhGyKRoVKQ-esPQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_Poc7IPDzEdqYgerqi84oCA"
+ name="refactoring" guid="_Poc7IPDzEdqYgerqi84oCA" briefDescription="This concept explains ways of improving the design of existing code in a way that does not alter its external behavior."
+ presentationName="Refactoring">
+ <presentation xmi:id="-fj_9xjbrpaYNSETyCz5yJg" href="uma://-fj_9xjbrpaYNSETyCz5yJg#-fj_9xjbrpaYNSETyCz5yJg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_0gpkAMlgEdmt3adZL5Dmdw"
+ name="layering" guid="_0gpkAMlgEdmt3adZL5Dmdw" briefDescription="This guideline provides recommendations for partitioning the system into layers."
+ presentationName="Layering">
+ <presentation xmi:id="_lbGQwMM3EdmSIPI87WLu3g" href="uma://_lbGQwMM3EdmSIPI87WLu3g#_lbGQwMM3EdmSIPI87WLu3g"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_-87r0BASEdyqb5chWQXsPQ"
+ name="Technical Open Source References" guid="_-87r0BASEdyqb5chWQXsPQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="_9ToeIB83Edqsvps02rpOOg"
+ name="tech_references" guid="_9ToeIB83Edqsvps02rpOOg" briefDescription="Additional references that may be useful, including books, method plug-ins, and commercial methodology products."
+ presentationName="References">
+ <presentation xmi:id="-aCI9T-9TIe8D35yXBU6qvg" href="uma://-aCI9T-9TIe8D35yXBU6qvg#-aCI9T-9TIe8D35yXBU6qvg"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Vqf5EMuFEdyuBO4ZIzcyig"
+ name="Technical Resources (Templates, Reports, Examples)" guid="_Vqf5EMuFEdyuBO4ZIzcyig">
+ <contentElements xsi:type="org.eclipse.epf.uma:Template" xmi:id="_m7p-AI5fEdyO5aWob1UGDA"
+ name="systemwide_requirements_specification" guid="_m7p-AI5fEdyO5aWob1UGDA"
+ briefDescription="This is the template suggested for specifying requirements and constraints in accordance with the FURPS+ classification."
+ presentationName="System-Wide Requirements Specification">
+ <presentation xmi:id="-13wK-dfNa9N1G8Ob27m-Og" href="uma://-13wK-dfNa9N1G8Ob27m-Og#-13wK-dfNa9N1G8Ob27m-Og"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Template" xmi:id="_3Y3XUI5fEdyO5aWob1UGDA"
+ name="use_case_specification" guid="_3Y3XUI5fEdyO5aWob1UGDA" briefDescription="This is the informal template suggested for representing a use case specification."
+ presentationName="Use-Case Specification" examples="_JLOiIMNvEdu2IdAIaWZyAw">
+ <presentation xmi:id="-zGnAaKUwKnn2pPANr7E0MQ" href="uma://-zGnAaKUwKnn2pPANr7E0MQ#-zGnAaKUwKnn2pPANr7E0MQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Template" xmi:id="_DtlRQI5gEdyO5aWob1UGDA"
+ name="vision" guid="_DtlRQI5gEdyO5aWob1UGDA" briefDescription="This is the informal template suggested for representing the Vision document."
+ presentationName="Vision">
+ <presentation xmi:id="-DUD2tbhBn23i6Jm6gcoN9Q" href="uma://-DUD2tbhBn23i6Jm6gcoN9Q#-DUD2tbhBn23i6Jm6gcoN9Q"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_hqWo8JF_EdyIDP1jVZ3aHA"
+ name="supporting_requirements_specification.tpl" guid="_hqWo8JF_EdyIDP1jVZ3aHA"
+ variabilityType="contributes" variabilityBasedOnElement="_BVh9cL-CEdqb7N6KIeDL8Q"
+ templates="_m7p-AI5fEdyO5aWob1UGDA"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_q6YC0JF_EdyIDP1jVZ3aHA"
+ name="use_case_specification.tpl" guid="_q6YC0JF_EdyIDP1jVZ3aHA" variabilityType="contributes"
+ variabilityBasedOnElement="_0VGbUMlgEdmt3adZL5Dmdw" templates="_3Y3XUI5fEdyO5aWob1UGDA"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_vOpUYJF_EdyIDP1jVZ3aHA"
+ name="vision.tpl" guid="_vOpUYJF_EdyIDP1jVZ3aHA" variabilityType="contributes"
+ variabilityBasedOnElement="_0WVxcMlgEdmt3adZL5Dmdw" templates="_DtlRQI5gEdyO5aWob1UGDA"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:Example" xmi:id="_t4QdAMNqEdu2IdAIaWZyAw"
+ name="uc_model_evolve" guid="_t4QdAMNqEdu2IdAIaWZyAw" briefDescription="This example illustrates how the use-case model evolves over time when you use a &quot;breadth before depth&quot; approach to maximize value and minimize risk early in the lifecycle and to minimize re-work later."
+ presentationName="Evolution of the Use-Case Model">
+ <presentation xmi:id="-JviMIao63C7w9C8W6iPJrw" href="uma://-JviMIao63C7w9C8W6iPJrw#-JviMIao63C7w9C8W6iPJrw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Example" xmi:id="_JLOiIMNvEdu2IdAIaWZyAw"
+ name="use_case_spec" guid="_JLOiIMNvEdu2IdAIaWZyAw" briefDescription="This is an example of a completed use-case specification for the Withdraw Cash use case for an Automated Teller Machine."
+ presentationName="Use-Case Specification" examples="_t4QdAMNqEdu2IdAIaWZyAw">
+ <presentation xmi:id="-qq-9Brh5oa6H3lsdp-m8mQ" href="uma://-qq-9Brh5oa6H3lsdp-m8mQ#-qq-9Brh5oa6H3lsdp-m8mQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Template" xmi:id="_yZtgQI5gEdyO5aWob1UGDA"
+ name="test_script" guid="_yZtgQI5gEdyO5aWob1UGDA" briefDescription="This is the informal template suggested for test scripts."
+ presentationName="Test Script">
+ <presentation xmi:id="-PHKmXwkVhDR81vcyAQAkxQ" href="uma://-PHKmXwkVhDR81vcyAQAkxQ#-PHKmXwkVhDR81vcyAQAkxQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Template" xmi:id="_yWaKEI5fEdyO5aWob1UGDA"
+ name="test_case" guid="_yWaKEI5fEdyO5aWob1UGDA" briefDescription="This is the informal template suggested for representing test cases."
+ presentationName="Test Case">
+ <presentation xmi:id="-JrYzWdOXPOZBIVGWibK1Bw" href="uma://-JrYzWdOXPOZBIVGWibK1Bw#-JrYzWdOXPOZBIVGWibK1Bw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_SMU0sJF_EdyIDP1jVZ3aHA"
+ name="test_script.tpl" guid="_SMU0sJF_EdyIDP1jVZ3aHA" variabilityType="contributes"
+ variabilityBasedOnElement="_0ZfMEMlgEdmt3adZL5Dmdw" templates="_yZtgQI5gEdyO5aWob1UGDA"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_nlcHUJF_EdyIDP1jVZ3aHA"
+ name="test_case.tpl" guid="_nlcHUJF_EdyIDP1jVZ3aHA" variabilityType="contributes"
+ variabilityBasedOnElement="_0ZS-0MlgEdmt3adZL5Dmdw" templates="_yWaKEI5fEdyO5aWob1UGDA"/>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_OOB2DQouEdyhlpBPrduOMw"
+ name="CapabilityPatterns" guid="_OOB2DQouEdyhlpBPrduOMw"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_OOB2DgouEdyhlpBPrduOMw"
+ name="DeliveryProcesses" guid="_OOB2DgouEdyhlpBPrduOMw"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_OOB2DwouEdyhlpBPrduOMw"
+ name="ProcessContributions" guid="_OOB2DwouEdyhlpBPrduOMw"/>
+ <bases href="uma://_iVydgENdEdy245g62lfWcA#_iVydgENdEdy245g62lfWcA"/>
+ <bases href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno4EKmEdyrauqpmnA8jQ"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/core.tech.common.base/resources/4plus1_2.jpg b/praclib/temp/core.tech.common.base/resources/4plus1_2.jpg
new file mode 100644
index 0000000..24cfc97
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/resources/4plus1_2.jpg
Binary files differ
diff --git a/praclib/temp/core.tech.common.base/workproducts/implementation.xmi b/praclib/temp/core.tech.common.base/workproducts/implementation.xmi
new file mode 100644
index 0000000..1c0b59e
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/workproducts/implementation.xmi
@@ -0,0 +1,33 @@
+<?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="-HPCdXGOQ2SGSCHZaDEKJRg"
+ name="implementation,_0YoQcMlgEdmt3adZL5Dmdw" guid="-HPCdXGOQ2SGSCHZaDEKJRg" authors="Jim Ruehlin"
+ changeDate="2007-03-02T10:47:39.492-0800" version="1.0.0">
+ <mainDescription><p>
+ This artifact&nbsp;is the collection of one or more of&nbsp;these elements:
+</p>
+<ul>
+ <li>
+ Source code files
+ </li>
+ <li>
+ Data files&nbsp;
+ </li>
+ <li>
+ Build scripts
+ </li>
+ <li>
+ Other files that are transformed into the executable system
+ </li>
+</ul></mainDescription>
+ <purpose><p>
+ To represent the physical parts that make up the system to be built, organized in a way that is understandable and
+ manageable.
+</p></purpose>
+ <representationOptions><p>
+ Implementation files represented as files in the local file system. File folders (directories), represented as
+ packages, group the files into logical units.
+</p></representationOptions>
+</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/praclib/temp/core.tech.common.base/workproducts/resources/supporting_reguirements2.gif b/praclib/temp/core.tech.common.base/workproducts/resources/supporting_reguirements2.gif
new file mode 100644
index 0000000..cf4c368
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/workproducts/resources/supporting_reguirements2.gif
Binary files differ
diff --git a/praclib/temp/core.tech.common.base/workproducts/system_wide_requirements.xmi b/praclib/temp/core.tech.common.base/workproducts/system_wide_requirements.xmi
new file mode 100644
index 0000000..8945d69
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/workproducts/system_wide_requirements.xmi
@@ -0,0 +1,80 @@
+<?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="-_dNuyh-0q5vpCiIiLfbj6w"
+ name="system_wide_requirements,_BVh9cL-CEdqb7N6KIeDL8Q" guid="-_dNuyh-0q5vpCiIiLfbj6w"
+ changeDate="2008-02-11T16:17:03.644-0800" version="1.0.0">
+ <keyConsiderations><ul>
+ <li>
+ When documenting system-wide requirements, ensure that the needs of all stakeholders are represented.&nbsp; In
+ particular, don't forget to include the needs of those responsible for maintaining or supporting the system once
+ delivered.
+ </li>
+ <li>
+ There are typically some overlaps and "gray areas" between system-wide requirements and other requirements work
+ products.&nbsp; For example, the authorization behavior of a system can be specified as use cases, or as statements
+ within system-wide requirements.&nbsp; The overall driving need is that no important requirements are missed or
+ duplicated and that there is an agreed approach for capturing and processing every type of requirement.
+ </li>
+ <li>
+ System-wide requirements originate from many places. Documenting the source of the requirement is particularly
+ important when separating out externally mandated requirements.
+ </li>
+ <li>
+ Requirements are often thought of as "Qualitative" (specifying a quality or desirable characteristic) versus
+ "Quantitative" (specifying a quantity).&nbsp;&nbsp;Qualitative requirements can sometimes be elaborated into
+ quantitative requirements.
+ </li>
+ <li>
+ A good quality requirement is one that can be verified, either through testing or some other objective evaluation.
+ </li>
+ <li>
+ System-wide requirements should be evaluated for cost, schedule impact and level of contribution to business goals.
+ They should be iteratively challenged, defended and amended based on this evaluation.
+ </li>
+</ul></keyConsiderations>
+ <purpose><p>
+ This artifact is used for the following purposes:
+</p>
+<ul>
+ <li>
+ It is used to describe the quality attributes of the system and the constraints which the design options will be
+ required to satisfy in order to deliver the business goals, objectives or capabilities.
+ </li>
+ <li>
+ It is used to capture functional requirements that are not expressed as use cases.
+ </li>
+ <li>
+ It is used to negotiate between, and select from, competing design options.
+ </li>
+ <li>
+ It is used to assess the sizing, cost and viability of the proposed system.
+ </li>
+ <li>
+ It is a key consideration for understanding service level requirements for operational management of the solution.
+ </li>
+</ul></purpose>
+ <impactOfNotHaving><p>
+ A failure to adequately manage and meet system-wide requirements leads to a risk of delivering a system which is
+ unacceptable to one or more stakeholders.<br />
+</p></impactOfNotHaving>
+ <reasonsForNotNeeding><p>
+ If none of the categories of system-wide requirements apply to the project under consideration, this artifact may not
+ be needed.
+</p></reasonsForNotNeeding>
+ <briefOutline><p>
+ System-wide requirements should be organized by a number of common themes or subcategories. These include the areas of
+ performance and capacity, availability, usability, security and privacy, maintainability, manageability and
+ flexibility. A description of the recommended categorization approach is given in the supporting guidance.
+</p>
+<p>
+ For each system-wide requirement capture attributes such as the source and priority of the requirements,
+ as&nbsp;described&nbsp;by the associated requirements management guidance.
+</p></briefOutline>
+ <representationOptions>This artifact&nbsp;represent influences on the design and delivery of a system which cover a broad range of themes.&nbsp;
+Requirements for each theme should be documented under separate headings within a document, or under appropriate category
+identifiers in a requirements gathering tool.&nbsp; Categories are often given easy-to-recognize identifiers so individual
+requirements can be readily associated with the appropriate category.&nbsp; The format of requirements will vary from
+category to category, with some being heavily textual, and others being more structured and quantitative.</representationOptions>
+</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/praclib/temp/core.tech.common.base/workproducts/test_case.xmi b/praclib/temp/core.tech.common.base/workproducts/test_case.xmi
new file mode 100644
index 0000000..876e924
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/workproducts/test_case.xmi
@@ -0,0 +1,36 @@
+<?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"
+ 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
+ the system under test.&nbsp; A test case is more formal than a test idea and usually takes the form of a
+ specification.&nbsp;In less formal environments, test cases can be created by identifying a unique ID, name, associated
+ test data, and expected results.&nbsp;
+</p>
+<p>
+ Test cases may be derived from&nbsp;many&nbsp;sources but will usually include a subset of both the requirements (such
+ as use cases, performance characteristics, reliability concerns) and other types of quality attributes.&nbsp; For more
+ information on types of tests and their relationship to quality test attributes, see&nbsp;<a
+ class="elementLinkWithType" href="./../../core.tech.common.base/guidances/concepts/types_of_test_CAE80710.html"
+ guid="_0aJ6cMlgEdmt3adZL5Dmdw">Concept: Types of Test</a>.
+</p></mainDescription>
+ <purpose><p>
+ The purpose of this artifact is to:
+</p>
+<ul>
+ <li>
+ provide a way to capture test inputs, conditions, and expected results for a system
+ </li>
+ <li>
+ systematically identify aspects of the software to test
+ </li>
+ <li>
+ specify whether an expected result has been reached based on verification of a system requirement, set of
+ requirements, or scenario
+ </li>
+</ul></purpose>
+</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/praclib/temp/core.tech.common.base/workproducts/test_log.xmi b/praclib/temp/core.tech.common.base/workproducts/test_log.xmi
new file mode 100644
index 0000000..3438734
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/workproducts/test_log.xmi
@@ -0,0 +1,37 @@
+<?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="_NqePEKeqEdmKDbQuyzCoqQ"
+ name="test_log,_0ZlSsMlgEdmt3adZL5Dmdw" guid="_NqePEKeqEdmKDbQuyzCoqQ" changeDate="2006-09-29T16:02:01.621-0700"
+ version="7.2.0">
+ <mainDescription>This artifact&nbsp;provides a detailed, typically time-based record that serves both as verification that a set of tests
+were executed, and provides information relating to the success of those tests.&nbsp; The focus is typically on the
+provision of an accurate audit trail, enabling post-execution diagnosis of failures to be undertaken.&nbsp; This raw data
+will subsequently be analyzed to help determine the results of some aspect of the test effort.</mainDescription>
+ <purpose><ul>
+ <li>
+ To provide verification that a set of tests was executed
+ </li>
+ <li>
+ To provide information relating to the success of those tests
+ </li>
+</ul></purpose>
+ <representationOptions><p>
+ Since this is a collection of raw data for subsequent analysis, it can be represented in a number of ways.
+</p>
+<p>
+ Some suggestions are:
+</p>
+<ul>
+ <li>
+ For manual tests, log the actual results on a copy of the manual Test Script
+ </li>
+ <li>
+ For automated tests, direct the output to log files that you can trace back to the automated Test Script
+ </li>
+ <li>
+ Track raw results data in a test management tool.
+ </li>
+</ul></representationOptions>
+</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/praclib/temp/core.tech.common.base/workproducts/test_script.xmi b/praclib/temp/core.tech.common.base/workproducts/test_script.xmi
new file mode 100644
index 0000000..8afd5d4
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/workproducts/test_script.xmi
@@ -0,0 +1,6 @@
+<?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="_NqYIcqeqEdmKDbQuyzCoqQ"
+ name="test_script,_0ZfMEMlgEdmt3adZL5Dmdw" guid="_NqYIcqeqEdmKDbQuyzCoqQ" changeDate="2005-07-19T16:12:17.077-0700"/>
diff --git a/praclib/temp/core.tech.common.base/workproducts/use_case.xmi b/praclib/temp/core.tech.common.base/workproducts/use_case.xmi
new file mode 100644
index 0000000..a0bd7f4
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/workproducts/use_case.xmi
@@ -0,0 +1,70 @@
+<?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="_zHZW8qYSEdmvhNXG0Oc2uA"
+ name="use_case,_0VGbUMlgEdmt3adZL5Dmdw" guid="_zHZW8qYSEdmvhNXG0Oc2uA" changeDate="2007-12-12T01:54:27.000-0800"
+ version="1.0.0">
+ <purpose><p>
+ Use cases are used for the following purposes:
+</p>
+<ul>
+ <li>
+ to reach a common understanding of system behavior.
+ </li>
+ <li>
+ to design elements that support the required behavior.
+ </li>
+ <li>
+ to identify test cases.
+ </li>
+ <li>
+ to plan and assess work.
+ </li>
+ <li>
+ to write user documentation.
+ </li>
+</ul></purpose>
+ <reasonsForNotNeeding>A project may use alternative requirements practices (e.g. “The system shall…” statements) which could replace use
+cases.<br /></reasonsForNotNeeding>
+ <briefOutline><p>
+ A use case typically includes the following information:
+</p>
+<ul>
+ <li>
+ <strong>Name:</strong> The name of the use case.
+ </li>
+ <li>
+ <strong>Brief Description:</strong> A brief description of the role and purpose of the use case.
+ </li>
+ <li>
+ <strong>Flow of Events:</strong> A textual description of what the system does in regard to a use case scenario
+ (not how specific problems are solved by the system). The description is understandable by the customer.&nbsp; The
+ flows can include a basic flow, alternative flows, and subflows.
+ </li>
+ <li>
+ <strong>Key scenarios:</strong> A textual description of the most important or frequently discussed scenarios.
+ </li>
+ <li>
+ <strong>Special Requirements:</strong> A textual description that collects all requirements, such as non-functional
+ requirements, on the use case, that are not considered in the use-case model, but that need to be taken care of
+ during design or implementation.&nbsp;&nbsp;
+ </li>
+ <li>
+ <strong>Preconditions:</strong>&nbsp;A textual description that defines a constraint on the system when the use
+ case may start.&nbsp;&nbsp;&nbsp;&nbsp;
+ </li>
+ <li>
+ <strong>Post conditions:</strong> A textual description that defines a constraint on the system when the use cases
+ have terminated.&nbsp;&nbsp;&nbsp;
+ </li>
+ <li>
+ <strong>Extension points:</strong> A list of locations within the flow of events of the use case at which
+ additional behavior can be inserted using the extend-relationship.&nbsp;&nbsp;&nbsp;
+ </li>
+</ul></briefOutline>
+ <representationOptions><p>
+ The use case can be documented as just a use-case specification document, or can be incorporated in a use-case
+ model.&nbsp; Use cases, and parts of use cases, can also be captured in a requirements management tool.
+</p></representationOptions>
+</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/praclib/temp/core.tech.common.base/workproducts/use_case_model.xmi b/praclib/temp/core.tech.common.base/workproducts/use_case_model.xmi
new file mode 100644
index 0000000..6761bf9
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/workproducts/use_case_model.xmi
@@ -0,0 +1,21 @@
+<?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="-kQg7MSGPB3RPjrplyxwimQ"
+ name="uc_model,_W2SgEDR5EdutE_HNDTJk5Q" guid="-kQg7MSGPB3RPjrplyxwimQ" changeDate="2007-12-05T09:39:55.000-0800"
+ version="1.0.0">
+ <purpose><p>
+ This artifact presents an overview of the system's intended behavior.&nbsp;It&nbsp;is the basis for agreement
+ between&nbsp;stakeholders and the project team regarding the intended functionality for the system. It also helps to
+ guide the various tasks in the software development lifecycle.
+</p></purpose>
+ <representationOptions><p>
+ Tailor this artifact to support the project team's needs.
+</p>
+<p>
+ Representation options include: reports and diagrams from UML modeling tools, graphical representations created using
+ drawing tools, drawings on whiteboards. Most of the information in the use-case model is captured in the use-case
+ specifications.
+</p></representationOptions>
+</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/praclib/temp/core.tech.common.base/workproducts/vision.xmi b/praclib/temp/core.tech.common.base/workproducts/vision.xmi
new file mode 100644
index 0000000..485a2be
--- /dev/null
+++ b/praclib/temp/core.tech.common.base/workproducts/vision.xmi
@@ -0,0 +1,40 @@
+<?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="_zHTQUKYSEdmvhNXG0Oc2uA"
+ name="vision,_0WVxcMlgEdmt3adZL5Dmdw" guid="_zHTQUKYSEdmvhNXG0Oc2uA" changeDate="2007-10-24T09:47:27.000-0700"
+ version="1.0.0">
+ <keyConsiderations><p>
+ It is generally good practice to keep this artifact brief so you can release it to stakeholders as soon as possible,
+ and to make it easy for stakeholders to read and understand. You can accomplish this by including only the most
+ important features and avoiding details of requirements.
+</p>
+<p>
+ Projects with a focus on product development may extend the marketing section and include a more detailed product
+ position statement based on their needs and research.
+</p></keyConsiderations>
+ <purpose><p>
+ This artifact provides a high-level basis for the more detailed technical requirements. It captures the essence of the
+ technical solution by describing high-level stakeholder requests and constraints that give an overview of the
+ reasoning, background and context for detailed requirements. It serves as input for communicating the fundamental "what
+ and why" for the project, and provides a strategy against which all future decisions should be validated.
+</p>
+<p>
+ The vision should rally team members behind an idea and give them the context for decision-making in the requirements
+ area. The vision must therefore be visible to everyone on the team.<br />
+</p></purpose>
+ <impactOfNotHaving>If this artifact is not used, there is a high risk that stakeholders and the development team will have different
+expectations. This could lead to cancellation of the project. Misunderstandings and miscommunication about the strategy may
+cause the project to move away from the original vision and create a discrepancy in stakeholder expectations.&nbsp;</impactOfNotHaving>
+ <reasonsForNotNeeding>This artifact is generally recommended for all but trivial projects.</reasonsForNotNeeding>
+ <representationOptions><p>
+ The vision is usually captured as a document.&nbsp;If key stakeholder needs are captured in a requirements management
+ tool, then this part of the document may be generated using reporting capabilities.
+</p>
+<p>
+ If the vision serves a set of projects or an entire program, the overall vision may be divided into several vision work
+ products. The vision of the program then brings the visions together by providing program-specific content and
+ referencing the subordinate visions.<br />
+</p></representationOptions>
+</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/praclib/temp/core.tech.slot.base/.project b/praclib/temp/core.tech.slot.base/.project
new file mode 100644
index 0000000..2c76ff5
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>core.tech.slot.base</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/core.tech.slot.base/guidances/concepts/resources/EBCDiagram.JPG b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/EBCDiagram.JPG
new file mode 100644
index 0000000..67970fe
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/EBCDiagram.JPG
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/concepts/resources/back_to_top.gif b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/back_to_top.gif
new file mode 100644
index 0000000..356d954
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/back_to_top.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/concepts/resources/co_soa_portfolio-01.gif b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/co_soa_portfolio-01.gif
new file mode 100644
index 0000000..987560d
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/co_soa_portfolio-01.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/concepts/resources/co_soa_portfolio-02.gif b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/co_soa_portfolio-02.gif
new file mode 100644
index 0000000..29cdc8e
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/co_soa_portfolio-02.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/concepts/resources/co_soa_portfolio-03.gif b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/co_soa_portfolio-03.gif
new file mode 100644
index 0000000..48fcc61
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/co_soa_portfolio-03.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/concepts/resources/co_soa_soa-01.gif b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/co_soa_soa-01.gif
new file mode 100644
index 0000000..f996360
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/co_soa_soa-01.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/concepts/resources/collapse.gif b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/collapse.gif
new file mode 100644
index 0000000..3f6541f
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/collapse.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/concepts/resources/collapse_all.gif b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/collapse_all.gif
new file mode 100644
index 0000000..38f7019
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/collapse_all.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/concepts/resources/concept.gif b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/concept.gif
new file mode 100644
index 0000000..f0e95cd
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/concept.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/concepts/resources/expand_all.gif b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/expand_all.gif
new file mode 100644
index 0000000..8a18a39
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/expand_all.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/concepts/resources/im_uc.gif b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/im_uc.gif
new file mode 100644
index 0000000..f271c09
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/im_uc.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/concepts/resources/md_acto2.gif b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/md_acto2.gif
new file mode 100644
index 0000000..29ede3a
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/md_acto2.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/concepts/resources/md_acto3.gif b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/md_acto3.gif
new file mode 100644
index 0000000..43fbf21
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/md_acto3.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/concepts/resources/shim.gif b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/shim.gif
new file mode 100644
index 0000000..0aba790
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/shim.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/concepts/resources/testFirstDesign.jpg b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/testFirstDesign.jpg
new file mode 100644
index 0000000..6da383c
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/testFirstDesign.jpg
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/concepts/resources/ucprepst.gif b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/ucprepst.gif
new file mode 100644
index 0000000..5f9e869
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/ucprepst.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/concepts/resources/ucstrct.gif b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/ucstrct.gif
new file mode 100644
index 0000000..4458bcb
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/guidances/concepts/resources/ucstrct.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/examples/resources/ex_work_items_list.xls b/praclib/temp/core.tech.slot.base/guidances/examples/resources/ex_work_items_list.xls
new file mode 100644
index 0000000..234f2a5
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/guidances/examples/resources/ex_work_items_list.xls
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/4plus1_2.jpg b/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/4plus1_2.jpg
new file mode 100644
index 0000000..24cfc97
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/4plus1_2.jpg
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/Which Req Gathering Technique.gif b/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/Which Req Gathering Technique.gif
new file mode 100644
index 0000000..10b6366
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/Which Req Gathering Technique.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/Workshop Activity Diagram.GIF b/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/Workshop Activity Diagram.GIF
new file mode 100644
index 0000000..228f102
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/Workshop Activity Diagram.GIF
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/ac_intsy.gif b/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/ac_intsy.gif
new file mode 100644
index 0000000..b4e468f
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/ac_intsy.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/co_dmec1.gif b/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/co_dmec1.gif
new file mode 100644
index 0000000..b076e0b
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/co_dmec1.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/co_dmec2.gif b/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/co_dmec2.gif
new file mode 100644
index 0000000..b8b7cd9
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/co_dmec2.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/co_dmec3.gif b/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/co_dmec3.gif
new file mode 100644
index 0000000..bfd2a4b
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/co_dmec3.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc1.gif b/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc1.gif
new file mode 100644
index 0000000..1c2beb3
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc1.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc2.gif b/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc2.gif
new file mode 100644
index 0000000..717c2b2
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc2.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc3.gif b/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc3.gif
new file mode 100644
index 0000000..06f3a9d
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc3.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc4.gif b/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc4.gif
new file mode 100644
index 0000000..cb79539
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc4.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc5.gif b/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc5.gif
new file mode 100644
index 0000000..8559e50
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc5.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc6.gif b/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc6.gif
new file mode 100644
index 0000000..13a7b72
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/jdbc6.gif
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/wil_overview.bmp b/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/wil_overview.bmp
new file mode 100644
index 0000000..920106d
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/guidances/guidelines/resources/wil_overview.bmp
Binary files differ
diff --git a/praclib/temp/core.tech.slot.base/plugin.xmi b/praclib/temp/core.tech.slot.base/plugin.xmi
new file mode 100644
index 0000000..19ce23b
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/plugin.xmi
@@ -0,0 +1,103 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_-cCH8LXuEduGP_98XMd0fg"
+ guid="_-cCH8LXuEduGP_98XMd0fg">
+ <resourceDescriptors xmi:id="_V7uggMhOEdubbfDwtMqgaQ" id="_Q8ipsMhOEdubbfDwtMqgaQ"
+ uri="capabilitypatterns/design_and_implement_scenario_arch_sig/model.xmi"/>
+ <resourceDescriptors xmi:id="_3Q758A4kEdydA9fIm5xHpg" id="-jbCbONi6H6_jHT7i7yGLtQ"
+ uri="workproducts/technical_specification_slot.xmi"/>
+ <resourceDescriptors xmi:id="_1axaEUqfEdyi3_jfs__bIQ" id="-OEaOjKP9J283DeVnMku6nA"
+ uri="workproducts/software_design_slot.xmi"/>
+ <resourceDescriptors xmi:id="_befZ0Kp8Edyaf4Nc4IfCUw" id="-q2TOWK55j3CrnAeI2uKzKg"
+ uri="workproducts/technical_vision_slot_XXX.xmi"/>
+ <resourceDescriptors xmi:id="_4LjwUNjhEdyQUcK-3ySmyA" id="-dbtxl4sYStfjW4yyXr67hg"
+ uri="workproducts/requirements_slot.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_-bv0ELXuEduGP_98XMd0fg" name="core.tech.slot.base"
+ guid="_-bv0ELXuEduGP_98XMd0fg" briefDescription="Contains the method elements that intended to be reused across software development contexts and lifecycles. "
+ changeDate="2007-08-05T10:25:00.781-0400">
+ <copyrightStatement href="uma://_iVydgENdEdy245g62lfWcA#_cTs20KzREduOqvpk_MDLfQ"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_-bv0EbXuEduGP_98XMd0fg"
+ name="Content" guid="_-bv0EbXuEduGP_98XMd0fg">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_-bv0ErXuEduGP_98XMd0fg"
+ name="Categories" guid="_-bv0ErXuEduGP_98XMd0fg">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_-bv0E7XuEduGP_98XMd0fg"
+ name="Domains" guid="_-bv0E7XuEduGP_98XMd0fg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_-bv0FLXuEduGP_98XMd0fg"
+ name="Disciplines" guid="_-bv0FLXuEduGP_98XMd0fg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_-bv0FbXuEduGP_98XMd0fg"
+ name="RoleSets" guid="_-bv0FbXuEduGP_98XMd0fg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_-bv0FrXuEduGP_98XMd0fg"
+ name="WP Types" guid="_-bv0FrXuEduGP_98XMd0fg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_-bv0F7XuEduGP_98XMd0fg"
+ name="Tools" guid="_-bv0F7XuEduGP_98XMd0fg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_-bv0GLXuEduGP_98XMd0fg"
+ name="StandardCategories" guid="_-bv0GLXuEduGP_98XMd0fg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_-bv0GbXuEduGP_98XMd0fg"
+ name="CustomCategories" guid="_-bv0GbXuEduGP_98XMd0fg">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_-bv0GrXuEduGP_98XMd0fg"
+ name="Hidden" guid="_-bv0GrXuEduGP_98XMd0fg">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_-bv0G7XuEduGP_98XMd0fg"
+ name="Custom Categories" guid="_-bv0G7XuEduGP_98XMd0fg" presentationName="Custom Categories"/>
+ </childPackages>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_-bv0HLXuEduGP_98XMd0fg"
+ name="CoreContent" guid="_-bv0HLXuEduGP_98XMd0fg">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="__wRXALXuEduGP_98XMd0fg"
+ name="Technical Work Product Slots" guid="__wRXALXuEduGP_98XMd0fg" briefDescription="This package contains the work products that cross practices. They are organized into content packages that are associatd with the practices that produce them. *** Some day I hope that abstract work products can be defined for these and that the concrete work products can be moved to the practices that actually provide the tasks that create these work products.">
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_8OD-cLPTEduocbW-TPTq7A"
+ name="technical_architecture_slot" guid="_8OD-cLPTEduocbW-TPTq7A" briefDescription="This slot represents the documentation of the architecture."
+ presentationName="[Technical Architecture]"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_i3vkoLS-EduDY8LNbMCDBA"
+ name="technical_specification_slot" guid="_i3vkoLS-EduDY8LNbMCDBA" presentationName="[Technical Specification]">
+ <presentation xmi:id="-jbCbONi6H6_jHT7i7yGLtQ" href="uma://-jbCbONi6H6_jHT7i7yGLtQ#-jbCbONi6H6_jHT7i7yGLtQ"/>
+ <containedArtifacts xmi:id="_gX_0gNjhEdyQUcK-3ySmyA" name="requirements_slot"
+ guid="_gX_0gNjhEdyQUcK-3ySmyA" briefDescription="This artifact specifies conditions or capabilities to which an information technology solution must conform."
+ presentationName="[Requirements]">
+ <presentation xmi:id="-dbtxl4sYStfjW4yyXr67hg" href="uma://-dbtxl4sYStfjW4yyXr67hg#-dbtxl4sYStfjW4yyXr67hg"/>
+ </containedArtifacts>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="__ViBYEL8EdyP_Jn83ylwUQ"
+ name="technical_vision_slot_XXX" guid="__ViBYEL8EdyP_Jn83ylwUQ" briefDescription="This artifact contains the definition of the stakeholders' view of the technical solution to be developed, specified in terms of the stakeholders' key needs and features. It contains an outline of the envisioned core requirements for the system."
+ presentationName="[Technical Vision]_XXX">
+ <presentation xmi:id="-q2TOWK55j3CrnAeI2uKzKg" href="uma://-q2TOWK55j3CrnAeI2uKzKg#-q2TOWK55j3CrnAeI2uKzKg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_Vux8UEfUEdyiPI8btkmvmw"
+ name="software_implementation_slot" guid="_Vux8UEfUEdyiPI8btkmvmw" briefDescription="Implementation of the software."
+ presentationName="[Software Implementation]"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_fahB0EfUEdyiPI8btkmvmw"
+ name="technical_test_results_slot" guid="_fahB0EfUEdyiPI8btkmvmw" briefDescription="Results of testing the hardware and software for the system being developed."
+ presentationName="[Technical Test Results]"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_IcQOUEqdEdyi3_jfs__bIQ"
+ name="software_design_slot" guid="_IcQOUEqdEdyi3_jfs__bIQ" briefDescription="This artifact describes the realization of required system functionality and serves as an abstraction of the source code. "
+ presentationName="[Software Design]">
+ <presentation xmi:id="-OEaOjKP9J283DeVnMku6nA" href="uma://-OEaOjKP9J283DeVnMku6nA#-OEaOjKP9J283DeVnMku6nA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_zjwzEKg_Edyn_rXSpKp-cg"
+ name="software_build_slot_XXX" guid="_zjwzEKg_Edyn_rXSpKp-cg" briefDescription="This artifact is the machine readable version of the software implementation."
+ presentationName="[Software Build]_XXX"/>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_ip7wMJI7Edyk6dG0ehkW5Q"
+ name="Guidance Slots" guid="_ip7wMJI7Edyk6dG0ehkW5Q" briefDescription="This package contains guidance slots used by practices to add guidance to other practices.">
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_z_wMgJI7Edyk6dG0ehkW5Q"
+ name="design_guidance_slot" guid="_z_wMgJI7Edyk6dG0ehkW5Q" briefDescription="All guidance related to performing system design tasks."
+ presentationName="[Design Guidance]"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_nOk0sJ6fEdyF5fwOV8Jf8A"
+ name="test_guidance_slot" guid="_nOk0sJ6fEdyF5fwOV8Jf8A" presentationName="[Test Guidance]"/>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_-bv0HbXuEduGP_98XMd0fg"
+ name="CapabilityPatterns" guid="_-bv0HbXuEduGP_98XMd0fg"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_-bv0HrXuEduGP_98XMd0fg"
+ name="DeliveryProcesses" guid="_-bv0HrXuEduGP_98XMd0fg"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_-bv0H7XuEduGP_98XMd0fg"
+ name="ProcessContributions" guid="_-bv0H7XuEduGP_98XMd0fg"/>
+ <bases href="uma://_iVydgENdEdy245g62lfWcA#_iVydgENdEdy245g62lfWcA"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/core.tech.slot.base/workproducts/requirements_slot.xmi b/praclib/temp/core.tech.slot.base/workproducts/requirements_slot.xmi
new file mode 100644
index 0000000..68d9740
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/workproducts/requirements_slot.xmi
@@ -0,0 +1,46 @@
+<?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="-dbtxl4sYStfjW4yyXr67hg"
+ name="new_artifact,_gX_0gNjhEdyQUcK-3ySmyA" guid="-dbtxl4sYStfjW4yyXr67hg" changeDate="2008-02-11T12:41:52.831-0800">
+ <keyConsiderations><ul>
+ <li>
+ A good quality requirement will allow the identification of specific actions, drive clear design and will be one
+ for which it is possible to measure or design a test or verification procedure for a solution.
+ </li>
+ <li>
+ The understanding of requirements changes over time, and so requirements should be revisited and refined as needed.
+ </li>
+ <li>
+ Customers often need guidance in developing requirements that suit their needs.&nbsp;This guidance may consist of
+ both what needs capturing and how it should be represented.
+ </li>
+ <li>
+ Requirements typically affect many different downstream artifacts.&nbsp;Some requirements may have an easily
+ identifiable and relatively localized impact whereas others have a far reaching affect.
+ </li>
+</ul></keyConsiderations>
+ <purpose><p>
+ Requirements are documented to gain agreement on:
+</p>
+<ul>
+ <li>
+ Capabilities needed by a user or organization to solve a problem or to achieve an objective.
+ </li>
+ <li>
+ Constraints that must be satisfied to conform to a contract, standard, or specification
+ </li>
+</ul>
+<p>
+ Requirements are used to derive designs, implementations, and tests for these capabilities and constraints.
+</p></purpose>
+ <impactOfNotHaving><p class="MsoNormal" style="MARGIN: 6pt 0pt">
+ <span style="mso-spacerun: yes">If this artifact is not used, there is a risk that stakeholders and the development
+ team will have different expectations of what is being developed.&nbsp;Additionally, without this artifact it is
+ difficult to determine when the project has been successfully completed. Projects without well defined requirements can
+ experience ‘scope creep’ causing them to run over schedule without being able to determine the cause of the
+ overrun.&nbsp;</span>
+</p></impactOfNotHaving>
+ <representationOptions>Requirements can be captured in models, requirements management tools, documents, or combinations of these.</representationOptions>
+</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/praclib/temp/core.tech.slot.base/workproducts/software_design_slot.xmi b/praclib/temp/core.tech.slot.base/workproducts/software_design_slot.xmi
new file mode 100644
index 0000000..a8a94ee
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/workproducts/software_design_slot.xmi
@@ -0,0 +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="-OEaOjKP9J283DeVnMku6nA"
+ name="software_design_slot,_IcQOUEqdEdyi3_jfs__bIQ" guid="-OEaOjKP9J283DeVnMku6nA"
+ changeDate="2008-01-16T14:20:59.069-0800" version="7.1.0"/>
diff --git a/praclib/temp/core.tech.slot.base/workproducts/technical_specification_slot.xmi b/praclib/temp/core.tech.slot.base/workproducts/technical_specification_slot.xmi
new file mode 100644
index 0000000..6322f5f
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/workproducts/technical_specification_slot.xmi
@@ -0,0 +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="-jbCbONi6H6_jHT7i7yGLtQ"
+ name="technical_requirements_slot,_i3vkoLS-EduDY8LNbMCDBA" guid="-jbCbONi6H6_jHT7i7yGLtQ"
+ changeDate="2008-02-11T12:41:49.330-0800" version="1.0.0"/>
diff --git a/praclib/temp/core.tech.slot.base/workproducts/technical_vision_slot_XXX.xmi b/praclib/temp/core.tech.slot.base/workproducts/technical_vision_slot_XXX.xmi
new file mode 100644
index 0000000..60b07c8
--- /dev/null
+++ b/praclib/temp/core.tech.slot.base/workproducts/technical_vision_slot_XXX.xmi
@@ -0,0 +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="-q2TOWK55j3CrnAeI2uKzKg"
+ name="technical_vision_slot,__ViBYEL8EdyP_Jn83ylwUQ" guid="-q2TOWK55j3CrnAeI2uKzKg"
+ changeDate="2007-12-13T08:45:24.000-0800" version="7.2.0"/>
diff --git a/praclib/temp/library.xmi b/praclib/temp/library.xmi
new file mode 100644
index 0000000..f60e7c5
--- /dev/null
+++ b/praclib/temp/library.xmi
@@ -0,0 +1,170 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xmi:XMI 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:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.ecore"
+ xmlns:epf="http://www.eclipse.org/epf" epf:version="1.2.0">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_TJVNUevFEdyp6czxLiQq9g"
+ guid="_TJVNUevFEdyp6czxLiQq9g">
+ <subManagers xmi:id="_MRPlsUFXEdy9ENCpSugIjA" href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPlsUFXEdy9ENCpSugIjA"/>
+ <subManagers xmi:id="_vsno8UKmEdyrauqpmnA8jQ" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno8UKmEdyrauqpmnA8jQ"/>
+ <subManagers xmi:id="_qLz-kUNdEdy245g62lfWcA" href="uma://_iVydgENdEdy245g62lfWcA#_qLz-kUNdEdy245g62lfWcA"/>
+ <subManagers xmi:id="_A1_toMYaEdyXeo04os5BOw" href="uma://_A118oMYaEdyXeo04os5BOw#_A1_toMYaEdyXeo04os5BOw"/>
+ <subManagers xmi:id="_fRdVIMYbEdyXeo04os5BOw" href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVIMYbEdyXeo04os5BOw"/>
+ <subManagers xmi:id="_nIcf4fL5Edm6Nvont3uinw" href="uma://_WCUhAO8KEdmKSqa_gSYthg#_nIcf4fL5Edm6Nvont3uinw"/>
+ <subManagers xmi:id="_141UsM3pEdyuBO4ZIzcyig" href="uma://_14Ft0M3pEdyuBO4ZIzcyig#_141UsM3pEdyuBO4ZIzcyig"/>
+ <subManagers xmi:id="_jjLggUMXEdyP_Jn83ylwUQ" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_jjLggUMXEdyP_Jn83ylwUQ"/>
+ <subManagers xmi:id="_iR3T8EKmEdyrauqpmnA8jQ" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iR3T8EKmEdyrauqpmnA8jQ"/>
+ <subManagers xmi:id="_CX-9EM3qEdyuBO4ZIzcyig" href="uma://_CX-9AM3qEdyuBO4ZIzcyig#_CX-9EM3qEdyuBO4ZIzcyig"/>
+ <subManagers xmi:id="_0UM7YJ-VEdy3Nc4rvuj7bA" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0UM7YJ-VEdy3Nc4rvuj7bA"/>
+ <subManagers xmi:id="_vJYugUfUEdyiPI8btkmvmw" href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYugUfUEdyiPI8btkmvmw"/>
+ <subManagers xmi:id="_LdRtoM3qEdyuBO4ZIzcyig" href="uma://_LdRtkM3qEdyuBO4ZIzcyig#_LdRtoM3qEdyuBO4ZIzcyig"/>
+ <subManagers xmi:id="_OOK_8AouEdyhlpBPrduOMw" href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOK_8AouEdyhlpBPrduOMw"/>
+ <subManagers xmi:id="_-cCH8LXuEduGP_98XMd0fg" href="uma://_-bv0ELXuEduGP_98XMd0fg#_-cCH8LXuEduGP_98XMd0fg"/>
+ <subManagers xmi:id="_Nh8IAa0EEdyKsPiG2Ur1fQ" href="uma://_Nh8H8K0EEdyKsPiG2Ur1fQ#_Nh8IAa0EEdyKsPiG2Ur1fQ"/>
+ <subManagers xmi:id="_4-jR8UbFEdyx8quJU3Grxg" href="uma://_4-jR4EbFEdyx8quJU3Grxg#_4-jR8UbFEdyx8quJU3Grxg"/>
+ <subManagers xmi:id="_iNwFwMhNEdygFZkm1d5NtQ" href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_iNwFwMhNEdygFZkm1d5NtQ"/>
+ <subManagers xmi:id="_qqyzEJ6WEdyQN-zRFaRrCQ" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzEJ6WEdyQN-zRFaRrCQ"/>
+ <subManagers xmi:id="_4gXdsL8BEdyWX5Yd-9QZ1A" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdsL8BEdyWX5Yd-9QZ1A"/>
+ <subManagers xmi:id="_NBRH0Mh3EdygFZkm1d5NtQ" href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_NBRH0Mh3EdygFZkm1d5NtQ"/>
+ <subManagers xmi:id="_nKb_wJ6YEdyQN-zRFaRrCQ" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKb_wJ6YEdyQN-zRFaRrCQ"/>
+ <subManagers xmi:id="_402MAJ6YEdyQN-zRFaRrCQ" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_402MAJ6YEdyQN-zRFaRrCQ"/>
+ <subManagers xmi:id="_IItp8MuXEdyLOriywSJkoQ" href="uma://_IItp4MuXEdyLOriywSJkoQ#_IItp8MuXEdyLOriywSJkoQ"/>
+ <subManagers xmi:id="_H0G_MG5KEdyAHIxjZ9kpqw" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_H0G_MG5KEdyAHIxjZ9kpqw"/>
+ <subManagers xmi:id="_iADyQM3PEdyKkus0T68H3Q" href="uma://_h_9roM3PEdyKkus0T68H3Q#_iADyQM3PEdyKkus0T68H3Q"/>
+ <subManagers xmi:id="_D_3hAMktEdygFZkm1d5NtQ" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D_3hAMktEdygFZkm1d5NtQ"/>
+ <subManagers xmi:id="_GxLUAM2sEdym_ZFqrJcXUg" href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_GxLUAM2sEdym_ZFqrJcXUg"/>
+ <subManagers xmi:id="_4ggZgbPREduocbW-TPTq7A" href="uma://_4gaS4LPREduocbW-TPTq7A#_4ggZgbPREduocbW-TPTq7A"/>
+ <subManagers xmi:id="_XPLEAMudEdyRPtFYRAKVDg" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_XPLEAMudEdyRPtFYRAKVDg"/>
+ <subManagers xmi:id="_Z20lULPPEduocbW-TPTq7A" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z20lULPPEduocbW-TPTq7A"/>
+ <subManagers xmi:id="_NjWMAMrmEdyd6uFrFHNXhA" href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_NjWMAMrmEdyd6uFrFHNXhA"/>
+ <subManagers xmi:id="_Y9TKQbS9EduDY8LNbMCDBA" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKQbS9EduDY8LNbMCDBA"/>
+ <subManagers xmi:id="_005S0Mt1EdyRPtFYRAKVDg" href="uma://_00zMMMt1EdyRPtFYRAKVDg#_005S0Mt1EdyRPtFYRAKVDg"/>
+ <subManagers xmi:id="_DaytUI7-Edy7q8CKc_B8eg" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DaytUI7-Edy7q8CKc_B8eg"/>
+ <subManagers xmi:id="_HZfOoMriEdyd6uFrFHNXhA" href="uma://_HYAA4MriEdyd6uFrFHNXhA#_HZfOoMriEdyd6uFrFHNXhA"/>
+ <subManagers xmi:id="_GbYfYbPaEduocbW-TPTq7A" href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfYbPaEduocbW-TPTq7A"/>
+ <subManagers xmi:id="_Z7teENQ1EdyQ89W1tgswSQ" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_Z7teENQ1EdyQ89W1tgswSQ"/>
+ <subManagers xmi:id="_4ulTkMg7EdyXeo04os5BOw" href="uma://_4ulTgMg7EdyXeo04os5BOw#_4ulTkMg7EdyXeo04os5BOw"/>
+ <resourceDescriptors xmi:id="_TJVNUuvFEdyp6czxLiQq9g" id="_TJVNUOvFEdyp6czxLiQq9g"
+ uri=""/>
+ <resourceDescriptors xmi:id="_bLklcOvFEdyp6czxLiQq9g" id="_MRPloEFXEdy9ENCpSugIjA"
+ uri="core.default.cat_def.base/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bMBRYOvFEdyp6czxLiQq9g" id="_vsno4EKmEdyrauqpmnA8jQ"
+ uri="core.default.nav_view.base/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bMLCZ-vFEdyp6czxLiQq9g" id="_iVydgENdEdy245g62lfWcA"
+ uri="core.default.release_copyright.base/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bMUMZOvFEdyp6czxLiQq9g" id="_A118oMYaEdyXeo04os5BOw"
+ uri="core.default.role_def.base/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bNqQIOvFEdyp6czxLiQq9g" id="_fRdVEMYbEdyXeo04os5BOw"
+ uri="core.default.tool_def.base/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bOG8EOvFEdyp6czxLiQq9g" id="_WCUhAO8KEdmKSqa_gSYthg"
+ uri="core.default.uma_concept.base/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bOQtEOvFEdyp6czxLiQq9g" id="_14Ft0M3pEdyuBO4ZIzcyig"
+ uri="core.gen.common.assign/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bOZ3B-vFEdyp6czxLiQq9g" id="_ji3-gEMXEdyP_Jn83ylwUQ"
+ uri="core.gen.common.base/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bOjoE-vFEdyp6czxLiQq9g" id="_iRbPEEKmEdyrauqpmnA8jQ"
+ uri="core.gen.slot.base/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bOsx_uvFEdyp6czxLiQq9g" id="_CX-9AM3qEdyuBO4ZIzcyig"
+ uri="core.mgmt.common.assign/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bPAUA-vFEdyp6czxLiQq9g" id="_0TmecJ-VEdy3Nc4rvuj7bA"
+ uri="core.mgmt.common.base/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bPJd-OvFEdyp6czxLiQq9g" id="_vJYucEfUEdyiPI8btkmvmw"
+ uri="core.mgmt.slot.base/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bPTO8OvFEdyp6czxLiQq9g" id="_LdRtkM3qEdyuBO4ZIzcyig"
+ uri="core.tech.common.assign/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bPv60OvFEdyp6czxLiQq9g" id="_OOB2AAouEdyhlpBPrduOMw"
+ uri="core.tech.common.base/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bP5E0-vFEdyp6czxLiQq9g" id="_-bv0ELXuEduGP_98XMd0fg"
+ uri="core.tech.slot.base/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bSIgcOvFEdyp6czxLiQq9g" id="_Nh8H8K0EEdyKsPiG2Ur1fQ"
+ uri="meth_mgmt.review_status.base/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bSlMYOvFEdyp6czxLiQq9g" id="_4-jR4EbFEdyx8quJU3Grxg"
+ uri="obsoleted_from_openup/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bS4HUOvFEdyp6czxLiQq9g" id="_iNwFsMhNEdygFZkm1d5NtQ"
+ uri="practice.mgmt.iterative_dev.assign/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bTUzX-vFEdyp6czxLiQq9g" id="_qqyzAJ6WEdyQN-zRFaRrCQ"
+ uri="practice.mgmt.iterative_dev.base/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bUEaLOvFEdyp6czxLiQq9g" id="_4gXdoL8BEdyWX5Yd-9QZ1A"
+ uri="practice.mgmt.risk_value_lifecycle.base/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bUNkJOvFEdyp6czxLiQq9g" id="_NBRHwMh3EdygFZkm1d5NtQ"
+ uri="practice.mgmt.two_level_project_planning.assign/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bUqQAOvFEdyp6czxLiQq9g" id="_nKS10J6YEdyQN-zRFaRrCQ"
+ uri="practice.mgmt.two_level_project_planning.base/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bU0BAOvFEdyp6czxLiQq9g" id="_40sbAJ6YEdyQN-zRFaRrCQ"
+ uri="practice.mgmt.whole_team.base/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bU9K-evFEdyp6czxLiQq9g" id="_IItp4MuXEdyLOriywSJkoQ"
+ uri="practice.tech.agile_testing.assign/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bVQtCOvFEdyp6czxLiQq9g" id="_Hz9OMG5KEdyAHIxjZ9kpqw"
+ uri="practice.tech.agile_testing.base/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bVjn4OvFEdyp6czxLiQq9g" id="_h_9roM3PEdyKkus0T68H3Q"
+ uri="practice.tech.continuous_integration.assign/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bVtY4OvFEdyp6czxLiQq9g" id="_D-ExQMktEdygFZkm1d5NtQ"
+ uri="practice.tech.continuous_integration.base/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bV2i3-vFEdyp6czxLiQq9g" id="_GxBjAM2sEdym_ZFqrJcXUg"
+ uri="practice.tech.evolutionary_arch.assign/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bWJd0OvFEdyp6czxLiQq9g" id="_4gaS4LPREduocbW-TPTq7A"
+ uri="practice.tech.evolutionary_arch.base/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bWTO2evFEdyp6czxLiQq9g" id="_XPLD8MudEdyRPtFYRAKVDg"
+ uri="practice.tech.evolutionary_design.assign/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bWv6sOvFEdyp6czxLiQq9g" id="_Z2cK0LPPEduocbW-TPTq7A"
+ uri="practice.tech.evolutionary_design.base/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bW5rxOvFEdyp6czxLiQq9g" id="_NjNCEMrmEdyd6uFrFHNXhA"
+ uri="practice.tech.shared_vision.assign/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bXVwkOvFEdyp6czxLiQq9g" id="_Y9TKMLS9EduDY8LNbMCDBA"
+ uri="practice.tech.shared_vision.base/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bXpSkOvFEdyp6czxLiQq9g" id="_00zMMMt1EdyRPtFYRAKVDg"
+ uri="practice.tech.test_driven_development.assign/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bX8NgOvFEdyp6czxLiQq9g" id="_DZ1rEI7-Edy7q8CKc_B8eg"
+ uri="practice.tech.test_driven_development.base/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bYFXc-vFEdyp6czxLiQq9g" id="_HYAA4MriEdyd6uFrFHNXhA"
+ uri="practice.tech.use_case_driven_dev.assign/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bYY5fevFEdyp6czxLiQq9g" id="_GbYfULPaEduocbW-TPTq7A"
+ uri="practice.tech.use_case_driven_dev.base/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bbhF8OvFEdyp6czxLiQq9g" id="_Z7teANQ1EdyQ89W1tgswSQ"
+ uri="process.openup.base/plugin.xmi"/>
+ <resourceDescriptors xmi:id="_bcG70OvFEdyp6czxLiQq9g" id="_4ulTgMg7EdyXeo04os5BOw"
+ uri="publish.openup.base/plugin.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:MethodLibrary xmi:id="_TJVNUOvFEdyp6czxLiQq9g" name="EPFPracLib_20080306"
+ guid="_TJVNUOvFEdyp6czxLiQq9g">
+ <methodPlugins xmi:id="_MRPloEFXEdy9ENCpSugIjA" href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPloEFXEdy9ENCpSugIjA"/>
+ <methodPlugins xmi:id="_vsno4EKmEdyrauqpmnA8jQ" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno4EKmEdyrauqpmnA8jQ"/>
+ <methodPlugins xmi:id="_iVydgENdEdy245g62lfWcA" href="uma://_iVydgENdEdy245g62lfWcA#_iVydgENdEdy245g62lfWcA"/>
+ <methodPlugins xmi:id="_A118oMYaEdyXeo04os5BOw" href="uma://_A118oMYaEdyXeo04os5BOw#_A118oMYaEdyXeo04os5BOw"/>
+ <methodPlugins xmi:id="_fRdVEMYbEdyXeo04os5BOw" href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVEMYbEdyXeo04os5BOw"/>
+ <methodPlugins xmi:id="_WCUhAO8KEdmKSqa_gSYthg" href="uma://_WCUhAO8KEdmKSqa_gSYthg#_WCUhAO8KEdmKSqa_gSYthg"/>
+ <methodPlugins xmi:id="_14Ft0M3pEdyuBO4ZIzcyig" href="uma://_14Ft0M3pEdyuBO4ZIzcyig#_14Ft0M3pEdyuBO4ZIzcyig"/>
+ <methodPlugins xmi:id="_ji3-gEMXEdyP_Jn83ylwUQ" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-gEMXEdyP_Jn83ylwUQ"/>
+ <methodPlugins xmi:id="_iRbPEEKmEdyrauqpmnA8jQ" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPEEKmEdyrauqpmnA8jQ"/>
+ <methodPlugins xmi:id="_CX-9AM3qEdyuBO4ZIzcyig" href="uma://_CX-9AM3qEdyuBO4ZIzcyig#_CX-9AM3qEdyuBO4ZIzcyig"/>
+ <methodPlugins xmi:id="_0TmecJ-VEdy3Nc4rvuj7bA" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0TmecJ-VEdy3Nc4rvuj7bA"/>
+ <methodPlugins xmi:id="_vJYucEfUEdyiPI8btkmvmw" href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYucEfUEdyiPI8btkmvmw"/>
+ <methodPlugins xmi:id="_LdRtkM3qEdyuBO4ZIzcyig" href="uma://_LdRtkM3qEdyuBO4ZIzcyig#_LdRtkM3qEdyuBO4ZIzcyig"/>
+ <methodPlugins xmi:id="_OOB2AAouEdyhlpBPrduOMw" href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2AAouEdyhlpBPrduOMw"/>
+ <methodPlugins xmi:id="_-bv0ELXuEduGP_98XMd0fg" href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0ELXuEduGP_98XMd0fg"/>
+ <methodPlugins xmi:id="_Nh8H8K0EEdyKsPiG2Ur1fQ" href="uma://_Nh8H8K0EEdyKsPiG2Ur1fQ#_Nh8H8K0EEdyKsPiG2Ur1fQ"/>
+ <methodPlugins xmi:id="_4-jR4EbFEdyx8quJU3Grxg" href="uma://_4-jR4EbFEdyx8quJU3Grxg#_4-jR4EbFEdyx8quJU3Grxg"/>
+ <methodPlugins xmi:id="_iNwFsMhNEdygFZkm1d5NtQ" href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_iNwFsMhNEdygFZkm1d5NtQ"/>
+ <methodPlugins xmi:id="_qqyzAJ6WEdyQN-zRFaRrCQ" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzAJ6WEdyQN-zRFaRrCQ"/>
+ <methodPlugins xmi:id="_4gXdoL8BEdyWX5Yd-9QZ1A" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdoL8BEdyWX5Yd-9QZ1A"/>
+ <methodPlugins xmi:id="_NBRHwMh3EdygFZkm1d5NtQ" href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_NBRHwMh3EdygFZkm1d5NtQ"/>
+ <methodPlugins xmi:id="_nKS10J6YEdyQN-zRFaRrCQ" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS10J6YEdyQN-zRFaRrCQ"/>
+ <methodPlugins xmi:id="_40sbAJ6YEdyQN-zRFaRrCQ" href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_40sbAJ6YEdyQN-zRFaRrCQ"/>
+ <methodPlugins xmi:id="_IItp4MuXEdyLOriywSJkoQ" href="uma://_IItp4MuXEdyLOriywSJkoQ#_IItp4MuXEdyLOriywSJkoQ"/>
+ <methodPlugins xmi:id="_Hz9OMG5KEdyAHIxjZ9kpqw" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9OMG5KEdyAHIxjZ9kpqw"/>
+ <methodPlugins xmi:id="_h_9roM3PEdyKkus0T68H3Q" href="uma://_h_9roM3PEdyKkus0T68H3Q#_h_9roM3PEdyKkus0T68H3Q"/>
+ <methodPlugins xmi:id="_D-ExQMktEdygFZkm1d5NtQ" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExQMktEdygFZkm1d5NtQ"/>
+ <methodPlugins xmi:id="_GxBjAM2sEdym_ZFqrJcXUg" href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_GxBjAM2sEdym_ZFqrJcXUg"/>
+ <methodPlugins xmi:id="_4gaS4LPREduocbW-TPTq7A" href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS4LPREduocbW-TPTq7A"/>
+ <methodPlugins xmi:id="_XPLD8MudEdyRPtFYRAKVDg" href="uma://_XPLD8MudEdyRPtFYRAKVDg#_XPLD8MudEdyRPtFYRAKVDg"/>
+ <methodPlugins xmi:id="_Z2cK0LPPEduocbW-TPTq7A" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK0LPPEduocbW-TPTq7A"/>
+ <methodPlugins xmi:id="_NjNCEMrmEdyd6uFrFHNXhA" href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_NjNCEMrmEdyd6uFrFHNXhA"/>
+ <methodPlugins xmi:id="_Y9TKMLS9EduDY8LNbMCDBA" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKMLS9EduDY8LNbMCDBA"/>
+ <methodPlugins xmi:id="_00zMMMt1EdyRPtFYRAKVDg" href="uma://_00zMMMt1EdyRPtFYRAKVDg#_00zMMMt1EdyRPtFYRAKVDg"/>
+ <methodPlugins xmi:id="_DZ1rEI7-Edy7q8CKc_B8eg" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rEI7-Edy7q8CKc_B8eg"/>
+ <methodPlugins xmi:id="_HYAA4MriEdyd6uFrFHNXhA" href="uma://_HYAA4MriEdyd6uFrFHNXhA#_HYAA4MriEdyd6uFrFHNXhA"/>
+ <methodPlugins xmi:id="_GbYfULPaEduocbW-TPTq7A" href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfULPaEduocbW-TPTq7A"/>
+ <methodPlugins xmi:id="_Z7teANQ1EdyQ89W1tgswSQ" href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_Z7teANQ1EdyQ89W1tgswSQ"/>
+ <methodPlugins xmi:id="_4ulTgMg7EdyXeo04os5BOw" href="uma://_4ulTgMg7EdyXeo04os5BOw#_4ulTgMg7EdyXeo04os5BOw"/>
+ </org.eclipse.epf.uma:MethodLibrary>
+</xmi:XMI>
diff --git a/praclib/temp/meth_mgmt.review_status.base/.project b/praclib/temp/meth_mgmt.review_status.base/.project
new file mode 100644
index 0000000..adb0a8d
--- /dev/null
+++ b/praclib/temp/meth_mgmt.review_status.base/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>meth_mgmt.review_status.base</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/meth_mgmt.review_status.base/plugin.xmi b/praclib/temp/meth_mgmt.review_status.base/plugin.xmi
new file mode 100644
index 0000000..a26f6c9
--- /dev/null
+++ b/praclib/temp/meth_mgmt.review_status.base/plugin.xmi
@@ -0,0 +1,217 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_Nh8IAa0EEdyKsPiG2Ur1fQ"
+ guid="_Nh8IAa0EEdyKsPiG2Ur1fQ"/>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_Nh8H8K0EEdyKsPiG2Ur1fQ" name="meth_mgmt.review_status.base"
+ guid="_Nh8H8K0EEdyKsPiG2Ur1fQ" changeDate="2008-01-31T09:58:34.093-0500">
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Nh8H8a0EEdyKsPiG2Ur1fQ"
+ name="Content" guid="_Nh8H8a0EEdyKsPiG2Ur1fQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Nh8H8q0EEdyKsPiG2Ur1fQ"
+ name="Categories" guid="_Nh8H8q0EEdyKsPiG2Ur1fQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Nh8H860EEdyKsPiG2Ur1fQ"
+ name="Domains" guid="_Nh8H860EEdyKsPiG2Ur1fQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Nh8H9K0EEdyKsPiG2Ur1fQ"
+ name="Disciplines" guid="_Nh8H9K0EEdyKsPiG2Ur1fQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Nh8H9a0EEdyKsPiG2Ur1fQ"
+ name="RoleSets" guid="_Nh8H9a0EEdyKsPiG2Ur1fQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Nh8H9q0EEdyKsPiG2Ur1fQ"
+ name="WP Types" guid="_Nh8H9q0EEdyKsPiG2Ur1fQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Nh8H960EEdyKsPiG2Ur1fQ"
+ name="Tools" guid="_Nh8H960EEdyKsPiG2Ur1fQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Nh8H-K0EEdyKsPiG2Ur1fQ"
+ name="StandardCategories" guid="_Nh8H-K0EEdyKsPiG2Ur1fQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Nh8H-a0EEdyKsPiG2Ur1fQ"
+ name="CustomCategories" guid="_Nh8H-a0EEdyKsPiG2Ur1fQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Nh8H-q0EEdyKsPiG2Ur1fQ"
+ name="Hidden" guid="_Nh8H-q0EEdyKsPiG2Ur1fQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_Nh8H-60EEdyKsPiG2Ur1fQ"
+ name="Custom Categories" guid="_Nh8H-60EEdyKsPiG2Ur1fQ" categorizedElements="_OjpckK0EEdyKsPiG2Ur1fQ _UMjl0K0EEdyKsPiG2Ur1fQ _XIKbUK0EEdyKsPiG2Ur1fQ _aBh1IK0EEdyKsPiG2Ur1fQ"/>
+ </childPackages>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_OjpckK0EEdyKsPiG2Ur1fQ"
+ name="passed_review" guid="_OjpckK0EEdyKsPiG2Ur1fQ" presentationName="Passed Review">
+ <methodElementProperty xmi:id="_SCuLgK0EEdyKsPiG2Ur1fQ" name="PUBLISH_CATEGORY"
+ value="true"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Template" href="uma://_OOB2AAouEdyhlpBPrduOMw#_3Y3XUI5fEdyO5aWob1UGDA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_GbYfULPaEduocbW-TPTq7A#_4BJ_YCxSEdqjsdw1QLH_6Q"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:TermDefinition" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_PgYREAeYEduWycDgioo5rg"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:TermDefinition" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_WUiFcAeYEduWycDgioo5rg"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0VGbUMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0WVxcMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_i3vkoLS-EduDY8LNbMCDBA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_UMjl0K0EEdyKsPiG2Ur1fQ"
+ name="ready_for_review" guid="_UMjl0K0EEdyKsPiG2Ur1fQ" presentationName="Ready for Review">
+ <methodElementProperty xmi:id="_WIPPYK0EEdyKsPiG2Ur1fQ" name="PUBLISH_CATEGORY"
+ value="true"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZS-0MlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZlSsMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZfMEMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Task" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_0iwc0clgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Task" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_0jO98MlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Task" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_0jVEkMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Checklist" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0Zxf8MlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Checklist" href="uma://_OOB2AAouEdyhlpBPrduOMw#_KZQJMBhBEduxCP6DVVLxsA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0jnYcMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0jzlsMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Checklist" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0Z9tMMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0aDz0MlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0aJ6cMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_JqYbgJ01EdyQ3oTO93enUw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_Poc7IPDzEdqYgerqi84oCA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_zjwzEKg_Edyn_rXSpKp-cg"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_Vux8UEfUEdyiPI8btkmvmw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_aGqAsJ01EdyQ3oTO93enUw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_kh9FcJ02EdyQ3oTO93enUw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_ADwlAJRtEdyrdaw_xGakyw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Task" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_znlIcJR9EdyVKbgqUOtqQA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Task" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_Ht-z8JfJEdyZkIR-s-Y8wQ"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Checklist" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_etwusJ01EdyQ3oTO93enUw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_YNx2sJ05EdyQ3oTO93enUw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_mlKb8JyJEdy9brKHb521mQ"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Task" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_R7atwJfIEdyZkIR-s-Y8wQ"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_2n8hUKNTEdywLvvgt1gQ3Q"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_2ZPqEKhNEdymmoKrEVbjiw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Roadmap" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_8yG48JRqEdyrdaw_xGakyw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Whitepaper" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_t7IacJRmEdyrdaw_xGakyw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_5s_DUJ03EdyQ3oTO93enUw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_aI-NgJ04EdyQ3oTO93enUw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_hFhQQJ01EdyQ3oTO93enUw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Example" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_QeE7YMCsEdyHnYlsYwuJQw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_xYMPoCZnEdyUaK463Ozu5g"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_xYMPoCZnEdyUaK463Ozu5g"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_ByOd4O6pEduvoopEslG-4g"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Template" href="uma://_OOB2AAouEdyhlpBPrduOMw#_m7p-AI5fEdyO5aWob1UGDA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Task" href="uma://_GbYfULPaEduocbW-TPTq7A#_4z8Z0EbEEdyx8quJU3Grxg"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Task" href="uma://_GbYfULPaEduocbW-TPTq7A#_SL7N0LPdEduocbW-TPTq7A"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Task" href="uma://_GbYfULPaEduocbW-TPTq7A#_-pOLIEbEEdyx8quJU3Grxg"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Task" href="uma://_GbYfULPaEduocbW-TPTq7A#_txpV0AFmEduDPKiaP0pu-Q"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Task" href="uma://_GbYfULPaEduocbW-TPTq7A#_P9cMUPV_EdmdHa9MmVPgqQ"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_Wn7HcNcEEdqz_d2XWoVt6Q"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_XNPOoEMDEdyP_Jn83ylwUQ"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_BVh9cL-CEdqb7N6KIeDL8Q"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#__ViBYEL8EdyP_Jn83ylwUQ"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_W2SgEDR5EdutE_HNDTJk5Q"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Checklist" href="uma://_OOB2AAouEdyhlpBPrduOMw#_Vael8CGMEdu3VKXZx45D3A"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Checklist" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0U6OEMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:CustomCategory" href="uma://_GbYfULPaEduocbW-TPTq7A#_lmNCoJ-lEdyBk-WQzMU-FQ"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_Z2cK0LPPEduocbW-TPTq7A#__MnggPTdEduDKIuqTXQ8SA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_bFjlAPTYEduDKIuqTXQ8SA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Template" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_EOPcMAMUEdylNddAObilIA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Checklist" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_0XSzsMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Task" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_0fshwMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:SupportingMaterial"
+ href="uma://_Z2cK0LPPEduocbW-TPTq7A#_FxgacOCqEdynptYdmll41Q"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_C4U9QPTeEduDKIuqTXQ8SA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Roadmap" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_irQiEOCsEdynptYdmll41Q"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_OlyWoOX7Edu8VZPtlaU33g"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:SupportingMaterial"
+ href="uma://_Z2cK0LPPEduocbW-TPTq7A#_skRykMuYEdyRPtFYRAKVDg"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_jJqygEqlEdyi3_jfs__bIQ"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_0WuL8slgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_m42lMPTeEduDKIuqTXQ8SA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Task" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_T8WvwL3vEdqLRJZPGVbHDA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Checklist" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_nnSXcD6SEduAL-bCqar_dg"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_ZTGAYL3uEdqLRJZPGVbHDA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_1fM3AC9_EduW5uTjiIcspQ"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_jkvJEPTeEduDKIuqTXQ8SA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:CustomCategory" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_h6kZgMLzEdyBCJ57WNAp3w"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_HZGFsKrPEdu6T6WyNqBzqQ"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0gvqoMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_jdKSsNpiEdyP58ppo1Ieaw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_HlRqANpbEdyP58ppo1Ieaw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_mzxI0A4LEduibvKwrGxWxA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_HrZGIA4MEduibvKwrGxWxA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_kgtcoNc8Edyd7OybSySFxg"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Example" href="uma://_OOB2AAouEdyhlpBPrduOMw#_eQ_s8Om5Edupia_tZIXEqg"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Example" href="uma://_OOB2AAouEdyhlpBPrduOMw#_O39h0O9pEdu635i_iQ5Jag"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0YP18MlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_O1kAANvfEduv2KOT-Teh6w"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Example" href="uma://_OOB2AAouEdyhlpBPrduOMw#_4bC4cNs_EdyEW4klSH3vRA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_pLEGUNqGEdy88NBoQgfGyg"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0gjdYMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#__O7tAMVvEduLYZUGfgZrkQ"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_OOB2AAouEdyhlpBPrduOMw#_34jWsLcIEduRNaXpzCOLXQ"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0SsecNr8EdyXE6np2_hUMA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0XY6UMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_OOB2AAouEdyhlpBPrduOMw#_we3F4ACpEdu8m4dIntu6jA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0gpkAMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0YJvUMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_OOB2AAouEdyhlpBPrduOMw#_vO2uoO0OEduUpsu85bVhiQ"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_4gaS4LPREduocbW-TPTq7A#_G0xGANfdEdy8T_PKWvNDBA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Task" href="uma://_4gaS4LPREduocbW-TPTq7A#_s4ojQNqREdy88NBoQgfGyg"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_4gaS4LPREduocbW-TPTq7A#_HrgUQNcuEdy1nJEYZGzN4A"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Task" href="uma://_4gaS4LPREduocbW-TPTq7A#_1kmN0NqREdy88NBoQgfGyg"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_4gaS4LPREduocbW-TPTq7A#_QHYwcM3jEdyjXslGsagg_w"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Template" href="uma://_4gaS4LPREduocbW-TPTq7A#_me8WcAANEdyRS9uciXlZ6g"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Checklist" href="uma://_4gaS4LPREduocbW-TPTq7A#_17PYUNd6EdmIm-bsRSNCgw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Task" href="uma://_4gaS4LPREduocbW-TPTq7A#_0f-1oMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Task" href="uma://_4gaS4LPREduocbW-TPTq7A#_0gRJgMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Roadmap" href="uma://_4gaS4LPREduocbW-TPTq7A#_Odpz8NciEdy1nJEYZGzN4A"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_4gaS4LPREduocbW-TPTq7A#_SPSs0NcSEdy1nJEYZGzN4A"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_4gaS4LPREduocbW-TPTq7A#_0XAf0MlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:SupportingMaterial"
+ href="uma://_4gaS4LPREduocbW-TPTq7A#_rA1NMc3lEdyjXslGsagg_w"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_XIKbUK0EEdyKsPiG2Ur1fQ"
+ name="returned_for_rework" guid="_XIKbUK0EEdyKsPiG2Ur1fQ" presentationName="Returned for Rework">
+ <methodElementProperty xmi:id="_ZkeFsK0EEdyKsPiG2Ur1fQ" name="PUBLISH_CATEGORY"
+ value="true"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Task" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_0fOAoMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Task" href="uma://_GbYfULPaEduocbW-TPTq7A#_SL7N0LPdEduocbW-TPTq7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_aBh1IK0EEdyKsPiG2Ur1fQ"
+ name="work_in_progress" guid="_aBh1IK0EEdyKsPiG2Ur1fQ" presentationName="Work In Progress">
+ <methodElementProperty xmi:id="_cQb8sK0EEdyKsPiG2Ur1fQ" name="PUBLISH_CATEGORY"
+ value="true"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Template" href="uma://_OOB2AAouEdyhlpBPrduOMw#_DtlRQI5gEdyO5aWob1UGDA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_eYtQQO0KEdqHTdbLTmC5IQ"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Checklist" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0kNwINk1Edq2Q8qZoWbvGA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_OOB2AAouEdyhlpBPrduOMw#_E-dPIL-GEdqb7N6KIeDL8Q"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Checklist" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0VrDEMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:CustomCategory" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_a1LJAJ-lEdyBk-WQzMU-FQ"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_KudM0NcJEdqz_d2XWoVt6Q"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_zGqO0MDpEduTGJ8i4u8TMw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_OOB2AAouEdyhlpBPrduOMw#_1AOsMO0JEdqHTdbLTmC5IQ"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_zjwzEKg_Edyn_rXSpKp-cg"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_OOB2AAouEdyhlpBPrduOMw#_6jXzYNcKEdqz_d2XWoVt6Q"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Checklist" href="uma://_OOB2AAouEdyhlpBPrduOMw#_jxn9EO0HEdqHTdbLTmC5IQ"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_JqYbgJ01EdyQ3oTO93enUw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_OOB2AAouEdyhlpBPrduOMw#_OnoNQNSAEdmLhZ9H5Plxyw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_GbYfULPaEduocbW-TPTq7A#_eyL0wCu-EdqSxKAVa9kmvA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_2jyfUAhVEduRe8TeoBmuGg"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_GbYfULPaEduocbW-TPTq7A#_0VAUsMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_VQ268O0KEdqHTdbLTmC5IQ"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_GbYfULPaEduocbW-TPTq7A#_qq0GMAXkEduj_7BEUj1JfQ"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_GbYfULPaEduocbW-TPTq7A#_wr24gNcGEdqz_d2XWoVt6Q"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Checklist" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0WoFUMlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Nh8H_K0EEdyKsPiG2Ur1fQ"
+ name="CoreContent" guid="_Nh8H_K0EEdyKsPiG2Ur1fQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_Nh8H_a0EEdyKsPiG2Ur1fQ"
+ name="CapabilityPatterns" guid="_Nh8H_a0EEdyKsPiG2Ur1fQ"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_Nh8H_q0EEdyKsPiG2Ur1fQ"
+ name="DeliveryProcesses" guid="_Nh8H_q0EEdyKsPiG2Ur1fQ"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_Nh8H_60EEdyKsPiG2Ur1fQ"
+ name="ProcessContributions" guid="_Nh8H_60EEdyKsPiG2Ur1fQ"/>
+ <bases href="uma://_WCUhAO8KEdmKSqa_gSYthg#_WCUhAO8KEdmKSqa_gSYthg"/>
+ <bases href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno4EKmEdyrauqpmnA8jQ"/>
+ <bases href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-gEMXEdyP_Jn83ylwUQ"/>
+ <bases href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPEEKmEdyrauqpmnA8jQ"/>
+ <bases href="uma://_iVydgENdEdy245g62lfWcA#_iVydgENdEdy245g62lfWcA"/>
+ <bases href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2AAouEdyhlpBPrduOMw"/>
+ <bases href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0ELXuEduGP_98XMd0fg"/>
+ <bases href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9OMG5KEdyAHIxjZ9kpqw"/>
+ <bases href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK0LPPEduocbW-TPTq7A"/>
+ <bases href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS4LPREduocbW-TPTq7A"/>
+ <bases href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKMLS9EduDY8LNbMCDBA"/>
+ <bases href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfULPaEduocbW-TPTq7A"/>
+ <bases href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rEI7-Edy7q8CKc_B8eg"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/obsoleted_from_openup/.project b/praclib/temp/obsoleted_from_openup/.project
new file mode 100644
index 0000000..9ef0cf4
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>obsoleted_from_openup</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/concepts/four_plus_one_view_of_arch.xmi b/praclib/temp/obsoleted_from_openup/guidances/concepts/four_plus_one_view_of_arch.xmi
new file mode 100644
index 0000000..9c5ea39
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/concepts/four_plus_one_view_of_arch.xmi
@@ -0,0 +1,73 @@
+<?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="-cnGBBA4NXmhTIjHjlHx4Mw"
+ name=",_T9nygClEEduLGM8dfVsrKg" guid="-cnGBBA4NXmhTIjHjlHx4Mw" changeDate="2008-02-09T14:36:39.468-0500"
+ version="7.1.0">
+ <mainDescription><p>
+ As an Architect, you may want to consider the following views (not all views are relevant to all systems or all the
+ Stakeholders). This set of views is known as the 4+1 Views of Software Architecture [<a class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/references_6CCF393.html"
+ guid="_9ToeIB83Edqsvps02rpOOg">KRU95</a>].
+</p>
+<p>
+ <img height="254" alt="4+1 Views of Software Architecture" src="./resources/4plus1_2.jpg" width="405" />
+</p>
+<ul>
+ <li>
+ <p>
+ Use-case view: Describes functionality of the system, its external interfaces, and its principal users. This
+ view is mandatory when using the 4+1 Views, because all elements of the architecture should be derived from
+ requirements.
+ </p>
+ </li>
+ <li>
+ <p>
+ Logical view: Describes how the system is structured in terms of units of implementation. The elements are
+ packages, classes, and interfaces. The relationship between elements shows dependencies, interface
+ realizations, part-whole relationships, and so forth. Note: This view is mandatory when using the 4+1 Views of
+ Software Architecture.
+ </p>
+ </li>
+ <li>
+ <p>
+ Implementation view: Describes how development artifacts are organized in the file system. The elements are
+ files and directories (any configuration items). This includes development artifacts and deployment artifacts.
+ This view is optional when using the 4+1 Views.
+ </p>
+ </li>
+ <li>
+ <p>
+ Process view: Describes how the run-time system is structured as a set of elements that have run-time behavior
+ and interactions. Run-time structure often bears little resemblance to the code structure. It consists of
+ rapidly changing networks of communication objects. The elements are components that have run-time presence
+ (processes, threads, Enterprise JavaBeans&trade; (EJB&trade;), servlets, DLLs, and so on), data stores, and complex
+ connectors, such as queues. Interaction between elements varies, based on technology. This view is useful for
+ thinking about run-time system quality attributes, such as performance and reliability. This view is optional
+ when using the 4+1 Views.
+ </p>
+ </li>
+ <li>
+ <p>
+ Deployment views: Describe how the system is mapped to the hardware. This view is optional when using the 4+1
+ Views.
+ </p>
+ </li>
+</ul>
+<p>
+ In addition, you may wish to represent the following,
+</p>
+<ul>
+ <li>
+ <p>
+ Data view: A specialization of the logical view. Use this view if persistence is a significant aspect of the
+ system, and the translation from the design model to the data model is not done automatically by the
+ persistence mechanism.
+ </p>
+ </li>
+</ul>
+<p>
+ <br />
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/concepts/resources/4plus1_2.jpg b/praclib/temp/obsoleted_from_openup/guidances/concepts/resources/4plus1_2.jpg
new file mode 100644
index 0000000..24cfc97
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/concepts/resources/4plus1_2.jpg
Binary files differ
diff --git a/praclib/temp/obsoleted_from_openup/guidances/concepts/types_of_developer_tests.xmi b/praclib/temp/obsoleted_from_openup/guidances/concepts/types_of_developer_tests.xmi
new file mode 100644
index 0000000..a6d1a33
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/concepts/types_of_developer_tests.xmi
@@ -0,0 +1,256 @@
+<?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="-VGT8iHGtQSiOUGitq1qmow"
+ name=",_eRutgC5QEduVhuZHT5jKZQ" guid="-VGT8iHGtQSiOUGitq1qmow" changeDate="2006-12-28T13:50:35.593-0500"
+ version="1.0.0">
+ <mainDescription><p>
+ This guideline describes a number of types of tests. To perform these types of testing you need to define, and then
+ run, a series of tests against the source code. A developer test is a single test that needs to be performed.
+</p>
+<p>
+ It is valuable&nbsp;to augment automated tests with human readable test scripts in order to implement developer test
+ cases, scripts that include the information discussed below. A test script is the actual steps, sometimes either
+ written procedures to follow or the source code of a test. Developer test scripts are run against testing targets:
+ either one unit of source code, a more complex portion of your system (such as a component), or the entire system
+ itself to test&nbsp;some developer issue such as integration.
+</p>
+<h3>
+ Regression Testing
+</h3>
+<p>
+ Regression testing is the act of ensuring that changes to&nbsp;the code have not adversely affected existing
+ functionality. It is important to recognize that incremental development makes regression testing critical. Whenever
+ you release an application, you must ensure its previous functionality still works, and because you release
+ applications more often when taking the incremental approach, this means regression testing becomes that much more
+ important. Regression testing is the first thing you should be thinking about when testing for the following reasons:
+</p>
+<ol>
+ <li>
+ You want to be able to modify code and know that you can rerun your tests to see if you broke anything.
+ </li>
+ <li>
+ Existing users get very angry when things that previously worked don’t work anymore.
+ </li>
+</ol>
+<p>
+ Regression testing is fairly straightforward conceptually – you just need to run all of the previous test cases against
+ the new version of the code. Regression testing tools help immensely because they are designed with regression testing
+ in mind. However, there are potential challenges to regression testing:
+</p>
+<ul>
+ <li>
+ When you change your production, either to enhance it or to refactor it, you will need to rework existing test
+ cases coupled to that code.
+ </li>
+ <li>
+ If your updates affect only a component of the system, then potentially you only need to run the test cases that
+ affect this single component. Although this approach is a little risky because your changes may have had a greater
+ impact than you suspect, it does help to reduce both the time and cost of regression testing.
+ </li>
+ <li>
+ The more non-code artifacts that you decide to keep, the greater the effort to regression test your work and
+ therefore the greater the risk to your project because you are more likely to skimp on your testing efforts.
+ </li>
+</ul>
+<p>
+ Regression testing is critical to success as an agile developer. Many software developers use the xUnit family of open
+ source tools, such as <a href="http://www.junit.org/" target="_blank" >JUnit</a> and <a href="http://www.vbunit.org/" target="_blank" >VBUnit</a>, to test their code. The advantage of these tools is that they implement a testing framework
+ with which you can regression test all of your source code. Commercial testing tools are also viable options.
+</p>
+<h3>
+ Traditional Code Testing Techniques
+</h3>
+<p>
+ Although object and procedural technologies are different, several important testing concepts from the procedural world
+ are valid regardless of the underlying technology. These traditional testing techniques are:
+</p>
+<ul>
+ <li>
+ Black-box testing
+ </li>
+ <li>
+ Clear-box testing
+ </li>
+ <li>
+ Boundary-value testing
+ </li>
+ <li>
+ Coverage/Path testing
+ </li>
+</ul>
+<h4>
+ Black-Box Testing
+</h4>
+<p>
+ Black-box testing, also called interface testing, is a technique in which you create test cases based only on the
+ expected functionality of a method, class, or application without any knowledge of its internal workings. One way to
+ define black-box testing is that given input A you should obtain expected results B.
+</p>
+<p>
+ The goal of black-box testing is to ensure the system can do what it should be able to do, but not how it does it. For
+ example, if you invoke differenceInDays(June 30 2006, July 3 2006) the expected result should be three. The creation of
+ black-box tests is often driven by the requirements for&nbsp;the system. The basic idea is&nbsp;to look at the user
+ requirement and ask what needs to be done to show that the user requirement is met.
+</p>
+<p>
+ The primary advantage of black-box testing is that it enables you to prove that your application fulfills the
+ requirements defined for it.&nbsp;&nbsp; The primary disadvantage is that it does not show that the internals
+ of&nbsp;the system work (hence the need for clear-box testing).
+</p>
+<h4>
+ Clear-Box Testing
+</h4>
+<p>
+ Clear-box testing, also called white-box testing, is based on the idea that&nbsp;the program code can drive the
+ development of test cases. The basic concept is you look at&nbsp;the code, and then create test cases that exercise it.
+ For example, assume you have access to the source code for differenceInDays(). When you look at it, you see an IF
+ statement determines whether the two dates are in the same year. If they are in the same year then&nbsp;a simple
+ strategy based on Julian dates is used; if not then a more complex&nbsp;strategy is used. This indicates that you need
+ at least one test that uses dates from the same year and one from different years. By looking at the code, you are able
+ to determine new test cases to exercise the different logic paths within it.
+</p>
+<p>
+ The primary advantage of this concept is that it motivates you to create tests that exercise specific lines of
+ code.&nbsp; The disadvantages are that it does not ensure that your code fulfils the actual requirements (hence the
+ need for black-box testing) and that your testing code becomes highly coupled to your application code.
+</p>
+<h4>
+ Boundary-Value Testing
+</h4>
+<p>
+ This is based on the knowledge that you need to test your code to ensure it can handle unusual and extreme situations.
+ For example, boundary-value test cases differenceInDays() would include passing it the same date, two wildly different
+ dates, one date on the last day of the year and the second on the first day of the following year, and one date on
+ February 29th of a leap year. The basic idea is you want to look for limits defined either by your business rules or by
+ common sense, and then create test cases to test attribute values in and around those values.
+</p>
+<p>
+ The primary advantage of boundary value testing is that it motivates you to confirm that your program code is able to
+ handle “unusual” or “extreme” cases.
+</p>
+<h4>
+ Coverage and Path Testing
+</h4>
+<p>
+ Two critical “traditional” concepts are coverage and path testing. Coverage testing is a technique in which you create
+ a series of test cases designed to test all the code paths in your code. In many ways, coverage testing is simply a
+ collection of clear-box test cases that together exercise every line of code in your application at least once. Path
+ testing is a superset of coverage testing that ensures not only have all lines of code been tested, but all paths of
+ logic have also been tested. The main difference occurs when you have a method with more than one set of case
+ statements or nested IF statements: to determine the number of test cases with coverage testing you would count the
+ maximum number of paths between the sets of case/nested IF statements and, with path testing, you would multiply the
+ number of logic paths.
+</p>
+<h4>
+ Unit and Integration Testing
+</h4>
+<p>
+ Unit testing is the testing of an item, such as an operation, in isolation. For example, the tests defined so far for
+ differenceInDays() are all unit tests. Integration testing, on the other hand, is the testing of a collection of items
+ to validate that they work together. In the case of the data library/class, do the various functions work together?
+ Perhaps the differenceInDays() function has a side effect that causes the dayOfWeek() function to fail if
+ differenceInDays() is called first. Integration testing looks for problems like this.
+</p>
+<h3>
+ Object-Oriented Testing Techniques
+</h3>
+<p>
+ When testing systems built using object technology it is important to understand that your source code is composed of
+ several constructs, including methods (operations), classes, and inheritance. Therefore you need testing techniques
+ that reflect the fact that you have these constructs. These techniques are:
+</p>
+<ul>
+ <li>
+ Method testing
+ </li>
+ <li>
+ Class testing
+ </li>
+ <li>
+ Class-integration testing
+ </li>
+ <li>
+ Inheritance-regression testing
+ </li>
+</ul>
+<h4>
+ Method Testing
+</h4>
+<p>
+ Method testing is the act of ensuring that your methods (operations) perform as defined. In procedural testing this
+ would have been called function/procedure testing. Issues to address via method testing include:
+</p>
+<ul>
+ <li>
+ Ensure that your getter/setter methods work as intended
+ </li>
+ <li>
+ Ensure that each method returns the proper values, including error messages and exceptions
+ </li>
+ <li>
+ Validate the parameters being passed to a method
+ </li>
+ <li>
+ Ensure that a method does what it should
+ </li>
+</ul>
+<p>
+ The advantage of method testing is that it ensures that methods work well in isolation but it does not help to find
+ unintended side effects.
+</p>
+<h4>
+ Class Testing
+</h4>
+<p>
+ The main purpose of class testing is to test classes in isolation, and it is effectively the combination of traditional
+ unit testing and integration testing. It is unit testing because you are testing the class and its instances as single
+ units in isolation, but it is also integration testing because you need to verify the methods and attributes of the
+ class work together. The one assumption you need to make while writing “class tests” is that all other classes in the
+ system work. Issues to address via class testing include:
+</p>
+<ul>
+ <li>
+ Validate that the attributes of an object are initialized properly
+ </li>
+ <li>
+ Validate the invariants of the class
+ </li>
+</ul>
+<p>
+ The primary advantages of class testing are that it validates that the operations and properties of a class work
+ together and that the class works in isolation. However, it does not guarantee that a class works well with the rest of
+ your system.
+</p>
+<h4>
+ Class-integration Testing
+</h4>
+<p>
+ Also known as component testing, this technique addresses the issue of whether the classes in your system, or a
+ component of your system, work together properly. The relationships between classes can be used to drive the
+ development of class integration test cases. Issues to address via class-integration testing include:
+</p>
+<ul>
+ <li>
+ Validate that objects do what other objects expect of them
+ </li>
+ <li>
+ Validate that return values are acted appropriately
+ </li>
+ <li>
+ Validate that exceptions/errors are processed appropriately
+ </li>
+</ul>
+<p>
+ The technique helps to validate that the various classes within a component, or a system, work together. However, it
+ can be difficult to define and develop the test cases to fully perform this level of testing.
+</p>
+<h4>
+ Inheritance-regression Testing
+</h4>This is the act of running of test cases defined for the superclasses on the instances of a subclass because errors
+have not been introduced by that new subclass. New methods are added and existing methods may be redefined by subclasses,
+methods which access and potentially change the value of the attributes defined in the superclass. It is possible that a
+subclass may change the value of the attributes in a way that was never intended in the superclass, or at least was never
+expected. The point is that you need to invoke the test suite of the superclass(es) when testing a subclass. <br /></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/guidelines/describing_arch_mechanisms.xmi b/praclib/temp/obsoleted_from_openup/guidances/guidelines/describing_arch_mechanisms.xmi
new file mode 100644
index 0000000..4ce7bf4
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/guidelines/describing_arch_mechanisms.xmi
@@ -0,0 +1,7 @@
+<?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="-bP4wJKW0CrR9pL0yz20r3Q"
+ name="xxxDELETE_describing_arch_mechanisms,_J6BKgNvIEduv2KOT-Teh6w" guid="-bP4wJKW0CrR9pL0yz20r3Q"
+ changeDate="2008-02-13T15:09:43.093-0500" version="7.2.0"/>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/guidelines/design.xmi b/praclib/temp/obsoleted_from_openup/guidances/guidelines/design.xmi
new file mode 100644
index 0000000..c8f5de4
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/guidelines/design.xmi
@@ -0,0 +1,234 @@
+<?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: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="_Qo7pYMM3EdmSIPI87WLu3g"
+ name="design,_0X3bcMlgEdmt3adZL5Dmdw" guid="_Qo7pYMM3EdmSIPI87WLu3g" changeDate="2006-09-09T09:28:07.410-0400"
+ version="7.2.0">
+ <mainDescription><p>
+ The design represents the behavior and structure of the system at various levels of abstraction – most notably not
+ solely at the code level of abstraction.&nbsp; This will help the designer reason&nbsp;about the quality, structure,
+ and behavior&nbsp;of the design.
+</p>
+<h3>
+ Multiple Passes
+</h3>
+<p>
+ The design will be revisited many times throughout the iterative lifecycle and even within an iteration.&nbsp;
+</p>
+<p>
+ Each time some design activity is being performed, it will be performed with some specific goal.&nbsp; The goal might
+ be to identify a notional set of participants in a collaboration that can be exercised to realize the behavior required
+ (an analysis pass).&nbsp; The goal might be in the identification of some coarse-grained elements that are required to
+ act out some scenario (an architectural pass).&nbsp; Then a pass might be done within one of those components to
+ identify the elements within that will collaborate together to perform the behavior required (a more detailed design
+ pass).
+</p>
+<p>
+ Design might be performed in a particular context such as database context, user-interface context, or perhaps the
+ context of how some existing library will be applied.&nbsp; In these cases the design steps will be performed just to
+ make and communicate decisions regarding that context.
+</p>
+<p>
+ Avoid analysis paralysis.&nbsp; Avoid refining, extending, and improving the design beyond a minimal version that
+ suffices to cover the needs of the requirements within the architecture.&nbsp; Design should be done in small chunks,
+ proven via implementation, improved via refactoring, and integrated into the baseline to provide value to the
+ stakeholders.
+</p>
+<h3>
+ Identification of&nbsp;Elements
+</h3>
+<p>
+ Identify the&nbsp;elements based on needs of the requirements.
+</p>
+<p>
+ The identification of elements can stem from a static perspective of walking through the requirements and identifying
+ elements clearly called out, a form of domain modeling.&nbsp; It can pull in other elements identified as being in the
+ application domain or deemed necessary from examining the requirements for the portion of the system being
+ designed.&nbsp; This can also pull from key abstractions identified while defining the architecture.
+</p>
+<p>
+ The identification of&nbsp;elements&nbsp;should&nbsp;apply a dynamic perspective&nbsp;by&nbsp;walking through scenarios
+ of usage of the system (or subsystem) identifying elements needed to support&nbsp;the behavior.&nbsp; That behavior
+ might be a scenario of usage from an external user perspective or, while designing a subsystem, a responsibility
+ assigned to the subsystem that has complex algorithmic behavior. Consider applying the <a class="elementLink"
+ href="./../../../migrated_from_openup10/guidances/guidelines/entity_control_boundary_pattern_C4047897.html"
+ guid="_uF-QYEAhEdq_UJTvM1DM2Q">Entity-Control-Boundary Pattern</a>&nbsp;to identify the elements necessary to support
+ the scenario or apply other patterns identified in the architecture that specify the elements that will be used to
+ support specific aspects of the scenario.
+</p>
+<p>
+ If the system being designed is a real-time system, include elements representing events and signals that allow us to
+ describe the asynchronous triggers of behavior to which the system must respond.&nbsp; Events are specifications of
+ interesting occurrences in time and space that usually (if they are noteworthy) require some response from the
+ system.&nbsp; Signals represent asynchronous mechanisms used to communicate certain types of events within the system.
+</p>
+<p>
+ If there are existing&nbsp;elements from previous passes over the design or from selected frameworks or other reusable
+ elements, those should be reused whenever possible.
+</p>
+<p>
+ Having identified the elements, each should be given a meaningful name.&nbsp; Each element should also have a
+ description so that the team members that work together to refine the design and implement from&nbsp;the
+ design&nbsp;will understand the role the&nbsp;element will play.
+</p>
+<p>
+ Based on the above, this identification of&nbsp;elements&nbsp;could be applied a number of times in designing just one
+ part of the system.&nbsp; While there is no&nbsp;one correct&nbsp;strategy for multiple passes, they could be done at a
+ coarse-grained level and then a fine-grained level or at an analysis (abstract) level and then a design level.
+</p>
+<h3>
+ Behavior&nbsp;of&nbsp;Elements
+</h3>
+<p>
+ To&nbsp;identify the behavior&nbsp;of the elements, walk through scenarios assigning behavior to the appropriate
+ collaborating participant.&nbsp; If a particular usage of the system or subsystem can have&nbsp;multiple possible
+ outcomes or variant sequences, cover enough scenarios to ensure that the design is robust enough to support the
+ necessary possibilities.
+</p>
+<p>
+ When assigning behavior to elements, consider applying the <a class="elementLink"
+ href="./../../../migrated_from_openup10/guidances/guidelines/entity_control_boundary_pattern_C4047897.html"
+ guid="_uF-QYEAhEdq_UJTvM1DM2Q">Entity-Control-Boundary Pattern</a>&nbsp;or other patterns identified in the
+ architecture.
+</p>
+<p>
+ Behavior can be&nbsp;represented as&nbsp;a simple statement of responsibility or it can be a detailed operation
+ specification.&nbsp; Use the appropriate level of detail to communicate important design decisions while&nbsp;giving
+ the freedom to make appropriate implementation decisions as those tasks ensue.
+</p>
+<p>
+ Behavior must be understood as a responsibility on an element, and as an interaction between two&nbsp;elements in the
+ context of some broader behavior of the system or subsystem.&nbsp; The latter part of this will lead the developer to
+ identify relationships needed between the elements.
+</p>
+<p>
+ Avoid too much&nbsp;identification of behavior solely from the perspective of domain modeling.&nbsp; Only include
+ behavior that is really needed, behavior identified by walking through required scenarios of system usage.
+</p>
+<h3>
+ Design&nbsp;Element Relationships
+</h3>
+<p>
+ The relationships between the&nbsp;elements necessary for the behavior must be designed.&nbsp; This can simply be the
+ identification of&nbsp;the ability&nbsp;to traverse from one&nbsp;element to another or a need to manage an association
+ between the elements.
+</p>
+<p>
+ More detailed design can be performed on the relationships as appropriate.&nbsp; This can include optionality,
+ multiplicity, whether the relationship is a simple dependency or managed association, etc. These decisions that drive
+ implementation details are best made at the design level when it is&nbsp;easier to see how all the pieces fit
+ together.&nbsp;
+</p>
+<p>
+ As with the behavior discussion above, avoid defining too many relationships based on relationships in the application
+ domain.&nbsp; Only include the relationships that are really needed based on the requirements.&nbsp; On the other hand,
+ a combination of requirements knowledge and domain knowledge can lead to some detailed decisions on the relationships
+ such as optionality and multiplicity.
+</p>
+<h3>
+ Refine Design
+</h3>
+<p>
+ Having identified a design&nbsp;including a set of collaborating&nbsp;elements with the behavior and relationships
+ robust enough to handle the requirements under consideration, the design can be improved and transformed into an
+ implementable system through refinement.
+</p>
+<p>
+ The visibility of each operation should be selected to be as&nbsp;restrictive as possible.&nbsp; Based on walking
+ through the scenario it should be clear which operations must be&nbsp;available to other elements in the design and
+ which can be considered private behavior inside the element that has the operation.&nbsp; Minimizing the number of
+ public operations creates a more maintainable and understandable design.
+</p>
+<p>
+ With respect to parameters, the return value, and&nbsp;a description of how it will go about performing the behavior,
+ operations can be detailed at a lower level that drives the actual implementation or that detail might be left to
+ be&nbsp;handled when writing the code.
+</p>
+<p>
+ Data attributes can be identified based on information needed to support behavior or based on additional requirements
+ such as information to be presented to the user or transmitted to another system.&nbsp; Avoid indiscriminate domain
+ analysis; there might be a great deal of data in the domain that is not needed to support the requirements.&nbsp; Data
+ attributes can simply be identified or they can be designed in detail with attribute types, initial values, and
+ constraints. Decide on the visibility of the data attribute; operations to access and update the data can be added or
+ deferred to implementation.
+</p>
+<p>
+ Generalization&nbsp;and interfaces can be applied to simplify or otherwise improve the design.&nbsp; Ensure that the
+ usage of these techniques actually improves the design rather than muddling it with complexity.&nbsp; For example,
+ common behavior can be factored into a parent class via generalization or out to a helper class via delegation; the
+ latter solution can be more understandable and maintainable as generalization is an inflexible relationship.
+</p>
+<p>
+ The refinement of any portion of the design could include another pass through the design process.&nbsp; One might find
+ that what was initially identified as a single behavior on an&nbsp;element&nbsp;warrants a detailed walkthrough of the
+ collaborating&nbsp;elements to realize that behavior.
+</p>
+<p>
+ When updating an existing design <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: Batang; mso-bidi-font-family: Arial; mso-ansi-language: EN-US; mso-fareast-language: KO; mso-bidi-language: AR-SA">–</span>
+ especially one that has had portions already implemented <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: Batang; mso-bidi-font-family: Arial; mso-ansi-language: EN-US; mso-fareast-language: KO; mso-bidi-language: AR-SA">–</span>
+ apply <a class="elementLink" href="./../../../core.tech.slot.base/guidances/concepts/refactoring_1B63BA3B.html"
+ guid="_Poc7IPDzEdqYgerqi84oCA">Refactoring</a> to ensure that the improved design continues to perform as expected.
+</p>
+<h4>
+ Organization of&nbsp;Elements (package-level)
+</h4>
+<p>
+ In a design of any notable size, the&nbsp;elements must be organized into packages.&nbsp; Assign the&nbsp;elements to
+ existing or new packages and ensure that the visibility relationships between the packages support
+ the&nbsp;navigability required between the elements.&nbsp; Decide whether each element should be visible to elements
+ outside its package.
+</p>
+<p>
+ When structuring the design into packages, consider <a class="elementLink"
+ href="./../../../practice.tech.evolutionary_arch.base/guidances/guidelines/layering_F169CF07.html"
+ guid="_0gpkAMlgEdmt3adZL5Dmdw">Layering</a>&nbsp;and other patterns.&nbsp; Though all design work must conform to
+ existing architectural decisions, the allocation of&nbsp;elements to packages and possible updates to package
+ visibility is an area of&nbsp;significant architectural concern.&nbsp; The developer should collaborate with the
+ architect to ensure that package-level decisions are in accordance with the rest of the architecture.
+</p>
+<p>
+ This guideline first talks about the identification and design of the&nbsp;elements and then about organizing
+ the&nbsp;elements into packages.&nbsp; This is not a strict order of events.&nbsp; There is nothing wrong with
+ identifying a package structure for the system and then populating that structure with identified&nbsp;elements&nbsp;as
+ long as the actual&nbsp;elements identified are allowed to influence the resulting package structure.
+</p>
+<h3>
+ Reviewing the Design
+</h3>
+<p>
+ Design is best done collaboratively as it is a problem-solving activity with a range parts and perspectives.&nbsp;
+ There should be a constant level of review to ensure that the decisions make sense within the area being designed and
+ in the design of the system overall.&nbsp; There also might be occasions where the review of some area of design is
+ reviewed by a set of interested or knowledgeable parties such as the architect who will verify that the design conforms
+ to some architectural decision or a developer&nbsp;who will be expected to implement the design.&nbsp;
+</p>
+<p>
+ The design should be examined to ensure that it follows heuristics of quality design such as loose coupling and high
+ cohesion.&nbsp; Responsibilities should be appropriately&nbsp;distributed to elements such that there are no elements
+ with too much responsibility and no elements are left without any responsibilities.&nbsp; The design should be able to
+ clearly&nbsp;communicate the design decisions while not delving into concerns best dealt with during implementation of
+ code.
+</p>
+<p>
+ Ensure the design follows any project-specific guidelines and conforms to the architecture.
+</p>
+<p>
+ Modifications to the design to improve it based on issues identified in reviewing it should apply <a
+ class="elementLink" href="./../../../core.tech.slot.base/guidances/concepts/refactoring_1B63BA3B.html"
+ guid="_Poc7IPDzEdqYgerqi84oCA">Refactoring</a> to ensure that the design and any existing implementation of the design
+ continues to fulfill its responsibilities.
+</p>
+<h3>
+ Relationship of Design to Architecture
+</h3>
+<p>
+ This guideline remarks on conforming to the architecture in various ways; it is written as though one is designing
+ within a pre-existing architecture.&nbsp; Though projects will often have pre-existing architectures available, a
+ particular architecture is the result of design activities.&nbsp; Therefore, in addition to discussing conformance to
+ some existing architecture, one must also consider the creation of the architecture and updates and improvements to the
+ architecture based on the work of design.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/guidelines/determining_arch_significant_rqmts.xmi b/praclib/temp/obsoleted_from_openup/guidances/guidelines/determining_arch_significant_rqmts.xmi
new file mode 100644
index 0000000..ee3ee6b
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/guidelines/determining_arch_significant_rqmts.xmi
@@ -0,0 +1,7 @@
+<?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="-EUXQjT8DebSClO4YjNuoHw"
+ name="xxxDELETE_determining_arch_significant_rqmts,_D3JXMNvKEduv2KOT-Teh6w" guid="-EUXQjT8DebSClO4YjNuoHw"
+ changeDate="2008-02-13T12:14:51.859-0500" version="7.2.0"/>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/guidelines/openup_architecture.xmi b/praclib/temp/obsoleted_from_openup/guidances/guidelines/openup_architecture.xmi
new file mode 100644
index 0000000..2e158e5
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/guidelines/openup_architecture.xmi
@@ -0,0 +1,17 @@
+<?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: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="-clUV9n59dDwg0e1VCcsB8Q"
+ name=",_REqtUMEvEduwZvIr61GnNg" guid="-clUV9n59dDwg0e1VCcsB8Q" changeDate="2007-02-20T14:13:25.950-0800">
+ <mainDescription><p>
+ Describe how Elaboration deals with architecture (link to existing content).
+</p>
+<p>
+ The architecture artifacts are the work products that provide the most benefit in development in terms of understanding
+ and extending the system.
+</p>
+<p>
+ Explain how architecture reduces technical risk and the importance of doing so.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/guidelines/openup_iterations.xmi b/praclib/temp/obsoleted_from_openup/guidances/guidelines/openup_iterations.xmi
new file mode 100644
index 0000000..0910702
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/guidelines/openup_iterations.xmi
@@ -0,0 +1,10 @@
+<?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: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="-Mobjz86dw07NW5-IhtEoNA"
+ name=",_U3VjIMEuEduwZvIr61GnNg" guid="-Mobjz86dw07NW5-IhtEoNA" changeDate="2007-02-20T14:09:51.021-0800">
+ <mainDescription>Describe the&nbsp;milestone of each phase (link to existing content). Explain that iterations are not homogeneous, but they
+all deliver stakeholder value. explain that that the focus on reducing risk and understanding the architecture in I &amp; E
+make C &amp; T more predictable.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/guidelines/openup_risk.xmi b/praclib/temp/obsoleted_from_openup/guidances/guidelines/openup_risk.xmi
new file mode 100644
index 0000000..c035022
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/guidelines/openup_risk.xmi
@@ -0,0 +1,18 @@
+<?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: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="-_BjYXvrfe1HHL5Y_QBfh4Q"
+ name=",_G08UgMEwEduwZvIr61GnNg" guid="-_BjYXvrfe1HHL5Y_QBfh4Q" changeDate="2007-02-20T14:22:16.653-0800">
+ <mainDescription><p>
+ Define risk (reference existing content).
+</p>
+<p>
+ Explain how addressing risk in early iterations reduces the uncertainty and unpredictabiliy in future iterations.
+ Describe the effect that identifying, tracking, and mitigating risk has on a project (better decisions, high comfort
+ level, more visibility into problems).
+</p>
+<p>
+ Reference definitions for risk and risk mitigation.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/guidelines/outlining_the_arch.xmi b/praclib/temp/obsoleted_from_openup/guidances/guidelines/outlining_the_arch.xmi
new file mode 100644
index 0000000..6c11f36
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/guidelines/outlining_the_arch.xmi
@@ -0,0 +1,7 @@
+<?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="-YeVRerdEixh4HgHOuw2KRQ"
+ name="analyze_arch_reqs,_42UD4A3tEduibvKwrGxWxA" guid="-YeVRerdEixh4HgHOuw2KRQ"
+ changeDate="2008-02-13T13:23:35.468-0500" version="1.0.0"/>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/guidelines/outlining_the_architecture.vm.xmi b/praclib/temp/obsoleted_from_openup/guidances/guidelines/outlining_the_architecture.vm.xmi
new file mode 100644
index 0000000..3e1a479
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/guidelines/outlining_the_architecture.vm.xmi
@@ -0,0 +1,14 @@
+<?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="-I-2SvZtjELUYDQO0jvdxEA"
+ name="new_guideline,_SYDjUMUKEdu5GrwIlTJV7g" guid="-I-2SvZtjELUYDQO0jvdxEA" changeDate="2008-02-09T11:51:10.671-0500"
+ version="7.2.0">
+ <mainDescription><p>
+ At this stage, you may find it useful to develop a draft version of your architectural models.&nbsp; For more
+ information, see <a class="elementLinkWithType"
+ href="./../../../practice.tech.evolutionary_arch.base/guidances/guidelines/architectural_models_8BE6E55B.html"
+ guid="_HrgUQNcuEdy1nJEYZGzN4A">Guideline: Architectural Models</a>.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/guidelines/physical_data_modeling.xmi b/praclib/temp/obsoleted_from_openup/guidances/guidelines/physical_data_modeling.xmi
new file mode 100644
index 0000000..86bc304
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/guidelines/physical_data_modeling.xmi
@@ -0,0 +1,177 @@
+<?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: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="-XMbxFU8M85cRlf3C4iwAGw"
+ name="new_guideline,_ienXEEyAEdu-df7p0PuRvQ" guid="-XMbxFU8M85cRlf3C4iwAGw" authors="Scott Ambler"
+ changeDate="2006-12-01T13:53:01.285-0800" version="1.0.0">
+ <mainDescription><h3>
+ Overview
+</h3>Physical data models (PDMs) are used to design the structure of a persistent data store. Typically a PDM is created
+for a single data store, although sometimes a PDM will cover several related data stores (this is particularly true when
+the data storage mechanism is file based). The assumption in this guideline is that you are modeling the schema of a single
+relational database. 
+<h3>
+ The Data Model in OpenUP
+</h3>The PDM is part of the Work Product: Design. It’s described as different views or perspectives of a portion of the
+design. 
+<h3>
+ Data Model Types
+</h3>
+<p dir="ltr" style="MARGIN-RIGHT: 0px">
+ Traditionally, there are three types of data models:
+</p>
+<ol>
+ <li>
+ <div style="MARGIN-RIGHT: 0px">
+ Conceptual. A conceptual model, also referred to as a domain model, depicts the critical business entities and
+ the relationships between them.
+ </div>
+ </li>
+ <li>
+ <div style="MARGIN-RIGHT: 0px">
+ Logical. A logical data model (LDM) adds detail, in particular data attributes and more entities. LDMs will
+ optionally indicate candidate keys (one or more attributes of an entity which uniquely identify it) of an
+ entity. LDMs describe how the design of the system handles the data that will be actually maintained in the
+ PDM.
+ </div>
+ </li>
+ <li>
+ <div style="MARGIN-RIGHT: 0px">
+ <p>
+ Physical. A PDM depicts the table structure (in the case of a relational database design), the
+ relationships between the tables, and the primary and foreign keys implemented by the tables. PDMs
+ potentially indicate views, stored procedures, and other database elements.
+ </p>
+ </div>
+ </li>
+</ol>
+<p>
+ For systems built using object and/or component-based technology, the LDM is usually not created in favor of a class
+ model.
+</p>
+<h4 style="MARGIN-RIGHT: 0px">
+ Physical Data Modeling
+</h4>
+<p>
+ The PDM consists of the detailed database table designs and their relationships. The tables in the PDM have
+ well-defined columns, as well as keys and indexes as needed. The tables might also have triggers defined as necessary
+ to support the database functionality and referential integrity of the system. In addition to the tables, stored
+ procedures have been created, documented, and associated with the database in which the stored procedure will reside.
+</p>
+<p>
+ The diagram below shows an example of some of the elements of a PDM. A UML-based notation is used, although other
+ notations such as “crow's feet” or Information Engineering (IE) are also common. This example model is a part of the
+ PDM of a fictional order entry system. It depicts three tables (Order, OrderItem, and Item), three stored procedures
+ (GetOrders, GetTotalBusiness, and TestDatabase), and a trigger on Order named deleteOrderItems. The figure also depicts
+ the columns of each table, the primary key for each table, and any foreign keys to other tables.
+</p>
+<p>
+ <strong>Example Physical Data Model</strong>
+</p>
+<p>
+ &nbsp;<img height="309" alt="" src="./resources/PDMSample.JPG" width="597" />
+</p>
+<p>
+ An existing database can be reverse-engineered to populate the PDM if the team has access to a tool that can transform
+ a database into a model.
+</p>
+<h3>
+ How to Model Database Schemas
+</h3>
+<p>
+ Perform the following in an iterative manner:
+</p>
+<ol>
+ <li>
+ Identify tables. A table is similar conceptually to object-orientation’s concept of a class – a table contains a
+ collection of rows of data whereas a class defines a collection of objects. A table could contain rows representing
+ people, places, things, events, or concepts. Examples of tables include Customer, Order, and OrderItem.
+ </li>
+ <li>
+ Identify columns. Each table has one or more columns. A column stores a single data attribute for each row. For
+ example, the Customer table may have columns such as First Name and Surname. A column has a single data type, such
+ as INT, DATETIME, or VARCHAR.
+ </li>
+ <li>
+ Follow accepted modeling conventions. Your organization should have standards and guidelines applicable to data
+ modeling, in particular naming conventions,&nbsp;that you should follow.
+ </li>
+ <li>
+ Identify relationships between tables. In the real world entities have relationships with other entities. For
+ example, customers PLACE orders, customers LIVE AT addresses, and line items ARE PART OF orders. These
+ relationships will exist between the rows of data stored in the corresponding tables.
+ </li>
+ <li>
+ Assign keys. A key is one or more columns that uniquely identify a row in a table. A primary key is the preferred
+ key for a table. For example, the Customer table may have two potential keys, CustomerID and SocialSecurityNumber.
+ You could choose to use CustomerID as the primary key, thereby making SocialSecurityNumber a secondary key. Foreign
+ keys are used to maintain relationships between rows.
+ </li>
+ <li>
+ Normalize to reduce data redundancy. Data normalization is a process in which columns within a PDM are organized to
+ increase the cohesion of tables. In other words, the goal of data normalization is to reduce and even eliminate
+ data redundancy, an important consideration for application developers because it is incredibly difficult to store
+ objects in a relational database that maintains the same information in several places.
+ </li>
+ <li>
+ De-normalize to improve performance. Normalized data schemas, when put into production, often suffer from
+ performance problems. An important part of data modeling is to de-normalize portions of&nbsp;the data schema, to
+ increase data redundancy by storing the same information in several places or manners, to improve database access
+ times.
+ </li>
+</ol>
+<h3>
+ Data Modeling Throughout the Lifecycle
+</h3>
+<h4>
+ Inception Phase
+</h4>
+<p>
+ During the Inception phase the goal is to identify high-level requirements for the system so that the scope may be
+ identified and project funding obtained. Little, if any, data modeling is performed at this point although some
+ conceptual modeling may occur. Detailed data models are usually not needed at this point.
+</p>
+<h4>
+ Elaboration Phase
+</h4>
+<p>
+ The goal of the Elaboration phase is to eliminate technical risk and to produce a stable (baselined) architecture for
+ the system. One of several architectural issues that is likely to arise is data architecture. To support this effort,
+ you will need to model the major database structures (tables, indexes, and primary and foreign key columns) and then
+ create the database schema from the model (ideally it would be generated from a modeling tool).
+</p>
+<p>
+ Additionally, representative data volumes may be loaded into the database to support performance testing. Based on the
+ results of performance testing, the PDM might need to be adjusted with optimization techniques, including but not
+ limited to de-normalizing, optimizing physical storage attributes, or distribution and indexing.
+</p>
+<h4>
+ Construction Phase
+</h4>
+<p>
+ During the Construction phase the goal is to build a working system that is ready to be released. During each
+ iteration&nbsp;the&nbsp;design, implementation, and tests are fleshed out to implement that iteration's requirements.
+ In other words development artifacts, including your data-oriented artifacts, evolve over time. To support data model
+ changes you may discover the need to refactor your existing database schema.
+</p>
+<h4>
+ Transition Phase
+</h4>
+<p>
+ The PDM is maintained during the Transition phase in response to approved change requests. You should keep the PDM
+ synchronized with the database as the application goes through final acceptance test and is deployed into production.
+</p>
+<h3>
+ Round-trip Engineering Considerations
+</h3>
+<p>
+ If a development team is using modern visual modeling tools that have the ability to convert classes to tables (and
+ vice versa) or has the ability to reverse and forward engineer databases, then the team needs to establish guidelines
+ for managing the transformation and engineering processes. The development team must define the points in the
+ development of the application (build-and-release cycle) at which it will be appropriate to perform the class-to-table
+ transformations and to forward-engineer the database. Once the initial database is created, the development team must
+ define guidelines for the team to manage the synchronization of the PDM and database as the design and code of the
+ system evolve throughout the project.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/guidelines/refining_the_architecture.xmi b/praclib/temp/obsoleted_from_openup/guidances/guidelines/refining_the_architecture.xmi
new file mode 100644
index 0000000..d42940a
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/guidelines/refining_the_architecture.xmi
@@ -0,0 +1,7 @@
+<?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="-t7mQSRPYITkMoYRVNz7jQg"
+ name="evolving_the_architecture,_mDf2EBapEduSTJywppIxVQ" guid="-t7mQSRPYITkMoYRVNz7jQg"
+ changeDate="2008-02-13T19:00:13.937-0500" version="1.0.0"/>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/guidelines/resources/compass.gif b/praclib/temp/obsoleted_from_openup/guidances/guidelines/resources/compass.gif
new file mode 100644
index 0000000..39f306a
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/guidelines/resources/compass.gif
Binary files differ
diff --git a/praclib/temp/obsoleted_from_openup/guidances/guidelines/resources/compassL.gif b/praclib/temp/obsoleted_from_openup/guidances/guidelines/resources/compassL.gif
new file mode 100644
index 0000000..4117414
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/guidelines/resources/compassL.gif
Binary files differ
diff --git a/praclib/temp/obsoleted_from_openup/guidances/guidelines/resources/icon_introL.gif b/praclib/temp/obsoleted_from_openup/guidances/guidelines/resources/icon_introL.gif
new file mode 100644
index 0000000..1826cbd
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/guidelines/resources/icon_introL.gif
Binary files differ
diff --git a/praclib/temp/obsoleted_from_openup/guidances/guidelines/resources/mic.gif b/praclib/temp/obsoleted_from_openup/guidances/guidelines/resources/mic.gif
new file mode 100644
index 0000000..0b316db
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/guidelines/resources/mic.gif
Binary files differ
diff --git a/praclib/temp/obsoleted_from_openup/guidances/guidelines/using_patterns.xmi b/praclib/temp/obsoleted_from_openup/guidances/guidelines/using_patterns.xmi
new file mode 100644
index 0000000..952f6ab
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/guidelines/using_patterns.xmi
@@ -0,0 +1,49 @@
+<?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: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="-U-5cLUk-mdaO518lh5CxTQ"
+ name="using_patterns,_0cr7cACrEdu8m4dIntu6jA" guid="-U-5cLUk-mdaO518lh5CxTQ" changeDate="2006-09-21T15:38:16.868-0700"
+ version="1.0.0">
+ <mainDescription><p>
+ In software design, it is primarily the development method and not the pattern and its pattern language that influences
+ the process of pattern selection and use. As discussed in <a class="elementLinkWithType"
+ href="./../../../core.tech.slot.base/guidances/concepts/pattern_10BE6D96.html"
+ guid="_0YJvUMlgEdmt3adZL5Dmdw">Concept: Pattern</a>, Alexander developed the concept of generative pattern languages to
+ guide a designer’s application of individual patterns to the entire design. In software design, however, as Alexander
+ observed [<a class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/references_6CCF393.html"
+ guid="_9ToeIB83Edqsvps02rpOOg">OOP96</a>] there is little evidence of using generative pattern languages.
+</p>
+<p>
+ For iterative development methods, software patterns and pattern languages support the development method through their
+ ability to be applied incrementally, or by piecemeal growth, and by providing extensible structures. From an
+ architectural perspective, these two qualities allow software architecture to be designed and refactored incrementally,
+ thus so avoid the need for a so-called "big, up-front design."
+</p>
+<h4>
+ Piecemeal growth
+</h4>
+<p>
+ The term <strong>piecemeal growth</strong>, as it applies to patterns, originates in Alexander's work. It refers to a
+ top-down design process in which a design starts from a high-level structure that is embellished or refined through the
+ implementation of lower-level patterns. For software development, this corresponds to using hierarchies of
+ architectural and design patterns and idioms like those proposed by Buschmann et. al. [<a
+ class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/references_6CCF393.html"
+ guid="_9ToeIB83Edqsvps02rpOOg">BUS96</a>]. Using the idea of piecemeal growth, an architect can start with one or more
+ architectural patterns to provide an architectural vision for the design, and then progressively extend the design
+ using design patterns. For example, an interactive application may use the Model-View-Controller pattern as its
+ architectural vision, then during implementation the Command pattern may be selected to implement the Controller
+ component.
+</p>
+<h4>
+ Extensibility
+</h4>
+<p>
+ A key aspect of object oriented design patterns is their ability to support extension without causing the rewriting of
+ existing code. This feature allows a bottom up approach to the design process through code refactoring. When a problem
+ is encountered during coding such as duplicate code, the developer can weighed up various patterns and their tradeoffs
+ and select the appropriate solution in the context of the application.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/supportingmaterials/keyword_index.xmi b/praclib/temp/obsoleted_from_openup/guidances/supportingmaterials/keyword_index.xmi
new file mode 100644
index 0000000..27ed53e
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/supportingmaterials/keyword_index.xmi
@@ -0,0 +1,17 @@
+<?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: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="_zZxTYNnmEdmO6L4XMImrsA"
+ name="keyword_index,2.0088322577945588E-305" guid="_zZxTYNnmEdmO6L4XMImrsA" changeDate="2005-06-14T08:32:05.050-0700">
+ <mainDescription><p class="banner" align="left">
+ The keyword index provides the ability to look-up topics in the method website based on keywords or topics. At the time
+ the pages are created, keywords are identified which allows the keyword index to be built. The top frame of the keyword
+ index window allows topics beginning with a letter or number to be displayed. The lower frame displays a list of topics
+ and their related links. Clicking on a link causes the related page to be displayed in the main frame of the published
+ site browser window.
+</p>
+<p class="banner" align="left">
+ <br />
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/supportingmaterials/resources/CorePrinciples_48.gif b/praclib/temp/obsoleted_from_openup/guidances/supportingmaterials/resources/CorePrinciples_48.gif
new file mode 100644
index 0000000..da5215c
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/supportingmaterials/resources/CorePrinciples_48.gif
Binary files differ
diff --git a/praclib/temp/obsoleted_from_openup/guidances/supportingmaterials/resources/Disciplines_48.gif b/praclib/temp/obsoleted_from_openup/guidances/supportingmaterials/resources/Disciplines_48.gif
new file mode 100644
index 0000000..36f36b4
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/supportingmaterials/resources/Disciplines_48.gif
Binary files differ
diff --git a/praclib/temp/obsoleted_from_openup/guidances/supportingmaterials/resources/GetStarted_48.gif b/praclib/temp/obsoleted_from_openup/guidances/supportingmaterials/resources/GetStarted_48.gif
new file mode 100644
index 0000000..5839c94
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/supportingmaterials/resources/GetStarted_48.gif
Binary files differ
diff --git a/praclib/temp/obsoleted_from_openup/guidances/supportingmaterials/resources/LifeCycle_48.gif b/praclib/temp/obsoleted_from_openup/guidances/supportingmaterials/resources/LifeCycle_48.gif
new file mode 100644
index 0000000..f7f4665
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/supportingmaterials/resources/LifeCycle_48.gif
Binary files differ
diff --git a/praclib/temp/obsoleted_from_openup/guidances/supportingmaterials/resources/OpenUp1_350.jpg b/praclib/temp/obsoleted_from_openup/guidances/supportingmaterials/resources/OpenUp1_350.jpg
new file mode 100644
index 0000000..0bb0b38
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/supportingmaterials/resources/OpenUp1_350.jpg
Binary files differ
diff --git a/praclib/temp/obsoleted_from_openup/guidances/supportingmaterials/resources/Roles_48.gif b/praclib/temp/obsoleted_from_openup/guidances/supportingmaterials/resources/Roles_48.gif
new file mode 100644
index 0000000..3fb662d
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/supportingmaterials/resources/Roles_48.gif
Binary files differ
diff --git a/praclib/temp/obsoleted_from_openup/guidances/supportingmaterials/resources/WorkProducts_48.gif b/praclib/temp/obsoleted_from_openup/guidances/supportingmaterials/resources/WorkProducts_48.gif
new file mode 100644
index 0000000..9554964
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/supportingmaterials/resources/WorkProducts_48.gif
Binary files differ
diff --git a/praclib/temp/obsoleted_from_openup/guidances/supportingmaterials/resources/icon_introL.gif b/praclib/temp/obsoleted_from_openup/guidances/supportingmaterials/resources/icon_introL.gif
new file mode 100644
index 0000000..1826cbd
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/supportingmaterials/resources/icon_introL.gif
Binary files differ
diff --git a/praclib/temp/obsoleted_from_openup/guidances/supportingmaterials/resources/mic.gif b/praclib/temp/obsoleted_from_openup/guidances/supportingmaterials/resources/mic.gif
new file mode 100644
index 0000000..0b316db
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/supportingmaterials/resources/mic.gif
Binary files differ
diff --git a/praclib/temp/obsoleted_from_openup/guidances/supportingmaterials/search_engine.xmi b/praclib/temp/obsoleted_from_openup/guidances/supportingmaterials/search_engine.xmi
new file mode 100644
index 0000000..8590829
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/supportingmaterials/search_engine.xmi
@@ -0,0 +1,150 @@
+<?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="_zZxTYtnmEdmO6L4XMImrsA"
+ name="search_engine,3.1789140222665413E-305" guid="_zZxTYtnmEdmO6L4XMImrsA" changeDate="2005-11-09T15:02:32.459-0500"
+ version="7.2.0">
+ <mainDescription><p>
+ <a id="using" name="using"><strong>Note</strong>: The&nbsp;Search Engine, implemented as applets, requires JRE 1.4.2 or
+ higher (you can download a JRE from</a> <a href="http://java.sun.com/j2se"
+ target="_blank" >http://java.sun.com/j2se</a><a id="using" name="using">).</a>
+</p>
+<h3>
+ Tips on Using the Search Engine
+</h3>
+<p>
+ The search engine allows you to search for pages in the&nbsp;published&nbsp;Web site in a number of ways. For example,
+ you can:
+</p>
+<ul>
+ <li>
+ Search for pages that contain <b>all</b> of the words that you have typed.
+ </li>
+ <li>
+ Search for pages that contain <b>any</b> of the words that you have typed.
+ </li>
+ <li>
+ Search for pages that contain the <b>exact phrase</b> that you have typed.
+ </li>
+ <li>
+ Search for pages that contain <b>none of the words</b> that you have typed.
+ </li>
+</ul>
+<p>
+ To enter a search query, type the words to be searched for in your choice of the <b>All the words</b>, <b>Any word</b>,
+ <b>Exact phrase</b>, and <b>Without the words</b> fields, and then press <tt>ENTER</tt> or click the <b>Search Now</b>
+ button. When the search is complete, each matching page will be listed in the <b>Results</b> field, showing the page
+ title and a short summary of the content. Click a title to open the page in your published siteWeb browser window.
+</p>
+<p>
+ For example, to search for pages that contain all of the words "Rational", "Unified", and "Process", and either or both
+ of the words "adopt" and "vision", type the words <tt>Rational Unified Process</tt> in the <b>All the words</b> field,
+ and <tt>adopt vision</tt> in the <b>Any word</b> field.
+</p>
+<p>
+ You can select how many results per page that you want by using the <b>Show</b> list. If the results are more than what
+ you selected to see per page, click the <b>next</b> and <b>previous</b> buttons to page through the results.
+</p>
+<p>
+ You can also indicate whether you want the query to be applied against the published web-site or developerWorks. To
+ choose between the published web-site and developerWorks, click the <b>In section</b> list, and then select the desired
+ section.
+</p>
+<h3>
+ <a id="finding" name="finding">Finding a Word on a Page</a>
+</h3>
+<p>
+ Once a page is displayed by the search engine, use the Web browser's search tool to find a specific word on that page.
+ Press <tt>CTRL+F</tt> to start the Web browser's search tool.
+</p>
+<h3>
+ <a id="entering" name="entering">Entering a Search Query</a>
+</h3>
+<p>
+ A search query consists of one or more specified words. Boolean operators cannot be used. Instead of Boolean operators,
+ use the <b>All the words</b>, <b>Any word</b>, <b>Exact phrase</b>, or <b>Without the word</b> fields that are
+ provided. The search process is not case-sensitive, which means that <font size="3"><tt>Hello, HELLO, and
+ hElLo</tt></font> are all considered the same. The wildcard symbol is not supported: <font size="3"><tt>*</tt></font>.
+</p>
+<p>
+ When more than one field is used, the query is evaluated with precedence from top to bottom. For example, the query:
+</p>
+<div align="center">
+ <table
+ style="BORDER-RIGHT: rgb(128,128,128) 1px solid; BORDER-TOP: rgb(128,128,128) 1px solid; BORDER-LEFT: rgb(128,128,128) 1px solid; BORDER-BOTTOM: rgb(128,128,128) 1px solid"
+ cellspacing="4" bordercolordark="#808080" cellpadding="4" width="350" bordercolorlight="#808080" border="0">
+ <tbody>
+ <tr>
+ <th align="left" width="40%">
+ All the words:
+ </th>
+ <td width="60%">
+ project management
+ </td>
+ </tr>
+ <tr>
+ <th align="left" width="40%">
+ <b>Any word</b>:
+ </th>
+ <td width="60%">
+ adopt vision
+ </td>
+ </tr>
+ <tr>
+ <th align="left" width="40%">
+ <b>Exact phrase</b>:
+ </th>
+ <td width="60%">
+ Rational Unified Process
+ </td>
+ </tr>
+ <tr>
+ <th align="left" width="40%">
+ <b>Without the words</b>:
+ </th>
+ <td width="60%">
+ implementation
+ </td>
+ </tr>
+ </tbody>
+ </table><br />
+ <br />
+</div>
+<p>
+ This can be expressed as the following: (project AND management) AND (adopt OR vision) AND (Rational Unified Process)
+ NOT (implementation). In other words, the matching pages must contain both of the words "project" and "management", the
+ word "adopt" or "vision", along with the phrase "Rational Unified Process". Matching pages must not contain the word
+ "implementation".
+</p>
+<h3>
+ <a id="special_considerations" name="special_considerations">Special Considerations</a>
+</h3>
+<ul>
+ <li>
+ The search engine automatically excludes common words such as "where", "when", and "the" from search queries,
+ because these words are excluded during the creation of the index files on which the search operates. Excluding
+ these words improves performance of the search without impacting the precision of the results.
+ </li>
+ <li>
+ In order for a query using the <b>Without the words</b> field to make sense, there must be text in at least one of
+ the other search fields. In other words, unless you first specify that you want the search to find pages that
+ <b>do</b> contain certain words or a specific phrase, the search engine cannot find pages that <b>do not</b>
+ contain certain words.
+ </li>
+ <li>
+ Wildcard searches using the wildcard character are not supported.
+ </li>
+ <li>
+ Boolean operators are not supported. See the section titled <a href="#entering" >Entering a Search Query</a> for
+ instructions on how to perform searches that are equivalent to using Boolean operators.
+ </li>
+ <li>
+ You may obtain unsatisfactory search results for queries that attempt to search for single digit numbers in their
+ numeric format, especially the numbers 0 though 9. Instead of searching for the numeric value, either omit the
+ number from the search or use the full textual spelling of the number, for example "zero", "six", "nine", "ten" and
+ so forth.
+ </li>
+</ul><br />
+<br /></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/actor.xmi b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/actor.xmi
new file mode 100644
index 0000000..ad5b021
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/actor.xmi
@@ -0,0 +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: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="-4RQJzq_1URTZ5FGCBKnTIw"
+ name="new_term_definition,_ZsK30EvBEdunZcj9T5hrMQ" guid="-4RQJzq_1URTZ5FGCBKnTIw">
+ <mainDescription>Someone or something, outside the system that interacts with the system.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/analyst.xmi b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/analyst.xmi
new file mode 100644
index 0000000..c65efb8
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/analyst.xmi
@@ -0,0 +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: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="-1RwpgmmY974S0YkxEOFDCw"
+ name="new_term_definition,_GEAwAEvCEdunZcj9T5hrMQ" guid="-1RwpgmmY974S0YkxEOFDCw">
+ <mainDescription>Role representing customer and end-user concerns</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/architect.xmi b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/architect.xmi
new file mode 100644
index 0000000..d52bd13
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/architect.xmi
@@ -0,0 +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.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="-2QB1bosN011CudkwZ0cn-g"
+ name="architect,_wI3R4EvCEdunZcj9T5hrMQ" guid="-2QB1bosN011CudkwZ0cn-g">
+ <mainDescription>Role representing someone responsible for designing the software architecture, which includes making the key technical
+decisions that constrain the overall design and implementation of the project</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/business_rule.xmi b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/business_rule.xmi
new file mode 100644
index 0000000..5c3b410
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/business_rule.xmi
@@ -0,0 +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: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="-COrjB4k8Qtf6ZpPEcBNwpw"
+ name=",_NtGL0EvDEdunZcj9T5hrMQ" guid="-COrjB4k8Qtf6ZpPEcBNwpw" version="7.2.0">
+ <mainDescription>A declaration of policy or condition that must be satisfied by the system under consideration.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/content_element.xmi b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/content_element.xmi
new file mode 100644
index 0000000..c7c027b
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/content_element.xmi
@@ -0,0 +1,17 @@
+<?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: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="-We7G-7OM2QspR_i1ErwtLA"
+ name="content_element,_N8x34B_LEdq6CKKKq4D7YA" guid="-We7G-7OM2QspR_i1ErwtLA"
+ changeDate="2006-09-28T13:46:45.015-0700">
+ <mainDescription>Any element modeled in <a class="elementLink"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/uma_73BA0C0C.html"
+guid="_cj6jkB_PEdq6CKKKq4D7YA">UMA</a>&nbsp;that is part of <a class="elementLink"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/method_content_6972AE81.html"
+guid="_Ts2joB_MEdq6CKKKq4D7YA">method content</a>. Content elements providestep-by-step explanations,describing how very
+specific development goals are achieved independent of the placement of these steps within a development lifecycle. They
+are instantiated and adapted to the specific situation within <a class="ELEMENTLINK"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/process_68E308B4.html"
+guid="_yQ5m2NnmEdmO6L4XMImrsA">process</a>&nbsp;structures.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/content_package.xmi b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/content_package.xmi
new file mode 100644
index 0000000..b049f7c
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/content_package.xmi
@@ -0,0 +1,19 @@
+<?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="-t4Xac9J5DWCA6r1b9L40Mw"
+ name=",_SAWgwMaFEduMlb2cQZNTYw" guid="-t4Xac9J5DWCA6r1b9L40Mw" changeDate="2007-02-27T12:10:22.988-0500"
+ version="7.2.0">
+ <mainDescription>A&nbsp;special method package that contains <a class="elementLinkWithUserText"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/content_element_DA3AD029.html"
+guid="_N8x34B_LEdq6CKKKq4D7YA">content elements</a> exclusively. Examples for content element are <a
+class="elementLinkWithUserText" href="./../../../legacy.obsoleted_from_openup/guidances/termdefinitions/artifact_F635D25.html"
+guid="_x7cUM9nmEdmO6L4XMImrsA" >artifacts</a>, <a class="elementLinkWithUserText"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/task_6C1FF051.html"
+guid="_x459ktnmEdmO6L4XMImrsA">tasks</a>, <a class="elementLinkWithUserText"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/role_37A0C602.html"
+guid="_yUefQNnmEdmO6L4XMImrsA">roles</a>, and <a class="elementLinkWithUserText"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/guidance_549AC394.html"
+guid="_83ttAB_NEdq6CKKKq4D7YA">guidance</a>.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/customer.xmi b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/customer.xmi
new file mode 100644
index 0000000..4311ce0
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/customer.xmi
@@ -0,0 +1,12 @@
+<?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: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="_yE05tNnmEdmO6L4XMImrsA"
+ name="customer,_yE05s9nmEdmO6L4XMImrsA" guid="_yE05tNnmEdmO6L4XMImrsA">
+ <mainDescription>A person or organization, internal or external to the producing organization, who takes financial responsibility for the
+system. In a large system this may or may not be the user. The customer is the ultimate recipient of the developed product.
+See also: <i><a class="elementLink"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/stakeholder_4A6A8AED.html"
+guid="_yWHeDNnmEdmO6L4XMImrsA">stakeholder</a>.</i></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/developer.xmi b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/developer.xmi
new file mode 100644
index 0000000..7088e27
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/developer.xmi
@@ -0,0 +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.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="-802sCZ4lJcejyRbhLmkxkw"
+ name=",_-61a8EvOEdunZcj9T5hrMQ" guid="-802sCZ4lJcejyRbhLmkxkw" changeDate="2006-09-24T07:17:35.993-0700">
+ <mainDescription>Role representing someone&nbsp; responsible for developing a part of the system, including designing it to fit into the
+architecture, and then implementing, unit-testing, and integrating the components that are part of the solution.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/document.xmi b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/document.xmi
new file mode 100644
index 0000000..9701194
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/document.xmi
@@ -0,0 +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: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="_yG6kZNnmEdmO6L4XMImrsA"
+ name="document,_yG6kY9nmEdmO6L4XMImrsA" guid="_yG6kZNnmEdmO6L4XMImrsA">
+ <mainDescription>A document is a collection of information intended to be represented on paper, or in a medium using a paper metaphor. The
+paper metaphor includes the concept of pages, and it has either an implicit or explicit sequence of contents. The
+information is in text or two-dimensional pictures. Examples of paper metaphors are word processor documents, spreadsheets,
+schedules, Gantt charts, web-pages,&nbsp;and overhead slide presentations.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/glossary.xmi b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/glossary.xmi
new file mode 100644
index 0000000..bd51f3e
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/glossary.xmi
@@ -0,0 +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.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="-05pn_DGdNui9qqwx46iKZQ"
+ name=",_VhhDMEvrEdunZcj9T5hrMQ" guid="-05pn_DGdNui9qqwx46iKZQ" changeDate="2006-09-24T10:40:24.193-0700">
+ <mainDescription>An artifact in OpenUP that defines the vocabulary and other important terms that are part of a project and the problem
+domain.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/model.xmi b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/model.xmi
new file mode 100644
index 0000000..960316a
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/model.xmi
@@ -0,0 +1,12 @@
+<?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: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="_yNefZNnmEdmO6L4XMImrsA"
+ name="model,_yNefY9nmEdmO6L4XMImrsA" guid="_yNefZNnmEdmO6L4XMImrsA" changeDate="2006-09-28T14:16:05.562-0700">
+ <mainDescription><p>
+ A model is an abstraction of a more complicated thing.
+</p><br />
+<br />
+<br /></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/model_element.xmi b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/model_element.xmi
new file mode 100644
index 0000000..27e4f74
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/model_element.xmi
@@ -0,0 +1,10 @@
+<?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: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="_yNnpVtnmEdmO6L4XMImrsA"
+ name="model_element,_yNnpVdnmEdmO6L4XMImrsA" guid="_yNnpVtnmEdmO6L4XMImrsA" changeDate="2006-04-13T15:20:00.937-0700">
+ <mainDescription>An element that is an abstraction drawn from the system being modeled. Contrast: <i><a class="elementLink"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/view_element_2E9304EB.html"
+guid="_ybefKdnmEdmO6L4XMImrsA">view element</a></i>.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/process_contribution.xmi b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/process_contribution.xmi
new file mode 100644
index 0000000..52b3ff4
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/process_contribution.xmi
@@ -0,0 +1,12 @@
+<?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: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="-fkIJikbdLETPdu0ALqo7fw"
+ name="new_term_definition,_3iqPEMaGEduMlb2cQZNTYw" guid="-fkIJikbdLETPdu0ALqo7fw"
+ changeDate="2007-02-27T09:21:33.607-0800">
+ <mainDescription>A special <a class="elementLinkWithUserText"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/process_68E308B4.html"
+guid="_yQ5m2NnmEdmO6L4XMImrsA">process</a> that externally defines additions and changes to an existing process without
+directly modifying it.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/process_package.xmi b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/process_package.xmi
new file mode 100644
index 0000000..8378d11
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/process_package.xmi
@@ -0,0 +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: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="-GBZOfgyCAdK00NMpe1N5_Q"
+ name="new_term_definition,_MN1doMaHEduMlb2cQZNTYw" guid="-GBZOfgyCAdK00NMpe1N5_Q"
+ changeDate="2007-02-27T09:23:38.044-0800">
+ <mainDescription>A&nbsp;method package that contains processes such as <a class="elementLinkWithUserText"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/capability_pattern_F5DDC5F.html"
+guid="_2RUJACO4EdqaNq6Ptg8uyA">capability patterns</a> or <a class="elementLinkWithUserText"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/delivery_process_BCDF50B7.html"
+guid="_ZufeMCO3EdqaNq6Ptg8uyA">delivery processes</a> only.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/release.xmi b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/release.xmi
new file mode 100644
index 0000000..bf2d749
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/release.xmi
@@ -0,0 +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.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="-hFYlBf3iN29RqVmHB9C4ug"
+ name="new_term_definition,_Ua93IMaHEduMlb2cQZNTYw" guid="-hFYlBf3iN29RqVmHB9C4ug"
+ changeDate="2007-02-27T11:26:19.003-0800">
+ <mainDescription>The delivery of a functional system meeting predefined objectives.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/stakeholder.xmi b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/stakeholder.xmi
new file mode 100644
index 0000000..f30447c
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/stakeholder.xmi
@@ -0,0 +1,12 @@
+<?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: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="_yWHeDdnmEdmO6L4XMImrsA"
+ name="stakeholder,_yWHeDNnmEdmO6L4XMImrsA" guid="_yWHeDdnmEdmO6L4XMImrsA">
+ <mainDescription>An individual who is who is materially affected by the&nbsp;outcome of the <a class="elementLink"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/process_68E308B4.html"
+guid="_yQ5m2NnmEdmO6L4XMImrsA">process</a>&nbsp;(i.e. the <a class="elementLink"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/deliverable_BFE1A5A9.html"
+guid="_yFbWoNnmEdmO6L4XMImrsA">deliverable</a>s&nbsp;the process produces).</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/static_work_product.xmi b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/static_work_product.xmi
new file mode 100644
index 0000000..01a566f
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/static_work_product.xmi
@@ -0,0 +1,12 @@
+<?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="_yWaY99nmEdmO6L4XMImrsA"
+ name="static_work_product,_yWaY9tnmEdmO6L4XMImrsA" guid="_yWaY99nmEdmO6L4XMImrsA"
+ changeDate="2005-09-07T15:07:47.378-0400" version="7.2.0">
+ <mainDescription>A <a class="elementLink" href="./../../../legacy.obsoleted_from_openup/guidances/termdefinitions/work_product_826E4C22.html"
+guid="_H4JXwB_SEdq6CKKKq4D7YA" >work product</a>&nbsp;that is used, but not changed, by a <a class="elementLink"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/process_68E308B4.html"
+guid="_yQ5m2NnmEdmO6L4XMImrsA">process</a>.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/test_case.xmi b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/test_case.xmi
new file mode 100644
index 0000000..2c7f8e1
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/test_case.xmi
@@ -0,0 +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: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="-6oW2YOnoWq_xPpmoil91KA"
+ name="test_case,_U4RYEEvOEdunZcj9T5hrMQ" guid="-6oW2YOnoWq_xPpmoil91KA">
+ <mainDescription><p>
+ The specification of a set of test inputs, execution conditions, and expected results, which need to be validated to
+ enable an assessment of some particular aspects of the system under test.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/tester.xmi b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/tester.xmi
new file mode 100644
index 0000000..4463dee
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/tester.xmi
@@ -0,0 +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: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="-prQBbamJ4CLPywfEbyaPaA"
+ name=",_WB6rQEvPEdunZcj9T5hrMQ" guid="-prQBbamJ4CLPywfEbyaPaA" changeDate="2006-09-24T07:20:01.152-0700">
+ <mainDescription>Role representing someone&nbsp; responsible for the core activities of the test effort.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/use_case.xmi b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/use_case.xmi
new file mode 100644
index 0000000..dace2a1
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/use_case.xmi
@@ -0,0 +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.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="-HDfMzDXoilK-f2iNreHRVg"
+ name=",_IHRO8EvHEdunZcj9T5hrMQ" guid="-HDfMzDXoilK-f2iNreHRVg">
+ <mainDescription>Captures requirements as&nbsp;a&nbsp; sequence of actions a system performs that yields an observable result of value to
+those interacting with the system.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/use_case_model.xmi b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/use_case_model.xmi
new file mode 100644
index 0000000..a2a298f
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/use_case_model.xmi
@@ -0,0 +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: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="-UTrE64wEDJIC1FRUomEYDg"
+ name=",_k6B3kEvmEdunZcj9T5hrMQ" guid="-UTrE64wEDJIC1FRUomEYDg">
+ <mainDescription>A&nbsp;model of the system use cases and actors and the relationships between them</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/view_element.xmi b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/view_element.xmi
new file mode 100644
index 0000000..c5c4106
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/view_element.xmi
@@ -0,0 +1,10 @@
+<?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: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="_ybefKtnmEdmO6L4XMImrsA"
+ name="view_element,_ybefKdnmEdmO6L4XMImrsA" guid="_ybefKtnmEdmO6L4XMImrsA" changeDate="2006-04-13T15:22:45.153-0700">
+ <mainDescription>A view element is a textual and/or graphical projection of a collection of <i><a class="elementLinkWithUserText"
+href="./../../../core.default.uma_concepts/guidances/termdefinitions/model_element_D23CE90D.html"
+guid="_yNnpVdnmEdmO6L4XMImrsA">model elements</a></i>.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/vision.xmi b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/vision.xmi
new file mode 100644
index 0000000..2c179d9
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/guidances/termdefinitions/vision.xmi
@@ -0,0 +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.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="-VMnkFJpPLdEDUpbz2QDgow"
+ name=",_J_5kgEvHEdunZcj9T5hrMQ" guid="-VMnkFJpPLdEDUpbz2QDgow" changeDate="2006-09-24T06:21:36.312-0700">
+ <mainDescription>The user's or customer's view of the product to be developed, specified at the level of key stakeholder needs and features
+of the system.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/obsoleted_from_openup/plugin.xmi b/praclib/temp/obsoleted_from_openup/plugin.xmi
new file mode 100644
index 0000000..3aa7652
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/plugin.xmi
@@ -0,0 +1,392 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_4-jR8UbFEdyx8quJU3Grxg"
+ guid="_4-jR8UbFEdyx8quJU3Grxg">
+ <resourceDescriptors xmi:id="_nEzWAfL5Edm6Nvont3uinw" id="_Nqwi8KeqEdmKDbQuyzCoqQ"
+ uri="tasks/detail_requirements.xmi"/>
+ <resourceDescriptors xmi:id="_NmdiMEf7EduISP1GQDlvVQ" id="-_mfd9ziTwQV_5LE80jJw4g"
+ uri="tasks/detail_requirements.ucm.xmi"/>
+ <resourceDescriptors xmi:id="_nxdG4DRcEduFvfVCXiK3AA" id="-JcGDIeBIMM099mbWX5fXbA"
+ uri="workproducts/use_case_intent_req.xmi"/>
+ <resourceDescriptors xmi:id="_mvi3tfL5Edm6Nvont3uinw" id="_zHZW9KYSEdmvhNXG0Oc2uA"
+ uri="workproducts/uc_model_intent_req_ucm.xmi"/>
+ <resourceDescriptors xmi:id="__wASEDRZEdudA-StyUUwnw" id="-SUqkkwrs1D_5YXZls-3YBg"
+ uri="workproducts/supporting_requirements_intent_req.xmi"/>
+ <resourceDescriptors xmi:id="_2hWugClTEduLGM8dfVsrKg" id="-U-5cLUk-mdaO518lh5CxTQ"
+ uri="guidances/guidelines/using_patterns.xmi"/>
+ <resourceDescriptors xmi:id="_nDXLkfL5Edm6Nvont3uinw" id="_K-e8IKX4EdmvhNXG0Oc2uA"
+ uri="workproducts/status_assessment.xmi"/>
+ <resourceDescriptors xmi:id="_dEVfgACsEdu8m4dIntu6jA" id="-HhGIkAPjHSIxnPzI3cyDnQ"
+ uri="guidances/concepts/managing_risks.xmi"/>
+ <resourceDescriptors xmi:id="_cuUoIEvrEdunZcj9T5hrMQ" id="-05pn_DGdNui9qqwx46iKZQ"
+ uri="guidances/termdefinitions/glossary.xmi"/>
+ <resourceDescriptors xmi:id="_R2ylEEvDEdunZcj9T5hrMQ" id="-COrjB4k8Qtf6ZpPEcBNwpw"
+ uri="guidances/termdefinitions/business_rule.xmi"/>
+ <resourceDescriptors xmi:id="_SVMdcMaHEduMlb2cQZNTYw" id="-GBZOfgyCAdK00NMpe1N5_Q"
+ uri="guidances/termdefinitions/process_package.xmi"/>
+ <resourceDescriptors xmi:id="_ceiKEArjEdqtvYgC7fo_aQ" id="_zZxTYNnmEdmO6L4XMImrsA"
+ uri="guidances/supportingmaterials/keyword_index.xmi"/>
+ <resourceDescriptors xmi:id="_4RT3pPIwEdm7AIOuZcqunQ" id="_zZxTYtnmEdmO6L4XMImrsA"
+ uri="guidances/supportingmaterials/search_engine.xmi"/>
+ <resourceDescriptors xmi:id="_5LUmUUvBEdunZcj9T5hrMQ" id="-4RQJzq_1URTZ5FGCBKnTIw"
+ uri="guidances/termdefinitions/actor.xmi"/>
+ <resourceDescriptors xmi:id="_Oz_loEvHEdunZcj9T5hrMQ" id="-VMnkFJpPLdEDUpbz2QDgow"
+ uri="guidances/termdefinitions/vision.xmi"/>
+ <resourceDescriptors xmi:id="_nzyS8UvmEdunZcj9T5hrMQ" id="-UTrE64wEDJIC1FRUomEYDg"
+ uri="guidances/termdefinitions/use_case_model.xmi"/>
+ <resourceDescriptors xmi:id="_uzNYoUvlEdunZcj9T5hrMQ" id="-HDfMzDXoilK-f2iNreHRVg"
+ uri="guidances/termdefinitions/use_case.xmi"/>
+ <resourceDescriptors xmi:id="_MGOxIUvCEdunZcj9T5hrMQ" id="-1RwpgmmY974S0YkxEOFDCw"
+ uri="guidances/termdefinitions/analyst.xmi"/>
+ <resourceDescriptors xmi:id="_zbijkEvCEdunZcj9T5hrMQ" id="-2QB1bosN011CudkwZ0cn-g"
+ uri="guidances/termdefinitions/architect.xmi"/>
+ <resourceDescriptors xmi:id="_aPpdcMaFEduMlb2cQZNTYw" id="-t4Xac9J5DWCA6r1b9L40Mw"
+ uri="guidances/termdefinitions/content_package.xmi"/>
+ <resourceDescriptors xmi:id="_auhsEB_LEdq6CKKKq4D7YA" id="-We7G-7OM2QspR_i1ErwtLA"
+ uri="guidances/termdefinitions/content_element.xmi"/>
+ <resourceDescriptors xmi:id="_NMio0B8-Edq-0cJih6RYrQ" id="_yE05tNnmEdmO6L4XMImrsA"
+ uri="guidances/termdefinitions/customer.xmi"/>
+ <resourceDescriptors xmi:id="_J9kvoUvPEdunZcj9T5hrMQ" id="-802sCZ4lJcejyRbhLmkxkw"
+ uri="guidances/termdefinitions/developer.xmi"/>
+ <resourceDescriptors xmi:id="_OucV4B89Edq-0cJih6RYrQ" id="_yG6kZNnmEdmO6L4XMImrsA"
+ uri="guidances/termdefinitions/document.xmi"/>
+ <resourceDescriptors xmi:id="_-Kk-QMaGEduMlb2cQZNTYw" id="-fkIJikbdLETPdu0ALqo7fw"
+ uri="guidances/termdefinitions/process_contribution.xmi"/>
+ <resourceDescriptors xmi:id="_3EDZoB87Edq-0cJih6RYrQ" id="_yNefZNnmEdmO6L4XMImrsA"
+ uri="guidances/termdefinitions/model.xmi"/>
+ <resourceDescriptors xmi:id="_ZkcCocaYEduMlb2cQZNTYw" id="-hFYlBf3iN29RqVmHB9C4ug"
+ uri="guidances/termdefinitions/release.xmi"/>
+ <resourceDescriptors xmi:id="_IItYAB89Edq-0cJih6RYrQ" id="_yNnpVtnmEdmO6L4XMImrsA"
+ uri="guidances/termdefinitions/model_element.xmi"/>
+ <resourceDescriptors xmi:id="_FETWYB8-Edq-0cJih6RYrQ" id="_yWHeDdnmEdmO6L4XMImrsA"
+ uri="guidances/termdefinitions/stakeholder.xmi"/>
+ <resourceDescriptors xmi:id="_x-GsIB8-Edq-0cJih6RYrQ" id="_yWaY99nmEdmO6L4XMImrsA"
+ uri="guidances/termdefinitions/static_work_product.xmi"/>
+ <resourceDescriptors xmi:id="_n2PogUvPEdunZcj9T5hrMQ" id="-6oW2YOnoWq_xPpmoil91KA"
+ uri="guidances/termdefinitions/test_case.xmi"/>
+ <resourceDescriptors xmi:id="_a7dNEUvPEdunZcj9T5hrMQ" id="-prQBbamJ4CLPywfEbyaPaA"
+ uri="guidances/termdefinitions/tester.xmi"/>
+ <resourceDescriptors xmi:id="_BHbGkB89Edq-0cJih6RYrQ" id="_ybefKtnmEdmO6L4XMImrsA"
+ uri="guidances/termdefinitions/view_element.xmi"/>
+ <resourceDescriptors xmi:id="_m-9zx_L5Edm6Nvont3uinw" id="_Qo7pYMM3EdmSIPI87WLu3g"
+ uri="guidances/guidelines/design.xmi"/>
+ <resourceDescriptors xmi:id="_09MY8EyFEdu-df7p0PuRvQ" id="-XMbxFU8M85cRlf3C4iwAGw"
+ uri="guidances/guidelines/physical_data_modeling.xmi"/>
+ <resourceDescriptors xmi:id="_XQS1oC5REduVhuZHT5jKZQ" id="-VGT8iHGtQSiOUGitq1qmow"
+ uri="guidances/concepts/types_of_developer_tests.xmi"/>
+ <resourceDescriptors xmi:id="_rKMEsMEvEduwZvIr61GnNg" id="-clUV9n59dDwg0e1VCcsB8Q"
+ uri="guidances/guidelines/openup_architecture.xmi"/>
+ <resourceDescriptors xmi:id="_GU3Q0MExEduwZvIr61GnNg" id="-_BjYXvrfe1HHL5Y_QBfh4Q"
+ uri="guidances/guidelines/openup_risk.xmi"/>
+ <resourceDescriptors xmi:id="_FdKesMEvEduwZvIr61GnNg" id="-Mobjz86dw07NW5-IhtEoNA"
+ uri="guidances/guidelines/openup_iterations.xmi"/>
+ <resourceDescriptors xmi:id="_HhqNQDn8Edu_y4hBImiwwQ" id="-fDVhZTkf1TqDyExbI9DM-w"
+ uri="workproducts/work_items_list_pm.xmi"/>
+ <resourceDescriptors xmi:id="_prz9sMUKEdu5GrwIlTJV7g" id="-I-2SvZtjELUYDQO0jvdxEA"
+ uri="guidances/guidelines/outlining_the_architecture.vm.xmi"/>
+ <resourceDescriptors xmi:id="_43csUA3tEduibvKwrGxWxA" id="-YeVRerdEixh4HgHOuw2KRQ"
+ uri="guidances/guidelines/outlining_the_arch.xmi"/>
+ <resourceDescriptors xmi:id="_nrMMoBapEduSTJywppIxVQ" id="-t7mQSRPYITkMoYRVNz7jQg"
+ uri="guidances/guidelines/refining_the_architecture.xmi"/>
+ <resourceDescriptors xmi:id="_kdDu4NvJEduv2KOT-Teh6w" id="-bP4wJKW0CrR9pL0yz20r3Q"
+ uri="guidances/guidelines/describing_arch_mechanisms.xmi"/>
+ <resourceDescriptors xmi:id="_NvMaYNvKEduv2KOT-Teh6w" id="-EUXQjT8DebSClO4YjNuoHw"
+ uri="guidances/guidelines/determining_arch_significant_rqmts.xmi"/>
+ <resourceDescriptors xmi:id="_ZXEuAClFEduLGM8dfVsrKg" id="-cnGBBA4NXmhTIjHjlHx4Mw"
+ uri="guidances/concepts/four_plus_one_view_of_arch.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_4-jR4EbFEdyx8quJU3Grxg" name="obsoleted_from_openup"
+ guid="_4-jR4EbFEdyx8quJU3Grxg" briefDescription="This plug-in documents what is no longer included in the new open source practice library. See the description of each content package for further details."
+ changeDate="2008-02-08T14:00:55.609-0500">
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4-jR4UbFEdyx8quJU3Grxg"
+ name="Content" guid="_4-jR4UbFEdyx8quJU3Grxg">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4-jR4kbFEdyx8quJU3Grxg"
+ name="Categories" guid="_4-jR4kbFEdyx8quJU3Grxg">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4-jR40bFEdyx8quJU3Grxg"
+ name="Domains" guid="_4-jR40bFEdyx8quJU3Grxg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4-jR5EbFEdyx8quJU3Grxg"
+ name="Disciplines" guid="_4-jR5EbFEdyx8quJU3Grxg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4-jR5UbFEdyx8quJU3Grxg"
+ name="RoleSets" guid="_4-jR5UbFEdyx8quJU3Grxg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4-jR5kbFEdyx8quJU3Grxg"
+ name="WP Types" guid="_4-jR5kbFEdyx8quJU3Grxg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4-jR50bFEdyx8quJU3Grxg"
+ name="Tools" guid="_4-jR50bFEdyx8quJU3Grxg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4-jR6EbFEdyx8quJU3Grxg"
+ name="StandardCategories" guid="_4-jR6EbFEdyx8quJU3Grxg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4-jR6UbFEdyx8quJU3Grxg"
+ name="CustomCategories" guid="_4-jR6UbFEdyx8quJU3Grxg">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4-jR6kbFEdyx8quJU3Grxg"
+ name="Hidden" guid="_4-jR6kbFEdyx8quJU3Grxg">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_4-jR60bFEdyx8quJU3Grxg"
+ name="Custom Categories" guid="_4-jR60bFEdyx8quJU3Grxg"/>
+ </childPackages>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4-jR7EbFEdyx8quJU3Grxg"
+ name="CoreContent" guid="_4-jR7EbFEdyx8quJU3Grxg">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_8NYlYEbFEdyx8quJU3Grxg"
+ name="OBSOLETED OpenUP Content" guid="_8NYlYEbFEdyx8quJU3Grxg" briefDescription="These elements do not exist in the new open source practice library, but they did exist in OpenUP 1.0. They are no longer needed for the new open source practice library. The original OpenUP elements have been moved here in the event that someone wants to put these elements back into the practice library. By moving them from here the guid is preserved. This also serves as documentation for the Open Source community of what was removed from OpenUP 1.0 content.">
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_0e1mIMlgEdmt3adZL5Dmdw"
+ name="detail_requirements" guid="_0e1mIMlgEdmt3adZL5Dmdw" briefDescription="The purpose of this task is to describe one or more requirements in sufficient detail to validate understanding of the requirement, to ensure concurrence with stakeholder expectations, and to permit software development to begin."
+ orderingGuide="<?xml version="1.0" encoding="ASCII"?> <com.ibm.uma.edit.tng.util.model:OrderInfoCollection xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:com.ibm.uma.edit.tng.util.model="http:///com/ibm/uma/edit/tng/util/model.ecore"> <orderInfos name="sections" timestamp="1113334493908"> <gUIDs>_yqm4kKuJEdmhFZtkg1nakg</gUIDs> <gUIDs>_zg2kEKuJEdmhFZtkg1nakg</gUIDs> <gUIDs>_1GGDkKuJEdmhFZtkg1nakg</gUIDs> <gUIDs>_35vP4KuJEdmhFZtkg1nakg</gUIDs> <gUIDs>_5mtIAKuJEdmhFZtkg1nakg</gUIDs> <gUIDs>_7g3HkKuJEdmhFZtkg1nakg</gUIDs> </orderInfos> </com.ibm.uma.edit.tng.util.model:OrderInfoCollection> "
+ presentationName="* Detail Requirements">
+ <presentation xmi:id="_Nqwi8KeqEdmKDbQuyzCoqQ" href="uma://_Nqwi8KeqEdmKDbQuyzCoqQ#_Nqwi8KeqEdmKDbQuyzCoqQ"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_VQ268O0KEdqHTdbLTmC5IQ"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_0Wh-sMlgEdmt3adZL5Dmdw"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_eYtQQO0KEdqHTdbLTmC5IQ"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_VXZ5wO0IEdqHTdbLTmC5IQ"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_KudM0NcJEdqz_d2XWoVt6Q"/>
+ <checklists href="uma://_OOB2AAouEdyhlpBPrduOMw#_jxn9EO0HEdqHTdbLTmC5IQ"/>
+ <checklists href="uma://_OOB2AAouEdyhlpBPrduOMw#_Vael8CGMEdu3VKXZx45D3A"/>
+ <checklists href="uma://_OOB2AAouEdyhlpBPrduOMw#_0kNwINk1Edq2Q8qZoWbvGA"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_E-dPIL-GEdqb7N6KIeDL8Q"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_1AOsMO0JEdqHTdbLTmC5IQ"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_6jXzYNcKEdqz_d2XWoVt6Q"/>
+ <guidelines href="uma://_GbYfULPaEduocbW-TPTq7A#_4BJ_YCxSEdqjsdw1QLH_6Q"/>
+ <guidelines href="uma://_GbYfULPaEduocbW-TPTq7A#_qq0GMAXkEduj_7BEUj1JfQ"/>
+ <mandatoryInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_BVh9cL-CEdqb7N6KIeDL8Q"/>
+ <mandatoryInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0VGbUMlgEdmt3adZL5Dmdw"/>
+ <mandatoryInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#__ViBYEL8EdyP_Jn83ylwUQ"/>
+ <output xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_BVh9cL-CEdqb7N6KIeDL8Q"/>
+ <output xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0VGbUMlgEdmt3adZL5Dmdw"/>
+ <output xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_XNPOoEMDEdyP_Jn83ylwUQ"/>
+ <optionalInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_XNPOoEMDEdyP_Jn83ylwUQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_7_3vEAFmEduDPKiaP0pu-Q"
+ name="detail_requirements.ucm" guid="_7_3vEAFmEduDPKiaP0pu-Q" orderingGuide="<?xml version="1.0" encoding="ASCII"?> <org.eclipse.epf.uma.edit.tng.util.model:OrderInfoCollection xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma.edit.tng.util.model="http:///com/ibm/uma/edit/tng/util/model.ecore"> <orderInfos name="sections" timestamp="1186062903593"> <gUIDs>_GCLqsED8EdyoefaQkqWN_Q</gUIDs> <gUIDs>_IYYtEED8EdyoefaQkqWN_Q</gUIDs> <gUIDs>_yuAxYAo_EdyT57ElgMr6TA</gUIDs> <gUIDs>_NRUK4ED8EdyoefaQkqWN_Q</gUIDs> <gUIDs>_Tk_IYED8EdyoefaQkqWN_Q</gUIDs> </orderInfos> </org.eclipse.epf.uma.edit.tng.util.model:OrderInfoCollection> "
+ presentationName="(was detail_requirements_intent_req_ucm)" variabilityType="contributes"
+ variabilityBasedOnElement="_0e1mIMlgEdmt3adZL5Dmdw">
+ <presentation xmi:id="-_mfd9ziTwQV_5LE80jJw4g" href="uma://-_mfd9ziTwQV_5LE80jJw4g#-_mfd9ziTwQV_5LE80jJw4g"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_oclg0DRXEdudA-StyUUwnw"
+ name="supporting_requirements_intent_req" guid="_oclg0DRXEdudA-StyUUwnw"
+ variabilityType="contributes">
+ <presentation xmi:id="-SUqkkwrs1D_5YXZls-3YBg" href="uma://-SUqkkwrs1D_5YXZls-3YBg#-SUqkkwrs1D_5YXZls-3YBg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_0UCrZclgEdmt3adZL5Dmdw"
+ name="uc_model_intent_req_ucm" guid="_0UCrZclgEdmt3adZL5Dmdw" briefDescription="This artifact captures a model of the system's intended functions and its environment, and serves as a contract between the customer and the developers."
+ variabilityType="contributes">
+ <presentation xmi:id="_zHZW9KYSEdmvhNXG0Oc2uA" href="uma://_zHZW9KYSEdmvhNXG0Oc2uA#_zHZW9KYSEdmvhNXG0Oc2uA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_qis78DRbEduFvfVCXiK3AA"
+ name="use_case_intent_req" guid="_qis78DRbEduFvfVCXiK3AA" variabilityType="contributes">
+ <presentation xmi:id="-JcGDIeBIMM099mbWX5fXbA" href="uma://-JcGDIeBIMM099mbWX5fXbA#-JcGDIeBIMM099mbWX5fXbA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_SBnZ4AFlEduDPKiaP0pu-Q"
+ name="use_case_intent_req_ucm" guid="_SBnZ4AFlEduDPKiaP0pu-Q" variabilityType="contributes"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_NtGL0EvDEdunZcj9T5hrMQ"
+ name="business_rule" guid="_NtGL0EvDEdunZcj9T5hrMQ" presentationName="** business rule">
+ <presentation xmi:id="-COrjB4k8Qtf6ZpPEcBNwpw" href="uma://-COrjB4k8Qtf6ZpPEcBNwpw#-COrjB4k8Qtf6ZpPEcBNwpw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_MN1doMaHEduMlb2cQZNTYw"
+ name="process_package" guid="_MN1doMaHEduMlb2cQZNTYw" presentationName="process package">
+ <presentation xmi:id="-GBZOfgyCAdK00NMpe1N5_Q" href="uma://-GBZOfgyCAdK00NMpe1N5_Q#-GBZOfgyCAdK00NMpe1N5_Q"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="2.0088322577945588E-305"
+ name="keyword_index" guid="2.0088322577945588E-305" briefDescription="The keyword index provides the ability to look-up topics based on keywords or topics."
+ presentationName="Keyword Index" nodeicon="../../../NewLibs/opn/shared/legacy.obsoleted_from_openup/guidances/supportingmaterials/resources/bookc.gif">
+ <presentation xmi:id="_zZxTYNnmEdmO6L4XMImrsA" href="uma://_zZxTYNnmEdmO6L4XMImrsA#_zZxTYNnmEdmO6L4XMImrsA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="3.1789140222665413E-305"
+ name="search_engine" guid="3.1789140222665413E-305" briefDescription="The search engine allows you to search for pages in the published Web Site."
+ presentationName="Search Engine" shapeicon="../../../NewLibs/opn/shared/legacy.obsoleted_from_openup/guidances/supportingmaterials/resources/bookcL.gif"
+ nodeicon="../../../NewLibs/opn/shared/legacy.obsoleted_from_openup/guidances/supportingmaterials/resources/bookc.gif">
+ <presentation xmi:id="_zZxTYtnmEdmO6L4XMImrsA" href="uma://_zZxTYtnmEdmO6L4XMImrsA#_zZxTYtnmEdmO6L4XMImrsA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_ZsK30EvBEdunZcj9T5hrMQ"
+ name="actor" guid="_ZsK30EvBEdunZcj9T5hrMQ" presentationName="actor">
+ <presentation xmi:id="-4RQJzq_1URTZ5FGCBKnTIw" href="uma://-4RQJzq_1URTZ5FGCBKnTIw#-4RQJzq_1URTZ5FGCBKnTIw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_k6B3kEvmEdunZcj9T5hrMQ"
+ name="use_case_model" guid="_k6B3kEvmEdunZcj9T5hrMQ" presentationName="use-case model">
+ <presentation xmi:id="-UTrE64wEDJIC1FRUomEYDg" href="uma://-UTrE64wEDJIC1FRUomEYDg#-UTrE64wEDJIC1FRUomEYDg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_IHRO8EvHEdunZcj9T5hrMQ"
+ name="use_case" guid="_IHRO8EvHEdunZcj9T5hrMQ" presentationName="use case">
+ <presentation xmi:id="-HDfMzDXoilK-f2iNreHRVg" href="uma://-HDfMzDXoilK-f2iNreHRVg#-HDfMzDXoilK-f2iNreHRVg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_J_5kgEvHEdunZcj9T5hrMQ"
+ name="vision" guid="_J_5kgEvHEdunZcj9T5hrMQ" presentationName="vision">
+ <presentation xmi:id="-VMnkFJpPLdEDUpbz2QDgow" href="uma://-VMnkFJpPLdEDUpbz2QDgow#-VMnkFJpPLdEDUpbz2QDgow"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_GEAwAEvCEdunZcj9T5hrMQ"
+ name="analyst" guid="_GEAwAEvCEdunZcj9T5hrMQ" presentationName="analyst">
+ <presentation xmi:id="-1RwpgmmY974S0YkxEOFDCw" href="uma://-1RwpgmmY974S0YkxEOFDCw#-1RwpgmmY974S0YkxEOFDCw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_wI3R4EvCEdunZcj9T5hrMQ"
+ name="architect" guid="_wI3R4EvCEdunZcj9T5hrMQ" presentationName="architect">
+ <presentation xmi:id="-2QB1bosN011CudkwZ0cn-g" href="uma://-2QB1bosN011CudkwZ0cn-g#-2QB1bosN011CudkwZ0cn-g"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_N8x34B_LEdq6CKKKq4D7YA"
+ name="content_element" guid="_N8x34B_LEdq6CKKKq4D7YA" presentationName="content element">
+ <presentation xmi:id="-We7G-7OM2QspR_i1ErwtLA" href="uma://-We7G-7OM2QspR_i1ErwtLA#-We7G-7OM2QspR_i1ErwtLA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_SAWgwMaFEduMlb2cQZNTYw"
+ name="content_package" guid="_SAWgwMaFEduMlb2cQZNTYw" presentationName="content package">
+ <presentation xmi:id="-t4Xac9J5DWCA6r1b9L40Mw" href="uma://-t4Xac9J5DWCA6r1b9L40Mw#-t4Xac9J5DWCA6r1b9L40Mw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_yE05s9nmEdmO6L4XMImrsA"
+ name="customer" guid="_yE05s9nmEdmO6L4XMImrsA" presentationName="customer">
+ <presentation xmi:id="_yE05tNnmEdmO6L4XMImrsA" href="uma://_yE05tNnmEdmO6L4XMImrsA#_yE05tNnmEdmO6L4XMImrsA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_-61a8EvOEdunZcj9T5hrMQ"
+ name="developer" guid="_-61a8EvOEdunZcj9T5hrMQ" presentationName="developer">
+ <presentation xmi:id="-802sCZ4lJcejyRbhLmkxkw" href="uma://-802sCZ4lJcejyRbhLmkxkw#-802sCZ4lJcejyRbhLmkxkw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_yG6kY9nmEdmO6L4XMImrsA"
+ name="document" guid="_yG6kY9nmEdmO6L4XMImrsA" presentationName="document">
+ <presentation xmi:id="_yG6kZNnmEdmO6L4XMImrsA" href="uma://_yG6kZNnmEdmO6L4XMImrsA#_yG6kZNnmEdmO6L4XMImrsA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_yNnpVdnmEdmO6L4XMImrsA"
+ name="model_element" guid="_yNnpVdnmEdmO6L4XMImrsA" presentationName="model element">
+ <presentation xmi:id="_yNnpVtnmEdmO6L4XMImrsA" href="uma://_yNnpVtnmEdmO6L4XMImrsA#_yNnpVtnmEdmO6L4XMImrsA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_yNefY9nmEdmO6L4XMImrsA"
+ name="model" guid="_yNefY9nmEdmO6L4XMImrsA" presentationName="model">
+ <presentation xmi:id="_yNefZNnmEdmO6L4XMImrsA" href="uma://_yNefZNnmEdmO6L4XMImrsA#_yNefZNnmEdmO6L4XMImrsA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_3iqPEMaGEduMlb2cQZNTYw"
+ name="process_contribution" guid="_3iqPEMaGEduMlb2cQZNTYw" presentationName="process contribution">
+ <presentation xmi:id="-fkIJikbdLETPdu0ALqo7fw" href="uma://-fkIJikbdLETPdu0ALqo7fw#-fkIJikbdLETPdu0ALqo7fw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_Ua93IMaHEduMlb2cQZNTYw"
+ name="release" guid="_Ua93IMaHEduMlb2cQZNTYw" presentationName="release">
+ <presentation xmi:id="-hFYlBf3iN29RqVmHB9C4ug" href="uma://-hFYlBf3iN29RqVmHB9C4ug#-hFYlBf3iN29RqVmHB9C4ug"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_yWHeDNnmEdmO6L4XMImrsA"
+ name="stakeholder" guid="_yWHeDNnmEdmO6L4XMImrsA" presentationName="stakeholder">
+ <presentation xmi:id="_yWHeDdnmEdmO6L4XMImrsA" href="uma://_yWHeDdnmEdmO6L4XMImrsA#_yWHeDdnmEdmO6L4XMImrsA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_yWaY9tnmEdmO6L4XMImrsA"
+ name="static_work_product" guid="_yWaY9tnmEdmO6L4XMImrsA" presentationName="static work product">
+ <presentation xmi:id="_yWaY99nmEdmO6L4XMImrsA" href="uma://_yWaY99nmEdmO6L4XMImrsA#_yWaY99nmEdmO6L4XMImrsA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_U4RYEEvOEdunZcj9T5hrMQ"
+ name="test_case" guid="_U4RYEEvOEdunZcj9T5hrMQ" presentationName="test case">
+ <presentation xmi:id="-6oW2YOnoWq_xPpmoil91KA" href="uma://-6oW2YOnoWq_xPpmoil91KA#-6oW2YOnoWq_xPpmoil91KA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_WB6rQEvPEdunZcj9T5hrMQ"
+ name="tester" guid="_WB6rQEvPEdunZcj9T5hrMQ" presentationName="tester">
+ <presentation xmi:id="-prQBbamJ4CLPywfEbyaPaA" href="uma://-prQBbamJ4CLPywfEbyaPaA#-prQBbamJ4CLPywfEbyaPaA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_ybefKdnmEdmO6L4XMImrsA"
+ name="view_element" guid="_ybefKdnmEdmO6L4XMImrsA" presentationName="view element">
+ <presentation xmi:id="_ybefKtnmEdmO6L4XMImrsA" href="uma://_ybefKtnmEdmO6L4XMImrsA#_ybefKtnmEdmO6L4XMImrsA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_0X3bcMlgEdmt3adZL5Dmdw"
+ name="design" guid="_0X3bcMlgEdmt3adZL5Dmdw" briefDescription="This guideline gives additional information on how to design a portion of the system."
+ presentationName="Design">
+ <presentation xmi:id="_Qo7pYMM3EdmSIPI87WLu3g" href="uma://_Qo7pYMM3EdmSIPI87WLu3g#_Qo7pYMM3EdmSIPI87WLu3g"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_VhhDMEvrEdunZcj9T5hrMQ"
+ name="glossary" guid="_VhhDMEvrEdunZcj9T5hrMQ" presentationName="[CONSIDER DELETING] glossary">
+ <presentation xmi:id="-05pn_DGdNui9qqwx46iKZQ" href="uma://-05pn_DGdNui9qqwx46iKZQ#-05pn_DGdNui9qqwx46iKZQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_sNoQ0Dn6Edu_y4hBImiwwQ"
+ name="work_items_list_pm" guid="_sNoQ0Dn6Edu_y4hBImiwwQ" briefDescription="[*** NOTE: This content has been added directly to the work_items_list artifact, rather than contributing it ***]">
+ <presentation xmi:id="-fDVhZTkf1TqDyExbI9DM-w" href="uma://-fDVhZTkf1TqDyExbI9DM-w#-fDVhZTkf1TqDyExbI9DM-w"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_SYDjUMUKEdu5GrwIlTJV7g"
+ name="outlining_the_architecture.vm" guid="_SYDjUMUKEdu5GrwIlTJV7g"
+ variabilityType="contributes" variabilityBasedOnElement="_42UD4A3tEduibvKwrGxWxA">
+ <presentation xmi:id="-I-2SvZtjELUYDQO0jvdxEA" href="uma://-I-2SvZtjELUYDQO0jvdxEA#-I-2SvZtjELUYDQO0jvdxEA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_42UD4A3tEduibvKwrGxWxA"
+ name="outlining_the_arch" guid="_42UD4A3tEduibvKwrGxWxA" briefDescription="This guideline provides suggestions and recommendations for outlining an architecture."
+ presentationName="Outlining the Architecture">
+ <presentation xmi:id="-YeVRerdEixh4HgHOuw2KRQ" href="uma://-YeVRerdEixh4HgHOuw2KRQ#-YeVRerdEixh4HgHOuw2KRQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_mDf2EBapEduSTJywppIxVQ"
+ name="refining_the_architecture" guid="_mDf2EBapEduSTJywppIxVQ" briefDescription="This guideline provides additional information to support the ongoing refinement and development of the architecture."
+ presentationName="Refining the Architecture">
+ <presentation xmi:id="-t7mQSRPYITkMoYRVNz7jQg" href="uma://-t7mQSRPYITkMoYRVNz7jQg#-t7mQSRPYITkMoYRVNz7jQg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_J6BKgNvIEduv2KOT-Teh6w"
+ name="describing_arch_mechanisms" guid="_J6BKgNvIEduv2KOT-Teh6w" briefDescription="This guideline describes how to describe the different categories of architectural mechanisms."
+ presentationName="Describing Architectural Mechanisms">
+ <presentation xmi:id="-bP4wJKW0CrR9pL0yz20r3Q" href="uma://-bP4wJKW0CrR9pL0yz20r3Q#-bP4wJKW0CrR9pL0yz20r3Q"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_D3JXMNvKEduv2KOT-Teh6w"
+ name="determining_arch_significant_rqmts" guid="_D3JXMNvKEduv2KOT-Teh6w"
+ briefDescription="This guideline describes techniques for identifying and prioritizing architecturally-significant requirements."
+ presentationName="Determining Architecturally-Significant Requirements">
+ <presentation xmi:id="-EUXQjT8DebSClO4YjNuoHw" href="uma://-EUXQjT8DebSClO4YjNuoHw#-EUXQjT8DebSClO4YjNuoHw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_T9nygClEEduLGM8dfVsrKg"
+ name="four_plus_one_view_of_arch" guid="_T9nygClEEduLGM8dfVsrKg" briefDescription="This concept describes on possible set of views for describing a software architecture."
+ presentationName="4+1 Views of Software Architecture">
+ <presentation xmi:id="-cnGBBA4NXmhTIjHjlHx4Mw" href="uma://-cnGBBA4NXmhTIjHjlHx4Mw#-cnGBBA4NXmhTIjHjlHx4Mw"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4tHfAEdGEdyxNt4vToxPuw"
+ name="DEPRECATED in OpenUP 1.0" guid="_4tHfAEdGEdyxNt4vToxPuw" briefDescription="These elements were in OpenUP 0.9 plus (as of 03/22/07), but are no longer in OpenUP 1.0.">
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_0cr7cACrEdu8m4dIntu6jA"
+ name="using_patterns" guid="_0cr7cACrEdu8m4dIntu6jA" briefDescription="This guidance discusses the practical application of patterns in a project."
+ presentationName="Using Patterns">
+ <presentation xmi:id="-U-5cLUk-mdaO518lh5CxTQ" href="uma://-U-5cLUk-mdaO518lh5CxTQ#-U-5cLUk-mdaO518lh5CxTQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_0bA2EMlgEdmt3adZL5Dmdw"
+ name="status_assessment" guid="_0bA2EMlgEdmt3adZL5Dmdw" briefDescription="Capture and communicate results and actions from assessments. This is typically done at the end of each iteration."
+ presentationName="Status Assessment">
+ <presentation xmi:id="_K-e8IKX4EdmvhNXG0Oc2uA" href="uma://_K-e8IKX4EdmvhNXG0Oc2uA#_K-e8IKX4EdmvhNXG0Oc2uA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_ienXEEyAEdu-df7p0PuRvQ"
+ name="physical_data_modeling" guid="_ienXEEyAEdu-df7p0PuRvQ" briefDescription="A physical data model (PDM) captures the design of a persistent data store such as a relational database or data file. Data modeling is the act of creating such a model."
+ presentationName="Physical Data Modeling">
+ <presentation xmi:id="-XMbxFU8M85cRlf3C4iwAGw" href="uma://-XMbxFU8M85cRlf3C4iwAGw#-XMbxFU8M85cRlf3C4iwAGw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_REqtUMEvEduwZvIr61GnNg"
+ name="openup_architecture" guid="_REqtUMEvEduwZvIr61GnNg" briefDescription="The early iterations of OpenUP/Basic focus on addressing the requirements that will produce an executable architecture. Buiding and validating the architecture first significantly reduces the technical risk in a project."
+ presentationName="The Importance of Architecture in OpenUP/Basic" shapeicon="guidances/guidelines/resources/icon_introL.gif"
+ nodeicon="guidances/guidelines/resources/mic.gif">
+ <presentation xmi:id="-clUV9n59dDwg0e1VCcsB8Q" href="uma://-clUV9n59dDwg0e1VCcsB8Q#-clUV9n59dDwg0e1VCcsB8Q"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_U3VjIMEuEduwZvIr61GnNg"
+ name="openup_iterations" guid="_U3VjIMEuEduwZvIr61GnNg" briefDescription="The set of iterations in a phase address specific milestones that objectively track a project's progress. Each phase has its own milestone that reflects the emphasis of the phase."
+ presentationName="The Benefit of OpenUP/Basic Iterations" shapeicon="guidances/guidelines/resources/icon_introL.gif"
+ nodeicon="guidances/guidelines/resources/mic.gif">
+ <presentation xmi:id="-Mobjz86dw07NW5-IhtEoNA" href="uma://-Mobjz86dw07NW5-IhtEoNA#-Mobjz86dw07NW5-IhtEoNA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_G08UgMEwEduwZvIr61GnNg"
+ name="openup_risk" guid="_G08UgMEwEduwZvIr61GnNg" briefDescription="Risk is a reflection of uncertainty in a project. Reducing uncertainty increases the predictability and possible of success."
+ presentationName="OpenUP/Basic constantly identifies and removes risk from a project"
+ shapeicon="guidances/guidelines/resources/icon_introL.gif" nodeicon="guidances/guidelines/resources/mic.gif">
+ <presentation xmi:id="-_BjYXvrfe1HHL5Y_QBfh4Q" href="uma://-_BjYXvrfe1HHL5Y_QBfh4Q#-_BjYXvrfe1HHL5Y_QBfh4Q"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_NOHy0BOGEduCNqgZdt_OaA"
+ name="using_openup_basic" guid="_NOHy0BOGEduCNqgZdt_OaA" briefDescription="This guideline explains the various usage scenarios of this Web site."
+ presentationName="Using OpenUP/Basic" shapeicon="guidances/guidelines/resources/compassL.gif"
+ nodeicon="guidances/guidelines/resources/compass.gif"/>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_lyzMoMt1EdyuBO4ZIzcyig"
+ name="Not used in OpenUP 1.0 - but still in the CVS library" guid="_lyzMoMt1EdyuBO4ZIzcyig"
+ briefDescription="This element is still in the CVS library for OpenUP 1.0, however there are no references to it from the content anywhere. It is essentially dead content in the OpenUP 1.0 library.">
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_eRutgC5QEduVhuZHT5jKZQ"
+ name="types_of_developer_tests" guid="_eRutgC5QEduVhuZHT5jKZQ" briefDescription="This guideline describes various types of developer tests."
+ presentationName="Types of Developer Tests">
+ <presentation xmi:id="-VGT8iHGtQSiOUGitq1qmow" href="uma://-VGT8iHGtQSiOUGitq1qmow#-VGT8iHGtQSiOUGitq1qmow"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_4-jR7UbFEdyx8quJU3Grxg"
+ name="CapabilityPatterns" guid="_4-jR7UbFEdyx8quJU3Grxg"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_4-jR7kbFEdyx8quJU3Grxg"
+ name="DeliveryProcesses" guid="_4-jR7kbFEdyx8quJU3Grxg"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_4-jR70bFEdyx8quJU3Grxg"
+ name="ProcessContributions" guid="_4-jR70bFEdyx8quJU3Grxg"/>
+ <bases href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0ELXuEduGP_98XMd0fg"/>
+ <bases href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2AAouEdyhlpBPrduOMw"/>
+ <bases href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKMLS9EduDY8LNbMCDBA"/>
+ <bases href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfULPaEduocbW-TPTq7A"/>
+ <bases href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS4LPREduocbW-TPTq7A"/>
+ <bases href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK0LPPEduocbW-TPTq7A"/>
+ <bases href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPEEKmEdyrauqpmnA8jQ"/>
+ <bases href="uma://_iVydgENdEdy245g62lfWcA#_iVydgENdEdy245g62lfWcA"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/obsoleted_from_openup/tasks/detail_requirements.ucm.xmi b/praclib/temp/obsoleted_from_openup/tasks/detail_requirements.ucm.xmi
new file mode 100644
index 0000000..d447f52
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/tasks/detail_requirements.ucm.xmi
@@ -0,0 +1,22 @@
+<?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.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="-_mfd9ziTwQV_5LE80jJw4g"
+ name="detail_requirements.ucm,_7_3vEAFmEduDPKiaP0pu-Q" guid="-_mfd9ziTwQV_5LE80jJw4g"
+ version="1.0.0">
+ <sections xmi:id="_yuAxYAo_EdyT57ElgMr6TA" name="Update Use-Case Model" guid="_yuAxYAo_EdyT57ElgMr6TA">
+ <sectionDescription>Based on your work update the <a class="elementLink"
+href="./../../core.tech.common.base/workproducts/use_case_model_85965D1B.html" guid="_W2SgEDR5EdutE_HNDTJk5Q">*Use-Case
+Model</a>.&nbsp; Add, remove or update&nbsp;<a class="elementLinkWithUserText"
+href="./../../core.tech.common.base/guidances/concepts/actor_411726C.html" guid="_zGqO0MDpEduTGJ8i4u8TMw">Actors</a> and
+<a class="elementLink" href="./../../core.tech.common.base/workproducts/use_case_22BE66E2.html"
+guid="_0VGbUMlgEdmt3adZL5Dmdw">***Use Case</a>s as required.&nbsp; For more information on creating and structuring your
+use case model see <a class="elementLinkWithType"
+href="./../../opn.tech.prac.rqmts_with_use_cases/guidances/guidelines/use_case_model_4C64E97D.html"
+guid="_0VAUsMlgEdmt3adZL5Dmdw">Guideline: *Use-Case Model</a>.&nbsp; For assistance in assessing the quality of your use
+case model see <a class="elementLinkWithType"
+href="./../../opn.tech.prac.rqmts_with_use_cases/guidances/checklists/use_case_model_27A2D1CF.html"
+guid="_0U6OEMlgEdmt3adZL5Dmdw">Checklist: *Use-Case Model</a>.</sectionDescription>
+ </sections>
+</org.eclipse.epf.uma:TaskDescription>
diff --git a/praclib/temp/obsoleted_from_openup/tasks/detail_requirements.xmi b/praclib/temp/obsoleted_from_openup/tasks/detail_requirements.xmi
new file mode 100644
index 0000000..c778104
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/tasks/detail_requirements.xmi
@@ -0,0 +1,94 @@
+<?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.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="_Nqwi8KeqEdmKDbQuyzCoqQ"
+ name="detail_requirements,_0e1mIMlgEdmt3adZL5Dmdw" guid="_Nqwi8KeqEdmKDbQuyzCoqQ"
+ changeDate="2006-09-29T15:31:25.226-0700" version="1.0.0">
+ <sections xmi:id="_vWeHMCxSEdqjsdw1QLH_6Q" name="Detail Use Cases and Scenarios"
+ guid="_vWeHMCxSEdqjsdw1QLH_6Q">
+ <sectionDescription><p>
+ Some <a class="elementLink" href="./../../core.tech.common.base/workproducts/use_case_22BE66E2.html"
+ guid="_0VGbUMlgEdmt3adZL5Dmdw">***Use Case</a>s and scenarios may need to be described in more detail to validate our
+ understanding of the requirement and to permit software development to begin. This does not imply that all&nbsp;use
+ cases and scenarios will be detailed prior to commencing implementation. Collaborate with stakeholders to detail only
+ those that are prioritized for implementation in the next iteration or two (see <a class="elementLinkWithType"
+ href="./../../opn.swd.prac.legacy_pm/workproducts/iteration_plan_B46FED39.html"
+ guid="_0aQBEslgEdmt3adZL5Dmdw">Artifact: Iteration Plan</a>), or those that are deemed architecturally significant (see
+ <a class="elementLinkWithType"
+ href="./../../core.tech.slot.base/guidances/concepts/architecturally_significant_requirements_1EE5D757.html"
+ guid="_HrZGIA4MEduibvKwrGxWxA">Concept: Architecturally Significant Requirements</a>).
+</p>
+<p>
+ The level of detail captured will vary depending upon the needs of the project and the complexity of the use case. For
+ a discussion of the different levels of detail that may be applicable see <a class="elementLinkWithType"
+ href="./../../opn.tech.prac.rqmts_with_use_cases/guidances/guidelines/use_case_formats_FF4AE425.html"
+ guid="_qq0GMAXkEduj_7BEUj1JfQ">Guideline: *Use Case Formats</a>.
+</p>
+<p>
+ Capture the use-case details in <a class="elementLinkWithType"
+ href="./../../core.tech.common.base/workproducts/use_case_22BE66E2.html" guid="_0VGbUMlgEdmt3adZL5Dmdw">Artifact:
+ ***Use Case</a>. For additional information on detailing use cases and scenarios, see <a class="elementLinkWithType"
+ href="./../../opn.tech.prac.rqmts_with_use_cases/guidances/guidelines/detail_ucs_and_scenarios_6BC56BB7.html"
+ guid="_4BJ_YCxSEdqjsdw1QLH_6Q">Guideline: ***Detail Use Cases and Scenarios</a>. For assistance in assessing the
+ quality of the use cases see <a class="elementLinkWithType"
+ href="./../../opn.tech.prac.rqmts_with_use_cases/guidances/checklists/use_case_C5362874.html"
+ guid="_0kNwINk1Edq2Q8qZoWbvGA">Checklist: *Use Case</a>.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_B47VwCxTEdqjsdw1QLH_6Q" name="Detail System-Wide Requirements "
+ guid="_B47VwCxTEdqjsdw1QLH_6Q">
+ <sectionDescription><p>
+ Some <a class="elementLink" href="./../../core.tech.common.base/workproducts/system_wide_requirements_7D9DD47C.html"
+ guid="_BVh9cL-CEdqb7N6KIeDL8Q">** System-Wide Requirements</a> may need to be clarified or described in more detail,
+ new requirements&nbsp;may have been discovered as we detailed the use cases and scenarios, and new requirements may
+ have been submitted as <a class="elementLink"
+ href="./../../opn.swd.prac.legacy_pm/guidances/concepts/change_requests_AD4868FE.html"
+ guid="_6jdvECb3Edqh1LYUOGRh2A">Change Requests</a>. Collaborate with stakeholders to capture, refine and validate those
+ requirements that will have an impact on near term work (see <a class="elementLinkWithType"
+ href="./../../opn.swd.prac.legacy_pm/workproducts/iteration_plan_B46FED39.html"
+ guid="_0aQBEslgEdmt3adZL5Dmdw">Artifact: Iteration Plan</a>) or are deemed architecturally significant (see <a
+ class="elementLinkWithType"
+ href="./../../core.tech.slot.base/guidances/concepts/architecturally_significant_requirements_1EE5D757.html"
+ guid="_HrZGIA4MEduibvKwrGxWxA">Concept: Architecturally Significant Requirements</a>).
+</p>
+<p>
+ Capture these requirements in the <a class="elementLinkWithType"
+ href="./../../core.tech.common.base/workproducts/system_wide_requirements_7D9DD47C.html"
+ guid="_BVh9cL-CEdqb7N6KIeDL8Q">Artifact: ** System-Wide Requirements</a>.&nbsp; For additional guidance on detailing
+ supporting requirements see <a class="elementLinkWithType"
+ href="./../../opn.tech.prac.rqmts_with_use_cases/guidances/guidelines/system_wide_requirements_8ED0BB6B.html"
+ guid="_wr24gNcGEdqz_d2XWoVt6Q">Guideline: *System-Wide Requirements</a>. For assistance in assessing the quality of
+ your supporting requirements see <a class="elementLinkWithType"
+ href="./../../core.tech.slot.base/guidances/checklists/non_functional_or_system_wide_requirements_renamed_3158BF2F.html"
+ guid="_Vael8CGMEdu3VKXZx45D3A">Checklist: *Non-Functional or System-Wide Requirements</a>.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_2389cOz2Edq2wJOsmRwmhg" name="Detail Glossary terms" guid="_2389cOz2Edq2wJOsmRwmhg">
+ <sectionDescription>Review the flow of the use case or scenario. If information is exchanged, be specific about what is passed back and forth.
+Collaborate with stakeholders to ensure that you define newly discovered domain terms, or ambiguous terms properly in the
+<a class="elementLink" href="./../../core.gen.common.base/workproducts/glossary_5D300778.html"
+guid="_Wn7HcNcEEdqz_d2XWoVt6Q">*Glossary</a>. If your understanding of the domain has improved, refine existing glossary
+terms.</sectionDescription>
+ </sections>
+ <sections xmi:id="_BYbboN-bEdqiM_wFaqLjNg" name="Achieve concurrence" guid="_BYbboN-bEdqiM_wFaqLjNg">
+ <sectionDescription><p>
+ Conduct a review&nbsp;of the&nbsp;requirements (<a class="elementLinkWithType"
+ href="./../../core.tech.common.base/workproducts/use_case_22BE66E2.html" guid="_0VGbUMlgEdmt3adZL5Dmdw">Artifact:
+ ***Use Case</a> and <a class="elementLinkWithType"
+ href="./../../core.tech.common.base/workproducts/system_wide_requirements_7D9DD47C.html"
+ guid="_BVh9cL-CEdqb7N6KIeDL8Q">Artifact: ** System-Wide Requirements</a>)&nbsp;with relevant&nbsp;<a
+ class="elementLinkWithUserText" href="./../../opn.tech.roles.openup_role_defs/roles/stakeholder_9FFD4106.html"
+ guid="_dTa6gMAYEdqX-s4mWhkyqQ">Stakeholders</a> and the development team to ensure consistency with the <a
+ class="elementLink" href="./../../core.tech.common.base/workproducts/vision_2E71B03C.html"
+ guid="_0WVxcMlgEdmt3adZL5Dmdw">** Vision</a>, assess quality, and identify required changes. See&nbsp;<a
+ class="elementLinkWithType"
+ href="./../../opn.tech.prac.basic_tech_rqmts_def/guidances/guidelines/effective_req_reviews_5913D369.html"
+ guid="_E-dPIL-GEdqb7N6KIeDL8Q">Guideline: *Effective Requirement Reviews</a>&nbsp;for more information.
+</p></sectionDescription>
+ </sections>
+ <keyConsiderations>To avoid unnecessary rework, only those requirements that are scheduled for implementation in the near term (in the next
+iteration or two) should be detailed.</keyConsiderations>
+ <purpose>The purpose of this task is to describe one or more requirements in sufficient detail to validate understanding of the
+requirement, to ensure concurrence with stakeholder expectations, and to permit software development to begin.</purpose>
+</org.eclipse.epf.uma:TaskDescription>
diff --git a/praclib/temp/obsoleted_from_openup/workproducts/status_assessment.xmi b/praclib/temp/obsoleted_from_openup/workproducts/status_assessment.xmi
new file mode 100644
index 0000000..e37d99e
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/workproducts/status_assessment.xmi
@@ -0,0 +1,20 @@
+<?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="_K-e8IKX4EdmvhNXG0Oc2uA"
+ name="status_assessment,_0bA2EMlgEdmt3adZL5Dmdw" guid="_K-e8IKX4EdmvhNXG0Oc2uA"
+ changeDate="2006-11-01T15:32:14.824-0800" version="1.0.0">
+ <purpose><p>
+ Capture and communicate whether the project is on track, requires corrective actions, and whether there are
+ opportunities for improvement.
+</p></purpose>
+ <impactOfNotHaving>The team may not understand whether they are on track or not, and whether established iteration objectives and evaluation
+criteria are met. The team may not be able to improve the way they develop software.</impactOfNotHaving>
+ <representationOptions><p>
+ The format of the status assessment varies from one&nbsp;project to another. It can be the minutes of an assessment
+ meeting, an update to a web site, or just an email. The important thing&nbsp;is to effectively communicate&nbsp;to all
+ involved parties whether iteration objectives and evaluation criteria were addressed, and what improvements are
+ needed&nbsp;to the way the team is working.
+</p></representationOptions>
+</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/praclib/temp/obsoleted_from_openup/workproducts/supporting_requirements_intent_req.xmi b/praclib/temp/obsoleted_from_openup/workproducts/supporting_requirements_intent_req.xmi
new file mode 100644
index 0000000..2445a43
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/workproducts/supporting_requirements_intent_req.xmi
@@ -0,0 +1,21 @@
+<?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="-SUqkkwrs1D_5YXZls-3YBg"
+ name=",_oclg0DRXEdudA-StyUUwnw" guid="-SUqkkwrs1D_5YXZls-3YBg" changeDate="2006-09-14T06:34:35.021-0700">
+ <representationOptions><h4>
+ Recommendation: Use the Supporting Requirements Specification Template
+</h4>
+<p>
+ <a class="elementLinkWithType"
+ href="./../../openup_basic/guidances/templates/supporting_requirements_spec,_ItYXcNa9Edqrw4BYKyYKiA.html"
+ guid="_ItYXcNa9Edqrw4BYKyYKiA">Template: Supporting Requirements Specification</a>&nbsp;provides a tool to capture,
+ structure, and organize the supporting requirements.
+</p>
+<p>
+ Even in a small project, a requirements management tool, a database, or a spreadsheet, are recommended for prioritizing
+ and managing requirements. If Stakeholders are comfortable with accessing requirements directly from that tool or with
+ accessing a report automatically generated from the tool, you will not need a separate document.
+</p></representationOptions>
+</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/praclib/temp/obsoleted_from_openup/workproducts/uc_model_intent_req_ucm.xmi b/praclib/temp/obsoleted_from_openup/workproducts/uc_model_intent_req_ucm.xmi
new file mode 100644
index 0000000..1278902
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/workproducts/uc_model_intent_req_ucm.xmi
@@ -0,0 +1,21 @@
+<?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="_zHZW9KYSEdmvhNXG0Oc2uA"
+ name="uc_model,_0UCrZclgEdmt3adZL5Dmdw" guid="_zHZW9KYSEdmvhNXG0Oc2uA" changeDate="2006-12-21T09:42:02.273-0800"
+ version="1.0.0">
+ <purpose><p>
+ This artifact presents an overview of the system's intended behavior.&nbsp; It&nbsp;is the basis for agreement
+ between&nbsp;stakeholders and the project team regarding the intended functionality for the system. It also helps to
+ guide the various tasks in the software development lifecycle.
+</p></purpose>
+ <representationOptions><p>
+ Tailor this artifact to support the project team's needs.
+</p>
+<p>
+ Representation options include: reports and diagrams from UML modeling tools, graphical representations created using
+ drawing tools, drawings on whiteboards. Most of the information in the use-case model is captured in the use-case
+ specifications.
+</p></representationOptions>
+</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/praclib/temp/obsoleted_from_openup/workproducts/use_case_intent_req.xmi b/praclib/temp/obsoleted_from_openup/workproducts/use_case_intent_req.xmi
new file mode 100644
index 0000000..eac92c0
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/workproducts/use_case_intent_req.xmi
@@ -0,0 +1,15 @@
+<?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="-JcGDIeBIMM099mbWX5fXbA"
+ name=",_qis78DRbEduFvfVCXiK3AA" guid="-JcGDIeBIMM099mbWX5fXbA" changeDate="2006-09-14T06:30:41.163-0700">
+ <representationOptions><p>
+ Some projects apply Use Cases informally to help discover requirements, documenting and maintaining these requirements
+ in another form such as user stories. How you tailor Use Cases may depend on project size, team experience, your tool
+ set, the customer relationship, and so forth. See <a class="elementLinkWithType"
+ href="./../../opn.tech.prac.rqmts_with_use_cases/guidances/guidelines/detail_ucs_and_scenarios_6BC56BB7.html"
+ guid="_4BJ_YCxSEdqjsdw1QLH_6Q">Guideline: ***Detail Use Cases and Scenarios</a>&nbsp;for guidance related to
+ documenting Use Cases.
+</p></representationOptions>
+</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/praclib/temp/obsoleted_from_openup/workproducts/work_items_list_pm.xmi b/praclib/temp/obsoleted_from_openup/workproducts/work_items_list_pm.xmi
new file mode 100644
index 0000000..04da433
--- /dev/null
+++ b/praclib/temp/obsoleted_from_openup/workproducts/work_items_list_pm.xmi
@@ -0,0 +1,11 @@
+<?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="-fDVhZTkf1TqDyExbI9DM-w"
+ name=",_sNoQ0Dn6Edu_y4hBImiwwQ" guid="-fDVhZTkf1TqDyExbI9DM-w" changeDate="2006-09-07T17:41:14.873-0400"
+ version="7.2.0">
+ <mainDescription><p>
+ Work Items should contain estimates, see <a class="elementLinkWithType" href="./../../openup/guidances/guidelines/work_items_list_32AC6ABD.html" guid="_7vEXEMA4EdqSgKaj2SZBmg">Guideline: Managing Work Items</a>&nbsp;and <a class="elementLinkWithType" href="./../../openup/guidances/guidelines/agile_estimation_A4EF42B3.html" guid="_CGHskBEdEdqY7JB6N6CW2w">Guideline: Agile Estimation</a>.
+</p></mainDescription>
+</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.assign/.project b/praclib/temp/practice.mgmt.iterative_dev.assign/.project
new file mode 100644
index 0000000..b7855cf
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.assign/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>practice.mgmt.iterative_dev.assign</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.assign/plugin.xmi b/praclib/temp/practice.mgmt.iterative_dev.assign/plugin.xmi
new file mode 100644
index 0000000..00b6ea4
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.assign/plugin.xmi
@@ -0,0 +1,114 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_iNwFwMhNEdygFZkm1d5NtQ"
+ guid="_iNwFwMhNEdygFZkm1d5NtQ"/>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_iNwFsMhNEdygFZkm1d5NtQ" name="practice.mgmt.iterative_dev.assign"
+ guid="_iNwFsMhNEdygFZkm1d5NtQ">
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iNwFschNEdygFZkm1d5NtQ"
+ name="Content" guid="_iNwFschNEdygFZkm1d5NtQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iNwFsshNEdygFZkm1d5NtQ"
+ name="Categories" guid="_iNwFsshNEdygFZkm1d5NtQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iNwFs8hNEdygFZkm1d5NtQ"
+ name="Domains" guid="_iNwFs8hNEdygFZkm1d5NtQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:Domain" xmi:id="_9LmzQMhNEdygFZkm1d5NtQ"
+ name="project_management_domain.assign" guid="_9LmzQMhNEdygFZkm1d5NtQ"
+ variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Domain" href="uma://_MRPloEFXEdy9ENCpSugIjA#_8M6J4K80Edy9cPK11VzBuQ"/>
+ <workProducts xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_0aQBEslgEdmt3adZL5Dmdw"/>
+ <workProducts xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_Ckay8Cc_EduIsqH1Q6ZuqA"/>
+ <workProducts xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_rGNWsCbSEdqh1LYUOGRh2A"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iNwFtMhNEdygFZkm1d5NtQ"
+ name="Disciplines" guid="_iNwFtMhNEdygFZkm1d5NtQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:Discipline" xmi:id="_qc9i0MhNEdygFZkm1d5NtQ"
+ name="project_management_discipline.assign" guid="_qc9i0MhNEdygFZkm1d5NtQ"
+ variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Discipline" href="uma://_MRPloEFXEdy9ENCpSugIjA#_iGSHtFZ-EdyIUdvDLLUdeg"/>
+ <tasks href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_0l53cMlgEdmt3adZL5Dmdw"/>
+ <tasks href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_8S2aICbYEdqh1LYUOGRh2A"/>
+ <tasks href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_0keUEMlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Discipline" xmi:id="_sewB4OPMEdygc55Ul2bjdw"
+ name="configuration_and_change_management_discipline.assign" guid="_sewB4OPMEdygc55Ul2bjdw"
+ variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Discipline" href="uma://_MRPloEFXEdy9ENCpSugIjA#_iGSHslZ-EdyIUdvDLLUdeg"/>
+ <tasks href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_0mwzEclgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iNwFtchNEdygFZkm1d5NtQ"
+ name="RoleSets" guid="_iNwFtchNEdygFZkm1d5NtQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iNwFtshNEdygFZkm1d5NtQ"
+ name="WP Types" guid="_iNwFtshNEdygFZkm1d5NtQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iNwFt8hNEdygFZkm1d5NtQ"
+ name="Tools" guid="_iNwFt8hNEdygFZkm1d5NtQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iNwFuMhNEdygFZkm1d5NtQ"
+ name="StandardCategories" guid="_iNwFuMhNEdygFZkm1d5NtQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iNwFuchNEdygFZkm1d5NtQ"
+ name="CustomCategories" guid="_iNwFuchNEdygFZkm1d5NtQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iNwFushNEdygFZkm1d5NtQ"
+ name="Hidden" guid="_iNwFushNEdygFZkm1d5NtQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_iNwFu8hNEdygFZkm1d5NtQ"
+ name="Custom Categories" guid="_iNwFu8hNEdygFZkm1d5NtQ"/>
+ </childPackages>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iNwFvMhNEdygFZkm1d5NtQ"
+ name="CoreContent" guid="_iNwFvMhNEdygFZkm1d5NtQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_lUsBcMhNEdygFZkm1d5NtQ"
+ name="Role Assignments" guid="_lUsBcMhNEdygFZkm1d5NtQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:Role" xmi:id="_KIHF8MhOEdygFZkm1d5NtQ"
+ name="project_manager.assign_wp" guid="_KIHF8MhOEdygFZkm1d5NtQ" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Role" href="uma://_A118oMYaEdyXeo04os5BOw#_0a0o0MlgEdmt3adZL5Dmdw"/>
+ <responsibleFor xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_0aQBEslgEdmt3adZL5Dmdw"/>
+ <responsibleFor xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_Ckay8Cc_EduIsqH1Q6ZuqA"/>
+ <responsibleFor xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_rGNWsCbSEdqh1LYUOGRh2A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_skSmQMhOEdygFZkm1d5NtQ"
+ name="assess_results.assign_role" guid="_skSmQMhOEdygFZkm1d5NtQ" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Task" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_0l53cMlgEdmt3adZL5Dmdw"/>
+ <performedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0a0o0MlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0VxJsMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0X9iEMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_dTa6gMAYEdqX-s4mWhkyqQ"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0ZM4MclgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_54V2QMhOEdygFZkm1d5NtQ"
+ name="manage_iteration.assign_role" guid="_54V2QMhOEdygFZkm1d5NtQ" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Task" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_8S2aICbYEdqh1LYUOGRh2A"/>
+ <performedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0a0o0MlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0VxJsMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0X9iEMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_dTa6gMAYEdqX-s4mWhkyqQ"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0ZM4MclgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_EO2XEMhPEdygFZkm1d5NtQ"
+ name="plan_iteration.assign_role" guid="_EO2XEMhPEdygFZkm1d5NtQ" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Task" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_0keUEMlgEdmt3adZL5Dmdw"/>
+ <performedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0a0o0MlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0VxJsMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0X9iEMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_dTa6gMAYEdqX-s4mWhkyqQ"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0ZM4MclgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_iNwFvchNEdygFZkm1d5NtQ"
+ name="CapabilityPatterns" guid="_iNwFvchNEdygFZkm1d5NtQ"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_iNwFvshNEdygFZkm1d5NtQ"
+ name="DeliveryProcesses" guid="_iNwFvshNEdygFZkm1d5NtQ"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_iNwFv8hNEdygFZkm1d5NtQ"
+ name="ProcessContributions" guid="_iNwFv8hNEdygFZkm1d5NtQ"/>
+ <bases href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPloEFXEdy9ENCpSugIjA"/>
+ <bases href="uma://_A118oMYaEdyXeo04os5BOw#_A118oMYaEdyXeo04os5BOw"/>
+ <bases href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzAJ6WEdyQN-zRFaRrCQ"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/.project b/praclib/temp/practice.mgmt.iterative_dev.base/.project
new file mode 100644
index 0000000..4abce53
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>practice.mgmt.iterative_dev.base</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/iterative_dev_practice.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/iterative_dev_practice.xmi
new file mode 100644
index 0000000..ade0ed8
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/iterative_dev_practice.xmi
@@ -0,0 +1,60 @@
+<?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: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="-Godh4yG8PB3TBqovJQY9SQ"
+ name="iterative_dev_practice,_1pc5QJ-kEdyBk-WQzMU-FQ" guid="-Godh4yG8PB3TBqovJQY9SQ"
+ changeDate="2008-02-24T15:18:21.875-0500">
+ <mainDescription><p>
+ The&nbsp;Iterative Development&nbsp;practice&nbsp; [***.......TO BE COMPLETED ***]
+</p>
+<h3>
+ The Essence of Iterative Development
+</h3>
+<p>
+ The following capture the key principles of Iterative Development: [***.......TO BE COMPLETED ***]
+</p>
+<ul>
+ <li>
+ <strong>Micro-incroments.</strong>
+ </li>
+ <li>
+ <strong>Retrospective.</strong>
+ </li>
+</ul>
+<h3>
+ <br />
+ Why Adopt this Practice?
+</h3>
+<p>
+ [*** Include some content here that describes the business value of this practice -- what do you get when you adopt
+ it?&nbsp; This section is essentially the value proposition for the practice.&nbsp; You may want to describe some
+ common problems and how this practice solves those problems.&nbsp; &nbsp;***]&nbsp;&nbsp;&nbsp;
+</p>
+<h3>
+ How to Read this Practice
+</h3>
+<p>
+ The best way to read this practice is to first familiarize yourself with its overall structure -- what it is in it and
+ how it is organized.&nbsp;
+</p>
+<p>
+ [*** To be completed.... ***]
+</p>
+<p>
+ For step-by-step instructions on how to adopt this practice, see <a class="elementLink"
+ href="./../../practice.mgmt.iterative_dev.base/guidances/roadmaps/how_to_adopt_85BF1B9B.html"
+ guid="_bpWt8OMPEdyM47cGD2jiaQ">How to Adopt This Practice</a>.
+</p>
+<h3>
+ Additional Resources
+</h3>
+<p>
+ For more information on the whole team approach, see the following:
+</p>
+<ul>
+ <li>
+ [*** Add more, as needed ***]<br />
+ </li>
+</ul></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/bookc.gif b/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/bookc.gif
new file mode 100644
index 0000000..7f2ab85
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/bookc.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/bookcL.gif b/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/bookcL.gif
new file mode 100644
index 0000000..6c5b064
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/bookcL.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/compass.gif b/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/compass.gif
new file mode 100644
index 0000000..39f306a
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/compass.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/compassL.gif b/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/compassL.gif
new file mode 100644
index 0000000..4117414
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/compassL.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/guide_dgm32.gif b/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/guide_dgm32.gif
new file mode 100644
index 0000000..5a9f688
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/guide_dgm32.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/pract_dgm32.gif b/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/pract_dgm32.gif
new file mode 100644
index 0000000..f597332
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/pract_dgm32.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/pract_obj.gif b/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/pract_obj.gif
new file mode 100644
index 0000000..fe8075a
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/pract_obj.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/report_dgm32.gif b/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/report_dgm32.gif
new file mode 100644
index 0000000..1f86c7e
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/report_dgm32.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/report_obj.gif b/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/report_obj.gif
new file mode 100644
index 0000000..c22c85e
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/report_obj.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/task_dgm32.gif b/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/task_dgm32.gif
new file mode 100644
index 0000000..a91ea1c
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/task_dgm32.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/task_obj.gif b/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/task_obj.gif
new file mode 100644
index 0000000..7633d58
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/task_obj.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/template_dgm32.gif b/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/template_dgm32.gif
new file mode 100644
index 0000000..8fab4e8
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/template_dgm32.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/template_obj.gif b/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/template_obj.gif
new file mode 100644
index 0000000..ca5f822
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/template_obj.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/workproduct_dgm32.gif b/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/workproduct_dgm32.gif
new file mode 100644
index 0000000..009c9af
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/workproduct_dgm32.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/workproduct_obj.gif b/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/workproduct_obj.gif
new file mode 100644
index 0000000..3e58c6f
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/customcategories/resources/workproduct_obj.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/checklists/iteration_plan.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/checklists/iteration_plan.xmi
new file mode 100644
index 0000000..b9fd4cc
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/checklists/iteration_plan.xmi
@@ -0,0 +1,32 @@
+<?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="-z4NERMW6W4_X_5DuTTXv6A"
+ name="new_checklist,_OHRDMAarEdy1uLAzgK8btg" guid="-z4NERMW6W4_X_5DuTTXv6A">
+ <sections xmi:id="_EQJdAAa_Edy1uLAzgK8btg" name="Have you elaborated on the plan with the team?"
+ guid="_EQJdAAa_Edy1uLAzgK8btg">
+ <sectionDescription><p> Iteration planning should not be done in isolation, and every member of the 
+ team should be involved. </p></sectionDescription>
+ </sections>
+ <sections xmi:id="_lmIhYAarEdy1uLAzgK8btg" name="Are iteration objectives clear?"
+ guid="_lmIhYAarEdy1uLAzgK8btg">
+ <sectionDescription><ul>
+ <li> Are the objectives based on stakeholder priorities? </li>
+ <li> Do they help the team target what should be targeted for the iteration? 
+ </li>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_i2r4kAarEdy1uLAzgK8btg" name="Have key milestones for the iteration been identified?"
+ guid="_i2r4kAarEdy1uLAzgK8btg">
+ <sectionDescription><p>
+ This may include dates for iteration reviews, demonstrations (demos), and retrospective reviews.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_oKlbIAarEdy1uLAzgK8btg" name="Do the team members feel confident about their Work Item assignments?"
+ guid="_oKlbIAarEdy1uLAzgK8btg">
+ <sectionDescription><p align="left"> Looking at results from previous iterations, does the amount 
+ of work selected for current iteration seem feasible? </p>
+<p align="left"> If the team feels there's too much to do, discuss with stakeholders 
+ whether some Work Items can be scheduled for future iterations. </p></sectionDescription>
+ </sections>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/checklists/work_items_list.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/checklists/work_items_list.xmi
new file mode 100644
index 0000000..bfa5e36
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/checklists/work_items_list.xmi
@@ -0,0 +1,36 @@
+<?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="-BTXdT-1bO6nbAPf25q0_yA"
+ name="new_checklist,_xlrdEAVtEdy3F_fZDaPZVA" guid="-BTXdT-1bO6nbAPf25q0_yA" version="7.2.0">
+ <sections xmi:id="_U7JSUAbNEdy1uLAzgK8btg" name="Have Work Items been described without ambiguity?"
+ guid="_U7JSUAbNEdy1uLAzgK8btg">
+ <sectionDescription><p> Does each Work Item have a name and clear description? This helps the team 
+ estimate Work Item size. If necessary, include links on the Work Items List 
+ to reference material where further detail is available. </p></sectionDescription>
+ </sections>
+ <sections xmi:id="_dL2nwAVuEdy3F_fZDaPZVA" name="Have Work Items been prioritized?"
+ guid="_dL2nwAVuEdy3F_fZDaPZVA">
+ <sectionDescription><p align="left"> Has every Work Item been prioritized by business value? This 
+ helps the team select the Work Items to be delivered in each iteration. </p></sectionDescription>
+ </sections>
+ <sections xmi:id="_bF3LoAVuEdy3F_fZDaPZVA" name="Have Work Items been estimated?"
+ guid="_bF3LoAVuEdy3F_fZDaPZVA">
+ <sectionDescription><p align="left"> Every Work Item should be estimated by business value. This will 
+ help the team to select the Work Items to be delivered in each iteration. </p></sectionDescription>
+ </sections>
+ <sections xmi:id="_O7VloAbFEdy1uLAzgK8btg" name="Are the Work Items being tracked?"
+ guid="_O7VloAbFEdy1uLAzgK8btg">
+ <sectionDescription><p align="left"> Does every Work Item have a state attribute? This helps the team 
+ track its development project.&nbsp; </p></sectionDescription>
+ </sections>
+ <sections xmi:id="_tENnkAVuEdy3F_fZDaPZVA" name="Are scheduled Work Items the right size?"
+ guid="_tENnkAVuEdy3F_fZDaPZVA">
+ <sectionDescription>If a Work Item is scheduled for an iteration, then it should be broken down into Work Items that can be completed in a
+reasonable timeframe (a few hours, to a few days). This will help&nbsp;the team be more productive and produce&nbsp;more
+detailed effort estimates, see <a class="elementLink" href="./../../../practice.mgmt.iterative_dev.base/guidances/concepts/micro_increments.html"
+guid="_S80VwCNbEdyCq8v2ZO4QcA" >Micro-Increments</a>. <br align="left" />
+<br /></sectionDescription>
+ </sections>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/concepts/iteration_lifecycle.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/concepts/iteration_lifecycle.xmi
new file mode 100644
index 0000000..d733f2c
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/concepts/iteration_lifecycle.xmi
@@ -0,0 +1,72 @@
+<?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="-5xbLr54QjpynnPU8ZJ3_fw"
+ name="new_concept,_DI_tICNaEdyCq8v2ZO4QcA" guid="-5xbLr54QjpynnPU8ZJ3_fw" changeDate="2007-07-22T19:30:20.319-0400">
+ <mainDescription><p>
+ Iterations in OpenUP keep the team focused on delivering incremental customer value every few weeks by delivering a
+ fully tested demo-able or shippable build (product increment). This creates a healthy focus on ensuring that whatever
+ is worked on is of value to the stakeholders. Decision making must to happen faster since there is no time for endless
+ debate. Iterative development focuses on producing working code reducing the risk of analysis-paralysis. Frequent
+ demonstration of working code provides feedback mechanisms that allow course corrections to be taken as needed.
+</p>
+<p>
+ Iteration planning, estimation, and progress tracking are centered on work items. The iteration plan is created by
+ selecting the top-priority work items. Agile estimation techniques are used to understand how many work items can
+ safely fit within the time-boxed iteration, and work items are filtered to ensure that the chosen work items will allow
+ the team to deliver upon iteration objectives agreed to by stakeholders. Progress is demonstrated through continuous
+ completion of many small work items (see <a class="elementLink"
+ href="./../../../openup/guidances/concepts/micro_increments.html" guid="_S80VwCNbEdyCq8v2ZO4QcA">Micro-Increments</a>).
+</p>
+<p>
+ Just as a project goes through a lifecycle, iterations go through a lifecycle with a different focus for the team
+ depending on whether you are in the first versus the last week of the iteration, see Figure below and <a
+ class="elementlinkwithusertext" href="./../../../openup/guidances/supportingmaterials/references.html#JAZZ"
+ guid="_9ToeIB83Edqsvps02rpOOg">[JAZZ]</a>. An iteration starts with an iteration planning meeting that is a few hours
+ long. The initial one or two days are typically focused on further planning and architecture to, among other things,
+ understand the dependencies and logical ordering of work items, and architectural impacts of the work to be done. Most
+ of the time during an iteration is spent on executing the micro increments. Each micro increment should deliver tested
+ code to a build, as well as validated artifacts. To give additional discipline, stable builds are produced at the end
+ of each week. More attention is spent on these builds to make sure that the quality is not eroding and issues are dealt
+ with early so the success of the iteration isn’t jeopardized. The last week or last few days of the iteration typically
+ have a stronger emphasis on polishing and bug fixing than earlier weeks, even though new features are added as
+ appropriate. The goal is to never let quality erode, thus ensuring&nbsp;that a high-quality useful product increment is
+ produced at the end of the iteration. The iteration ends with an assessment (with stakeholders) of what was built, and
+ a retrospective to understand how to improve the process for next iteration.
+</p>
+<p>
+ <img
+ alt="Picture shows an iteration that starts with a planning meeting, has stable weekly builds, and ends with an iteration review."
+ src="./resources/iteration_lifecycle.jpg" />
+</p>
+<p>
+ <em>An iteration goes through a lifecycle with a stronger focus on planning and architecture early-on and a stronger
+ focus on bug-fixing and stabilization toward the end.</em>
+</p>
+<p>
+ Team members work more effectively if they can influence what they do and how they do it, rather than operating in an
+ environment where they are told what to do. Giving the team the ability and responsibility to organize their work and
+ determine how to best meet their commitments motivates team members to do their best. This also helps them collaborate
+ to ensure that the right skills are applied to the appropriate tasks. Self organization impacts many areas, including
+ how planning and commitments are made (by a team, not by individuals), how work is assigned (you sign up versus get
+ assigned), and how team members view their role in the project (team member first, job function second).
+</p>
+<p>
+ <a class="elementLinkWithUserText" href="./../../../openup/guidances/guidelines/self_organize_work_assignments.html"
+ guid="_rmBEkJjsEduad8I_c-ogIA">Self organization</a>&nbsp;requires a few things to work:
+</p>
+<ul>
+ <li>
+ Transparency and commitments are crucial to aid in team communication and to bring out the best in the team
+ members. Open communication about the team’s commitments related to the iteration lifecycle, and personal
+ commitments made relative to micro increments ensure that execution problems are vetted and the right people are
+ focused on solving them.
+ </li>
+ <li>
+ Coaching is required to help teams self organize and to remove barriers for success. The assumption is that the
+ project manager is the coach. This requires that the project manager avoid a command-and-control style of
+ management in favor of a coaching style. This has been a key recommendation in management books for the last two
+ decades, but some project managers may still not be able to make that transition.
+ </li>
+</ul></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/concepts/micro_increments.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/concepts/micro_increments.xmi
new file mode 100644
index 0000000..0893d28
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/concepts/micro_increments.xmi
@@ -0,0 +1,77 @@
+<?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: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="-vysTxqikgsqd3pYIkSofjg"
+ name="new_concept,_S80VwCNbEdyCq8v2ZO4QcA" guid="-vysTxqikgsqd3pYIkSofjg" changeDate="2008-02-22T10:26:49.500-0500"
+ version="7.2.0">
+ <mainDescription><p>
+ <strong>[*** To Fix:&nbsp; If this content is to remain in this practice, it needs to remove the references to
+ OpenUP.&nbsp; If you want to keep it OpenUP-specific, then it needs to move to the publish.openup plug-in.&nbsp; Also,
+ need to fix the reference to Project Lifecycle...it can't be made from here with the current construction.&nbsp; Maybe
+ a new Concept: Project Lifecycle that is independent of Unified Process lifecycle terminology needs to be
+ created&nbsp;(maybe it should be in common) and that concept referenced from here. ***]</strong>
+</p>
+<p>
+ Personal contribution on an OpenUP project is organized in <strong>micro-increments</strong>. A micro-increment
+ represents the outcome of a few hours to a few days of work for one, or typically a few people collaborating to reach
+ the goals of the iteration. The concept of a micro-increment helps the individual team member to partition their work
+ into small units that each delivers something of measurable value to the team. Micro-increments provide an extremely
+ short feedback loop that drives adaptive decisions within each iteration.
+</p>
+<p>
+ A micro-increment should be well defined, and you should be able to track daily progress of each micro-increment.
+ Micro-increments are specified and tracked by a work item. Change sets represent the physical outcome in terms of the
+ files are modified as a part of completing the work item. Let’s have a look at some sample micro-increments:
+</p>
+<ul>
+ <li>
+ <em>Identify Stakeholders.</em> Defining the Vision is a task that can drag on for weeks, so to ensure that you
+ make and track daily progress, divide the task into small and well-defined micro-increments. Describing and getting
+ buy-in on what Stakeholders to put into a Vision document is a meaningful result, and may take a few hours, or at
+ most a few days, and thus represents a suitable micro-increment.
+ </li>
+ <li>
+ <em>Develop Solution Increment.</em> Defining, designing, implementing, and testing a use case or even a scenario
+ can take weeks or longer. To ensure continuous progress, we seek to divide the work into smaller increments, each
+ of which can be done in a couple of days. A more suitable micro-increment may be to only define, design, implement,
+ and test a subflow of a use-case or step within a scenario.
+ </li>
+ <li>
+ <em>Agree on Technical Approach for Persistency.</em> Agreeing on your technical solution may take quite some time,
+ so we need to narrow the task to something that can be defined and agreed to in a short time. One way to partition
+ the work is according to the issues you need to resolve, such as persistency or reporting. This micro-increment
+ will probably involve defining requirements, surveying available assets, prototyping, and documentating the
+ decisions.
+ </li>
+ <li>
+ <em>Plan Iteration.</em> This micro-increment could include setting up a meeting for creating the iteration plan,
+ doing some preparation for the meeting, such as reviewing candidate work items, coaching the team through the
+ iteration planning meeting, and posting the iteration plan for easy access. The end result is something complete
+ and measurable, a posted plan that has buy-in from the team.
+ </li>
+</ul>
+<p>
+ Your application evolves in micro-increments through simultaneous execution of a number of work items. By openly
+ sharing progress on your micro-increments through daily team meetings and team collaboration tools, you achieve the
+ transparency and insight into each other’s work required for effective teamwork. At the same time, you demonstrate
+ continuous progress by evolving your application one micro-increment at the time.
+</p>
+<p>
+ OpenUP provides a set of activities. Each activity is captured as a set of tasks, steps within tasks, and guidance.
+ Even thought micro-increments are not an explicit construct in the process, you will find descriptions of how to carry
+ out a set of related micro-increments that are commonly found in projects within the activity. OpenUP does not provide
+ a complete description of potential micro-increments, and each organization should consider adding their own ‘recipes’
+ for commonly occurring micro-increments.
+</p>
+<p>
+ OpenUP provides a powerful learning tool and makes it easier to find relevant guidance by outlining when you are most
+ likely to carry out various tasks. This is done through a visualization of the delivery process which provides a
+ time-based organization of the tasks within the context of a <a class="elementLink"
+ href="./../../../practice.mgmt.risk_value_lifecycle.base/guidances/concepts/project_lifecycle_203F87.html"
+ guid="_nSfVwCNYEdyCq8v2ZO4QcA">Project Lifecycle</a>. As an example, you are more likely to agree on a technical
+ approach early in the project. This doesn’t mean you wouldn’t make technical decisions late in the project. A process
+ is like a map, use it to understand the big picture and as a reference, but when reality and map don’t match, trust
+ reality.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/concepts/resources/iteration_lifecycle.jpg b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/concepts/resources/iteration_lifecycle.jpg
new file mode 100644
index 0000000..da4a55e
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/concepts/resources/iteration_lifecycle.jpg
Binary files differ
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/concepts/retrospective.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/concepts/retrospective.xmi
new file mode 100644
index 0000000..52dd6f0
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/concepts/retrospective.xmi
@@ -0,0 +1,90 @@
+<?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="-ENSD2TqUsFcf3Sf-oeozUA"
+ name="retrospective,_2PfbIA4QEdy2q5zsU8WDnA" guid="-ENSD2TqUsFcf3Sf-oeozUA" changeDate="2007-05-30T09:11:26.048-0700">
+ <mainDescription><p>
+ Retrospectives, as applied in software development, have historical roots in Project Retrospectives described as:
+</p>
+<blockquote>
+ "A ritual held <b>at the end</b> of a project to learn from the experience and plan changes for the next
+ effort." [<a class="elementLinkWithUserText" href="./../../../openup/guidances/supportingmaterials/references_6CCF393.html#KER01" guid="_9ToeIB83Edqsvps02rpOOg">KER01</a>]
+</blockquote>
+<p>
+ While Retrospectives conducted at the end of a project remain valuable, the spirit of Retrospectives should be imbued
+ across the project continuum, conducted at key project milestones: at the end of project iterations, releases, and
+ immediately upon occurrences of key project incidents (significant unexpected events). 
+</p> 
+<p> 
+ When the practice of
+ Retrospectives is intimately intertwined with the processes of the project, the health of the team is constantly
+ monitored, the heartbeat of project progress is readily measured, and the team hones an awareness of opportunities for
+ improvement and increased productivity. A symbiotic relationship emerges between an evolutionary development process
+ and a Retrospective that supports the various methods of inspection and adaptation.
+</p>
+<p>
+ The iteration, incident, and project Retrospectives are designed, in part, to calibrate the team's progress with the
+ goals of the project. Several methods can be used to incite the Retrospective team to begin their collective
+ investigative work, such as posing the following three driving questions to the team: "What worked well for us during
+ the past iteration (or project, and so on)?", "What did not work well for us during the past iteration (or project, and so on)?",
+ and "What should we do differently, or what improvements should we undertake during our next iteration (or project, and so on)". 
+</p> 
+<p> 
+ The questions are expected to generate actions that will assist the team in prioritizing suggested improvements
+ for the project, to be implemented during the subsequent cycle. In addition to the aforementioned investigative
+ questions, a Retrospective should include steps that provide structure for the team's focus and resulting work.
+</p>
+<p>
+ An effectively facilitated Retrospective will create an environment that is conducive to various practices of
+ inspection and adaptation. The methods of inspection and adaptation are project control mechanisms that assume, and
+ respond to, the existence of complexity, unpredictability, and constant change. Practiced in the context of a
+ Retrospective, the methods of inspection and adaptation produce a feedback loop from which flexibility, responsiveness,
+ and reliability are realized.
+</p>
+<p>
+ The mere execution of Retrospectives is insufficient without an organizational commitment to a collaborative culture.
+ The success of Retrospectives is directly proportional to, and necessarily contingent on, an environment that engenders
+ highly motivated and performing teams (not the individual), nurtures open and frequent communication, and a thriving
+ sense of dedication to the team community. Retrospectives embody the spirit of team collaboration and self-reflection
+ by offering an environment in which teams are encouraged to provide feedback and identify lessons learned [<a class="elementLinkWithUserText" href="./../../../openup/guidances/supportingmaterials/references_6CCF393.html#DER06" guid="_9ToeIB83Edqsvps02rpOOg">DER06</a>]. The compositional aspects of the team are crucial in supporting the highly
+ collaborative nature of Retrospectives, enabling the team to produce insight(s) into improving the processes of the
+ project.
+</p>
+<p>
+ The participants that gather in the context of a Retrospective constitute more than a "working group".
+ The participants should be thought of as "a small number of people with complementary skills who are committed to
+ a common purpose, performance goals, and approach for which they hold themselves mutually accountable." [<a class="elementLinkWithUserText" href="./../../../openup/guidances/supportingmaterials/references_6CCF393.html#KAT93" guid="_9ToeIB83Edqsvps02rpOOg">KAT93</a>]
+</p>
+<p>
+ The participants should consist of individuals representing cross-functional groups, having been involved in the
+ project period or project incident for which the Retrospective will be conducted. The size of the team is important,
+ for the rigorously participative environment of the Retrospective may be difficult to achieve with an overwhelmingly
+ large group (25+ individuals), and a time-boxed period in which to conduct the Retrospective. Conversely, a
+ small set of participants that is under-represented by the appropriate functional groups will limit the
+ benefits and productivity of team collaboration and self-organization. Although a Retrospective achieves productive
+ results by actualizing team responsibility, self-organization, and opposing traditional imposing authority, the work
+ conducted in a Retrospective - involving the members of cross-functional groups - demands the presence of a designated
+ facilitator.
+</p>
+<p>
+ The individual that is designated to assume the role of facilitator, or Retrospective leader, should possess
+ fundamental skills of a facilitative management approach:
+</p>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p class="quote">
+ "A facilitator is an individual who enables groups and organizations to work more effectively; to collaborate and
+ achieve synergy. She or he is a "content neutral" party who by not taking sides or expressing or advocating a point
+ of view during the meeting, can advocate for fair, open, and inclusive procedures to accomplish the group's work. A
+ facilitator can also be a learning or dialogue guide to assist a group in thinking deeply about its assumptions,
+ beliefs and values and about its systemic processes and context." [<a class="elementLinkWithUserText" href="./../../../openup/guidances/supportingmaterials/references_6CCF393.html#KAN96" guid="_9ToeIB83Edqsvps02rpOOg">KAN96</a>]
+ </p>
+</blockquote>
+<p>
+ The facilitator can be expected to allow the participants to exercise a sense of ownership in the operating mode of
+ thought, act to remove impediments to the team's effort to reach targeted goals, foster an environment of trust and
+ thriving collaboration, and support the team in a manner that allows the team to achieve its best thinking. Ultimately,
+ the facilitator focuses on managing the format of the Retrospective, while the participants hone their skills in
+ managing the Retrospective content and maintaining a high-performance, participatory group dynamic.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/examples/iteration_burndown_report_example.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/examples/iteration_burndown_report_example.xmi
new file mode 100644
index 0000000..5873c42
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/examples/iteration_burndown_report_example.xmi
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:GuidanceDescription 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="-FNbGVhn2P45T1cT9RvMiGQ"
+ name="new_example,_GtGisDcGEdyTZ9G7ByfQTw" guid="-FNbGVhn2P45T1cT9RvMiGQ">
+ <attachments>../reports/resources/ex_iteration_burndown.xls</attachments>
+</org.eclipse.epf.uma:GuidanceDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/examples/iteration_plan.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/examples/iteration_plan.xmi
new file mode 100644
index 0000000..175f81a
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/examples/iteration_plan.xmi
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:GuidanceDescription 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="-nDr0XNiUWBo6VS1YS6KAqA"
+ name=",_TuNhIEE4EdulKujnGUuxbg" guid="-nDr0XNiUWBo6VS1YS6KAqA" changeDate="2006-09-10T22:11:20.945-0400"
+ version="7.1.0">
+ <mainDescription><p>
+ <a href="./resources/ex_iteration_plan.doc" target="_blank" ></a>&nbsp;
+</p></mainDescription>
+</org.eclipse.epf.uma:GuidanceDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/examples/resources/ex_iteration_plan.doc b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/examples/resources/ex_iteration_plan.doc
new file mode 100644
index 0000000..5802f01
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/examples/resources/ex_iteration_plan.doc
Binary files differ
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/examples/resources/ex_work_items_list.xls b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/examples/resources/ex_work_items_list.xls
new file mode 100644
index 0000000..234f2a5
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/examples/resources/ex_work_items_list.xls
Binary files differ
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/examples/work_items_list.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/examples/work_items_list.xmi
new file mode 100644
index 0000000..c92bf44
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/examples/work_items_list.xmi
@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:GuidanceDescription 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="-qunTPN3vqTIGpELwajXpLA"
+ name="work_items_list,_nHomIDgzEdu4E8ZdmlYjtA" guid="-qunTPN3vqTIGpELwajXpLA"
+ changeDate="2006-08-31T10:50:15.463-0400" version="1.0.0">
+ <mainDescription><a href="./resources/ex_work_items_list.xls" target="_blank" >ex_work_items_list.xls</a></mainDescription>
+</org.eclipse.epf.uma:GuidanceDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/assign_changes_to_iteration.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/assign_changes_to_iteration.xmi
new file mode 100644
index 0000000..8b8ad3a
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/assign_changes_to_iteration.xmi
@@ -0,0 +1,39 @@
+<?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: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="-bUmvEAAtFf6B0aUCux8k9Q"
+ name="changes_at_iter_bound,__yQQ4L6REdqti4GwqTkbsQ" guid="-bUmvEAAtFf6B0aUCux8k9Q"
+ changeDate="2006-09-22T13:37:52.530-0400" version="7.2.0">
+ <mainDescription><p>
+ Most iterative software development processes recommend that changes not be introduced during an iteration. The main
+ idea is that the iterations should be short and with clearly defined scope so that they can be time-boxed.
+</p>
+<p>
+ To limit scope within an iteration, change requests are reviewed and prioritized as soon as possible, but are not
+ assigned for implementation until a future iteration via the <a class="elementLinkWithType"
+ href="./../../../opn.swd.prac.legacy_pm/workproducts/work_items_list_39D03CC8.html"
+ guid="_rGNWsCbSEdqh1LYUOGRh2A">Artifact: Work Items List</a>.
+</p>
+<p>
+ Since iterations are relatively short this should not cause undue delay in dealing with urgent and important change
+ requests.
+</p>
+<p>
+ One notable exception is a defect discovered during testing that prevents the team from meeting the objectives of the
+ iteration. In this case it is reasonable to assign the work item to the current iteration as this does not represent a
+ scope change, it represents unfinished work.
+</p>
+<p>
+ Consider the following when choosing the future iteration where the change request will be addressed:
+</p>
+<ul>
+ <li>
+ Group similar change requests in the same iteration. For example multiple change requests focused on the same
+ functionality or that are dependent on each other.
+ </li>
+ <li>
+ Assign change requests that mitigate high risks to the earliest iteration possible.
+ </li>
+</ul></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/conduct_retrospective.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/conduct_retrospective.xmi
new file mode 100644
index 0000000..f73a313
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/conduct_retrospective.xmi
@@ -0,0 +1,144 @@
+<?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="-i-UeSpBxKd6YtGLz_NW8GQ"
+ name=",_277QEA4gEdy63f1yVoPyfA" guid="-i-UeSpBxKd6YtGLz_NW8GQ" changeDate="2007-06-01T15:50:36.302-0700">
+ <mainDescription><h1> Establish norms and agreements</h1>
+<p> Begin the Project Retrospective by establishing the duration, goals, and expectations 
+ of the session. The following are typical durations for various Retrospectives: 
+</p>
+<ul>
+ 
+ <li><b> Iteration: </b>2 to 4 hours </li>
+ <li><b> Incident: </b>15 to 45 minutes </li>
+ <li> <b>Project: </b>1 to several days </li>
+</ul>
+<p>
+ Select the facilitator of the Retrospective (See <a class="elementLinkWithType" href="./../../../openup/guidances/concepts/retrospective_B003F386.html" guid="_2PfbIA4QEdy2q5zsU8WDnA">Concept: Retrospective</a> for more detail on the facilitator).
+</p>
+<p> If the team is gathering to conduct the first Retrospective, the group will 
+ need to create the cultural norms that will be used in the future Retrospectives. 
+ If the team is regrouping to conduct a Retrospective, the existing cultural 
+ norms will be used. Norm Kerth’s Prime Directive is an excellent and widely 
+ referenced guiding principle for each Retrospective: </p>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ 
+ <p class="quote"> <strong>Prime Directive</strong>: “Regardless of what we discover, we understand 
+ and truly believe that everyone did the best job they could, given what they 
+ knew at the time, their skills and abilities, the resources available, and 
+ the situation at hand.” [<a class="elementLinkWithUserText" href="./../../../openup/guidances/supportingmaterials/references_6CCF393.html#KER01" guid="_9ToeIB83Edqsvps02rpOOg">KER01</a>] 
+ </p>
+</blockquote>
+<p> Remind the team that the Prime Directive and cultural norms of the Retrospective 
+ are in place to establish an environment in which the members can safely expose 
+ sensitive topics and manage meaningful, if provocative, dialogue. The cultural 
+ norms guide the team by a “social contract” that clearly outlines the “team 
+ values and working agreements” that have been established by the team. The social 
+ contract needs to include organizational value statements that govern acceptable 
+ behavior and interactions, supplemented by inviolable principles that govern 
+ the conduct and ethics of the team. The team must establish these rules of group 
+ engagement before the Retrospective continues to the core of the group’s intended 
+ gathering. Examples of working agreements include: tardiness is not acceptable; 
+ mobile phones must be powered off during the session; all participants must 
+ be in attendance throughout the duration of the Retrospective or ask permission 
+ from the group for early departure; all opinions are welcome; the team must 
+ strive for healthy, high-quality interaction. </p>
+<p> The team’s working agreements (and&nbsp;the Prime Directive statement) should 
+ be displayed prominently in the Retrospective session, so that they are clearly 
+ visible to all members of the team and, if required, easily accessible so that 
+ the team can edit the content. After it is defined, future Retrospectives can 
+ begin with a review of these working agreements. </p>
+<p> After the team has established a safe environment in which to conduct the 
+ Retrospective, the facilitator of the Retrospective should elicit participation 
+ from the group, thereby granting tacit permission to members who are hesitant 
+ to participate immediately. </p>
+<h1> Collect and analyze data </h1>
+<p> The team begins this step of the Retrospective with a review of the meaningful 
+ characteristics of the iteration, release, incident, or project period. The 
+ focus of the team’s work in this step includes: critical developments, notable 
+ discoveries, work completed, project metrics (velocity, number of defects, and 
+ so forth), and review of project artifacts (requirements artifacts, project 
+ plans, and such). Encourage the team to capture all information (project data, 
+ opinions, and so on) by using various tools (white boards, charts, timelines) 
+ that provide a visual representation so that the team can identify relationships 
+ and emerging patterns. </p>
+<p> The team uses guiding questions to collect and analyze meaningful project 
+ data. You can use these examples of key questions to elicit relevant information: 
+</p>
+<ul>
+ <li>
+ Were the defined goals and objectives met? Did the release meet its functionality and quality goals? Did the
+ release meet performance and capacity goals?
+ </li>
+ <li>
+ Were risks reduced or eliminated? Can we identify new risks?
+ </li>
+ <li> Were all planned work items addressed? What was the team’s velocity relative 
+ to the plan? </li>
+ <li>
+ Did the end users provide favorable feedback on what we built in this iteration?
+ </li>
+ <li>
+ Are changes to the project plan required?
+ </li>
+ <li> What portion of the current release will be used to establish the baseline? 
+ What portion will need to be reworked? </li>
+ <li> Have there been external changes, such as changes in the marketplace, in 
+ the user community, or in the requirements? </li>
+ <li> Was the development process appropriate? How can it be fine-tuned for the 
+ specific needs of this project? </li>
+</ul>
+<p> The team has generated a list of candidate topics to focus on for its collective 
+ inquiry, or heightened analysis. The team’s methods of analysis need to facilitate 
+ a deepening understanding of the events characterizing the iteration, incident, 
+ release, or Project Retrospective. The team will be evaluating these driving 
+ factors, which ultimately documents a roadmap for the next cycle: </p>
+<ul>
+ <li><b>Success: </b>“What worked well for us during the past iteration (or project 
+ or phase)?”</li>
+ <li><b>Failure: </b>“What did not work well for us during the past iteration 
+ [or project or phase)?”</li>
+ <li><b>Opportunities for improvement: </b>“What should we do differently, or 
+ what improvements should we undertake during our next iteration (or project 
+ or phase)?”</li>
+</ul>
+<p> With increasing emphasis, the thread of team collaboration continues throughout 
+ the Retrospective, thereby fostering an environment conducive to candid, unimpeded 
+ examination by the team -- a rigorous style of examination that will be required 
+ to unearth the details lurking in the interactions of the team, the conditions 
+ of the project, fortuitous events, failures, risks, and examples of flourishing 
+ success. </p>
+<p> After the team has collected and analyzed the key data in the Retrospective, 
+ the team will have evaluated key project content. For each item evaluated, they 
+ will have established a root cause. The team will know what worked well, what 
+ did not, and what to do differently this time, so they can carry forward a list 
+ of suggested improvements that will be prioritized by the team. </p>
+<h1> Set priorities</h1>
+<p> By referencing the project data collected and analyzed in the Retrospective, 
+ the team now creates a list of suggested improvements, assigning a priority 
+ to each item on the list. </p>
+<p> The selection of improvements should be limited to a subset that will be applied 
+ in the next iteration cycle. This list should be considered as input to update 
+ the next Iteration Plan, so you can ensure an integrated relationship between 
+ the changes identified in the Retrospective and the normal course of the team’s 
+ work plans. </p>
+<p> Get commitment from members to complete, the suggested improvements that have 
+ been chosen for application in the next iteration cycle. The visibility and 
+ commitment among the members of the team imbue a sense that the Retrospective 
+ was worthy of the team’s investment of time and that the results of the work 
+ on the Retrospective will be tracked in the next iteration cycle. </p>
+<p> Maintain a backlog of the suggested improvements that were not chosen for 
+ the next iteration cycle. This will preserve the work of the Retrospective. 
+ The selected content will be available for convenient access and monitoring 
+ for progress, and the unselected items will be available for consideration during 
+ future iteration cycles. </p>
+<h1> Conclude and document the process</h1>
+<p>
+ The team’s honed methods of investigation and analysis&nbsp;are now applied to the Retrospective itself. During the
+ evaluation of the Retrospective, the team considers the moments of empowering thought and interaction, considers ideas
+ for improving future Retrospectives, revisits the team’s social contract, extends appreciation throughout the group,
+ and preserves the discoveries of the team (for example,&nbsp;through the use of Retrospective documentation
+ or&nbsp;pictures from a digital camera taken during the Retrospective).
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/iteration_assessment.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/iteration_assessment.xmi
new file mode 100644
index 0000000..0df0167
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/iteration_assessment.xmi
@@ -0,0 +1,74 @@
+<?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: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="-Cn1EflOAHbfuEjRZeLMyzA"
+ name="new_guideline,_FekBAC4IEdyhZrtGEIITGQ" guid="-Cn1EflOAHbfuEjRZeLMyzA" changeDate="2008-02-22T10:36:15.203-0500"
+ version="7.2.0">
+ <mainDescription><h3>
+ [*** Can't reference Guideline: Deploying the Solution.&nbsp; That info needs to be contributed from
+ risk_value_lifecycle.base **]
+</h3>
+<h3>
+ Practice
+</h3>An iteration assessment is a short meeting (up to 4 hours) involving the team and stakeholders that uses the solution
+increment as the focal point for brainstorming and to consider what functionality might be added in the next Iteration. It
+is a low ceremony meeting so the team should not waste too much time preparing the demo and formal presentations.
+Preparations can, instead, be focused on making the demo fast-paced and thinking about a good story to present the
+scenarios planned for the demo [<a class="elementLinkWithUserText"
+href="./../../../core.tech.common.base/guidances/supportingmaterials/tech_references_6CCF393.html#STZ07"
+guid="_9ToeIB83Edqsvps02rpOOg">STZ07</a>].<br />
+<br />
+The team should start the meeting by reviewing the iteration goal before presenting&nbsp;the functionality. The demo should
+be kept at a business-oriented level, leaving out the technical details. It should be focused on what was
+accomplished&nbsp;rather than how it was done. If possible, the audience should try to use the product. Minor bug fixes and
+trivial features should not be demonstrated, just mentioned, because the audience&nbsp;may lose focus on more important
+scenarios. Functionality that isn't <span style="BACKGROUND-COLOR: rgb(255,255,255)">really done (acceptance
+tested)</span>&nbsp;should not&nbsp;be presented. <br />
+<br />
+Team members present the system functionality and answer stakeholder questions. They also record changes, missing
+functionality and&nbsp;ideas for new features in the work item list. At the end of the presentation, the stakeholders are
+asked for their impressions and the priority of the changes. The potential rearrangement of the <a class="elementLink"
+href="./../../../core.mgmt.slot.base/workproducts/project_work_slot_F12BAC46.html" guid="_1QZI8EfUEdyiPI8btkmvmw">[Project
+Work]</a> is discussed with the team. Other points of discussion may include:<br />
+<br />
+<ul>
+ <li>
+ Were the defined goals and objectives met? Did the release meet its functionality and quality goals? Did the
+ release meet performance and capacity goals?
+ </li>
+ <li>
+ Were risks reduced or eliminated?&nbsp;Were new risks&nbsp;identified?
+ </li>
+ <li>
+ Were all planned work items addressed? What was the team's velocity relative to plan?
+ </li>
+ <li>
+ Did the end-users provide favorable feedback on what was built in this iteration?
+ </li>
+ <li>
+ Are any changes to the project plan required?
+ </li>
+ <li>
+ What portion of the current release will be baselined? What portion will need to be reworked?
+ </li>
+ <li>
+ Have there been external changes such as changes in the marketplace, in the user community, or in the requirements,
+ that will affect the project plan?
+ </li>
+</ul>
+<p>
+ Stakeholders and the team may also agree that there is sufficient functionality in the system to provide immediate
+ business value and they may decide to put the solution into production. In that case, discuss what deployment-related
+ work items should be added to the <a class="elementLink"
+ href="./../../../core.mgmt.slot.base/workproducts/project_work_slot_F12BAC46.html"
+ guid="_1QZI8EfUEdyiPI8btkmvmw">[Project Work]</a>.
+</p>
+<h3>
+ Value
+</h3>
+<p>
+ The Iteration Assessment provides an opportunity for everybody to learn about the solution being built and obtain vital
+ feedback from stakeholders. It also forces the team to actually finish work and release it.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/iteration_planning.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/iteration_planning.xmi
new file mode 100644
index 0000000..84fcd3b
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/iteration_planning.xmi
@@ -0,0 +1,137 @@
+<?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: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="_71hDkMPgEdmbOvqy4O0adg"
+ name="iteration_plan,_0auiMMlgEdmt3adZL5Dmdw" guid="_71hDkMPgEdmbOvqy4O0adg" changeDate="2006-11-01T14:17:34.612-0500"
+ version="7.2.0">
+ <mainDescription><h3>
+ Introduction
+</h3>
+<p>
+ The goal with iteration planning is to establish a few high-level objectives for what to accomplish during the
+ iteration, produce a sufficiently detailed plan outlining who needs to do what to accomplish those objectives, and
+ define how to assess that you accomplished what you set out to accomplish.
+</p>
+<p>
+ Iteration planning is ideally done with the entire team in a meeting, including key stakeholders, typically lasting one
+ to a few hours, at the beginning of an iteration. This ensures that the entire team understands what needs to be done,
+ and they become committed to the success of the team. In some cases, it is preferred to have a smaller subset of
+ people, such as the Project Manager, an Architect and an Analyst to meet in advance to prep the meeting with a draft
+ iteration plan.
+</p>
+<h3>
+ Define High-Level Objectives
+</h3>
+<p>
+ A key aspect of an iteration is to focus the team on a short term deliverable of measurable value. Document 1-5
+ high-level objectives to make sure that you don't lose focus on what to accomplish during the iteration. Typically, the
+ project plan should outline one or several objectives for each iteration, and those objectives are used as a starting
+ point. If you need to further detail or clarify the objectives as you plan your iteration, do so.
+</p>
+<p>
+ The objectives are usually based on the following factors:
+</p>
+<ul>
+ <li>
+ <strong>Critical risks not yet mitigated:</strong> Iteration goals often include driving down the most critical
+ risks.
+ </li>
+ <li>
+ <strong>The time allocated to the iteration:</strong> Iterations are timeboxed, so the Project Manager must ensure
+ that the goals for the iteration are realistic relative to the time and the resources allocated to the iteration.
+ </li>
+ <li>
+ <strong>The highest priority features:</strong> Requirements are prioritized to ensure that the critical features
+ of the application will be developed and tested early on.
+ </li>
+</ul>
+<h3>
+ Produce an Iteration Plan
+</h3>
+<p>
+ There is an Iteration Plan per iteration that should outline who will implement which Work Item in how long a time.
+ Since iterations are time-boxed, we need to understand how big our ‘box” is by assessing how many hours of actual work
+ can be taken on, see <a class="elementLinkWithType" href="./../../../openup/guidances/guidelines/agile_estimation_A4EF42B3.html" guid="_CGHskBEdEdqY7JB6N6CW2w">Guideline: Agile Estimation</a>. Let’s assume that you have 6 team members, and you have 15 working days in your iteration, and
+ you on average can do 5 actual hours of work per person and day. This will give you 6x15x5h = 450 hours of actual work.
+ Note that the average team member only performs 4-6 hours of actual project work per day, with the rest being consumed
+ by e-mails, meetings, and other overhead activities not directly related to the project.
+</p>
+<p>
+ The team should then revisit and update priorities for all the high-priority items in the Work Items List, to make sure
+ that an important Work Item is not missed that would otherwise fall just below the list of what can be taken on in this
+ iteration.
+</p>
+<p>
+ Pick the top-priority Work Item and see if it matches the objectives of the iteration. If it does, assess whether the
+ Work Item is too big to take on within an iteration. If it is too big, break it down into smaller Work Items. Once the
+ Work Item has been decomposed, the team determines whether to take on one or several child Work Items.
+</p>
+<p>
+ <em>Example: The team would like to take on Work Item “Develop Use Case A”, but it would take roughly 300 hours to
+ develop, so they feel that it is only necessary to do a subset of the use case to achieve their iteration objectives,
+ allowing them to take on other high-priority Work Items. They divide the Work Item into 5 smaller work items
+ representing different scenarios of use case A. The team decides to take on one out of the 5 identified scenarios in
+ this iteration.</em>
+</p>
+<p>
+ When a team has decided to take on a Work Item, it will assign the work to one or several team members. Ideally, this
+ is done by team members signing up to do the work, since this makes people motivated and committed to doing the job,
+ but based on culture, you may instead have the project manager assign the work.
+</p>
+<p>
+ The next step is for team member(s) to assess how many actual hours or days it will take to do the work. Ideally, you
+ want to have each work assignment to be from a few hours up to&nbsp;2 days of work. If the Work Item is too big,
+ consider breaking it down into smaller Work Items.
+</p>
+<p>
+ The team sums up the actual estimate for each Work Item they have committed to, and checks if they can commit to any
+ more work.
+</p>
+<p>
+ <em>Example: Jack signed up to develop the chosen scenario for use case A. He thinks that it would take 50 hours, so he
+ decided to develop the work into a set of tasks, and he asks other team members to help out with various subtasks:</em>
+</p>
+<ul>
+ <li>
+ <em>Detail the requirements (Jack) —5 hours</em>
+ </li>
+ <li>
+ <em>Design the scenario (Jack, Ann, and David) —5 hours</em>
+ </li>
+ <li>
+ <em>Implement and test the dB changes (Ann)—12 hours</em>
+ </li>
+ <li>
+ <em>Implement and test the server portion (David)—16 hours</em>
+ </li>
+ <li>
+ <em>Implement and test the client portion (Jack)—12 hours</em>
+ </li>
+ <li>
+ <em>Total—50 hours</em>
+ </li>
+</ul>
+<p>
+ As Work Items are decomposed into smaller tasks, estimates can typically be improved. You also better come to
+ understand what is involved, and whether other team member may be better suited to take on a subset of the task
+</p>
+<p>
+ The team now determines whether they are willing to take on another Work Item by comparing actual hours signed up for
+ to the actual hours available. In this case, the team has only signed up for 50 hours so far, and hence have another
+ 400 hours available
+</p>
+<h3>
+ Define Evaluation Criteria
+</h3>
+<p>
+ It is critical that it is clear to all team members and other stakeholders how you will measure success at the end of
+ the iteration. Obvious success criteria should be that you can test the functionality implemented, and that no or few
+ defects are detected. Having too many defects makes it impossible to use the functionality, and it will prevent
+ meaningful feedback. Test objectives and test cases need to be clearly outlined.
+</p>
+<p>
+ There may be other success criteria, such as that you demo the capabilities to a certain set of stakeholders with
+ favorable review comments, or that you can successfully demonstrate or make available a tech preview at a conference.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/managing_work_items.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/managing_work_items.xmi
new file mode 100644
index 0000000..1892bf7
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/managing_work_items.xmi
@@ -0,0 +1,154 @@
+<?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: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="-G1Oxlk6F0R09vClqy1EzOw"
+ name="managing_work_items,_7vEXEMA4EdqSgKaj2SZBmg" guid="-G1Oxlk6F0R09vClqy1EzOw"
+ changeDate="2007-11-13T11:37:23.968-0500" version="7.2.0">
+ <mainDescription>The <a class="elementLinkWithType"
+href="./../../../opn.swd.prac.legacy_pm/workproducts/work_items_list_39D03CC8.html"
+guid="_rGNWsCbSEdqh1LYUOGRh2A">Artifact: Work Items List</a>&nbsp;captures all scheduled work to be done within the
+project, as well as proposed work that may affect the product. Some of the Work Items may be implemented in this project,
+some of them may be implemented in a future project, and some of them may never be implemented. 
+<p>
+ Some of the Work Items may still be poorly defined; therefore, it could represent a big chunk of work, requiring
+ potentially several staff months of effort. As the priority of these Work Items increases, they are typically
+ decomposed into smaller work items that represent specific and well-defined tasks that may take hours or days to
+ address, see <a class="elementLink"
+ href="./../../../opn.swd.prac.legacy_pm/guidances/concepts/micro_increments_C8773066.html"
+ guid="_S80VwCNbEdyCq8v2ZO4QcA">Micro-Increments</a>. In other cases, specific and well-defined Work Items are created
+ directly, representing, for example, a defect to be addressed, as this figure illustrates.
+</p>
+<p align="center">
+ <strong><font face="Verdana, Arial, Helvetica, sans-serif" size="2"><strong><font
+ face="Verdana, Arial, Helvetica, sans-serif" size="2">Work Items List provides one prioritized list of scheduled and
+ proposed work</font></strong></font></strong>
+</p>
+<div align="center">
+ <strong><br />
+ <img alt="" src="./resources/work_item_prioritization_diagram.jpg" /></strong>
+</div>
+<p>
+ A Work Item may represent work associated with a defect, enhancement request, change request, use case, scenario, user
+ story, supporting requirement, stakeholder request, or anything else that captures a potential requirement or
+ improvement to your system. A Work Item may reference any type of requirement or other useful information that guides
+ you in what needs to be done.
+</p>
+<p>
+ A big advantage with the <a class="elementLinkWithType"
+ href="./../../../opn.swd.prac.legacy_pm/workproducts/work_items_list_39D03CC8.html"
+ guid="_rGNWsCbSEdqh1LYUOGRh2A">Artifact: Work Items List</a>&nbsp;is that it enables you to prioritize only one list
+ containing all of the things that may need to be addressed, whether the Work Item represent a work related to a
+ requirement, enhancement, or defect. The one exception is that we prioritize the risk list separately.
+</p>
+<p>
+ Nothing in the project will get done if not represented or mapped to a Work Item. This means that all requirements,
+ defect reports, and change requests have to be mapped to a Work Item at some stage. Also, a developer will not take on
+ work that is not represented in a Work Item. Only Work Items needs to be prioritized. This also means that tracking
+ Work Items are a primary means of understanding the status of the project.
+</p>
+<p>
+ There are two major types of Work Items:
+</p>
+<ul>
+ <li>
+ <strong>Unscheduled Work Items:</strong> These Work Items have not yet been assigned to an iteration, and there is
+ no detailed effort estimate for the Work Item yet.<br />
+ </li>
+ <li>
+ <strong>Scheduled Work Items:</strong> These Work Items are assigned to an iteration, and they typically have an
+ additional set of attributes filled in, such as detailed effort estimates.
+ </li>
+</ul>
+<h1>
+ Unscheduled Work Items
+</h1>
+<p>
+ Most Work Items are initially unscheduled, meaning that it has not yet been decided whether to do them and when to do
+ them. Unscheduled Work Items should always represent something meaningful to deliver to stakeholders, such a scenario
+ to be detailed, designed, implemented, and tested. You may consider capturing the following data for such Work Items:
+</p>
+<ul>
+ <li>
+ Name
+ </li>
+ <li>
+ Description
+ </li>
+ <li>
+ Priority
+ </li>
+ <li>
+ Size estimate, such as a point estimate (see <a class="elementLinkWithType"
+ href="./../../../opn.swd.prac.legacy_pm/guidances/guidelines/agile_estimation_A4EF42B3.html"
+ guid="_CGHskBEdEdqY7JB6N6CW2w">Guideline: Agile Estimation</a>)
+ </li>
+ <li>
+ State, such as New, Assigned, Resolved, Verified, Closed (see Work Items states, which follows here)
+ </li>
+ <li>
+ Links to other reference material, such as requirements or detailed specifications of what needs to be done
+ </li>
+</ul>
+<h1>
+ Scheduled Work Items
+</h1>
+<p>
+ After a Work Item has been assigned to an iteration, it becomes <i>scheduled</i>. We assign Work Items only to the
+ current or next iteration. There is no point in assigning Work Items to a specific future iteration, since we cannot
+ predict what a meaningful schedule will be more than an iteration in advance (see <a class="elementLinkWithType"
+ href="./../../../opn.swd.prac.legacy_pm/guidances/guidelines/iteration_planning_C77F13CE.html"
+ guid="_0auiMMlgEdmt3adZL5Dmdw">Guideline: Iteration Planning</a>).
+</p>
+<p>
+ The following additional attributes are useful for Scheduled Work Items:
+</p>
+<ul>
+ <li>
+ Target iteration
+ </li>
+ <li>
+ Responsible team member
+ </li>
+ <li>
+ Effort estimate left, such as actual hours of work (see <a class="elementLinkWithType"
+ href="./../../../opn.swd.prac.legacy_pm/guidances/guidelines/agile_estimation_A4EF42B3.html"
+ guid="_CGHskBEdEdqY7JB6N6CW2w">Guideline: Agile Estimation</a>
+ </li>
+ <li>
+ Hours worked
+ </li>
+</ul>
+<p>
+ This provides the information required to plan and manage an iteration. We can plan iterations by understanding effort
+ involved, and we can <a class="elementLinkWithType"
+ href="./../../../opn.swd.prac.legacy_pm/guidances/reports/iteration_burndown_9C1C96F5.html"
+ guid="_uAzgkDg3Edu4E8ZdmlYjtA">Report: Iteration Burndown</a> by tracking how much work is left to do.
+</p>
+<h1>
+ Work Item states
+</h1>
+<p>
+ We have found the following states to be useful for tracking Work Items:
+</p>
+<ul>
+ <li>
+ <b>New:</b> Work Item has been created, but not yet assigned to a team member.
+ </li>
+ <li>
+ <b>Assigned:</b> A team member has been identified as responsible for the Work Item.
+ </li>
+ <li>
+ <b>Resolved:</b> The team member responsible for the Work Items has implemented and tested the Work Item.
+ </li>
+ <li>
+ <b>Verified:</b> The Work Item has been independently tested.
+ </li>
+ <li>
+ <b>Closed:</b> The Work Item is no longer active.
+ </li>
+</ul>
+<p>
+ You may choose another set of states, based on your needs.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/prioritizing_work_items.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/prioritizing_work_items.xmi
new file mode 100644
index 0000000..022e045
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/prioritizing_work_items.xmi
@@ -0,0 +1,135 @@
+<?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: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="-b0rH1AkPSmj1YKyweFWSuQ"
+ name="new_guideline,_oVMZADSoEdy07ZJqOGUGaQ" guid="-b0rH1AkPSmj1YKyweFWSuQ" changeDate="2008-02-21T19:52:40.468-0500">
+ <mainDescription><h3>
+ [*** Need to refactor to remove the specific reference to Project Plan and Project Lifecycle ***]
+</h3>
+<h3>
+ What Is Prioritized?
+</h3>
+<p>
+ Work items are used to prioritize among others:
+</p>
+<ul>
+ <li>
+ enhancement requests and requirements at a level of abstraction appropriate for stakeholders prioritization, such
+ as use cases and scenarios,
+ </li>
+ <li>
+ project tasks, such as setting up required infrastructure,
+ </li>
+ <li>
+ defects,
+ </li>
+</ul>
+<p>
+ or any other work that needs to be prioritized. The <a class="elementLink"
+ href="./../../../practice.mgmt.iterative_dev.base/workproducts/work_items_list_39D03CC8.html"
+ guid="_rGNWsCbSEdqh1LYUOGRh2A">Work Items List</a> hence provides us with one place for prioritizing work. Prioritizing
+ too small units of work may lead to analysis-paralysis.
+</p>
+<h3>
+ Who Prioritizes?
+</h3>
+<p>
+ Prioritization is done by the extended team. Here are some examples on how different team members contribute to the
+ prioritization:
+</p>
+<ul>
+ <li>
+ <em>Analysts</em>&nbsp;collaborate with stakeholders to establish the initial priorities for work items to
+ implement, such as features, use cases and scenarios.
+ </li>
+ <li>
+ <em>Architects</em>&nbsp;collaborate with stakeholders and development team to identify the architecturally
+ significant use cases and scenarios, and re-prioritizes these so the team understands what needs to be done to
+ drive down technical risk and to progress the evolution of the product in a technically sensible fashion.
+ </li>
+ <li>
+ <em>Developers</em>&nbsp;and&nbsp;<em>Testers</em> calls out (not decides) the priorities of defects relative to
+ achieving iteration objectives.
+ </li>
+ <li>
+ <em>Project Managers</em> facilitates (not decide) driving convergence on what the team should focus on when
+ planning a project, planning an iteration, and managing an iteration to ensure smooth execution, and that the
+ perspectives of all team members are properly heard. When the team cannot gain consensus in a reasonable time, the
+ project manager has final say on the priority of work items to small to warrant the attention of the paying
+ stakeholder(s).
+ </li>
+ <li>
+ <em>Stakeholders</em>&nbsp;that pay for the application has the final say on what capabilities to prioritize.
+ </li>
+</ul>
+<h3>
+ When Do You Prioritize?
+</h3>
+<p>
+ When you put in a new work item in a <a class="elementLink"
+ href="./../../../practice.mgmt.iterative_dev.base/workproducts/work_items_list_39D03CC8.html"
+ guid="_rGNWsCbSEdqh1LYUOGRh2A">Work Items List</a>, you should give it an initial priority. Priorities are always
+ changing, and below we describe what (re-)prioritization is done when Planning a Project, Planning an Iteration, and
+ Managing an Iteration.
+</p>
+<h4>
+ Prioritizing When Planning a Project
+</h4>
+<p>
+ When planning the project, see <a class="elementLink"
+ href="./../../../practice.mgmt.two_level_project_planning.base/tasks/plan_the_project_A4A80C96.html"
+ guid="_0lC70MlgEdmt3adZL5Dmdw">Plan Project</a>, key features, use cases, and scenarios are prioritized and potentially
+ assigned to iterations as a part of laying out the project plan and what should be done when. These prioritizes will be
+ revised later on as iterations are planned.
+</p>
+<p>
+ When starting a project where we enhance an existing application, we may have an existing work items list from past
+ projects and usage of the application. If this is the case, we go through the work items list to survey and
+ re-prioritize existing work items, so we understand which to focus on.
+</p>
+<h4>
+ Prioritizing When Planning an Iteration
+</h4>
+<p>
+ When planning what to deliver for an iteration, see <a class="elementLink"
+ href="./../../../practice.mgmt.iterative_dev.base/tasks/plan_iteration_957C90DC.html"
+ guid="_0keUEMlgEdmt3adZL5Dmdw">Plan Iteration</a>, the team needs to balance what delivers immediate value to the
+ stakeholders with mitigating risk, see <a class="elementLink"
+ href="./../../../practice.mgmt.risk_value_lifecycle.base/guidances/concepts/project_lifecycle_203F87.html"
+ guid="_nSfVwCNYEdyCq8v2ZO4QcA">Project Lifecycle</a>. The chosen balance should be reflected in the iteration
+ objectives, which are then driving further prioritization and assignments of work items to the next iteration. This
+ exercise should be done by the entire team to reflect all key perspectives, such as technical (“doing A before B saves
+ you time”), managerial (“we do not have anybody that knows that legacy application until next iteration”, or business
+ (“this scenario is more important than that scenario”).
+</p>
+<h4>
+ Prioritizing When Managing an Iteration
+</h4>
+<p>
+ We recommend against expanding or changing the scope of an iteration, see <a class="elementLink"
+ href="./../../../practice.mgmt.iterative_dev.base/tasks/manage_iteration_E4D93A64.html"
+ guid="_8S2aICbYEdqh1LYUOGRh2A">Manage Iteration</a>, since this will almost certainly lead to scope creep, and
+ potentially confusion among the team what to work on. This means that as you can up with new enhancement requests, you
+ should capture them to a work item, but not assign them to the current iteration.
+</p>
+<p>
+ During an iteration, you are developing and testing code. As you develop solution increments, you will find defects. In
+ most cases, you will directly fix the defect since it is trivial, best done by you, and should be fixed now. Examples
+ of such defects are the many problems you find as you implement your code using a test-driven development approach. In
+ other cases, the defect should captured as a work item. This allows it to be prioritized, potentially developed by
+ somebody else and at a different time. If a defect needs to be addressed to provide an iteration build of reasonable
+ quality that addresses the iteration objectives, it should be addressed to the current iteration. Note that this is not
+ a creep or change of scope, since it merely indicates that we need to fix something to deliver what we already
+ committed to.
+</p>
+<h3>
+ How Do You Prioritize
+</h3>
+<p>
+ Prioritizing is the difficult balancing of frequently competing priorities. For more information on the art of
+ prioritizing, see for example [<a class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/tech_references_6CCF393.html#COH05"
+ guid="_9ToeIB83Edqsvps02rpOOg">COH05</a>].
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/resources/assess_results_EC34D88D.html b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/resources/assess_results_EC34D88D.html
new file mode 100644
index 0000000..9416e23
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/resources/assess_results_EC34D88D.html
@@ -0,0 +1,285 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" lang="en" xml:lang="en">
+<head>
+<META http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>Task: Assess Results</title>
+<meta content="Task" name="uma.type">
+<meta content="assess_results" name="uma.name">
+<meta content="Assess Results" name="uma.presentationName">
+<meta content="Discipline:project_management:Project Management" name="uma.category">
+<meta name="element_type" content="activity">
+<meta content="description" name="filetype">
+<meta name="role" content="Project Manager">
+<link type="text/css" href="./../../css/default.css" rel="StyleSheet">
+<script language="JavaScript" type="text/javascript" src="./../../scripts/ContentPageResource.js"></script><script language="JavaScript" type="text/javascript" src="./../../scripts/ContentPageSection.js"></script><script language="JavaScript" type="text/javascript" src="./../../scripts/ContentPageSubSection.js"></script><script language="JavaScript" type="text/javascript" src="./../../scripts/ContentPageToolbar.js"></script><script language="JavaScript" type="text/javascript" src="./../../scripts/contentPage.js"></script><script language="JavaScript" type="text/javascript">
+ var backPath = './../../';
+ var imgPath = './../../images/';
+ var nodeInfo=null;
+ contentPage.preload(imgPath, backPath, nodeInfo, '', true, false, false);
+ </script>
+</head>
+<body>
+<div id="breadcrumbs"></div>
+<table width="100%" cellspacing="0" cellpadding="0" border="0">
+<tr>
+<td valign="top">
+<div id="page-guid" value="_0l53cMlgEdmt3adZL5Dmdw"></div>
+<table width="100%" cellpadding="0" cellspacing="0" border="0">
+<tr>
+<td nowrap="true" class="pageTitle">Task: Assess Results</td><td width="100%">
+<div id="contentPageToolbar" align="right"></div>
+</td><td align="right" class="expandCollapseLink" width="100%"><a href="./../../index.htm" name="mainIndex"></a><script src="./../../scripts/treebrowser.js" type="text/javascript" language="JavaScript"></script></td>
+</tr>
+</table>
+<table cellspacing="0" cellpadding="0" border="0" width="100%">
+<tr>
+<td class="pageTitleSeparator"><img height="1" title="" alt="" src="./../../images/shim.gif"></td>
+</tr>
+</table>
+<div class="overview">
+<table cellpadding="0" cellspacing="0" border="0" width="97%">
+<tr>
+<td width="50"><img title="" alt="" src="./../../images/task.gif"></td><td>
+<table cellpadding="0" cellspacing="0" border="0" class="overviewTable">
+<tr>
+<td valign="top">Demonstrate the value of the solution increment that was built during the iteration and apply the lessons learned to modify the project or improve the process.</td>
+</tr>
+<tr>
+<td>Disciplines: <a href="./../../openup/disciplines/project_management_AFB03A6.html" guid="_0TqQ4MlgEdmt3adZL5Dmdw">Project Management</a></td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Purpose</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<td class="sectionTableSingleCell">To adjust expectations at regular intervals of the project, brainstorming around product increments and adapting behavior
+to the acquired knowledge.</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Relationships</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Roles</th><td width="42%" class="sectionTableCell"><span class="sectionTableCellHeading">Primary Performer:
+ </span>
+<ul>
+<li>
+<a href="./../../openup/roles/project_manager_E657F936.html" guid="_0a0o0MlgEdmt3adZL5Dmdw">Project Manager</a>
+</li>
+</ul>
+</td><td class="sectionTableCell"><span class="sectionTableCellHeading">Additional Performers:
+ </span>
+<ul>
+<li>
+<a href="./../../openup/roles/analyst_39D7C49B.html" guid="_0VxJsMlgEdmt3adZL5Dmdw">Analyst</a>
+</li>
+<li>
+<a href="./../../openup/roles/any_role_C36B701F.html" guid="_0dsWoMlgEdmt3adZL5Dmdw">Any Role</a>
+</li>
+<li>
+<a href="./../../openup/roles/architect_E7A12309.html" guid="_0X9iEMlgEdmt3adZL5Dmdw">Architect</a>
+</li>
+<li>
+<a href="./../../openup/roles/developer_C633AB7.html" guid="_0YDosMlgEdmt3adZL5Dmdw">Developer</a>
+</li>
+<li>
+<a href="./../../openup/roles/stakeholder_9FFD4106.html" guid="_dTa6gMAYEdqX-s4mWhkyqQ">Stakeholder</a>
+</li>
+<li>
+<a href="./../../openup/roles/tester_9859B590.html" guid="_0ZM4MclgEdmt3adZL5Dmdw">Tester</a>
+</li>
+</ul>
+</td>
+</tr>
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Inputs</th><td width="42%" class="sectionTableCell"><span class="sectionTableCellHeading">Mandatory:
+ </span>
+<ul>
+<li>
+<a href="./../../openup/workproducts/iteration_plan_B46FED39.html" guid="_0aQBEslgEdmt3adZL5Dmdw">Iteration Plan</a>
+</li>
+<li>
+<a href="./../../openup/workproducts/project_plan_1CDBB7E4.html" guid="_0a6vcMlgEdmt3adZL5Dmdw">Project Plan</a>
+</li>
+<li>
+<a href="./../../openup/workproducts/work_items_list_39D03CC8.html" guid="_rGNWsCbSEdqh1LYUOGRh2A">Work Items List</a>
+</li>
+</ul>
+</td><td class="sectionTableCell"><span class="sectionTableCellHeading">Optional:
+ </span>
+<ul>
+<li>
+<a href="./../../openup/workproducts/test_log_CBA2FDF4.html" guid="_0ZlSsMlgEdmt3adZL5Dmdw">Test Log</a>
+</li>
+<li>
+<a href="./../../openup/workproducts/vision_2E71B03C.html" guid="_0WVxcMlgEdmt3adZL5Dmdw">Vision</a>
+</li>
+</ul>
+</td>
+</tr>
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Outputs</th><td colspan="2" class="sectionTableCell">
+<ul>
+<li>
+<a href="./../../openup/workproducts/iteration_plan_B46FED39.html" guid="_0aQBEslgEdmt3adZL5Dmdw">Iteration Plan</a>
+</li>
+<li>
+<a href="./../../openup/workproducts/project_plan_1CDBB7E4.html" guid="_0a6vcMlgEdmt3adZL5Dmdw">Project Plan</a>
+</li>
+<li>
+<a href="./../../openup/workproducts/work_items_list_39D03CC8.html" guid="_rGNWsCbSEdqh1LYUOGRh2A">Work Items List</a>
+</li>
+</ul>
+</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Main Description</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<td class="sectionTableSingleCell">The <a class="elementLink" href="./../../openup/roles/project_manager_E657F936.html" guid="_0a0o0MlgEdmt3adZL5Dmdw">Project Manager</a> is responsible for coordinating the assessment. He or she discusses
+
+with the team how the iteration results with be best presented to stakeholders so they can learn as much about the solution
+
+as possible. The project manager also listens what the team has to say about what went wrong and what went right during the
+
+iteration. This knowledge will help everybody to make informed decisions for next iteration planning and determine the best
+
+course of action for the project. This task is performed at the end of every iteration until the end of the project.</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Steps</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr>
+<td class="sectionTableSingleCell">
+<div class="stepHeading">Review iteration results</div>
+<div class="stepContent">
+<table cellpadding="0" cellspacing="0" border="0" class="stepTable">
+<tr valign="top">
+<td><p>
+ Towards the end of the iteration, the team should jointly assess whether the objectives and evaluation criteria
+ established in the <a class="elementLink" href="./../../openup/workproducts/iteration_plan_B46FED39.html" guid="_0aQBEslgEdmt3adZL5Dmdw">Iteration Plan</a> were met, and whether the team adhered to the plan and completed all
+ the work items committed to the iteration. It should use objective measures to the greatest extent
+ possible. To assess that a given work item is completed, the team should ensure that the corresponding test cases were
+ successfully run against it.
+</p></td>
+</tr>
+</table>
+</div>
+<div class="stepHeading">Demonstrate value and gather feedback</div>
+<div class="stepContent">
+<table cellpadding="0" cellspacing="0" border="0" class="stepTable">
+<tr valign="top">
+<td><p>
+ The team should demonstrate the product to customer, end-users, and other <a class="elementLink" href="./../../openup/roles/stakeholder_9FFD4106.html" guid="_dTa6gMAYEdqX-s4mWhkyqQ">Stakeholder</a>s to collect their feedback,
+ or better yet, have end users to use the product themselves. This should be done throughout the iteration, or at least
+ in a separate session towards the end of the iteration (see <a class="elementLinkWithType" href="./../../openup/guidances/guidelines/iteration_assessment_E27E9DDE.html" guid="_FekBAC4IEdyhZrtGEIITGQ">Guideline: Iteration Assessment</a>). Work that is not completed should not be demonstrated. Resulting knowledge, such as new functionality,
+ requested changes and defects are recorded in the <a class="elementLink" href="./../../openup/workproducts/work_items_list_39D03CC8.html" guid="_rGNWsCbSEdqh1LYUOGRh2A">Work Items List</a>, so project
+ priorities, scope and duration can be refined in the next iteration planning.
+</p></td>
+</tr>
+</table>
+</div>
+<div class="stepHeading">Perform a retrospective</div>
+<div class="stepContent">
+<table cellpadding="0" cellspacing="0" border="0" class="stepTable">
+<tr valign="top">
+<td><p>
+ Review with the team the approach taken to development and collaboration, the effectiveness of the development
+ environment, the suitability of the working environment, and other factors. Discuss what things went well, what could
+ have gone better, and how things could be changed to deliver better results. Capture assessment results in the current
+ <a class="elementLink" href="./../../openup/workproducts/iteration_plan_B46FED39.html" guid="_0aQBEslgEdmt3adZL5Dmdw">Iteration Plan</a> as well as stakeholder feedback and actions to be taken to
+ improve the development approach for next iteration. Gather lessons learned and record those in the <a class="elementLink" href="./../../openup/workproducts/project_plan_1CDBB7E4.html" guid="_0a6vcMlgEdmt3adZL5Dmdw">Project Plan</a> to be used in the future. You may wish to leverage EPF composer to improve the process by incorporating the
+ lessons that have been successfully piloted in the project and enhance templates, checklists, activities, steps,
+ introduce new practices and guidance. See <a class="elementLinkWithType" href="./../../openup/guidances/supportingmaterials/resources_for_modifying_methods_7663A1A6.html" guid="_omneEMX4EduywMSzPTUUwA">Supporting Material: Resources for Modifying Methods</a> for more information.
+</p>
+<p>
+ When the assessment period coincides with the end of a phase the corresponding milestone review takes place. These are
+ informal reviews of the work accomplished where the team and stakeholders agree on moving the project on to the next
+ phase, spanning a set of iterations with a new common goal, in accordance with the emphasis of the following phase. For
+ more information, refer to <a class="elementLinkWithType" href="./../../openup/guidances/concepts/phase_milestones_5678231E.html" guid="_HNxbwMBJEdqSgKaj2SZBmg">Concept: Phase Milestones</a>.
+</p></td>
+</tr>
+</table>
+</div>
+<div class="stepHeading">Close-out project</div>
+<div class="stepContent">
+<table cellpadding="0" cellspacing="0" border="0" class="stepTable">
+<tr valign="top">
+<td><p>
+
+ This step must be performed only when the iteration review coincides with the end of the project. Involve the team and
+
+ stakeholders in a final assessment for project acceptance which, if successful, marks the point when the customer
+
+ accepts ownership of the software product. Complete the close-out of the project by disposing of the remaining assets
+
+ and reassigning the remaining staff.
+
+</p></td>
+</tr>
+</table>
+</div>
+</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">More Information</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Concepts</th><td class="sectionTableCell">
+<ul>
+<li>
+<a href="./../../openup/guidances/concepts/phase_milestones_5678231E.html" guid="_HNxbwMBJEdqSgKaj2SZBmg">Phase Milestones</a>
+</li>
+<li>
+<a href="./../../openup/guidances/concepts/retrospective_B003F386.html" guid="_2PfbIA4QEdy2q5zsU8WDnA">Retrospective</a>
+</li>
+</ul>
+</td>
+</tr>
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Guidelines</th><td class="sectionTableCell">
+<ul>
+<li>
+<a href="./../../openup/guidances/guidelines/conduct_retrospective_1A6C7321.html" guid="_277QEA4gEdy63f1yVoPyfA">Conduct Project Retrospective</a>
+</li>
+<li>
+<a href="./../../openup/guidances/guidelines/deploying_the_solution_A64311AA.html" guid="_yYlQoC3xEdycYKq0PulnEQ">Deploying the Solution</a>
+</li>
+<li>
+<a href="./../../openup/guidances/guidelines/iteration_assessment_E27E9DDE.html" guid="_FekBAC4IEdyhZrtGEIITGQ">Iteration Assessment</a>
+</li>
+</ul>
+</td>
+</tr>
+</table>
+</div>
+<table cellpadding="0" cellspacing="0" border="0" class="copyright">
+<tr>
+<td class="copyright"><p>
+ This program and the accompanying materials are made available under the<br />
+ <a href="http://www.eclipse.org/org/documents/epl-v10.php" target="_blank">Eclipse Public License v1.0</a> which
+ accompanies this distribution.
+</p><p/><p>
+ <a class="elementLink" href="./../../openup/guidances/supportingmaterials/openup_copyright_C3031062.html" guid="_UaGfECcTEduSX6N2jUafGA">OpenUP Copyright</a>.
+</p></td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+</body>
+<script language="JavaScript" type="text/javascript">
+ contentPage.onload();
+ </script>
+</html>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/resources/plan_iteration_957C90DC.html b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/resources/plan_iteration_957C90DC.html
new file mode 100644
index 0000000..d62f825
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/resources/plan_iteration_957C90DC.html
@@ -0,0 +1,364 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" lang="en" xml:lang="en">
+<head>
+<META http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>Task: Plan Iteration</title>
+<meta content="Task" name="uma.type">
+<meta content="plan_iteration" name="uma.name">
+<meta content="Plan Iteration" name="uma.presentationName">
+<meta content="Discipline:project_management:Project Management" name="uma.category">
+<meta name="element_type" content="activity">
+<meta content="description" name="filetype">
+<meta name="role" content="Project Manager">
+<link type="text/css" href="./../../css/default.css" rel="StyleSheet">
+<script language="JavaScript" type="text/javascript" src="./../../scripts/ContentPageResource.js"></script><script language="JavaScript" type="text/javascript" src="./../../scripts/ContentPageSection.js"></script><script language="JavaScript" type="text/javascript" src="./../../scripts/ContentPageSubSection.js"></script><script language="JavaScript" type="text/javascript" src="./../../scripts/ContentPageToolbar.js"></script><script language="JavaScript" type="text/javascript" src="./../../scripts/contentPage.js"></script><script language="JavaScript" type="text/javascript">
+ var backPath = './../../';
+ var imgPath = './../../images/';
+ var nodeInfo=null;
+ contentPage.preload(imgPath, backPath, nodeInfo, '', true, false, false);
+ </script>
+</head>
+<body>
+<div id="breadcrumbs"></div>
+<table width="100%" cellspacing="0" cellpadding="0" border="0">
+<tr>
+<td valign="top">
+<div id="page-guid" value="_0keUEMlgEdmt3adZL5Dmdw"></div>
+<table width="100%" cellpadding="0" cellspacing="0" border="0">
+<tr>
+<td nowrap="true" class="pageTitle">Task: Plan Iteration</td><td width="100%">
+<div id="contentPageToolbar" align="right"></div>
+</td><td align="right" class="expandCollapseLink" width="100%"><a href="./../../index.htm" name="mainIndex"></a><script src="./../../scripts/treebrowser.js" type="text/javascript" language="JavaScript"></script></td>
+</tr>
+</table>
+<table cellspacing="0" cellpadding="0" border="0" width="100%">
+<tr>
+<td class="pageTitleSeparator"><img height="1" title="" alt="" src="./../../images/shim.gif"></td>
+</tr>
+</table>
+<div class="overview">
+<table cellpadding="0" cellspacing="0" border="0" width="97%">
+<tr>
+<td width="50"><img title="" alt="" src="./../../images/task.gif"></td><td>
+<table cellpadding="0" cellspacing="0" border="0" class="overviewTable">
+<tr>
+<td valign="top">A collaborative task that plans the scope and responsibilities for a single iteration, defining goals and evaluation criteria.</td>
+</tr>
+<tr>
+<td>Disciplines: <a href="./../../openup/disciplines/project_management_AFB03A6.html" guid="_0TqQ4MlgEdmt3adZL5Dmdw">Project Management</a></td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Purpose</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<td class="sectionTableSingleCell"><p>
+
+
+ To identify the next increment of system capability, and create a fine-grained plan for achieving that capability
+
+
+ within a single iteration.
+
+
+</p></td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Relationships</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Roles</th><td width="42%" class="sectionTableCell"><span class="sectionTableCellHeading">Primary Performer:
+ </span>
+<ul>
+<li>
+<a href="./../../openup/roles/project_manager_E657F936.html" guid="_0a0o0MlgEdmt3adZL5Dmdw">Project Manager</a>
+</li>
+</ul>
+</td><td class="sectionTableCell"><span class="sectionTableCellHeading">Additional Performers:
+ </span>
+<ul>
+<li>
+<a href="./../../openup/roles/analyst_39D7C49B.html" guid="_0VxJsMlgEdmt3adZL5Dmdw">Analyst</a>
+</li>
+<li>
+<a href="./../../openup/roles/architect_E7A12309.html" guid="_0X9iEMlgEdmt3adZL5Dmdw">Architect</a>
+</li>
+<li>
+<a href="./../../openup/roles/developer_C633AB7.html" guid="_0YDosMlgEdmt3adZL5Dmdw">Developer</a>
+</li>
+<li>
+<a href="./../../openup/roles/stakeholder_9FFD4106.html" guid="_dTa6gMAYEdqX-s4mWhkyqQ">Stakeholder</a>
+</li>
+<li>
+<a href="./../../openup/roles/tester_9859B590.html" guid="_0ZM4MclgEdmt3adZL5Dmdw">Tester</a>
+</li>
+</ul>
+</td>
+</tr>
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Inputs</th><td width="42%" class="sectionTableCell"><span class="sectionTableCellHeading">Mandatory:
+ </span>
+<ul>
+<li>
+<a href="./../../openup/workproducts/project_plan_1CDBB7E4.html" guid="_0a6vcMlgEdmt3adZL5Dmdw">Project Plan</a>
+</li>
+<li>
+<a href="./../../openup/workproducts/work_items_list_39D03CC8.html" guid="_rGNWsCbSEdqh1LYUOGRh2A">Work Items List</a>
+</li>
+</ul>
+</td><td class="sectionTableCell"><span class="sectionTableCellHeading">Optional:
+ </span>
+<ul>
+<li>
+<a href="./../../openup/workproducts/architecture_notebook_9BB92433.html" guid="_0XAf0MlgEdmt3adZL5Dmdw">Architecture Notebook</a>
+</li>
+<li>
+<a href="./../../openup/workproducts/iteration_plan_B46FED39.html" guid="_0aQBEslgEdmt3adZL5Dmdw">Iteration Plan</a>
+</li>
+<li>
+<a href="./../../openup/workproducts/risk_list_C4B6F290.html" guid="_Ckay8Cc_EduIsqH1Q6ZuqA">Risk List</a>
+</li>
+<li>
+<a href="./../../openup/workproducts/vision_2E71B03C.html" guid="_0WVxcMlgEdmt3adZL5Dmdw">Vision</a>
+</li>
+</ul>
+</td>
+</tr>
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Outputs</th><td colspan="2" class="sectionTableCell">
+<ul>
+<li>
+<a href="./../../openup/workproducts/iteration_plan_B46FED39.html" guid="_0aQBEslgEdmt3adZL5Dmdw">Iteration Plan</a>
+</li>
+<li>
+<a href="./../../openup/workproducts/risk_list_C4B6F290.html" guid="_Ckay8Cc_EduIsqH1Q6ZuqA">Risk List</a>
+</li>
+<li>
+<a href="./../../openup/workproducts/work_items_list_39D03CC8.html" guid="_rGNWsCbSEdqh1LYUOGRh2A">Work Items List</a>
+</li>
+</ul>
+</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Main Description</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<td class="sectionTableSingleCell"><p>
+
+
+ During project planning, iterations are identified but the estimates have an acceptable uncertainty due to the lack of
+
+
+ detail at the project inception. This task is repeated for each iteration within a release. It allows the team to
+
+
+ increase the accuracy of the estimates for one iteration, as more detail is known along the project. The <a class="elementLink" href="./../../openup/roles/project_manager_E657F936.html" guid="_0a0o0MlgEdmt3adZL5Dmdw">Project Manager</a> has the responsibility of ensuring that the team commits to a
+
+
+ reasonable amount of work for the iteration, based on team performance from previous iterations.
+
+
+</p></td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Steps</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr>
+<td class="sectionTableSingleCell">
+<div class="stepHeading">Prioritize Work Items List</div>
+<div class="stepContent">
+<table cellpadding="0" cellspacing="0" border="0" class="stepTable">
+<tr valign="top">
+<td>The WIL should be prioritized before you plan the next iteration. Consider what has changed since the last iteration
+plan such as new change requests, shifting priorities of your stakeholders or new risks that have been encountered.</td>
+</tr>
+</table>
+</div>
+<div class="stepHeading">Refine project plan</div>
+<div class="stepContent">
+<table cellpadding="0" cellspacing="0" border="0" class="stepTable">
+<tr valign="top">
+<td>Depending on the results of the previous iteration assessment the <a class="elementLink" href="./../../openup/roles/project_manager_E657F936.html" guid="_0a0o0MlgEdmt3adZL5Dmdw">Project Manager</a> may need to
+
+revise the <a class="elementLink" href="./../../openup/workproducts/project_plan_1CDBB7E4.html" guid="_0a6vcMlgEdmt3adZL5Dmdw">Project Plan</a>. Necessary changes can encompass the need to acquire new resources, to
+
+absorb an unplanned effort increase, or to implement a specific change request. If a change affects defined project
+
+milestones, the <a class="elementLink" href="./../../openup/roles/project_manager_E657F936.html" guid="_0a0o0MlgEdmt3adZL5Dmdw">Project Manager</a> should consult with the stakeholders before committing to them.</td>
+</tr>
+</table>
+</div>
+<div class="stepHeading">Define the iteration objectives</div>
+<div class="stepContent">
+<table cellpadding="0" cellspacing="0" border="0" class="stepTable">
+<tr valign="top">
+<td><p>
+
+
+ Work with the team to refine the iteration objectives found in the <a class="elementLink" href="./../../openup/workproducts/project_plan_1CDBB7E4.html" guid="_0a6vcMlgEdmt3adZL5Dmdw">Project Plan</a>, and document them in the <a class="elementLink" href="./../../openup/workproducts/iteration_plan_B46FED39.html" guid="_0aQBEslgEdmt3adZL5Dmdw">Iteration Plan</a> in order to provide high-level direction to what should be
+
+
+ targeted for the iteration. The objectives should be driven based on <a class="elementLink" href="./../../openup/roles/stakeholder_9FFD4106.html" guid="_dTa6gMAYEdqX-s4mWhkyqQ">Stakeholder</a> priorities, and will be revised as the iteration plan is finalized.
+
+
+ Those objectives are usually defined as high-level capabilities or scenarios that need to be implemented and tested
+
+
+ during the iteration in order to deliver increased value to the customer.<br />
+
+
+</p></td>
+</tr>
+</table>
+</div>
+<div class="stepHeading">Commit work to the iteration</div>
+<div class="stepContent">
+<table cellpadding="0" cellspacing="0" border="0" class="stepTable">
+<tr valign="top">
+<td><p>
+
+ The <a class="elementLink" href="./../../openup/roles/project_manager_E657F936.html" guid="_0a0o0MlgEdmt3adZL5Dmdw">Project Manager</a> works with the rest of the team, and especially the project
+
+ stakeholders, to identify the high-priority work items from the <a class="elementLink" href="./../../openup/workproducts/work_items_list_39D03CC8.html" guid="_rGNWsCbSEdqh1LYUOGRh2A">Work Items List</a> to be
+
+ addressed. The high-level objectives provide guidance on what work items should be considered. The <a class="elementLink" href="./../../openup/workproducts/iteration_plan_B46FED39.html" guid="_0aQBEslgEdmt3adZL5Dmdw">Iteration Plan</a> from previous iteration should include an assessment of the
+
+ results and can also be used as input to the current iteration planning. The team reviews its velocity and
+
+ determines the amount of work that can be done within the iteration. The team breaks down into tasks those work
+
+ items that are assigned to the iteration and estimates the effort to complete each task (see <a class="elementLinkWithType" href="./../../openup/guidances/guidelines/agile_estimation_A4EF42B3.html" guid="_CGHskBEdEdqY7JB6N6CW2w">Guideline: Agile Estimation</a>). Typical tasks range from half day to two days in
+
+ lenght.
+
+</p>
+
+<p>
+
+ When a team has decided to take on a work item, it will assign the work to one or several team members. Ideally, this
+
+ is done by team members signing up to do the work, since this makes people motivated and committed to doing the job,
+
+ but based on culture, you may instead have the project manager assign the work.<br />
+
+</p></td>
+</tr>
+</table>
+</div>
+<div class="stepHeading">Review risks</div>
+<div class="stepContent">
+<table cellpadding="0" cellspacing="0" border="0" class="stepTable">
+<tr valign="top">
+<td><p>
+
+
+ Throughout the project, new assumptions and concerns may arise. The team identifies and prioritizes new risks
+
+
+ as part of iteration planning, updating the <a class="elementLink" href="./../../openup/workproducts/risk_list_C4B6F290.html" guid="_Ckay8Cc_EduIsqH1Q6ZuqA">Risk List</a>. Responses to risks are added to the <a class="elementLink" href="./../../openup/workproducts/work_items_list_39D03CC8.html" guid="_rGNWsCbSEdqh1LYUOGRh2A">Work Items List</a>, influencing the work that is being planned for that iteration.
+
+
+</p></td>
+</tr>
+</table>
+</div>
+<div class="stepHeading">Define evaluation criteria</div>
+<div class="stepContent">
+<table cellpadding="0" cellspacing="0" border="0" class="stepTable">
+<tr valign="top">
+<td><p>
+
+
+ Each iteration should include testing as a part of the evaluation, and the test objectives and test cases
+
+
+ that need to be detailed. Other evaluation criteria may include successful demonstrations to key stakeholders, or
+
+
+ favorable usage by a small group of target users. Document evaluation criteria in the <a class="elementLink" href="./../../openup/workproducts/iteration_plan_B46FED39.html" guid="_0aQBEslgEdmt3adZL5Dmdw">Iteration Plan</a>.<br />
+
+
+</p></td>
+</tr>
+</table>
+</div>
+</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">More Information</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Concepts</th><td class="sectionTableCell">
+<ul>
+<li>
+<a href="./../../openup/guidances/concepts/iteration_C20B1904.html" guid="_lam4ADkBEduxovfWMDsntw">Iteration</a>
+</li>
+<li>
+<a href="./../../openup/guidances/concepts/iteration_lifecycle_B16552E2.html" guid="_DI_tICNaEdyCq8v2ZO4QcA">Iteration Lifecycle</a>
+</li>
+<li>
+<a href="./../../openup/guidances/concepts/micro_increments_C8773066.html" guid="_S80VwCNbEdyCq8v2ZO4QcA">Micro-Increments</a>
+</li>
+</ul>
+</td>
+</tr>
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Guidelines</th><td class="sectionTableCell">
+<ul>
+<li>
+<a href="./../../openup/guidances/guidelines/iteration_planning_C77F13CE.html" guid="_0auiMMlgEdmt3adZL5Dmdw">Iteration Planning</a>
+</li>
+<li>
+<a href="./../../openup/guidances/guidelines/agile_estimation_A4EF42B3.html" guid="_CGHskBEdEdqY7JB6N6CW2w">Agile Estimation</a>
+</li>
+<li>
+<a href="./../../openup/guidances/guidelines/assign_changes_to_iteration_67B3DEA2.html" guid="__yQQ4L6REdqti4GwqTkbsQ">Assign Changes to an Iteration</a>
+</li>
+<li>
+<a href="./../../openup/guidances/guidelines/work_items_list_32AC6ABD.html" guid="_7vEXEMA4EdqSgKaj2SZBmg">Managing Work Items</a>
+</li>
+<li>
+<a href="./../../openup/guidances/guidelines/self_organize_work_assignments_F47FC314.html" guid="_rmBEkJjsEduad8I_c-ogIA">Self Organize Work Assignments</a>
+</li>
+<li>
+<a href="./../../openup/guidances/guidelines/risk_management_B1256EB4.html" guid="_VNxL4ACsEdu8m4dIntu6jA">Managing Risks</a>
+</li>
+<li>
+<a href="./../../openup/guidances/guidelines/deploying_the_solution_A64311AA.html" guid="_yYlQoC3xEdycYKq0PulnEQ">Deploying the Solution</a>
+</li>
+</ul>
+</td>
+</tr>
+</table>
+</div>
+<table cellpadding="0" cellspacing="0" border="0" class="copyright">
+<tr>
+<td class="copyright"><p>
+ This program and the accompanying materials are made available under the<br />
+ <a href="http://www.eclipse.org/org/documents/epl-v10.php" target="_blank">Eclipse Public License v1.0</a> which
+ accompanies this distribution.
+</p><p/><p>
+ <a class="elementLink" href="./../../openup/guidances/supportingmaterials/openup_copyright_C3031062.html" guid="_UaGfECcTEduSX6N2jUafGA">OpenUP Copyright</a>.
+</p></td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+</body>
+<script language="JavaScript" type="text/javascript">
+ contentPage.onload();
+ </script>
+</html>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/resources/references_6CCF393.html b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/resources/references_6CCF393.html
new file mode 100644
index 0000000..9ed43f5
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/resources/references_6CCF393.html
@@ -0,0 +1,870 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" lang="en" xml:lang="en">
+<head>
+<META http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>Supporting Material: References</title>
+<meta content="SupportingMaterial" name="uma.type">
+<meta content="references" name="uma.name">
+<meta content="References" name="uma.presentationName">
+<meta name="element_type" content="other">
+<meta content="description" name="filetype">
+<meta name="role" content="">
+<link type="text/css" href="./../../../css/default.css" rel="StyleSheet">
+<script language="JavaScript" type="text/javascript" src="./../../../scripts/ContentPageResource.js"></script><script language="JavaScript" type="text/javascript" src="./../../../scripts/ContentPageSection.js"></script><script language="JavaScript" type="text/javascript" src="./../../../scripts/ContentPageSubSection.js"></script><script language="JavaScript" type="text/javascript" src="./../../../scripts/ContentPageToolbar.js"></script><script language="JavaScript" type="text/javascript" src="./../../../scripts/contentPage.js"></script><script language="JavaScript" type="text/javascript">
+ var backPath = './../../../';
+ var imgPath = './../../../images/';
+ var nodeInfo=null;
+ contentPage.preload(imgPath, backPath, nodeInfo, '', false, false, false);
+ </script>
+</head>
+<body>
+<div id="breadcrumbs"></div>
+<table width="100%" cellspacing="0" cellpadding="0" border="0">
+<tr>
+<td valign="top"><a name="Top"></a>
+<div id="page-guid" value="_9ToeIB83Edqsvps02rpOOg"></div>
+<table width="100%" cellpadding="0" cellspacing="0" border="0">
+<tr>
+<td nowrap="true" class="pageTitle">References</td><td width="100%">
+<div id="contentPageToolbar" align="right"></div>
+</td><td align="right" class="expandCollapseLink" width="100%"><a href="./../../../index.htm" name="mainIndex"></a><script src="./../../../scripts/treebrowser.js" type="text/javascript" language="JavaScript"></script></td>
+</tr>
+</table>
+<table cellspacing="0" cellpadding="0" border="0" width="100%">
+<tr>
+<td class="pageTitleSeparator"><img height="1" title="" alt="" src="./../../../images/shim.gif"></td>
+</tr>
+</table>
+<div class="overview">
+<table cellpadding="0" cellspacing="0" border="0" width="97%">
+<tr>
+<td width="50"><img title="" alt="" src="./../../../images/supportingmaterial.gif"></td><td>
+<table cellpadding="0" cellspacing="0" border="0" class="overviewTable">
+<tr>
+<td valign="top">Additional references that may be useful, including books, method plug-ins, and commercial methodology products.</td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Main Description</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<td class="sectionTableSingleCell"><table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="ADO03" name="ADO03">ADO03</a>
+ </td>
+ <td colspan="2">
+ Adolph, Bramble, Cockburn, and Pols <em>Patterns for Effective Use Cases</em>, Addison Wesley, 2003.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="ADO04" name="ADO04">ADO04</a>
+ </td>
+ <td colspan="2">
+ Adolph, Bramble, Cockburn, and Pols <em>Tutorial 17: Patterns for Writing Effective Use Cases</em>,
+ presented at the 19th Annual Conference on Object-Oriented Programming, Systems, Languages and
+ Applications, 2004.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="ALE77" name="ALE77">ALE77</a>
+ </td>
+ <td colspan="2">
+ Alexander, C. <em>A Pattern Language</em>, Oxford University Press, 1977
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="ALE79" name="ALE79">ALE79</a>
+ </td>
+ <td colspan="2">
+ Alexander, C., <em>A Timeless Way of Building</em>, Oxford University Press, 1979
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="ALL02" name="ALL02">ALL02</a>
+ </td>
+ <td colspan="2">
+ Allamaraju, S. <em>Architecture Paradox</em>, <a href="http://www.sei.cmu.edu/architecture/essays.html">http://www.sei.cmu.edu/architecture/essays.html</a>.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="ALU03" name="ALU03">ALU03</a>
+ </td>
+ <td colspan="2">
+ <p>
+ Alur, D., Crupi, J., Malks, D., <em>Core J2EE Patterns: Best Practices and Design Strategies</em>,
+ Prentice Hall/Sun Press, 2001.
+ </p>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="AMB02" name="AMB02">AMB02</a>
+ </td>
+ <td colspan="2">
+ Ambler, S.W.<em>Agile Modeling: Effective Practices for Extreme Programming and Unified Process</em>. Wiley
+ Publishing, 2002.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="AMB03" name="AMB03">AMB03</a>
+ </td>
+ <td colspan="2">
+ Ambler, S.W.<em>Agile Database Techniques: Effective Strategies for the Agile Software Developer</em>.
+ Wiley Publishing, 2003.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="AMB04" name="AMB04">AMB04</a>
+ </td>
+ <td colspan="2">
+ Ambler, S.W.<em>The Object Primer 3rd Edition: Agile Model Driven Development with UML 2</em>. Addison
+ Wesley, 2006.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="AMB06" name="AMB06">AMB06</a>
+ </td>
+ <td colspan="2">
+ Ambler, S.W. and Sadalage, P.J. <em>Refactoring Databases: Evolutionary Database Design</em>. Addison
+ Wesley, 2006.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="AMB07" name="AMB07">AMB07</a>
+ </td>
+ <td colspan="2">
+ Ambler, S.W.<em>The Agile End Game,</em> <a href="http://www.agilealliance.org/show/1819">http://www.agilealliance.org/show/1819</a>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="BEC05" name="BEC05">BEC05</a>
+ </td>
+ <td colspan="2">
+ Beck, K., Andres, C. <em>Extreme Programming Explained: Embrace Change, 2nd Edition</em>, Addison Wesley,
+ 2005.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="BOE88" name="BOE88">BOE88</a>
+ </td>
+ <td colspan="2">
+ Boehm, B., Papaccio, C. <em>Understanding and Controlling Software Cost</em>, IEEE Trans. on Software
+ Engineering, Oct. 1988.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="BOE95" name="BOE95">BOE95</a>
+ </td>
+ <td colspan="2">
+ Boehm, B. <em>Anchoring the Software Process</em>, <a href="http://sunset.usc.edu/publications/TECHRPTS/1995/usccse95-507/ASP.pdf">http://sunset.usc.edu/publications/TECHRPTS/1995/usccse95-507/ASP.pdf</a>
+ (Get <a href="http://www.adobe.com/products/acrobat/alternate.html">Adobe reader</a>.)
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="BRO87" name="BRO87">BRO87</a>
+ </td>
+ <td colspan="2">
+ Brooks, F.P <em>No Silver Bullet: Essence and Accidents of Software Engineering.</em>Computer, April. 1987,
+ pp. 10-19.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="BOO05" name="BOO05">BOO05</a>
+ </td>
+ <td colspan="2">
+ Booch, G., Rumbaugh, J., Jacobson, I.<em>The Unified Modeling Language User Guide</em>, Addison-Wesley
+ Professional, 2005
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="BUS96" name="BUS96">BUS96</a>
+ </td>
+ <td colspan="2">
+ Buschmann, F., Meunier, R., Rohnert, H.,Sommerlad, P., Stal, M., <em>Pattern-Oriented Software Architecture
+ -- A System of Patterns</em>, Wiley, 1996.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="COH05" name="COH05">COH05</a>
+ </td>
+ <td colspan="2">
+ Cohn, M., <em>Agile Estimation and Planning</em>, Addison Wesley Longman, 2005
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="COP95" name="COP95">COP95</a>
+ </td>
+ <td colspan="2">
+ Coplien, J., Schmidt, D., <em>Pattern Languages of Program Design</em>, Addison-Wesley Professional, 1995.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="CRO79" name="CRO79">CRO79</a>
+ </td>
+ <td colspan="2">
+ Crosby, Philip. <em>Quality is Free: The Art of Making Quality Certain</em>, McGraw-Hill, 1979.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="DER06" name="DER06">DER06</a>
+ </td>
+ <td colspan="2">
+ Derby, Esther and Larsen, Diana <em>Agile Retrospectives: Making Good Team Great</em>, Pragmatic Bookshelf,
+ Dallas, Texas, 2006.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="DEW92" name="DEW92">DEW92</a>
+ </td>
+ <td colspan="2">
+ Dewayne E. Perry and Alexander L. Wolf. <em>Foundations for the Study of Software Architecture</em>. ACM
+ SIGSOFT Software Engineering Notes, 17(4):40-52, October 1992.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="DSDM" name="DSDM">DSDM</a>
+ </td>
+ <td colspan="2">
+ DSDM Consortium, <em>DSDM</em><br />
+ <a href="http://www.dsdm.org/products/">http://www.dsdm.org/products/</a>
+ </td>
+ </tr>
+ </tbody>
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="FOW06" name="FOW06">FOW06</a>
+ </td>
+ <td colspan="2">
+ Fowler, Martin <em>Continuous Integration</em><br />
+ <a href="http://www.martinfowler.com/articles/continuousIntegration.html">http://www.martinfowler.com/articles/continuousIntegration.html</a>
+ </td>
+ </tr>
+ </tbody>
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="FOW99" name="FOW99">FOW99</a>
+ </td>
+ <td colspan="2">
+ Fowler, Martin, <em>Refactoring: Improving the Design of Existing Code</em>, Addison-Wesley Professional;
+ 1999
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="GAM95" name="GAM95">GAM95</a>
+ </td>
+ <td colspan="2">
+ Gamma, E., Helm, R., Johnson, R., Vlissides, J., <em>Design Patterns: Elements of Reusable Object-Oriented
+ Software</em>, Addison-Wesley Professional; 1995
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="GAB98" name="GAB98">GAB98</a>
+ </td>
+ <td colspan="2">
+ Gabriel, Richard P., <em>Patterns of Software: Tales from the Software Community</em>, Oxford University
+ Press, 1998.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="GAR93" name="GAR93">GAR93</a>
+ </td>
+ <td colspan="2">
+ David Garlan and Mary Shaw. <em>An Introduction to Software Architecture</em>, SEI Technical Report
+ CMU/SEI-94-TR-21.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="HIC03" name="HIC03">HIC03</a>
+ </td>
+ <td colspan="2">
+ Hickey A., Davis, A. <em>Elicitation Technique Selection: How Do the Experts Do It?</em>, International
+ Conference on Requirements Engineering (RE03), Los Alamitos, California: IEEE Computer Society Press,
+ September 2003.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="HUL05" name="HUL05">HUL05</a>
+ </td>
+ <td colspan="2">
+ Hull, E., Jackson, K. and Dick, J. <em>Requirements Engineering</em>, Second Edition. Springer, 2005.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="IEP1471" name="IEP1471">IEP1471</a>
+ </td>
+ <td colspan="2">
+ IEEE <em>Recommended Practice for Architectural Description</em>, IEEE Std P1471, 2000.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="JAZZ" name="JAZZ">JAZZ</a>
+ </td>
+ <td colspan="2">
+ The <em>Eclipse Way</em> is among others available through the JAZZ Project,<br />
+ <a href="http://www.jazz.net">http://www.jazz.net</a>
+ </td>
+ </tr>
+ </tbody>
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="KAN96" name="KAN96">KAN96</a>
+ </td>
+ <td colspan="2">
+ Kaner, Sam <em>The Facilitator's Guide to Participatory Decision-Making</em>, New Society Publishers,
+ Gabriola Island, BC, 1996.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="KAT93" name="KAT93">KAT93</a>
+ </td>
+ <td colspan="2">
+ Katzenbach, J.R. & Smith, D.K. <em>The wisdom of teams: Creating the high-performance
+ organization</em>, Harvard Business School, Boston, 1993.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="KAZ00" name="KAZ00">KAZ00</a>
+ </td>
+ <td colspan="2">
+ Kazman, R., Carriere, S. J., Woods, S. G. <a href="http://www.sei.cmu.edu/staff/rkazman/annals-scenario.pdf">Toward a Discipline of Scenario-Based
+ Architectural Engineering</a>,(Get <a href="http://www.adobe.com/products/acrobat/alternate.html">Adobe
+ reader</a>.) <a href="http://manta.cs.vt.edu./ase/">Annals of Software Engineering</a>, Vol. 9, 2000, 5-33.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="KAZ04" name="KAZ04">KAZ04</a>
+ </td>
+ <td colspan="2">
+ Kazman, R., Kruchten, P., Nord, R., Tomayko, J. <em>Integrating Software-Architecture-Centric Methods
+ into the Rational Unified Process</em>, CMU-SEI Technical Reports, 2004.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="KER01" name="KER01">KER01</a>
+ </td>
+ <td colspan="2">
+ Norman L. Kerth. <em>Project Retrospectives: A Handbook for Team Reviews</em>, Dorset House Publishers, New
+ York, 2001.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="KRO03" name="KRO03">KRO03</a>
+ </td>
+ <td colspan="2">
+ Kroll, P. and Kruchten, P. <em>The Rational Unified Process Made Easy</em>, Addison Wesley, 2003.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ KRO05
+ </td>
+ <td colspan="2">
+ Kroll, P. and MacIsaac, B. <em>Agility and Discipline Made Easy</em>, Addison Wesley, 2005.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="KRU95" name="KRU95">KRU95</a>
+ </td>
+ <td colspan="2">
+ Kruchten, Phillipe B., <em>The 4+1 View Model of Architecture</em>, IEEE Software, vol. 12, no. 6, pp
+ 42-50, November 1995
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="LAR03" name="LAR03">LAR03</a>
+ </td>
+ <td colspan="2">
+ Larman, Craig <em>Agile and Iterative Development: A Manager's Guide</em>, Addison Wesley, 2003
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="MAR03" name="MAR03">MAR03</a>
+ </td>
+ <td colspan="2">
+ <p>
+ Marick, B., <em>Exploration Through Example</em>, <a href="http://www.testing.com/cgi-bin/blog/2003/08/21#agile-testing-project-1">http://www.testing.com/cgi-bin/blog/2003/08/21#agile-testing-project-1</a>
+ </p>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="MEY97" name="MEY97">MEY97</a>
+ </td>
+ <td colspan="2">
+ Meyer, B., <em>Object-Oriented Software Construction</em>, Prentice Hall, 1997
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <p>
+ <a id="NBG01" name="NBG01">NBG01</a>
+ </p>
+ </td>
+ <td colspan="2">
+ Eric J. Naiburg and Robert A. Maksimchuk. <em>UML for Database Design</em>, New York, NY: Addison Wesley,
+ 2001
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="OOP96" name="OOP96">OOP96</a>
+ </td>
+ <td colspan="2">
+ The 1996 ACM Conference on Object-Oriented Programs, Systems, Languages and Applications (OOPSLA), <em>The
+ Origins of Pattern Theory, the Future of the Theory, And The Generation of a Living World.</em>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top" width="12%">
+ </td>
+ <td width="10%">
+ </td>
+ <td style="PADDING-BOTTOM: 10px" width="78%">
+ See <a href="http://www.patternlanguage.com/archive/ieee/ieeetext.htm">http://www.patternlanguage.com/archive/ieee/ieeetext.htm</a>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="PMI04" name="PMI04">PMI04</a>
+ </td>
+ <td colspan="2">
+ Project Management Institute, <em>A Guide to the Project Management Body of Knowledge</em>, Third Edition,
+ 2004.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="RUP06" name="RUP06">RUP06</a>
+ </td>
+ <td colspan="2">
+ IBM Rational 2006. <em>The Rational Unified Process.</em>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top" width="12%">
+ </td>
+ <td width="10%">
+ </td>
+ <td style="PADDING-BOTTOM: 10px" width="78%">
+ A commercial methodology, also based on the Eclipse Process Framework, and advanced guidance on topics such
+ as business modeling, portfolio management, asset-based development, real-time design, user experience, and
+ so on.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="SCH04" name="SCH04">SCH04</a>
+ </td>
+ <td colspan="2">
+ Schwaber, K. <em>Agile Project Management with Scrum.</em> Microsoft Press 2004.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="SEI99" name="SEI99">SEI99</a>
+ </td>
+ <td colspan="2">
+ SEI <em>Software Risk Evaluation (SRE) Method Description, v2.0</em>SEI, 1999<br />
+ <a href="http://www.sei.cmu.edu/pub/documents/99.reports/pdf/99tr029-body.pdf#search="software risk evaluation"">http://www.sei.cmu.edu/pub/documents/99.reports/pdf/99tr029-body.pdf#search=%22software%20risk%20evaluation%22</a>
+ (Get <a href="http://www.adobe.com/products/acrobat/alternate.html">Adobe reader</a>.)
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="SHA05" name="SHA05">SHA05</a>
+ </td>
+ <td colspan="2">
+ Shalloway, J., Trott, J. <em>Design Patterns Explained</em> A New Perspective on Object-Oriented Design,
+ Second Edition, Addison Wesley, 2005
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="SHO06" name="SHO06">SHO06</a>
+ </td>
+ <td colspan="2">
+ Shore, James <em>Successful Software</em><br />
+ <a href="http://www.jamesshore.com/Blog/Continuous-Integration-on-a-Dollar-a-Day.html">http://www.jamesshore.com/Blog/Continuous-Integration-on-a-Dollar-a-Day.html</a>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="STZ07" name="STZ07">STZ07</a>
+ </td>
+ <td colspan="2">
+ Schatz , Bob - <span class="sans" style="FONT-STYLE: italic">Successful Sprint Reviews</span><br />
+ <a href="http://www.scrumalliance.org/articles/48-successful-sprint-reviews">http://www.scrumalliance.org/articles/48-successful-sprint-reviews</a>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="SUT06" name="SUT06">SUT06</a>
+ </td>
+ <td colspan="2">
+ Sutherland, <font face="Arial, Helvetica, sans-serif">Jeff <em>- Why the Three questions in the Daily Scrum
+ Meeting?</em></font><br />
+ <a href="http://jeffsutherland.com/scrum/2006/06/why-three-questions-in-daily-scrum.html">http://jeffsutherland.com/scrum/2006/06/why-three-questions-in-daily-scrum.html</a>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="TAV84" name="TAV84">TAV84</a>
+ </td>
+ <td colspan="2">
+ Tavalato, P., K. Vincena <em>A Prototyping Methodology and its Tool</em>, in Approaches to Prototyping, R.
+ Budde, ed., Berlin: Springer-Verlag, 1984, pp. 434-446
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="TEL06" name="TEL06">TEL06</a>
+ </td>
+ <td colspan="2">
+ Telelogic, 2006. <em>Get It Right the First Time: Writing Better Requirements.</em>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="THA00" name="THA00">THA00</a>
+ </td>
+ <td colspan="2">
+ Thayer, Richard H. and Dorfman, Merlin <em>Software Requirements Engineering Second Edition</em>,
+ IEEE Computer Society, 2000
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="UML05" name="UML05">UML05</a>
+ </td>
+ <td colspan="2">
+ OMG, 2005. <em>Unified Modeling Language 2.0: Superstructure.</em><br />
+ <a href="http://www.omg.org/docs/formal/05-07-04.pdf">http://www.omg.org/docs/formal/05-07-04.pdf</a> (Get
+ <a href="http://www.adobe.com/products/acrobat/alternate.html">Adobe reader</a>.)
+ </td>
+ </tr>
+ </tbody>
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="WIB04" name="WIB04">WIB04</a>
+ </td>
+ <td colspan="2">
+ Wiborg-Weber, D., Vignaud, J. L. <em>A Framework for Managing Component Based Development</em>, Telelogic
+ Whitepaper, 2004<br />
+ <a href="http://www.telelogic.com/download/index.cfm?id=4423">http://www.telelogic.com/download/index.cfm?id=4423</a>
+ </td>
+ </tr>
+ </tbody>
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="WIKP-MVC" name="WIKP-MVC">WIKP-MVC</a>
+ </td>
+ <td colspan="2">
+ Wikipedia <em>Model-view-controller</em><br />
+ <a href="http://en.wikipedia.org/wiki/Model-view-controller">http://en.wikipedia.org/wiki/Model-view-controller</a>
+ </td>
+ </tr>
+ </tbody>
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="WIKP-CI" name="WIKP-CI">WIKP-CI</a>
+ </td>
+ <td colspan="2">
+ Wikipedia <em>Continuous Integration</em><br />
+ <a href="http://en.wikipedia.org/wiki/Continuous_Integration">http://en.wikipedia.org/wiki/Continuous_Integration</a>
+ </td>
+ </tr>
+ </tbody>
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="YIP" name="YIP">YIP</a>
+ </td>
+ <td colspan="2">
+ YIP, Jason <em>It's Not Just Standing Up: Patterns of Daily Stand-up Meetings</em><br />
+ <a href="http://www.martinfowler.com/articles/itsNotJustStandingUp.html">http://www.martinfowler.com/articles/itsNotJustStandingUp.html</a>
+ </td>
+ </tr>
+ </tbody>
+</table></td>
+</tr>
+</table>
+</div>
+<table cellpadding="0" cellspacing="0" border="0" class="copyright">
+<tr>
+<td class="copyright"><p>
+ This program and the accompanying materials are made available under the<br />
+ <a href="http://www.eclipse.org/org/documents/epl-v10.php" target="_blank">Eclipse Public License v1.0</a> which
+ accompanies this distribution.
+</p><p/><p>
+ <a class="elementLink" href="./../../../openup/guidances/supportingmaterials/openup_copyright_C3031062.html" guid="_UaGfECcTEduSX6N2jUafGA">OpenUP Copyright</a>.
+</p></td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+</body>
+<script language="JavaScript" type="text/javascript">
+ contentPage.onload();
+ </script>
+</html>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/resources/risk_AF5840DA.html b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/resources/risk_AF5840DA.html
new file mode 100644
index 0000000..5bf63ba
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/resources/risk_AF5840DA.html
@@ -0,0 +1,257 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" lang="en" xml:lang="en">
+<head>
+<META http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>Concept: Risk</title>
+<meta content="Concept" name="uma.type">
+<meta content="risk" name="uma.name">
+<meta content="Risk" name="uma.presentationName">
+<meta name="element_type" content="concept">
+<meta content="description" name="filetype">
+<meta name="role" content="">
+<link type="text/css" href="./../../../css/default.css" rel="StyleSheet">
+<script language="JavaScript" type="text/javascript" src="./../../../scripts/ContentPageResource.js"></script><script language="JavaScript" type="text/javascript" src="./../../../scripts/ContentPageSection.js"></script><script language="JavaScript" type="text/javascript" src="./../../../scripts/ContentPageSubSection.js"></script><script language="JavaScript" type="text/javascript" src="./../../../scripts/ContentPageToolbar.js"></script><script language="JavaScript" type="text/javascript" src="./../../../scripts/contentPage.js"></script><script language="JavaScript" type="text/javascript">
+ var backPath = './../../../';
+ var imgPath = './../../../images/';
+ var nodeInfo=null;
+ contentPage.preload(imgPath, backPath, nodeInfo, '', false, false, false);
+ </script>
+</head>
+<body>
+<div id="breadcrumbs"></div>
+<table width="100%" cellspacing="0" cellpadding="0" border="0">
+<tr>
+<td valign="top"><a name="Top"></a>
+<div id="page-guid" value="_0bsLgMlgEdmt3adZL5Dmdw"></div>
+<table width="100%" cellpadding="0" cellspacing="0" border="0">
+<tr>
+<td nowrap="true" class="pageTitle">Concept: Risk</td><td width="100%">
+<div id="contentPageToolbar" align="right"></div>
+</td><td align="right" class="expandCollapseLink" width="100%"><a href="./../../../index.htm" name="mainIndex"></a><script src="./../../../scripts/treebrowser.js" type="text/javascript" language="JavaScript"></script></td>
+</tr>
+</table>
+<table cellspacing="0" cellpadding="0" border="0" width="100%">
+<tr>
+<td class="pageTitleSeparator"><img height="1" title="" alt="" src="./../../../images/shim.gif"></td>
+</tr>
+</table>
+<div class="overview">
+<table cellpadding="0" cellspacing="0" border="0" width="97%">
+<tr>
+<td width="50"><img title="" alt="" src="./../../../images/concept.gif"></td><td>
+<table cellpadding="0" cellspacing="0" border="0" class="overviewTable">
+<tr>
+<td valign="top">A risk is whatever may stand in the way of success, and is currently unknown or uncertain. Usually, a risk is qualified by the probability of its occurrence and the impact in the project, if it occurs.</td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Relationships</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Related Elements</th><td class="sectionTableCell">
+<ul>
+<li>
+<a href="./../../../openup/guidances/concepts/project_lifecycle_203F87.html" guid="_nSfVwCNYEdyCq8v2ZO4QcA">Project Lifecycle</a>
+</li>
+<li>
+<a href="./../../../openup/tasks/plan_the_project_A4A80C96.html" guid="_0lC70MlgEdmt3adZL5Dmdw">Plan Project</a>
+</li>
+<li>
+<a href="./../../../openup/tasks/manage_iteration_E4D93A64.html" guid="_8S2aICbYEdqh1LYUOGRh2A">Manage Iteration</a>
+</li>
+<li>
+<a href="./../../../openup/workproducts/risk_list_C4B6F290.html" guid="_Ckay8Cc_EduIsqH1Q6ZuqA">Risk List</a>
+</li>
+<li>
+<a href="./../../../openup/disciplines/project_management_AFB03A6.html" guid="_0TqQ4MlgEdmt3adZL5Dmdw">Project Management</a>
+</li>
+<li>
+<a href="./../../../openup/guidances/concepts/elaboration_phase_BE880435.html" guid="_2plxwBOMEduCNqgZdt_OaA">Elaboration Phase</a>
+</li>
+</ul>
+</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Main Description</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<td class="sectionTableSingleCell"><h1>
+ What is a Risk?
+</h1>
+<p>A risk is an uncertain event or condition that, if it occurs, will have a negative or positive effect on one or more
+project objectives [<a class="elementLinkWithUserText" href="./../../../openup/guidances/supportingmaterials/references_6CCF393.html#PMI04" guid="_9ToeIB83Edqsvps02rpOOg">PMI04</a>]. Project risks may be seen as threats or opportunities. The latter means
+that taking a calculated risk may bring, for example, competitive advantage for a product or organization.
+If there are benefits associated with an opportunity, then you can take certain degrees of risk for a project to
+be successful [<a class="elementLinkWithUserText" href="./../../../openup/guidances/supportingmaterials/references_6CCF393.html#SEI99" guid="_9ToeIB83Edqsvps02rpOOg">SEI99</a>].</p>
+<p>
+ In everyday life a risk is an exposure to loss or injury: A factor, thing, element, or course involving uncertain
+ danger. Similarly, in software development a risk is something that can compromise the success of a project.
+ Examples of potential sources of risk in software development are listed below (see [<a class="elementLinkWithUserText" href="./../../../openup/guidances/supportingmaterials/references_6CCF393.html#SEI99" guid="_9ToeIB83Edqsvps02rpOOg">SEI99</a>] for more details):
+</p>
+<ul>
+ <li>
+ Requirements
+ </li>
+ <li>
+ Design
+ </li>
+ <li>
+ Development process
+ </li>
+ <li>
+ Work environment
+ </li>
+ <li>
+ Resources
+ </li>
+ <li>
+ Contract
+ </li>
+ <li>
+ Project interdependencies
+ </li>
+ <li>
+ And so on
+ </li>
+</ul>
+<h1>
+ Risk Attributes
+</h1>
+<p>
+ You can record as much information as you like or need about your risks. You will find a list of common risk
+ attributes following.
+</p>
+<ul>
+ <li>
+ <b>Risk Description:</b> A description of the risk detailing the impact for the project if this risk
+ becomes a problem (that is, it becomes a reality).
+ </li>
+ <li>
+ <b>Risk Category</b>: Risk identification is usually more easily done when there is a "mental framework"
+ in place to ensure that potential areas of risk are not overlooked. One way of doing this is to divide risks into
+ categories (such as technical, project management, organizational, and external), to ensure that all aspects of the
+ project which are prone to risk are covered.
+ </li>
+ <li>
+ <b>Risk Type:</b> Used to classify the risk as:
+ </li>
+ <li style="LIST-STYLE-TYPE: none">
+ <ul>
+ <li>
+ <b>Direct risk</b>: A risk that the project has a large degree of control over
+ </li>
+ <li>
+ <b>Indirect risk</b>: A risk with little or no project control
+ </li>
+ </ul>
+ </li>
+ <li>
+ <b>Risk Probability:</b> How likely the risk event will happen. This is usually represented as a scale of
+ values (for example: High, Medium, Low). Probability is one of the most difficult quantities to judge accurately.
+ </li>
+ <li>
+ <b>Risk Impact</b> (level): If this risk becomes a problem, what will the impact on
+ the project be? This is not the actual <b>description</b> of the impact, but the <b>level</b> of impact. As the risk
+ probability, it is usually represented as a scale. This attribute is also sometimes called the
+ <b>severity</b> of the risk.
+ </li>
+ <li>
+ <b>Risk Magnitude</b>: To be able to rank and define which risks need to be mitigate first, the
+ <b>Risk Probability </b> and <b>Risk Impact</b> attributes are often combined in a
+ single <b>Risk</b> <b>Magnitude</b> indicator represented as a scale similar to the
+ combined attributes.
+ </li>
+</ul>
+<h1>
+ Risk Response Strategies
+</h1>
+<p>
+ The risk response should be in line with the significance of the risk. The strategies for handling risk cover two
+ main types: negative risks and positive risks (or opportunities). Common response strategies for negative risks or
+ threats include:
+</p>
+<ul>
+ <li>
+ <b>Avoid</b>: Reorganize the project so that it cannot be affected by that risk (for example, removing work)
+ </li>
+ <li>
+ <b>Mitigate</b>: Define actions to reduce the probability or the impact of the risk, removing it from the
+ top of the list
+ </li>
+ <li>
+ <b>Transfer</b>: Reorganize the project so that someone or something else bears the risk. It simply
+ gives another party responsibility for its management. It doesn't eliminate the risk.
+ </li>
+</ul>
+<p>
+ Common response strategies for positive risks or opportunities include:
+</p>
+<ul class="noindent">
+ <li>
+ <b>Exploit</b>: Add work or reorganize the project to make sure that the opportunity occurs (it
+ is the reverse of avoid)
+ </li>
+ <li>
+ <b>Enhance</b>: Define actions to increase the probability or the positive impact of the risk
+ (this is the reverse of mitigate)
+ </li>
+ <li>
+ <b>Share</b>: Allocate
+ the ownership of the opportunity to a third party who is best able to capture the opportunity for the
+ benefit of the project.
+ </li>
+</ul>
+<p>
+ Another response strategy for both threats or opportunities is to <b>Accept</b>: Decide to live with the
+ risk, and define a contingency plan.
+</p>
+<p>
+ Some scenarios for software development may help to make these concepts more clear:
+</p>
+<ul>
+ <li>
+ You need to use a new framework. A risk avoidance strategy could be to drop this new framework and use another
+ one that is already understood by the team.
+ </li>
+ <li>
+ The application you are developing needs to communicate with a legacy system. A risk transfer strategy would
+ be to have the legacy support team be responsible for providing the APIs to access the legacy system.
+ </li>
+ <li>
+ You need to use new middleware. A risk mitigation strategy could be to build a prototype using this new middleware
+ to validate that it will provide the features you need for your application.
+ </li>
+ <li>
+ Your integrator is the only one who knows how to integrate the different components of your application. A
+ contingency plan could be to identify a resource on another project that you could bring on if your integrator is
+ sick, leaves the company, and so on.
+ </li>
+</ul></td>
+</tr>
+</table>
+</div>
+<table cellpadding="0" cellspacing="0" border="0" class="copyright">
+<tr>
+<td class="copyright"><p>
+ This program and the accompanying materials are made available under the<br />
+ <a href="http://www.eclipse.org/org/documents/epl-v10.php" target="_blank">Eclipse Public License v1.0</a> which
+ accompanies this distribution.
+</p><p/><p>
+ <a class="elementLink" href="./../../../openup/guidances/supportingmaterials/openup_copyright_C3031062.html" guid="_UaGfECcTEduSX6N2jUafGA">OpenUP Copyright</a>.
+</p></td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+</body>
+<script language="JavaScript" type="text/javascript">
+ contentPage.onload();
+ </script>
+</html>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/resources/risk_list_33A6AE1E.html b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/resources/risk_list_33A6AE1E.html
new file mode 100644
index 0000000..4419c0e
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/resources/risk_list_33A6AE1E.html
@@ -0,0 +1,97 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" lang="en" xml:lang="en">
+<head>
+<META http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>Template: Risk List</title>
+<meta content="Template" name="uma.type">
+<meta content="risk_list" name="uma.name">
+<meta content="Risk List" name="uma.presentationName">
+<meta name="element_type" content="other">
+<meta content="description" name="filetype">
+<meta name="role" content="">
+<link type="text/css" href="./../../../css/default.css" rel="StyleSheet">
+<script language="JavaScript" type="text/javascript" src="./../../../scripts/ContentPageResource.js"></script><script language="JavaScript" type="text/javascript" src="./../../../scripts/ContentPageSection.js"></script><script language="JavaScript" type="text/javascript" src="./../../../scripts/ContentPageSubSection.js"></script><script language="JavaScript" type="text/javascript" src="./../../../scripts/ContentPageToolbar.js"></script><script language="JavaScript" type="text/javascript" src="./../../../scripts/contentPage.js"></script><script language="JavaScript" type="text/javascript">
+ var backPath = './../../../';
+ var imgPath = './../../../images/';
+ var nodeInfo=null;
+ contentPage.preload(imgPath, backPath, nodeInfo, '', false, false, false);
+ </script>
+</head>
+<body>
+<div id="breadcrumbs"></div>
+<table width="100%" cellspacing="0" cellpadding="0" border="0">
+<tr>
+<td valign="top"><a name="Top"></a>
+<div id="page-guid" value="_MIUO0C8FEduzydamRseoUw"></div>
+<table width="100%" cellpadding="0" cellspacing="0" border="0">
+<tr>
+<td nowrap="true" class="pageTitle">Template: Risk List</td><td width="100%">
+<div id="contentPageToolbar" align="right"></div>
+</td><td align="right" class="expandCollapseLink" width="100%"><a href="./../../../index.htm" name="mainIndex"></a><script src="./../../../scripts/treebrowser.js" type="text/javascript" language="JavaScript"></script></td>
+</tr>
+</table>
+<table cellspacing="0" cellpadding="0" border="0" width="100%">
+<tr>
+<td class="pageTitleSeparator"><img height="1" title="" alt="" src="./../../../images/shim.gif"></td>
+</tr>
+</table>
+<div class="overview">
+<table cellpadding="0" cellspacing="0" border="0" width="97%">
+<tr>
+<td width="50"><img title="" alt="" src="./../../../images/template.gif"></td><td>
+<table cellpadding="0" cellspacing="0" border="0" class="overviewTable">
+<tr>
+<td valign="top">A list or table containing risk attributes. As it is usual to rank risks by priority, spreadsheets may be an alternative to capture risks</td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Relationships</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Related Elements</th><td class="sectionTableCell">
+<ul>
+<li>
+<a href="./../../../openup/workproducts/risk_list_C4B6F290.html" guid="_Ckay8Cc_EduIsqH1Q6ZuqA">Risk List</a>
+</li>
+</ul>
+</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Description</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Attached Files</th><td class="sectionTableCell">
+<UL>
+<li>
+<a target="_blank" href="resources/risk_list_tpl.xls">risk_list_tpl.xls</a>
+</li>
+</UL>
+</td>
+</tr>
+</table>
+</div>
+<table cellpadding="0" cellspacing="0" border="0" class="copyright">
+<tr>
+<td class="copyright"><p>
+ This program and the accompanying materials are made available under the<br />
+ <a href="http://www.eclipse.org/org/documents/epl-v10.php" target="_blank">Eclipse Public License v1.0</a> which
+ accompanies this distribution.
+</p><p/><p>
+ <a class="elementLink" href="./../../../openup/guidances/supportingmaterials/openup_copyright_C3031062.html" guid="_UaGfECcTEduSX6N2jUafGA">OpenUP Copyright</a>.
+</p></td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+</body>
+<script language="JavaScript" type="text/javascript">
+ contentPage.onload();
+ </script>
+</html>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/resources/risk_list_C4B6F290.html b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/resources/risk_list_C4B6F290.html
new file mode 100644
index 0000000..9feec4a
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/resources/risk_list_C4B6F290.html
@@ -0,0 +1,214 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" lang="en" xml:lang="en">
+<head>
+<META http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>Artifact: Risk List</title>
+<meta content="Artifact" name="uma.type">
+<meta content="risk_list" name="uma.name">
+<meta content="Risk List" name="uma.presentationName">
+<meta content="@Type:@Name:@DisplayName" name="uma.category">
+<meta content="WorkProductType:project_data:Project Data" name="uma.category">
+<meta content="Artifact" name="element_type">
+<meta content="description" name="filetype">
+<meta name="role" content="">
+<link type="text/css" href="./../../css/default.css" rel="StyleSheet">
+<script language="JavaScript" type="text/javascript" src="./../../scripts/ContentPageResource.js"></script><script language="JavaScript" type="text/javascript" src="./../../scripts/ContentPageSection.js"></script><script language="JavaScript" type="text/javascript" src="./../../scripts/ContentPageSubSection.js"></script><script language="JavaScript" type="text/javascript" src="./../../scripts/ContentPageToolbar.js"></script><script language="JavaScript" type="text/javascript" src="./../../scripts/contentPage.js"></script><script language="JavaScript" type="text/javascript">
+ var backPath = './../../';
+ var imgPath = './../../images/';
+ var nodeInfo=null;
+ contentPage.preload(imgPath, backPath, nodeInfo, '', false, false, false);
+ </script>
+</head>
+<body>
+<div id="breadcrumbs"></div>
+<table width="100%" cellspacing="0" cellpadding="0" border="0">
+<tr>
+<td valign="top"><a name="Top"></a>
+<div id="page-guid" value="_Ckay8Cc_EduIsqH1Q6ZuqA"></div>
+<table width="100%" cellpadding="0" cellspacing="0" border="0">
+<tr>
+<td nowrap="true" class="pageTitle">Artifact: Risk List</td><td width="100%">
+<div id="contentPageToolbar" align="right"></div>
+</td><td align="right" class="expandCollapseLink" width="100%"><a href="./../../index.htm" name="mainIndex"></a><script src="./../../scripts/treebrowser.js" type="text/javascript" language="JavaScript"></script></td>
+</tr>
+</table>
+<table cellspacing="0" cellpadding="0" border="0" width="100%">
+<tr>
+<td class="pageTitleSeparator"><img height="1" title="" alt="" src="./../../images/shim.gif"></td>
+</tr>
+</table>
+<div class="overview">
+<table cellpadding="0" cellspacing="0" border="0" width="97%">
+<tr>
+<td width="50"><img title="" alt="" src="./../../images/artifact.gif"></td><td>
+<table cellpadding="0" cellspacing="0" border="0" class="overviewTable">
+<tr>
+<td valign="top">This artifact is a list of known and open risks to the project, sorted in order of importance and associated with specific mitigation or contingency actions.</td>
+</tr>
+<tr>
+<td>Domains: <a href="./../../openup/domains/project_management_F6DB5D59.html" guid="_QxjGYMWfEdqiT9CqkRksWQ">Project Management</a>
+<br>Work Product Kinds: <a href="./../../openup/workproducttypes/project_data_12F2C55.html" guid="_hOaxYDz7Edq03rqPoNVoKg">Project Data</a></td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Purpose</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<td class="sectionTableSingleCell">To capture the perceived risks to the success of the project.</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Relationships</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Roles</th><td width="42%" class="sectionTableCell"><span class="sectionTableCellHeading">Responsible:
+ </span>
+<ul>
+<li>
+<a href="./../../openup/roles/project_manager_E657F936.html" guid="_0a0o0MlgEdmt3adZL5Dmdw">Project Manager</a>
+</li>
+</ul>
+</td><td class="sectionTableCell"><span class="sectionTableCellHeading">Modified By:
+ </span>
+<ul>
+<li>
+<a href="./../../openup/roles/project_manager_E657F936.html" guid="_0a0o0MlgEdmt3adZL5Dmdw">Project Manager</a>
+</li>
+</ul>
+</td>
+</tr>
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Tasks</th><td width="42%" class="sectionTableCell"><span class="sectionTableCellHeading">Input To:
+ </span>
+<ul>
+<li>
+<a href="./../../openup/tasks/manage_iteration_E4D93A64.html" guid="_8S2aICbYEdqh1LYUOGRh2A">Manage Iteration</a>
+</li>
+</ul>
+<br>
+<ul>
+<li>
+<a href="./../../openup/tasks/plan_iteration_957C90DC.html" guid="_0keUEMlgEdmt3adZL5Dmdw">Plan Iteration</a>
+</li>
+<li>
+<a href="./../../openup/tasks/plan_the_project_A4A80C96.html" guid="_0lC70MlgEdmt3adZL5Dmdw">Plan Project</a>
+</li>
+</ul>
+</td><td class="sectionTableCell"><span class="sectionTableCellHeading">Output From:
+ </span>
+<ul>
+<li>
+<a href="./../../openup/tasks/manage_iteration_E4D93A64.html" guid="_8S2aICbYEdqh1LYUOGRh2A">Manage Iteration</a>
+</li>
+<li>
+<a href="./../../openup/tasks/plan_iteration_957C90DC.html" guid="_0keUEMlgEdmt3adZL5Dmdw">Plan Iteration</a>
+</li>
+<li>
+<a href="./../../openup/tasks/plan_the_project_A4A80C96.html" guid="_0lC70MlgEdmt3adZL5Dmdw">Plan Project</a>
+</li>
+</ul>
+</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Description</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Main Description</th><td class="sectionTableCell"><p>
+ This list identifies, in decreasing order of priority, all the <a class="elementLinkWithUserText" href="./../../openup/guidances/termdefinitions/risk_33255339.html" guid="_ii2LUEvGEdunZcj9T5hrMQ">risks</a> associated to a project. It serves as a focal point for project
+ activities and is the basis around which iterations are organized.
+</p>
+<p>
+ See <a class="elementLinkWithType" href="./../../openup/guidances/concepts/risk_AF5840DA.html" guid="_0bsLgMlgEdmt3adZL5Dmdw">Concept: Risk</a> for more details.<!--EndFragment-->
+</p></td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Illustrations </div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Templates</th><td class="sectionTableCell">
+<ul>
+<li>
+<a href="./../../openup/guidances/templates/risk_list_33A6AE1E.html" guid="_MIUO0C8FEduzydamRseoUw">Risk List</a>
+</li>
+</ul>
+</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Key Considerations</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<td class="sectionTableSingleCell"><p>
+ This list should capture the critical and serious risks. If you find this list extending beyond 20, carefully consider
+ whether they are really serious risks. Tracking more than 20 risks is an onerous task.
+</p></td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Tailoring</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Representation Options</th><td class="sectionTableCell"><h4>
+ Option: list of risks captured in the project plan
+</h4>
+<p>
+ In this approach you put the overall risk list in the project plan. The iteration plan will contain only the tasks you
+ will be doing during the iteration to mitigate the risks. This will ensure that the iteration plan contains only
+ iteration information. The project plan has to be revisited constantly as you update risks.
+</p></td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">More Information</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Checklists</th><td class="sectionTableCell">
+<ul>
+<li>
+<a href="./../../openup/guidances/checklists/risk_list_33460EDD.html" guid="_7BZa0DIdEduDTv4Y1akVTA">Risk List</a>
+</li>
+</ul>
+</td>
+</tr>
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Concepts</th><td class="sectionTableCell">
+<ul>
+<li>
+<a href="./../../openup/guidances/concepts/risk_AF5840DA.html" guid="_0bsLgMlgEdmt3adZL5Dmdw">Risk</a>
+</li>
+</ul>
+</td>
+</tr>
+</table>
+</div>
+<table cellpadding="0" cellspacing="0" border="0" class="copyright">
+<tr>
+<td class="copyright"><p>
+ This program and the accompanying materials are made available under the<br />
+ <a href="http://www.eclipse.org/org/documents/epl-v10.php" target="_blank">Eclipse Public License v1.0</a> which
+ accompanies this distribution.
+</p><p/><p>
+ <a class="elementLink" href="./../../openup/guidances/supportingmaterials/openup_copyright_C3031062.html" guid="_UaGfECcTEduSX6N2jUafGA">OpenUP Copyright</a>.
+</p></td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+</body>
+<script language="JavaScript" type="text/javascript">
+ contentPage.onload();
+ </script>
+</html>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/resources/work_item_prioritization_diagram.jpg b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/resources/work_item_prioritization_diagram.jpg
new file mode 100644
index 0000000..12f9048
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/resources/work_item_prioritization_diagram.jpg
Binary files differ
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/resources/work_items_list_39D03CC8.html b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/resources/work_items_list_39D03CC8.html
new file mode 100644
index 0000000..bbc5499
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/guidelines/resources/work_items_list_39D03CC8.html
@@ -0,0 +1,339 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" lang="en" xml:lang="en">
+<head>
+<META http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>Artifact: Work Items List</title>
+<meta content="Artifact" name="uma.type">
+<meta content="work_items_list" name="uma.name">
+<meta content="Work Items List" name="uma.presentationName">
+<meta content="@Type:@Name:@DisplayName" name="uma.category">
+<meta content="WorkProductType:project_data:Project Data" name="uma.category">
+<meta content="Artifact" name="element_type">
+<meta content="description" name="filetype">
+<meta name="role" content="">
+<link type="text/css" href="./../../css/default.css" rel="StyleSheet">
+<script language="JavaScript" type="text/javascript" src="./../../scripts/ContentPageResource.js"></script><script language="JavaScript" type="text/javascript" src="./../../scripts/ContentPageSection.js"></script><script language="JavaScript" type="text/javascript" src="./../../scripts/ContentPageSubSection.js"></script><script language="JavaScript" type="text/javascript" src="./../../scripts/ContentPageToolbar.js"></script><script language="JavaScript" type="text/javascript" src="./../../scripts/contentPage.js"></script><script language="JavaScript" type="text/javascript">
+ var backPath = './../../';
+ var imgPath = './../../images/';
+ var nodeInfo=null;
+ contentPage.preload(imgPath, backPath, nodeInfo, '', false, false, false);
+ </script>
+</head>
+<body>
+<div id="breadcrumbs"></div>
+<table width="100%" cellspacing="0" cellpadding="0" border="0">
+<tr>
+<td valign="top"><a name="Top"></a>
+<div id="page-guid" value="_rGNWsCbSEdqh1LYUOGRh2A"></div>
+<table width="100%" cellpadding="0" cellspacing="0" border="0">
+<tr>
+<td nowrap="true" class="pageTitle">Artifact: Work Items List</td><td width="100%">
+<div id="contentPageToolbar" align="right"></div>
+</td><td align="right" class="expandCollapseLink" width="100%"><a href="./../../index.htm" name="mainIndex"></a><script src="./../../scripts/treebrowser.js" type="text/javascript" language="JavaScript"></script></td>
+</tr>
+</table>
+<table cellspacing="0" cellpadding="0" border="0" width="100%">
+<tr>
+<td class="pageTitleSeparator"><img height="1" title="" alt="" src="./../../images/shim.gif"></td>
+</tr>
+</table>
+<div class="overview">
+<table cellpadding="0" cellspacing="0" border="0" width="97%">
+<tr>
+<td width="50"><img title="" alt="" src="./../../images/artifact.gif"></td><td>
+<table cellpadding="0" cellspacing="0" border="0" class="overviewTable">
+<tr>
+<td valign="top">This artifact contains a list of all scheduled work to be done within the project, as well as proposed work that may affect the product in this or future projects. Each work item may contain references to information relevant to carry out the work described within the work item.</td>
+</tr>
+<tr>
+<td>Domains: <a href="./../../openup/domains/project_management_F6DB5D59.html" guid="_QxjGYMWfEdqiT9CqkRksWQ">Project Management</a>
+<br>Work Product Kinds: <a href="./../../openup/workproducttypes/project_data_12F2C55.html" guid="_hOaxYDz7Edq03rqPoNVoKg">Project Data</a></td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Purpose</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<td class="sectionTableSingleCell">To collect all requests for work that will potentially be taken on within the project, so work can be prioritized, effort
+estimated and progress tracked.</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Relationships</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Roles</th><td width="42%" class="sectionTableCell"><span class="sectionTableCellHeading">Responsible:
+ </span>
+<ul>
+<li>
+<a href="./../../openup/roles/project_manager_E657F936.html" guid="_0a0o0MlgEdmt3adZL5Dmdw">Project Manager</a>
+</li>
+</ul>
+</td><td class="sectionTableCell"><span class="sectionTableCellHeading">Modified By:
+ </span>
+<ul>
+<li>
+<a href="./../../openup/roles/analyst_39D7C49B.html" guid="_0VxJsMlgEdmt3adZL5Dmdw">Analyst</a>
+</li>
+<li>
+<a href="./../../openup/roles/any_role_C36B701F.html" guid="_0dsWoMlgEdmt3adZL5Dmdw">Any Role</a>
+</li>
+<li>
+<a href="./../../openup/roles/developer_C633AB7.html" guid="_0YDosMlgEdmt3adZL5Dmdw">Developer</a>
+</li>
+<li>
+<a href="./../../openup/roles/project_manager_E657F936.html" guid="_0a0o0MlgEdmt3adZL5Dmdw">Project Manager</a>
+</li>
+<li>
+<a href="./../../openup/roles/tester_9859B590.html" guid="_0ZM4MclgEdmt3adZL5Dmdw">Tester</a>
+</li>
+</ul>
+</td>
+</tr>
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Tasks</th><td width="42%" class="sectionTableCell"><span class="sectionTableCellHeading">Input To:
+ </span>
+<ul>
+<li>
+<a href="./../../openup/tasks/assess_results_EC34D88D.html" guid="_0l53cMlgEdmt3adZL5Dmdw">Assess Results</a>
+</li>
+<li>
+<a href="./../../openup/tasks/find_and_outline_requirements_90D272B9.html" guid="_P9cMUPV_EdmdHa9MmVPgqQ">Find and Outline Requirements</a>
+</li>
+<li>
+<a href="./../../openup/tasks/manage_iteration_E4D93A64.html" guid="_8S2aICbYEdqh1LYUOGRh2A">Manage Iteration</a>
+</li>
+<li>
+<a href="./../../openup/tasks/plan_iteration_957C90DC.html" guid="_0keUEMlgEdmt3adZL5Dmdw">Plan Iteration</a>
+</li>
+<li>
+<a href="./../../openup/tasks/plan_the_project_A4A80C96.html" guid="_0lC70MlgEdmt3adZL5Dmdw">Plan Project</a>
+</li>
+</ul>
+<br>
+<ul>
+<li>
+<a href="./../../openup/tasks/define_vision_9D36CF2F.html" guid="_0fOAoMlgEdmt3adZL5Dmdw">Define Vision</a>
+</li>
+<li>
+<a href="./../../openup/tasks/implement_test_scripts_26F00282.html" guid="_0jO98MlgEdmt3adZL5Dmdw">Implement Test Scripts</a>
+</li>
+<li>
+<a href="./../../openup/tasks/request_change_A048C387.html" guid="_0mwzEclgEdmt3adZL5Dmdw">Request Change</a>
+</li>
+</ul>
+</td><td class="sectionTableCell"><span class="sectionTableCellHeading">Output From:
+ </span>
+<ul>
+<li>
+<a href="./../../openup/tasks/assess_results_EC34D88D.html" guid="_0l53cMlgEdmt3adZL5Dmdw">Assess Results</a>
+</li>
+<li>
+<a href="./../../openup/tasks/define_vision_9D36CF2F.html" guid="_0fOAoMlgEdmt3adZL5Dmdw">Define Vision</a>
+</li>
+<li>
+<a href="./../../openup/tasks/find_and_outline_requirements_90D272B9.html" guid="_P9cMUPV_EdmdHa9MmVPgqQ">Find and Outline Requirements</a>
+</li>
+<li>
+<a href="./../../openup/tasks/manage_iteration_E4D93A64.html" guid="_8S2aICbYEdqh1LYUOGRh2A">Manage Iteration</a>
+</li>
+<li>
+<a href="./../../openup/tasks/plan_iteration_957C90DC.html" guid="_0keUEMlgEdmt3adZL5Dmdw">Plan Iteration</a>
+</li>
+<li>
+<a href="./../../openup/tasks/plan_the_project_A4A80C96.html" guid="_0lC70MlgEdmt3adZL5Dmdw">Plan Project</a>
+</li>
+<li>
+<a href="./../../openup/tasks/request_change_A048C387.html" guid="_0mwzEclgEdmt3adZL5Dmdw">Request Change</a>
+</li>
+<li>
+<a href="./../../openup/tasks/run_developer_tests_73D7DBC4.html" guid="_0iYCUMlgEdmt3adZL5Dmdw">Run Developer Tests</a>
+</li>
+<li>
+<a href="./../../openup/tasks/run_tests_49698054.html" guid="_0jVEkMlgEdmt3adZL5Dmdw">Run Tests</a>
+</li>
+</ul>
+</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Description</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Main Description</th><td class="sectionTableCell"><p>
+ This artifact provides a focal point for the entire team:
+</p>
+<ul>
+ <li>
+ It provides one list containing all requests for additional capabilities or enhancement for that application. Note
+ that some of these requests may never be implemented, or be implemented in later projects
+ </li>
+ <li>
+ It provides one list of all the work to be prioritized, estimated, and assigned within the project. The risk list
+ is prioritized separately.
+ </li>
+ <li>
+ It provides one place to go to for the development team to understand what <a class="elementLink" href="./../../openup/guidances/concepts/micro_increments_C8773066.html" guid="_S80VwCNbEdyCq8v2ZO4QcA">Micro-Increments</a> need to be delivered, get references to material required
+ to carry out the work, and one place to go to report progress made.
+ </li>
+</ul>
+<p>
+ These are the typical work items that go into this list:
+</p>
+<ul>
+ <li>
+ Use cases (and references to use-case specifications)
+ </li>
+ <li>
+ Supporting requirements
+ </li>
+ <li>
+ Changes and enhancement requests
+ </li>
+ <li>
+ Defects
+ </li>
+ <li>
+ Development tasks
+ </li>
+</ul>
+<p>
+ Work items can be very large in scope, especially when capturing requests for enhancements, such as “Support Financial
+ Planning” for a personal finance application. To allow the application to be developed in micro-increments, work items
+ are analyzed and broken down into smaller work items so they can be assigned to an iteration, such as a use-case
+ scenario for “Calculate Net Worth”. Further breakdown may be required to identify suitable tasks to be assigned to
+ developers, such as “Develop UI for Calculate Net Worth”. This means that work items often have parent/child
+ relationships, where the lowest level is a specification and tracking device for micro-increments.
+</p><p/><p>
+ Work Items should contain estimates, see <a class="elementLinkWithType" href="./../../openup/guidances/guidelines/work_items_list_32AC6ABD.html" guid="_7vEXEMA4EdqSgKaj2SZBmg">Guideline: Managing Work Items</a> and <a class="elementLinkWithType" href="./../../openup/guidances/guidelines/agile_estimation_A4EF42B3.html" guid="_CGHskBEdEdqY7JB6N6CW2w">Guideline: Agile Estimation</a>.
+</p></td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Illustrations </div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Templates</th><td class="sectionTableCell">
+<ul>
+<li>
+<a href="./../../openup/guidances/templates/work_items_list_B30CEE46.html" guid="_QwUJYDg0Edu4E8ZdmlYjtA">Work Items List</a>
+</li>
+</ul>
+</td>
+</tr>
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Reports</th><td class="sectionTableCell">
+<ul>
+<li>
+<a href="./../../openup/guidances/reports/project_burndown_206E4670.html" guid="_ePrt8Dj3EduxovfWMDsntw">Project Burndown</a>
+</li>
+<li>
+<a href="./../../openup/guidances/reports/iteration_burndown_9C1C96F5.html" guid="_uAzgkDg3Edu4E8ZdmlYjtA">Iteration Burndown</a>
+</li>
+</ul>
+</td>
+</tr>
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Examples</th><td class="sectionTableCell">
+<ul>
+<li>
+<a href="./../../openup/guidances/examples/work_items_list_F527B77D.html" guid="_nHomIDgzEdu4E8ZdmlYjtA">Work Items List</a>
+</li>
+</ul>
+</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Tailoring</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Representation Options</th><td class="sectionTableCell"><h3>
+ As a spreadsheet or database
+</h3>
+<p>
+ The Work Items List can be captured as a separate artifact, represented by a spreadsheet or database table. See <a class="elementLinkWithType" href="./../../openup/guidances/examples/work_items_list_F527B77D.html" guid="_nHomIDgzEdu4E8ZdmlYjtA">Example: Work Items List</a>.
+</p>
+<h3>
+ In specific tools
+</h3>
+<p>
+ Project Management, Requirements Management and Change Request tools are options to capture the list of work to be
+ done.
+</p>
+<h3>
+ As part of the Iteration Plan
+</h3>
+<p>
+ The <a class="elementLinkWithType" href="./../../openup/workproducts/iteration_plan_B46FED39.html" guid="_0aQBEslgEdmt3adZL5Dmdw">Artifact: Iteration Plan</a> typically references work items that are assigned to that
+ iteration. If the team is capturing the iteration plan on a whiteboard, for example, the team may choose to reference
+ high-level work items in the Work Items List that are assigned to the iteration, and maintain low-level child work
+ items used to track day-to-day work only within an iteration plan.<br />
+</p></td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">More Information</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Checklists</th><td class="sectionTableCell">
+<ul>
+<li>
+<a href="./../../openup/guidances/checklists/work_items_list_F9443B37.html" guid="_xlrdEAVtEdy3F_fZDaPZVA">Work Items List</a>
+</li>
+</ul>
+</td>
+</tr>
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Concepts</th><td class="sectionTableCell">
+<ul>
+<li>
+<a href="./../../openup/guidances/concepts/micro_increments_C8773066.html" guid="_S80VwCNbEdyCq8v2ZO4QcA">Micro-Increments</a>
+</li>
+</ul>
+</td>
+</tr>
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Guidelines</th><td class="sectionTableCell">
+<ul>
+<li>
+<a href="./../../openup/guidances/guidelines/work_items_list_32AC6ABD.html" guid="_7vEXEMA4EdqSgKaj2SZBmg">Managing Work Items</a>
+</li>
+<li>
+<a href="./../../openup/guidances/guidelines/agile_estimation_A4EF42B3.html" guid="_CGHskBEdEdqY7JB6N6CW2w">Agile Estimation</a>
+</li>
+<li>
+<a href="./../../openup/guidances/guidelines/prioritizing_work_items_A12C9BEC.html" guid="_oVMZADSoEdy07ZJqOGUGaQ">Prioritizing Work Items</a>
+</li>
+</ul>
+</td>
+</tr>
+</table>
+</div>
+<table cellpadding="0" cellspacing="0" border="0" class="copyright">
+<tr>
+<td class="copyright"><p>
+ This program and the accompanying materials are made available under the<br />
+ <a href="http://www.eclipse.org/org/documents/epl-v10.php" target="_blank">Eclipse Public License v1.0</a> which
+ accompanies this distribution.
+</p><p/><p>
+ <a class="elementLink" href="./../../openup/guidances/supportingmaterials/openup_copyright_C3031062.html" guid="_UaGfECcTEduSX6N2jUafGA">OpenUP Copyright</a>.
+</p></td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+</body>
+<script language="JavaScript" type="text/javascript">
+ contentPage.onload();
+ </script>
+</html>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/practices/iterative_development_practice.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/practices/iterative_development_practice.xmi
new file mode 100644
index 0000000..6852422
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/practices/iterative_development_practice.xmi
@@ -0,0 +1,9 @@
+<?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.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="-Yvy3AKQTjSqBPNxsWkizkQ"
+ name="iterative_development_practice,_LR_g4J9WEdy3Nc4rvuj7bA" guid="-Yvy3AKQTjSqBPNxsWkizkQ">
+ <mainDescription>[*** this can remain as a placeholder for now.&nbsp; After EPF's enhanced support for publishing practice guidance is
+completed, this is where the practice will be defined. ***]</mainDescription>
+</org.eclipse.epf.uma:PracticeDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/reports/iteration_burndown.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/reports/iteration_burndown.xmi
new file mode 100644
index 0000000..14f1bba
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/reports/iteration_burndown.xmi
@@ -0,0 +1,38 @@
+<?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: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="-Aw8p59vJ9rWsOV82rljQiQ"
+ name="iteration_burndown,_uAzgkDg3Edu4E8ZdmlYjtA" guid="-Aw8p59vJ9rWsOV82rljQiQ"
+ changeDate="2006-11-03T10:59:14.929-0500" version="1.0.0">
+ <mainDescription><p>
+ The iteration burndown report is&nbsp;the primary tool for understanding the status of the current iteration. It shows
+ the trend for how much work is left to do within the iteration. This is accomplished by adding the estimated effort
+ left for each of the Work Items to be addressed within the iteration and showing how the estimated effort is changing
+ over the duration of the iteration. The iteration backlog should be updated frequently, preferably daily.
+</p>
+<p>
+ These factors affect the team’s assessment of how much work remains:
+</p>
+<ul>
+ <li>
+ Work that has been completed, which means there is less work remaining.
+ </li>
+ <li>
+ The developer responsible for a Work Item changes the assessment of effort required to complete the Work Item. This
+ should be expected, because we typically understand what it really takes to complete a task after we have done a
+ subset of the task.&nbsp;It's common for estimates of the work remaining to increase in the beginning of the
+ iteration, especially for inexperienced teams, because they often underestimate efforts. Expect estimates to
+ continue changing as teams become more experienced, but the modifications are upward as often as downward.
+ </li>
+</ul>
+<p>
+ Daily or frequent updates of the iteration burndown report allow the team to react to changes. For example, changes can
+ include cutting the project scope by removing Work Items from the iteration, reducing the ambition level associated
+ with a Work Item, or finding better ways of approaching Work Items, such as having an expert team member help with
+ difficult Work Items.
+</p>
+<p>
+ See&nbsp;<a class="elementLink" href="./../../../openup/guidances/examples/iteration_burndown_report_example_1AE62791.html" guid="_GtGisDcGEdyTZ9G7ByfQTw">Iteration Burndown Report</a> for&nbsp;an example of an iteration burndown report.<br />
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/reports/resources/ex_iteration_burndown.xls b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/reports/resources/ex_iteration_burndown.xls
new file mode 100644
index 0000000..67cb1b6
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/reports/resources/ex_iteration_burndown.xls
Binary files differ
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/roadmaps/how_to_adopt.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/roadmaps/how_to_adopt.xmi
new file mode 100644
index 0000000..6efbbfc
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/roadmaps/how_to_adopt.xmi
@@ -0,0 +1,21 @@
+<?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: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="-hWKKNia-vOmQZTZWO24u5w"
+ name="how_to_adopt,_ERIDQOMPEdyM47cGD2jiaQ" guid="-hWKKNia-vOmQZTZWO24u5w" changeDate="2008-02-17T08:09:46.937-0500"
+ version="7.2.0">
+ <mainDescription><h3>
+ Getting Started&nbsp;
+</h3>
+<p>
+ TODO:&nbsp; Describe how to 'read' this practice.......provide description with links to appropriate content to help
+ someone get started with this practice
+</p>
+<h3>
+ Common Pitfalls
+</h3>
+<p>
+ TBD
+</p><br /></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/supportingmaterials/release_info_iterative_dev.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/supportingmaterials/release_info_iterative_dev.xmi
new file mode 100644
index 0000000..3ee69c8
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/supportingmaterials/release_info_iterative_dev.xmi
@@ -0,0 +1,23 @@
+<?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="-WeT7CrjLCAbaJKlpVk3O8w"
+ name="new_supporting_material,_TFhnsMN-Edy3nv0ZK8D4GQ" guid="-WeT7CrjLCAbaJKlpVk3O8w"
+ changeDate="2008-01-15T10:29:47.765-0500">
+ <mainDescription><h3>
+ Iterative Development Practice
+</h3>
+<p>
+ Version 1.0
+</p>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p>
+ [*** NOT YET RELEASED ***]
+ </p>
+ <p>
+ This is the initial release of this practice.
+ </p><br />
+ <br />
+</blockquote><br /></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/templates/iteration_plan.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/templates/iteration_plan.xmi
new file mode 100644
index 0000000..026d8ec
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/templates/iteration_plan.xmi
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:GuidanceDescription 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="_Z_bUIMM2EdmSIPI87WLu3g"
+ name="iteration_plan,_0dBoQMlgEdmt3adZL5Dmdw" guid="_Z_bUIMM2EdmSIPI87WLu3g" changeDate="2006-05-09T00:49:33.210+0100">
+ <attachments>resources/iteration_plan_tpl.dot</attachments>
+</org.eclipse.epf.uma:GuidanceDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/templates/resources/iteration_plan_tpl.dot b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/templates/resources/iteration_plan_tpl.dot
new file mode 100644
index 0000000..7bc6b05
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/templates/resources/iteration_plan_tpl.dot
Binary files differ
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/templates/resources/work_items_list_tpl.xls b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/templates/resources/work_items_list_tpl.xls
new file mode 100644
index 0000000..9f0b462
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/templates/resources/work_items_list_tpl.xls
Binary files differ
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/templates/work_items_list.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/templates/work_items_list.xmi
new file mode 100644
index 0000000..c8503ea
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/templates/work_items_list.xmi
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:GuidanceDescription 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="-mPA7vone29k1OvF_1rACjg"
+ name="work_items_list,_QwUJYDg0Edu4E8ZdmlYjtA" guid="-mPA7vone29k1OvF_1rACjg">
+ <attachments>resources/work_items_list_tpl.xls</attachments>
+</org.eclipse.epf.uma:GuidanceDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/termdefinitions/iteration.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/termdefinitions/iteration.xmi
new file mode 100644
index 0000000..d728919
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/termdefinitions/iteration.xmi
@@ -0,0 +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.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="-_G0VvVOdMoajk615LwFtxg"
+ name=",_ZBUnMEvFEdunZcj9T5hrMQ" guid="-_G0VvVOdMoajk615LwFtxg" changeDate="2006-09-24T06:23:38.618-0700">
+ <mainDescription>Short and time-boxed division of a project. Iterations allow to demonstrate incremental value and obtain early and
+continuous feedback</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/termdefinitions/iteration_burndown.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/termdefinitions/iteration_burndown.xmi
new file mode 100644
index 0000000..d8119b0
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/termdefinitions/iteration_burndown.xmi
@@ -0,0 +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.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="-3G3HV0opAmFWGxYgsD5AhA"
+ name=",_8b20EEvvEdunZcj9T5hrMQ" guid="-3G3HV0opAmFWGxYgsD5AhA" version="7.2.0">
+ <mainDescription>A&nbsp;primary report for understanding the status of an iteration. It shows the trend for how much work is left to do
+within that iteration.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/termdefinitions/point.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/termdefinitions/point.xmi
new file mode 100644
index 0000000..c5a5187
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/termdefinitions/point.xmi
@@ -0,0 +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.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="-oShmMITo9RIi1AzACWI9vw"
+ name="new_term_definition,_MvOuAEvGEdunZcj9T5hrMQ" guid="-oShmMITo9RIi1AzACWI9vw"
+ changeDate="2006-09-24T13:59:48.289-0400" version="7.2.0">
+ <mainDescription>A relative measure of size that is typically used for Agile estimation.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/termdefinitions/velocity.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/termdefinitions/velocity.xmi
new file mode 100644
index 0000000..7ad5b41
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/termdefinitions/velocity.xmi
@@ -0,0 +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.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="-mgWkuUy3q0zzFaxE7DY1ag"
+ name=",_Nj2hsEvuEdunZcj9T5hrMQ" guid="-mgWkuUy3q0zzFaxE7DY1ag">
+ <mainDescription>A&nbsp;key metric used for iteration planning. It indicates how many points are delivered upon within an iteration for a
+certain team and project.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/termdefinitions/work_item.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/termdefinitions/work_item.xmi
new file mode 100644
index 0000000..b55c26b
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/termdefinitions/work_item.xmi
@@ -0,0 +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.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="-1Oc9t_TLaBgW_YLugZcq7w"
+ name="work_item,_jyVgcEvKEdunZcj9T5hrMQ" guid="-1Oc9t_TLaBgW_YLugZcq7w" changeDate="2006-09-24T14:07:26.158-0400"
+ version="7.2.0">
+ <mainDescription>Scheduled work to be done within the project.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/guidances/toolmentors/use_method_composer_to_update_process.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/toolmentors/use_method_composer_to_update_process.xmi
new file mode 100644
index 0000000..2e9588f
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/guidances/toolmentors/use_method_composer_to_update_process.xmi
@@ -0,0 +1,12 @@
+<?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: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="-5xHoLfZa5sXxhjnW81VZbQ"
+ name="new_toolmentor,_pJJuIOFSEdyhmsbt0Xyl8A" guid="-5xHoLfZa5sXxhjnW81VZbQ" changeDate="2008-02-22T09:37:55.031-0500">
+ <mainDescription>You may wish to leverage&nbsp;the Method Composer to improve the process by incorporating the lessons that have been
+successfully piloted in the project by enhancing templates, checklists, activities,&nbsp;steps, or introducing new
+practices and guidance. See&nbsp;<a class="elementLinkWithType"
+href="./../../../core.default.tool_def.base/guidances/supportingmaterials/resources_for_modifying_methods_7663A1A6.html"
+guid="_omneEMX4EduywMSzPTUUwA">Supporting Material: Resources for Modifying Methods</a> for more information.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/plugin.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/plugin.xmi
new file mode 100644
index 0000000..d181eb2
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/plugin.xmi
@@ -0,0 +1,479 @@
+<?xml version="1.0" encoding="UTF-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.4/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.2.0" xmlns:epf="http://www.eclipse.org/epf"
+ epf:version="1.2.0">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_qqyzEJ6WEdyQN-zRFaRrCQ"
+ guid="_qqyzEJ6WEdyQN-zRFaRrCQ">
+ <resourceDescriptors xmi:id="_nDwNIfL5Edm6Nvont3uinw" id="_Z_bUIMM2EdmSIPI87WLu3g"
+ uri="guidances/templates/iteration_plan.xmi"/>
+ <resourceDescriptors xmi:id="_FG9cgEE7EdulKujnGUuxbg" id="-nDr0XNiUWBo6VS1YS6KAqA"
+ uri="guidances/examples/iteration_plan.xmi"/>
+ <resourceDescriptors xmi:id="_98ybUUvvEdunZcj9T5hrMQ" id="-3G3HV0opAmFWGxYgsD5AhA"
+ uri="guidances/termdefinitions/iteration_burndown.xmi"/>
+ <resourceDescriptors xmi:id="_MqK-EDcGEdyTZ9G7ByfQTw" id="-FNbGVhn2P45T1cT9RvMiGQ"
+ uri="guidances/examples/iteration_burndown_report_example.xmi"/>
+ <resourceDescriptors xmi:id="_nDK-UvL5Edm6Nvont3uinw" id="_BcBR8KX5EdmvhNXG0Oc2uA"
+ uri="workproducts/iteration_plan.xmi"/>
+ <resourceDescriptors xmi:id="_RvzJIC4IEdyhZrtGEIITGQ" id="-Cn1EflOAHbfuEjRZeLMyzA"
+ uri="guidances/guidelines/iteration_assessment.xmi"/>
+ <resourceDescriptors xmi:id="_8UFwQCbYEdqh1LYUOGRh2A" id="-PbfqVxB_j9KN-Jx39_pEUA"
+ uri="tasks/manage_iteration.xmi"/>
+ <resourceDescriptors xmi:id="_j5D7kAarEdy1uLAzgK8btg" id="-z4NERMW6W4_X_5DuTTXv6A"
+ uri="guidances/checklists/iteration_plan.xmi"/>
+ <resourceDescriptors xmi:id="_FFod4NVuEdqWcvghdb0qxA" id="-bUmvEAAtFf6B0aUCux8k9Q"
+ uri="guidances/guidelines/assign_changes_to_iteration.xmi"/>
+ <resourceDescriptors xmi:id="_eZaAAAVuEdy3F_fZDaPZVA" id="-BTXdT-1bO6nbAPf25q0_yA"
+ uri="guidances/checklists/work_items_list.xmi"/>
+ <resourceDescriptors xmi:id="_nDRE8vL5Edm6Nvont3uinw" id="_71hDkMPgEdmbOvqy4O0adg"
+ uri="guidances/guidelines/iteration_planning.xmi"/>
+ <resourceDescriptors xmi:id="_yAx9ECNbEdyCq8v2ZO4QcA" id="-vysTxqikgsqd3pYIkSofjg"
+ uri="guidances/concepts/micro_increments.xmi"/>
+ <resourceDescriptors xmi:id="_HU76YDkAEduxovfWMDsntw" id="-qunTPN3vqTIGpELwajXpLA"
+ uri="guidances/examples/work_items_list.xmi"/>
+ <resourceDescriptors xmi:id="_sbx-cDSpEdy07ZJqOGUGaQ" id="-b0rH1AkPSmj1YKyweFWSuQ"
+ uri="guidances/guidelines/prioritizing_work_items.xmi"/>
+ <resourceDescriptors xmi:id="_nGh0VfL5Edm6Nvont3uinw" id="_a3uz4LBYEdm7Eph_l9Cn9w"
+ uri="tasks/assess_results.xmi"/>
+ <resourceDescriptors xmi:id="_gTd74Dj9EduxovfWMDsntw" id="-mPA7vone29k1OvF_1rACjg"
+ uri="guidances/templates/work_items_list.xmi"/>
+ <resourceDescriptors xmi:id="_Aw2t0A4hEdy63f1yVoPyfA" id="-i-UeSpBxKd6YtGLz_NW8GQ"
+ uri="guidances/guidelines/conduct_retrospective.xmi"/>
+ <resourceDescriptors xmi:id="_RJ6pcUvuEdunZcj9T5hrMQ" id="-mgWkuUy3q0zzFaxE7DY1ag"
+ uri="guidances/termdefinitions/velocity.xmi"/>
+ <resourceDescriptors xmi:id="_Kl_0AEvvEdunZcj9T5hrMQ" id="-1Oc9t_TLaBgW_YLugZcq7w"
+ uri="guidances/termdefinitions/work_item.xmi"/>
+ <resourceDescriptors xmi:id="_wljKoCNaEdyCq8v2ZO4QcA" id="-5xbLr54QjpynnPU8ZJ3_fw"
+ uri="guidances/concepts/iteration_lifecycle.xmi"/>
+ <resourceDescriptors xmi:id="_t_ZKUCbSEdqh1LYUOGRh2A" id="-buxz4BVToq97bSxaqyjySg"
+ uri="workproducts/work_items_list.xmi"/>
+ <resourceDescriptors xmi:id="_eRfk4EcmEdu6ianenth5PQ" id="-Aw8p59vJ9rWsOV82rljQiQ"
+ uri="guidances/reports/iteration_burndown.xmi"/>
+ <resourceDescriptors xmi:id="_Ze38MA4gEdy-5fPdYA9Psg" id="-ENSD2TqUsFcf3Sf-oeozUA"
+ uri="guidances/concepts/retrospective.xmi"/>
+ <resourceDescriptors xmi:id="_nGbttPL5Edm6Nvont3uinw" id="_Wk7noKe1EdmGSrcKGOYDGg"
+ uri="tasks/plan_iteration.xmi"/>
+ <resourceDescriptors xmi:id="_KbS1UEvuEdunZcj9T5hrMQ" id="-oShmMITo9RIi1AzACWI9vw"
+ uri="guidances/termdefinitions/point.xmi"/>
+ <resourceDescriptors xmi:id="_iZ-GsEvHEdunZcj9T5hrMQ" id="-_G0VvVOdMoajk615LwFtxg"
+ uri="guidances/termdefinitions/iteration.xmi"/>
+ <resourceDescriptors xmi:id="__qWzAcN-Edy3nv0ZK8D4GQ" id="-WeT7CrjLCAbaJKlpVk3O8w"
+ uri="guidances/supportingmaterials/release_info_iterative_dev.xmi"/>
+ <resourceDescriptors xmi:id="_7WIYYDg2Edu4E8ZdmlYjtA" id="-G1Oxlk6F0R09vClqy1EzOw"
+ uri="guidances/guidelines/managing_work_items.xmi"/>
+ <resourceDescriptors xmi:id="_U37zIdm8EdyzZqGyZ7hwdw" id="-Yvy3AKQTjSqBPNxsWkizkQ"
+ uri="guidances/practices/iterative_development_practice.xmi"/>
+ <resourceDescriptors xmi:id="_nGuBkPL5Edm6Nvont3uinw" id="_Nr0S4KeqEdmKDbQuyzCoqQ"
+ uri="tasks/request_change.xmi"/>
+ <resourceDescriptors xmi:id="_eYqfseFVEdyhmsbt0Xyl8A" id="-5xHoLfZa5sXxhjnW81VZbQ"
+ uri="guidances/toolmentors/use_method_composer_to_update_process.xmi"/>
+ <resourceDescriptors xmi:id="_bqsxweMPEdyM47cGD2jiaQ" id="-hWKKNia-vOmQZTZWO24u5w"
+ uri="guidances/roadmaps/how_to_adopt.xmi"/>
+ <resourceDescriptors xmi:id="_Ou2iMeMWEdyM47cGD2jiaQ" id="-Godh4yG8PB3TBqovJQY9SQ"
+ uri="customcategories/iterative_dev_practice.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_qqyzAJ6WEdyQN-zRFaRrCQ" name="practice.mgmt.iterative_dev.base"
+ guid="_qqyzAJ6WEdyQN-zRFaRrCQ" changeDate="2008-02-22T09:31:42.828-0500">
+ <copyrightStatement href="uma://_iVydgENdEdy245g62lfWcA#_cTs20KzREduOqvpk_MDLfQ"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_qqyzAZ6WEdyQN-zRFaRrCQ"
+ name="Content" guid="_qqyzAZ6WEdyQN-zRFaRrCQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_qqyzAp6WEdyQN-zRFaRrCQ"
+ name="Categories" guid="_qqyzAp6WEdyQN-zRFaRrCQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_qqyzA56WEdyQN-zRFaRrCQ"
+ name="Domains" guid="_qqyzA56WEdyQN-zRFaRrCQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_qqyzBJ6WEdyQN-zRFaRrCQ"
+ name="Disciplines" guid="_qqyzBJ6WEdyQN-zRFaRrCQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_qqyzBZ6WEdyQN-zRFaRrCQ"
+ name="RoleSets" guid="_qqyzBZ6WEdyQN-zRFaRrCQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_qqyzBp6WEdyQN-zRFaRrCQ"
+ name="WP Types" guid="_qqyzBp6WEdyQN-zRFaRrCQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_qqyzB56WEdyQN-zRFaRrCQ"
+ name="Tools" guid="_qqyzB56WEdyQN-zRFaRrCQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:Tool" xmi:id="_tYzlcOFSEdyhmsbt0Xyl8A"
+ name="method_composer_tool.assign" guid="_tYzlcOFSEdyhmsbt0Xyl8A" variabilityType="contributes"
+ toolMentors="_pJJuIOFSEdyhmsbt0Xyl8A">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Tool" href="uma://_fRdVEMYbEdyXeo04os5BOw#_mHQIMMYbEdyXeo04os5BOw"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_qqyzCJ6WEdyQN-zRFaRrCQ"
+ name="StandardCategories" guid="_qqyzCJ6WEdyQN-zRFaRrCQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_qqyzCZ6WEdyQN-zRFaRrCQ"
+ name="CustomCategories" guid="_qqyzCZ6WEdyQN-zRFaRrCQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_qqyzCp6WEdyQN-zRFaRrCQ"
+ name="Hidden" guid="_qqyzCp6WEdyQN-zRFaRrCQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_qqyzC56WEdyQN-zRFaRrCQ"
+ name="Custom Categories" guid="_qqyzC56WEdyQN-zRFaRrCQ" categorizedElements="_1pc5QJ-kEdyBk-WQzMU-FQ _QzieIMg4EdyXeo04os5BOw"/>
+ </childPackages>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_1pc5QJ-kEdyBk-WQzMU-FQ"
+ name="iterative_dev_practice" guid="_1pc5QJ-kEdyBk-WQzMU-FQ" briefDescription="This practice creates a solution in increments. Each increment is completed in a fixed period of time, an "iteration"."
+ presentationName="Iterative Development" shapeicon="customcategories/resources/pract_dgm32.gif"
+ nodeicon="customcategories/resources/pract_obj.gif" categorizedElements="_bpWt8OMPEdyM47cGD2jiaQ _UjfMEJ_zEdyBk-WQzMU-FQ _1UYPQJ_zEdyBk-WQzMU-FQ _be0xEJ_0EdyBk-WQzMU-FQ">
+ <presentation xmi:id="-Godh4yG8PB3TBqovJQY9SQ" href="uma://-Godh4yG8PB3TBqovJQY9SQ#-Godh4yG8PB3TBqovJQY9SQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_UjfMEJ_zEdyBk-WQzMU-FQ"
+ name="tasks" guid="_UjfMEJ_zEdyBk-WQzMU-FQ" presentationName="Tasks"
+ shapeicon="customcategories/resources/task_dgm32.gif" nodeicon="customcategories/resources/task_obj.gif"
+ categorizedElements="_0keUEMlgEdmt3adZL5Dmdw _8S2aICbYEdqh1LYUOGRh2A _0l53cMlgEdmt3adZL5Dmdw _0mwzEclgEdmt3adZL5Dmdw">
+ <methodElementProperty xmi:id="_K1PvsJ_0EdyBk-WQzMU-FQ" name="CategoryElementsSortType"
+ value="Alphabetic"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_1UYPQJ_zEdyBk-WQzMU-FQ"
+ name="work_products" guid="_1UYPQJ_zEdyBk-WQzMU-FQ" presentationName="Work Products"
+ shapeicon="customcategories/resources/workproduct_dgm32.gif" nodeicon="customcategories/resources/workproduct_obj.gif">
+ <methodElementProperty xmi:id="_JC8roJ_0EdyBk-WQzMU-FQ" name="CategoryElementsSortType"
+ value="Manual"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="#_0aQBEslgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="#_rGNWsCbSEdqh1LYUOGRh2A"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_Ckay8Cc_EduIsqH1Q6ZuqA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_be0xEJ_0EdyBk-WQzMU-FQ"
+ name="guidance" guid="_be0xEJ_0EdyBk-WQzMU-FQ" presentationName="Guidance"
+ shapeicon="customcategories/resources/bookcL.gif" nodeicon="customcategories/resources/bookc.gif">
+ <methodElementProperty xmi:id="_5yp78J_0EdyBk-WQzMU-FQ" name="CategoryElementsSortType"
+ value="MethodType"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="#_7vEXEMA4EdqSgKaj2SZBmg"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_CGHskBEdEdqY7JB6N6CW2w"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="#__yQQ4L6REdqti4GwqTkbsQ"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="#_277QEA4gEdy63f1yVoPyfA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="#_FekBAC4IEdyhZrtGEIITGQ"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Report" href="#_uAzgkDg3Edu4E8ZdmlYjtA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Example" href="#_GtGisDcGEdyTZ9G7ByfQTw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="#_DI_tICNaEdyCq8v2ZO4QcA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Checklist" href="#_OHRDMAarEdy1uLAzgK8btg"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Template" href="#_0dBoQMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Example" href="#_TuNhIEE4EdulKujnGUuxbg"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="#_0auiMMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_VNxL4ACsEdu8m4dIntu6jA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="#_S80VwCNbEdyCq8v2ZO4QcA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="#_oVMZADSoEdy07ZJqOGUGaQ"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="#_2PfbIA4QEdy2q5zsU8WDnA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Template" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_MIUO0C8FEduzydamRseoUw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Checklist" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_7BZa0DIdEduDTv4Y1akVTA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Checklist" href="#_xlrdEAVtEdy3F_fZDaPZVA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Template" href="#_QwUJYDg0Edu4E8ZdmlYjtA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Example" href="#_nHomIDgzEdu4E8ZdmlYjtA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_QzieIMg4EdyXeo04os5BOw"
+ name="contributions_to_nav_building_blocks" guid="_QzieIMg4EdyXeo04os5BOw"
+ presentationName="Contributions to Navigation Building Blocks" categorizedElements="_MCgrMMhQEdygFZkm1d5NtQ _tWks4MhQEdygFZkm1d5NtQ _QcxakMhREdygFZkm1d5NtQ _aUIhQMhREdygFZkm1d5NtQ _ioaEkMhREdygFZkm1d5NtQ _riXu4MhREdygFZkm1d5NtQ _y7LvgMhREdygFZkm1d5NtQ _-MtHEMhREdygFZkm1d5NtQ _TYjZwMhSEdygFZkm1d5NtQ _487XgNQuEdyM_J8-fv54DA _KdFZwOMQEdyM47cGD2jiaQ"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_MCgrMMhQEdygFZkm1d5NtQ"
+ name="release_info.assign" guid="_MCgrMMhQEdygFZkm1d5NtQ" variabilityType="contributes"
+ categorizedElements="_TFhnsMN-Edy3nv0ZK8D4GQ">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCIHYcRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_tWks4MhQEdygFZkm1d5NtQ"
+ name="artifact_list.assign" guid="_tWks4MhQEdygFZkm1d5NtQ" variabilityType="contributes">
+ <methodElementProperty xmi:id="_1GoI0MhQEdygFZkm1d5NtQ" name="CategoryElementsSortType"
+ value="Manual"/>
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4YMRdEdyD76CYS6Ta7A"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="#_0aQBEslgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_Ckay8Cc_EduIsqH1Q6ZuqA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="#_rGNWsCbSEdqh1LYUOGRh2A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_QcxakMhREdygFZkm1d5NtQ"
+ name="checklist_list.assign" guid="_QcxakMhREdygFZkm1d5NtQ" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_pGt9MMReEdyD76CYS6Ta7A"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Checklist" href="#_OHRDMAarEdy1uLAzgK8btg"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Checklist" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_7BZa0DIdEduDTv4Y1akVTA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Checklist" href="#_xlrdEAVtEdy3F_fZDaPZVA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_aUIhQMhREdygFZkm1d5NtQ"
+ name="concept_list" guid="_aUIhQMhREdygFZkm1d5NtQ" variabilityType="contributes"
+ categorizedElements="_DI_tICNaEdyCq8v2ZO4QcA _S80VwCNbEdyCq8v2ZO4QcA _2PfbIA4QEdy2q5zsU8WDnA">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4Y8RdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_ioaEkMhREdygFZkm1d5NtQ"
+ name="example_list.assign" guid="_ioaEkMhREdygFZkm1d5NtQ" variabilityType="contributes"
+ categorizedElements="_GtGisDcGEdyTZ9G7ByfQTw _TuNhIEE4EdulKujnGUuxbg _nHomIDgzEdu4E8ZdmlYjtA">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4ZMRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_riXu4MhREdygFZkm1d5NtQ"
+ name="guideline_list.assign" guid="_riXu4MhREdygFZkm1d5NtQ" variabilityType="contributes"
+ categorizedElements="__yQQ4L6REdqti4GwqTkbsQ _277QEA4gEdy63f1yVoPyfA _FekBAC4IEdyhZrtGEIITGQ _0auiMMlgEdmt3adZL5Dmdw _oVMZADSoEdy07ZJqOGUGaQ _7vEXEMA4EdqSgKaj2SZBmg">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4ZcRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_y7LvgMhREdygFZkm1d5NtQ"
+ name="report_list.assign" guid="_y7LvgMhREdygFZkm1d5NtQ" variabilityType="contributes"
+ categorizedElements="_uAzgkDg3Edu4E8ZdmlYjtA">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_sJd8gMReEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_-MtHEMhREdygFZkm1d5NtQ"
+ name="template_list.assign" guid="_-MtHEMhREdygFZkm1d5NtQ" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4Z8RdEdyD76CYS6Ta7A"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Template" href="#_0dBoQMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Template" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_MIUO0C8FEduzydamRseoUw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Template" href="#_QwUJYDg0Edu4E8ZdmlYjtA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_TYjZwMhSEdygFZkm1d5NtQ"
+ name="practice_list.assign" guid="_TYjZwMhSEdygFZkm1d5NtQ" variabilityType="contributes"
+ categorizedElements="_1pc5QJ-kEdyBk-WQzMU-FQ">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCIHY8RdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_487XgNQuEdyM_J8-fv54DA"
+ name="management_practice_list.assign" guid="_487XgNQuEdyM_J8-fv54DA"
+ variabilityType="contributes" categorizedElements="_1pc5QJ-kEdyBk-WQzMU-FQ">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_auUD0NQuEdyM_J8-fv54DA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_KdFZwOMQEdyM47cGD2jiaQ"
+ name="roadmap_list.assign" guid="_KdFZwOMQEdyM47cGD2jiaQ" variabilityType="contributes"
+ categorizedElements="_bpWt8OMPEdyM47cGD2jiaQ">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4ZsRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_qqyzDJ6WEdyQN-zRFaRrCQ"
+ name="CoreContent" guid="_qqyzDJ6WEdyQN-zRFaRrCQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_BwrisJ9WEdy3Nc4rvuj7bA"
+ name="Iterative Development" guid="_BwrisJ9WEdy3Nc4rvuj7bA">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_jRZ5EMOBEdy3nv0ZK8D4GQ"
+ name="Release Info" guid="_jRZ5EMOBEdy3nv0ZK8D4GQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="_TFhnsMN-Edy3nv0ZK8D4GQ"
+ name="release_info_iterative_dev" guid="_TFhnsMN-Edy3nv0ZK8D4GQ" presentationName="Iterative Development Practice">
+ <presentation xmi:id="-WeT7CrjLCAbaJKlpVk3O8w" href="uma://-WeT7CrjLCAbaJKlpVk3O8w#-WeT7CrjLCAbaJKlpVk3O8w"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_dLzj4MhPEdygFZkm1d5NtQ"
+ name="Templates, Reports, and Examples" guid="_dLzj4MhPEdygFZkm1d5NtQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:Report" xmi:id="_uAzgkDg3Edu4E8ZdmlYjtA"
+ name="iteration_burndown" guid="_uAzgkDg3Edu4E8ZdmlYjtA" briefDescription="The iteration burndown shows the trend for how much work is left to do within that iteration. "
+ presentationName="Iteration Burndown">
+ <presentation xmi:id="-Aw8p59vJ9rWsOV82rljQiQ" href="uma://-Aw8p59vJ9rWsOV82rljQiQ#-Aw8p59vJ9rWsOV82rljQiQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Template" xmi:id="_0dBoQMlgEdmt3adZL5Dmdw"
+ name="iteration_plan" guid="_0dBoQMlgEdmt3adZL5Dmdw" briefDescription="This is the informal template suggested for an iteration plan."
+ presentationName="Iteration Plan">
+ <presentation xmi:id="_Z_bUIMM2EdmSIPI87WLu3g" href="uma://_Z_bUIMM2EdmSIPI87WLu3g#_Z_bUIMM2EdmSIPI87WLu3g"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Template" xmi:id="_QwUJYDg0Edu4E8ZdmlYjtA"
+ name="work_items_list" guid="_QwUJYDg0Edu4E8ZdmlYjtA" briefDescription="This is a spreadsheet suggested for representing a work items list. Alternative templates would be usage of a specific tool or database with similar information."
+ presentationName="Work Items List">
+ <presentation xmi:id="-mPA7vone29k1OvF_1rACjg" href="uma://-mPA7vone29k1OvF_1rACjg#-mPA7vone29k1OvF_1rACjg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Example" xmi:id="_GtGisDcGEdyTZ9G7ByfQTw"
+ name="iteration_burndown_report_example" guid="_GtGisDcGEdyTZ9G7ByfQTw"
+ briefDescription="This is an example of an iteration burndown report."
+ presentationName="Iteration Burndown Report">
+ <presentation xmi:id="-FNbGVhn2P45T1cT9RvMiGQ" href="uma://-FNbGVhn2P45T1cT9RvMiGQ#-FNbGVhn2P45T1cT9RvMiGQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Example" xmi:id="_TuNhIEE4EdulKujnGUuxbg"
+ name="iteration_plan" guid="_TuNhIEE4EdulKujnGUuxbg" briefDescription="This is an example of an iteration plan for iteration 5 for a small team. In this example, the team has chosen not to list work items in the iteration plan. Instead, the team will search the work items list for work items assigned to iteration 5. This is the preferred solution when work items are managed in a tool that provides basic search capabilities."
+ presentationName="Iteration Plan">
+ <presentation xmi:id="-nDr0XNiUWBo6VS1YS6KAqA" href="uma://-nDr0XNiUWBo6VS1YS6KAqA#-nDr0XNiUWBo6VS1YS6KAqA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Example" xmi:id="_nHomIDgzEdu4E8ZdmlYjtA"
+ name="work_items_list" guid="_nHomIDgzEdu4E8ZdmlYjtA" briefDescription="This is an example of a partial Work Items List for a small team who just started to work on iteration 3."
+ presentationName="Work Items List">
+ <presentation xmi:id="-qunTPN3vqTIGpELwajXpLA" href="uma://-qunTPN3vqTIGpELwajXpLA#-qunTPN3vqTIGpELwajXpLA"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_gfuaMOFSEdyhmsbt0Xyl8A"
+ name="Method Composer Tool Mentors" guid="_gfuaMOFSEdyhmsbt0Xyl8A">
+ <contentElements xsi:type="org.eclipse.epf.uma:ToolMentor" xmi:id="_pJJuIOFSEdyhmsbt0Xyl8A"
+ name="use_method_composer_to_update_process" guid="_pJJuIOFSEdyhmsbt0Xyl8A"
+ presentationName="Use Method Composer to Update the Process">
+ <presentation xmi:id="-5xHoLfZa5sXxhjnW81VZbQ" href="uma://-5xHoLfZa5sXxhjnW81VZbQ#-5xHoLfZa5sXxhjnW81VZbQ"/>
+ </contentElements>
+ </childPackages>
+ <contentElements xsi:type="org.eclipse.epf.uma:Practice" xmi:id="_LR_g4J9WEdy3Nc4rvuj7bA"
+ name="iterative_development_practice" guid="_LR_g4J9WEdy3Nc4rvuj7bA"
+ briefDescription="Create a solution in increments. Each increment is completed in a fixed period of time, an "iteration"."
+ presentationName="Iterative Development" contentReferences="_1pc5QJ-kEdyBk-WQzMU-FQ">
+ <presentation xmi:id="-Yvy3AKQTjSqBPNxsWkizkQ" href="uma://-Yvy3AKQTjSqBPNxsWkizkQ#-Yvy3AKQTjSqBPNxsWkizkQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_DI_tICNaEdyCq8v2ZO4QcA"
+ name="iteration_lifecycle" guid="_DI_tICNaEdyCq8v2ZO4QcA" briefDescription="The iteration lifecycle provides a set of team-based practices describing how to leverage iterations to focus the team on delivering incremental value to stakeholders in a predictable manner."
+ presentationName="Iteration Lifecycle">
+ <presentation xmi:id="-5xbLr54QjpynnPU8ZJ3_fw" href="uma://-5xbLr54QjpynnPU8ZJ3_fw#-5xbLr54QjpynnPU8ZJ3_fw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_S80VwCNbEdyCq8v2ZO4QcA"
+ name="micro_increments" guid="_S80VwCNbEdyCq8v2ZO4QcA" briefDescription="A micro-increment is a small, measurable step towards reaching the goals of an iteration. A micro-increment represents the outcome of a few hours to a few days of work performed by one or typically a few people collaborating to reach a goal."
+ presentationName="Micro-Increments">
+ <presentation xmi:id="-vysTxqikgsqd3pYIkSofjg" href="uma://-vysTxqikgsqd3pYIkSofjg#-vysTxqikgsqd3pYIkSofjg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_2PfbIA4QEdy2q5zsU8WDnA"
+ name="retrospective" guid="_2PfbIA4QEdy2q5zsU8WDnA" presentationName="Retrospective">
+ <presentation xmi:id="-ENSD2TqUsFcf3Sf-oeozUA" href="uma://-ENSD2TqUsFcf3Sf-oeozUA#-ENSD2TqUsFcf3Sf-oeozUA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Checklist" xmi:id="_OHRDMAarEdy1uLAzgK8btg"
+ name="iteration_plan" guid="_OHRDMAarEdy1uLAzgK8btg" briefDescription="This checklist provides questions to verify that iteration plans are created in 
a consistent manner."
+ presentationName="Iteration Plan">
+ <presentation xmi:id="-z4NERMW6W4_X_5DuTTXv6A" href="uma://-z4NERMW6W4_X_5DuTTXv6A#-z4NERMW6W4_X_5DuTTXv6A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Checklist" xmi:id="_xlrdEAVtEdy3F_fZDaPZVA"
+ name="work_items_list" guid="_xlrdEAVtEdy3F_fZDaPZVA" briefDescription="This checklist is used to verify that every kind of work to be done in the project 
is being tracked"
+ presentationName="Work Items List">
+ <presentation xmi:id="-BTXdT-1bO6nbAPf25q0_yA" href="uma://-BTXdT-1bO6nbAPf25q0_yA#-BTXdT-1bO6nbAPf25q0_yA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_277QEA4gEdy63f1yVoPyfA"
+ name="conduct_retrospective" guid="_277QEA4gEdy63f1yVoPyfA" briefDescription="This guideline covers how to conduct a Project Retrospective, step by step."
+ presentationName="Conduct Project Retrospective">
+ <presentation xmi:id="-i-UeSpBxKd6YtGLz_NW8GQ" href="uma://-i-UeSpBxKd6YtGLz_NW8GQ#-i-UeSpBxKd6YtGLz_NW8GQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_FekBAC4IEdyhZrtGEIITGQ"
+ name="iteration_assessment" guid="_FekBAC4IEdyhZrtGEIITGQ" briefDescription="This Guideline describes how to review the iteration results with the stakeholders. An Iteration Assessment provides an observation point for project progress at the end of every iteration. Based on collected feedback the team can adapt and build better software. or a decision can be made to put it into production, if it provides enough business value."
+ presentationName="Iteration Assessment">
+ <presentation xmi:id="-Cn1EflOAHbfuEjRZeLMyzA" href="uma://-Cn1EflOAHbfuEjRZeLMyzA#-Cn1EflOAHbfuEjRZeLMyzA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_oVMZADSoEdy07ZJqOGUGaQ"
+ name="prioritizing_work_items" guid="_oVMZADSoEdy07ZJqOGUGaQ" briefDescription="This guidelines describes who, when and how work items are prioritized througout the project lifecycle."
+ presentationName="Prioritizing Work Items">
+ <presentation xmi:id="-b0rH1AkPSmj1YKyweFWSuQ" href="uma://-b0rH1AkPSmj1YKyweFWSuQ#-b0rH1AkPSmj1YKyweFWSuQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_0l53cMlgEdmt3adZL5Dmdw"
+ name="assess_results" guid="_0l53cMlgEdmt3adZL5Dmdw" briefDescription="Determine success or failure of the iteration. Apply the lessons learned to modify the project or improve the process."
+ presentationName="Assess Results" conceptsAndPapers="_2PfbIA4QEdy2q5zsU8WDnA"
+ guidelines="_277QEA4gEdy63f1yVoPyfA _FekBAC4IEdyhZrtGEIITGQ" mandatoryInput="_0aQBEslgEdmt3adZL5Dmdw _rGNWsCbSEdqh1LYUOGRh2A"
+ output="_0aQBEslgEdmt3adZL5Dmdw _rGNWsCbSEdqh1LYUOGRh2A" toolMentors="_pJJuIOFSEdyhmsbt0Xyl8A">
+ <presentation xmi:id="_a3uz4LBYEdm7Eph_l9Cn9w" href="uma://_a3uz4LBYEdm7Eph_l9Cn9w#_a3uz4LBYEdm7Eph_l9Cn9w"/>
+ <optionalInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_i3vkoLS-EduDY8LNbMCDBA"/>
+ <optionalInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_fahB0EfUEdyiPI8btkmvmw"/>
+ <optionalInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_vJYucEfUEdyiPI8btkmvmw#_RJMUcNpUEdyzZqGyZ7hwdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_8S2aICbYEdqh1LYUOGRh2A"
+ name="manage_iteration" guid="_8S2aICbYEdqh1LYUOGRh2A" briefDescription="Assess project status and identify any blocking issues and/or opportunities. Identify and manage exceptions, problems and risks. Communicate project status."
+ presentationName="Manage Iteration">
+ <presentation xmi:id="-PbfqVxB_j9KN-Jx39_pEUA" href="uma://-PbfqVxB_j9KN-Jx39_pEUA#-PbfqVxB_j9KN-Jx39_pEUA"/>
+ <conceptsAndPapers href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0bsLgMlgEdmt3adZL5Dmdw"/>
+ <conceptsAndPapers href="#_DI_tICNaEdyCq8v2ZO4QcA"/>
+ <conceptsAndPapers href="#_S80VwCNbEdyCq8v2ZO4QcA"/>
+ <conceptsAndPapers href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0mYYkMlgEdmt3adZL5Dmdw"/>
+ <guidelines href="#__yQQ4L6REdqti4GwqTkbsQ"/>
+ <guidelines href="uma://_vJYucEfUEdyiPI8btkmvmw#_68JUYN8-Edyhmsbt0Xyl8A"/>
+ <guidelines href="uma://_vJYucEfUEdyiPI8btkmvmw#_BslGYN8_Edyhmsbt0Xyl8A"/>
+ <mandatoryInput xsi:type="org.eclipse.epf.uma:Artifact" href="#_0aQBEslgEdmt3adZL5Dmdw"/>
+ <mandatoryInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_Ckay8Cc_EduIsqH1Q6ZuqA"/>
+ <mandatoryInput xsi:type="org.eclipse.epf.uma:Artifact" href="#_rGNWsCbSEdqh1LYUOGRh2A"/>
+ <mandatoryInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_vJYucEfUEdyiPI8btkmvmw#_RJMUcNpUEdyzZqGyZ7hwdw"/>
+ <output xsi:type="org.eclipse.epf.uma:Artifact" href="#_0aQBEslgEdmt3adZL5Dmdw"/>
+ <output xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_Ckay8Cc_EduIsqH1Q6ZuqA"/>
+ <output xsi:type="org.eclipse.epf.uma:Artifact" href="#_rGNWsCbSEdqh1LYUOGRh2A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_0keUEMlgEdmt3adZL5Dmdw"
+ name="plan_iteration" guid="_0keUEMlgEdmt3adZL5Dmdw" briefDescription="Plan the scope and responsibilities for a single iteration."
+ presentationName="Plan Iteration">
+ <presentation xmi:id="_Wk7noKe1EdmGSrcKGOYDGg" href="uma://_Wk7noKe1EdmGSrcKGOYDGg#_Wk7noKe1EdmGSrcKGOYDGg"/>
+ <conceptsAndPapers href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_lam4ADkBEduxovfWMDsntw"/>
+ <conceptsAndPapers href="#_S80VwCNbEdyCq8v2ZO4QcA"/>
+ <conceptsAndPapers href="#_DI_tICNaEdyCq8v2ZO4QcA"/>
+ <guidelines href="#_7vEXEMA4EdqSgKaj2SZBmg"/>
+ <guidelines href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_CGHskBEdEdqY7JB6N6CW2w"/>
+ <guidelines href="#__yQQ4L6REdqti4GwqTkbsQ"/>
+ <guidelines href="#_0auiMMlgEdmt3adZL5Dmdw"/>
+ <guidelines href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_VNxL4ACsEdu8m4dIntu6jA"/>
+ <guidelines href="uma://_vJYucEfUEdyiPI8btkmvmw#_sLQ6AN8-Edyhmsbt0Xyl8A"/>
+ <mandatoryInput xsi:type="org.eclipse.epf.uma:Artifact" href="#_rGNWsCbSEdqh1LYUOGRh2A"/>
+ <mandatoryInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_vJYucEfUEdyiPI8btkmvmw#_RJMUcNpUEdyzZqGyZ7hwdw"/>
+ <output xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_Ckay8Cc_EduIsqH1Q6ZuqA"/>
+ <output xsi:type="org.eclipse.epf.uma:Artifact" href="#_0aQBEslgEdmt3adZL5Dmdw"/>
+ <output xsi:type="org.eclipse.epf.uma:Artifact" href="#_rGNWsCbSEdqh1LYUOGRh2A"/>
+ <optionalInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_8OD-cLPTEduocbW-TPTq7A"/>
+ <optionalInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_i3vkoLS-EduDY8LNbMCDBA"/>
+ <optionalInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_Ckay8Cc_EduIsqH1Q6ZuqA"/>
+ <optionalInput xsi:type="org.eclipse.epf.uma:Artifact" href="#_0aQBEslgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="__yQQ4L6REdqti4GwqTkbsQ"
+ name="assign_changes_to_iteration" guid="__yQQ4L6REdqti4GwqTkbsQ" briefDescription="This guideline promotes the best practice of isolating team members from disruptive changes during the current iteration. Change requests are reviewed and prioritized during the current iteration, but are not acted upon until assigned to a future iteration."
+ presentationName="Assign Changes to an Iteration">
+ <presentation xmi:id="-bUmvEAAtFf6B0aUCux8k9Q" href="uma://-bUmvEAAtFf6B0aUCux8k9Q#-bUmvEAAtFf6B0aUCux8k9Q"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_0auiMMlgEdmt3adZL5Dmdw"
+ name="iteration_planning" guid="_0auiMMlgEdmt3adZL5Dmdw" briefDescription="The goal with iteration planning is to establish a few high-level iteration objectives that delivers stakeholder value, produce a sufficiently detailed plan outlining who needs to do what, and to define how to assess end results."
+ presentationName="Iteration Planning">
+ <presentation xmi:id="_71hDkMPgEdmbOvqy4O0adg" href="uma://_71hDkMPgEdmbOvqy4O0adg#_71hDkMPgEdmbOvqy4O0adg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_8b20EEvvEdunZcj9T5hrMQ"
+ name="iteration_burndown" guid="_8b20EEvvEdunZcj9T5hrMQ" presentationName="iteration burndown">
+ <presentation xmi:id="-3G3HV0opAmFWGxYgsD5AhA" href="uma://-3G3HV0opAmFWGxYgsD5AhA#-3G3HV0opAmFWGxYgsD5AhA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_Nj2hsEvuEdunZcj9T5hrMQ"
+ name="velocity" guid="_Nj2hsEvuEdunZcj9T5hrMQ" presentationName="velocity">
+ <presentation xmi:id="-mgWkuUy3q0zzFaxE7DY1ag" href="uma://-mgWkuUy3q0zzFaxE7DY1ag#-mgWkuUy3q0zzFaxE7DY1ag"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_jyVgcEvKEdunZcj9T5hrMQ"
+ name="work_item" guid="_jyVgcEvKEdunZcj9T5hrMQ" presentationName="work item">
+ <presentation xmi:id="-1Oc9t_TLaBgW_YLugZcq7w" href="uma://-1Oc9t_TLaBgW_YLugZcq7w#-1Oc9t_TLaBgW_YLugZcq7w"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_MvOuAEvGEdunZcj9T5hrMQ"
+ name="point" guid="_MvOuAEvGEdunZcj9T5hrMQ" presentationName="point">
+ <presentation xmi:id="-oShmMITo9RIi1AzACWI9vw" href="uma://-oShmMITo9RIi1AzACWI9vw#-oShmMITo9RIi1AzACWI9vw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_ZBUnMEvFEdunZcj9T5hrMQ"
+ name="iteration" guid="_ZBUnMEvFEdunZcj9T5hrMQ" presentationName="iteration">
+ <presentation xmi:id="-_G0VvVOdMoajk615LwFtxg" href="uma://-_G0VvVOdMoajk615LwFtxg#-_G0VvVOdMoajk615LwFtxg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_7vEXEMA4EdqSgKaj2SZBmg"
+ name="managing_work_items" guid="_7vEXEMA4EdqSgKaj2SZBmg" briefDescription="This guideline explains the lifecycle of Work Items and how the Work Items List is used."
+ presentationName="Managing Work Items">
+ <presentation xmi:id="-G1Oxlk6F0R09vClqy1EzOw" href="uma://-G1Oxlk6F0R09vClqy1EzOw#-G1Oxlk6F0R09vClqy1EzOw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_0mwzEclgEdmt3adZL5Dmdw"
+ name="request_change" guid="_0mwzEclgEdmt3adZL5Dmdw" briefDescription="Capture and record change requests."
+ presentationName="Request Change" output="_rGNWsCbSEdqh1LYUOGRh2A" optionalInput="_rGNWsCbSEdqh1LYUOGRh2A">
+ <presentation xmi:id="_Nr0S4KeqEdmKDbQuyzCoqQ" href="uma://_Nr0S4KeqEdmKDbQuyzCoqQ#_Nr0S4KeqEdmKDbQuyzCoqQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_AwS4wNpnEdyzZqGyZ7hwdw"
+ name="project_work_slot.assign" guid="_AwS4wNpnEdyzZqGyZ7hwdw" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_vJYucEfUEdyiPI8btkmvmw#_1QZI8EfUEdyiPI8btkmvmw"/>
+ <containedArtifacts xmi:id="_rGNWsCbSEdqh1LYUOGRh2A" name="work_items_list"
+ guid="_rGNWsCbSEdqh1LYUOGRh2A" briefDescription="This artifact contains a list of all scheduled work to be done within the project, as well as proposed work that may affect the product in this or future projects. Each work item may contain references to information relevant to carry out the work described within the work item."
+ presentationName="Work Items List" guidelines="_7vEXEMA4EdqSgKaj2SZBmg"
+ examples="_GtGisDcGEdyTZ9G7ByfQTw _nHomIDgzEdu4E8ZdmlYjtA" reports="_uAzgkDg3Edu4E8ZdmlYjtA"
+ templates="_QwUJYDg0Edu4E8ZdmlYjtA">
+ <presentation xmi:id="-buxz4BVToq97bSxaqyjySg" href="uma://-buxz4BVToq97bSxaqyjySg#-buxz4BVToq97bSxaqyjySg"/>
+ </containedArtifacts>
+ <containedArtifacts xmi:id="_0aQBEslgEdmt3adZL5Dmdw" name="iteration_plan"
+ guid="_0aQBEslgEdmt3adZL5Dmdw" briefDescription="A fine-grained plan describing the objectives, work assignments, and evaluation criteria for the iteration."
+ presentationName="Iteration Plan" examples="_GtGisDcGEdyTZ9G7ByfQTw _TuNhIEE4EdulKujnGUuxbg"
+ reports="_uAzgkDg3Edu4E8ZdmlYjtA" templates="_0dBoQMlgEdmt3adZL5Dmdw">
+ <presentation xmi:id="_BcBR8KX5EdmvhNXG0Oc2uA" href="uma://_BcBR8KX5EdmvhNXG0Oc2uA#_BcBR8KX5EdmvhNXG0Oc2uA"/>
+ <conceptsAndPapers href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_lam4ADkBEduxovfWMDsntw"/>
+ </containedArtifacts>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_dlNOkNpnEdyzZqGyZ7hwdw"
+ name="project_risk_slot.assign" guid="_dlNOkNpnEdyzZqGyZ7hwdw" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_vJYucEfUEdyiPI8btkmvmw#_0TkXgNpUEdyzZqGyZ7hwdw"/>
+ <containedArtifacts xmi:id="_9BtSUOFlEdyhmsbt0Xyl8A" name="risk_list.assign"
+ guid="_9BtSUOFlEdyhmsbt0Xyl8A" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_Ckay8Cc_EduIsqH1Q6ZuqA"/>
+ </containedArtifacts>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_nzEFcOKFEdyM47cGD2jiaQ"
+ name="project_status_slot.assign" guid="_nzEFcOKFEdyM47cGD2jiaQ" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_vJYucEfUEdyiPI8btkmvmw#_kf7foNpUEdyzZqGyZ7hwdw"/>
+ <containedArtifacts xmi:id="_ytVaoOKFEdyM47cGD2jiaQ" name="work_items_list.child"
+ guid="_ytVaoOKFEdyM47cGD2jiaQ" variabilityType="contributes" variabilityBasedOnElement="_rGNWsCbSEdqh1LYUOGRh2A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Roadmap" xmi:id="_bpWt8OMPEdyM47cGD2jiaQ"
+ name="how_to_adopt" guid="_bpWt8OMPEdyM47cGD2jiaQ" briefDescription="This roadmap describes how to adopt the Iterative Development Practice."
+ presentationName="How to Adopt This Practice">
+ <presentation xmi:id="-hWKKNia-vOmQZTZWO24u5w" href="uma://-hWKKNia-vOmQZTZWO24u5w#-hWKKNia-vOmQZTZWO24u5w"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_qqyzDZ6WEdyQN-zRFaRrCQ"
+ name="CapabilityPatterns" guid="_qqyzDZ6WEdyQN-zRFaRrCQ"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_qqyzDp6WEdyQN-zRFaRrCQ"
+ name="DeliveryProcesses" guid="_qqyzDp6WEdyQN-zRFaRrCQ"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_qqyzD56WEdyQN-zRFaRrCQ"
+ name="ProcessContributions" guid="_qqyzD56WEdyQN-zRFaRrCQ"/>
+ <bases href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYucEfUEdyiPI8btkmvmw"/>
+ <bases href="uma://_iVydgENdEdy245g62lfWcA#_iVydgENdEdy245g62lfWcA"/>
+ <bases href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0TmecJ-VEdy3Nc4rvuj7bA"/>
+ <bases href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0ELXuEduGP_98XMd0fg"/>
+ <bases href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno4EKmEdyrauqpmnA8jQ"/>
+ <bases href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVEMYbEdyXeo04os5BOw"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/tasks/assess_results.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/tasks/assess_results.xmi
new file mode 100644
index 0000000..3b5504c
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/tasks/assess_results.xmi
@@ -0,0 +1,59 @@
+<?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.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="_a3uz4LBYEdm7Eph_l9Cn9w"
+ name="assess_results,_0l53cMlgEdmt3adZL5Dmdw" guid="_a3uz4LBYEdm7Eph_l9Cn9w" changeDate="2008-02-21T16:23:09.593-0500"
+ version="1.0.0">
+ <mainDescription>The&nbsp;project manager&nbsp;is responsible for coordinating the assessment. He or she&nbsp;discusses with the team how
+the iteration results will be best presented to stakeholders so they can learn as much about the solution as possible. The
+project manager also listens what the team has to say about what went wrong and what went right during the iteration. This
+knowledge will help everybody to make informed decisions for next iteration planning and determine the best course of
+action for the project. This task is performed at the end of every iteration until the end of the project.</mainDescription>
+ <sections xmi:id="_o28GgMMsEdmdo9HxCRR_Gw" name="Review iteration results" guid="_o28GgMMsEdmdo9HxCRR_Gw">
+ <sectionDescription><p>
+ Towards the end of the iteration, the team should jointly assess whether the objectives and evaluation criteria
+ established in the <a class="elementLink"
+ href="./../../practice.mgmt.iterative_dev.base/workproducts/iteration_plan_B46FED39.html"
+ guid="_0aQBEslgEdmt3adZL5Dmdw">Iteration Plan</a> were met, and whether the team adhered to the plan and completed all
+ the work items committed to the iteration.&nbsp;It should&nbsp;use&nbsp;objective measures to the greatest extent
+ possible. To assess that a given work item is completed, the team should ensure that the corresponding test cases were
+ successfully run against it.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_iSiDEIx4Edyzd4h-mxj9YA" name="Demonstrate value and gather feedback"
+ guid="_iSiDEIx4Edyzd4h-mxj9YA">
+ <sectionDescription><p>
+ The team should demonstrate the product to customers, end-users, and other stakeholders to collect their feedback, or
+ better yet, have end users to use the product themselves. This should be done throughout the iteration, or at least in
+ a separate session towards the end of the iteration (see <a class="elementLinkWithType"
+ href="./../../practice.mgmt.iterative_dev.base/guidances/guidelines/iteration_assessment_E27E9DDE.html"
+ guid="_FekBAC4IEdyhZrtGEIITGQ">Guideline: Iteration Assessment</a>). Work that is not completed should not be
+ demonstrated. Resulting knowledge, such as new functionality, requested changes and defects are recorded in the <a
+ class="elementLink" href="./../../practice.mgmt.iterative_dev.base/workproducts/work_items_list_39D03CC8.html"
+ guid="_rGNWsCbSEdqh1LYUOGRh2A">Work Items List</a>, so project priorities, scope and duration can be refined in the
+ next iteration planning.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_iL7cQEpqEdup0IY9DKDPkg" name="Perform a retrospective" guid="_iL7cQEpqEdup0IY9DKDPkg">
+ <sectionDescription><p>
+ Review with the team the approach taken to development and collaboration, the effectiveness of the development
+ environment, the suitability of the working environment, and other factors. Discuss what things went well, what could
+ have gone better, and how things could be changed to deliver better results. Capture assessment results in the current
+ <a class="elementLink" href="./../../practice.mgmt.iterative_dev.base/workproducts/iteration_plan_B46FED39.html"
+ guid="_0aQBEslgEdmt3adZL5Dmdw">Iteration Plan</a>&nbsp;as well as stakeholder feedback and actions to be taken to
+ improve the development approach for next iteration. Record lessons learned in this iteration with&nbsp;a collection of
+ lessons learned for the entire project.&nbsp;&nbsp;
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_1YHH8DLqEdueZPye-FaNgA" name="Close-out project" guid="_1YHH8DLqEdueZPye-FaNgA">
+ <sectionDescription><p>
+ This step must be performed only when the iteration review coincides with the end of the project. Involve the team and
+ stakeholders in&nbsp;a final assessment for project acceptance which, if successful, marks the point when the customer
+ accepts ownership of the software product. Complete the close-out of the project by disposing of the remaining assets
+ and reassigning the remaining staff.
+</p></sectionDescription>
+ </sections>
+ <purpose>Demonstrate the value of the solution increment that was built during the iteration and apply the lessons learned to modify
+the project or improve the process.</purpose>
+</org.eclipse.epf.uma:TaskDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/tasks/manage_iteration.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/tasks/manage_iteration.xmi
new file mode 100644
index 0000000..85ebf83
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/tasks/manage_iteration.xmi
@@ -0,0 +1,101 @@
+<?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.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="-PbfqVxB_j9KN-Jx39_pEUA"
+ name="manage_iteration,_8S2aICbYEdqh1LYUOGRh2A" guid="-PbfqVxB_j9KN-Jx39_pEUA"
+ changeDate="2006-08-31T09:45:37.803-0400" version="1.0.0">
+ <mainDescription><p>
+ Developing the team is part of executing the project. The project manager is responsible for improving the interaction
+ of team members and the trust among the team, incorporating team building into project activities and empowering the
+ team to make decisions. Management is done by objectives and not by time reporting.
+</p>
+<p>
+ The project manager helps the team to meet the iteration objectives by removing constraints and monitoring the progress
+ and work remaining to completion. When the team is falling behind,&nbsp;the project&nbsp;manager&nbsp;helps the team to
+ assess how it can reduce work and still meet the iteration goals. Stakeholders' needs must be continuously met and
+ their issues resolved throughout the iteration. The stakeholders may need to be involved in approving changes and
+ actions that affect them.
+</p></mainDescription>
+ <sections xmi:id="_OE65ICuxEdqTIKp3l5PtzQ" name="Capture and communicate status"
+ guid="_OE65ICuxEdqTIKp3l5PtzQ">
+ <sectionDescription><p>
+ The project manager needs to do the following:&nbsp;
+</p>
+<ul>
+ <li>
+ continuously monitor the project to ensure it is progressing appropriately
+ </li>
+ <li>
+ enable the team to react as soon as possible to any change
+ </li>
+</ul>
+<p>
+ Many alternative means may be used to track the status. Quick, daily meetings with the entire project team are useful
+ to understand what team members have accomplished since the&nbsp;last meeting, and what they plan to accomplish before
+ the next meeting. It also allows the team to identify any blocking issues. See <a class="elementLink"
+ href="./../../core.mgmt.slot.base/guidances/guidelines/collaboration_guidance_slot_D3B8DD40.html"
+ guid="_68JUYN8-Edyhmsbt0Xyl8A">[Collaboration Guidance]</a>.
+</p>
+<p>
+ Another approach is the collection of basic metrics, ideally automatically generated from the tools at hand, or
+ manually assembled. <span
+ style="FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Burndown
+ charts are one of the most useful project progress metrics. They show how many work items where accomplished during
+ previous iterations (or days) and the remaining work. They can be used to track project releases and iterations
+ (see&nbsp;<a class="elementLinkWithType"
+ href="./../../practice.mgmt.iterative_dev.base/guidances/reports/iteration_burndown_9C1C96F5.html"
+ guid="_uAzgkDg3Edu4E8ZdmlYjtA">Report: Iteration Burndown</a>).&nbsp;Communicating project status is as important as
+ gathering it. Keep the information visible to stakeholders and project team at all times.</span> The <a
+ class="elementLink" href="./../../core.mgmt.slot.base/workproducts/project_defiinition_slot_BB8EB6F7.html"
+ guid="_RJMUcNpUEdyzZqGyZ7hwdw">[Project Definition and Scope]</a>&nbsp;should outline which metrics the project should
+ use.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_oIZdkCbZEdqh1LYUOGRh2A" name="Handle exceptions and problems"
+ guid="_oIZdkCbZEdqh1LYUOGRh2A">
+ <sectionDescription><p>
+ One of the project manager's key responsibilities is to know about the project team's problems and issues. The manager
+ needs to focus on problems that are blocking progress. A quick, daily meeting is usually a good way to monitor those
+ problems and issues.&nbsp;A record of issues that have to be solved within the team may be kept in the <a
+ class="elementLink" href="./../../practice.mgmt.iterative_dev.base/workproducts/iteration_plan_B46FED39.html"
+ guid="_0aQBEslgEdmt3adZL5Dmdw">Iteration Plan</a><font color="#003399">.</font>
+</p>
+<p>
+ Identify the cause and impact of problems and exceptions as they arise. Identify possible solutions for problems that
+ have an immediate impact on the short-term goals and objectives and identify who needs to be involved in implementing
+ the solution. Then, define the corrective actions and implement them.&nbsp;
+</p>
+<p>
+ [*** Suggest rewording the last sentence.&nbsp; It is not good English to begin a sentence with 'Then'.&nbsp; ***]
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_xiFJwCbZEdqh1LYUOGRh2A" name="Identify and manage risks" guid="_xiFJwCbZEdqh1LYUOGRh2A">
+ <sectionDescription><p>
+ Identify risks as soon as the project starts and continue identifying and managing risks throughout the project. The <a
+ class="elementLink" href="./../../practice.mgmt.iterative_dev.base/workproducts/risk_list_C4B6F290.html"
+ guid="_Ckay8Cc_EduIsqH1Q6ZuqA">Risk List</a>&nbsp;should be revisited weekly, or at a minimum once per iteration. The
+ entire team should be involved in identifying and mitigating risks.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_Br6VECuxEdqTIKp3l5PtzQ" name="Manage objectives" guid="_Br6VECuxEdqTIKp3l5PtzQ">
+ <sectionDescription>When a team is falling significantly behind, or critical problems occur that prevents the team&nbsp;from meeting the
+iteration objectives, it may be necessary to descope work to ensure that the team delivers a useful product increment by
+the end of the iteration, while maximizing stakeholder value. The project manager should work with the team and
+stakeholders&nbsp;to revise the <a class="elementLink"
+href="./../../practice.mgmt.iterative_dev.base/workproducts/iteration_plan_B46FED39.html"
+guid="_0aQBEslgEdmt3adZL5Dmdw">Iteration Plan</a> and, as necessary, reduce the emphasis on less critical tasks postponing
+them to a subsequent iteration. In rare cases, if the iteration objectives still seem impossible to be met, the team might
+consider terminating the iteration or reformulating the iteration to a new objective.</sectionDescription>
+ </sections>
+ <purpose><p>
+
+
+ To help the team to meet the iteration objectives and&nbsp;keep the project on track.&nbsp;Manage stakeholders
+
+
+ expectations as technical and practical discoveries are made during the project.
+
+
+</p></purpose>
+</org.eclipse.epf.uma:TaskDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/tasks/plan_iteration.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/tasks/plan_iteration.xmi
new file mode 100644
index 0000000..7da0f78
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/tasks/plan_iteration.xmi
@@ -0,0 +1,98 @@
+<?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.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="_Wk7noKe1EdmGSrcKGOYDGg"
+ name="plan_iteration,_0keUEMlgEdmt3adZL5Dmdw" guid="_Wk7noKe1EdmGSrcKGOYDGg" changeDate="2008-02-21T15:32:50.812-0500"
+ version="7.2.0">
+ <mainDescription><p>
+ During project planning, iterations are identified but the estimates have an acceptable uncertainty due to the lack of
+ detail at the project inception. This task is repeated for each iteration within a release. It allows the team to
+ increase the accuracy of the estimates for one iteration, as more detail is known along the project. The project
+ manager&nbsp;has the responsibility of ensuring that the team commits to a reasonable amount&nbsp;of work&nbsp; for the
+ iteration, based on team performance from previous iterations.
+</p></mainDescription>
+ <sections xmi:id="_7bz7AIyAEdyhZb-MhCJrlA" name="Prioritize Work Items List" guid="_7bz7AIyAEdyhZb-MhCJrlA">
+ <sectionDescription>The WIL should be prioritized before you plan the next iteration.&nbsp; Consider what has changed since the last iteration
+plan such as new change requests, shifting priorities of your stakeholders or new risks that have been encountered.</sectionDescription>
+ </sections>
+ <sections xmi:id="_xCSWAOLxEdyM47cGD2jiaQ" name="Refine project definition and scope"
+ guid="_xCSWAOLxEdyM47cGD2jiaQ">
+ <sectionDescription><p>
+ <strong>[*** Does this step belong here?&nbsp; It would be preferable if there was a way for 2-level project planning
+ practice to somehow insert this.&nbsp; But, without a hard dependency on this practice, we don't have a way.
+ ***]</strong>
+</p>
+<p>
+ Depending on the results of the previous iteration assessment&nbsp;the&nbsp;project manager may need to revise
+ the&nbsp;<a class="elementLink"
+ href="./../../core.mgmt.slot.base/workproducts/project_defiinition_and_scope_slot_BB8EB6F7.html"
+ guid="_RJMUcNpUEdyzZqGyZ7hwdw">[Project Definition and Scope]</a>. Necessary changes can encompass the need to acquire
+ new resources, to absorb an unplanned effort increase, or to implement a specific change request.&nbsp;If a change
+ affects defined project milestones, the project manager should consult with the stakeholders before committing to them.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_CtKCMMBHEdqSgKaj2SZBmg" name="Define iteration objectives" guid="_CtKCMMBHEdqSgKaj2SZBmg">
+ <sectionDescription><p>
+ Work with the team to refine the iteration objectives found in the&nbsp;<a class="elementLink"
+ href="./../../core.mgmt.slot.base/workproducts/project_defiinition_slot_BB8EB6F7.html"
+ guid="_RJMUcNpUEdyzZqGyZ7hwdw">[Project Definition and Scope]</a>, and document them in the <a class="elementLink"
+ href="./../../practice.mgmt.iterative_dev.base/workproducts/iteration_plan_B46FED39.html"
+ guid="_0aQBEslgEdmt3adZL5Dmdw">Iteration Plan</a>&nbsp;in order to provide high-level direction to what should be
+ targeted for the iteration. The objectives should be driven based on&nbsp;stakeholder priorities, and will be revised
+ as the iteration plan is finalized. Those objectives are usually defined as high-level capabilities or scenarios that
+ need to be implemented and tested during the iteration in order to deliver increased value to the customer.<br />
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_307v0MMsEdmdo9HxCRR_Gw" name="Commit work to the iteration" guid="_307v0MMsEdmdo9HxCRR_Gw">
+ <sectionDescription><p>
+ The project manager works with the rest of the team, and especially the project stakeholders,&nbsp;to identify the
+ high-priority work items from the <a class="elementLink"
+ href="./../../practice.mgmt.iterative_dev.base/workproducts/work_items_list_39D03CC8.html"
+ guid="_rGNWsCbSEdqh1LYUOGRh2A">Work Items List</a> to be addressed. The high-level objectives provide guidance on what
+ work items should be considered. The <a class="elementLink"
+ href="./../../practice.mgmt.iterative_dev.base/workproducts/iteration_plan_B46FED39.html"
+ guid="_0aQBEslgEdmt3adZL5Dmdw">Iteration Plan</a>&nbsp; from previous iteration should include an assessment of the
+ results and can also be used as input to the current iteration planning.&nbsp;The team reviews its velocity and
+ determines the amount of work that can be done within the iteration.&nbsp;The team breaks down into tasks those work
+ items that are assigned to the iteration&nbsp;and estimates the effort to complete each task (see&nbsp;<a
+ class="elementLinkWithType" href="./../../core.mgmt.common.base/guidances/guidelines/agile_estimation_A4EF42B3.html"
+ guid="_CGHskBEdEdqY7JB6N6CW2w">Guideline: Agile Estimation</a>). Typical tasks range from half day to two days in
+ length.
+</p>
+<p>
+ When a team has decided to take on a work item, it will assign the work to one or several team members. Ideally, this
+ is done by team members signing up to do the work, since this makes people motivated and committed to doing the job,
+ but based on culture, you may instead have the project manager assign the work.<br />
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_HzNVgIyBEdyhZb-MhCJrlA" name="Review risks" guid="_HzNVgIyBEdyhZb-MhCJrlA">
+ <sectionDescription><p>
+ Throughout the project, new assumptions and concerns may arise.&nbsp;The team identifies and prioritizes new&nbsp;risks
+ as part of iteration planning, updating the <a class="elementLink"
+ href="./../../practice.mgmt.iterative_dev.base/workproducts/risk_list_C4B6F290.html"
+ guid="_Ckay8Cc_EduIsqH1Q6ZuqA">Risk List</a>. Responses to risks&nbsp;are added to the&nbsp;<a class="elementLink"
+ href="./../../practice.mgmt.iterative_dev.base/workproducts/work_items_list_39D03CC8.html"
+ guid="_rGNWsCbSEdqh1LYUOGRh2A">Work Items List</a>, influencing the work that is being planned for that iteration.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_7Hqr4MMsEdmdo9HxCRR_Gw" name="Define evaluation criteria" guid="_7Hqr4MMsEdmdo9HxCRR_Gw">
+ <sectionDescription><p>
+ Each iteration should include testing as a part of the evaluation, as well as the test objectives and test cases
+ that&nbsp;need to be detailed. Other evaluation criteria may include successful demonstrations to key stakeholders or
+ favorable usage by a small group of target users. Document evaluation criteria in the <a class="elementLink"
+ href="./../../practice.mgmt.iterative_dev.base/workproducts/iteration_plan_B46FED39.html"
+ guid="_0aQBEslgEdmt3adZL5Dmdw">Iteration Plan</a>.<br />
+</p></sectionDescription>
+ </sections>
+ <purpose><p>
+
+
+ To identify the next increment of system capability, and create a fine-grained plan for achieving that capability
+
+
+ within a single iteration.
+
+
+</p></purpose>
+</org.eclipse.epf.uma:TaskDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/tasks/request_change.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/tasks/request_change.xmi
new file mode 100644
index 0000000..0277d93
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/tasks/request_change.xmi
@@ -0,0 +1,23 @@
+<?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.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="_Nr0S4KeqEdmKDbQuyzCoqQ"
+ name="submit_change_request,_0mwzEclgEdmt3adZL5Dmdw" guid="_Nr0S4KeqEdmKDbQuyzCoqQ"
+ changeDate="2005-07-07T14:57:19.105-0700">
+ <sections xmi:id="_qEkewKuoEdmEGLSmmpF1Sg" name="Gather change request information"
+ guid="_qEkewKuoEdmEGLSmmpF1Sg">
+ <sectionDescription><p>
+ Gather the information required to describe the change request. This should include a description of the requested
+ change, the reason for the change (defect or enhancement), the&nbsp;artifact&nbsp;affected, including&nbsp;the version,
+ and&nbsp;the priority of the change. If possible,&nbsp;provide an estimate of the effort required to implement the
+ change.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_r2aP0KuoEdmEGLSmmpF1Sg" name="Update the Work Item List" guid="_r2aP0KuoEdmEGLSmmpF1Sg">
+ <sectionDescription>Update the <a class="elementLinkWithType"
+href="./../../opn.swd.prac.legacy_pm/workproducts/work_items_list_39D03CC8.html"
+guid="_rGNWsCbSEdqh1LYUOGRh2A">Artifact: Work Items List</a>&nbsp;to&nbsp;document the information that you gathered in the
+previous step.</sectionDescription>
+ </sections>
+</org.eclipse.epf.uma:TaskDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/workproducts/iteration_plan.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/workproducts/iteration_plan.xmi
new file mode 100644
index 0000000..7d98d6a
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/workproducts/iteration_plan.xmi
@@ -0,0 +1,71 @@
+<?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="_BcBR8KX5EdmvhNXG0Oc2uA"
+ name="iteration_plan,_0aQBEslgEdmt3adZL5Dmdw" guid="_BcBR8KX5EdmvhNXG0Oc2uA" changeDate="2006-09-01T16:47:45.470-0400"
+ version="7.2.0">
+ <mainDescription><p>
+ The main objectives of the iteration plan is to provide the team with one central place for information regarding
+ iteration objectives, detailed plan with task assignments, and evaluation results. This artifact also helps the team to
+ monitor the progress of the iteration and keeps the results of the iteration assessment that may be usefull for
+ improving the next one.
+</p>
+<p>
+ The task assignments for an iteration is a subset of all tasks on the <a class="elementLinkWithType"
+ href="./../../opn.swd.prac.legacy_pm/workproducts/work_items_list_39D03CC8.html"
+ guid="_rGNWsCbSEdqh1LYUOGRh2A">Artifact: Work Items List</a>, therefore the iteration plan ideally references those
+ work items.
+</p></mainDescription>
+ <keyConsiderations><p>
+
+ Work items assigned to an iteration do not necessarily have the same priority. When selecting work items from the Work
+
+ Items List, the iteration plan may end up having work items with different priorities (for example, you assign the
+
+ remaining high priority work items, plus a few mid priority ones from the Work Items List). No matter what previous
+
+ priorities the work items had, when assigned to an iteration&nbsp;the team has to make sure they are able to develop
+
+ what has been&nbsp;assigned to the&nbsp;iteration, and deciding on&nbsp;what to&nbsp;develop first (or
+
+ even&nbsp;develop things in parallel) on an iteration will vary from project to project, from iteration to iteration.
+
+</p></keyConsiderations>
+ <purpose><p>
+
+ Communicate the objectives, task assignment, and evaluation criteria for a given iteration.
+
+</p></purpose>
+ <representationOptions><p>
+
+ The level of detail/formality of the plan must be adapted to what you need to successfully meet these objectives.The
+
+ plan could, for example, be captured on the following places:
+
+</p>
+
+<ul>
+
+ <li>
+
+ a whiteboard listing the objectives, task assignments and evaluation criteria;
+
+ </li>
+
+ <li>
+
+ a 1-page document listing the objectives and evaluation criteria of the iteration, as well as referencing the Work
+
+ Items List for assignments for that iteration;
+
+ </li>
+
+ <li>
+
+ a more complex document, supported by a Gantt or Pert chart in a project planning tool.
+
+ </li>
+
+</ul></representationOptions>
+</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/praclib/temp/practice.mgmt.iterative_dev.base/workproducts/work_items_list.xmi b/praclib/temp/practice.mgmt.iterative_dev.base/workproducts/work_items_list.xmi
new file mode 100644
index 0000000..15ba02d
--- /dev/null
+++ b/praclib/temp/practice.mgmt.iterative_dev.base/workproducts/work_items_list.xmi
@@ -0,0 +1,86 @@
+<?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="-buxz4BVToq97bSxaqyjySg"
+ name="work_items_list,_rGNWsCbSEdqh1LYUOGRh2A" guid="-buxz4BVToq97bSxaqyjySg"
+ changeDate="2008-02-13T14:04:39.593-0500" version="1.0.0">
+ <mainDescription><p>
+ This artifact provides a focal point for the entire team:
+</p>
+<ul>
+ <li>
+ It provides one list containing all requests for additional capabilities or enhancement for that application. Note
+ that some of these requests may never be implemented, or be implemented in later projects
+ </li>
+ <li>
+ It provides one list of all the work to be prioritized, estimated, and assigned within the project. The risk list
+ is prioritized separately.
+ </li>
+ <li>
+ It provides one place to go to for the development team to understand what <a class="elementLink"
+ href="./../../practice.mgmt.iterative_dev.base/guidances/concepts/micro_increments_C8773066.html"
+ guid="_S80VwCNbEdyCq8v2ZO4QcA">Micro-Increments</a>&nbsp;need to be delivered, get references to material required
+ to carry out the work, and one place to go to report progress made.
+ </li>
+</ul>
+<p>
+ These are the typical work items that go into this list:
+</p>
+<ul>
+ <li>
+ Use cases (and references to use-case specifications)
+ </li>
+ <li>
+ System-wide requirements
+ </li>
+ <li>
+ Changes and enhancement requests
+ </li>
+ <li>
+ Defects
+ </li>
+ <li>
+ Development tasks
+ </li>
+</ul>
+<p>
+ Work items can be very large in scope, especially when capturing requests for enhancements, such as “Support Financial
+ Planning” for a personal finance application. To allow the application to be developed in micro-increments, work items
+ are analyzed and broken down into smaller work items so they can be assigned to an iteration, such as a use-case
+ scenario for&nbsp;“Calculate Net Worth”. Further breakdown may be required to identify suitable tasks to be assigned to
+ developers, such as “Develop UI for Calculate Net Worth”. This means that work items often have parent/child
+ relationships, where the lowest level is a specification and tracking device for micro-increments.
+</p></mainDescription>
+ <keyConsiderations><p>
+ Work Items should contain estimates, see <a class="elementLinkWithType"
+ href="./../../practice.mgmt.iterative_dev.base/guidances/guidelines/managing_work_items_32AC6ABD.html"
+ guid="_7vEXEMA4EdqSgKaj2SZBmg">Guideline: Managing Work Items</a>&nbsp;and <a class="elementLinkWithType"
+ href="./../../core.mgmt.common.base/guidances/guidelines/agile_estimation_A4EF42B3.html"
+ guid="_CGHskBEdEdqY7JB6N6CW2w">Guideline: Agile Estimation</a>.
+</p></keyConsiderations>
+ <purpose>To collect all requests for work that will potentially be taken on within the project, so work can be prioritized, effort
+estimated and progress tracked.</purpose>
+ <representationOptions><h3>
+ As a spreadsheet or database
+</h3>
+<p>
+ The Work Items List can be captured as a separate artifact, represented by a spreadsheet or database table. See <a class="elementLinkWithType" href="./../../openup/guidances/examples/work_items_list_F527B77D.html" guid="_nHomIDgzEdu4E8ZdmlYjtA">Example: Work Items List</a>.
+</p>
+<h3>
+ In specific tools
+</h3>
+<p>
+ Project Management, Requirements Management and Change Request tools are&nbsp;options to capture the list of work to be
+ done.
+</p>
+<h3>
+ As part of the Iteration Plan
+</h3>
+<p>
+ The <a class="elementLinkWithType" href="./../../openup/workproducts/iteration_plan_B46FED39.html" guid="_0aQBEslgEdmt3adZL5Dmdw">Artifact: Iteration Plan</a> typically references work items that are assigned to that
+ iteration. If the team is capturing the iteration plan on a whiteboard, for example, the team may choose to reference
+ high-level work items in the Work Items List that are assigned to the iteration, and maintain low-level child work
+ items used to track day-to-day work only within an iteration plan.<br />
+</p></representationOptions>
+</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/.project b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/.project
new file mode 100644
index 0000000..5652238
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>practice.mgmt.risk_value_lifecycle.base</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/capabilitypatterns/risk_value_lifecycle_phases/content.xmi b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/capabilitypatterns/risk_value_lifecycle_phases/content.xmi
new file mode 100644
index 0000000..e210973
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/capabilitypatterns/risk_value_lifecycle_phases/content.xmi
@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:ProcessDescription 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="-1IlTGK1mPdoxAMwuAjqLYg"
+ name="ris_value_lifecycle_phases,_FzchseL7EdyM47cGD2jiaQ" guid="-1IlTGK1mPdoxAMwuAjqLYg"/>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/capabilitypatterns/risk_value_lifecycle_phases/diagram.xmi b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/capabilitypatterns/risk_value_lifecycle_phases/diagram.xmi
new file mode 100644
index 0000000..9fb6cf7
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/capabilitypatterns/risk_value_lifecycle_phases/diagram.xmi
@@ -0,0 +1,413 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xmi:XMI xmi:version="2.0"
+ xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xmlns:ecore="http://www.eclipse.org/emf/2002/Ecore" xmlns:notation="http://www.eclipse.org/gmf/runtime/1.0.1/notation"
+ xmlns:uml="http://www.eclipse.org/uml2/2.1.0/UML">
+ <uml:Activity xmi:id="_q9BVAOL-EdyM47cGD2jiaQ" name="risk_value_lifecycle_phases">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_q9BVAeL-EdyM47cGD2jiaQ" source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_q9BVAuL-EdyM47cGD2jiaQ"
+ key="uri" value="uma://_SKnAwOL9EdyM47cGD2jiaQ#_SKnA1uL9EdyM47cGD2jiaQ"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_q9BVA-L-EdyM47cGD2jiaQ"
+ key="type" value="Activity"/>
+ </eAnnotations>
+ <node xmi:type="uml:StructuredActivityNode" xmi:id="_q96s4OL-EdyM47cGD2jiaQ" name="Inception Iteration [1..n]"
+ outgoing="_VvjcQOL_EdyM47cGD2jiaQ" incoming="_Pjx2gOL_EdyM47cGD2jiaQ">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_q96s4eL-EdyM47cGD2jiaQ"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_q96s4uL-EdyM47cGD2jiaQ"
+ key="uri" value="uma://_SKnAwOL9EdyM47cGD2jiaQ#_SKnAzuL9EdyM47cGD2jiaQ"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_q96s4-L-EdyM47cGD2jiaQ"
+ key="type" value="Iteration"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:ActivityParameterNode" xmi:id="_q96s5OL-EdyM47cGD2jiaQ" name="Lifecycle Objectives Milestone"
+ outgoing="_82ipYOMAEdyM47cGD2jiaQ" incoming="_VvjcQOL_EdyM47cGD2jiaQ">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_q96s5eL-EdyM47cGD2jiaQ"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_q96s5uL-EdyM47cGD2jiaQ"
+ key="uri" value="uma://_SKnAwOL9EdyM47cGD2jiaQ#_0_FFQOL9EdyM47cGD2jiaQ"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_q96s5-L-EdyM47cGD2jiaQ"
+ key="type" value="Milestone"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:StructuredActivityNode" xmi:id="_q96s6OL-EdyM47cGD2jiaQ" name="Elaboration Iteration [1..n]"
+ outgoing="_ioe2gOL_EdyM47cGD2jiaQ" incoming="_82ipYOMAEdyM47cGD2jiaQ">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_q96s6eL-EdyM47cGD2jiaQ"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_q96s6uL-EdyM47cGD2jiaQ"
+ key="uri" value="uma://_SKnAwOL9EdyM47cGD2jiaQ#_SKnA0uL9EdyM47cGD2jiaQ"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_q96s6-L-EdyM47cGD2jiaQ"
+ key="type" value="Iteration"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:ActivityParameterNode" xmi:id="_q96s7OL-EdyM47cGD2jiaQ" name="Lifecycle Architecture Milestone"
+ outgoing="_98kdUOMAEdyM47cGD2jiaQ" incoming="_ioe2gOL_EdyM47cGD2jiaQ">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_q96s7eL-EdyM47cGD2jiaQ"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_q96s7uL-EdyM47cGD2jiaQ"
+ key="uri" value="uma://_SKnAwOL9EdyM47cGD2jiaQ#_bTNukOL-EdyM47cGD2jiaQ"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_q96s7-L-EdyM47cGD2jiaQ"
+ key="type" value="Milestone"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:StructuredActivityNode" xmi:id="_q96s8OL-EdyM47cGD2jiaQ" name="Construction Iteration [1..n]"
+ outgoing="_rNoR8OMAEdyM47cGD2jiaQ" incoming="_98kdUOMAEdyM47cGD2jiaQ">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_q96s8eL-EdyM47cGD2jiaQ"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_q96s8uL-EdyM47cGD2jiaQ"
+ key="uri" value="uma://_SKnAwOL9EdyM47cGD2jiaQ#_SKnAyOL9EdyM47cGD2jiaQ"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_q96s8-L-EdyM47cGD2jiaQ"
+ key="type" value="Iteration"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:ActivityParameterNode" xmi:id="_q96s9OL-EdyM47cGD2jiaQ" name="Initial Operational Capability"
+ outgoing="_-2iLMOMAEdyM47cGD2jiaQ" incoming="_rNoR8OMAEdyM47cGD2jiaQ">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_q96s9eL-EdyM47cGD2jiaQ"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_q96s9uL-EdyM47cGD2jiaQ"
+ key="uri" value="uma://_SKnAwOL9EdyM47cGD2jiaQ#_gIkT8OL-EdyM47cGD2jiaQ"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_q96s9-L-EdyM47cGD2jiaQ"
+ key="type" value="Milestone"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:StructuredActivityNode" xmi:id="_q96s-OL-EdyM47cGD2jiaQ" name="Transition Iteration [1..n]"
+ outgoing="_yLBh4OMAEdyM47cGD2jiaQ" incoming="_-2iLMOMAEdyM47cGD2jiaQ">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_q96s-eL-EdyM47cGD2jiaQ"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_q96s-uL-EdyM47cGD2jiaQ"
+ key="uri" value="uma://_SKnAwOL9EdyM47cGD2jiaQ#_SKnAxOL9EdyM47cGD2jiaQ"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_q96s--L-EdyM47cGD2jiaQ"
+ key="type" value="Iteration"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:ActivityParameterNode" xmi:id="_q96s_OL-EdyM47cGD2jiaQ" name="Product Release Milestone"
+ outgoing="_AuytUOMBEdyM47cGD2jiaQ" incoming="_yLBh4OMAEdyM47cGD2jiaQ">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_q96s_eL-EdyM47cGD2jiaQ"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_q96s_uL-EdyM47cGD2jiaQ"
+ key="uri" value="uma://_SKnAwOL9EdyM47cGD2jiaQ#_l4LiIOL-EdyM47cGD2jiaQ"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_q96s_-L-EdyM47cGD2jiaQ"
+ key="type" value="Milestone"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:InitialNode" xmi:id="_4dvIAOL-EdyM47cGD2jiaQ" outgoing="_Pjx2gOL_EdyM47cGD2jiaQ"/>
+ <node xmi:type="uml:ActivityFinalNode" xmi:id="_5mKIoOL-EdyM47cGD2jiaQ" incoming="_AuytUOMBEdyM47cGD2jiaQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_Pjx2gOL_EdyM47cGD2jiaQ" source="_4dvIAOL-EdyM47cGD2jiaQ"
+ target="_q96s4OL-EdyM47cGD2jiaQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_VvjcQOL_EdyM47cGD2jiaQ" name="[last iteration in Inception] "
+ source="_q96s4OL-EdyM47cGD2jiaQ" target="_q96s5OL-EdyM47cGD2jiaQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_ioe2gOL_EdyM47cGD2jiaQ" name="[last iteration in Elaboration] "
+ source="_q96s6OL-EdyM47cGD2jiaQ" target="_q96s7OL-EdyM47cGD2jiaQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_rNoR8OMAEdyM47cGD2jiaQ" name="[last iteration in Construction] "
+ source="_q96s8OL-EdyM47cGD2jiaQ" target="_q96s9OL-EdyM47cGD2jiaQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_yLBh4OMAEdyM47cGD2jiaQ" name="[last iteration in Transtion] "
+ source="_q96s-OL-EdyM47cGD2jiaQ" target="_q96s_OL-EdyM47cGD2jiaQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_82ipYOMAEdyM47cGD2jiaQ" source="_q96s5OL-EdyM47cGD2jiaQ"
+ target="_q96s6OL-EdyM47cGD2jiaQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_98kdUOMAEdyM47cGD2jiaQ" source="_q96s7OL-EdyM47cGD2jiaQ"
+ target="_q96s8OL-EdyM47cGD2jiaQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_-2iLMOMAEdyM47cGD2jiaQ" source="_q96s9OL-EdyM47cGD2jiaQ"
+ target="_q96s-OL-EdyM47cGD2jiaQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_AuytUOMBEdyM47cGD2jiaQ" source="_q96s_OL-EdyM47cGD2jiaQ"
+ target="_5mKIoOL-EdyM47cGD2jiaQ"/>
+ </uml:Activity>
+ <notation:Diagram xmi:id="_q9BVBOL-EdyM47cGD2jiaQ" type="AD" element="_q9BVAOL-EdyM47cGD2jiaQ"
+ name="risk_value_lifecycle_phases" measurementUnit="Pixel">
+ <children xmi:type="notation:Node" xmi:id="_q96tAOL-EdyM47cGD2jiaQ" type="1011"
+ element="_q96s4OL-EdyM47cGD2jiaQ">
+ <children xmi:type="notation:Node" xmi:id="_q96tBuL-EdyM47cGD2jiaQ" type="4010"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_q96tAeL-EdyM47cGD2jiaQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_q96tAuL-EdyM47cGD2jiaQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_q96tA-L-EdyM47cGD2jiaQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_q96tBOL-EdyM47cGD2jiaQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_q96tBeL-EdyM47cGD2jiaQ"
+ x="144" y="99" width="117"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_q96tB-L-EdyM47cGD2jiaQ" type="1012"
+ element="_q96s5OL-EdyM47cGD2jiaQ">
+ <children xmi:type="notation:Node" xmi:id="_q96tDeL-EdyM47cGD2jiaQ" type="4011"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_q96tCOL-EdyM47cGD2jiaQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_q96tCeL-EdyM47cGD2jiaQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_q96tCuL-EdyM47cGD2jiaQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_q96tC-L-EdyM47cGD2jiaQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_q96tDOL-EdyM47cGD2jiaQ"
+ x="125" y="246" width="154"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_q96tDuL-EdyM47cGD2jiaQ" type="1011"
+ element="_q96s6OL-EdyM47cGD2jiaQ">
+ <children xmi:type="notation:Node" xmi:id="_q-Ed4OL-EdyM47cGD2jiaQ" type="4010"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_q96tD-L-EdyM47cGD2jiaQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_q96tEOL-EdyM47cGD2jiaQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_q96tEeL-EdyM47cGD2jiaQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_q96tEuL-EdyM47cGD2jiaQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_q96tE-L-EdyM47cGD2jiaQ"
+ x="312" y="99" width="128"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_q-Ed4eL-EdyM47cGD2jiaQ" type="1012"
+ element="_q96s7OL-EdyM47cGD2jiaQ">
+ <children xmi:type="notation:Node" xmi:id="_q-Ed5-L-EdyM47cGD2jiaQ" type="4011"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_q-Ed4uL-EdyM47cGD2jiaQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_q-Ed4-L-EdyM47cGD2jiaQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_q-Ed5OL-EdyM47cGD2jiaQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_q-Ed5eL-EdyM47cGD2jiaQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_q-Ed5uL-EdyM47cGD2jiaQ"
+ x="295" y="246" width="163"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_q-Ed6OL-EdyM47cGD2jiaQ" type="1011"
+ element="_q96s8OL-EdyM47cGD2jiaQ">
+ <children xmi:type="notation:Node" xmi:id="_q-Ed7uL-EdyM47cGD2jiaQ" type="4010"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_q-Ed6eL-EdyM47cGD2jiaQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_q-Ed6uL-EdyM47cGD2jiaQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_q-Ed6-L-EdyM47cGD2jiaQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_q-Ed7OL-EdyM47cGD2jiaQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_q-Ed7eL-EdyM47cGD2jiaQ"
+ x="504" y="99" width="136"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_q-Ed7-L-EdyM47cGD2jiaQ" type="1012"
+ element="_q96s9OL-EdyM47cGD2jiaQ">
+ <children xmi:type="notation:Node" xmi:id="_q-Ed9eL-EdyM47cGD2jiaQ" type="4011"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_q-Ed8OL-EdyM47cGD2jiaQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_q-Ed8eL-EdyM47cGD2jiaQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_q-Ed8uL-EdyM47cGD2jiaQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_q-Ed8-L-EdyM47cGD2jiaQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_q-Ed9OL-EdyM47cGD2jiaQ"
+ x="504" y="246" width="137"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_q-Ed9uL-EdyM47cGD2jiaQ" type="1011"
+ element="_q96s-OL-EdyM47cGD2jiaQ">
+ <children xmi:type="notation:Node" xmi:id="_q-Nn0OL-EdyM47cGD2jiaQ" type="4010"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_q-Ed9-L-EdyM47cGD2jiaQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_q-Ed-OL-EdyM47cGD2jiaQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_q-Ed-eL-EdyM47cGD2jiaQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_q-Ed-uL-EdyM47cGD2jiaQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_q-Ed--L-EdyM47cGD2jiaQ"
+ x="684" y="99" width="121"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_q-Nn0eL-EdyM47cGD2jiaQ" type="1012"
+ element="_q96s_OL-EdyM47cGD2jiaQ">
+ <children xmi:type="notation:Node" xmi:id="_q-Nn1-L-EdyM47cGD2jiaQ" type="4011"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_q-Nn0uL-EdyM47cGD2jiaQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_q-Nn0-L-EdyM47cGD2jiaQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_q-Nn1OL-EdyM47cGD2jiaQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_q-Nn1eL-EdyM47cGD2jiaQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_q-Nn1uL-EdyM47cGD2jiaQ"
+ x="677" y="246" width="134"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_4dvIAeL-EdyM47cGD2jiaQ" type="1004"
+ element="_4dvIAOL-EdyM47cGD2jiaQ">
+ <children xmi:type="notation:Node" xmi:id="_4dvIB-L-EdyM47cGD2jiaQ" type="4003">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_4dvICOL-EdyM47cGD2jiaQ"
+ y="5"/>
+ </children>
+ <styles xmi:type="notation:FontStyle" xmi:id="_4dvIAuL-EdyM47cGD2jiaQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_4dvIA-L-EdyM47cGD2jiaQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_4dvIBOL-EdyM47cGD2jiaQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_4dvIBeL-EdyM47cGD2jiaQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_4dvIBuL-EdyM47cGD2jiaQ"
+ x="44" y="115" width="20"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_5mKIoeL-EdyM47cGD2jiaQ" type="1001"
+ element="_5mKIoOL-EdyM47cGD2jiaQ">
+ <children xmi:type="notation:Node" xmi:id="_5mTSkOL-EdyM47cGD2jiaQ" type="4001">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_5mTSkeL-EdyM47cGD2jiaQ"
+ y="5"/>
+ </children>
+ <styles xmi:type="notation:FontStyle" xmi:id="_5mKIouL-EdyM47cGD2jiaQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_5mKIo-L-EdyM47cGD2jiaQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_5mKIpOL-EdyM47cGD2jiaQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_5mKIpeL-EdyM47cGD2jiaQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_5mKIpuL-EdyM47cGD2jiaQ"
+ x="906" y="260" width="24"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_0WBPQOL_EdyM47cGD2jiaQ" type="Note">
+ <children xmi:type="notation:Node" xmi:id="_0WBPQ-L_EdyM47cGD2jiaQ" type="DiagramName">
+ <element xsi:nil="true"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_0WBPROL_EdyM47cGD2jiaQ" type="Description">
+ <element xsi:nil="true"/>
+ </children>
+ <styles xmi:type="notation:ShapeStyle" xmi:id="_0WBPQeL_EdyM47cGD2jiaQ" fontName="Arial"
+ fontHeight="8" description="Inception Phase" fillColor="13369343" lineColor="6737151"/>
+ <element xsi:nil="true"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_0WBPQuL_EdyM47cGD2jiaQ"
+ x="144" y="24" width="109" height="25"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_YXq4kOMAEdyM47cGD2jiaQ" type="Note">
+ <children xmi:type="notation:Node" xmi:id="_YXq4k-MAEdyM47cGD2jiaQ" type="DiagramName">
+ <element xsi:nil="true"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_YXq4lOMAEdyM47cGD2jiaQ" type="Description">
+ <element xsi:nil="true"/>
+ </children>
+ <styles xmi:type="notation:ShapeStyle" xmi:id="_YXq4keMAEdyM47cGD2jiaQ" fontName="Arial"
+ fontHeight="8" description="Elaboration Phase" fillColor="13369343" lineColor="6737151"/>
+ <element xsi:nil="true"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_YXq4kuMAEdyM47cGD2jiaQ"
+ x="308" y="24" width="113" height="25"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_eV5KgOMAEdyM47cGD2jiaQ" type="Note">
+ <children xmi:type="notation:Node" xmi:id="_eV5Kg-MAEdyM47cGD2jiaQ" type="DiagramName">
+ <element xsi:nil="true"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_eV5KhOMAEdyM47cGD2jiaQ" type="Description">
+ <element xsi:nil="true"/>
+ </children>
+ <styles xmi:type="notation:ShapeStyle" xmi:id="_eV5KgeMAEdyM47cGD2jiaQ" fontName="Arial"
+ fontHeight="8" description="Construction Phase" fillColor="13369343" lineColor="6737151"/>
+ <element xsi:nil="true"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_eV5KguMAEdyM47cGD2jiaQ"
+ x="516" y="24" width="121" height="25"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_hrIA8OMAEdyM47cGD2jiaQ" type="Note">
+ <children xmi:type="notation:Node" xmi:id="_hrIA8-MAEdyM47cGD2jiaQ" type="DiagramName">
+ <element xsi:nil="true"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_hrIA9OMAEdyM47cGD2jiaQ" type="Description">
+ <element xsi:nil="true"/>
+ </children>
+ <styles xmi:type="notation:ShapeStyle" xmi:id="_hrIA8eMAEdyM47cGD2jiaQ" fontName="Arial"
+ fontHeight="8" description="Transition Phase" fillColor="13369343" lineColor="6737151"/>
+ <element xsi:nil="true"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_hrIA8uMAEdyM47cGD2jiaQ"
+ x="684" y="24" width="109" height="25"/>
+ </children>
+ <styles xmi:type="notation:PageStyle" xmi:id="_q9BVBeL-EdyM47cGD2jiaQ"/>
+ <styles xmi:type="notation:GuideStyle" xmi:id="_q9BVBuL-EdyM47cGD2jiaQ"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_q9BVB-L-EdyM47cGD2jiaQ"/>
+ <edges xmi:type="notation:Edge" xmi:id="_Pj7ngOL_EdyM47cGD2jiaQ" type="3001" element="_Pjx2gOL_EdyM47cGD2jiaQ"
+ source="_4dvIAeL-EdyM47cGD2jiaQ" target="_q96tAOL-EdyM47cGD2jiaQ">
+ <children xmi:type="notation:Node" xmi:id="_Pj7nheL_EdyM47cGD2jiaQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_Pj7nhuL_EdyM47cGD2jiaQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_Pj7ngeL_EdyM47cGD2jiaQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_Pj7nguL_EdyM47cGD2jiaQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_Pj7ng-L_EdyM47cGD2jiaQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_Pj7nhOL_EdyM47cGD2jiaQ"
+ points="[10, -1, -138, -1]$[141, -26, -7, -26]"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_VvtNQeL_EdyM47cGD2jiaQ" type="3001" element="_VvjcQOL_EdyM47cGD2jiaQ"
+ source="_q96tAOL-EdyM47cGD2jiaQ" target="_q96tB-L-EdyM47cGD2jiaQ">
+ <children xmi:type="notation:Node" xmi:id="_VvtNRuL_EdyM47cGD2jiaQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_VvtNR-L_EdyM47cGD2jiaQ"
+ x="-12" y="17"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_VvtNQuL_EdyM47cGD2jiaQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_VvtNQ-L_EdyM47cGD2jiaQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_VvtNROL_EdyM47cGD2jiaQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_VvtNReL_EdyM47cGD2jiaQ"
+ points="[7, 27, 7, -120]$[7, 121, 7, -26]"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_ioe2guL_EdyM47cGD2jiaQ" type="3001" element="_ioe2gOL_EdyM47cGD2jiaQ"
+ source="_q96tDuL-EdyM47cGD2jiaQ" target="_q-Ed4eL-EdyM47cGD2jiaQ">
+ <children xmi:type="notation:Node" xmi:id="_ioe2h-L_EdyM47cGD2jiaQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_ioe2iOL_EdyM47cGD2jiaQ"
+ x="-12" y="11"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_ioe2g-L_EdyM47cGD2jiaQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_ioe2hOL_EdyM47cGD2jiaQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_ioe2heL_EdyM47cGD2jiaQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_ioe2huL_EdyM47cGD2jiaQ"
+ points="[1, 27, 1, -120]$[1, 121, 1, -26]"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_rNoR8uMAEdyM47cGD2jiaQ" type="3001" element="_rNoR8OMAEdyM47cGD2jiaQ"
+ source="_q-Ed6OL-EdyM47cGD2jiaQ" target="_q-Ed7-L-EdyM47cGD2jiaQ">
+ <children xmi:type="notation:Node" xmi:id="_rNoR9-MAEdyM47cGD2jiaQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_rNoR-OMAEdyM47cGD2jiaQ"
+ x="-12" y="11"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_rNoR8-MAEdyM47cGD2jiaQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_rNoR9OMAEdyM47cGD2jiaQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_rNoR9eMAEdyM47cGD2jiaQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_rNoR9uMAEdyM47cGD2jiaQ"
+ points="[-2, 27, -2, -120]$[-68, 141, -68, -6]"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_yLBh4uMAEdyM47cGD2jiaQ" type="3001" element="_yLBh4OMAEdyM47cGD2jiaQ"
+ source="_q-Ed9uL-EdyM47cGD2jiaQ" target="_q-Nn0eL-EdyM47cGD2jiaQ">
+ <children xmi:type="notation:Node" xmi:id="_yLBh5-MAEdyM47cGD2jiaQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_yLBh6OMAEdyM47cGD2jiaQ"
+ x="-24" y="5"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_yLBh4-MAEdyM47cGD2jiaQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_yLBh5OMAEdyM47cGD2jiaQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_yLBh5eMAEdyM47cGD2jiaQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_yLBh5uMAEdyM47cGD2jiaQ"
+ points="[-6, 27, 0, -103]$[-9, 121, -3, -9]"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_yLBh6eMAEdyM47cGD2jiaQ"
+ id="(0.4552239,0.16981132)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_82ipYuMAEdyM47cGD2jiaQ" type="3001" element="_82ipYOMAEdyM47cGD2jiaQ"
+ source="_q96tB-L-EdyM47cGD2jiaQ" target="_q96tDuL-EdyM47cGD2jiaQ">
+ <children xmi:type="notation:Node" xmi:id="_82ipZ-MAEdyM47cGD2jiaQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_82ipaOMAEdyM47cGD2jiaQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_82ipY-MAEdyM47cGD2jiaQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_82ipZOMAEdyM47cGD2jiaQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_82ipZeMAEdyM47cGD2jiaQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_82ipZuMAEdyM47cGD2jiaQ"
+ points="[13, -12, -153, 121]$[102, -130, -64, 3]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_82ipaeMAEdyM47cGD2jiaQ"
+ id="(0.5519481,0.2264151)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_98kdUuMAEdyM47cGD2jiaQ" type="3001" element="_98kdUOMAEdyM47cGD2jiaQ"
+ source="_q-Ed4eL-EdyM47cGD2jiaQ" target="_q-Ed6OL-EdyM47cGD2jiaQ">
+ <children xmi:type="notation:Node" xmi:id="_98kdV-MAEdyM47cGD2jiaQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_98kdWOMAEdyM47cGD2jiaQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_98kdU-MAEdyM47cGD2jiaQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_98kdVOMAEdyM47cGD2jiaQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_98kdVeMAEdyM47cGD2jiaQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_98kdVuMAEdyM47cGD2jiaQ"
+ points="[32, -26, -164, 121]$[128, -143, -68, 4]"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_-2iLMuMAEdyM47cGD2jiaQ" type="3001" element="_-2iLMOMAEdyM47cGD2jiaQ"
+ source="_q-Ed7-L-EdyM47cGD2jiaQ" target="_q-Ed9uL-EdyM47cGD2jiaQ">
+ <children xmi:type="notation:Node" xmi:id="_-2iLN-MAEdyM47cGD2jiaQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_-2iLOOMAEdyM47cGD2jiaQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_-2iLM-MAEdyM47cGD2jiaQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_-2iLNOMAEdyM47cGD2jiaQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_-2iLNeMAEdyM47cGD2jiaQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_-2iLNuMAEdyM47cGD2jiaQ"
+ points="[14, -13, -148, 139]$[159, -160, -3, -8]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_-2iLOeMAEdyM47cGD2jiaQ"
+ id="(0.5182482,0.24528302)"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_-2iLOuMAEdyM47cGD2jiaQ"
+ id="(0.43801653,0.1509434)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_Au73QOMBEdyM47cGD2jiaQ" type="3001" element="_AuytUOMBEdyM47cGD2jiaQ"
+ source="_q-Nn0eL-EdyM47cGD2jiaQ" target="_5mKIoeL-EdyM47cGD2jiaQ">
+ <children xmi:type="notation:Node" xmi:id="_Au73ReMBEdyM47cGD2jiaQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_Au73RuMBEdyM47cGD2jiaQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_Au73QeMBEdyM47cGD2jiaQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_Au73QuMBEdyM47cGD2jiaQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_Au73Q-MBEdyM47cGD2jiaQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_Au73ROMBEdyM47cGD2jiaQ"
+ points="[67, -1, -107, -1]$[162, -1, -12, -1]"/>
+ </edges>
+ </notation:Diagram>
+</xmi:XMI>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/capabilitypatterns/risk_value_lifecycle_phases/model.xmi b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/capabilitypatterns/risk_value_lifecycle_phases/model.xmi
new file mode 100644
index 0000000..29165d3
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/capabilitypatterns/risk_value_lifecycle_phases/model.xmi
@@ -0,0 +1,72 @@
+<?xml version="1.0" encoding="UTF-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.4/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.2.0" xmlns:epf="http://www.eclipse.org/epf"
+ epf:version="1.2.0">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_THHFQOL9EdyM47cGD2jiaQ"
+ guid="_THHFQOL9EdyM47cGD2jiaQ">
+ <resourceDescriptors xmi:id="_THHFQeL9EdyM47cGD2jiaQ" id="-1IlTGK1mPdoxAMwuAjqLYg"
+ uri="content.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:ProcessComponent xmi:id="_SKnAwOL9EdyM47cGD2jiaQ" name="risk_value_lifecycle_phases"
+ guid="_SKnAwOL9EdyM47cGD2jiaQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_SKnAzeL9EdyM47cGD2jiaQ"
+ name="Inception Iteration [1..n]" guid="_SKnAzeL9EdyM47cGD2jiaQ">
+ <processElements xsi:type="org.eclipse.epf.uma:Iteration" xmi:id="_SKnAzuL9EdyM47cGD2jiaQ"
+ name="Inception Iteration [1..n]" guid="_SKnAzuL9EdyM47cGD2jiaQ" presentationName="Inception Iteration [1..n]"
+ superActivities="_SKnA1uL9EdyM47cGD2jiaQ" isRepeatable="true"/>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_SKnA0eL9EdyM47cGD2jiaQ"
+ name="Elaboration Iteration [1..n]" guid="_SKnA0eL9EdyM47cGD2jiaQ">
+ <processElements xsi:type="org.eclipse.epf.uma:Iteration" xmi:id="_SKnA0uL9EdyM47cGD2jiaQ"
+ name="Elaboration Iteration [1..n]" guid="_SKnA0uL9EdyM47cGD2jiaQ" presentationName="Elaboration Iteration [1..n]"
+ superActivities="_SKnA1uL9EdyM47cGD2jiaQ" isRepeatable="true" linkToPredecessor="_82ipYeMAEdyM47cGD2jiaQ"/>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_82ipYeMAEdyM47cGD2jiaQ"
+ guid="_82ipYeMAEdyM47cGD2jiaQ" pred="_0_FFQOL9EdyM47cGD2jiaQ"/>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_SKnAx-L9EdyM47cGD2jiaQ"
+ name="Construction Iteration [1..n]" guid="_SKnAx-L9EdyM47cGD2jiaQ">
+ <processElements xsi:type="org.eclipse.epf.uma:Iteration" xmi:id="_SKnAyOL9EdyM47cGD2jiaQ"
+ name="Construction Iteration [1..n]" guid="_SKnAyOL9EdyM47cGD2jiaQ" presentationName="Construction Iteration [1..n]"
+ superActivities="_SKnA1uL9EdyM47cGD2jiaQ" isRepeatable="true" linkToPredecessor="_98kdUeMAEdyM47cGD2jiaQ"/>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_98kdUeMAEdyM47cGD2jiaQ"
+ guid="_98kdUeMAEdyM47cGD2jiaQ" pred="_bTNukOL-EdyM47cGD2jiaQ"/>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_SKnAw-L9EdyM47cGD2jiaQ"
+ name="Transition Iteration [1..n]" guid="_SKnAw-L9EdyM47cGD2jiaQ">
+ <processElements xsi:type="org.eclipse.epf.uma:Iteration" xmi:id="_SKnAxOL9EdyM47cGD2jiaQ"
+ name="Transition Iteration [1..n]" guid="_SKnAxOL9EdyM47cGD2jiaQ" presentationName="Transition Iteration [1..n]"
+ superActivities="_SKnA1uL9EdyM47cGD2jiaQ" isRepeatable="true" linkToPredecessor="_-2iLMeMAEdyM47cGD2jiaQ"/>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_-2iLMeMAEdyM47cGD2jiaQ"
+ guid="_-2iLMeMAEdyM47cGD2jiaQ" pred="_gIkT8OL-EdyM47cGD2jiaQ"/>
+ </childPackages>
+ <processElements xsi:type="org.eclipse.epf.uma:Milestone" xmi:id="_0_FFQOL9EdyM47cGD2jiaQ"
+ name="Lifecycle Objectives Milestone" guid="_0_FFQOL9EdyM47cGD2jiaQ" presentationName="Lifecycle Objectives Milestone"
+ superActivities="_SKnA1uL9EdyM47cGD2jiaQ" linkToPredecessor="_VvtNQOL_EdyM47cGD2jiaQ"/>
+ <processElements xsi:type="org.eclipse.epf.uma:Milestone" xmi:id="_bTNukOL-EdyM47cGD2jiaQ"
+ name="Lifecycle Architecture Milestone" guid="_bTNukOL-EdyM47cGD2jiaQ" presentationName="Lifecycle Architecture Milestone"
+ superActivities="_SKnA1uL9EdyM47cGD2jiaQ" linkToPredecessor="_ioe2geL_EdyM47cGD2jiaQ"/>
+ <processElements xsi:type="org.eclipse.epf.uma:Milestone" xmi:id="_gIkT8OL-EdyM47cGD2jiaQ"
+ name="Initial Operational Capability" guid="_gIkT8OL-EdyM47cGD2jiaQ" presentationName="Initial Operational Capability"
+ superActivities="_SKnA1uL9EdyM47cGD2jiaQ" linkToPredecessor="_rNoR8eMAEdyM47cGD2jiaQ"/>
+ <processElements xsi:type="org.eclipse.epf.uma:Milestone" xmi:id="_l4LiIOL-EdyM47cGD2jiaQ"
+ name="Product Release Milestone" guid="_l4LiIOL-EdyM47cGD2jiaQ" presentationName="Product Release Milestone"
+ superActivities="_SKnA1uL9EdyM47cGD2jiaQ" linkToPredecessor="_yLBh4eMAEdyM47cGD2jiaQ"/>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_VvtNQOL_EdyM47cGD2jiaQ"
+ guid="_VvtNQOL_EdyM47cGD2jiaQ" pred="_SKnAzuL9EdyM47cGD2jiaQ"/>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_ioe2geL_EdyM47cGD2jiaQ"
+ guid="_ioe2geL_EdyM47cGD2jiaQ" pred="_SKnA0uL9EdyM47cGD2jiaQ"/>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_rNoR8eMAEdyM47cGD2jiaQ"
+ guid="_rNoR8eMAEdyM47cGD2jiaQ" pred="_SKnAyOL9EdyM47cGD2jiaQ"/>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_yLBh4eMAEdyM47cGD2jiaQ"
+ guid="_yLBh4eMAEdyM47cGD2jiaQ" pred="_SKnAxOL9EdyM47cGD2jiaQ"/>
+ <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_SKnA1uL9EdyM47cGD2jiaQ"
+ name="risk_value_lifecycle_phases" guid="_SKnA1uL9EdyM47cGD2jiaQ" presentationName="Risk-Value Lifecycle Phases"
+ breakdownElements="_SKnAzuL9EdyM47cGD2jiaQ _0_FFQOL9EdyM47cGD2jiaQ _SKnA0uL9EdyM47cGD2jiaQ _bTNukOL-EdyM47cGD2jiaQ _SKnAyOL9EdyM47cGD2jiaQ _gIkT8OL-EdyM47cGD2jiaQ _SKnAxOL9EdyM47cGD2jiaQ _l4LiIOL-EdyM47cGD2jiaQ">
+ <presentation xmi:id="-1IlTGK1mPdoxAMwuAjqLYg" href="uma://-1IlTGK1mPdoxAMwuAjqLYg#-1IlTGK1mPdoxAMwuAjqLYg"/>
+ <defaultContext href="uma://_1hLAOeJ7EdyM47cGD2jiaQ#_U9L9cOL6EdyM47cGD2jiaQ"/>
+ <validContext href="uma://_1hLAOeJ7EdyM47cGD2jiaQ#_U9L9cOL6EdyM47cGD2jiaQ"/>
+ </process>
+ </org.eclipse.epf.uma:ProcessComponent>
+</xmi:XMI>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/capabilitypatterns/risk_value_lifecycle_phasesXXX/content.xmi b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/capabilitypatterns/risk_value_lifecycle_phasesXXX/content.xmi
new file mode 100644
index 0000000..967d00e
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/capabilitypatterns/risk_value_lifecycle_phasesXXX/content.xmi
@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:ProcessDescription 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="-f0m93bWwWngjhcTY_sDPwg"
+ name="ris_value_lifecycle_phases,_FzchseL7EdyM47cGD2jiaQ" guid="-f0m93bWwWngjhcTY_sDPwg"/>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/capabilitypatterns/risk_value_lifecycle_phasesXXX/diagram.xmi b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/capabilitypatterns/risk_value_lifecycle_phasesXXX/diagram.xmi
new file mode 100644
index 0000000..879bac7
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/capabilitypatterns/risk_value_lifecycle_phasesXXX/diagram.xmi
@@ -0,0 +1,3 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xmi:XMI xmi:version="2.0"
+ xmlns:xmi="http://www.omg.org/XMI"/>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/capabilitypatterns/risk_value_lifecycle_phasesXXX/model.xmi b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/capabilitypatterns/risk_value_lifecycle_phasesXXX/model.xmi
new file mode 100644
index 0000000..3e7efc8
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/capabilitypatterns/risk_value_lifecycle_phasesXXX/model.xmi
@@ -0,0 +1,85 @@
+<?xml version="1.0" encoding="UTF-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.4/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.2.0" xmlns:epf="http://www.eclipse.org/epf"
+ epf:version="1.2.0">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_F0V5kOL7EdyM47cGD2jiaQ"
+ guid="_F0V5kOL7EdyM47cGD2jiaQ">
+ <resourceDescriptors xmi:id="_F0V5keL7EdyM47cGD2jiaQ" id="-f0m93bWwWngjhcTY_sDPwg"
+ uri="content.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:ProcessComponent xmi:id="_FzchsOL7EdyM47cGD2jiaQ" name="risk_value_lifecycle_phasesXXX"
+ guid="_FzchsOL7EdyM47cGD2jiaQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_VzwjoOL7EdyM47cGD2jiaQ"
+ name="Inception Phase" guid="_VzwjoOL7EdyM47cGD2jiaQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_E59fgOL8EdyM47cGD2jiaQ"
+ name="Inception Iteration [1..n]" guid="_E59fgOL8EdyM47cGD2jiaQ">
+ <processElements xsi:type="org.eclipse.epf.uma:Iteration" xmi:id="_E59fgeL8EdyM47cGD2jiaQ"
+ name="Inception Iteration [1..n]" guid="_E59fgeL8EdyM47cGD2jiaQ" presentationName="Inception Iteration [1..n]"
+ superActivities="_VzwjoeL7EdyM47cGD2jiaQ" isRepeatable="true"/>
+ </childPackages>
+ <processElements xsi:type="org.eclipse.epf.uma:Phase" xmi:id="_VzwjoeL7EdyM47cGD2jiaQ"
+ name="Inception Phase" guid="_VzwjoeL7EdyM47cGD2jiaQ" presentationName="Inception Phase"
+ superActivities="_FzchseL7EdyM47cGD2jiaQ" breakdownElements="_E59fgeL8EdyM47cGD2jiaQ _wAIw8OL7EdyM47cGD2jiaQ"/>
+ <processElements xsi:type="org.eclipse.epf.uma:Milestone" xmi:id="_wAIw8OL7EdyM47cGD2jiaQ"
+ name="Lifecycle Objectives Milestone" guid="_wAIw8OL7EdyM47cGD2jiaQ" presentationName="Lifecycle Objectives Milestone"
+ superActivities="_VzwjoeL7EdyM47cGD2jiaQ"/>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_es02EOL7EdyM47cGD2jiaQ"
+ name="Elaboration Phase" guid="_es02EOL7EdyM47cGD2jiaQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_08yRIOL7EdyM47cGD2jiaQ"
+ name="Lifecycle Architecture Milestone" guid="_08yRIOL7EdyM47cGD2jiaQ">
+ <processElements xsi:type="org.eclipse.epf.uma:Iteration" xmi:id="_08yRIeL7EdyM47cGD2jiaQ"
+ name="Lifecycle Architecture Milestone" guid="_08yRIeL7EdyM47cGD2jiaQ"
+ presentationName="Lifecycle Architecture Milestone" superActivities="_es02EeL7EdyM47cGD2jiaQ"/>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_JUyFAOL8EdyM47cGD2jiaQ"
+ name="Elaboration Iteration [1..n]" guid="_JUyFAOL8EdyM47cGD2jiaQ">
+ <processElements xsi:type="org.eclipse.epf.uma:Iteration" xmi:id="_JUyFAeL8EdyM47cGD2jiaQ"
+ name="Elaboration Iteration [1..n]" guid="_JUyFAeL8EdyM47cGD2jiaQ" presentationName="Elaboration Iteration [1..n]"
+ superActivities="_es02EeL7EdyM47cGD2jiaQ" isRepeatable="true"/>
+ </childPackages>
+ <processElements xsi:type="org.eclipse.epf.uma:Phase" xmi:id="_es02EeL7EdyM47cGD2jiaQ"
+ name="Elaboration Phase" guid="_es02EeL7EdyM47cGD2jiaQ" presentationName="Elaboration Phase"
+ superActivities="_FzchseL7EdyM47cGD2jiaQ" breakdownElements="_JUyFAeL8EdyM47cGD2jiaQ _08yRIeL7EdyM47cGD2jiaQ"/>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_j2mMQOL7EdyM47cGD2jiaQ"
+ name="Construction Phase" guid="_j2mMQOL7EdyM47cGD2jiaQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_MZyHEOL8EdyM47cGD2jiaQ"
+ name="Construction Iteration [1..n]" guid="_MZyHEOL8EdyM47cGD2jiaQ">
+ <processElements xsi:type="org.eclipse.epf.uma:Iteration" xmi:id="_MZyHEeL8EdyM47cGD2jiaQ"
+ name="Construction Iteration [1..n]" guid="_MZyHEeL8EdyM47cGD2jiaQ" presentationName="Construction Iteration [1..n]"
+ superActivities="_j2mMQeL7EdyM47cGD2jiaQ" isRepeatable="true"/>
+ </childPackages>
+ <processElements xsi:type="org.eclipse.epf.uma:Phase" xmi:id="_j2mMQeL7EdyM47cGD2jiaQ"
+ name="Construction Phase" guid="_j2mMQeL7EdyM47cGD2jiaQ" presentationName="Construction Phase"
+ superActivities="_FzchseL7EdyM47cGD2jiaQ" breakdownElements="_MZyHEeL8EdyM47cGD2jiaQ _525asOL7EdyM47cGD2jiaQ"/>
+ <processElements xsi:type="org.eclipse.epf.uma:Milestone" xmi:id="_525asOL7EdyM47cGD2jiaQ"
+ name="Initial Operational Capability Milestone" guid="_525asOL7EdyM47cGD2jiaQ"
+ presentationName="Initial Operational Capability Milestone" superActivities="_j2mMQeL7EdyM47cGD2jiaQ"/>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_l3CaAOL7EdyM47cGD2jiaQ"
+ name="Transition Phase" guid="_l3CaAOL7EdyM47cGD2jiaQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_VMJUkOL8EdyM47cGD2jiaQ"
+ name="Transition Iteration [1..n]" guid="_VMJUkOL8EdyM47cGD2jiaQ">
+ <processElements xsi:type="org.eclipse.epf.uma:Iteration" xmi:id="_VMJUkeL8EdyM47cGD2jiaQ"
+ name="Transition Iteration [1..n]" guid="_VMJUkeL8EdyM47cGD2jiaQ" presentationName="Transition Iteration [1..n]"
+ superActivities="_l3CaAeL7EdyM47cGD2jiaQ" isRepeatable="true"/>
+ </childPackages>
+ <processElements xsi:type="org.eclipse.epf.uma:Phase" xmi:id="_l3CaAeL7EdyM47cGD2jiaQ"
+ name="Transition Phase" guid="_l3CaAeL7EdyM47cGD2jiaQ" presentationName="Transition Phase"
+ superActivities="_FzchseL7EdyM47cGD2jiaQ" breakdownElements="_VMJUkeL8EdyM47cGD2jiaQ _9ifisOL7EdyM47cGD2jiaQ"/>
+ <processElements xsi:type="org.eclipse.epf.uma:Milestone" xmi:id="_9ifisOL7EdyM47cGD2jiaQ"
+ name="Product Release Milestone" guid="_9ifisOL7EdyM47cGD2jiaQ" presentationName="Product Release Milestone"
+ superActivities="_l3CaAeL7EdyM47cGD2jiaQ"/>
+ </childPackages>
+ <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_FzchseL7EdyM47cGD2jiaQ"
+ name="risk_value_lifecycle_phasesXXX" guid="_FzchseL7EdyM47cGD2jiaQ" presentationName="Risk-Value Lifecycle Phases"
+ breakdownElements="_VzwjoeL7EdyM47cGD2jiaQ _es02EeL7EdyM47cGD2jiaQ _j2mMQeL7EdyM47cGD2jiaQ _l3CaAeL7EdyM47cGD2jiaQ">
+ <presentation xmi:id="-f0m93bWwWngjhcTY_sDPwg" href="uma://-f0m93bWwWngjhcTY_sDPwg#-f0m93bWwWngjhcTY_sDPwg"/>
+ <defaultContext href="uma://_1hLAOeJ7EdyM47cGD2jiaQ#_U9L9cOL6EdyM47cGD2jiaQ"/>
+ <validContext href="uma://_1hLAOeJ7EdyM47cGD2jiaQ#_U9L9cOL6EdyM47cGD2jiaQ"/>
+ </process>
+ </org.eclipse.epf.uma:ProcessComponent>
+</xmi:XMI>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/customcategories/resources/bookc.gif b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/customcategories/resources/bookc.gif
new file mode 100644
index 0000000..7f2ab85
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/customcategories/resources/bookc.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/customcategories/resources/bookcL.gif b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/customcategories/resources/bookcL.gif
new file mode 100644
index 0000000..6c5b064
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/customcategories/resources/bookcL.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/customcategories/resources/pract_dgm32.gif b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/customcategories/resources/pract_dgm32.gif
new file mode 100644
index 0000000..f597332
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/customcategories/resources/pract_dgm32.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/customcategories/resources/pract_obj.gif b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/customcategories/resources/pract_obj.gif
new file mode 100644
index 0000000..fe8075a
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/customcategories/resources/pract_obj.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/customcategories/risk_value_lifecycle_practice.xmi b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/customcategories/risk_value_lifecycle_practice.xmi
new file mode 100644
index 0000000..327d17c
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/customcategories/risk_value_lifecycle_practice.xmi
@@ -0,0 +1,90 @@
+<?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: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="-nKGm7zbsVde3L5ev2OeazQ"
+ name="bi_level_project_planning_practice,_7Q49IL8EEdyWX5Yd-9QZ1A" guid="-nKGm7zbsVde3L5ev2OeazQ"
+ changeDate="2008-02-24T15:11:29.906-0500" version="7.2.0">
+ <mainDescription><p>
+ The&nbsp;Risk-Value Lifecycle&nbsp;practice&nbsp;supplements the Iterative Development&nbsp;and Two-Level Planning
+ Practices with the Unified Process Lifecycle.&nbsp; This lifecycle identifies four phases, each of which attempts to
+ balance value provided against risk mitigation appropriate to the phase.&nbsp;[***.......TO BE COMPLETED ***]
+</p>
+<h3>
+ The Essence of the Risk-Value Lifecycle
+</h3>
+<p>
+ The following capture the key principles of Risk-Value Lifecycle:
+</p>
+<ul>
+ <li>
+ <strong>Inception Phase</strong> focuses on identifying the objectives of the project and mitigating risks
+ associated with this goal.
+ </li>
+ <li>
+ <strong>Elaboration Phase</strong> focuses on solidifying the architecture for the system being built and mitigaing
+ risks associated with this goal.&nbsp; Production of executable examples of the most risky elements of the
+ architecture is included.
+ </li>
+ <li>
+ <strong>Construction Phase&nbsp;</strong>focuses on actually building the system, culminating in the first
+ beta-level versions of the entire system.&nbsp;&nbsp;
+ </li>
+ <li>
+ <strong>Transition Phase</strong> focuses on incorporating feedback from early customer evaluations of the system
+ and preparing the entire system for final product release, including end-user materials and distribution.
+ </li>
+</ul>
+<h3>
+ <br />
+ Why Adopt this Practice?
+</h3>
+<p>
+ [*** Include some content here that describes the business value of this practice -- what do you get when you adopt
+ it?&nbsp; This section is essentially the value proposition for the practice.&nbsp; You may want to describe some
+ common problems and how this practice solves those problems.&nbsp; &nbsp;***]&nbsp;&nbsp;&nbsp;
+</p>
+<h3>
+ How to Read this Practice
+</h3>
+<p>
+ The best way to read this practice is to first familiarize yourself with its overall structure -- what it is in it and
+ how it is organized.&nbsp;
+</p>
+<p>
+ [*** To be completed.... ***]
+</p>
+<p>
+ For step-by-step instructions on how to adopt this practice, see <a class="elementLink"
+ href="./../../practice.mgmt.risk_value_lifecycle.base/guidances/roadmaps/how_to_adopt_C61F3A1F.html"
+ guid="_ERIDQOMPEdyM47cGD2jiaQ">How to Adopt This Practice</a>.
+</p>
+<h3>
+ Additional Resources
+</h3>
+<p>
+ For more information on the whole team approach, see the following:
+</p>
+<ul>
+ <li>
+ [*** Add more, as needed ***]<br />
+ </li>
+</ul><br />
+<br />
+<br />
+<br />
+<h4>
+ Dependencies on other practices
+</h4>
+<p>
+ This practice provides additional guidance to the following practices:
+</p>
+<ul>
+ <li>
+ Iterative Development
+ </li>
+ <li>
+ Bi-Level Project Planning<br />
+ </li>
+</ul></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/construction_phase.xmi b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/construction_phase.xmi
new file mode 100644
index 0000000..9844c12
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/construction_phase.xmi
@@ -0,0 +1,49 @@
+<?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: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="-bbpT_BdDRrv6waNI365Qhg"
+ name=",_48EKsBOMEduCNqgZdt_OaA" guid="-bbpT_BdDRrv6waNI365Qhg" changeDate="2008-02-24T11:12:12.421-0500"
+ version="1.0.0">
+ <mainDescription><p>
+ The purpose in this phase is to complete the development of the system based upon the baselined architecture.
+</p>
+<p>
+ There are objectives for the Construction phase that help us to&nbsp;have cost-efficient development of a complete
+ product - an operational version of your system - that can be deployed&nbsp;in the user community&nbsp;<a
+ class="elementlinkwithusertext"
+ href="./../../../core.mgmt.common.base/guidances/supportingmaterials/mgmt_references_D80619F3.html#KRO03"
+ guid="_JlTPUM6aEdyuBO4ZIzcyig">[KRO03]</a>:
+</p>
+<ol>
+ <li>
+ Iteratively develop a complete product that is ready to transition to its user community. Describe remaining
+ requirements, fill in design details, complete the implementation and test the software. Release the first
+ operational version (beta) of the system and determine if users are ready for the application to be deployed.
+ </li>
+ <li>
+ Minimize development costs and achieve some degree of parallelism. Optimize resources and leverage development
+ parallelism between developers or teams of developers, by for example, assigning components that can be developed
+ independently of one another.
+ </li>
+</ol>
+<h4>
+ Key considerations
+</h4>
+<p>
+ Typically, the Construction phase has more iterations (two to four) than the other phases, depending on the types of
+ projects:
+</p>
+<ul>
+ <li>
+ Simple project: One iteration to build the product (to a beta release)
+ </li>
+ <li>
+ More substantial project: One iteration to expose a partial system and one to mature it to beta testing
+ </li>
+ <li>
+ Large project: Three or more iterations, given the size of the project (number of requirements to implement for a
+ beta release)
+ </li>
+</ul></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/elaboration_phase.xmi b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/elaboration_phase.xmi
new file mode 100644
index 0000000..b74c211
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/elaboration_phase.xmi
@@ -0,0 +1,65 @@
+<?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: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="-F-eWIBzxEXE1jygbN3nrrQ"
+ name=",_2plxwBOMEduCNqgZdt_OaA" guid="-F-eWIBzxEXE1jygbN3nrrQ" changeDate="2008-02-24T11:14:58.015-0500"
+ version="1.0.0">
+ <mainDescription><p>
+ The purpose of this phase is to establish the baseline of the architecture of the system and provide a stable basis for
+ the bulk of the&nbsp;development effort in the next phase.
+</p>
+<p>
+ There are objectives for the Elaboration phase that help you address risks associated with requirements, architecture,
+ costs, and schedule <a class="elementlinkwithusertext"
+ href="./../../../core.mgmt.common.base/guidances/supportingmaterials/mgmt_references_D80619F3.html#KRO03"
+ guid="_JlTPUM6aEdyuBO4ZIzcyig">[KRO03]</a>:
+</p>
+<ul>
+ <li>
+ <p>
+ <strong>Get a more detailed understanding of the requirements.</strong> Having a good understanding of the
+ majority of requirements allows you to create a more detailed plan and to get buy-in from stakeholders. Be sure
+ to gain an in-depth understanding of the most critical requirements to be validated by&nbsp;the architecture.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Design, implement, validate, and establish the baseline for the architecture.</strong> Design,
+ implement, and test a skeleton structure of the system. Although the functionality is not complete yet, most of
+ the interfaces between the building blocks are implemented and tested. This is referred to <strong>an
+ executable architecture</strong>.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Mitigate essential risks, and produce accurate schedule and cost estimates.</strong> Many technical
+ risks are addressed as a result of detailing the requirements and of designing, implementing, and testing the
+ architecture. Refine and detail the high-level project plan.
+ </p>
+ </li>
+</ul>
+<h4>
+ Key considerations
+</h4>
+<p>
+ The number of iterations in the Elaboration phase is dependent on, but not limited to, factors such as green-field
+ development versus maintenance cycle, unprecedented system versus well-known technology and architecture, and so on.
+</p>
+<p>
+ Typically, on the first iteration, you should design, implement, and test a small number of critical scenarios to
+ identify what type of architecture and architectural mechanisms you need, so you can mitigate the most crucial risks.
+ You also detail high-risk requirements that have to be addressed early in the project. You test enough to validate that
+ the architectural risks are mitigated.
+</p>
+<p>
+ On the following iterations, you fix whatever was not right from the previous iteration. You design, implement, and
+ test the remaining architecturally significant scenarios, ensuring that you check all major areas of the system
+ (architectural coverage), so potential hidden risks arise as early as possible. <a class="elementlinkwithusertext"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/tech_references_6CCF393.html"
+ guid="_9ToeIB83Edqsvps02rpOOg">[KRO03]</a>
+</p>
+<p>
+ <br />
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/inception_phase.xmi b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/inception_phase.xmi
new file mode 100644
index 0000000..e43d553
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/inception_phase.xmi
@@ -0,0 +1,67 @@
+<?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: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="-GRJW_KNOJoEQF3r6lmBrEw"
+ name=",_0hmKgBOMEduCNqgZdt_OaA" guid="-GRJW_KNOJoEQF3r6lmBrEw" changeDate="2008-02-24T11:15:36.718-0500"
+ version="1.0.0">
+ <mainDescription><p>
+ The purpose&nbsp;in this phase is to achieve concurrence among all stakeholders on the lifecycle objectives for the
+ project.
+</p>
+<p>
+ There are four objectives of the Inception phase that clarify the scope, project objectives, and feasibility of the
+ intended solution <a class="elementlinkwithusertext"
+ href="./../../../core.mgmt.common.base/guidances/supportingmaterials/mgmt_references_D80619F3.html#KRO03"
+ guid="_JlTPUM6aEdyuBO4ZIzcyig">[KRO03]</a>:
+</p>
+<ol>
+ <li>
+ <p>
+ <strong>Understand what to build.</strong> Determine the <a class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/workproducts/vision_2E71B03C.html"
+ guid="_0WVxcMlgEdmt3adZL5Dmdw">Vision</a>, the scope of the system, and its boundaries. Identify who is
+ interested in this system and why (see <a class="elementLinkWithUserText"
+ href="./../../../core.default.role_def.base/roles/stakeholder_9FFD4106.html"
+ guid="_dTa6gMAYEdqX-s4mWhkyqQ">Stakeholders</a>).
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Identify key system functionality.</strong> Decide which requirements are most critical.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Determine at least one possible solution.</strong> Identify at least one candidate architecture and its
+ feasibility.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Understand</strong> the cost, schedule, and risks associated with the project.
+ </p>
+ </li>
+</ol><br />
+<h4>
+ Key considerations
+</h4>
+<p>
+ Projects may have one or more iterations in the Inception phase. Among reasons for multiple iterations in Inception,
+ you find:
+</p>
+<ul>
+ <li>
+ Project is large, and it is&nbsp;hard to define its scope.
+ </li>
+ <li>
+ Unprecedented system.
+ </li>
+ <li>
+ Too many stakeholders with competing needs and complex relationships.
+ </li>
+ <li>
+ Major technical risks demand the creation of a prototype or proof of concept.
+ </li>
+</ul><br /></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/phase.xmi b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/phase.xmi
new file mode 100644
index 0000000..9ccdc22
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/phase.xmi
@@ -0,0 +1,41 @@
+<?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: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="-bhzuf6RMHP3d-AHkoKDg7g"
+ name="phase,__7xOEC7aEdqHMdmRzC0-2g" guid="-bhzuf6RMHP3d-AHkoKDg7g" changeDate="2008-02-22T01:49:33.109-0500"
+ version="1.0.0">
+ <mainDescription><h3>
+ What is a Phase?
+</h3>
+<p>
+ While the entire purpose of a project is to produce a product, the specific goals of the team will vary substantially
+ throughout the project. In the beginning, there usually is considerable latitude in the requirements for the product.
+ It may not be clear whether the project is feasible or even if it is likely to be profitable. At that time, it is
+ critical to bring an answer to these questions, and of little to no value to start developing the product in
+ earnest.&nbsp;Towards the end of the project, the product itself is usually complete, and issues of quality, delivery,
+ and completeness then take center stage. At different points in time, tasks are undertaken in new ways and work
+ products will have new content.
+</p>
+<p>
+ To coordinate the team’s efforts in a manner that takes these fundamental observations into account, the project
+ lifecycle should be divided into a sequence of phases. Each phase has a defined set of goals, its own iteration style
+ and customized&nbsp; <a class="elementLinkWithUserText"
+ href="./../../../core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html"
+ guid="_x459ktnmEdmO6L4XMImrsA">tasks</a>&nbsp;and&nbsp;<a class="elementLinkWithUserText"
+ href="./../../../core.default.uma_concept.base/guidances/termdefinitions/work_product_826E4C22.html"
+ guid="_H4JXwB_SEdq6CKKKq4D7YA">work products</a> to address the unique needs of the project at that point in time.
+</p>
+<p>
+ We recommend&nbsp;dividing the project lifecycle into&nbsp;four phases: Inception, Elaboration, Construction and
+ Transition.
+</p>
+<h3>
+ Iteration and Phases
+</h3>
+<p>
+ Each phase is divided into iterations. An iteration is a complete development loop resulting in a build (internal or
+ external) of an executable system, usually a subset of the final product under development, which grows incrementally
+ from iteration to iteration to become the final product.<br />
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/phase_milestones.xmi b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/phase_milestones.xmi
new file mode 100644
index 0000000..69a2b1a
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/phase_milestones.xmi
@@ -0,0 +1,66 @@
+<?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: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="-DG8mYMnTGosWIxjPQFUoTA"
+ name="milestones,_HNxbwMBJEdqSgKaj2SZBmg" guid="-DG8mYMnTGosWIxjPQFUoTA" changeDate="2008-02-11T16:56:57.359-0500"
+ version="7.2.0">
+ <mainDescription><p>
+ From a&nbsp;development perspective, each iteration provides an increment of functionality to the product. Thus, the
+ end of each iteration corresponds to a checkpoint where the project team demonstrates to stakeholders that the
+ objectives for that iteration have been met.
+</p>
+<p>
+ From a management perspective, the software lifecycle&nbsp;is decomposed over time into four sequential phases, each
+ concluded by a major milestone [<a class="elementLinkWithUserText"
+ href="./../../../core.mgmt.common.base/guidances/supportingmaterials/mgmt_references_D80619F3.html#BOE95"
+ guid="_JlTPUM6aEdyuBO4ZIzcyig">BOE95</a>]. There are four major milestones that provide evaluation criteria at the end
+ of each phase.
+</p>
+<p class="banner" align="center">
+ <img height="156" alt="Click on text for more information about phases and milestones" src="./resources/co_phas1.gif"
+ width="406" border="0" />
+</p>
+<p class="picturetext" align="center">
+ The phases and milestones of a project
+</p>
+<p>
+ Each phase is&nbsp;a span of time between two major milestones and has specific focus and objectives. At each phase-end
+ an assessment is performed to determine whether the objectives of the phase have been met. A satisfactory assessment
+ allows the project to move to the next phase. When a milestone is not met, more iterations in the current phase may be
+ performed before the milestone can be considered complete. Achieving a milestone represents an objective criteria with
+ which to measure progress.
+</p>
+<p>
+ At the end of the <a class="elementLink"
+ href="./../../../practice.mgmt.risk_value_lifecycle.base/guidances/concepts/inception_phase_C4456871.html"
+ guid="_0hmKgBOMEduCNqgZdt_OaA">Inception Phase</a> is the first major project milestone or <strong>Lifecycle Objectives
+ Milestone</strong>. At this point, you examine the cost versus benefits of the project, and decide either to proceed
+ with the project or to cancel it.
+</p>
+<p>
+ At the end of the <a class="elementLink"
+ href="./../../../practice.mgmt.risk_value_lifecycle.base/guidances/concepts/elaboration_phase_BE880435.html"
+ guid="_2plxwBOMEduCNqgZdt_OaA">Elaboration Phase</a>&nbsp;is the second important project milestone, the
+ <strong>Lifecycle Architecture Milestone</strong>. At this point, a baseline of requirements is agreed to, you examine
+ the detailed system objectives and scope, the choice of architecture, and the resolution of the major risks. The
+ milestone is achieved when the architecture has been validated.
+</p>
+<p>
+ At the end of the <a class="elementLink"
+ href="./../../../practice.mgmt.risk_value_lifecycle.base/guidances/concepts/construction_phase_873B6559.html"
+ guid="_48EKsBOMEduCNqgZdt_OaA">Construction Phase</a><strong>&nbsp;</strong>is the third important project milestone,
+ the <strong>Initial Operational Capability Milestone</strong>. At this point, the product is ready to be handed over to
+ the transition team. All functionality has been developed and all alpha testing (if any) has been completed. In
+ addition to the software, a user manual has been developed, and there is a description of the current release. The
+ product is ready for beta testing.
+</p>
+<p>
+ At the end of the <a class="elementLink"
+ href="./../../../practice.mgmt.risk_value_lifecycle.base/guidances/concepts/transition_phase_DD5986E5.html"
+ guid="__ca5UBOMEduCNqgZdt_OaA">Transition Phase</a><strong>&nbsp;</strong>is the fourth important project milestone,
+ the <strong>Product Release Milestone</strong>. At this point, you decide if the objectives were met, and if you should
+ start another development cycle. The Product Release Milestone is the result of the customer reviewing and accepting
+ the project deliverables.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/project_lifecycle.xmi b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/project_lifecycle.xmi
new file mode 100644
index 0000000..ba6287e
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/project_lifecycle.xmi
@@ -0,0 +1,72 @@
+<?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: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="-ebKPqn9bWfbh1K2spgOwWQ"
+ name="project_lifecycle,_nSfVwCNYEdyCq8v2ZO4QcA" guid="-ebKPqn9bWfbh1K2spgOwWQ"
+ changeDate="2008-02-24T11:24:45.109-0500">
+ <mainDescription><p>
+ The project lifecycle provides <em>stakeholders</em> with oversight, transparency, and steering mechanisms to control
+ project funding, scope, risk exposure, value provided, and other aspects of the process.
+</p>
+<p>
+ Each iteration delivers a product increment, which provides an opportunity for stakeholders to understand what value
+ has been delivered and how well the project is tracking. It also gives the development team the opportunity to make
+ changes to the project to optimize the outcome.
+</p>
+<p>
+ OpenUP organizes iterations into a set of phases. Each phase ends with a milestone aimed at providing oversight by
+ raising and answering a set of questions that are typically critical to stakeholders:
+</p>
+<ul>
+ <li>
+ <a class="elementLinkWithUserText"
+ href="./../../../practice.mgmt.risk_value_lifecycle.base/guidances/concepts/inception_phase_C4456871.html"
+ guid="_0hmKgBOMEduCNqgZdt_OaA">Inception</a>. Do we agree on project scope and objectives, and whether or not the
+ project should proceed?
+ </li>
+ <li>
+ <a class="elementLinkWithUserText"
+ href="./../../../practice.mgmt.risk_value_lifecycle.base/guidances/concepts/elaboration_phase_BE880435.html"
+ guid="_2plxwBOMEduCNqgZdt_OaA">Elaboration</a>. Do we agree on the executable architecture to be used for
+ developing the application and do we find that the value delivered so far and the remaining risk is acceptable?
+ </li>
+ <li>
+ <a class="elementLinkWithUserText"
+ href="./../../../practice.mgmt.risk_value_lifecycle.base/guidances/concepts/construction_phase_873B6559.html"
+ guid="_48EKsBOMEduCNqgZdt_OaA">Construction</a>. Do we find that we have an application that is sufficiently close
+ to being released that we should switch the primary focus of the team to tuning, polishing and ensuring successful
+ deployment?
+ </li>
+ <li>
+ <a class="elementLinkWithUserText"
+ href="./../../../practice.mgmt.risk_value_lifecycle.base/guidances/concepts/transition_phase_DD5986E5.html"
+ guid="__ca5UBOMEduCNqgZdt_OaA">Transition</a>. Is the application ready to release?
+ </li>
+</ul>
+<p>
+ If the answer is Yes to the above questions at the phase review, the project continues. If the answer is No, the phase
+ is delayed (usually by adding an extra iteration) until a satisfactory answer is received, or the stakeholders may
+ determine that the project should be cancelled.
+</p>
+<p>
+ One of the objectives of the project lifecycle is to focus on two key stakeholder drivers: risk reduction and value
+ creation. The OpenUP phases focus the team on risk reduction related to the questions to be answered at the end of the
+ phase, while tracking value creation, see Figure below.
+</p>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <img height="268" alt="Risk goes down and vlaue goes up as project progresses." src="./resources/project_lifecycle.jpg"
+ width="500" />&nbsp;
+</blockquote>
+<p dir="ltr">
+ <em>Risk reduction (red curve) and value creation (green curve) during the project lifecycle.</em>
+</p>
+<p dir="ltr">
+ Risk is a manifestation of the likelihood of unexpected things happening to the project, and risk stands in the way of
+ value creation. Risk is directly proportional to uncertainty in estimates, and stakeholders typically want to know
+ sooner rather than later what value the project can deliver in the stipulated time. In many cases, you reduce risk when
+ you create value by implementing and testing the most critical capabilities. However, there are situations where risk
+ reduction and immediate value creation are at odds with each other, requiring careful balancing of these competing
+ priorities to maximize stakeholder value.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/resources/co_phas1.gif b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/resources/co_phas1.gif
new file mode 100644
index 0000000..919e282
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/resources/co_phas1.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/resources/concept_dgm32.gif b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/resources/concept_dgm32.gif
new file mode 100644
index 0000000..fa195bd
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/resources/concept_dgm32.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/resources/concept_obj.gif b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/resources/concept_obj.gif
new file mode 100644
index 0000000..03af38b
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/resources/concept_obj.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/resources/project_lifecycle.jpg b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/resources/project_lifecycle.jpg
new file mode 100644
index 0000000..7d90779
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/resources/project_lifecycle.jpg
Binary files differ
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/transition_phase.xmi b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/transition_phase.xmi
new file mode 100644
index 0000000..ff22f1a
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/concepts/transition_phase.xmi
@@ -0,0 +1,55 @@
+<?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: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="-FrUmsKsGW4bnNmb9uaNOkg"
+ name=",__ca5UBOMEduCNqgZdt_OaA" guid="-FrUmsKsGW4bnNmb9uaNOkg" changeDate="2008-02-24T11:16:27.171-0500"
+ version="1.0.0">
+ <mainDescription><p>
+ The purpose in this phase is to ensure that the software is ready for delivery to users.
+</p>
+<p>
+ There are objectives for the Transition phase that help you to&nbsp;fine-tune functionality, performance, and overall
+ quality of the beta product from the end of&nbsp;the previous phase <a class="elementlinkwithusertext"
+ href="./../../../core.mgmt.common.base/guidances/supportingmaterials/mgmt_references_D80619F3.html#KRO03"
+ guid="_JlTPUM6aEdyuBO4ZIzcyig">[KRO03]</a>:
+</p>
+<ol>
+ <li>
+ <p>
+ <strong>Beta test to validate that user expectations are met.</strong> This typically requires some fine-tuning
+ activities, such as bug-fixing and making enhancements for performance and usability.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Achieve stakeholder concurrence that deployment is complete.</strong> This may involve various levels
+ of tests for product acceptance, including formal and informal tests and beta tests.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Improve future project performance through lessons learned.</strong> Document lessons learned and
+ improve the process and tool environment for the project.
+ </p>
+ </li>
+</ol>
+<h4>
+ <br />
+ Key considerations<br />
+</h4>
+<p>
+ The Transition phase can include running old and new systems in parallel, migrating data, training users, and adjusting
+ business processes.
+</p>
+<p>
+ The number of iterations in the Transition phase varies from one iteration for a simple system requiring primarily
+ minor bug fixing, to many iterations for a complex system, involving addition of features and performing activities to
+ make the business transition from using the old system to using the new system.
+</p>
+<p>
+ When the Transition phase objectives are met, the project is in position to be closed.&nbsp;For some products, the end
+ of the current project lifecycle may coincide with the beginning of the next lifecycle, leading to the next generation
+ of the same product.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/examples/project_burndown_report_example.xmi b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/examples/project_burndown_report_example.xmi
new file mode 100644
index 0000000..3e95579
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/examples/project_burndown_report_example.xmi
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:GuidanceDescription 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="-ThmcJuMmkwabvA7gn7hC6g"
+ name="new_example,_Yiq2EDcGEdyTZ9G7ByfQTw" guid="-ThmcJuMmkwabvA7gn7hC6g">
+ <attachments>../reports/resources/ex_project_burndown.xls</attachments>
+</org.eclipse.epf.uma:GuidanceDescription>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/examples/project_plan.xmi b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/examples/project_plan.xmi
new file mode 100644
index 0000000..ec8c5d3
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/examples/project_plan.xmi
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:GuidanceDescription 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="-IdlCQXdDNYGrGJU4TBwvCA"
+ name="new_example,_Nzv5kDoAEdusGsHODb-STA" guid="-IdlCQXdDNYGrGJU4TBwvCA" changeDate="2006-09-27T17:07:10.301-0400"
+ version="1.0.0">
+ <mainDescription><p>
+ This example is the actual project plan used for the development of OpenUP/Basic.
+</p>
+<p>
+ <a href="./resources/project_plan.doc" target="_blank" >project_plan.doc</a>
+</p></mainDescription>
+</org.eclipse.epf.uma:GuidanceDescription>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/examples/resources/project_plan.doc b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/examples/resources/project_plan.doc
new file mode 100644
index 0000000..5b4a2f6
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/examples/resources/project_plan.doc
Binary files differ
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/guidelines/deploying_the_solution.xmi b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/guidelines/deploying_the_solution.xmi
new file mode 100644
index 0000000..2b65405
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/guidelines/deploying_the_solution.xmi
@@ -0,0 +1,85 @@
+<?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="-aOaMjqW4RZWOiHT1_U1NNw"
+ name="deploying_the_solution,_yYlQoC3xEdycYKq0PulnEQ" guid="-aOaMjqW4RZWOiHT1_U1NNw"
+ changeDate="2007-07-23T13:14:50.468-0700">
+ <mainDescription><h3>
+ Planning Transition Iterations
+</h3>
+<p>
+ Software may be deployed into a production environment at the end of any Construction or Transition iteration.
+ Deployment to production before the end of the project may be done to drive down risk by validating the application,
+ deployment scripts, the deployment environment, and to get valuable feedback from operations and systems teams, as well
+ as end user. These early deployments are often done on a limited scale in terms of target audience or deployment of
+ only partial applications. For the deployment to work, one or several iterations are focused on work necessary to
+ successfully release the system. In Transition, one or several iterations may be dedicated to preparing for a smooth
+ deployment. The number of iterations depends on the complexity of the system and various other factors, as listed
+ below. When planning for deployment, the work item list should be updated with relevant tasks related to:
+</p>
+<ul>
+ <li>
+ Resolving defects
+ </li>
+ <li>
+ Testing installation or deployment scripts to avoid surprises in actual deployment&nbsp;
+ </li>
+ <li>
+ Updating any&nbsp;operations&nbsp;&amp; support test environments used to simulate production problems
+ </li>
+ <li>
+ Performing release-specific testing efforts such as pilot or beta testing to a subset of your end-user community
+ where the system is deployed
+ </li>
+ <li>
+ Conducting acceptance reviews with stakeholders, including a&nbsp;final release acceptance testing effort where
+ people outside of the team are involved and decide whether it truly meets their needs
+ </li>
+ <li>
+ Finalizing relevant documentation, such as operations and system manuals, end-user documentation and release notes
+ </li>
+ <li>
+ Creating&nbsp;physical collateral, such as installation media
+ </li>
+ <li>
+ Replacing and/or installing physical assets, including workstations, servers, and network components
+ </li>
+ <li>
+ Replacing existing software with new versions
+ </li>
+ <li>
+ Updating existing databases, including any relevant data migration and/or database schema changes
+ </li>
+ <li>
+ Production data population
+ </li>
+ <li>
+ Training end users and operations&nbsp;and support staff
+ </li>
+ <li>
+ Fixing any discrepancies discovered during the transition phase
+ </li>
+ <li>
+ Setting up management and operational systems and processes
+ </li>
+ <li>
+ Training the team that is taking over maintenance and evolution of the system
+ </li>
+ <li>
+ Deploying the software to the production environment
+ </li>
+</ul>
+<p>
+ See [<a class="elementLinkWithUserText" href="./../../../openup/guidances/supportingmaterials/references.html#AMB07"
+ guid="_9ToeIB83Edqsvps02rpOOg">AMB07</a>]&nbsp; for more information.
+</p>
+<h3>
+ <span style="BACKGROUND-COLOR: rgb(255,255,255)">Reviewing Transition Iterations</span><br />
+</h3>
+<p>
+ Transition iteration reviews have a different focus from other iterations in the project lifecycle. The goal is not to
+ brainstorm around what&nbsp;features to develop next. Instead, reviews will assess the release management resources and
+ procedures, the quality of the software,&nbsp;and how prepared users and operations teams are to face a move of the
+ software into the production environment.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/reports/project_burndown.xmi b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/reports/project_burndown.xmi
new file mode 100644
index 0000000..348af81
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/reports/project_burndown.xmi
@@ -0,0 +1,24 @@
+<?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: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="-hrDndmFd0zexB0HNYX3gww"
+ name="project_burndown,_ePrt8Dj3EduxovfWMDsntw" guid="-hrDndmFd0zexB0HNYX3gww"
+ changeDate="2006-09-25T20:07:38.314-0400" version="1.0.0">
+ <mainDescription><p>
+ The project burndown report is a primary tool for understanding the status of a project. It shows the trend for how
+ much work is left to do within that project. This is done by adding the estimated effort left for each of the Work
+ Items to be addressed within the project and showing how the estimated effort is changing from iteration to iteration.
+ The project burndown report should be updated at the end of each iteration.
+</p>
+<p>
+ The project burndown rate is usually communicated in graphical form.&nbsp;The project burndown chart consists of two
+ perspectives, with the horizontal axis showing the iterations and the vertical axis indicating the remaining points
+ from the Work Items List. Additionally, the average burndown rate from previous iterations is calculated, and a trend
+ for the remainder of the project forecasted from that historical data.&nbsp;
+</p>
+<p>
+ Project burndown management is a enabling technique that allows direct linkage of iteration goals to Work Items. The
+ Project Manager will use the project burndown information for communicating progress and trends to senior management.
+</p>See <a class="elementLink" href="./../../../openup/guidances/examples/project_burndown_report_example_847643C1.html" guid="_Yiq2EDcGEdyTZ9G7ByfQTw">Project Burndown Report</a>&nbsp;for an example of project burndown report.<br /></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/reports/resources/ex_project_burndown.xls b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/reports/resources/ex_project_burndown.xls
new file mode 100644
index 0000000..e63fef8
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/reports/resources/ex_project_burndown.xls
Binary files differ
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/roadmaps/how_to_adopt.xmi b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/roadmaps/how_to_adopt.xmi
new file mode 100644
index 0000000..5e56382
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/roadmaps/how_to_adopt.xmi
@@ -0,0 +1,21 @@
+<?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: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="-R1d0qAJDnmI5Fm9ChHCYQw"
+ name="how_to_adopt,_ERIDQOMPEdyM47cGD2jiaQ" guid="-R1d0qAJDnmI5Fm9ChHCYQw" changeDate="2008-02-17T08:09:46.937-0500"
+ version="7.2.0">
+ <mainDescription><h3>
+ Getting Started&nbsp;
+</h3>
+<p>
+ TODO:&nbsp; Describe how to 'read' this practice.......provide description with links to appropriate content to help
+ someone get started with this practice
+</p>
+<h3>
+ Common Pitfalls
+</h3>
+<p>
+ TBD
+</p><br /></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/supportingmaterials/delivery_process_graph.xmi b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/supportingmaterials/delivery_process_graph.xmi
new file mode 100644
index 0000000..9281a1f
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/supportingmaterials/delivery_process_graph.xmi
@@ -0,0 +1,35 @@
+<?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: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="-cy0DcnEk7uJJ1OOH3_E6rg"
+ name="new_supporting_material,_Pt_fYBjoEduxUfEVCtmW4Q" guid="-cy0DcnEk7uJJ1OOH3_E6rg"
+ changeDate="2006-07-21T11:39:59.312-0700">
+ <mainDescription><img height="192" alt="OpenUP/Basic Lifecycle" src="./resources/openup-basic_lifecycle.jpg" width="667" usemap="#map"
+border="0" /> <map id="Map" name="Map">
+ <area shape="rect" coords="116,7,175,25"
+ href="./../../../core.tech.common.base/guidances/concepts/inception_phase_C4456871.html"
+ guid="_0hmKgBOMEduCNqgZdt_OaA" />
+ <area shape="rect" coords="255,11,327,27"
+ href="./../../../core.tech.common.base/guidances/concepts/elaboration_phase_BE880435.html"
+ guid="_2plxwBOMEduCNqgZdt_OaA" />
+ <area shape="rect" coords="395,11,476,27"
+ href="./../../../core.tech.common.base/guidances/concepts/construction_phase_873B6559.html"
+ guid="_48EKsBOMEduCNqgZdt_OaA" />
+ <area shape="rect" coords="554,10,619,27"
+ href="./../../../core.tech.common.base/guidances/concepts/transition_phase_DD5986E5.html"
+ guid="__ca5UBOMEduCNqgZdt_OaA" />
+ <area shape="rect" coords="39,98,100,162"
+ href="./../../../opn.legacy.openup_basic.KEEP/deliveryprocesses/inception_phase_iteration_648AE2DA.html"
+ guid="_xupMvxOKEduCNqgZdt_OaA" />
+ <area shape="rect" coords="188,99,250,168"
+ href="./../../../opn.legacy.openup_basic.KEEP/deliveryprocesses/elaboration_phase_iteration_427C4DE0.html"
+ guid="_0Spa4BOKEduCNqgZdt_OaA" />
+ <area shape="rect" coords="332,100,397,165"
+ href="./../../../opn.legacy.openup_basic.KEEP/deliveryprocesses/construction_phase_iteration_A276D580.html"
+ guid="_3CqrAROKEduCNqgZdt_OaA" />
+ <area shape="rect" coords="480,98,541,167"
+ href="./../../../opn.legacy.openup_basic.KEEP/deliveryprocesses/transition_phase_iteration_31BFECF6.html"
+ guid="_467NIhOKEduCNqgZdt_OaA" />
+</map></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/supportingmaterials/release_info_risk_value_lifecycle.xmi b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/supportingmaterials/release_info_risk_value_lifecycle.xmi
new file mode 100644
index 0000000..b818257
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/supportingmaterials/release_info_risk_value_lifecycle.xmi
@@ -0,0 +1,27 @@
+<?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="-sqx8arvFbAtMVoqGeHA_kA"
+ name="release_info_risk_value_lifecycle,_Oc6L4MOAEdy3nv0ZK8D4GQ" guid="-sqx8arvFbAtMVoqGeHA_kA"
+ changeDate="2008-01-31T15:16:07.828-0500" version="7.2.0">
+ <mainDescription><h3>
+ Risk-Value&nbsp;Lifecycle&nbsp;Practice
+</h3>
+<p>
+ Version 1.0
+</p>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p>
+ This practice contributes the phases for the Unified Process (iteration, construction, elaboration, transition) to
+ the Iterative Development Practice and the Two-Level Project Planning Practice.&nbsp;
+ </p>
+ <p>
+ [*** NOT YET RELEASED ***]
+ </p>
+ <p>
+ This is the initial release of this practice.
+ </p><br />
+ <br />
+</blockquote><br /></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/supportingmaterials/resources/openup-basic_lifecycle.jpg b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/supportingmaterials/resources/openup-basic_lifecycle.jpg
new file mode 100644
index 0000000..4719cad
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/supportingmaterials/resources/openup-basic_lifecycle.jpg
Binary files differ
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/templates/project_plan.xmi b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/templates/project_plan.xmi
new file mode 100644
index 0000000..5f04189
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/templates/project_plan.xmi
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:GuidanceDescription 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="_XjOXcMM2EdmSIPI87WLu3g"
+ name="project_plan,_0c7hoMlgEdmt3adZL5Dmdw" guid="_XjOXcMM2EdmSIPI87WLu3g" changeDate="2006-05-09T01:03:04.654+0100">
+ <attachments>resources/project_plan_tpl.dot</attachments>
+</org.eclipse.epf.uma:GuidanceDescription>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/templates/resources/project_plan_tpl.dot b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/templates/resources/project_plan_tpl.dot
new file mode 100644
index 0000000..ad2d41a
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/templates/resources/project_plan_tpl.dot
Binary files differ
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/termdefinitions/construction.xmi b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/termdefinitions/construction.xmi
new file mode 100644
index 0000000..8439da9
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/termdefinitions/construction.xmi
@@ -0,0 +1,10 @@
+<?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: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="-5wJmUR0WqX7lCIxsyqFsdA"
+ name=",_0sD60EvDEdunZcj9T5hrMQ" guid="-5wJmUR0WqX7lCIxsyqFsdA" changeDate="2008-02-22T01:56:13.671-0500"
+ version="7.2.0">
+ <mainDescription>The third phase of the project lifecycle, in which the software is brought from an executable architectural baseline to the
+point at which it is ready to be transitioned to the user community.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/termdefinitions/elaboration.xmi b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/termdefinitions/elaboration.xmi
new file mode 100644
index 0000000..9d1cb05
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/termdefinitions/elaboration.xmi
@@ -0,0 +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.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="-0g2jTHQla8lbP6xGB3iGlg"
+ name=",_8DkT4EvDEdunZcj9T5hrMQ" guid="-0g2jTHQla8lbP6xGB3iGlg" changeDate="2008-02-22T01:56:42.859-0500"
+ version="7.2.0">
+ <mainDescription>Second of four phases in the in the project lifecycle, when architecturally-significant risks are addressed</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/termdefinitions/inception.xmi b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/termdefinitions/inception.xmi
new file mode 100644
index 0000000..40fa686
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/termdefinitions/inception.xmi
@@ -0,0 +1,10 @@
+<?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: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="-dhgOQQ4GsV0-dNJmTmF9GA"
+ name=",_525A8EvDEdunZcj9T5hrMQ" guid="-dhgOQQ4GsV0-dNJmTmF9GA" changeDate="2008-02-22T01:56:53.984-0500"
+ version="7.2.0">
+ <mainDescription>First of the four phases in the project lifecycle, it is about understanding the project scope and objectives and getting
+enough information to confirm that the project should proceed&nbsp; or not.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/termdefinitions/ioc_milestone.xmi b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/termdefinitions/ioc_milestone.xmi
new file mode 100644
index 0000000..0924072
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/termdefinitions/ioc_milestone.xmi
@@ -0,0 +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: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="-gEgZg2UkFLjGeXkJLpAP6A"
+ name=",_O7JBYEvFEdunZcj9T5hrMQ" guid="-gEgZg2UkFLjGeXkJLpAP6A" changeDate="2006-09-24T06:41:48.635-0700">
+ <mainDescription>At the end of Construction phase is the third important project milestone.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/termdefinitions/lca_milestone.xmi b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/termdefinitions/lca_milestone.xmi
new file mode 100644
index 0000000..3d2e5fa
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/termdefinitions/lca_milestone.xmi
@@ -0,0 +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: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="-MllWL01NL93RTB7VsY69fw"
+ name=",_NL4DMEvFEdunZcj9T5hrMQ" guid="-MllWL01NL93RTB7VsY69fw">
+ <mainDescription>At the end of the Elaboration phase is the second important project milestone</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/termdefinitions/lco_milestone.xmi b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/termdefinitions/lco_milestone.xmi
new file mode 100644
index 0000000..209d18e
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/termdefinitions/lco_milestone.xmi
@@ -0,0 +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: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="-Rl8kaRW9Bxqdvq32kVCi7w"
+ name=",_LGRBkEvFEdunZcj9T5hrMQ" guid="-Rl8kaRW9Bxqdvq32kVCi7w">
+ <mainDescription>At the end of the Inception phase is the first major project milestone</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/termdefinitions/pr_milestone.xmi b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/termdefinitions/pr_milestone.xmi
new file mode 100644
index 0000000..4d4267b
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/termdefinitions/pr_milestone.xmi
@@ -0,0 +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: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="-JegYQHIteCRN0iV2EKMjSA"
+ name=",_QuywUEvFEdunZcj9T5hrMQ" guid="-JegYQHIteCRN0iV2EKMjSA">
+ <mainDescription>At the end of the Transition phase is the last major project milestone</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/termdefinitions/transition.xmi b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/termdefinitions/transition.xmi
new file mode 100644
index 0000000..f30a628
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/guidances/termdefinitions/transition.xmi
@@ -0,0 +1,10 @@
+<?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: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="-yoFF90pq-_UV3fm-5oDenw"
+ name=",_-5ms4EvDEdunZcj9T5hrMQ" guid="-yoFF90pq-_UV3fm-5oDenw" changeDate="2008-02-22T01:57:04.656-0500"
+ version="7.2.0">
+ <mainDescription>The fourth and last <span class="docEmphasis">phase</span> of the project lifecycle, which results in a final product <span
+class="docEmphasis">release</span>.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/plugin.xmi b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/plugin.xmi
new file mode 100644
index 0000000..e05b5f1
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/plugin.xmi
@@ -0,0 +1,354 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_4gXdsL8BEdyWX5Yd-9QZ1A"
+ guid="_4gXdsL8BEdyWX5Yd-9QZ1A">
+ <subManagers xmi:id="_F0V5kOL7EdyM47cGD2jiaQ" href="uma://_FzchsOL7EdyM47cGD2jiaQ#_F0V5kOL7EdyM47cGD2jiaQ"/>
+ <subManagers xmi:id="_THHFQOL9EdyM47cGD2jiaQ" href="uma://_SKnAwOL9EdyM47cGD2jiaQ#_THHFQOL9EdyM47cGD2jiaQ"/>
+ <resourceDescriptors xmi:id="_B2T28ROPEduCNqgZdt_OaA" id="-FrUmsKsGW4bnNmb9uaNOkg"
+ uri="guidances/concepts/transition_phase.xmi"/>
+ <resourceDescriptors xmi:id="_eMOOgBONEduCNqgZdt_OaA" id="-GRJW_KNOJoEQF3r6lmBrEw"
+ uri="guidances/concepts/inception_phase.xmi"/>
+ <resourceDescriptors xmi:id="_o3qSICdEEduIsqH1Q6ZuqA" id="-DG8mYMnTGosWIxjPQFUoTA"
+ uri="guidances/concepts/phase_milestones.xmi"/>
+ <resourceDescriptors xmi:id="_esJPQBOOEduCNqgZdt_OaA" id="-bbpT_BdDRrv6waNI365Qhg"
+ uri="guidances/concepts/construction_phase.xmi"/>
+ <resourceDescriptors xmi:id="_CyjSMBOOEduCNqgZdt_OaA" id="-F-eWIBzxEXE1jygbN3nrrQ"
+ uri="guidances/concepts/elaboration_phase.xmi"/>
+ <resourceDescriptors xmi:id="_qpZKsCNZEdyCq8v2ZO4QcA" id="-ebKPqn9bWfbh1K2spgOwWQ"
+ uri="guidances/concepts/project_lifecycle.xmi"/>
+ <resourceDescriptors xmi:id="_D7dnwEvFEdunZcj9T5hrMQ" id="-dhgOQQ4GsV0-dNJmTmF9GA"
+ uri="guidances/termdefinitions/inception.xmi"/>
+ <resourceDescriptors xmi:id="_EAp3gEvKEdunZcj9T5hrMQ" id="-gEgZg2UkFLjGeXkJLpAP6A"
+ uri="guidances/termdefinitions/ioc_milestone.xmi"/>
+ <resourceDescriptors xmi:id="_5QECwEvJEdunZcj9T5hrMQ" id="-MllWL01NL93RTB7VsY69fw"
+ uri="guidances/termdefinitions/lca_milestone.xmi"/>
+ <resourceDescriptors xmi:id="_4dN4QEvDEdunZcj9T5hrMQ" id="-5wJmUR0WqX7lCIxsyqFsdA"
+ uri="guidances/termdefinitions/construction.xmi"/>
+ <resourceDescriptors xmi:id="_5KcVYUvpEdunZcj9T5hrMQ" id="-yoFF90pq-_UV3fm-5oDenw"
+ uri="guidances/termdefinitions/transition.xmi"/>
+ <resourceDescriptors xmi:id="_DMZa8EvIEdunZcj9T5hrMQ" id="-0g2jTHQla8lbP6xGB3iGlg"
+ uri="guidances/termdefinitions/elaboration.xmi"/>
+ <resourceDescriptors xmi:id="_Nh-cwEvKEdunZcj9T5hrMQ" id="-JegYQHIteCRN0iV2EKMjSA"
+ uri="guidances/termdefinitions/pr_milestone.xmi"/>
+ <resourceDescriptors xmi:id="_tgigkEvJEdunZcj9T5hrMQ" id="-Rl8kaRW9Bxqdvq32kVCi7w"
+ uri="guidances/termdefinitions/lco_milestone.xmi"/>
+ <resourceDescriptors xmi:id="_XSM3sBjoEduxUfEVCtmW4Q" id="-cy0DcnEk7uJJ1OOH3_E6rg"
+ uri="guidances/supportingmaterials/delivery_process_graph.xmi"/>
+ <resourceDescriptors xmi:id="_Y7aZYb8SEdyWX5Yd-9QZ1A" id="-nKGm7zbsVde3L5ev2OeazQ"
+ uri="customcategories/risk_value_lifecycle_practice.xmi"/>
+ <resourceDescriptors xmi:id="_XS6AsC7oEdqHMdmRzC0-2g" id="-bhzuf6RMHP3d-AHkoKDg7g"
+ uri="guidances/concepts/phase.xmi"/>
+ <resourceDescriptors xmi:id="_nDwNIPL5Edm6Nvont3uinw" id="_XjOXcMM2EdmSIPI87WLu3g"
+ uri="guidances/templates/project_plan.xmi"/>
+ <resourceDescriptors xmi:id="_UItQgDoAEdusGsHODb-STA" id="-IdlCQXdDNYGrGJU4TBwvCA"
+ uri="guidances/examples/project_plan.xmi"/>
+ <resourceDescriptors xmi:id="_1BKVgEptEduVV9JixWe5Rw" id="-hrDndmFd0zexB0HNYX3gww"
+ uri="guidances/reports/project_burndown.xmi"/>
+ <resourceDescriptors xmi:id="_dh6XQDcGEdyTZ9G7ByfQTw" id="-ThmcJuMmkwabvA7gn7hC6g"
+ uri="guidances/examples/project_burndown_report_example.xmi"/>
+ <resourceDescriptors xmi:id="_eKb0scOAEdy3nv0ZK8D4GQ" id="-sqx8arvFbAtMVoqGeHA_kA"
+ uri="guidances/supportingmaterials/release_info_risk_value_lifecycle.xmi"/>
+ <resourceDescriptors xmi:id="_AVdbMC3yEdycYKq0PulnEQ" id="-aOaMjqW4RZWOiHT1_U1NNw"
+ uri="guidances/guidelines/deploying_the_solution.xmi"/>
+ <resourceDescriptors xmi:id="_TDZ60OFZEdyhmsbt0Xyl8A" id="-EYuybNBtVpvW4i5T_j805w"
+ uri="tasks/assess_results.guidance.xmi"/>
+ <resourceDescriptors xmi:id="_ylpCcOFtEdyhmsbt0Xyl8A" id="-3Jpwts4YZlF8GJjQaSINRA"
+ uri="tasks/plan_the_project.additions.xmi"/>
+ <resourceDescriptors xmi:id="_Fzchs-L7EdyM47cGD2jiaQ" id="_FzchsOL7EdyM47cGD2jiaQ"
+ uri="capabilitypatterns/risk_value_lifecycle_phasesXXX/model.xmi"/>
+ <resourceDescriptors xmi:id="_TG0KUeL9EdyM47cGD2jiaQ" id="_SKnAwOL9EdyM47cGD2jiaQ"
+ uri="capabilitypatterns/risk_value_lifecycle_phases/model.xmi"/>
+ <resourceDescriptors xmi:id="_EjKOceMPEdyM47cGD2jiaQ" id="-R1d0qAJDnmI5Fm9ChHCYQw"
+ uri="guidances/roadmaps/how_to_adopt.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_4gXdoL8BEdyWX5Yd-9QZ1A" name="practice.mgmt.risk_value_lifecycle.base"
+ guid="_4gXdoL8BEdyWX5Yd-9QZ1A" changeDate="2008-02-21T22:48:11.062-0800">
+ <copyrightStatement href="uma://_iVydgENdEdy245g62lfWcA#_cTs20KzREduOqvpk_MDLfQ"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4gXdob8BEdyWX5Yd-9QZ1A"
+ name="Content" guid="_4gXdob8BEdyWX5Yd-9QZ1A">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4gXdor8BEdyWX5Yd-9QZ1A"
+ name="Categories" guid="_4gXdor8BEdyWX5Yd-9QZ1A">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4gXdo78BEdyWX5Yd-9QZ1A"
+ name="Domains" guid="_4gXdo78BEdyWX5Yd-9QZ1A"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4gXdpL8BEdyWX5Yd-9QZ1A"
+ name="Disciplines" guid="_4gXdpL8BEdyWX5Yd-9QZ1A"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4gXdpb8BEdyWX5Yd-9QZ1A"
+ name="RoleSets" guid="_4gXdpb8BEdyWX5Yd-9QZ1A"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4gXdpr8BEdyWX5Yd-9QZ1A"
+ name="WP Types" guid="_4gXdpr8BEdyWX5Yd-9QZ1A"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4gXdp78BEdyWX5Yd-9QZ1A"
+ name="Tools" guid="_4gXdp78BEdyWX5Yd-9QZ1A"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4gXdqL8BEdyWX5Yd-9QZ1A"
+ name="StandardCategories" guid="_4gXdqL8BEdyWX5Yd-9QZ1A"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4gXdqb8BEdyWX5Yd-9QZ1A"
+ name="CustomCategories" guid="_4gXdqb8BEdyWX5Yd-9QZ1A">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4gXdqr8BEdyWX5Yd-9QZ1A"
+ name="Hidden" guid="_4gXdqr8BEdyWX5Yd-9QZ1A">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_4gXdq78BEdyWX5Yd-9QZ1A"
+ name="Custom Categories" guid="_4gXdq78BEdyWX5Yd-9QZ1A" categorizedElements="_7Q49IL8EEdyWX5Yd-9QZ1A _uy5kUMh5EdygFZkm1d5NtQ"/>
+ </childPackages>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_7Q49IL8EEdyWX5Yd-9QZ1A"
+ name="risk_value_lifecycle_practice" guid="_7Q49IL8EEdyWX5Yd-9QZ1A"
+ briefDescription="This practice aligns the project around four phases (Inception, Elaboration, Construction, and Transition). Each phase has specific goals and risks to be addressed that drive the project towards a successful completion. Milestones at the end of each phase validate mitigation of the risks addressed in the phase, as well as the value achieved."
+ presentationName="Risk-Value Lifecycle" shapeicon="customcategories/resources/pract_dgm32.gif"
+ nodeicon="customcategories/resources/pract_obj.gif">
+ <methodElementProperty xmi:id="_oxskUL8MEdyWX5Yd-9QZ1A" name="CategoryElementsSortType"
+ value="Manual"/>
+ <presentation xmi:id="-nKGm7zbsVde3L5ev2OeazQ" href="uma://-nKGm7zbsVde3L5ev2OeazQ#-nKGm7zbsVde3L5ev2OeazQ"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Roadmap" href="#_ERIDQOMPEdyM47cGD2jiaQ"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://_SKnAwOL9EdyM47cGD2jiaQ#_SKnA1uL9EdyM47cGD2jiaQ"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:CustomCategory" href="#_UfU6wOMQEdyM47cGD2jiaQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_uy5kUMh5EdygFZkm1d5NtQ"
+ name="contributions_to_nav_building_blocks" guid="_uy5kUMh5EdygFZkm1d5NtQ"
+ presentationName="Contributions to Navigation Building Blocks" categorizedElements="_aLCoIMh8EdygFZkm1d5NtQ _iZzZUMh8EdygFZkm1d5NtQ _iZzZUch8EdygFZkm1d5NtQ _0rirUMh8EdygFZkm1d5NtQ _0rirUch8EdygFZkm1d5NtQ _iZzZUsh8EdygFZkm1d5NtQ _Yuo1oNQvEdyM_J8-fv54DA _Hw34cNnLEdyzZqGyZ7hwdw _DnSmoOMQEdyM47cGD2jiaQ"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_aLCoIMh8EdygFZkm1d5NtQ"
+ name="release_info.assign" guid="_aLCoIMh8EdygFZkm1d5NtQ" variabilityType="contributes"
+ categorizedElements="_Oc6L4MOAEdy3nv0ZK8D4GQ">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCIHYcRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_iZzZUMh8EdygFZkm1d5NtQ"
+ name="concept_list" guid="_iZzZUMh8EdygFZkm1d5NtQ" variabilityType="contributes"
+ categorizedElements="_48EKsBOMEduCNqgZdt_OaA _2plxwBOMEduCNqgZdt_OaA _0hmKgBOMEduCNqgZdt_OaA _HNxbwMBJEdqSgKaj2SZBmg __7xOEC7aEdqHMdmRzC0-2g _nSfVwCNYEdyCq8v2ZO4QcA __ca5UBOMEduCNqgZdt_OaA">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4Y8RdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_iZzZUch8EdygFZkm1d5NtQ"
+ name="report_list.assign" guid="_iZzZUch8EdygFZkm1d5NtQ" variabilityType="contributes"
+ categorizedElements="_ePrt8Dj3EduxovfWMDsntw">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_sJd8gMReEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_iZzZUsh8EdygFZkm1d5NtQ"
+ name="practice_list.assign" guid="_iZzZUsh8EdygFZkm1d5NtQ" variabilityType="contributes"
+ categorizedElements="_7Q49IL8EEdyWX5Yd-9QZ1A">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCIHY8RdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_0rirUMh8EdygFZkm1d5NtQ"
+ name="example_list.assign" guid="_0rirUMh8EdygFZkm1d5NtQ" variabilityType="contributes"
+ categorizedElements="_Yiq2EDcGEdyTZ9G7ByfQTw _Nzv5kDoAEdusGsHODb-STA">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4ZMRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_0rirUch8EdygFZkm1d5NtQ"
+ name="template_list.assign" guid="_0rirUch8EdygFZkm1d5NtQ" variabilityType="contributes"
+ categorizedElements="_0c7hoMlgEdmt3adZL5Dmdw">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4Z8RdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_Yuo1oNQvEdyM_J8-fv54DA"
+ name="management_practice_list.assign" guid="_Yuo1oNQvEdyM_J8-fv54DA"
+ variabilityType="contributes" categorizedElements="_7Q49IL8EEdyWX5Yd-9QZ1A">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_auUD0NQuEdyM_J8-fv54DA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_Hw34cNnLEdyzZqGyZ7hwdw"
+ name="guideline_list.assign" guid="_Hw34cNnLEdyzZqGyZ7hwdw" variabilityType="contributes"
+ categorizedElements="_yYlQoC3xEdycYKq0PulnEQ">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4ZcRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_DnSmoOMQEdyM47cGD2jiaQ"
+ name="roadmap_list.assign" guid="_DnSmoOMQEdyM47cGD2jiaQ" variabilityType="contributes"
+ categorizedElements="_ERIDQOMPEdyM47cGD2jiaQ">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4ZsRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_UfU6wOMQEdyM47cGD2jiaQ"
+ name="guidances" guid="_UfU6wOMQEdyM47cGD2jiaQ" presentationName="Guidances"
+ shapeicon="customcategories/resources/bookcL.gif" nodeicon="customcategories/resources/bookc.gif"
+ categorizedElements="_ePrt8Dj3EduxovfWMDsntw _Yiq2EDcGEdyTZ9G7ByfQTw _Nzv5kDoAEdusGsHODb-STA _0c7hoMlgEdmt3adZL5Dmdw _48EKsBOMEduCNqgZdt_OaA _yYlQoC3xEdycYKq0PulnEQ _2plxwBOMEduCNqgZdt_OaA _0hmKgBOMEduCNqgZdt_OaA __7xOEC7aEdqHMdmRzC0-2g _HNxbwMBJEdqSgKaj2SZBmg _nSfVwCNYEdyCq8v2ZO4QcA __ca5UBOMEduCNqgZdt_OaA">
+ <methodElementProperty xmi:id="_fuwAkOMQEdyM47cGD2jiaQ" name="CategoryElementsSortType"
+ value="MethodType"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4gXdrL8BEdyWX5Yd-9QZ1A"
+ name="CoreContent" guid="_4gXdrL8BEdyWX5Yd-9QZ1A">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_fiq3sL8GEdyWX5Yd-9QZ1A"
+ name="Risk-Value Lifecycle" guid="_fiq3sL8GEdyWX5Yd-9QZ1A">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_f4YZsMN_Edy3nv0ZK8D4GQ"
+ name="Release Info" guid="_f4YZsMN_Edy3nv0ZK8D4GQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="_Oc6L4MOAEdy3nv0ZK8D4GQ"
+ name="release_info_risk_value_lifecycle" guid="_Oc6L4MOAEdy3nv0ZK8D4GQ"
+ presentationName="Risk-Value Lifecycle Practice">
+ <presentation xmi:id="-sqx8arvFbAtMVoqGeHA_kA" href="uma://-sqx8arvFbAtMVoqGeHA_kA#-sqx8arvFbAtMVoqGeHA_kA"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_B3azkMh5EdygFZkm1d5NtQ"
+ name="Template, Report, and Examples" guid="_B3azkMh5EdygFZkm1d5NtQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:Example" xmi:id="_Yiq2EDcGEdyTZ9G7ByfQTw"
+ name="project_burndown_report_example" guid="_Yiq2EDcGEdyTZ9G7ByfQTw"
+ briefDescription="This is an example of a project burndown report."
+ presentationName="Project Burndown Report">
+ <presentation xmi:id="-ThmcJuMmkwabvA7gn7hC6g" href="uma://-ThmcJuMmkwabvA7gn7hC6g#-ThmcJuMmkwabvA7gn7hC6g"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Example" xmi:id="_Nzv5kDoAEdusGsHODb-STA"
+ name="project_plan" guid="_Nzv5kDoAEdusGsHODb-STA" briefDescription="This is an example of a project plan."
+ presentationName="Project Plan">
+ <presentation xmi:id="-IdlCQXdDNYGrGJU4TBwvCA" href="uma://-IdlCQXdDNYGrGJU4TBwvCA#-IdlCQXdDNYGrGJU4TBwvCA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Template" xmi:id="_0c7hoMlgEdmt3adZL5Dmdw"
+ name="project_plan" guid="_0c7hoMlgEdmt3adZL5Dmdw" briefDescription="This is the informal template for representing the project plan."
+ presentationName="Project Plan">
+ <presentation xmi:id="_XjOXcMM2EdmSIPI87WLu3g" href="uma://_XjOXcMM2EdmSIPI87WLu3g#_XjOXcMM2EdmSIPI87WLu3g"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Report" xmi:id="_ePrt8Dj3EduxovfWMDsntw"
+ name="project_burndown" guid="_ePrt8Dj3EduxovfWMDsntw" briefDescription="An effective way of communicating project progress."
+ presentationName="Project Burndown">
+ <presentation xmi:id="-hrDndmFd0zexB0HNYX3gww" href="uma://-hrDndmFd0zexB0HNYX3gww#-hrDndmFd0zexB0HNYX3gww"/>
+ </contentElements>
+ </childPackages>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_48EKsBOMEduCNqgZdt_OaA"
+ name="construction_phase" guid="_48EKsBOMEduCNqgZdt_OaA" briefDescription="Third of the four phases in the project lifecycle, Construction focuses on design, implementation, and testing of functionalities to develop a complete system."
+ presentationName="Construction Phase">
+ <presentation xmi:id="-bbpT_BdDRrv6waNI365Qhg" href="uma://-bbpT_BdDRrv6waNI365Qhg#-bbpT_BdDRrv6waNI365Qhg"/>
+ <conceptsAndPapers href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_lam4ADkBEduxovfWMDsntw"/>
+ <conceptsAndPapers href="#_nSfVwCNYEdyCq8v2ZO4QcA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_2plxwBOMEduCNqgZdt_OaA"
+ name="elaboration_phase" guid="_2plxwBOMEduCNqgZdt_OaA" briefDescription="Second of four phases in the project lifecycle, when architecturally significant risks are addressed."
+ presentationName="Elaboration Phase">
+ <presentation xmi:id="-F-eWIBzxEXE1jygbN3nrrQ" href="uma://-F-eWIBzxEXE1jygbN3nrrQ#-F-eWIBzxEXE1jygbN3nrrQ"/>
+ <conceptsAndPapers href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_lam4ADkBEduxovfWMDsntw"/>
+ <conceptsAndPapers href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0bsLgMlgEdmt3adZL5Dmdw"/>
+ <conceptsAndPapers href="#_nSfVwCNYEdyCq8v2ZO4QcA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_0hmKgBOMEduCNqgZdt_OaA"
+ name="inception_phase" guid="_0hmKgBOMEduCNqgZdt_OaA" briefDescription="First of the four phases in the project lifecycle, it is about understanding the project scope and objectives and getting enough information to confirm that the project should proceed - or convince you that it should not."
+ presentationName="Inception Phase">
+ <presentation xmi:id="-GRJW_KNOJoEQF3r6lmBrEw" href="uma://-GRJW_KNOJoEQF3r6lmBrEw#-GRJW_KNOJoEQF3r6lmBrEw"/>
+ <conceptsAndPapers href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_lam4ADkBEduxovfWMDsntw"/>
+ <conceptsAndPapers href="#_nSfVwCNYEdyCq8v2ZO4QcA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_HNxbwMBJEdqSgKaj2SZBmg"
+ name="phase_milestones" guid="_HNxbwMBJEdqSgKaj2SZBmg" briefDescription="The point at which a phase formally ends, thus providing a check-point for whether the project is ready to move to the next phase."
+ presentationName="Phase Milestones" conceptsAndPapers="_48EKsBOMEduCNqgZdt_OaA _2plxwBOMEduCNqgZdt_OaA _0hmKgBOMEduCNqgZdt_OaA __ca5UBOMEduCNqgZdt_OaA">
+ <presentation xmi:id="-DG8mYMnTGosWIxjPQFUoTA" href="uma://-DG8mYMnTGosWIxjPQFUoTA#-DG8mYMnTGosWIxjPQFUoTA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="__ca5UBOMEduCNqgZdt_OaA"
+ name="transition_phase" guid="__ca5UBOMEduCNqgZdt_OaA" briefDescription="Fourth and final phase in the project lifecycle."
+ presentationName="Transition Phase">
+ <presentation xmi:id="-FrUmsKsGW4bnNmb9uaNOkg" href="uma://-FrUmsKsGW4bnNmb9uaNOkg#-FrUmsKsGW4bnNmb9uaNOkg"/>
+ <conceptsAndPapers href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_lam4ADkBEduxovfWMDsntw"/>
+ <conceptsAndPapers href="#_nSfVwCNYEdyCq8v2ZO4QcA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_nSfVwCNYEdyCq8v2ZO4QcA"
+ name="project_lifecycle" guid="_nSfVwCNYEdyCq8v2ZO4QcA" briefDescription="The project lifecycle provides stakeholders and team members with visibility, synchronization points, and decisions points throughout the project enabling oversight and go/no-go decisions to be taken at appropriate times."
+ presentationName="Project Lifecycle" shapeicon="guidances/concepts/resources/concept_dgm32.gif"
+ nodeicon="guidances/concepts/resources/concept_obj.gif">
+ <presentation xmi:id="-ebKPqn9bWfbh1K2spgOwWQ" href="uma://-ebKPqn9bWfbh1K2spgOwWQ#-ebKPqn9bWfbh1K2spgOwWQ"/>
+ <conceptsAndPapers href="#__7xOEC7aEdqHMdmRzC0-2g"/>
+ <conceptsAndPapers href="#_48EKsBOMEduCNqgZdt_OaA"/>
+ <conceptsAndPapers href="#_2plxwBOMEduCNqgZdt_OaA"/>
+ <conceptsAndPapers href="#_0hmKgBOMEduCNqgZdt_OaA"/>
+ <conceptsAndPapers href="#__ca5UBOMEduCNqgZdt_OaA"/>
+ <conceptsAndPapers href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0bsLgMlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_0sD60EvDEdunZcj9T5hrMQ"
+ name="construction" guid="_0sD60EvDEdunZcj9T5hrMQ" presentationName="Construction">
+ <presentation xmi:id="-5wJmUR0WqX7lCIxsyqFsdA" href="uma://-5wJmUR0WqX7lCIxsyqFsdA#-5wJmUR0WqX7lCIxsyqFsdA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_8DkT4EvDEdunZcj9T5hrMQ"
+ name="elaboration" guid="_8DkT4EvDEdunZcj9T5hrMQ" presentationName="Elaboration">
+ <presentation xmi:id="-0g2jTHQla8lbP6xGB3iGlg" href="uma://-0g2jTHQla8lbP6xGB3iGlg#-0g2jTHQla8lbP6xGB3iGlg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_525A8EvDEdunZcj9T5hrMQ"
+ name="inception" guid="_525A8EvDEdunZcj9T5hrMQ" presentationName="Inception">
+ <presentation xmi:id="-dhgOQQ4GsV0-dNJmTmF9GA" href="uma://-dhgOQQ4GsV0-dNJmTmF9GA#-dhgOQQ4GsV0-dNJmTmF9GA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_O7JBYEvFEdunZcj9T5hrMQ"
+ name="ioc_milestone" guid="_O7JBYEvFEdunZcj9T5hrMQ" presentationName="Initial Operational Capability Milestone.">
+ <presentation xmi:id="-gEgZg2UkFLjGeXkJLpAP6A" href="uma://-gEgZg2UkFLjGeXkJLpAP6A#-gEgZg2UkFLjGeXkJLpAP6A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_NL4DMEvFEdunZcj9T5hrMQ"
+ name="lca_milestone" guid="_NL4DMEvFEdunZcj9T5hrMQ" presentationName="Lifecycle Architecture Milestone ">
+ <presentation xmi:id="-MllWL01NL93RTB7VsY69fw" href="uma://-MllWL01NL93RTB7VsY69fw#-MllWL01NL93RTB7VsY69fw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_LGRBkEvFEdunZcj9T5hrMQ"
+ name="lco_milestone" guid="_LGRBkEvFEdunZcj9T5hrMQ" presentationName="Lifecycle Objectives Milestone">
+ <presentation xmi:id="-Rl8kaRW9Bxqdvq32kVCi7w" href="uma://-Rl8kaRW9Bxqdvq32kVCi7w#-Rl8kaRW9Bxqdvq32kVCi7w"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_QuywUEvFEdunZcj9T5hrMQ"
+ name="pr_milestone" guid="_QuywUEvFEdunZcj9T5hrMQ" presentationName="Product Release Milestone ">
+ <presentation xmi:id="-JegYQHIteCRN0iV2EKMjSA" href="uma://-JegYQHIteCRN0iV2EKMjSA#-JegYQHIteCRN0iV2EKMjSA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_-5ms4EvDEdunZcj9T5hrMQ"
+ name="transition" guid="_-5ms4EvDEdunZcj9T5hrMQ" presentationName="Transition">
+ <presentation xmi:id="-yoFF90pq-_UV3fm-5oDenw" href="uma://-yoFF90pq-_UV3fm-5oDenw#-yoFF90pq-_UV3fm-5oDenw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_g4iB8L8HEdyWX5Yd-9QZ1A"
+ name="assess_results.guidance" guid="_g4iB8L8HEdyWX5Yd-9QZ1A" orderingGuide="<?xml version="1.0" encoding="ASCII"?>
<org.eclipse.epf.uma.edit.tng.util.model:OrderInfoCollection xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma.edit.tng.util.model="http:///com/ibm/uma/edit/tng/util/model.ecore">
 <orderInfos name="sections" timestamp="1203693285796">
 <gUIDs>_o28GgMMsEdmdo9HxCRR_Gw</gUIDs>
 <gUIDs>_iSiDEIx4Edyzd4h-mxj9YA</gUIDs>
 <gUIDs>_iL7cQEpqEdup0IY9DKDPkg</gUIDs>
 <gUIDs>_uYLJAOFYEdyhmsbt0Xyl8A</gUIDs>
 <gUIDs>_1YHH8DLqEdueZPye-FaNgA</gUIDs>
 </orderInfos>
</org.eclipse.epf.uma.edit.tng.util.model:OrderInfoCollection>
"
+ variabilityType="contributes" conceptsAndPapers="_HNxbwMBJEdqSgKaj2SZBmg"
+ guidelines="_yYlQoC3xEdycYKq0PulnEQ">
+ <presentation xmi:id="-EYuybNBtVpvW4i5T_j805w" href="uma://-EYuybNBtVpvW4i5T_j805w#-EYuybNBtVpvW4i5T_j805w"/>
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Task" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_0l53cMlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_yKWvEL8HEdyWX5Yd-9QZ1A"
+ name="plan_the_project.additions" guid="_yKWvEL8HEdyWX5Yd-9QZ1A" orderingGuide="<?xml version="1.0" encoding="ASCII"?>
<org.eclipse.epf.uma.edit.tng.util.model:OrderInfoCollection xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma.edit.tng.util.model="http:///com/ibm/uma/edit/tng/util/model.ecore">
 <orderInfos name="sections" timestamp="1203702124984">
 <gUIDs>_gu-PgIyBEdyhZb-MhCJrlA</gUIDs>
 <gUIDs>_jknm8IyBEdyhZb-MhCJrlA</gUIDs>
 <gUIDs>_lrYj0MBAEdqSgKaj2SZBmg</gUIDs>
 <gUIDs>_4Xg3QOFpEdyhmsbt0Xyl8A</gUIDs>
 <gUIDs>_uu1coIyBEdyhZb-MhCJrlA</gUIDs>
 <gUIDs>_X63B4OFtEdyhmsbt0Xyl8A</gUIDs>
 <gUIDs>_xWBhUIyBEdyhZb-MhCJrlA</gUIDs>
 <gUIDs>_zeN84IyBEdyhZb-MhCJrlA</gUIDs>
 </orderInfos>
</org.eclipse.epf.uma.edit.tng.util.model:OrderInfoCollection>
"
+ variabilityType="contributes" conceptsAndPapers="_HNxbwMBJEdqSgKaj2SZBmg">
+ <presentation xmi:id="-3Jpwts4YZlF8GJjQaSINRA" href="uma://-3Jpwts4YZlF8GJjQaSINRA#-3Jpwts4YZlF8GJjQaSINRA"/>
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Task" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_0lC70MlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="__7xOEC7aEdqHMdmRzC0-2g"
+ name="phase" guid="__7xOEC7aEdqHMdmRzC0-2g" briefDescription="This guidance introduces the concept of a phase and its purpose within a project."
+ presentationName="Phase">
+ <presentation xmi:id="-bhzuf6RMHP3d-AHkoKDg7g" href="uma://-bhzuf6RMHP3d-AHkoKDg7g#-bhzuf6RMHP3d-AHkoKDg7g"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_NIW3MMLlEdysDsQChI42QQ"
+ name="project_plan.guidance" guid="_NIW3MMLlEdysDsQChI42QQ" variabilityType="contributes"
+ examples="_Yiq2EDcGEdyTZ9G7ByfQTw _Nzv5kDoAEdusGsHODb-STA" reports="_ePrt8Dj3EduxovfWMDsntw"
+ templates="_0c7hoMlgEdmt3adZL5Dmdw">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_0a6vcMlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="_Pt_fYBjoEduxUfEVCtmW4Q"
+ name="delivery_process_graph" guid="_Pt_fYBjoEduxUfEVCtmW4Q" presentationName="Delivery Process Graph">
+ <presentation xmi:id="-cy0DcnEk7uJJ1OOH3_E6rg" href="uma://-cy0DcnEk7uJJ1OOH3_E6rg#-cy0DcnEk7uJJ1OOH3_E6rg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_yYlQoC3xEdycYKq0PulnEQ"
+ name="deploying_the_solution" guid="_yYlQoC3xEdycYKq0PulnEQ" briefDescription="This guideline describes activities that usually take place when moving the developed software into production."
+ presentationName="Deploying the Solution">
+ <presentation xmi:id="-aOaMjqW4RZWOiHT1_U1NNw" href="uma://-aOaMjqW4RZWOiHT1_U1NNw#-aOaMjqW4RZWOiHT1_U1NNw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_eZ1CAOKBEdyM47cGD2jiaQ"
+ name="plan_iteration.guidance" guid="_eZ1CAOKBEdyM47cGD2jiaQ" variabilityType="contributes"
+ guidelines="_yYlQoC3xEdycYKq0PulnEQ">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Task" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_0keUEMlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Roadmap" xmi:id="_ERIDQOMPEdyM47cGD2jiaQ"
+ name="how_to_adopt" guid="_ERIDQOMPEdyM47cGD2jiaQ" briefDescription="This roadmap describes how to adopt the Risk-Value Lifecycle Practice."
+ presentationName="How to Adopt This Practice">
+ <presentation xmi:id="-R1d0qAJDnmI5Fm9ChHCYQw" href="uma://-R1d0qAJDnmI5Fm9ChHCYQw#-R1d0qAJDnmI5Fm9ChHCYQw"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_4gXdrb8BEdyWX5Yd-9QZ1A"
+ name="CapabilityPatterns" guid="_4gXdrb8BEdyWX5Yd-9QZ1A">
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_LYTG0OL6EdyM47cGD2jiaQ"
+ name="Risk-Value Lifecycle Phases" guid="_LYTG0OL6EdyM47cGD2jiaQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessComponent" xmi:id="_FzchsOL7EdyM47cGD2jiaQ"
+ href="uma://_FzchsOL7EdyM47cGD2jiaQ#_FzchsOL7EdyM47cGD2jiaQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessComponent" xmi:id="_SKnAwOL9EdyM47cGD2jiaQ"
+ href="uma://_SKnAwOL9EdyM47cGD2jiaQ#_SKnAwOL9EdyM47cGD2jiaQ"/>
+ </childPackages>
+ </childPackages>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_4gXdrr8BEdyWX5Yd-9QZ1A"
+ name="DeliveryProcesses" guid="_4gXdrr8BEdyWX5Yd-9QZ1A"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_4gXdr78BEdyWX5Yd-9QZ1A"
+ name="ProcessContributions" guid="_4gXdr78BEdyWX5Yd-9QZ1A"/>
+ <bases href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0TmecJ-VEdy3Nc4rvuj7bA"/>
+ <bases href="uma://_iVydgENdEdy245g62lfWcA#_iVydgENdEdy245g62lfWcA"/>
+ <bases href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS10J6YEdyQN-zRFaRrCQ"/>
+ <bases href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzAJ6WEdyQN-zRFaRrCQ"/>
+ <bases href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno4EKmEdyrauqpmnA8jQ"/>
+ <bases href="uma://_WCUhAO8KEdmKSqa_gSYthg#_WCUhAO8KEdmKSqa_gSYthg"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/tasks/assess_results.guidance.xmi b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/tasks/assess_results.guidance.xmi
new file mode 100644
index 0000000..5d05dfa
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/tasks/assess_results.guidance.xmi
@@ -0,0 +1,18 @@
+<?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.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="-EYuybNBtVpvW4i5T_j805w"
+ name="assess_results.guidance,_g4iB8L8HEdyWX5Yd-9QZ1A" guid="-EYuybNBtVpvW4i5T_j805w">
+ <sections xmi:id="_uYLJAOFYEdyhmsbt0Xyl8A" name="Perform a retrospective (end of phase)"
+ guid="_uYLJAOFYEdyhmsbt0Xyl8A">
+ <sectionDescription><p>
+ When the assessment period coincides with the end of a phase the corresponding milestone review takes place. These are
+ informal reviews of the work accomplished where the team and stakeholders agree on moving the project on to the next
+ phase, spanning a set of iterations with a new common goal, in accordance with the emphasis of the following phase. For
+ more information, refer to <a class="elementLinkWithType"
+ href="./../../practice.mgmt.risk_value_lifecycle.base/guidances/concepts/phase_milestones_5678231E.html"
+ guid="_HNxbwMBJEdqSgKaj2SZBmg">Concept: Phase Milestones</a>.
+</p></sectionDescription>
+ </sections>
+</org.eclipse.epf.uma:TaskDescription>
diff --git a/praclib/temp/practice.mgmt.risk_value_lifecycle.base/tasks/plan_the_project.additions.xmi b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/tasks/plan_the_project.additions.xmi
new file mode 100644
index 0000000..064076a
--- /dev/null
+++ b/praclib/temp/practice.mgmt.risk_value_lifecycle.base/tasks/plan_the_project.additions.xmi
@@ -0,0 +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.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="-3Jpwts4YZlF8GJjQaSINRA"
+ name="plan_the_project.additions,_yKWvEL8HEdyWX5Yd-9QZ1A" guid="-3Jpwts4YZlF8GJjQaSINRA">
+ <sections xmi:id="_X63B4OFtEdyhmsbt0Xyl8A" name="Outline project lifecycle" guid="_X63B4OFtEdyhmsbt0Xyl8A">
+ <sectionDescription><p>
+ Organize&nbsp;iterations into a set of phases. Each phase in the project lifecycle will end with a milestone aimed at
+ providing stakeholders with&nbsp;oversight and steering mechanisms to control project funding, scope, risk exposure,
+ value provided, and other aspects of the process (see <a class="elementLinkWithType"
+ href="./../../practice.mgmt.risk_value_lifecycle.base/guidances/concepts/project_lifecycle_203F87.html"
+ guid="_nSfVwCNYEdyCq8v2ZO4QcA">Concept: Project Lifecycle</a>)
+</p></sectionDescription>
+ </sections>
+</org.eclipse.epf.uma:TaskDescription>
diff --git a/praclib/temp/practice.mgmt.two_level_project_planning.assign/.project b/praclib/temp/practice.mgmt.two_level_project_planning.assign/.project
new file mode 100644
index 0000000..5685d45
--- /dev/null
+++ b/praclib/temp/practice.mgmt.two_level_project_planning.assign/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>practice.mgmt.two_level_project_planning.assign</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/practice.mgmt.two_level_project_planning.assign/plugin.xmi b/praclib/temp/practice.mgmt.two_level_project_planning.assign/plugin.xmi
new file mode 100644
index 0000000..40f5794
--- /dev/null
+++ b/praclib/temp/practice.mgmt.two_level_project_planning.assign/plugin.xmi
@@ -0,0 +1,82 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_NBRH0Mh3EdygFZkm1d5NtQ"
+ guid="_NBRH0Mh3EdygFZkm1d5NtQ"/>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_NBRHwMh3EdygFZkm1d5NtQ" name="practice.mgmt.two_level_project_planning.assign"
+ guid="_NBRHwMh3EdygFZkm1d5NtQ" changeDate="2008-01-21T18:19:18.218-0500">
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_NBRHwch3EdygFZkm1d5NtQ"
+ name="Content" guid="_NBRHwch3EdygFZkm1d5NtQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_NBRHwsh3EdygFZkm1d5NtQ"
+ name="Categories" guid="_NBRHwsh3EdygFZkm1d5NtQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_NBRHw8h3EdygFZkm1d5NtQ"
+ name="Domains" guid="_NBRHw8h3EdygFZkm1d5NtQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:Domain" xmi:id="_jx3KsMh3EdygFZkm1d5NtQ"
+ name="project_management_domain.assign" guid="_jx3KsMh3EdygFZkm1d5NtQ"
+ variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Domain" href="uma://_MRPloEFXEdy9ENCpSugIjA#_8M6J4K80Edy9cPK11VzBuQ"/>
+ <workProducts xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_0a6vcMlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_NBRHxMh3EdygFZkm1d5NtQ"
+ name="Disciplines" guid="_NBRHxMh3EdygFZkm1d5NtQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:Discipline" xmi:id="_c0d6wMh3EdygFZkm1d5NtQ"
+ name="project_management_discipline.assign" guid="_c0d6wMh3EdygFZkm1d5NtQ"
+ variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Discipline" href="uma://_MRPloEFXEdy9ENCpSugIjA#_iGSHtFZ-EdyIUdvDLLUdeg"/>
+ <tasks href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_0lC70MlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_NBRHxch3EdygFZkm1d5NtQ"
+ name="RoleSets" guid="_NBRHxch3EdygFZkm1d5NtQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_NBRHxsh3EdygFZkm1d5NtQ"
+ name="WP Types" guid="_NBRHxsh3EdygFZkm1d5NtQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_NBRHx8h3EdygFZkm1d5NtQ"
+ name="Tools" guid="_NBRHx8h3EdygFZkm1d5NtQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_NBRHyMh3EdygFZkm1d5NtQ"
+ name="StandardCategories" guid="_NBRHyMh3EdygFZkm1d5NtQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_NBRHych3EdygFZkm1d5NtQ"
+ name="CustomCategories" guid="_NBRHych3EdygFZkm1d5NtQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_NBRHysh3EdygFZkm1d5NtQ"
+ name="Hidden" guid="_NBRHysh3EdygFZkm1d5NtQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_NBRHy8h3EdygFZkm1d5NtQ"
+ name="Custom Categories" guid="_NBRHy8h3EdygFZkm1d5NtQ"/>
+ </childPackages>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_NBRHzMh3EdygFZkm1d5NtQ"
+ name="CoreContent" guid="_NBRHzMh3EdygFZkm1d5NtQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_2Ve24Mh3EdygFZkm1d5NtQ"
+ name="Role Assignments" guid="_2Ve24Mh3EdygFZkm1d5NtQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:Role" xmi:id="_2Ve248h3EdygFZkm1d5NtQ"
+ name="project_manager.assign_wp" guid="_2Ve248h3EdygFZkm1d5NtQ" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Role" href="uma://_A118oMYaEdyXeo04os5BOw#_0a0o0MlgEdmt3adZL5Dmdw"/>
+ <responsibleFor xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_0a6vcMlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_2Ve25Mh3EdygFZkm1d5NtQ"
+ name="plan_the_project.assign_role" guid="_2Ve25Mh3EdygFZkm1d5NtQ" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Task" href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_0lC70MlgEdmt3adZL5Dmdw"/>
+ <performedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0a0o0MlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0VxJsMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0X9iEMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_dTa6gMAYEdqX-s4mWhkyqQ"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0ZM4MclgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_NBRHzch3EdygFZkm1d5NtQ"
+ name="CapabilityPatterns" guid="_NBRHzch3EdygFZkm1d5NtQ"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_NBRHzsh3EdygFZkm1d5NtQ"
+ name="DeliveryProcesses" guid="_NBRHzsh3EdygFZkm1d5NtQ"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_NBRHz8h3EdygFZkm1d5NtQ"
+ name="ProcessContributions" guid="_NBRHz8h3EdygFZkm1d5NtQ"/>
+ <bases href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPloEFXEdy9ENCpSugIjA"/>
+ <bases href="uma://_A118oMYaEdyXeo04os5BOw#_A118oMYaEdyXeo04os5BOw"/>
+ <bases href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS10J6YEdyQN-zRFaRrCQ"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/practice.mgmt.two_level_project_planning.base/.project b/praclib/temp/practice.mgmt.two_level_project_planning.base/.project
new file mode 100644
index 0000000..ef7d60c
--- /dev/null
+++ b/praclib/temp/practice.mgmt.two_level_project_planning.base/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>practice.mgmt.two_level_project_planning.base</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/practice.mgmt.two_level_project_planning.base/customcategories/resources/bookc.gif b/praclib/temp/practice.mgmt.two_level_project_planning.base/customcategories/resources/bookc.gif
new file mode 100644
index 0000000..7f2ab85
--- /dev/null
+++ b/praclib/temp/practice.mgmt.two_level_project_planning.base/customcategories/resources/bookc.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.two_level_project_planning.base/customcategories/resources/bookcL.gif b/praclib/temp/practice.mgmt.two_level_project_planning.base/customcategories/resources/bookcL.gif
new file mode 100644
index 0000000..6c5b064
--- /dev/null
+++ b/praclib/temp/practice.mgmt.two_level_project_planning.base/customcategories/resources/bookcL.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.two_level_project_planning.base/customcategories/resources/compass.gif b/praclib/temp/practice.mgmt.two_level_project_planning.base/customcategories/resources/compass.gif
new file mode 100644
index 0000000..39f306a
--- /dev/null
+++ b/praclib/temp/practice.mgmt.two_level_project_planning.base/customcategories/resources/compass.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.two_level_project_planning.base/customcategories/resources/compassL.gif b/praclib/temp/practice.mgmt.two_level_project_planning.base/customcategories/resources/compassL.gif
new file mode 100644
index 0000000..4117414
--- /dev/null
+++ b/praclib/temp/practice.mgmt.two_level_project_planning.base/customcategories/resources/compassL.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.two_level_project_planning.base/customcategories/resources/pract_dgm32.gif b/praclib/temp/practice.mgmt.two_level_project_planning.base/customcategories/resources/pract_dgm32.gif
new file mode 100644
index 0000000..f597332
--- /dev/null
+++ b/praclib/temp/practice.mgmt.two_level_project_planning.base/customcategories/resources/pract_dgm32.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.two_level_project_planning.base/customcategories/resources/pract_obj.gif b/praclib/temp/practice.mgmt.two_level_project_planning.base/customcategories/resources/pract_obj.gif
new file mode 100644
index 0000000..fe8075a
--- /dev/null
+++ b/praclib/temp/practice.mgmt.two_level_project_planning.base/customcategories/resources/pract_obj.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.two_level_project_planning.base/customcategories/resources/report_dgm32.gif b/praclib/temp/practice.mgmt.two_level_project_planning.base/customcategories/resources/report_dgm32.gif
new file mode 100644
index 0000000..1f86c7e
--- /dev/null
+++ b/praclib/temp/practice.mgmt.two_level_project_planning.base/customcategories/resources/report_dgm32.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.two_level_project_planning.base/customcategories/resources/report_obj.gif b/praclib/temp/practice.mgmt.two_level_project_planning.base/customcategories/resources/report_obj.gif
new file mode 100644
index 0000000..c22c85e
--- /dev/null
+++ b/praclib/temp/practice.mgmt.two_level_project_planning.base/customcategories/resources/report_obj.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.two_level_project_planning.base/customcategories/resources/template_dgm32.gif b/praclib/temp/practice.mgmt.two_level_project_planning.base/customcategories/resources/template_dgm32.gif
new file mode 100644
index 0000000..8fab4e8
--- /dev/null
+++ b/praclib/temp/practice.mgmt.two_level_project_planning.base/customcategories/resources/template_dgm32.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.two_level_project_planning.base/customcategories/resources/template_obj.gif b/praclib/temp/practice.mgmt.two_level_project_planning.base/customcategories/resources/template_obj.gif
new file mode 100644
index 0000000..ca5f822
--- /dev/null
+++ b/praclib/temp/practice.mgmt.two_level_project_planning.base/customcategories/resources/template_obj.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.two_level_project_planning.base/customcategories/two_level_project_planning_practice.xmi b/praclib/temp/practice.mgmt.two_level_project_planning.base/customcategories/two_level_project_planning_practice.xmi
new file mode 100644
index 0000000..544671d
--- /dev/null
+++ b/praclib/temp/practice.mgmt.two_level_project_planning.base/customcategories/two_level_project_planning_practice.xmi
@@ -0,0 +1,61 @@
+<?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: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="-X4AinwJCvgga0QAU9sI9Ng"
+ name="two_level_project_planning_practice,_LhuNEJ-lEdyBk-WQzMU-FQ" guid="-X4AinwJCvgga0QAU9sI9Ng"
+ changeDate="2008-02-24T14:59:08.234-0500">
+ <mainDescription><p>
+ The&nbsp;Two-Level Project Planning&nbsp;practice&nbsp; [***.......TO BE COMPLETED ***]
+</p>
+<h3>
+ The Essence of Two-Level Project Planning
+</h3>
+<p>
+ The following capture the key principles of Two-Level Project Planning:
+</p>
+<ul>
+ <li>
+ <strong>Plan the entire project at a very high level.</strong>
+ </li>
+ <li>
+ <strong>Plan&nbsp;low-level details&nbsp;just-in-time before a planned increment or iteration is about to
+ start.</strong>
+ </li>
+</ul>
+<h3>
+ <br />
+ Why Adopt this Practice?
+</h3>
+<p>
+ [*** Include some content here that describes the business value of this practice -- what do you get when you adopt
+ it?&nbsp; This section is essentially the value proposition for the practice.&nbsp; You may want to describe some
+ common problems and how this practice solves those problems.&nbsp; &nbsp;***]&nbsp;&nbsp;&nbsp;
+</p>
+<h3>
+ How to Read this Practice
+</h3>
+<p>
+ The best way to read this practice is to first familiarize yourself with its overall structure -- what it is in it and
+ how it is organized.&nbsp;
+</p>
+<p>
+ [*** To be completed.... ***]
+</p>
+<p>
+ For step-by-step instructions on how to adopt this practice, see <a class="elementLink"
+ href="./../../practice.mgmt.two_level_project_planning.base/guidances/roadmaps/how_to_adopt_520D7115.html"
+ guid="_ihr3sOMPEdyM47cGD2jiaQ">How to Adopt This Practice</a>.
+</p>
+<h3>
+ Additional Resources
+</h3>
+<p>
+ For more information on the whole team approach, see the following:
+</p>
+<ul>
+ <li>
+ [*** Add more, as needed ***]<br />
+ </li>
+</ul></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/checklists/project_plan.xmi b/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/checklists/project_plan.xmi
new file mode 100644
index 0000000..d98b19e
--- /dev/null
+++ b/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/checklists/project_plan.xmi
@@ -0,0 +1,46 @@
+<?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: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="-iMEYJ2Jbm9S8GihBKFOaFA"
+ name="new_checklist,_-qtjsAasEdy1uLAzgK8btg" guid="-iMEYJ2Jbm9S8GihBKFOaFA">
+ <sections xmi:id="_J4SxQAa_Edy1uLAzgK8btg" name="Has the plan been elaborated with the team?"
+ guid="_J4SxQAa_Edy1uLAzgK8btg">
+ <sectionDescription><p>
+ Project planning should not be done in isolation and every member of the team should be involved.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_Ln-rYAatEdy1uLAzgK8btg" name="Has the team agreed on development practices for the project?"
+ guid="_Ln-rYAatEdy1uLAzgK8btg">
+ <sectionDescription><p>
+ Who plays which roles?
+</p>
+<p>
+ How long will the iterations be?
+</p>
+<p>
+ What coding standards should be followed?&nbsp;
+</p>
+<p>
+ Has the project directory structure been identified?
+</p>
+<p>
+ What development, build and test&nbsp;tools&nbsp;should be&nbsp;used?
+</p>
+<p>
+ What measures and metrics will be used to track progress?
+</p><br /></sectionDescription>
+ </sections>
+ <sections xmi:id="_MdRUoAatEdy1uLAzgK8btg" name="Have the project milestones been defined?"
+ guid="_MdRUoAatEdy1uLAzgK8btg">
+ <sectionDescription><p>
+ What are the major milestones for each release?
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_T2-tIAatEdy1uLAzgK8btg" name="Has the deployment strategy been discussed?"
+ guid="_T2-tIAatEdy1uLAzgK8btg">
+ <sectionDescription><p>
+ How will the product be delivered to the customer?
+</p></sectionDescription>
+ </sections>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/concepts/resources/co_phas1.gif b/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/concepts/resources/co_phas1.gif
new file mode 100644
index 0000000..919e282
--- /dev/null
+++ b/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/concepts/resources/co_phas1.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/concepts/resources/concept_dgm32.gif b/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/concepts/resources/concept_dgm32.gif
new file mode 100644
index 0000000..fa195bd
--- /dev/null
+++ b/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/concepts/resources/concept_dgm32.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/concepts/resources/concept_obj.gif b/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/concepts/resources/concept_obj.gif
new file mode 100644
index 0000000..03af38b
--- /dev/null
+++ b/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/concepts/resources/concept_obj.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/concepts/resources/project_lifecycle.jpg b/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/concepts/resources/project_lifecycle.jpg
new file mode 100644
index 0000000..7d90779
--- /dev/null
+++ b/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/concepts/resources/project_lifecycle.jpg
Binary files differ
diff --git a/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/examples/resources/project_plan.doc b/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/examples/resources/project_plan.doc
new file mode 100644
index 0000000..5b4a2f6
--- /dev/null
+++ b/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/examples/resources/project_plan.doc
Binary files differ
diff --git a/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/guidelines/staffing_project.xmi b/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/guidelines/staffing_project.xmi
new file mode 100644
index 0000000..708883b
--- /dev/null
+++ b/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/guidelines/staffing_project.xmi
@@ -0,0 +1,67 @@
+<?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: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="-HYO1lwAFOxlT7ncq8EjSng"
+ name="new_guideline,_Jq64EJjsEduad8I_c-ogIA" guid="-HYO1lwAFOxlT7ncq8EjSng" changeDate="2007-01-31T13:46:21.802-0500"
+ version="1.0.0">
+ <mainDescription><p>
+ Good software development teams are made up of a collection of people who collaborate effectively. How the project team
+ is staffed, by either adding or removing people, will greatly impact the team's productivity.
+</p>
+<p>
+ When staffing a development project, consider the following advice:
+</p>
+<ol>
+ <li>
+ Include people who fit into the existing team culture. Good teams don't just appear magically one day, but instead
+ are grown and nurtured over time. Invite people onto the team who will add value and furthermore who will not be
+ disruptive. Similarly, you may need to invite someone to leave the team if they do not fit well with the existing
+ team and they don't seem to be able to change.
+ </li>
+ <li>
+ People should want to be on the team. People are far more productive when they're working on a project that they
+ believe in and want to see succeed.
+ </li>
+ <li>
+ Build your team with "generalizing specialists". A generalizing specialist is someone with one or more technical
+ specialties who actively seeks to gain new skills in both their existing specialties as well as in other areas,
+ including both technical and domain areas. Generalizing specialists add value to the team because they have
+ specialized skills that you need while at the same time appreciate the full range of issues that a general
+ understanding of the software development process and the business domain offers.
+ </li>
+ <li>
+ Include stakeholders. Stakeholders, including business stakeholders such as end users and technical stakeholders
+ such as operations staff, can add significant value to your team. Instead of just interviewing them to gain
+ information from them, or asking them to review your work, why not include them as active participants on the team?
+ </li>
+ <li>
+ Include specialists for short-term, specialized work. Specialists can still add value on an agile development team,
+ particularly when they have specific skills and experience which existing team members do not have. It can often be
+ more effective to bring a specialist into the team for a short period of time to help with a specific task, such as
+ installation and setup of an application server, the development of an architectural spike, or simply taking part
+ in a review.
+ </li>
+ <li>
+ Give people opportunities to evolve their skills. At the beginning of a project the team may not have the full
+ range of skills that it needs, or perhaps a few individuals may not have the skills required to fulfill the roles
+ they are filling. This is a very common risk taken on by the majority of project teams for the simple reasons that
+ you often can't find the perfect combination of people and even if you could you still want to provide people with
+ opportunities to grow as professionals.
+ </li>
+ <li>
+ Remember Brook's Law. Adding people to a late project will only make it later [<a
+ href="./../../../core.mgmt.common.base/guidances/supportingmaterials/mgmt_references_D80619F3.html#BRO95"
+ guid="_JlTPUM6aEdyuBO4ZIzcyig">BRO95</a>]. The corollary is that removing people from a late project may speed
+ things up [<a href="./../../../core.tech.common.base/guidances/supportingmaterials/tech_references_6CCF393.html"
+ guid="_9ToeIB83Edqsvps02rpOOg">AMB04</a>].
+ </li>
+</ol>
+<p>
+ Sometimes you will need to go against some of this advice due to environmental constraints. Perhaps only specialists
+ are available (although there's nothing stopping a specialist from becoming a generalizing specialist), perhaps there
+ aren't as many opportunities for people to try new things as they would like, or perhaps the stakeholders aren't
+ available to be active members of the team. The advice above is designed to lead to as high-performing a team as
+ possible, but even partial adherence to this guideline will improve the team.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/reports/resources/ex_project_burndown.xls b/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/reports/resources/ex_project_burndown.xls
new file mode 100644
index 0000000..e63fef8
--- /dev/null
+++ b/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/reports/resources/ex_project_burndown.xls
Binary files differ
diff --git a/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/roadmaps/how_to_adopt.xmi b/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/roadmaps/how_to_adopt.xmi
new file mode 100644
index 0000000..0ca01d8
--- /dev/null
+++ b/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/roadmaps/how_to_adopt.xmi
@@ -0,0 +1,21 @@
+<?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: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="-4a1QxeLdn2OKx5_Lft8tBA"
+ name="how_to_adopt,_ERIDQOMPEdyM47cGD2jiaQ" guid="-4a1QxeLdn2OKx5_Lft8tBA" changeDate="2008-02-17T08:09:46.937-0500"
+ version="7.2.0">
+ <mainDescription><h3>
+ Getting Started&nbsp;
+</h3>
+<p>
+ TODO:&nbsp; Describe how to 'read' this practice.......provide description with links to appropriate content to help
+ someone get started with this practice
+</p>
+<h3>
+ Common Pitfalls
+</h3>
+<p>
+ TBD
+</p><br /></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/supportingmaterials/release_info_two_level_project_planning.xmi b/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/supportingmaterials/release_info_two_level_project_planning.xmi
new file mode 100644
index 0000000..60b6e68
--- /dev/null
+++ b/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/supportingmaterials/release_info_two_level_project_planning.xmi
@@ -0,0 +1,23 @@
+<?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="-FMA7pB1MClBDXVA8-A8D2A"
+ name="release_info_two_level_project_planning,_SP6Y4MN_Edy3nv0ZK8D4GQ" guid="-FMA7pB1MClBDXVA8-A8D2A"
+ changeDate="2008-01-15T10:29:47.765-0500">
+ <mainDescription><h3>
+ Two-Level Project Planning&nbsp;Practice
+</h3>
+<p>
+ Version 1.0
+</p>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p>
+ [*** NOT YET RELEASED ***]
+ </p>
+ <p>
+ This is the initial release of this practice.
+ </p><br />
+ <br />
+</blockquote><br /></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/supportingmaterials/resources/openup-basic_lifecycle.jpg b/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/supportingmaterials/resources/openup-basic_lifecycle.jpg
new file mode 100644
index 0000000..4719cad
--- /dev/null
+++ b/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/supportingmaterials/resources/openup-basic_lifecycle.jpg
Binary files differ
diff --git a/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/templates/resources/project_plan_tpl.dot b/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/templates/resources/project_plan_tpl.dot
new file mode 100644
index 0000000..ad2d41a
--- /dev/null
+++ b/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/templates/resources/project_plan_tpl.dot
Binary files differ
diff --git a/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/termdefinitions/project_burndown.xmi b/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/termdefinitions/project_burndown.xmi
new file mode 100644
index 0000000..f02c831
--- /dev/null
+++ b/praclib/temp/practice.mgmt.two_level_project_planning.base/guidances/termdefinitions/project_burndown.xmi
@@ -0,0 +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.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="-NNByAM5YsjCu39flaOSZtQ"
+ name=",_eX0YsEvvEdunZcj9T5hrMQ" guid="-NNByAM5YsjCu39flaOSZtQ" changeDate="2006-09-24T11:09:54.521-0700">
+ <mainDescription>A chart consisting of two perspectives, the horizontal axis showing the iterations and the vertical axis indicating the
+remaining points from the work items list.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.two_level_project_planning.base/plugin.xmi b/praclib/temp/practice.mgmt.two_level_project_planning.base/plugin.xmi
new file mode 100644
index 0000000..4285d92
--- /dev/null
+++ b/praclib/temp/practice.mgmt.two_level_project_planning.base/plugin.xmi
@@ -0,0 +1,197 @@
+<?xml version="1.0" encoding="UTF-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.4/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.2.0" xmlns:epf="http://www.eclipse.org/epf"
+ epf:version="1.2.0">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_nKb_wJ6YEdyQN-zRFaRrCQ"
+ guid="_nKb_wJ6YEdyQN-zRFaRrCQ">
+ <resourceDescriptors xmi:id="_nDXLkPL5Edm6Nvont3uinw" id="_IbVp8KX4EdmvhNXG0Oc2uA"
+ uri="workproducts/project_plan.xmi"/>
+ <resourceDescriptors xmi:id="_Kp55kAatEdy1uLAzgK8btg" id="-iMEYJ2Jbm9S8GihBKFOaFA"
+ uri="guidances/checklists/project_plan.xmi"/>
+ <resourceDescriptors xmi:id="_gdtuMUvvEdunZcj9T5hrMQ" id="-NNByAM5YsjCu39flaOSZtQ"
+ uri="guidances/termdefinitions/project_burndown.xmi"/>
+ <resourceDescriptors xmi:id="_nGh0UfL5Edm6Nvont3uinw" id="_fPbdIKe2Edmzde8VFK5bxg"
+ uri="tasks/plan_the_project.xmi"/>
+ <resourceDescriptors xmi:id="_SRaNscN_Edy3nv0ZK8D4GQ" id="-FMA7pB1MClBDXVA8-A8D2A"
+ uri="guidances/supportingmaterials/release_info_two_level_project_planning.xmi"/>
+ <resourceDescriptors xmi:id="_jrhTMJjsEduad8I_c-ogIA" id="-HYO1lwAFOxlT7ncq8EjSng"
+ uri="guidances/guidelines/staffing_project.xmi"/>
+ <resourceDescriptors xmi:id="_VpgtsOGWEdyhmsbt0Xyl8A" id="-qsk_KkHMnoS0PIISuCiTrA"
+ uri="workproducts/project_risk_slot.assign.xmi"/>
+ <resourceDescriptors xmi:id="_ijU2ceMPEdyM47cGD2jiaQ" id="-4a1QxeLdn2OKx5_Lft8tBA"
+ uri="guidances/roadmaps/how_to_adopt.xmi"/>
+ <resourceDescriptors xmi:id="_-XincOMTEdyM47cGD2jiaQ" id="-X4AinwJCvgga0QAU9sI9Ng"
+ uri="customcategories/two_level_project_planning_practice.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_nKS10J6YEdyQN-zRFaRrCQ" name="practice.mgmt.two_level_project_planning.base"
+ guid="_nKS10J6YEdyQN-zRFaRrCQ" changeDate="2008-02-22T12:29:17.359-0500">
+ <copyrightStatement href="uma://_iVydgENdEdy245g62lfWcA#_cTs20KzREduOqvpk_MDLfQ"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_nKS10Z6YEdyQN-zRFaRrCQ"
+ name="Content" guid="_nKS10Z6YEdyQN-zRFaRrCQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_nKS10p6YEdyQN-zRFaRrCQ"
+ name="Categories" guid="_nKS10p6YEdyQN-zRFaRrCQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_nKS1056YEdyQN-zRFaRrCQ"
+ name="Domains" guid="_nKS1056YEdyQN-zRFaRrCQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_nKS11J6YEdyQN-zRFaRrCQ"
+ name="Disciplines" guid="_nKS11J6YEdyQN-zRFaRrCQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_nKS11Z6YEdyQN-zRFaRrCQ"
+ name="RoleSets" guid="_nKS11Z6YEdyQN-zRFaRrCQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_nKS11p6YEdyQN-zRFaRrCQ"
+ name="WP Types" guid="_nKS11p6YEdyQN-zRFaRrCQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_nKS1156YEdyQN-zRFaRrCQ"
+ name="Tools" guid="_nKS1156YEdyQN-zRFaRrCQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_nKS12J6YEdyQN-zRFaRrCQ"
+ name="StandardCategories" guid="_nKS12J6YEdyQN-zRFaRrCQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_nKS12Z6YEdyQN-zRFaRrCQ"
+ name="CustomCategories" guid="_nKS12Z6YEdyQN-zRFaRrCQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_nKS12p6YEdyQN-zRFaRrCQ"
+ name="Hidden" guid="_nKS12p6YEdyQN-zRFaRrCQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_nKS1256YEdyQN-zRFaRrCQ"
+ name="Custom Categories" guid="_nKS1256YEdyQN-zRFaRrCQ" categorizedElements="_LhuNEJ-lEdyBk-WQzMU-FQ _XLU2EMh5EdygFZkm1d5NtQ"/>
+ </childPackages>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_LhuNEJ-lEdyBk-WQzMU-FQ"
+ name="two_level_project_planning_practice" guid="_LhuNEJ-lEdyBk-WQzMU-FQ"
+ briefDescription="This practice plans the project at two levels: first at a high level and then at a more detailed level for the most immediate project iteration."
+ presentationName="Two-Level Project Planning" shapeicon="customcategories/resources/pract_dgm32.gif"
+ nodeicon="customcategories/resources/pract_obj.gif" categorizedElements="_ihr3sOMPEdyM47cGD2jiaQ _0lC70MlgEdmt3adZL5Dmdw _0a6vcMlgEdmt3adZL5Dmdw _KsCT4J_1EdyBk-WQzMU-FQ">
+ <presentation xmi:id="-X4AinwJCvgga0QAU9sI9Ng" href="uma://-X4AinwJCvgga0QAU9sI9Ng#-X4AinwJCvgga0QAU9sI9Ng"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_KsCT4J_1EdyBk-WQzMU-FQ"
+ name="guidance" guid="_KsCT4J_1EdyBk-WQzMU-FQ" presentationName="Guidance"
+ shapeicon="customcategories/resources/bookcL.gif" nodeicon="customcategories/resources/bookc.gif">
+ <methodElementProperty xmi:id="_IR1s4J_2EdyBk-WQzMU-FQ" name="CategoryElementsSortType"
+ value="MethodType"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0mYYkMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="#_Jq64EJjsEduad8I_c-ogIA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Checklist" href="#_-qtjsAasEdy1uLAzgK8btg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_XLU2EMh5EdygFZkm1d5NtQ"
+ name="contributions_to_nav_building_blocks" guid="_XLU2EMh5EdygFZkm1d5NtQ"
+ presentationName="Contributions to Navigation Building Blocks" categorizedElements="_WirFMMh6EdygFZkm1d5NtQ _fW-zcMh6EdygFZkm1d5NtQ _oy7Jcch6EdygFZkm1d5NtQ _oW_7EMh9EdygFZkm1d5NtQ _gxU5sNQvEdyM_J8-fv54DA _cWtJcNnKEdyzZqGyZ7hwdw _9g4CAOMPEdyM47cGD2jiaQ"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_WirFMMh6EdygFZkm1d5NtQ"
+ name="release_info.assign" guid="_WirFMMh6EdygFZkm1d5NtQ" variabilityType="contributes"
+ categorizedElements="_SP6Y4MN_Edy3nv0ZK8D4GQ">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCIHYcRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_fW-zcMh6EdygFZkm1d5NtQ"
+ name="checklist_list.assign" guid="_fW-zcMh6EdygFZkm1d5NtQ" variabilityType="contributes"
+ categorizedElements="_-qtjsAasEdy1uLAzgK8btg">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_pGt9MMReEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_oy7Jcch6EdygFZkm1d5NtQ"
+ name="artifact_list.assign" guid="_oy7Jcch6EdygFZkm1d5NtQ" variabilityType="contributes"
+ categorizedElements="_0a6vcMlgEdmt3adZL5Dmdw">
+ <methodElementProperty xmi:id="_pAMJYMh6EdygFZkm1d5NtQ" name="CategoryElementsSortType"
+ value="Manual"/>
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4YMRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_oW_7EMh9EdygFZkm1d5NtQ"
+ name="practice_list.assign" guid="_oW_7EMh9EdygFZkm1d5NtQ" variabilityType="contributes"
+ categorizedElements="_LhuNEJ-lEdyBk-WQzMU-FQ">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCIHY8RdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_gxU5sNQvEdyM_J8-fv54DA"
+ name="management_practice_list.assign" guid="_gxU5sNQvEdyM_J8-fv54DA"
+ variabilityType="contributes" categorizedElements="_LhuNEJ-lEdyBk-WQzMU-FQ">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_auUD0NQuEdyM_J8-fv54DA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_cWtJcNnKEdyzZqGyZ7hwdw"
+ name="guideline_list.assign" guid="_cWtJcNnKEdyzZqGyZ7hwdw" variabilityType="contributes"
+ categorizedElements="_Jq64EJjsEduad8I_c-ogIA">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4ZcRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_9g4CAOMPEdyM47cGD2jiaQ"
+ name="roadmap_list.assign" guid="_9g4CAOMPEdyM47cGD2jiaQ" variabilityType="contributes"
+ categorizedElements="_ihr3sOMPEdyM47cGD2jiaQ">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4ZsRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_nKS13J6YEdyQN-zRFaRrCQ"
+ name="CoreContent" guid="_nKS13J6YEdyQN-zRFaRrCQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_hLcgcJ9WEdy3Nc4rvuj7bA"
+ name="Two-Level Project Planning" guid="_hLcgcJ9WEdy3Nc4rvuj7bA">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_q8sJwMOBEdy3nv0ZK8D4GQ"
+ name="Release Info" guid="_q8sJwMOBEdy3nv0ZK8D4GQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="_SP6Y4MN_Edy3nv0ZK8D4GQ"
+ name="release_info_two_level_project_planning" guid="_SP6Y4MN_Edy3nv0ZK8D4GQ"
+ presentationName="Two-Level Project Planning Practice">
+ <presentation xmi:id="-FMA7pB1MClBDXVA8-A8D2A" href="uma://-FMA7pB1MClBDXVA8-A8D2A#-FMA7pB1MClBDXVA8-A8D2A"/>
+ </contentElements>
+ </childPackages>
+ <contentElements xsi:type="org.eclipse.epf.uma:Checklist" xmi:id="_-qtjsAasEdy1uLAzgK8btg"
+ name="project_plan" guid="_-qtjsAasEdy1uLAzgK8btg" briefDescription="This check list provides questions to verify that the project plan ise created in a consistent manner."
+ presentationName="Project Plan">
+ <presentation xmi:id="-iMEYJ2Jbm9S8GihBKFOaFA" href="uma://-iMEYJ2Jbm9S8GihBKFOaFA#-iMEYJ2Jbm9S8GihBKFOaFA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_0lC70MlgEdmt3adZL5Dmdw"
+ name="plan_the_project" guid="_0lC70MlgEdmt3adZL5Dmdw" briefDescription="A collaborative task that outlines an initial agreement on how the project will deliver the product vision. The resulting project plan provides a summary-level overview of the project. [*** Need to use terminology that is more generic than 'product vision' ***]"
+ presentationName="Plan Project" output="_0a6vcMlgEdmt3adZL5Dmdw">
+ <presentation xmi:id="_fPbdIKe2Edmzde8VFK5bxg" href="uma://_fPbdIKe2Edmzde8VFK5bxg#_fPbdIKe2Edmzde8VFK5bxg"/>
+ <conceptsAndPapers href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_lam4ADkBEduxovfWMDsntw"/>
+ <conceptsAndPapers href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0bsLgMlgEdmt3adZL5Dmdw"/>
+ <guidelines href="#_Jq64EJjsEduad8I_c-ogIA"/>
+ <guidelines href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_CGHskBEdEdqY7JB6N6CW2w"/>
+ <guidelines href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_VNxL4ACsEdu8m4dIntu6jA"/>
+ <guidelines href="uma://_vJYucEfUEdyiPI8btkmvmw#_sLQ6AN8-Edyhmsbt0Xyl8A"/>
+ <mandatoryInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_i3vkoLS-EduDY8LNbMCDBA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_eX0YsEvvEdunZcj9T5hrMQ"
+ name="project_burndown" guid="_eX0YsEvvEdunZcj9T5hrMQ" presentationName="project burndown ">
+ <presentation xmi:id="-NNByAM5YsjCu39flaOSZtQ" href="uma://-NNByAM5YsjCu39flaOSZtQ#-NNByAM5YsjCu39flaOSZtQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_hGZcsNaeEdyqVc_mrD0bfw"
+ name="project_definition_slot.assign" guid="_hGZcsNaeEdyqVc_mrD0bfw"
+ variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_vJYucEfUEdyiPI8btkmvmw#_RJMUcNpUEdyzZqGyZ7hwdw"/>
+ <containedArtifacts xmi:id="_0a6vcMlgEdmt3adZL5Dmdw" name="project_plan"
+ guid="_0a6vcMlgEdmt3adZL5Dmdw" briefDescription="This artifact gathers all information required to manage the project. Its main part consists of a coarse-grained plan, containing project phases and milestones."
+ presentationName="Project Plan">
+ <presentation xmi:id="_IbVp8KX4EdmvhNXG0Oc2uA" href="uma://_IbVp8KX4EdmvhNXG0Oc2uA#_IbVp8KX4EdmvhNXG0Oc2uA"/>
+ </containedArtifacts>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_Jq64EJjsEduad8I_c-ogIA"
+ name="staffing_project" guid="_Jq64EJjsEduad8I_c-ogIA" briefDescription="Advice for how to staff a software development project."
+ presentationName="Staffing a Project">
+ <presentation xmi:id="-HYO1lwAFOxlT7ncq8EjSng" href="uma://-HYO1lwAFOxlT7ncq8EjSng#-HYO1lwAFOxlT7ncq8EjSng"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_mpOp4OFkEdyhmsbt0Xyl8A"
+ name="project_risk_slot.assign" guid="_mpOp4OFkEdyhmsbt0Xyl8A" variabilityType="contributes">
+ <presentation xmi:id="-qsk_KkHMnoS0PIISuCiTrA" href="uma://-qsk_KkHMnoS0PIISuCiTrA#-qsk_KkHMnoS0PIISuCiTrA"/>
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_vJYucEfUEdyiPI8btkmvmw#_0TkXgNpUEdyzZqGyZ7hwdw"/>
+ <containedArtifacts xmi:id="_DYXSYOFmEdyhmsbt0Xyl8A" name="risk_list.assign"
+ guid="_DYXSYOFmEdyhmsbt0Xyl8A" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_Ckay8Cc_EduIsqH1Q6ZuqA"/>
+ </containedArtifacts>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Roadmap" xmi:id="_ihr3sOMPEdyM47cGD2jiaQ"
+ name="how_to_adopt" guid="_ihr3sOMPEdyM47cGD2jiaQ" briefDescription="This roadmap describes how to adopt the Two-Level Project Planning Practice."
+ presentationName="How to Adopt This Practice">
+ <presentation xmi:id="-4a1QxeLdn2OKx5_Lft8tBA" href="uma://-4a1QxeLdn2OKx5_Lft8tBA#-4a1QxeLdn2OKx5_Lft8tBA"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_nKS13Z6YEdyQN-zRFaRrCQ"
+ name="CapabilityPatterns" guid="_nKS13Z6YEdyQN-zRFaRrCQ"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_nKS13p6YEdyQN-zRFaRrCQ"
+ name="DeliveryProcesses" guid="_nKS13p6YEdyQN-zRFaRrCQ"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_nKS1356YEdyQN-zRFaRrCQ"
+ name="ProcessContributions" guid="_nKS1356YEdyQN-zRFaRrCQ"/>
+ <bases href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYucEfUEdyiPI8btkmvmw"/>
+ <bases href="uma://_iVydgENdEdy245g62lfWcA#_iVydgENdEdy245g62lfWcA"/>
+ <bases href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0ELXuEduGP_98XMd0fg"/>
+ <bases href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0TmecJ-VEdy3Nc4rvuj7bA"/>
+ <bases href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno4EKmEdyrauqpmnA8jQ"/>
+ <bases href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzAJ6WEdyQN-zRFaRrCQ"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/practice.mgmt.two_level_project_planning.base/tasks/plan_the_project.xmi b/praclib/temp/practice.mgmt.two_level_project_planning.base/tasks/plan_the_project.xmi
new file mode 100644
index 0000000..ca30a5c
--- /dev/null
+++ b/praclib/temp/practice.mgmt.two_level_project_planning.base/tasks/plan_the_project.xmi
@@ -0,0 +1,122 @@
+<?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.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="_fPbdIKe2Edmzde8VFK5bxg"
+ name="plan_the_project,_0lC70MlgEdmt3adZL5Dmdw" guid="_fPbdIKe2Edmzde8VFK5bxg"
+ changeDate="2008-02-22T00:56:40.578-0500" version="1.0.0">
+ <mainDescription>Developing the project plan provides an opportunity for the team to agree on project scope, objectives, initial timeframe,
+
+and deliverables. It allows the team to begin demonstrating self-organization by defining success criteria and work
+
+practices to be used. Collaboration and consensus by all key project participants is the goal, but the project manager has
+
+ultimate responsibility for ensuring that everybody is committed to the plan.</mainDescription>
+ <keyConsiderations><p>
+
+ Gain agreement with stakeholders and the rest of the project team regarding the order of objectives and the duration of
+
+ the project and make adjustments as&nbsp;necessary.
+
+</p></keyConsiderations>
+ <sections xmi:id="_gu-PgIyBEdyhZb-MhCJrlA" name="Establish a cohesive team" guid="_gu-PgIyBEdyhZb-MhCJrlA">
+ <sectionDescription>Project planning, even at the summary level, should not be done in isolation since it outlines what the project will
+deliver and how. The team starts by discussing who plays which roles and agrees on their responsibilities. The project
+manager needs to make sure that staffing is made in accordance with the project's interests and that every necessary role
+is covered.</sectionDescription>
+ </sections>
+ <sections xmi:id="_jknm8IyBEdyhZb-MhCJrlA" name="Determine project size and scope"
+ guid="_jknm8IyBEdyhZb-MhCJrlA">
+ <sectionDescription><p>
+ The&nbsp;team produces rough size estimates for each item&nbsp;in the <a class="elementLink"
+ href="./../../core.mgmt.slot.base/workproducts/project_work_slot_F12BAC46.html" guid="_1QZI8EfUEdyiPI8btkmvmw">[Project
+ Work]</a>&nbsp;(see <a class="elementLinkWithType"
+ href="./../../core.mgmt.common.base/guidances/guidelines/agile_estimation_A4EF42B3.html"
+ guid="_CGHskBEdEdqY7JB6N6CW2w">Guideline: Agile Estimation</a>).&nbsp;
+</p>
+<p>
+ Discussions are held with the stakeholders to determine what is realistic to develop within the constraints of the
+ project.&nbsp; Stakeholder priorities and estimates from the team are used to guide these discussions.
+</p>
+<p>
+ If the project is feature-driven, the team looks at how many people they would need to complete these work items, which
+ gives them a high level understanding of project duration, staffing profile, and scope.&nbsp;If the project instead is
+ date-driven, the team assesses how much work can roughly be done in the time-frame given and using the available team.
+ Out-of-scope work can be considered in future releases.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_lrYj0MBAEdqSgKaj2SZBmg" name="Evaluate risks" guid="_lrYj0MBAEdqSgKaj2SZBmg">
+ <sectionDescription><p>
+ The team identifies project risks, performs a qualitative risk analysis to assess their order of magnitude, and updates
+ the <a class="elementLink" href="./../../core.mgmt.common.base/workproducts/risk_list_C4B6F290.html"
+ guid="_Ckay8Cc_EduIsqH1Q6ZuqA">Risk List</a>. The project manager facilitates the team decision about which risks they
+ should respond to, and which risks they should watch for.
+</p>
+<p>
+ Responses may include avoiding or mitigating risks, exploring opportunities or increasing the probability and positive
+ impacts of the risk. Depending on the case, work items may have to be added or removed from the <a class="elementLink"
+ href="./../../core.mgmt.slot.base/workproducts/project_work_slot_F12BAC46.html" guid="_1QZI8EfUEdyiPI8btkmvmw">[Project
+ Work]</a> to make sure that responses will be prioritized and handled by the team along with other project work. As it
+ is not feasible to plan responses for all risks identified, the team can decide to accept some of them. Risks to watch
+ will be communicated to stakeholders and remain on the Risk List.&nbsp; Actions will be determined only if they occur.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_4Xg3QOFpEdyhmsbt0Xyl8A" name="Outline milestones and iterations"
+ guid="_4Xg3QOFpEdyhmsbt0Xyl8A">
+ <sectionDescription><p>
+ <strong>[*** This is a new step.&nbsp; It is added because the 2nd paragraph of the prior 'Outline project lifecycle'
+ step&nbsp;needs to be contributed as a follow-on step from risk-value lifecycle.&nbsp; The 1st and 3rd paragraphs of
+ the original Outline project lifecycle step are appropraite here.&nbsp;&nbsp; NOTE:&nbsp; This content introduces a
+ dependency of this practice on Iterative Development.&nbsp;&nbsp;***]</strong>
+</p>
+<p>
+ Define the iteration length and use it to assess target velocity (see <a class="elementLinkWithType"
+ href="./../../core.mgmt.common.base/guidances/guidelines/agile_estimation_A4EF42B3.html"
+ guid="_CGHskBEdEdqY7JB6N6CW2w">Guideline: Agile Estimation</a>). The number of items to be delivered in each iteration
+ will be set by the velocity of the team and the estimates for each item. The team uses the Work Items List to outline
+ what features to implement in what iteration, putting top priority work items first, including planned responses to the
+ higher risks or opportunities.
+</p>
+<p>
+ You don't need to spend too much time in doing this planning. The Project plan should document only&nbsp;a brief
+ summary of&nbsp; project milestones&nbsp;and 1-3 objectives for each iteration. Do not commit individual work items to
+ the plan, since this will force too much re-planning. The goal is just to create a high-level plan outlining
+ how&nbsp;the team&nbsp;can build the resulting application in the given set of iterations. Extra level of detail will
+ be achieved in other planning sessions throughout the project (see <a class="elementLinkWithType"
+ href="./../../practice.mgmt.iterative_dev.base/tasks/plan_iteration_957C90DC.html" guid="_0keUEMlgEdmt3adZL5Dmdw">Task:
+ Plan Iteration</a>). You may need to revisit&nbsp;this plan&nbsp;later to adapt it based on what you will
+ learn&nbsp;by&nbsp;running&nbsp;the iterations (see <a class="elementLinkWithType"
+ href="./../../practice.mgmt.iterative_dev.base/workproducts/iteration_plan_B46FED39.html"
+ guid="_0aQBEslgEdmt3adZL5Dmdw">Artifact: Iteration Plan</a>&nbsp;from previous iterations).
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_xWBhUIyBEdyhZb-MhCJrlA" name="Establish costs and articulate value"
+ guid="_xWBhUIyBEdyhZb-MhCJrlA">
+ <sectionDescription><p>
+ Develop a rough order of magnitude estimate for the costs of resources needed to complete project work items.&nbsp; A
+ simplified project costing model&nbsp;can be&nbsp;applied by&nbsp;multiplying the approximate cost per person for the
+ entire team by the length of an iteration to derive ongoing financial impact (i.e., cost per iteration). This first
+ round of planning should keep things very rough and flexible. The goal is just to articulate value against the budget
+ constraints of the project and help stakeholders to decide whether it's worth moving forward with the project or not.
+ If necessary propose options to decrease costs, such as removing from the scope low value and high cost work items.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_zeN84IyBEdyhZb-MhCJrlA" name="Plan deployment" guid="_zeN84IyBEdyhZb-MhCJrlA">
+ <sectionDescription><p>
+ <strong>[*** Reword this to indicate that Project Work may be impacted, but don't show that being done here...it is the
+ task of iterative development (plan and manage iteration) to do that. ***]</strong>
+</p>
+<p>
+ Plan the strategy for deploying the software (and its updates) into the production environment. Discuss release
+ timeframe with the operations and support departments to ensure that your project fits into your overall corporate
+ deployment system. If you are replacing an existing system, decide whether you will run the new system in parallel with
+ it or you will perform a cutover. You may also have to negotiate with the owners of the systems that the new system has
+ dependencies on. Update the <a class="elementLink"
+ href="./../../core.mgmt.slot.base/workproducts/project_work_slot_F12BAC46.html" guid="_1QZI8EfUEdyiPI8btkmvmw">[Project
+ Work]</a>&nbsp;with additional work that may be needed for deployment. Add significant deployment risks to the Risk
+ List and, if necessary, make adjustments to the Project Plan.
+</p></sectionDescription>
+ </sections>
+ <purpose>Get stakeholder buy-in for starting the project and team commitment to move forward with it. This plan can be updated a the
+project progresses based on feedback and changes in the environment.</purpose>
+</org.eclipse.epf.uma:TaskDescription>
diff --git a/praclib/temp/practice.mgmt.two_level_project_planning.base/workproducts/project_plan.xmi b/praclib/temp/practice.mgmt.two_level_project_planning.base/workproducts/project_plan.xmi
new file mode 100644
index 0000000..a2fb85a
--- /dev/null
+++ b/praclib/temp/practice.mgmt.two_level_project_planning.base/workproducts/project_plan.xmi
@@ -0,0 +1,29 @@
+<?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="_IbVp8KX4EdmvhNXG0Oc2uA"
+ name="project_plan,_0a6vcMlgEdmt3adZL5Dmdw" guid="_IbVp8KX4EdmvhNXG0Oc2uA" changeDate="2008-02-22T01:35:44.953-0500"
+ version="1.0.0">
+ <mainDescription><p>
+ <span style="FONT-SIZE: 10pt; mso-bidi-font-family: Arial">This artifact&nbsp;defines the parameters for project
+ progress tracking and specifies the high-level objectives of the iterations and their milestones. Additionally,&nbsp;it
+ describes how the project is organized and which roles are played by whom.</span>
+</p>
+<p>
+ <span style="FONT-SIZE: 10pt; mso-bidi-font-family: Arial">The project plan allows stakeholders and other team members
+ to understand the big picture and, roughly, when to expect what level of functionality. It it also used for recording
+ the lessons learned from the project.</span><span style="FONT-SIZE: 10pt; mso-bidi-font-family: Arial"><br />
+ </span>
+</p></mainDescription>
+ <purpose><p>
+
+
+ The purpose of this artifact is&nbsp;to provide a central document where any project team member can find the
+
+
+ information on how the project will be managed.&nbsp;
+
+
+</p></purpose>
+</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/praclib/temp/practice.mgmt.two_level_project_planning.base/workproducts/project_risk_slot.assign.xmi b/praclib/temp/practice.mgmt.two_level_project_planning.base/workproducts/project_risk_slot.assign.xmi
new file mode 100644
index 0000000..dec9745
--- /dev/null
+++ b/praclib/temp/practice.mgmt.two_level_project_planning.base/workproducts/project_risk_slot.assign.xmi
@@ -0,0 +1,15 @@
+<?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="-qsk_KkHMnoS0PIISuCiTrA"
+ name="new_artifact,_mpOp4OFkEdyhmsbt0Xyl8A" guid="-qsk_KkHMnoS0PIISuCiTrA" changeDate="2008-02-22T17:30:47.156-0500">
+ <representationOptions><h4>
+ Option: List of risks captured in the project plan
+</h4>
+<p>
+ In this approach you put the overall risk list in the project plan. The iteration plan will contain only the tasks you
+ will be doing during the iteration to mitigate the risks. This will ensure that the iteration plan contains only
+ iteration information. The project plan has to be revisited constantly as you update risks.
+</p></representationOptions>
+</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/praclib/temp/practice.mgmt.whole_team.base/.project b/praclib/temp/practice.mgmt.whole_team.base/.project
new file mode 100644
index 0000000..ca8d84a
--- /dev/null
+++ b/praclib/temp/practice.mgmt.whole_team.base/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>practice.mgmt.whole_team.base</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/practice.mgmt.whole_team.base/customcategories/resources/bookc.gif b/praclib/temp/practice.mgmt.whole_team.base/customcategories/resources/bookc.gif
new file mode 100644
index 0000000..7f2ab85
--- /dev/null
+++ b/praclib/temp/practice.mgmt.whole_team.base/customcategories/resources/bookc.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.whole_team.base/customcategories/resources/bookcL.gif b/praclib/temp/practice.mgmt.whole_team.base/customcategories/resources/bookcL.gif
new file mode 100644
index 0000000..6c5b064
--- /dev/null
+++ b/praclib/temp/practice.mgmt.whole_team.base/customcategories/resources/bookcL.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.whole_team.base/customcategories/resources/pract_dgm32.gif b/praclib/temp/practice.mgmt.whole_team.base/customcategories/resources/pract_dgm32.gif
new file mode 100644
index 0000000..f597332
--- /dev/null
+++ b/praclib/temp/practice.mgmt.whole_team.base/customcategories/resources/pract_dgm32.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.whole_team.base/customcategories/resources/pract_obj.gif b/praclib/temp/practice.mgmt.whole_team.base/customcategories/resources/pract_obj.gif
new file mode 100644
index 0000000..fe8075a
--- /dev/null
+++ b/praclib/temp/practice.mgmt.whole_team.base/customcategories/resources/pract_obj.gif
Binary files differ
diff --git a/praclib/temp/practice.mgmt.whole_team.base/customcategories/whole_team_practice.xmi b/praclib/temp/practice.mgmt.whole_team.base/customcategories/whole_team_practice.xmi
new file mode 100644
index 0000000..4a58d83
--- /dev/null
+++ b/praclib/temp/practice.mgmt.whole_team.base/customcategories/whole_team_practice.xmi
@@ -0,0 +1,64 @@
+<?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: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="-EzgBl0xrSQUDdBUN6hI01A"
+ name="self_organizing_teams_practice,_AH2x0J-lEdyBk-WQzMU-FQ" guid="-EzgBl0xrSQUDdBUN6hI01A"
+ changeDate="2008-03-05T13:27:59.406-0500" version="7.2.0">
+ <mainDescription><p>
+ The&nbsp;Whole Team&nbsp;practice primary adds guidance to to assist teams with collaboration techniques to make the
+ entire team work more effectively together.&nbsp;
+</p>
+<h3>
+ The Essence of the Whole Team Practice
+</h3>
+<p>
+ The following capture the key principles of the&nbsp;Whole Team&nbsp;practice:
+</p>
+<ul>
+ <li>
+ <strong>Maintain a sustainable pace</strong>
+ </li>
+ <li>
+ <strong>Self-organize work assignments</strong>
+ </li>
+ <li>
+ <strong>Daily&nbsp;meetings</strong>
+ </li>
+</ul>
+<h3>
+ <br />
+ Why Adopt this Practice?
+</h3>
+<p>
+ [*** Include some content here that describes the business value of this practice -- what do you get when you adopt
+ it?&nbsp; This section is essentially the value proposition for the practice.&nbsp; You may want to describe some
+ common problems and how this practice solves those problems.&nbsp; &nbsp;***]&nbsp;&nbsp;&nbsp;
+</p>
+<h3>
+ How to Read this Practice
+</h3>
+<p>
+ The best way to read this practice is to first familiarize yourself with its overall structure -- what it is in it and
+ how it is organized.&nbsp;
+</p>
+<p>
+ [*** To be completed.... ***]
+</p>
+<p>
+ For step-by-step instructions on how to adopt this practice, see <a class="elementLink"
+ href="./../../practice.mgmt.whole_team.base/guidances/roadmaps/how_to_adopt_F55EBFB2.html"
+ guid="_oHdNYOMPEdyM47cGD2jiaQ">How to Adopt This Practice</a>.
+</p>
+<h3>
+ Additional Resources
+</h3>
+<p>
+ For more information on the whole team approach, see the following:
+</p>
+<ul>
+ <li>
+ [*** Add more, as needed ***]<br />
+ </li>
+</ul></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.whole_team.base/guidances/guidelines/daily_meetings.xmi b/praclib/temp/practice.mgmt.whole_team.base/guidances/guidelines/daily_meetings.xmi
new file mode 100644
index 0000000..0734b7a
--- /dev/null
+++ b/praclib/temp/practice.mgmt.whole_team.base/guidances/guidelines/daily_meetings.xmi
@@ -0,0 +1,86 @@
+<?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: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="-zqsjK1qfcSGuOsNO5K7UhA"
+ name="new_guideline,_251UMCmREdyy6Oss2-0s1g" guid="-zqsjK1qfcSGuOsNO5K7UhA" changeDate="2007-07-09T11:42:04.884-0400"
+ version="7.2.0">
+ <mainDescription><h3>
+ Practices
+</h3>
+<p>
+ Daily meetings are the heartbeat of the project. All team members are required to attend&nbsp;it. The meetings are held
+ in the same place at the same time every work day and should&nbsp;not last for more than 15 minutes. Usually, teams do
+ the meetings standing up to keep them short. Anyone who is directly involved&nbsp;can also attend the meeting as an
+ observer, but care should be taken because too many people in the meeting may cause disruption or cause people to be
+ uncomfortable in sharing information. Typical daily meetings should have at most 10 people.
+</p>During the daily meeting, each team member updates their peers with answers to the following three questions <a
+class="elementLinkWithUserText"
+href="./../../../core.mgmt.common.base/guidances/supportingmaterials/mgmt_references_D80619F3.html#SCH04"
+guid="_JlTPUM6aEdyuBO4ZIzcyig">[SCH04]</a>: 
+<ol>
+ <li>
+ What did I do yesterday?
+ </li>
+ <li>
+ What will I do today?
+ </li>
+ <li>
+ What is impeding my work?
+ </li>
+</ol>
+<p>
+ These 3 questions have a specific purpose [<a class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/tech_references_6CCF393.html#SUT06"
+ guid="_9ToeIB83Edqsvps02rpOOg">SUT06</a>]:
+</p>
+<ul>
+ <li>
+ The first question tests the focus of the team - anything done that was not work planned for the iteration is
+ questioned.
+ </li>
+ <li>
+ Answering the second question revises project strategy on a daily basis by reorienting the team due to dependency
+ changes that were revealed by the previous question.
+ </li>
+ <li>
+ The third question will create issues that may result in new tasks in the work items list. The most important
+ effect of this question is to create a list of issues that are assigned to the team or to managers.&nbsp;The team
+ should expect management to help eliminating bottlenecks.&nbsp;
+ </li>
+</ul>
+<p>
+ These are the minimum number of questions that satisfy the goals of daily meetings. Experienced practitioners tend to
+ add an additional question for improving collaboration among team members: "What have I learned or decided of relevance
+ to the team?" [<a class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/tech_references_6CCF393.html#LAR03"
+ guid="_9ToeIB83Edqsvps02rpOOg">LAR03</a>].&nbsp;“What might help or hinder others in meeting their commitments?” [<a
+ class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/tech_references_6CCF393.html#YIP"
+ guid="_9ToeIB83Edqsvps02rpOOg">YIP</a>]. Other topics of discussion (<i>e.g.</i>, design discussions, gossip, etc.)
+ should be deferred until after the meeting.
+</p>
+<h3>
+ Value
+</h3>
+<p>
+ For self-directed teams, the daily meeting is a mechanism to quickly inform the team about the state of the project and
+ people. It supports openness and allows resolution of dependencies and conflicts in real-time. It builds a team -
+ effective teams are built by regularly communicating, sharing commitments and helping each other. [<a
+ class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/tech_references_6CCF393.html#LAR03"
+ guid="_9ToeIB83Edqsvps02rpOOg">LAR03</a>]<br />
+ <br />
+</p>
+<h3>
+ What a daily meeting is not
+</h3>
+<p>
+ The daily meeting is not a status update meeting in which the project manager is collecting information about who is
+ behind schedule. Rather, it is a meeting in which team members make commitments to each other.<br />
+ <br />
+ Neither is it a problem-solving or issue resolution meeting. Issues that are raised are registered and usually dealt
+ with by the relevant team members immediately afterwards. It is the project manager's responsibility to resolve them as
+ quickly as possible or to make sure that someone on the team does so.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.whole_team.base/guidances/guidelines/maintain_a_sustainable_pace.xmi b/praclib/temp/practice.mgmt.whole_team.base/guidances/guidelines/maintain_a_sustainable_pace.xmi
new file mode 100644
index 0000000..d619988
--- /dev/null
+++ b/praclib/temp/practice.mgmt.whole_team.base/guidances/guidelines/maintain_a_sustainable_pace.xmi
@@ -0,0 +1,28 @@
+<?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="-aoCtIwigi2NOLiclMAXvgQ"
+ name="new_guideline,_KzYHYMLmEdysDsQChI42QQ" guid="-aoCtIwigi2NOLiclMAXvgQ" changeDate="2008-01-14T16:29:21.515-0500">
+ <mainDescription><p>
+ A <strong>sustainable pace</strong> is the rate of development that the team can maintain consistently without burning
+ out team members.
+</p>
+<p>
+ This idea of a <i>sustainable pace</i> is one of the central drivers behind XP (eXtreme Programming) . Any development
+ team can hack out gobs of code over a one-year period, but sustaining code much beyond this period is a costly and
+ difficult proposition.
+</p>
+<p>
+ XP suggests that activities should be built into the everyday work, rather than bunched up and performed only at
+ particular points during the development cycle.&nbsp; For instance, inspect the code all the time through pair
+ programming and collective code ownership, and continually specify the system through automated tests all the
+ time.&nbsp; This prevents roadblocks in the process from occurring that prevent maintaining a sustainable pace
+ throughout the entire development cycle.
+</p><br />
+<p>
+ [*** This guideline requires more work....the above content was based on information obtained from this link:&nbsp; <a
+ href="http://langrsoft.com/articles/sustainablePace.shtml"
+ target="_blank">http://langrsoft.com/articles/sustainablePace.shtml</a>&nbsp;***]&nbsp;
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.whole_team.base/guidances/guidelines/self_organize_work_assignments.xmi b/praclib/temp/practice.mgmt.whole_team.base/guidances/guidelines/self_organize_work_assignments.xmi
new file mode 100644
index 0000000..80f2542
--- /dev/null
+++ b/praclib/temp/practice.mgmt.whole_team.base/guidances/guidelines/self_organize_work_assignments.xmi
@@ -0,0 +1,101 @@
+<?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: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="-e26WOHRbTVQrDssK5zijVA"
+ name="self_organize_work_assignments,_rmBEkJjsEduad8I_c-ogIA" guid="-e26WOHRbTVQrDssK5zijVA"
+ changeDate="2008-02-22T02:07:11.171-0500" version="1.0.0">
+ <mainDescription><p>
+ A "self organizing team" has the authority to choose the work that it will perform and the responsibility to do that
+ work in the way that it chooses.&nbsp; Important aspects of a self organizing team&nbsp;are:
+</p>
+<ol>
+ <li>
+ The team selects its own work. At the beginning of an iteration the team collectively selects the work from the
+ prioritized <a class="elementLink"
+ href="./../../../core.mgmt.slot.base/workproducts/project_work_slot_F12BAC46.html"
+ guid="_1QZI8EfUEdyiPI8btkmvmw">[Project Work]</a>. Work selection is performed within given constraints, including
+ the priorities set by stakeholders, time (such as the length of the current iteration or project increment), the
+ budget, and the skills of team members.
+ </li>
+ <li>
+ Individuals select their own work. Individuals are empowered to select their own work. Someone will choose to do
+ something because they are good at it and know that they can do the work effectively, because they want to gain
+ more experience at something and hope to improve their skill-set by working with someone with such experience, or
+ because they know that the work needs to be done and that it's their turn to do so. Although an individual fulfills
+ one or more roles on a project team that doesn't imply that the person is constrained to only doing specific types
+ of work.
+ </li>
+ <li>
+ The team determines how to perform the work. At the beginning of an iteration the team will hold an "all hands"
+ planning meeting where it determines the general strategy for doing the work and the tasks required to do so. More
+ detailed planning, if required, will be done on a just-in-time (JIT) basis by the individual(s) doing the work.
+ Note that the team is still constrained by your organization's standards, technical infrastructure, regulations,
+ and so on.
+ </li>
+ <li>
+ Everyone commits to the work. The team commits to accomplishing the work that it has agreed to do by the end of the
+ iteration. Individuals also commit to doing the work that they say they will do, although as the iteration
+ progresses various tasks may be renegotiated as required.
+ </li>
+ <li>
+ The team coordinates regularly. To ensure that the work is accomplished the team must coordinate its efforts
+ effectively. This is typically done through daily stand up meetings of the team and impromptu discussions between
+ individuals.
+ </li>
+</ol>
+<p>
+ This is a participatory approach to decision making where everyone has the opportunity to provide input and to listen
+ to the decision making process. The goal is to make decisions at the right place within the organizational structure,
+ empowering teams by giving them both the responsibility and the authority to get the job done. It improves motivation
+ amongst team members, and thereby their productivity, by giving them control over their work.
+</p>
+<h3>
+ Project Manager Responsibilities
+</h3>
+<p>
+ There is still work for the project manager on self organizing teams. The project manager must still:
+</p>
+<ol>
+ <li>
+ Provide leadership. Team culture and project vision must be nurtured and evolved throughout the project, and
+ direction must be provided to the team.
+ </li>
+ <li>
+ Mediate disagreements. The manager must be prepared to step in and make a decision when other team members are
+ unable to come to a decision.
+ </li>
+ <li>
+ Ensure that team members grow their skill-set. From time to time the manager may need to motivate individuals to
+ take on new tasks that are outside their comfort zone or to work with others to help those people gain new skills.
+ </li>
+ <li>
+ Ensure that the team respects their limits. Self organizing teams have the authority to make decisions within the
+ scope of their responsibility, but that doesn't mean that they get to rethink everything that they feel like. For
+ example, the development team must still conform to the technical infrastructure and to the business strategy of
+ your organization: they likely don't have the authority to change these things even though they may not fully agree
+ with them. When an issue falls outside their scope of responsibility the team must either accept it or collaborate
+ with the people with the appropriate authority.
+ </li>
+ <li>
+ Summarize the project plan. External stakeholders, such as senior management or business representatives not
+ actively involved with the team, will want to know the current status of the project and the team's current plans.
+ The project manager may be required to summarize and communicate this information to those people.
+ </li>
+</ol>
+<h3>
+ What This Isn't
+</h3>
+<p>
+ The concept of self organizing teams often sounds like anarchy or non-management to traditional IT professionals, but
+ nothing could be further from the truth. Although self organization relies on team members being responsible and mature
+ it is tempered by the guiding hand of a good project manager. It is also tempered by organizational standards,
+ infrastructure, and external regulations. "Self organizing" doesn't mean that you have complete freedom to do what you
+ want.
+</p>
+<p>
+ Self organization isn't necessarily a consensus-based approach either; sometimes individuals will disagree with a
+ decision but will choose to go along with the will of the team. Nevertheless, consensus isn't ruled out by this
+ approach but it certainly isn't required.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.whole_team.base/guidances/roadmaps/how_to_adopt.xmi b/praclib/temp/practice.mgmt.whole_team.base/guidances/roadmaps/how_to_adopt.xmi
new file mode 100644
index 0000000..d6efa17
--- /dev/null
+++ b/praclib/temp/practice.mgmt.whole_team.base/guidances/roadmaps/how_to_adopt.xmi
@@ -0,0 +1,21 @@
+<?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: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="-kGPLyLlIylW-w3B0RlwbwQ"
+ name="how_to_adopt,_ERIDQOMPEdyM47cGD2jiaQ" guid="-kGPLyLlIylW-w3B0RlwbwQ" changeDate="2008-02-17T08:09:46.937-0500"
+ version="7.2.0">
+ <mainDescription><h3>
+ Getting Started&nbsp;
+</h3>
+<p>
+ TODO:&nbsp; Describe how to 'read' this practice.......provide description with links to appropriate content to help
+ someone get started with this practice
+</p>
+<h3>
+ Common Pitfalls
+</h3>
+<p>
+ TBD
+</p><br /></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.whole_team.base/guidances/supportingmaterials/release_info_whole_team.xmi b/praclib/temp/practice.mgmt.whole_team.base/guidances/supportingmaterials/release_info_whole_team.xmi
new file mode 100644
index 0000000..596da1b
--- /dev/null
+++ b/praclib/temp/practice.mgmt.whole_team.base/guidances/supportingmaterials/release_info_whole_team.xmi
@@ -0,0 +1,27 @@
+<?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="-PZv-hK8T1VJ10ii7iZn85Q"
+ name="release_info_iterative_dev.whole_team,_kAKR8MOAEdy3nv0ZK8D4GQ" guid="-PZv-hK8T1VJ10ii7iZn85Q"
+ changeDate="2008-01-15T10:42:22.234-0500">
+ <mainDescription><h3>
+ Whole Team&nbsp;Practice
+</h3>
+<p>
+ Version 1.0
+</p>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p>
+ This practice contributes&nbsp;guidance&nbsp;that enables the team to&nbsp;be high-performing&nbsp;to the Iterative
+ Development Practice and the Two-Level Project Planning Practice.&nbsp;
+ </p>
+ <p>
+ [*** NOT YET RELEASED ***]
+ </p>
+ <p>
+ This is the initial release of this practice.
+ </p><br />
+ <br />
+</blockquote><br /></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.mgmt.whole_team.base/plugin.xmi b/praclib/temp/practice.mgmt.whole_team.base/plugin.xmi
new file mode 100644
index 0000000..95495a4
--- /dev/null
+++ b/praclib/temp/practice.mgmt.whole_team.base/plugin.xmi
@@ -0,0 +1,155 @@
+<?xml version="1.0" encoding="UTF-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.4/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.2.0" xmlns:epf="http://www.eclipse.org/epf"
+ epf:version="1.2.0">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_402MAJ6YEdyQN-zRFaRrCQ"
+ guid="_402MAJ6YEdyQN-zRFaRrCQ">
+ <resourceDescriptors xmi:id="_GWl9ICmSEdyy6Oss2-0s1g" id="-zqsjK1qfcSGuOsNO5K7UhA"
+ uri="guidances/guidelines/daily_meetings.xmi"/>
+ <resourceDescriptors xmi:id="_2IlrcJjsEduad8I_c-ogIA" id="-e26WOHRbTVQrDssK5zijVA"
+ uri="guidances/guidelines/self_organize_work_assignments.xmi"/>
+ <resourceDescriptors xmi:id="_Yepk4L8SEdyWX5Yd-9QZ1A" id="-EzgBl0xrSQUDdBUN6hI01A"
+ uri="customcategories/whole_team_practice.xmi"/>
+ <resourceDescriptors xmi:id="_VTz44cLpEdysDsQChI42QQ" id="-aoCtIwigi2NOLiclMAXvgQ"
+ uri="guidances/guidelines/maintain_a_sustainable_pace.xmi"/>
+ <resourceDescriptors xmi:id="_kBDp0cOAEdy3nv0ZK8D4GQ" id="-PZv-hK8T1VJ10ii7iZn85Q"
+ uri="guidances/supportingmaterials/release_info_whole_team.xmi"/>
+ <resourceDescriptors xmi:id="_oIzRMeMPEdyM47cGD2jiaQ" id="-kGPLyLlIylW-w3B0RlwbwQ"
+ uri="guidances/roadmaps/how_to_adopt.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_40sbAJ6YEdyQN-zRFaRrCQ" name="practice.mgmt.whole_team.base"
+ guid="_40sbAJ6YEdyQN-zRFaRrCQ" changeDate="2008-02-19T18:24:57.140-0500">
+ <copyrightStatement href="uma://_iVydgENdEdy245g62lfWcA#_cTs20KzREduOqvpk_MDLfQ"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_40sbAZ6YEdyQN-zRFaRrCQ"
+ name="Content" guid="_40sbAZ6YEdyQN-zRFaRrCQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_40sbAp6YEdyQN-zRFaRrCQ"
+ name="Categories" guid="_40sbAp6YEdyQN-zRFaRrCQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_40sbA56YEdyQN-zRFaRrCQ"
+ name="Domains" guid="_40sbA56YEdyQN-zRFaRrCQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_40sbBJ6YEdyQN-zRFaRrCQ"
+ name="Disciplines" guid="_40sbBJ6YEdyQN-zRFaRrCQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_40sbBZ6YEdyQN-zRFaRrCQ"
+ name="RoleSets" guid="_40sbBZ6YEdyQN-zRFaRrCQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_40sbBp6YEdyQN-zRFaRrCQ"
+ name="WP Types" guid="_40sbBp6YEdyQN-zRFaRrCQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_40sbB56YEdyQN-zRFaRrCQ"
+ name="Tools" guid="_40sbB56YEdyQN-zRFaRrCQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_40sbCJ6YEdyQN-zRFaRrCQ"
+ name="StandardCategories" guid="_40sbCJ6YEdyQN-zRFaRrCQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_40sbCZ6YEdyQN-zRFaRrCQ"
+ name="CustomCategories" guid="_40sbCZ6YEdyQN-zRFaRrCQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_40sbCp6YEdyQN-zRFaRrCQ"
+ name="Hidden" guid="_40sbCp6YEdyQN-zRFaRrCQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_40sbC56YEdyQN-zRFaRrCQ"
+ name="Custom Categories" guid="_40sbC56YEdyQN-zRFaRrCQ" categorizedElements="_AH2x0J-lEdyBk-WQzMU-FQ _vqLKkMh5EdygFZkm1d5NtQ"/>
+ </childPackages>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_AH2x0J-lEdyBk-WQzMU-FQ"
+ name="whole_team_practice" guid="_AH2x0J-lEdyBk-WQzMU-FQ" briefDescription="This practice organizes the team and work assignments through a collaborative approach."
+ presentationName="Whole Team" shapeicon="customcategories/resources/pract_dgm32.gif"
+ nodeicon="customcategories/resources/pract_obj.gif" categorizedElements="_oHdNYOMPEdyM47cGD2jiaQ _KS1cIOMREdyM47cGD2jiaQ">
+ <presentation xmi:id="-EzgBl0xrSQUDdBUN6hI01A" href="uma://-EzgBl0xrSQUDdBUN6hI01A#-EzgBl0xrSQUDdBUN6hI01A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_vqLKkMh5EdygFZkm1d5NtQ"
+ name="contributions_to_nav_building_blocks" guid="_vqLKkMh5EdygFZkm1d5NtQ"
+ presentationName="Contributions to Navigation Building Blocks" categorizedElements="_KLCIMMh8EdygFZkm1d5NtQ _ZIw2UMh9EdygFZkm1d5NtQ _adZuAMh9EdygFZkm1d5NtQ _qmwGsNQvEdyM_J8-fv54DA _0jLuQOMPEdyM47cGD2jiaQ"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_KLCIMMh8EdygFZkm1d5NtQ"
+ name="release_info.assign" guid="_KLCIMMh8EdygFZkm1d5NtQ" variabilityType="contributes"
+ categorizedElements="_kAKR8MOAEdy3nv0ZK8D4GQ">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCIHYcRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_ZIw2UMh9EdygFZkm1d5NtQ"
+ name="guideline_list.assign" guid="_ZIw2UMh9EdygFZkm1d5NtQ" variabilityType="contributes"
+ categorizedElements="_251UMCmREdyy6Oss2-0s1g _KzYHYMLmEdysDsQChI42QQ _rmBEkJjsEduad8I_c-ogIA">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4ZcRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_adZuAMh9EdygFZkm1d5NtQ"
+ name="practice_list.assign" guid="_adZuAMh9EdygFZkm1d5NtQ" variabilityType="contributes"
+ categorizedElements="_AH2x0J-lEdyBk-WQzMU-FQ">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCIHY8RdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_qmwGsNQvEdyM_J8-fv54DA"
+ name="management_practice_list.assign" guid="_qmwGsNQvEdyM_J8-fv54DA"
+ variabilityType="contributes" categorizedElements="_AH2x0J-lEdyBk-WQzMU-FQ">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_auUD0NQuEdyM_J8-fv54DA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_0jLuQOMPEdyM47cGD2jiaQ"
+ name="roadmap_list.assign" guid="_0jLuQOMPEdyM47cGD2jiaQ" variabilityType="contributes"
+ categorizedElements="_oHdNYOMPEdyM47cGD2jiaQ">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4ZsRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_KS1cIOMREdyM47cGD2jiaQ"
+ name="guidance" guid="_KS1cIOMREdyM47cGD2jiaQ" presentationName="Guidance"
+ shapeicon="customcategories/resources/bookcL.gif" nodeicon="customcategories/resources/bookc.gif"
+ categorizedElements="_251UMCmREdyy6Oss2-0s1g _KzYHYMLmEdysDsQChI42QQ _rmBEkJjsEduad8I_c-ogIA">
+ <methodElementProperty xmi:id="_Re1IwOMREdyM47cGD2jiaQ" name="CategoryElementsSortType"
+ value="Alphabetic"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_40sbDJ6YEdyQN-zRFaRrCQ"
+ name="CoreContent" guid="_40sbDJ6YEdyQN-zRFaRrCQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_VxJAUJ9WEdy3Nc4rvuj7bA"
+ name="Whole Team" guid="_VxJAUJ9WEdy3Nc4rvuj7bA">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_idXpgMOAEdy3nv0ZK8D4GQ"
+ name="Release Info" guid="_idXpgMOAEdy3nv0ZK8D4GQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="_kAKR8MOAEdy3nv0ZK8D4GQ"
+ name="release_info_whole_team" guid="_kAKR8MOAEdy3nv0ZK8D4GQ" presentationName="Whole Team Practice">
+ <presentation xmi:id="-PZv-hK8T1VJ10ii7iZn85Q" href="uma://-PZv-hK8T1VJ10ii7iZn85Q#-PZv-hK8T1VJ10ii7iZn85Q"/>
+ </contentElements>
+ </childPackages>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_251UMCmREdyy6Oss2-0s1g"
+ name="daily_meetings" guid="_251UMCmREdyy6Oss2-0s1g" briefDescription="This guideline describes how the team can synchronize their work and progress by meeting every day for a quick status update and report on impediments."
+ presentationName="Daily Meetings">
+ <presentation xmi:id="-zqsjK1qfcSGuOsNO5K7UhA" href="uma://-zqsjK1qfcSGuOsNO5K7UhA#-zqsjK1qfcSGuOsNO5K7UhA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_rmBEkJjsEduad8I_c-ogIA"
+ name="self_organize_work_assignments" guid="_rmBEkJjsEduad8I_c-ogIA"
+ briefDescription="Agile software development teams organize the work that needs to be done together as a team."
+ presentationName="Self-Organize Work Assignments">
+ <presentation xmi:id="-e26WOHRbTVQrDssK5zijVA" href="uma://-e26WOHRbTVQrDssK5zijVA#-e26WOHRbTVQrDssK5zijVA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_KzYHYMLmEdysDsQChI42QQ"
+ name="maintain_a_sustainable_pace" guid="_KzYHYMLmEdysDsQChI42QQ" presentationName="Maintain a Sustainable Pace">
+ <presentation xmi:id="-aoCtIwigi2NOLiclMAXvgQ" href="uma://-aoCtIwigi2NOLiclMAXvgQ#-aoCtIwigi2NOLiclMAXvgQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_aP5rMN8_Edyhmsbt0Xyl8A"
+ name="project_planning_guidance_slot.assign" guid="_aP5rMN8_Edyhmsbt0Xyl8A"
+ variabilityType="contributes" guidelines="_KzYHYMLmEdysDsQChI42QQ">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_vJYucEfUEdyiPI8btkmvmw#_sLQ6AN8-Edyhmsbt0Xyl8A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_7FQ-sN8_Edyhmsbt0Xyl8A"
+ name="collaboration_guidance_slot.assign" guid="_7FQ-sN8_Edyhmsbt0Xyl8A"
+ variabilityType="contributes" guidelines="_251UMCmREdyy6Oss2-0s1g">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_vJYucEfUEdyiPI8btkmvmw#_68JUYN8-Edyhmsbt0Xyl8A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_EY3RAN9AEdyhmsbt0Xyl8A"
+ name="work_assignment_guidance_slot.assign" guid="_EY3RAN9AEdyhmsbt0Xyl8A"
+ variabilityType="contributes" guidelines="_rmBEkJjsEduad8I_c-ogIA">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_vJYucEfUEdyiPI8btkmvmw#_BslGYN8_Edyhmsbt0Xyl8A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Roadmap" xmi:id="_oHdNYOMPEdyM47cGD2jiaQ"
+ name="how_to_adopt" guid="_oHdNYOMPEdyM47cGD2jiaQ" briefDescription="This roadmap describes how to adopt the Whole Team Practice."
+ presentationName="How to Adopt This Practice">
+ <presentation xmi:id="-kGPLyLlIylW-w3B0RlwbwQ" href="uma://-kGPLyLlIylW-w3B0RlwbwQ#-kGPLyLlIylW-w3B0RlwbwQ"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_40sbDZ6YEdyQN-zRFaRrCQ"
+ name="CapabilityPatterns" guid="_40sbDZ6YEdyQN-zRFaRrCQ"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_40sbDp6YEdyQN-zRFaRrCQ"
+ name="DeliveryProcesses" guid="_40sbDp6YEdyQN-zRFaRrCQ"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_40sbD56YEdyQN-zRFaRrCQ"
+ name="ProcessContributions" guid="_40sbD56YEdyQN-zRFaRrCQ"/>
+ <bases href="uma://_iVydgENdEdy245g62lfWcA#_iVydgENdEdy245g62lfWcA"/>
+ <bases href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno4EKmEdyrauqpmnA8jQ"/>
+ <bases href="uma://_vJYucEfUEdyiPI8btkmvmw#_vJYucEfUEdyiPI8btkmvmw"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/practice.tech.agile_testing.assign/.project b/praclib/temp/practice.tech.agile_testing.assign/.project
new file mode 100644
index 0000000..2343379
--- /dev/null
+++ b/praclib/temp/practice.tech.agile_testing.assign/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>practice.tech.agile_testing.assign</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/practice.tech.agile_testing.assign/plugin.xmi b/praclib/temp/practice.tech.agile_testing.assign/plugin.xmi
new file mode 100644
index 0000000..25fe0b6
--- /dev/null
+++ b/praclib/temp/practice.tech.agile_testing.assign/plugin.xmi
@@ -0,0 +1,84 @@
+<?xml version="1.0" encoding="UTF-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.4/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.2.0" xmlns:epf="http://www.eclipse.org/epf"
+ epf:version="1.2.0">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_IItp8MuXEdyLOriywSJkoQ"
+ guid="_IItp8MuXEdyLOriywSJkoQ"/>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_IItp4MuXEdyLOriywSJkoQ" name="practice.tech.agile_testing.assign"
+ guid="_IItp4MuXEdyLOriywSJkoQ">
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_IItp4cuXEdyLOriywSJkoQ"
+ name="Content" guid="_IItp4cuXEdyLOriywSJkoQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_IItp4suXEdyLOriywSJkoQ"
+ name="Categories" guid="_IItp4suXEdyLOriywSJkoQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_IItp48uXEdyLOriywSJkoQ"
+ name="Domains" guid="_IItp48uXEdyLOriywSJkoQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_IItp5MuXEdyLOriywSJkoQ"
+ name="Disciplines" guid="_IItp5MuXEdyLOriywSJkoQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:Discipline" xmi:id="_iBsdQMubEdy1o5Xnqdh1Tg"
+ name="test_discipline.assign" guid="_iBsdQMubEdy1o5Xnqdh1Tg" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Discipline" href="uma://_MRPloEFXEdy9ENCpSugIjA#_iGSHtlZ-EdyIUdvDLLUdeg"/>
+ <tasks href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_0iwc0clgEdmt3adZL5Dmdw"/>
+ <tasks href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_0jO98MlgEdmt3adZL5Dmdw"/>
+ <tasks href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_0jVEkMlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_IItp5cuXEdyLOriywSJkoQ"
+ name="RoleSets" guid="_IItp5cuXEdyLOriywSJkoQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_IItp5suXEdyLOriywSJkoQ"
+ name="WP Types" guid="_IItp5suXEdyLOriywSJkoQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_IItp58uXEdyLOriywSJkoQ"
+ name="Tools" guid="_IItp58uXEdyLOriywSJkoQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_IItp6MuXEdyLOriywSJkoQ"
+ name="StandardCategories" guid="_IItp6MuXEdyLOriywSJkoQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_IItp6cuXEdyLOriywSJkoQ"
+ name="CustomCategories" guid="_IItp6cuXEdyLOriywSJkoQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_IItp6suXEdyLOriywSJkoQ"
+ name="Hidden" guid="_IItp6suXEdyLOriywSJkoQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_IItp68uXEdyLOriywSJkoQ"
+ name="Custom Categories" guid="_IItp68uXEdyLOriywSJkoQ"/>
+ </childPackages>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_IItp7MuXEdyLOriywSJkoQ"
+ name="CoreContent" guid="_IItp7MuXEdyLOriywSJkoQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Z30okMuaEdy1o5Xnqdh1Tg"
+ name="Role Assignments" guid="_Z30okMuaEdy1o5Xnqdh1Tg">
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_0M2bkMuaEdy1o5Xnqdh1Tg"
+ name="create_test_cases.assign_role" guid="_0M2bkMuaEdy1o5Xnqdh1Tg"
+ variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Task" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_0iwc0clgEdmt3adZL5Dmdw"/>
+ <performedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0ZM4MclgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0VxJsMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_dTa6gMAYEdqX-s4mWhkyqQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_47yP4MuaEdy1o5Xnqdh1Tg"
+ name="implement_tests.assign_role" guid="_47yP4MuaEdy1o5Xnqdh1Tg" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Task" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_0jO98MlgEdmt3adZL5Dmdw"/>
+ <performedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0ZM4MclgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0VxJsMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_dTa6gMAYEdqX-s4mWhkyqQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_9wPdYMuaEdy1o5Xnqdh1Tg"
+ name="run_tests.assign_role" guid="_9wPdYMuaEdy1o5Xnqdh1Tg" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Task" href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_0jVEkMlgEdmt3adZL5Dmdw"/>
+ <performedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0ZM4MclgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_IItp7cuXEdyLOriywSJkoQ"
+ name="CapabilityPatterns" guid="_IItp7cuXEdyLOriywSJkoQ"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_IItp7suXEdyLOriywSJkoQ"
+ name="DeliveryProcesses" guid="_IItp7suXEdyLOriywSJkoQ"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_IItp78uXEdyLOriywSJkoQ"
+ name="ProcessContributions" guid="_IItp78uXEdyLOriywSJkoQ"/>
+ <bases href="uma://_A118oMYaEdyXeo04os5BOw#_A118oMYaEdyXeo04os5BOw"/>
+ <bases href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2AAouEdyhlpBPrduOMw"/>
+ <bases href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0ELXuEduGP_98XMd0fg"/>
+ <bases href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9OMG5KEdyAHIxjZ9kpqw"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/practice.tech.agile_testing.base/.project b/praclib/temp/practice.tech.agile_testing.base/.project
new file mode 100644
index 0000000..6fee7d6
--- /dev/null
+++ b/praclib/temp/practice.tech.agile_testing.base/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>practice.tech.agile_testing.base</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/practice.tech.agile_testing.base/customcategories/resources/bookc.gif b/praclib/temp/practice.tech.agile_testing.base/customcategories/resources/bookc.gif
new file mode 100644
index 0000000..7f2ab85
--- /dev/null
+++ b/praclib/temp/practice.tech.agile_testing.base/customcategories/resources/bookc.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.agile_testing.base/customcategories/resources/bookcL.gif b/praclib/temp/practice.tech.agile_testing.base/customcategories/resources/bookcL.gif
new file mode 100644
index 0000000..6c5b064
--- /dev/null
+++ b/praclib/temp/practice.tech.agile_testing.base/customcategories/resources/bookcL.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.agile_testing.base/customcategories/resources/compass.gif b/praclib/temp/practice.tech.agile_testing.base/customcategories/resources/compass.gif
new file mode 100644
index 0000000..39f306a
--- /dev/null
+++ b/praclib/temp/practice.tech.agile_testing.base/customcategories/resources/compass.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.agile_testing.base/customcategories/resources/compassL.gif b/praclib/temp/practice.tech.agile_testing.base/customcategories/resources/compassL.gif
new file mode 100644
index 0000000..4117414
--- /dev/null
+++ b/praclib/temp/practice.tech.agile_testing.base/customcategories/resources/compassL.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.agile_testing.base/customcategories/resources/pract_dgm32.gif b/praclib/temp/practice.tech.agile_testing.base/customcategories/resources/pract_dgm32.gif
new file mode 100644
index 0000000..f597332
--- /dev/null
+++ b/praclib/temp/practice.tech.agile_testing.base/customcategories/resources/pract_dgm32.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.agile_testing.base/customcategories/resources/pract_obj.gif b/praclib/temp/practice.tech.agile_testing.base/customcategories/resources/pract_obj.gif
new file mode 100644
index 0000000..fe8075a
--- /dev/null
+++ b/praclib/temp/practice.tech.agile_testing.base/customcategories/resources/pract_obj.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.agile_testing.base/customcategories/resources/task_dgm32.gif b/praclib/temp/practice.tech.agile_testing.base/customcategories/resources/task_dgm32.gif
new file mode 100644
index 0000000..a91ea1c
--- /dev/null
+++ b/praclib/temp/practice.tech.agile_testing.base/customcategories/resources/task_dgm32.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.agile_testing.base/customcategories/resources/task_obj.gif b/praclib/temp/practice.tech.agile_testing.base/customcategories/resources/task_obj.gif
new file mode 100644
index 0000000..7633d58
--- /dev/null
+++ b/praclib/temp/practice.tech.agile_testing.base/customcategories/resources/task_obj.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.agile_testing.base/customcategories/resources/workproduct_dgm32.gif b/praclib/temp/practice.tech.agile_testing.base/customcategories/resources/workproduct_dgm32.gif
new file mode 100644
index 0000000..009c9af
--- /dev/null
+++ b/praclib/temp/practice.tech.agile_testing.base/customcategories/resources/workproduct_dgm32.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.agile_testing.base/customcategories/resources/workproduct_obj.gif b/praclib/temp/practice.tech.agile_testing.base/customcategories/resources/workproduct_obj.gif
new file mode 100644
index 0000000..3e58c6f
--- /dev/null
+++ b/praclib/temp/practice.tech.agile_testing.base/customcategories/resources/workproduct_obj.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.agile_testing.base/plugin.xmi b/praclib/temp/practice.tech.agile_testing.base/plugin.xmi
new file mode 100644
index 0000000..fc89c89
--- /dev/null
+++ b/praclib/temp/practice.tech.agile_testing.base/plugin.xmi
@@ -0,0 +1,154 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_H0G_MG5KEdyAHIxjZ9kpqw"
+ guid="_H0G_MG5KEdyAHIxjZ9kpqw">
+ <resourceDescriptors xmi:id="_nGVnFPL5Edm6Nvont3uinw" id="_NrVKsKeqEdmKDbQuyzCoqQ"
+ uri="tasks/create_test_cases.xmi"/>
+ <resourceDescriptors xmi:id="_nGVnFfL5Edm6Nvont3uinw" id="_NrbRUKeqEdmKDbQuyzCoqQ"
+ uri="tasks/implement_tests.xmi"/>
+ <resourceDescriptors xmi:id="_nGbtsPL5Edm6Nvont3uinw" id="_NrbRUqeqEdmKDbQuyzCoqQ"
+ uri="tasks/run_tests.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_Hz9OMG5KEdyAHIxjZ9kpqw" name="practice.tech.agile_testing.base"
+ guid="_Hz9OMG5KEdyAHIxjZ9kpqw" changeDate="2008-02-05T16:19:33.625-0500">
+ <copyrightStatement href="uma://_iVydgENdEdy245g62lfWcA#_cTs20KzREduOqvpk_MDLfQ"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Hz9OMW5KEdyAHIxjZ9kpqw"
+ name="Content" guid="_Hz9OMW5KEdyAHIxjZ9kpqw">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Hz9OMm5KEdyAHIxjZ9kpqw"
+ name="Categories" guid="_Hz9OMm5KEdyAHIxjZ9kpqw">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Hz9OM25KEdyAHIxjZ9kpqw"
+ name="Domains" guid="_Hz9OM25KEdyAHIxjZ9kpqw"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Hz9ONG5KEdyAHIxjZ9kpqw"
+ name="Disciplines" guid="_Hz9ONG5KEdyAHIxjZ9kpqw"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Hz9ONW5KEdyAHIxjZ9kpqw"
+ name="RoleSets" guid="_Hz9ONW5KEdyAHIxjZ9kpqw"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Hz9ONm5KEdyAHIxjZ9kpqw"
+ name="WP Types" guid="_Hz9ONm5KEdyAHIxjZ9kpqw"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Hz9ON25KEdyAHIxjZ9kpqw"
+ name="Tools" guid="_Hz9ON25KEdyAHIxjZ9kpqw"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Hz9OOG5KEdyAHIxjZ9kpqw"
+ name="StandardCategories" guid="_Hz9OOG5KEdyAHIxjZ9kpqw"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Hz9OOW5KEdyAHIxjZ9kpqw"
+ name="CustomCategories" guid="_Hz9OOW5KEdyAHIxjZ9kpqw">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Hz9OOm5KEdyAHIxjZ9kpqw"
+ name="Hidden" guid="_Hz9OOm5KEdyAHIxjZ9kpqw">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_Hz9OO25KEdyAHIxjZ9kpqw"
+ name="Custom Categories" guid="_Hz9OO25KEdyAHIxjZ9kpqw" categorizedElements="_7vvsoJ-lEdyBk-WQzMU-FQ _z30CYNQvEdyM_J8-fv54DA"/>
+ </childPackages>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_7vvsoJ-lEdyBk-WQzMU-FQ"
+ name="agile_testing_practice" guid="_7vvsoJ-lEdyBk-WQzMU-FQ" briefDescription="This practice focuses the testing effort where it will provide the greatest value, by applying agile testing principles."
+ presentationName="Independent Testing" shapeicon="customcategories/resources/pract_dgm32.gif"
+ nodeicon="customcategories/resources/pract_obj.gif" categorizedElements="_fKHk0J_5EdyBk-WQzMU-FQ _rSUswJ_5EdyBk-WQzMU-FQ _6nQ2cJ_5EdyBk-WQzMU-FQ"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_fKHk0J_5EdyBk-WQzMU-FQ"
+ name="tasks" guid="_fKHk0J_5EdyBk-WQzMU-FQ" presentationName="Tasks"
+ shapeicon="customcategories/resources/task_dgm32.gif" nodeicon="customcategories/resources/task_obj.gif"
+ categorizedElements="_0iwc0clgEdmt3adZL5Dmdw _0jO98MlgEdmt3adZL5Dmdw _0jVEkMlgEdmt3adZL5Dmdw"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_rSUswJ_5EdyBk-WQzMU-FQ"
+ name="work_products" guid="_rSUswJ_5EdyBk-WQzMU-FQ" presentationName="Work Products"
+ shapeicon="customcategories/resources/workproduct_dgm32.gif" nodeicon="customcategories/resources/workproduct_obj.gif">
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZS-0MlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZlSsMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZfMEMlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_6nQ2cJ_5EdyBk-WQzMU-FQ"
+ name="guidance" guid="_6nQ2cJ_5EdyBk-WQzMU-FQ" presentationName="Guidance"
+ shapeicon="customcategories/resources/bookcL.gif" nodeicon="customcategories/resources/bookc.gif">
+ <methodElementProperty xmi:id="_N9ZksJ_6EdyBk-WQzMU-FQ" name="CategoryElementsSortType"
+ value="MethodType"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Checklist" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0Zxf8MlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Checklist" href="uma://_OOB2AAouEdyhlpBPrduOMw#_KZQJMBhBEduxCP6DVVLxsA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0jnYcMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0jzlsMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Checklist" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0Z9tMMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0aDz0MlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0aJ6cMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0kF5kMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0j5sUMlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_z30CYNQvEdyM_J8-fv54DA"
+ name="contributions_to_nav_building_blocks" guid="_z30CYNQvEdyM_J8-fv54DA"
+ presentationName="Contributions to Navigation Building Blocks" categorizedElements="_7pz_ENQvEdyM_J8-fv54DA _LFm-sNQwEdyM_J8-fv54DA"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_7pz_ENQvEdyM_J8-fv54DA"
+ name="practice_list.assign" guid="_7pz_ENQvEdyM_J8-fv54DA" variabilityType="contributes"
+ categorizedElements="_7vvsoJ-lEdyBk-WQzMU-FQ">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCIHY8RdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_LFm-sNQwEdyM_J8-fv54DA"
+ name="technical_practice_list" guid="_LFm-sNQwEdyM_J8-fv54DA" presentationName="Technical Practices"
+ variabilityType="contributes" categorizedElements="_7vvsoJ-lEdyBk-WQzMU-FQ">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_lBrxENQuEdyM_J8-fv54DA"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Hz9OPG5KEdyAHIxjZ9kpqw"
+ name="CoreContent" guid="_Hz9OPG5KEdyAHIxjZ9kpqw">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4GsDkIfxEdy1GthOId7fdw"
+ name="Agile Testing" guid="_4GsDkIfxEdy1GthOId7fdw">
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_0iwc0clgEdmt3adZL5Dmdw"
+ name="create_test_cases" guid="_0iwc0clgEdmt3adZL5Dmdw" briefDescription="Develop the test cases and test data for the requirements to be tested."
+ presentationName="Create Test Cases">
+ <presentation xmi:id="_NrVKsKeqEdmKDbQuyzCoqQ" href="uma://_NrVKsKeqEdmKDbQuyzCoqQ#_NrVKsKeqEdmKDbQuyzCoqQ"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_0jzlsMlgEdmt3adZL5Dmdw"/>
+ <mandatoryInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_i3vkoLS-EduDY8LNbMCDBA"/>
+ <output xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZS-0MlgEdmt3adZL5Dmdw"/>
+ <optionalInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZS-0MlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_0jO98MlgEdmt3adZL5Dmdw"
+ name="implement_tests" guid="_0jO98MlgEdmt3adZL5Dmdw" briefDescription="Implement Test Scripts to validate a Build of the solution. Organize Test Scripts into suites, and collaborate to ensure appropriate depth and breadth of test feedback."
+ presentationName="Implement Tests">
+ <presentation xmi:id="_NrbRUKeqEdmKDbQuyzCoqQ" href="uma://_NrbRUKeqEdmKDbQuyzCoqQ#_NrbRUKeqEdmKDbQuyzCoqQ"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_0jnYcMlgEdmt3adZL5Dmdw"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_0kF5kMlgEdmt3adZL5Dmdw"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_0j5sUMlgEdmt3adZL5Dmdw"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_0jzlsMlgEdmt3adZL5Dmdw"/>
+ <mandatoryInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZS-0MlgEdmt3adZL5Dmdw"/>
+ <output xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZfMEMlgEdmt3adZL5Dmdw"/>
+ <optionalInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZfMEMlgEdmt3adZL5Dmdw"/>
+ <optionalInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_Vux8UEfUEdyiPI8btkmvmw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_0jVEkMlgEdmt3adZL5Dmdw"
+ name="run_tests" guid="_0jVEkMlgEdmt3adZL5Dmdw" briefDescription="Run the appropriate tests scripts, analyze results, articulate issues, and communicate test results to the team."
+ presentationName="Run Tests">
+ <presentation xmi:id="_NrbRUqeqEdmKDbQuyzCoqQ" href="uma://_NrbRUqeqEdmKDbQuyzCoqQ#_NrbRUqeqEdmKDbQuyzCoqQ"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_0kF5kMlgEdmt3adZL5Dmdw"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_0j5sUMlgEdmt3adZL5Dmdw"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_0aDz0MlgEdmt3adZL5Dmdw"/>
+ <mandatoryInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZfMEMlgEdmt3adZL5Dmdw"/>
+ <mandatoryInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_Vux8UEfUEdyiPI8btkmvmw"/>
+ <output xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZlSsMlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Practice" xmi:id="_9z1PgJ6NEdyQN-zRFaRrCQ"
+ name="agile_testing_practice" guid="_9z1PgJ6NEdyQN-zRFaRrCQ" briefDescription="Focus the testing effort where it will provide the greatest value, by applying agile testing principles."
+ presentationName="Agile Testing"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_ZnO2UNEVEdyxxIQodUOrwA"
+ name="technical_test_results_slot.at" guid="_ZnO2UNEVEdyxxIQodUOrwA"
+ variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_fahB0EfUEdyiPI8btkmvmw"/>
+ <containedArtifacts xmi:id="_kC9OUNEVEdyxxIQodUOrwA" name="test_log.at"
+ guid="_kC9OUNEVEdyxxIQodUOrwA" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZlSsMlgEdmt3adZL5Dmdw"/>
+ </containedArtifacts>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_Hz9OPW5KEdyAHIxjZ9kpqw"
+ name="CapabilityPatterns" guid="_Hz9OPW5KEdyAHIxjZ9kpqw"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_Hz9OPm5KEdyAHIxjZ9kpqw"
+ name="DeliveryProcesses" guid="_Hz9OPm5KEdyAHIxjZ9kpqw"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_Hz9OP25KEdyAHIxjZ9kpqw"
+ name="ProcessContributions" guid="_Hz9OP25KEdyAHIxjZ9kpqw"/>
+ <bases href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-gEMXEdyP_Jn83ylwUQ"/>
+ <bases href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPEEKmEdyrauqpmnA8jQ"/>
+ <bases href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2AAouEdyhlpBPrduOMw"/>
+ <bases href="uma://_iVydgENdEdy245g62lfWcA#_iVydgENdEdy245g62lfWcA"/>
+ <bases href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0ELXuEduGP_98XMd0fg"/>
+ <bases href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno4EKmEdyrauqpmnA8jQ"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/practice.tech.agile_testing.base/tasks/create_test_cases.xmi b/praclib/temp/practice.tech.agile_testing.base/tasks/create_test_cases.xmi
new file mode 100644
index 0000000..3969c96
--- /dev/null
+++ b/praclib/temp/practice.tech.agile_testing.base/tasks/create_test_cases.xmi
@@ -0,0 +1,93 @@
+<?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.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="_NrVKsKeqEdmKDbQuyzCoqQ"
+ name="create_test_cases,_0iwc0clgEdmt3adZL5Dmdw" guid="_NrVKsKeqEdmKDbQuyzCoqQ"
+ changeDate="2007-02-07T15:38:57.234-0800" version="1.0.0">
+ <keyConsiderations><p>
+ Develop test cases in parallel with requirements so that Analysts and Stakeholders can agree with the specific
+ conditions of satisfaction for each requirement. The test cases act as acceptance criteria by expanding on the intent
+ of the system&nbsp;through actual scenarios of use.&nbsp;This allows team members to measure progress in terms of
+ passing test cases.&nbsp;
+</p></keyConsiderations>
+ <sections xmi:id="_IJFSsKuSEdmhFZtkg1nakg" name="Review the requirements to be tested"
+ guid="_IJFSsKuSEdmhFZtkg1nakg">
+ <sectionDescription><p>
+ Work with analysts and developers&nbsp;to identify which scenarios and requirements&nbsp;need new or additional test
+ cases. Review the Plans&nbsp;to ensure you understand the scope of development for the current iteration.<br />
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_aDe_ILGcEdubqf8m_Zrvvg" name="Identify relevant Test Cases" guid="_aDe_ILGcEdubqf8m_Zrvvg">
+ <sectionDescription><p>
+ Identify paths through the scenario as unique test conditions.&nbsp; Consider alternative or exception paths from both
+ a positive and negative perspective.&nbsp;&nbsp;Review the test ideas list for patterns of test cases that apply to the
+ scenario.
+</p>
+<p>
+ Discuss the requirement with&nbsp;stakeholders to identify other conditions of satisfaction for the requirement.
+</p>
+<p>
+ List the test cases with a unique name that identifies the condition they evaluate or their expected result.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_LpbM8KuSEdmhFZtkg1nakg" name="Outline the Test Cases" guid="_LpbM8KuSEdmhFZtkg1nakg">
+ <sectionDescription><p>
+ For each test case, write a brief description with an expected result.&nbsp; Ensure that a casual reader can clearly
+ understand the difference between test cases.&nbsp; Note the logical pre-conditions and post-conditions that apply to
+ each test case. Optionally, outline steps for the test case.
+</p>
+<p>
+ Verify that test cases meet the <a class="elementLinkWithType"
+ href="./../../core.tech.common.base/guidances/checklists/test_case_9D3F2E96.html"
+ guid="_0Zxf8MlgEdmt3adZL5Dmdw">Checklist: Test Case</a>&nbsp;guidelines.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_NK18YKuSEdmhFZtkg1nakg" name="Identify test data needs" guid="_NK18YKuSEdmhFZtkg1nakg">
+ <sectionDescription><p>
+ Review each test case and note where data input or output might be required. Identify the type, quantity, and
+ uniqueness of the required data, and add these observations to the test case. Focus on articulating the data needed and
+ not on creating specific data.
+</p>
+<p>
+ For more information on test data selection, see <a class="elementLinkWithType"
+ href="./../../core.tech.common.base/guidances/checklists/test_data_48E804D.html"
+ guid="_KZQJMBhBEduxCP6DVVLxsA">Checklist: Test Data</a>.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_Ok_mMKuSEdmhFZtkg1nakg" name="Share and evaluate the Test Cases"
+ guid="_Ok_mMKuSEdmhFZtkg1nakg">
+ <sectionDescription><p>
+ Walk through the test cases with the analysts and developers&nbsp;responsible for the related
+ scenario.&nbsp;&nbsp;Ideally, the stakeholders will&nbsp;also participate.
+</p>
+<p>
+ Ask the participants to agree that if <em>these test cases pass</em>, they will consider these requirements
+ implemented.&nbsp; Elicit additional test ideas from Analysts and Stakeholders to ensure you understand the expected
+ behavior of the scenario.
+</p>
+<p>
+ During the walkthrough, ensure that:
+</p>
+<ul>
+ <li>
+ The requirements&nbsp;planned for the current iteration have test cases.
+ </li>
+ <li>
+ All the participants agree with the expected results of the test cases.
+ </li>
+ <li>
+ There are no&nbsp;<em>other</em> conditions of satisfaction for the requirement being tested, which indicates
+ either a missing test case or a missing requirement.
+ </li>
+</ul>
+<p>
+ Optionally, capture new patterns of test cases&nbsp;in&nbsp;the test ideas list (see <a class="elementLinkWithType"
+ href="./../../core.tech.common.base/guidances/concepts/test_ideas_ED562B58.html"
+ guid="_0jnYcMlgEdmt3adZL5Dmdw">Concept: Test Ideas</a>).
+</p></sectionDescription>
+ </sections>
+ <purpose><p>
+ To achieve a shared understanding of the specific conditions that the solution must meet.
+</p></purpose>
+</org.eclipse.epf.uma:TaskDescription>
diff --git a/praclib/temp/practice.tech.agile_testing.base/tasks/implement_tests.xmi b/praclib/temp/practice.tech.agile_testing.base/tasks/implement_tests.xmi
new file mode 100644
index 0000000..7da69be
--- /dev/null
+++ b/praclib/temp/practice.tech.agile_testing.base/tasks/implement_tests.xmi
@@ -0,0 +1,108 @@
+<?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.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="_NrbRUKeqEdmKDbQuyzCoqQ"
+ name="implement_tests,_0jO98MlgEdmt3adZL5Dmdw" guid="_NrbRUKeqEdmKDbQuyzCoqQ"
+ changeDate="2007-12-06T14:24:11.609-0800" version="1.0.0">
+ <sections xmi:id="_A56NkKRKEdyLP-jEVj8Kyw" name="Select Test Cases to implement"
+ guid="_A56NkKRKEdyLP-jEVj8Kyw">
+ <sectionDescription><p>
+ Select a set of Test Cases to develop into detailed, executable Test Scripts.&nbsp;
+</p>
+<p>
+ Work with project managers and developers to determine which Test Cases need detailed Test Scripts during the current
+ iteration. At a minimum, select Test Cases for requirements that are planned in the current or next iteration.
+</p>
+<p>
+ Perform each subsequent step in this task for each Test Script.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_WucQ4KRKEdyLP-jEVj8Kyw" name="Design the Test Script" guid="_WucQ4KRKEdyLP-jEVj8Kyw">
+ <sectionDescription><p>
+ Sketch an outline of the Test Script as a logical sequence of steps. Review the data requirements of the Test Case, and
+ determine if existing data sets are sufficient, or if you need to develop new test data for this Test Script. Examine
+ system-wide requirements that apply to this Test Script, and note where they affect the expected results of a step.
+</p>
+<p>
+ If available, review a build that implements the scenario, or demonstrates similar functionality.
+</p>Select an implementation technique for this design. At a minimum, determine if the Test Script will be manual or
+automated. If the Test Case is well understood, it's best to implement an automated Test Script without first writing a
+manual procedure. However, if the Test Case is new or novel, writing a manual Test Script can help validate the design of
+the test and aid collaboration with other team members. See <a class="elementLinkWithType"
+href="./../../core.tech.common.base/guidances/guidelines/programming_automated_tests_7DA10019.html"
+guid="_0j5sUMlgEdmt3adZL5Dmdw">Guideline: Programming Automated Tests</a> for more details about this decision.</sectionDescription>
+ </sections>
+ <sections xmi:id="_VN5M0KuSEdmhFZtkg1nakg" name="Implement the executable Test Script"
+ guid="_VN5M0KuSEdmhFZtkg1nakg">
+ <sectionDescription><p>
+ Develop a detailed, procedural Test Script based on your design. Use a request-response style that declares an exact
+ input, and expects an exact output.
+</p>
+<p>
+ Explain the pre-conditions that must be met before running this Test Script. Use temporary test data or put parameters
+ in your script for data values. Ensure that each post-condition in the Test Case is evaluated by steps in the Test
+ Script.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_WvBoYKuSEdmhFZtkg1nakg" name="Define specific test data" guid="_WvBoYKuSEdmhFZtkg1nakg">
+ <sectionDescription><p>
+ Specify data values that are specific to the Test Script or reference existing test data. For example, instead of
+ specifying "a prime number", indicate an actual value such as "3."
+</p>
+<p>
+ If the Test Script uses a dataset (such as a file or database), add the new test data to it and parameterize the Test
+ Script to retrieve values from the dataset. Otherwise, add executable test data values to the steps of the Test Script.
+ This applies to both manual and automated scripts.
+</p>
+<p>
+ Identify and minimize dependencies between test data used or modified by other Test Scripts. Note dependencies in the
+ Test Script.
+</p>
+<p>
+ If necessary, create containers for your test data sets, and separate the production data from generated data.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_2IA70KRKEdyLP-jEVj8Kyw" name="Organize Test Scripts into suites"
+ guid="_2IA70KRKEdyLP-jEVj8Kyw">
+ <sectionDescription><p>
+ Collect tests into related groups. The grouping you use depends on your test environment. Since the system under test
+ is undergoing its own evolution, create your test suites to facilitate regression testing, as well as system
+ configuration identification.
+</p>
+<p>
+ For help with test suite organization, see <a class="elementLinkWithType"
+ href="./../../core.tech.common.base/guidances/guidelines/test_suite_D54EEBED.html"
+ guid="_0aDz0MlgEdmt3adZL5Dmdw">Guideline: Test Suite</a>.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_X0dmcKuSEdmhFZtkg1nakg" name="Verify Test implementation" guid="_X0dmcKuSEdmhFZtkg1nakg">
+ <sectionDescription><p>
+ Run the Test Script to verify that it implements the Test Case correctly. For manual testing, conduct a walkthrough of
+ the Test Script. For automated tests, verify that the Test Script executes correctly and produces the expected result.
+</p>
+<p>
+ Verify that the Test Script meets the criteria in <a class="elementLinkWithType"
+ href="./../../core.tech.common.base/guidances/checklists/test_script_FBB4524E.html"
+ guid="_0Z9tMMlgEdmt3adZL5Dmdw">Checklist: Test Script</a>.
+</p>
+<p>
+ Add or update the Test Script(s) in configuration management.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_ABwoIKRLEdyLP-jEVj8Kyw" name="Share and evaluate Test Scripts"
+ guid="_ABwoIKRLEdyLP-jEVj8Kyw">
+ <sectionDescription><p>
+ Walk through the new or refined Test Scripts with the developers responsible for the related
+ scenarios.&nbsp;Optionally, the&nbsp;analysts and the stakeholders&nbsp;also participate.
+</p>
+<p>
+ Seek agreement that the Test Scripts correctly evaluate the expected results of the test, and that you understand the
+ implementation of the requirements. If the scenario is already implemented (such as in a developer workspace), walk
+ through a representative set of the Test Scripts using an implementation of the system.
+</p></sectionDescription>
+ </sections>
+ <purpose><p>
+ To implement step-by-step Test Scripts that demonstrate the solution satisfies the requirements.
+</p></purpose>
+</org.eclipse.epf.uma:TaskDescription>
diff --git a/praclib/temp/practice.tech.agile_testing.base/tasks/run_tests.xmi b/praclib/temp/practice.tech.agile_testing.base/tasks/run_tests.xmi
new file mode 100644
index 0000000..202d6bf
--- /dev/null
+++ b/praclib/temp/practice.tech.agile_testing.base/tasks/run_tests.xmi
@@ -0,0 +1,111 @@
+<?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.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="_NrbRUqeqEdmKDbQuyzCoqQ"
+ name="run_tests,_0jVEkMlgEdmt3adZL5Dmdw" guid="_NrbRUqeqEdmKDbQuyzCoqQ" changeDate="2007-12-06T14:34:58.984-0800"
+ version="1.0.0">
+ <keyConsiderations><ul>
+ <li>
+ Run all tests as frequently as possible. Ideally, run all test scripts against each build deployed to the test
+ environment. If this is impractical, run regression tests for existing functionality, and&nbsp;focus the test cycle
+ on work items completed in the new build.
+ </li>
+ <li>
+ Even test scripts that are expected to fail provide valuable feedback. However, once a test script is passing, it
+ should not fail&nbsp;against subsequent builds of the solution.
+ </li>
+</ul></keyConsiderations>
+ <sections xmi:id="_xVhnwKRLEdyLP-jEVj8Kyw" name="Review work items completed in the build"
+ guid="_xVhnwKRLEdyLP-jEVj8Kyw">
+ <sectionDescription>Review work items that were integrated into the build since the last test cycle. Focus on identifying any previously
+unimplemented or failing requirements are now expected to meet the conditions of satisfaction.</sectionDescription>
+ </sections>
+ <sections xmi:id="_1L1yAKRLEdyLP-jEVj8Kyw" name="Select Test Scripts" guid="_1L1yAKRLEdyLP-jEVj8Kyw">
+ <sectionDescription><p>
+ Select test scripts related to work items completed in the build.
+</p>
+<p>
+ Ideally, each test cycle should execute all test scripts, but some types of tests are too time-consuming to include in
+ each test cycle. For manual or time-intensive tests, include test scripts that will provide the most useful feedback
+ about the maturing solution based on the objectives of the iteration.
+</p>
+<p>
+ Plan with test suites to&nbsp;simplify the process of selecting tests for each build (see <a
+ class="elementLinkWithType" href="./../../core.tech.common.base/guidances/guidelines/test_suite_D54EEBED.html"
+ guid="_0aDz0MlgEdmt3adZL5Dmdw">Guideline: Test Suite</a>).
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_gV408KuSEdmhFZtkg1nakg" name="Execute Test Scripts against the build"
+ guid="_gV408KuSEdmhFZtkg1nakg">
+ <sectionDescription><p>
+ Run the tests using the step-by-step procedure in the <a class="elementLink"
+ href="./../../core.tech.common.base/workproducts/test_script_39A30BA2.html" guid="_0ZfMEMlgEdmt3adZL5Dmdw">Test
+ Script</a>.
+</p>
+<p>
+ For automated test scripts, initiate the test execution.&nbsp;Automated test scripts should run in suites in the
+ correct sequence, and collect results in the Test Log.
+</p>
+<p>
+ To execute a manual test script, establish its preconditions, perform the steps while logging results in the <a
+ class="elementLink" href="./../../core.tech.common.base/workproducts/test_log_CBA2FDF4.html"
+ guid="_0ZlSsMlgEdmt3adZL5Dmdw">Test Log</a>, and perform any teardown steps.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_sQaC4DO2EduqsLmIADMQ9g" name="Analyze and communicate test results"
+ guid="_sQaC4DO2EduqsLmIADMQ9g">
+ <sectionDescription><p>
+ Post the test results in a conspicuous place that is accessible to the entire team, such as a white board or wiki.
+</p>
+<p>
+ For each failing test script, analyze the Test Log to identify the cause of the test failure. Begin with failing tests
+ that you expected to begin passing against this build, which may indicate newly delivered work items that do not meet
+ the conditions of satisfaction. Then review previously passing test scripts that are now failing, which may indicate
+ regressive issues in the build.
+</p>
+<ul>
+ <li>
+ If a test failed because the solution does not meet the conditions of satisfaction for the test case, log the issue
+ in the Work Items List. In the work item, clearly identify the observed behavior, the expected behavior, and steps
+ to repeat the issue. Note which failing test initially discovered the issue.
+ </li>
+ <li>
+ If a test failed because of a change in the system (such as a user-interface change), but the implementation still
+ meets the conditions of satisfaction in the test case, update the test script to pass with the new implementation.
+ </li>
+ <li>
+ If a test failed because the test script is incorrect (a false negative result) or passed when it was expected to
+ fail (a false positive result), update the test script to correctly implement the conditions of satisfaction in the
+ test case. If the test case for a requirement is invalid, create a request change to modify the conditions of
+ satisfaction for the requirement.&nbsp;
+ </li>
+</ul>
+<p>
+ It's best to update test scripts as quickly and continuously as possible. If the change to the test script is trivial,
+ update the test while analyzing the test results. If the change is a non-trivial task, submit it to the Work Items List
+ so it can be prioritized against other tasks.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_3t6oADO2EduqsLmIADMQ9g" name="Provide feedback to the team" guid="_3t6oADO2EduqsLmIADMQ9g">
+ <sectionDescription><p>
+ Summarize and provide feedback to the team about how well the build satisfies the requirements planned to the
+ iteration. Focus on measuring progress in terms of passing tests.
+</p>
+<p>
+ Explain the results for the test cycle&nbsp;in the context of overall trends:
+</p>
+<ul>
+ <li>
+ How many tests were selected for the build, and what&nbsp;are their statuses (pass, fail, blocked, not run, etc.)?
+ </li>
+ <li>
+ How many issues were added to the Work Items List, and what are their statuses and severities?
+ </li>
+ <li>
+ For test scripts that were blocked or skipped, what are the main reasons (such as known issues)?
+ </li>
+</ul></sectionDescription>
+ </sections>
+ <purpose>To provide feedback to the team about how well a build satisfies the requirements.</purpose>
+</org.eclipse.epf.uma:TaskDescription>
diff --git a/praclib/temp/practice.tech.continuous_integration.assign/.project b/praclib/temp/practice.tech.continuous_integration.assign/.project
new file mode 100644
index 0000000..ec77d7f
--- /dev/null
+++ b/praclib/temp/practice.tech.continuous_integration.assign/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>practice.tech.continuous_integration.assign</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/practice.tech.continuous_integration.assign/plugin.xmi b/praclib/temp/practice.tech.continuous_integration.assign/plugin.xmi
new file mode 100644
index 0000000..793c273
--- /dev/null
+++ b/praclib/temp/practice.tech.continuous_integration.assign/plugin.xmi
@@ -0,0 +1,78 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_iADyQM3PEdyKkus0T68H3Q"
+ guid="_iADyQM3PEdyKkus0T68H3Q"/>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_h_9roM3PEdyKkus0T68H3Q" name="practice.tech.continuous_integration.assign"
+ guid="_h_9roM3PEdyKkus0T68H3Q" briefDescription="Assignments for Continuous Integration practice"
+ authors="Jim Ruehlin" changeDate="2008-01-28T10:48:34.971-0800">
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_h_9roc3PEdyKkus0T68H3Q"
+ name="Content" guid="_h_9roc3PEdyKkus0T68H3Q">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_h_9ros3PEdyKkus0T68H3Q"
+ name="Categories" guid="_h_9ros3PEdyKkus0T68H3Q">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_h_9ro83PEdyKkus0T68H3Q"
+ name="Domains" guid="_h_9ro83PEdyKkus0T68H3Q">
+ <contentElements xsi:type="org.eclipse.epf.uma:Domain" xmi:id="_ygcwgM3REdyKkus0T68H3Q"
+ name="development_domain.assign" guid="_ygcwgM3REdyKkus0T68H3Q" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Domain" href="uma://_MRPloEFXEdy9ENCpSugIjA#_5JQLoK80Edy9cPK11VzBuQ"/>
+ <workProducts xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_0YuXEMlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_h_9rpM3PEdyKkus0T68H3Q"
+ name="Disciplines" guid="_h_9rpM3PEdyKkus0T68H3Q">
+ <contentElements xsi:type="org.eclipse.epf.uma:Discipline" xmi:id="_8c5BwNnVEdyNj6EOmqy5Rg"
+ name="development.assign" guid="_8c5BwNnVEdyNj6EOmqy5Rg" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Discipline" href="uma://_MRPloEFXEdy9ENCpSugIjA#_iGSHsVZ-EdyIUdvDLLUdeg"/>
+ <tasks href="uma://_D-ExQMktEdygFZkm1d5NtQ#_kkZBgJOKEdyaRbFYa4AN4A"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_h_9rpc3PEdyKkus0T68H3Q"
+ name="RoleSets" guid="_h_9rpc3PEdyKkus0T68H3Q"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_h_9rps3PEdyKkus0T68H3Q"
+ name="WP Types" guid="_h_9rps3PEdyKkus0T68H3Q"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_h_9rp83PEdyKkus0T68H3Q"
+ name="Tools" guid="_h_9rp83PEdyKkus0T68H3Q"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_h_9rqM3PEdyKkus0T68H3Q"
+ name="StandardCategories" guid="_h_9rqM3PEdyKkus0T68H3Q"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_h_9rqc3PEdyKkus0T68H3Q"
+ name="CustomCategories" guid="_h_9rqc3PEdyKkus0T68H3Q">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_h_9rqs3PEdyKkus0T68H3Q"
+ name="Hidden" guid="_h_9rqs3PEdyKkus0T68H3Q">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_h_9rq83PEdyKkus0T68H3Q"
+ name="Custom Categories" guid="_h_9rq83PEdyKkus0T68H3Q"/>
+ </childPackages>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_h_9rrM3PEdyKkus0T68H3Q"
+ name="CoreContent" guid="_h_9rrM3PEdyKkus0T68H3Q">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_fTBSUM3REdyKkus0T68H3Q"
+ name="Role Assignments" guid="_fTBSUM3REdyKkus0T68H3Q">
+ <contentElements xsi:type="org.eclipse.epf.uma:Role" xmi:id="_gwhLEM3REdyKkus0T68H3Q"
+ name="developer.assign_wp" guid="_gwhLEM3REdyKkus0T68H3Q" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Role" href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
+ <responsibleFor xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_0YuXEMlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_2Xt1QNm_EdyzZqGyZ7hwdw"
+ name="integrate_and_create_build.assign_role" guid="_2Xt1QNm_EdyzZqGyZ7hwdw"
+ variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Task" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_kkZBgJOKEdyaRbFYa4AN4A"/>
+ <performedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_h_9rrc3PEdyKkus0T68H3Q"
+ name="CapabilityPatterns" guid="_h_9rrc3PEdyKkus0T68H3Q"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_h_9rrs3PEdyKkus0T68H3Q"
+ name="DeliveryProcesses" guid="_h_9rrs3PEdyKkus0T68H3Q"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_h_9rr83PEdyKkus0T68H3Q"
+ name="ProcessContributions" guid="_h_9rr83PEdyKkus0T68H3Q"/>
+ <bases href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExQMktEdygFZkm1d5NtQ"/>
+ <bases href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPloEFXEdy9ENCpSugIjA"/>
+ <bases href="uma://_A118oMYaEdyXeo04os5BOw#_A118oMYaEdyXeo04os5BOw"/>
+ <bases href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVEMYbEdyXeo04os5BOw"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/practice.tech.continuous_integration.base/.project b/praclib/temp/practice.tech.continuous_integration.base/.project
new file mode 100644
index 0000000..ba0bb68
--- /dev/null
+++ b/praclib/temp/practice.tech.continuous_integration.base/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>practice.tech.continuous_integration.base</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/practice.tech.continuous_integration.base/customcategories/resources/pract_dgm32.gif b/praclib/temp/practice.tech.continuous_integration.base/customcategories/resources/pract_dgm32.gif
new file mode 100644
index 0000000..f597332
--- /dev/null
+++ b/praclib/temp/practice.tech.continuous_integration.base/customcategories/resources/pract_dgm32.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.continuous_integration.base/customcategories/resources/pract_obj.gif b/praclib/temp/practice.tech.continuous_integration.base/customcategories/resources/pract_obj.gif
new file mode 100644
index 0000000..fe8075a
--- /dev/null
+++ b/praclib/temp/practice.tech.continuous_integration.base/customcategories/resources/pract_obj.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.continuous_integration.base/guidances/concepts/change_requests.xmi b/praclib/temp/practice.tech.continuous_integration.base/guidances/concepts/change_requests.xmi
new file mode 100644
index 0000000..d898329
--- /dev/null
+++ b/praclib/temp/practice.tech.continuous_integration.base/guidances/concepts/change_requests.xmi
@@ -0,0 +1,20 @@
+<?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: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="-BsXK3ZGMm-mUT0KnkdoYBg"
+ name="change_requests,_6jdvECb3Edqh1LYUOGRh2A" guid="-BsXK3ZGMm-mUT0KnkdoYBg"
+ changeDate="2007-02-22T12:13:54.919-0800">
+ <mainDescription><p>
+ A change request represents any request to change a work product. This includes items commonly called defect reports,
+ enhancement requests, requirements change request, implementation requests, and stakeholder requests.
+</p>
+<p>
+ In this process, change request are captured in the <a class="elementLinkWithType"
+ href="./../../../opn.swd.prac.legacy_pm/workproducts/work_items_list_39D03CC8.html"
+ guid="_rGNWsCbSEdqh1LYUOGRh2A">Artifact: Work Items List</a>.&nbsp; See <a class="elementLinkWithType"
+ href="./../../../core.tech.slot.base/guidances/guidelines/work_items_list_32AC6ABD.html"
+ guid="_7vEXEMA4EdqSgKaj2SZBmg">Guideline: Work Items List</a>&nbsp;for more information on the recommended
+ attributes&nbsp;of change requests.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.continuous_integration.base/guidances/concepts/change_set.xmi b/praclib/temp/practice.tech.continuous_integration.base/guidances/concepts/change_set.xmi
new file mode 100644
index 0000000..8b4f98c
--- /dev/null
+++ b/praclib/temp/practice.tech.continuous_integration.base/guidances/concepts/change_set.xmi
@@ -0,0 +1,40 @@
+<?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="-QpMXBM5_A8w0pRyIT5n5yA"
+ name="change_set,_1QU9MAIoEdyLh7vsrHZ4YA" guid="-QpMXBM5_A8w0pRyIT5n5yA" changeDate="2007-05-31T19:18:27.346-0400">
+ <mainDescription><p>
+ A change set is a logical grouping of related changes made to the implementation and supporting artifacts. Change sets
+ are defined for a specific purpose and encompass all changes made to achieve that purpose.
+</p>
+<p>
+ Change sets allow for multiple related changes to be referred to as single item, simplifying tracking of&nbsp;that
+ item’s progress through the development lifecycle.
+</p>
+<p>
+ The change set forms the basic unit of configuration control, accountability, and collaboration on the development
+ team.&nbsp; Additionally, change sets track the dependencies between artifact changes that facilitate discovery and
+ correction of configuration inconsistencies. The relationship between items in a change set can be used to verify that
+ all related changes have been included in a build.
+</p>
+<p>
+ Change sets have the following characteristics:
+</p>
+<ol>
+ <li>
+ Change sets consist of changes that belong together and can be built and tested together.
+ </li>
+ <li>
+ Change sets are owned by a single developer.
+ </li>
+ <li>
+ Change sets represent small, testable changes to the system.
+ </li>
+</ol>
+<p>
+ Multiple change sets&nbsp;may be&nbsp;related to&nbsp;a single work item.
+</p>
+<p>
+ Change sets are also known as CM tasks, activity change sets, change lists or change packages.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.continuous_integration.base/guidances/concepts/continuous_integration.xmi b/praclib/temp/practice.tech.continuous_integration.base/guidances/concepts/continuous_integration.xmi
new file mode 100644
index 0000000..2223d8c
--- /dev/null
+++ b/praclib/temp/practice.tech.continuous_integration.base/guidances/concepts/continuous_integration.xmi
@@ -0,0 +1,51 @@
+<?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="-dhAMzNZNWufBnW0fPYQtBA"
+ name="continuous_integration,_NApSVdtxEdq7ovUqqSoGBQ" guid="-dhAMzNZNWufBnW0fPYQtBA"
+ changeDate="2007-06-14T10:04:57.895-0700">
+ <mainDescription><p>
+ Continuous integration is an implementation practice where team members integrate their work with completed&nbsp;<a class="elementLink" href="./../../../openup/guidances/concepts/change_set_430BF233.html" guid="_1QU9MAIoEdyLh7vsrHZ4YA">Change Set</a>s from other developers, and test the application, before making their
+ work available to others. This&nbsp;enables detection of&nbsp;integration errors&nbsp;as&nbsp;early as possible, either
+ from compiler errors,&nbsp;configuration management&nbsp;system notifications,&nbsp;or&nbsp;failures reported by the
+ test suite. Ideally the integration is done automatically prior to <a class="elementLink" href="./../../../openup/guidances/guidelines/promoting_changes_9087B764.html" guid="_SM4YIL6dEdqti4GwqTkbsQ">Promoting Changes</a>.
+</p>
+<p>
+ Continuous integration provides the following benefits:
+</p>
+<ol>
+ <li>
+ Improved feedback. Continuous integration shows constant and demonstrable progress.
+ </li>
+ <li>
+ Improved error detection. Continuous integration enables you to detect and address errors early, often minutes
+ after they’ve been injected into the product. Effective continuous integration requires automated unit testing with
+ appropriate code coverage.
+ </li>
+ <li>
+ Improved collaboration. Continuous integration enables team members to work together safely. They know that they
+ can make a change to their code, integrate the system, and determine very quickly whether or not their change
+ conflicts with others.
+ </li>
+ <li>
+ Improved system integration. By integrating continuously throughout your project you know that you can actually
+ build the system, thereby mitigating integration surprises at the end of the lifecycle.
+ </li>
+ <li>
+ Reduced&nbsp;number of parallel changes that need to be merged and tested.
+ </li>
+ <li>
+ Reduced number of errors found during system testing. All conflicts&nbsp;are resolved prior to making new change
+ sets available, by the person who is in the best position to resolve them.
+ </li>
+ <li>
+ Reduced technical risk. You always have an up-to-date system against which to test.
+ </li>
+ <li>
+ Reduced management risk. By continuously integrating your system you know exactly how much functionality that
+ you’ve built to date, improving your ability to predict when and if you’re actually going to be able to deliver the
+ necessary functionality.
+ </li>
+</ol></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.continuous_integration.base/guidances/concepts/workspace.xmi b/praclib/temp/practice.tech.continuous_integration.base/guidances/concepts/workspace.xmi
new file mode 100644
index 0000000..76651ad
--- /dev/null
+++ b/praclib/temp/practice.tech.continuous_integration.base/guidances/concepts/workspace.xmi
@@ -0,0 +1,57 @@
+<?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: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="_Dfmk8MPiEdmbOvqy4O0adg"
+ name="workspace,_0cEmAMlgEdmt3adZL5Dmdw" guid="_Dfmk8MPiEdmbOvqy4O0adg" changeDate="2006-09-21T12:22:51.449-0700"
+ version="1.0.0">
+ <mainDescription><p align="left">
+ On small teams, shared workspaces may work fine, but you must coordinate activities between team members to avoid
+ conflicts.
+</p>
+<p align="left">
+ A better approach is for each developer to have a reasonably private area for the development and testing of their work
+ products. This workspace should be insulated&nbsp;so that destabilizing or conflicting changes made by others do not
+ interfere with&nbsp;progress. However, it should&nbsp;not be isolated to the extent that&nbsp;the developer's work is
+ unavailable to the team.
+</p>
+<p align="left">
+ In addition, insulated&nbsp;workspaces can be created for each test phase, such as integration testing and system
+ testing. This approach to workspaces provides several benefits <a class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/references_6CCF393.html"
+ guid="_9ToeIB83Edqsvps02rpOOg">[WIB04]</a>:
+</p>
+<ul>
+ <li>
+ <p>
+ Developers can develop, test, and debug software changes without being affected by others team
+ members'&nbsp;changes until they are ready. When ready, developers can update their insulated environments to
+ test the latest changes from other developers.
+ </p>
+ </li>
+ <li>
+ <p>
+ With separate workspaces for integration and system testing, a team could use a methodology that ensures
+ changes have passed integration testing before other developers get them, thereby minimizing the time spent
+ solving integration problems.&nbsp; For example, if two team members check in incompatible changes without
+ realizing it, and both changes are immediately available to everyone on the team, all team members&nbsp;might
+ waste time trying to resolve the broken build. Conversely, if both changes must pass integration testing before
+ being distributed to others, the problem could be found and fixed by one person with minimal disruption to the
+ team.
+ </p>
+ </li>
+ <li>
+ <p>
+ By setting up an integration area to collect and build the latest changes, the team can integrate early and
+ often. That is a well-known best practice for reducing overall cost and time to deliver software projects.
+ </p>
+ </li>
+ <li>
+ <p>
+ The system test area, which is used for preparing releases, is insulated from developers' ongoing changes and
+ contains only configurations that have passed integration testing. This lets you control the content of the
+ release while still enabling developers to continue working.
+ </p>
+ </li>
+</ul></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.continuous_integration.base/guidances/guidelines/continuous_integration.xmi b/praclib/temp/practice.tech.continuous_integration.base/guidances/guidelines/continuous_integration.xmi
new file mode 100644
index 0000000..740903f
--- /dev/null
+++ b/praclib/temp/practice.tech.continuous_integration.base/guidances/guidelines/continuous_integration.xmi
@@ -0,0 +1,79 @@
+<?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="-DlaqJu4sEqMPk84qhJ6IEA"
+ name="continuous_integration,_i8bUEL6cEdqti4GwqTkbsQ" guid="-DlaqJu4sEqMPk84qhJ6IEA"
+ changeDate="2007-07-18T05:02:20.454-0700">
+ <mainDescription><p>
+ Continuous integration is a software development practice that completely rebuilds and tests the application frequently
+ -- ideally, every time a change is introduced. This approach provides many benefits as outlined in <a class="elementLinkWithType" href="./../../../openup/guidances/concepts/continuous_integration_87682D06.html" guid="_B3xkEPD0EdqYgerqi84oCA">Concept: Continuous Integration</a> and in <a class="elementLinkWithUserText" href="./../../../openup/guidances/supportingmaterials/references_6CCF393.html#WIKP-CI" guid="_9ToeIB83Edqsvps02rpOOg">[WIKP-CI]</a>.
+</p>
+<h3>
+ Basic steps
+</h3>
+<p>
+ The detailed application of continuous integration depends on which tools you use (configuration management system,
+ automated build tool, automated test tool, and so forth). However, these are the basic steps:
+</p>
+<ol>
+ <li>
+ A developer, let’s call her Jane, selects a&nbsp;work item&nbsp;to work on.
+ </li>
+ <li>
+ Jane updates her <a class="elementLink" href="./../../../openup/guidances/concepts/workspace_722BBA90.html" guid="_0cEmAMlgEdmt3adZL5Dmdw">Workspace</a> to include the most recent <a class="elementLink" href="./../../../openup/workproducts/implementation_917CA61E.html" guid="_0YoQcMlgEdmt3adZL5Dmdw">Implementation</a> from
+ the integration workspace.
+ </li>
+ <li>
+ Jane makes her changes in her workspace to both her developer tests and to the implementation, and then she tests
+ the changes.
+ </li>
+ <li>
+ Before committing the changes, Jane updates her workspace again (because other developers may have introduced
+ conflicting changes) and reruns her developer tests.
+ </li>
+ <li>
+ If these tests are successful, the changes are promoted (see <a class="elementLinkWithType" href="./../../../openup/guidances/guidelines/promoting_changes_9087B764.html" guid="_SM4YIL6dEdqti4GwqTkbsQ">Guideline: Promoting Changes</a>) to&nbsp;the&nbsp;integration workspace.
+ </li>
+ <li>
+ A complete <a class="elementLink" href="./../../../openup/workproducts/build_95D7D8FD.html" guid="_0YuXEMlgEdmt3adZL5Dmdw">Build</a> of the application is performed by using the implementation from the
+ integration workspace, and the entire suite of developer tests is run on this build.
+ </li>
+ <li>
+ If any of these tests fail, the team is notified, and the failed test should be addressed as soon as possible.
+ </li>
+ <li>
+ This process repeats as the team develops and continuously integrates and tests functionality in small increments.
+ </li>
+</ol>
+<h3>
+ Constraints
+</h3>
+<p>
+ Conceptually, continuous integration can be performed manually (see <a class="elementLinkWithUserText" href="./../../../openup/guidances/supportingmaterials/references_6CCF393.html#SHO06" guid="_9ToeIB83Edqsvps02rpOOg">[SHO06]</a>
+ for example). However, in practice, there are several constraints that must be respected for it to be effective:
+</p>
+<ol>
+ <li>
+ All changes must be introduced into a tested configuration that you know to be good.
+ </li>
+ <li>
+ The integrate-build-test cycle must be fast enough so that it can be completed quickly and the team notified of the
+ results. Many published guidelines promote a 10-minute cycle.
+ </li>
+ <li>
+ Keep the <a class="elementLink" href="./../../../openup/guidances/concepts/change_set_430BF233.html" guid="_1QU9MAIoEdyLh7vsrHZ4YA">Change Set</a>s&nbsp;small enough so that the work can be completed and integration
+ performed several times per day. Many published guidelines promote a 2- to 4-hour cycle between integrations.
+ </li>
+</ol>
+<p>
+ These constraints imply the need for a configuration management (CM) repository to maintain configuration information
+ (Item 1 listed previously), automated build and test tools to meet the turnaround constraints (Item 2), and proper
+ planning and discipline by developers to ensure that their work items and change sets are small enough to complete
+ quickly (Item 3).
+</p>
+<p>
+ For a more detailed description of continuous integration, see <a class="elementLinkWithUserText" href="./../../../openup/guidances/supportingmaterials/references_6CCF393.html#FOW06" guid="_9ToeIB83Edqsvps02rpOOg">[FOW06]</a>
+ or <a class="elementLinkWithUserText" href="./../../../openup/guidances/supportingmaterials/references_6CCF393.html#WIKP-CI" guid="_9ToeIB83Edqsvps02rpOOg">[WIKP-CI]</a>.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.continuous_integration.base/guidances/guidelines/promoting_changes.xmi b/praclib/temp/practice.tech.continuous_integration.base/guidances/guidelines/promoting_changes.xmi
new file mode 100644
index 0000000..6225fd1
--- /dev/null
+++ b/praclib/temp/practice.tech.continuous_integration.base/guidances/guidelines/promoting_changes.xmi
@@ -0,0 +1,101 @@
+<?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: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="-zCM2ucJJxc_bQr_LoHlSaQ"
+ name="promoting_changes,_SM4YIL6dEdqti4GwqTkbsQ" guid="-zCM2ucJJxc_bQr_LoHlSaQ"
+ changeDate="2007-08-04T07:54:07.000-0400" version="1.0.0">
+ <mainDescription><p>
+ During iterative software development, the team&nbsp;creates numerous <a class="elementLink"
+ href="./resources/change_set_430BF233.html" guid="_1QU9MAIoEdyLh7vsrHZ4YA">Change Set</a>s that are combined into a <a
+ class="elementLink" href="./../../../opn.swd.prac.legacy_impl/workproducts/build_95D7D8FD.html"
+ guid="_0YuXEMlgEdmt3adZL5Dmdw">Build</a>. A build is initiated by combining the work completed by one or more
+ developers and resolving any conflicts between those changes. Ideally a build is then subjected to a battery of tests
+ to determine if it is of sufficient quality to move into production.
+</p>
+<p>
+ As the changes progress from development towards production, its beneficial to know two characteristics:
+</p>
+<p>
+ <strong>Test Context</strong>&nbsp;– identifying the elements and their versions that are tested together
+</p>
+<ul>
+ <li>
+ What changes are in this build (completed work items)
+ </li>
+ <li>
+ What&nbsp;changes are&nbsp;partially in this build (work items that are partially complete)
+ </li>
+ <li>
+ What changes are&nbsp;not in this build (work items that are not reflected at all in this build)
+ </li>
+</ul>
+<p>
+ <strong>Verification Level</strong> – identifying what amount of testing is complete.&nbsp; For example,
+</p>
+<ul>
+ <li>
+ Unit Tested
+ </li>
+ <li>
+ Integration Tested
+ </li>
+ <li>
+ System Tested
+ </li>
+</ul>
+<p>
+ The promotion lifecycle coordinates and synchronizes the efforts of the development team. This lifecycle consists of
+ the following steps:
+</p>
+<ul>
+ <li>
+ Changes are introduced into the system in the form of completed&nbsp;<a class="elementLink"
+ href="./resources/change_set_430BF233.html" guid="_1QU9MAIoEdyLh7vsrHZ4YA">Change Set</a>s
+ </li>
+ <li>
+ A build is generated clearly identifying the&nbsp;changes included in the build
+ </li>
+ <li>
+ Testing is conducted
+ </li>
+ <li>
+ When testing is successful the changes are marked with the appropriate&nbsp;verification level through labeling,
+ baselining or other related techniques.
+ </li>
+</ul>
+<p>
+ Ultimately all required testing is complete and a new system&nbsp;increment is ready.
+</p>
+<p>
+ Separate&nbsp;<a class="elementLink"
+ href="./../../../opn.swd.prac.legacy_pm/guidances/concepts/workspace_722BBA90.html"
+ guid="_0cEmAMlgEdmt3adZL5Dmdw">Workspace</a>s are often used as the context for each level of testing. As changes are
+ added to the <a class="elementLink" href="./../../../opn.swd.prac.legacy_pm/guidances/concepts/workspace_722BBA90.html"
+ guid="_0cEmAMlgEdmt3adZL5Dmdw">Workspace</a>, it is verified for consistency and tested. This ensures that the effort
+ of testing a build is applied to the correct&nbsp;set of changes, makes the context for the tests stable,&nbsp;and also
+ allows developers to continue working on the next build while the tests are being conducted.
+</p>
+<p>
+ A change promotion lifecycle such as this offers three key benefits
+</p>
+<ol>
+ <li>
+ Reduces effort because there is no reason to execute the tests in the next stages until the&nbsp;changes passes the
+ previous stage. For example you would not commit the resources to&nbsp;system testing a build until it
+ passes&nbsp;developer tests.
+ </li>
+ <li>
+ Helps to ensure that a change&nbsp;which is moved into production has been subjected to the appropriate level of
+ testing first.
+ </li>
+ <li>
+ Simplifies debugging since developers can base their work on a proven&nbsp;set of changes&nbsp;in relative
+ isolation from destabilizing changes from other developers
+ </li>
+</ol>
+<p>
+ For an example of this approach see <a href="http://www.agiledata.org/essays/sandboxes.html"
+ target="_blank" >Development Sandboxes: An Agile "Best" Practice.</a>
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.continuous_integration.base/guidances/guidelines/submitting_change_requests.xmi b/praclib/temp/practice.tech.continuous_integration.base/guidances/guidelines/submitting_change_requests.xmi
new file mode 100644
index 0000000..e706e81
--- /dev/null
+++ b/praclib/temp/practice.tech.continuous_integration.base/guidances/guidelines/submitting_change_requests.xmi
@@ -0,0 +1,70 @@
+<?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: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="-w7sImtXWkf4HDXdUWjRsUg"
+ name="new_guideline,_fnZj0NVXEdqy9sbRhejO5Q" guid="-w7sImtXWkf4HDXdUWjRsUg" authors="Chris Sibbald"
+ changeDate="2007-02-26T10:52:05.226-0800" changeDescription="Moved content from previous concept:change request to this guideline and updated in accordance with discussion from April 18, 2006 telecon."
+ version="0.2">
+ <mainDescription><h3>
+ Background
+</h3>
+<p>
+ Change requests typically have a lifecycle. They are raised,&nbsp;reviewed, accepted or rejected, implemented, verified
+ and closed. These states define the status of the change request at a particular point in time and represent critical
+ information for tracking progress. Other sets of states are possible.
+</p>
+<p>
+ During review of a change request, the goal&nbsp;is to assess the&nbsp;technical, cost, and schedule impact
+ of&nbsp;implementing the change.&nbsp; The technical impact&nbsp;assessment includes&nbsp;the determination of
+ which&nbsp;work products&nbsp;are affected and an estimate of the level of effort required to change and verify all
+ affected artifacts. This information becomes the basis of the cost and schedule impact assessments and, ultimately,
+ whether the change request will be accepted or rejected.
+</p>
+<p>
+ If accepted, the implementation and verification of the change request will be assigned to an iteration in the same
+ manner as any other work item.
+</p>
+<p>
+ The&nbsp;current process uses the <a class="elementLinkWithType"
+ href="./../../../opn.swd.prac.legacy_pm/workproducts/work_items_list_39D03CC8.html"
+ guid="_rGNWsCbSEdqh1LYUOGRh2A">Artifact: Work Items List</a> to capture, prioritize, and track the change requests
+ using the attributes defined for that artifact.
+</p>
+<h3>
+ Submitting Change Requests
+</h3>
+<p>
+ When submitting a change request provide as much information as possible to enable a speedy review and
+ disposition.&nbsp; As a minimum, all change requests should include the following information:
+</p>
+<ul>
+ <li>
+ <strong>ID</strong> - a unique identifier for the change request to simplify tracking.&nbsp; If you are using some
+ form of change tracking tool the tool will assign a unique ID.
+ </li>
+ <li>
+ <strong>Brief Description</strong>&nbsp;- a name that summarizes the change request
+ </li>
+ <li>
+ <strong>Detailed Description</strong> - A detailed description of the change request.&nbsp; For a defect, if you
+ can provide information that will help reproduce the defect please do so.&nbsp; For an enhancement request, provide
+ a rationale for the request.
+ </li>
+ <li>
+ <strong>Affected Item</strong>&nbsp;- the affected artifact and version.
+ </li>
+ <li>
+ <strong>Severity</strong> - how severe is this issue (show stopper, nice to have, etc.).
+ </li>
+ <li>
+ <strong>Priority</strong> - how important it is this request in your opinion.
+ </li>
+</ul>
+<p>
+ Depending upon the system you are using, the names of these data elements may differ.&nbsp; However, this information
+ is required, in one form or another, to permit a speedy review and disposition of the change request.
+</p><br />
+<br />
+<br /></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.continuous_integration.base/guidances/supportingmaterials/release_info_continuous_integration.xmi b/praclib/temp/practice.tech.continuous_integration.base/guidances/supportingmaterials/release_info_continuous_integration.xmi
new file mode 100644
index 0000000..9e52a80
--- /dev/null
+++ b/praclib/temp/practice.tech.continuous_integration.base/guidances/supportingmaterials/release_info_continuous_integration.xmi
@@ -0,0 +1,21 @@
+<?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="-_P9JU4M-5_0FI_g7_EGi6g"
+ name=",_NWZp0M3TEdyKkus0T68H3Q" guid="-_P9JU4M-5_0FI_g7_EGi6g" changeDate="2008-01-28T11:00:14.698-0800">
+ <mainDescription><h3>
+ Continuous Integration Practice
+</h3>
+<p>
+ Version 1.0
+</p>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p>
+ [*** NOT YET RELEASED ***]
+ </p>
+ <p>
+ This is the initial release of this practice.
+ </p>
+</blockquote></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.continuous_integration.base/guidances/termdefinitions/configuration.xmi b/praclib/temp/practice.tech.continuous_integration.base/guidances/termdefinitions/configuration.xmi
new file mode 100644
index 0000000..aacda09
--- /dev/null
+++ b/praclib/temp/practice.tech.continuous_integration.base/guidances/termdefinitions/configuration.xmi
@@ -0,0 +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: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="-VPoMu7qzVX9grE4-nB3kMw"
+ name=",__Cw30ElxEducWJcS4yanqg" guid="-VPoMu7qzVX9grE4-nB3kMw" changeDate="2006-09-21T06:07:10.404-0700">
+ <mainDescription>The performance, functional, and physical attributes of an existing or planned product, or a combination of products.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.continuous_integration.base/guidances/termdefinitions/version.xmi b/praclib/temp/practice.tech.continuous_integration.base/guidances/termdefinitions/version.xmi
new file mode 100644
index 0000000..c2b72d4
--- /dev/null
+++ b/praclib/temp/practice.tech.continuous_integration.base/guidances/termdefinitions/version.xmi
@@ -0,0 +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: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="-4iL0UEFR2Fg7oWkh1TymIg"
+ name=",_eX8K8ElyEducWJcS4yanqg" guid="-4iL0UEFR2Fg7oWkh1TymIg" changeDate="2006-09-21T06:10:30.780-0700">
+ <mainDescription>A variant of some artifact; later versions of an artifact typically expand upon earlier versions.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.continuous_integration.base/plugin.xmi b/praclib/temp/practice.tech.continuous_integration.base/plugin.xmi
new file mode 100644
index 0000000..2135e14
--- /dev/null
+++ b/praclib/temp/practice.tech.continuous_integration.base/plugin.xmi
@@ -0,0 +1,194 @@
+<?xml version="1.0" encoding="UTF-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.4/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.2.0" xmlns:epf="http://www.eclipse.org/epf"
+ epf:version="1.2.0">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_D_3hAMktEdygFZkm1d5NtQ"
+ guid="_D_3hAMktEdygFZkm1d5NtQ">
+ <resourceDescriptors xmi:id="_svkl0PD0EdqYgerqi84oCA" id="-DlaqJu4sEqMPk84qhJ6IEA"
+ uri="guidances/guidelines/continuous_integration.xmi"/>
+ <resourceDescriptors xmi:id="_B5BhQPD0EdqYgerqi84oCA" id="-dhAMzNZNWufBnW0fPYQtBA"
+ uri="guidances/concepts/continuous_integration.xmi"/>
+ <resourceDescriptors xmi:id="_m_KBAPL5Edm6Nvont3uinw" id="_NqSB0KeqEdmKDbQuyzCoqQ"
+ uri="workproducts/build.xmi"/>
+ <resourceDescriptors xmi:id="_SeEuQc3TEdyKkus0T68H3Q" id="-_P9JU4M-5_0FI_g7_EGi6g"
+ uri="guidances/supportingmaterials/release_info_continuous_integration.xmi"/>
+ <resourceDescriptors xmi:id="_jtrgkElyEducWJcS4yanqg" id="-4iL0UEFR2Fg7oWkh1TymIg"
+ uri="guidances/termdefinitions/version.xmi"/>
+ <resourceDescriptors xmi:id="_89PC0Cb3Edqh1LYUOGRh2A" id="-BsXK3ZGMm-mUT0KnkdoYBg"
+ uri="guidances/concepts/change_requests.xmi"/>
+ <resourceDescriptors xmi:id="_nDqGgPL5Edm6Nvont3uinw" id="_Dfmk8MPiEdmbOvqy4O0adg"
+ uri="guidances/concepts/workspace.xmi"/>
+ <resourceDescriptors xmi:id="_kmCAQJOKEdyaRbFYa4AN4A" id="-01L_eCnHjKmBPsGcdk8XTg"
+ uri="tasks/integrate_and_create_build.xmi"/>
+ <resourceDescriptors xmi:id="_TrtRwElyEducWJcS4yanqg" id="-VPoMu7qzVX9grE4-nB3kMw"
+ uri="guidances/termdefinitions/configuration.xmi"/>
+ <resourceDescriptors xmi:id="_jHV4oNVbEdqy9sbRhejO5Q" id="-w7sImtXWkf4HDXdUWjRsUg"
+ uri="guidances/guidelines/submitting_change_requests.xmi"/>
+ <resourceDescriptors xmi:id="_iIMyUKs4EdywgoUkEzD0zQ" id="-zCM2ucJJxc_bQr_LoHlSaQ"
+ uri="guidances/guidelines/promoting_changes.xmi"/>
+ <resourceDescriptors xmi:id="_JYJCAASEEdySm_fBmNKn4w" id="-QpMXBM5_A8w0pRyIT5n5yA"
+ uri="guidances/concepts/change_set.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_D-ExQMktEdygFZkm1d5NtQ" name="practice.tech.continuous_integration.base"
+ guid="_D-ExQMktEdygFZkm1d5NtQ" changeDate="2008-01-28T13:25:06.777-0500">
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_D-ExQcktEdygFZkm1d5NtQ"
+ name="Content" guid="_D-ExQcktEdygFZkm1d5NtQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_D-ExQsktEdygFZkm1d5NtQ"
+ name="Categories" guid="_D-ExQsktEdygFZkm1d5NtQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_D-ExQ8ktEdygFZkm1d5NtQ"
+ name="Domains" guid="_D-ExQ8ktEdygFZkm1d5NtQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_D-ExRMktEdygFZkm1d5NtQ"
+ name="Disciplines" guid="_D-ExRMktEdygFZkm1d5NtQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_D-ExRcktEdygFZkm1d5NtQ"
+ name="RoleSets" guid="_D-ExRcktEdygFZkm1d5NtQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_D-ExRsktEdygFZkm1d5NtQ"
+ name="WP Types" guid="_D-ExRsktEdygFZkm1d5NtQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_D-ExR8ktEdygFZkm1d5NtQ"
+ name="Tools" guid="_D-ExR8ktEdygFZkm1d5NtQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_D-ExSMktEdygFZkm1d5NtQ"
+ name="StandardCategories" guid="_D-ExSMktEdygFZkm1d5NtQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_D-ExScktEdygFZkm1d5NtQ"
+ name="CustomCategories" guid="_D-ExScktEdygFZkm1d5NtQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_D-ExSsktEdygFZkm1d5NtQ"
+ name="Hidden" guid="_D-ExSsktEdygFZkm1d5NtQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_D-ExS8ktEdygFZkm1d5NtQ"
+ name="Custom Categories" guid="_D-ExS8ktEdygFZkm1d5NtQ" categorizedElements="_TtsEwMktEdygFZkm1d5NtQ _yhOXIM3SEdyKkus0T68H3Q"/>
+ </childPackages>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_TtsEwMktEdygFZkm1d5NtQ"
+ name="continuous_integration_practice" guid="_TtsEwMktEdygFZkm1d5NtQ"
+ presentationName="Continuous Integration" shapeicon="customcategories/resources/pract_dgm32.gif"
+ nodeicon="customcategories/resources/pract_obj.gif" categorizedElements="_B3xkEPD0EdqYgerqi84oCA _i8bUEL6cEdqti4GwqTkbsQ _0YuXEMlgEdmt3adZL5Dmdw _6jdvECb3Edqh1LYUOGRh2A _1QU9MAIoEdyLh7vsrHZ4YA _kkZBgJOKEdyaRbFYa4AN4A _SM4YIL6dEdqti4GwqTkbsQ _fnZj0NVXEdqy9sbRhejO5Q _0cEmAMlgEdmt3adZL5Dmdw">
+ <methodElementProperty xmi:id="_vekVsNnLEdyzZqGyZ7hwdw" name="CategoryElementsSortType"
+ value="MethodType"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_yhOXIM3SEdyKkus0T68H3Q"
+ name="contributions_to_nav_building_blocks" guid="_yhOXIM3SEdyKkus0T68H3Q"
+ presentationName="Contributions to Navigation Building Blocks" categorizedElements="_6WVSMM3SEdyKkus0T68H3Q _8rtOIM3SEdyKkus0T68H3Q _-HfPoM3SEdyKkus0T68H3Q _AaX4QM3TEdyKkus0T68H3Q _cFZgoNQwEdyM_J8-fv54DA _fX82gNQwEdyM_J8-fv54DA"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_6WVSMM3SEdyKkus0T68H3Q"
+ name="release_info.assign" guid="_6WVSMM3SEdyKkus0T68H3Q" variabilityType="contributes"
+ categorizedElements="_NWZp0M3TEdyKkus0T68H3Q">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCIHYcRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_8rtOIM3SEdyKkus0T68H3Q"
+ name="guideline_list.assign" guid="_8rtOIM3SEdyKkus0T68H3Q" variabilityType="contributes"
+ categorizedElements="_i8bUEL6cEdqti4GwqTkbsQ _SM4YIL6dEdqti4GwqTkbsQ _fnZj0NVXEdqy9sbRhejO5Q">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4ZcRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_-HfPoM3SEdyKkus0T68H3Q"
+ name="concept_list.assign" guid="_-HfPoM3SEdyKkus0T68H3Q" variabilityType="contributes"
+ categorizedElements="_B3xkEPD0EdqYgerqi84oCA _6jdvECb3Edqh1LYUOGRh2A _1QU9MAIoEdyLh7vsrHZ4YA _0cEmAMlgEdmt3adZL5Dmdw">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4Y8RdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_AaX4QM3TEdyKkus0T68H3Q"
+ name="artifact_list.assign" guid="_AaX4QM3TEdyKkus0T68H3Q" variabilityType="contributes"
+ categorizedElements="_0YuXEMlgEdmt3adZL5Dmdw">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4YMRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_cFZgoNQwEdyM_J8-fv54DA"
+ name="practice_list.assign" guid="_cFZgoNQwEdyM_J8-fv54DA" variabilityType="contributes"
+ categorizedElements="_TtsEwMktEdygFZkm1d5NtQ">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCIHY8RdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_fX82gNQwEdyM_J8-fv54DA"
+ name="technical_practice_list" guid="_fX82gNQwEdyM_J8-fv54DA" presentationName="Technical Practices"
+ variabilityType="contributes" categorizedElements="_TtsEwMktEdygFZkm1d5NtQ">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_lBrxENQuEdyM_J8-fv54DA"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_D-ExTMktEdygFZkm1d5NtQ"
+ name="CoreContent" guid="_D-ExTMktEdygFZkm1d5NtQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_J6WicMktEdygFZkm1d5NtQ"
+ name="Continuous Integration" guid="_J6WicMktEdygFZkm1d5NtQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_B3xkEPD0EdqYgerqi84oCA"
+ name="continuous_integration" guid="_B3xkEPD0EdqYgerqi84oCA" briefDescription="This concept introduces the practice of continuously integrating completed change sets in order to reduce the effort required to merge parallel development, to find bugs earlier, and to drive a collaborative work environment."
+ presentationName="Continuous Integration" variabilityType="replaces">
+ <presentation xmi:id="-dhAMzNZNWufBnW0fPYQtBA" href="uma://-dhAMzNZNWufBnW0fPYQtBA#-dhAMzNZNWufBnW0fPYQtBA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_i8bUEL6cEdqti4GwqTkbsQ"
+ name="continuous_integration" guid="_i8bUEL6cEdqti4GwqTkbsQ" briefDescription="This guideline describes how to apply continuous integration to reduce the risk and effort associated with late integration."
+ presentationName="Continuous Integration" conceptsAndPapers="_B3xkEPD0EdqYgerqi84oCA">
+ <presentation xmi:id="-DlaqJu4sEqMPk84qhJ6IEA" href="uma://-DlaqJu4sEqMPk84qhJ6IEA#-DlaqJu4sEqMPk84qhJ6IEA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_0YuXEMlgEdmt3adZL5Dmdw"
+ name="build" guid="_0YuXEMlgEdmt3adZL5Dmdw" briefDescription="An operational version of a system or part of a system that demonstrates a subset of the capabilities to be provided in the final product."
+ presentationName="Build" conceptsAndPapers="_B3xkEPD0EdqYgerqi84oCA"
+ guidelines="_i8bUEL6cEdqti4GwqTkbsQ">
+ <presentation xmi:id="_NqSB0KeqEdmKDbQuyzCoqQ" href="uma://_NqSB0KeqEdmKDbQuyzCoqQ#_NqSB0KeqEdmKDbQuyzCoqQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_RF4lkM3OEdyKkus0T68H3Q"
+ name="software_implementation_slot.assign_build" guid="_RF4lkM3OEdyKkus0T68H3Q"
+ variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_Vux8UEfUEdyiPI8btkmvmw"/>
+ <containedArtifacts xmi:id="_Jok_IM3REdyKkus0T68H3Q" name="build.ci" guid="_Jok_IM3REdyKkus0T68H3Q"
+ variabilityType="contributes" variabilityBasedOnElement="_0YuXEMlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="_NWZp0M3TEdyKkus0T68H3Q"
+ name="release_info_continuous_integration" guid="_NWZp0M3TEdyKkus0T68H3Q"
+ presentationName="Continuous Integration Release Information">
+ <presentation xmi:id="-_P9JU4M-5_0FI_g7_EGi6g" href="uma://-_P9JU4M-5_0FI_g7_EGi6g#-_P9JU4M-5_0FI_g7_EGi6g"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_kkZBgJOKEdyaRbFYa4AN4A"
+ name="integrate_and_create_build" guid="_kkZBgJOKEdyaRbFYa4AN4A" briefDescription="This task describes how to integrate all changes made by developers into the code base and perform the minimal testing to validate the build. [*** This task needs revision to fit better with Continuous Integration ***]"
+ presentationName="Integrate and Create Build" conceptsAndPapers="_1QU9MAIoEdyLh7vsrHZ4YA _0cEmAMlgEdmt3adZL5Dmdw"
+ output="_0YuXEMlgEdmt3adZL5Dmdw">
+ <presentation xmi:id="-01L_eCnHjKmBPsGcdk8XTg" href="uma://-01L_eCnHjKmBPsGcdk8XTg#-01L_eCnHjKmBPsGcdk8XTg"/>
+ <mandatoryInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZfMEMlgEdmt3adZL5Dmdw"/>
+ <mandatoryInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_Vux8UEfUEdyiPI8btkmvmw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_6jdvECb3Edqh1LYUOGRh2A"
+ name="change_requests" guid="_6jdvECb3Edqh1LYUOGRh2A" briefDescription="A change request is a general term for any request to change a work product."
+ presentationName="Change Requests">
+ <presentation xmi:id="-BsXK3ZGMm-mUT0KnkdoYBg" href="uma://-BsXK3ZGMm-mUT0KnkdoYBg#-BsXK3ZGMm-mUT0KnkdoYBg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_1QU9MAIoEdyLh7vsrHZ4YA"
+ name="change_set" guid="_1QU9MAIoEdyLh7vsrHZ4YA" briefDescription="A change set is a meaningful set of related changes made to the implementation and supporting artifacts for a particular purpose."
+ presentationName="Change Set">
+ <presentation xmi:id="-QpMXBM5_A8w0pRyIT5n5yA" href="uma://-QpMXBM5_A8w0pRyIT5n5yA#-QpMXBM5_A8w0pRyIT5n5yA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_0cEmAMlgEdmt3adZL5Dmdw"
+ name="workspace" guid="_0cEmAMlgEdmt3adZL5Dmdw" briefDescription="Workspace refers to storage areas where developers can implement and test code in accordance with the project's adopted standards in relative isolation from other developers."
+ presentationName="Workspace">
+ <presentation xmi:id="_Dfmk8MPiEdmbOvqy4O0adg" href="uma://_Dfmk8MPiEdmbOvqy4O0adg#_Dfmk8MPiEdmbOvqy4O0adg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_SM4YIL6dEdqti4GwqTkbsQ"
+ name="promoting_changes" guid="_SM4YIL6dEdqti4GwqTkbsQ" briefDescription="This guideline describes how to promote a set of related changes up through a set of tiers from a private development area to a release area."
+ presentationName="Promoting Builds">
+ <presentation xmi:id="-zCM2ucJJxc_bQr_LoHlSaQ" href="uma://-zCM2ucJJxc_bQr_LoHlSaQ#-zCM2ucJJxc_bQr_LoHlSaQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_fnZj0NVXEdqy9sbRhejO5Q"
+ name="submitting_change_requests" guid="_fnZj0NVXEdqy9sbRhejO5Q" briefDescription="This guideline describes the type of information that is typically captured on a change request. This information is used to prioritize and scope the work required to implement the change and to monitor progress."
+ presentationName="Submitting Change Requests">
+ <presentation xmi:id="-w7sImtXWkf4HDXdUWjRsUg" href="uma://-w7sImtXWkf4HDXdUWjRsUg#-w7sImtXWkf4HDXdUWjRsUg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="__Cw30ElxEducWJcS4yanqg"
+ name="configuration" guid="__Cw30ElxEducWJcS4yanqg" presentationName="configuration">
+ <presentation xmi:id="-VPoMu7qzVX9grE4-nB3kMw" href="uma://-VPoMu7qzVX9grE4-nB3kMw#-VPoMu7qzVX9grE4-nB3kMw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_eX8K8ElyEducWJcS4yanqg"
+ name="version" guid="_eX8K8ElyEducWJcS4yanqg" presentationName="version">
+ <presentation xmi:id="-4iL0UEFR2Fg7oWkh1TymIg" href="uma://-4iL0UEFR2Fg7oWkh1TymIg#-4iL0UEFR2Fg7oWkh1TymIg"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_D-ExTcktEdygFZkm1d5NtQ"
+ name="CapabilityPatterns" guid="_D-ExTcktEdygFZkm1d5NtQ"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_D-ExTsktEdygFZkm1d5NtQ"
+ name="DeliveryProcesses" guid="_D-ExTsktEdygFZkm1d5NtQ"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_D-ExT8ktEdygFZkm1d5NtQ"
+ name="ProcessContributions" guid="_D-ExT8ktEdygFZkm1d5NtQ"/>
+ <bases href="uma://_iVydgENdEdy245g62lfWcA#_iVydgENdEdy245g62lfWcA"/>
+ <bases href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0ELXuEduGP_98XMd0fg"/>
+ <bases href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2AAouEdyhlpBPrduOMw"/>
+ <bases href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno4EKmEdyrauqpmnA8jQ"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/practice.tech.continuous_integration.base/tasks/integrate_and_create_build.xmi b/praclib/temp/practice.tech.continuous_integration.base/tasks/integrate_and_create_build.xmi
new file mode 100644
index 0000000..3aa2bc2
--- /dev/null
+++ b/praclib/temp/practice.tech.continuous_integration.base/tasks/integrate_and_create_build.xmi
@@ -0,0 +1,143 @@
+<?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.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="-01L_eCnHjKmBPsGcdk8XTg"
+ name=",_Dq0GQAIoEdyLh7vsrHZ4YA" guid="-01L_eCnHjKmBPsGcdk8XTg" changeDate="2007-05-28T14:31:33.068-0400">
+ <keyConsiderations><p>
+
+ In order to be effective at applying the practice of <a class="elementLink" href="./../../openup/guidances/concepts/continuous_integration_87682D06.html" guid="_B3xkEPD0EdqYgerqi84oCA">Continuous Integration</a>,&nbsp;the time to integrate, build, and test the increment must be short enough that it can be
+
+ performed several times per day.&nbsp; Changes should be broken down into relatively small <a class="elementLink" href="./../../openup/guidances/concepts/change_set_430BF233.html" guid="_1QU9MAIoEdyLh7vsrHZ4YA">Change Set</a>s that can
+
+ be implemented, integrated and tested quickly.
+
+</p></keyConsiderations>
+ <sections xmi:id="_kkZBhZOKEdyaRbFYa4AN4A" name="Integrate implemented elements"
+ guid="_kkZBhZOKEdyaRbFYa4AN4A">
+ <sectionDescription><p>
+ In&nbsp;the relevant&nbsp;<a class="elementLink" href="./../../openup/guidances/concepts/workspace_722BBA90.html" guid="_0cEmAMlgEdmt3adZL5Dmdw">Workspace</a>, combine all completed&nbsp;<a class="elementLink" href="./../../openup/guidances/concepts/change_set_430BF233.html" guid="_1QU9MAIoEdyLh7vsrHZ4YA">Change Set</a>s that are
+ not in the latest baseline. Resolve any conflicting versions of the artifacts by either removing one of the change sets
+ that created the conflict&nbsp;or by creating a new change set that includes merged versions of the conflicting
+ artifacts.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_kkZBgpOKEdyaRbFYa4AN4A" name="Create build" guid="_kkZBgpOKEdyaRbFYa4AN4A">
+ <sectionDescription><p>
+
+ Create the build.&nbsp;The details of this step depend upon the implementation language and development environment and
+
+ may involve compiling and linking (in the case of compiled languages) and/or other processes that result in an
+
+ executable increment of the system.
+
+</p>
+
+<p>
+
+ Examples of these steps&nbsp;include:
+
+</p>
+
+<ol>
+
+ <li>
+
+ Compiling and linking the source artifacts to create an executable
+
+ </li>
+
+ <li>
+
+ Loading binary objects on a test bench or simulator
+
+ </li>
+
+ <li>
+
+ Running a script to load/update database schemas
+
+ </li>
+
+ <li>
+
+ Packaging and deploying web applications<br />
+
+ </li>
+
+</ol></sectionDescription>
+ </sections>
+ <sections xmi:id="_kkZBhJOKEdyaRbFYa4AN4A" name="Test integrated elements" guid="_kkZBhJOKEdyaRbFYa4AN4A">
+ <sectionDescription><p>
+
+ <a class="elementLink" href="./../../openup/tasks/run_developer_tests_73D7DBC4.html" guid="_0iYCUMlgEdmt3adZL5Dmdw">Run Developer Tests</a>&nbsp;against the integrated elements to verify that they behave the same as they did in isolation.
+
+ Ensure that the scope of these&nbsp;tests is as broad as possible, which ensures that the latest change sets did not
+
+ cause failing developer tests in other areas of the system.
+
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_kkZBgZOKEdyaRbFYa4AN4A" name="Make changes available" guid="_kkZBgZOKEdyaRbFYa4AN4A">
+ <sectionDescription><p>
+
+ When tests are successfully completed and the build is considered "good," the results&nbsp;are made available to the
+
+ rest of the team by <a class="elementLink" href="./../../openup/guidances/guidelines/promoting_changes_9087B764.html" guid="_SM4YIL6dEdqti4GwqTkbsQ">Promoting Changes</a>.&nbsp;The details of this step depend on the configuration
+
+ management tools in use, but in general this involves committing&nbsp;a tested change set to the CM repository so that
+
+ it&nbsp;serves as the basis of development for the next increment of the system.&nbsp; This is the essence of <a class="elementLink" href="./../../openup/guidances/concepts/continuous_integration_87682D06.html" guid="_B3xkEPD0EdqYgerqi84oCA">Continuous Integration</a>.
+
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_kkZBg5OKEdyaRbFYa4AN4A" name="Run "Smoke Tests"" guid="_kkZBg5OKEdyaRbFYa4AN4A">
+ <sectionDescription><p>
+
+ Several builds will be created in each iteration. For each build, this step is performed only when change sets have
+
+ been delivered to satisfy the requirements of that build.
+
+</p>
+
+<p>
+
+ Execute a sub-set of the system tests to ensure that the build is suitable prior to committing resources to the full
+
+ scope of system testing.&nbsp;While the level of testing will vary, focus on gaining confidence that the increment is
+
+ of sufficient quality to establish a baseline for system testing.
+
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_kkZBhpOKEdyaRbFYa4AN4A" name="Create a baseline" guid="_kkZBhpOKEdyaRbFYa4AN4A">
+ <sectionDescription><p>
+
+ Several builds will be created in each iteration. For each build, this step is performed only when change sets have
+
+ been delivered to satisfy the requirements of that build.
+
+</p>
+
+<p>
+
+ The&nbsp;procedure for this step depends on the&nbsp;configuration management tools in use.
+
+</p>
+
+<p>
+
+ Create a baseline that unambiguously identifies the configuration for the build that is ready for system testing.
+
+ Identify the version of each implementation element and supporting artifacts that were used to create&nbsp;this build.
+
+</p></sectionDescription>
+ </sections>
+ <purpose>The purpose of this task is to integrate all changes made by all developers into the code base and perform the minimal
+
+
+testing on the system increment in order to validate the build.&nbsp; The goal is to identify integration issues as soon as
+
+
+possible so they can be corrected easily by the right person, at the right time.</purpose>
+</org.eclipse.epf.uma:TaskDescription>
diff --git a/praclib/temp/practice.tech.continuous_integration.base/workproducts/build.xmi b/praclib/temp/practice.tech.continuous_integration.base/workproducts/build.xmi
new file mode 100644
index 0000000..63f25eb
--- /dev/null
+++ b/praclib/temp/practice.tech.continuous_integration.base/workproducts/build.xmi
@@ -0,0 +1,45 @@
+<?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">
+ <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
+ executable version of the system will typically have a number of supporting files that are also considered part of this
+ composite artifact.
+</p></mainDescription>
+ <keyConsiderations><p>
+
+ In an iterative lifecycle, each build must evolve from the previous iteration's build, adding more functionality and
+
+ improving quality.
+
+</p>
+
+<p>
+
+ The purpose of early builds that minimize or eliminate a risk or verify architectural decisions is to achieve
+
+ consistently stable builds in later iterations.
+
+</p></keyConsiderations>
+ <purpose>Deliver incremental value to the user and customer, and provide a testable artifact for verification.</purpose>
+ <reasonsForNotNeeding><p>
+
+ There will always need to be an&nbsp;operational version of the system.
+
+</p></reasonsForNotNeeding>
+ <representationOptions><p>
+
+ This work product is&nbsp;almost always a composite product made up of numerous parts required to make the executable
+
+ system. Therefore a build is more than just executable files; it additionally includes such things as configuration
+
+ files, help files, and data repositories that will be put together resulting in the product that will be run by the
+
+ users. The specifics of those parts will vary by technology in use.
+
+</p></representationOptions>
+</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/praclib/temp/practice.tech.evolutionary_arch.assign/.project b/praclib/temp/practice.tech.evolutionary_arch.assign/.project
new file mode 100644
index 0000000..a6d5c94
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.assign/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>practice.tech.evolutionary_arch.assign</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/practice.tech.evolutionary_arch.assign/plugin.xmi b/praclib/temp/practice.tech.evolutionary_arch.assign/plugin.xmi
new file mode 100644
index 0000000..95f9657
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.assign/plugin.xmi
@@ -0,0 +1,93 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_GxLUAM2sEdym_ZFqrJcXUg"
+ guid="_GxLUAM2sEdym_ZFqrJcXUg"/>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_GxBjAM2sEdym_ZFqrJcXUg" name="practice.tech.evolutionary_arch.assign"
+ guid="_GxBjAM2sEdym_ZFqrJcXUg" briefDescription="This plug-in contains the standard category and role assignment for the Evolutionary Architecture practice. It is dependent on the practice plug-in, as well as the plug-ins containing the standard categories and roles being assigned to."
+ changeDate="2008-02-08T02:41:35.000-0500">
+ <copyrightStatement href="uma://_iVydgENdEdy245g62lfWcA#_uuunoPsDEdmyhNQr5STrZQ"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_GxBjAc2sEdym_ZFqrJcXUg"
+ name="Content" guid="_GxBjAc2sEdym_ZFqrJcXUg">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_GxBjAs2sEdym_ZFqrJcXUg"
+ name="Categories" guid="_GxBjAs2sEdym_ZFqrJcXUg">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_GxBjA82sEdym_ZFqrJcXUg"
+ name="Domains" guid="_GxBjA82sEdym_ZFqrJcXUg">
+ <contentElements xsi:type="org.eclipse.epf.uma:Domain" xmi:id="_WwaMgM3bEdyjXslGsagg_w"
+ name="architecture_domain.evarch" guid="_WwaMgM3bEdyjXslGsagg_w" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Domain" href="uma://_MRPloEFXEdy9ENCpSugIjA#_1r0bcK80Edy9cPK11VzBuQ"/>
+ <workProducts xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_4gaS4LPREduocbW-TPTq7A#_0XAf0MlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_GxBjBM2sEdym_ZFqrJcXUg"
+ name="Disciplines" guid="_GxBjBM2sEdym_ZFqrJcXUg">
+ <contentElements xsi:type="org.eclipse.epf.uma:Discipline" xmi:id="_pBQM0M2-Edym_ZFqrJcXUg"
+ name="architecture_discipline.evarch" guid="_pBQM0M2-Edym_ZFqrJcXUg"
+ variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Discipline" href="uma://_MRPloEFXEdy9ENCpSugIjA#_iGSHsFZ-EdyIUdvDLLUdeg"/>
+ <tasks href="uma://_4gaS4LPREduocbW-TPTq7A#_0gRJgMlgEdmt3adZL5Dmdw"/>
+ <tasks href="uma://_4gaS4LPREduocbW-TPTq7A#_0f-1oMlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_GxBjBc2sEdym_ZFqrJcXUg"
+ name="RoleSets" guid="_GxBjBc2sEdym_ZFqrJcXUg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_GxBjBs2sEdym_ZFqrJcXUg"
+ name="WP Types" guid="_GxBjBs2sEdym_ZFqrJcXUg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_GxBjB82sEdym_ZFqrJcXUg"
+ name="Tools" guid="_GxBjB82sEdym_ZFqrJcXUg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_GxBjCM2sEdym_ZFqrJcXUg"
+ name="StandardCategories" guid="_GxBjCM2sEdym_ZFqrJcXUg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_GxBjCc2sEdym_ZFqrJcXUg"
+ name="CustomCategories" guid="_GxBjCc2sEdym_ZFqrJcXUg">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_GxBjCs2sEdym_ZFqrJcXUg"
+ name="Hidden" guid="_GxBjCs2sEdym_ZFqrJcXUg">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_GxBjC82sEdym_ZFqrJcXUg"
+ name="Custom Categories" guid="_GxBjC82sEdym_ZFqrJcXUg"/>
+ </childPackages>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_GxBjDM2sEdym_ZFqrJcXUg"
+ name="CoreContent" guid="_GxBjDM2sEdym_ZFqrJcXUg">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_obUd8M2tEdym_ZFqrJcXUg"
+ name="Role Assignments" guid="_obUd8M2tEdym_ZFqrJcXUg" briefDescription="This package contains the assignment of practice tasks to performing roles.">
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_aymyQM29Edym_ZFqrJcXUg"
+ name="envision_the_arch.ra" guid="_aymyQM29Edym_ZFqrJcXUg" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Task" href="uma://_4gaS4LPREduocbW-TPTq7A#_0f-1oMlgEdmt3adZL5Dmdw"/>
+ <performedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0X9iEMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0VxJsMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0a0o0MlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_dTa6gMAYEdqX-s4mWhkyqQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_-fYuEM3ZEdyjXslGsagg_w"
+ name="refine_the_arch.ra" guid="_-fYuEM3ZEdyjXslGsagg_w" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Task" href="uma://_4gaS4LPREduocbW-TPTq7A#_0gRJgMlgEdmt3adZL5Dmdw"/>
+ <performedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0X9iEMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0a0o0MlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Role" xmi:id="_HpMKMM3lEdyjXslGsagg_w"
+ name="architect.ra" guid="_HpMKMM3lEdyjXslGsagg_w" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Role" href="uma://_A118oMYaEdyXeo04os5BOw#_0X9iEMlgEdmt3adZL5Dmdw"/>
+ <responsibleFor xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_4gaS4LPREduocbW-TPTq7A#_0XAf0MlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_GxBjDc2sEdym_ZFqrJcXUg"
+ name="CapabilityPatterns" guid="_GxBjDc2sEdym_ZFqrJcXUg"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_GxBjDs2sEdym_ZFqrJcXUg"
+ name="DeliveryProcesses" guid="_GxBjDs2sEdym_ZFqrJcXUg"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_GxBjD82sEdym_ZFqrJcXUg"
+ name="ProcessContributions" guid="_GxBjD82sEdym_ZFqrJcXUg"/>
+ <bases href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS4LPREduocbW-TPTq7A"/>
+ <bases href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPloEFXEdy9ENCpSugIjA"/>
+ <bases href="uma://_A118oMYaEdyXeo04os5BOw#_A118oMYaEdyXeo04os5BOw"/>
+ <bases href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVEMYbEdyXeo04os5BOw"/>
+ <bases href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno4EKmEdyrauqpmnA8jQ"/>
+ <bases href="uma://_iVydgENdEdy245g62lfWcA#_iVydgENdEdy245g62lfWcA"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/.project b/praclib/temp/practice.tech.evolutionary_arch.base/.project
new file mode 100644
index 0000000..1786e71
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>practice.tech.evolutionary_arch.base</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/evolutionary_arch_practice.xmi b/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/evolutionary_arch_practice.xmi
new file mode 100644
index 0000000..71280c8
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/evolutionary_arch_practice.xmi
@@ -0,0 +1,108 @@
+<?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="-gEb0V8Q3YP6iExbEvpjZIg"
+ name="evolutionary_arch_practice,_RBa6gJ-mEdyBk-WQzMU-FQ" guid="-gEb0V8Q3YP6iExbEvpjZIg"
+ changeDate="2008-02-21T11:51:11.234-0500" version="7.2.0">
+ <mainDescription><p>
+ The Evolutionary Architecture practice contains the method elements needed to analyze the major technical concerns that
+ affect the solution and capture those architectural decisions to ensure that those decisions are assessed and
+ communicated.<br />
+</p><br />
+<h3>
+ The Essence of Evolutionary Architecture
+</h3>
+<p>
+ The following capture the key principles of the Evolutionary Architecture practice:
+</p>
+<ul>
+ <li>
+ <strong>Architecture work is prioritized with all other work (architect "just in time" and evolve the architecture
+ over time).</strong> Architectural issues are explicitly identified, discussed by the team, and prioritized with
+ any other work within the context of iteration planning. Prioritization is based on need for technical risk
+ mitigation versus value creation.&nbsp; Assigning architectural issues to an iteration drives 'just-in-time'
+ architecture work and the architecture <em>evolves over time</em>.
+ </li>
+ <li>
+ <strong>Document key architectural decisions and outstanding issues</strong>.&nbsp; The <a class="elementLink"
+ href="./../../practice.tech.evolutionary_arch.base/workproducts/architecture_notebook_9BB92433.html"
+ guid="_0XAf0MlgEdmt3adZL5Dmdw">Architecture Notebook</a>&nbsp;provides a place to maintain a list of the
+ architectural issues, along with any supporting materials documented at the appropriate level to make it easy to
+ understand what architectural decisions have been made, and are still left to be made.
+ </li>
+ <li>
+ <strong>Implement and test key capabilities as a means to address architectural issues</strong>.&nbsp; Resolving an
+ architectural issues typically requires not only architectural brainstorming, but also associated
+ prototyping.&nbsp; In other words, implement enough code (hopefully code that becomes production code, minus what
+ had to be thrown away because proven invalid) to validate the assumptions behind the architecture.
+ </li>
+</ul>
+<h3>
+ <br />
+ Why Adopt this Practice?
+</h3>
+<p>
+ [*** Include some content here that describes the business value of this practice -- what do you get when you adopt
+ it?&nbsp; This section is essentially the value proposition for the practice.&nbsp; You may want to describe some
+ common problems and how this practice solves those problems.&nbsp; &nbsp;***]&nbsp;&nbsp;&nbsp;
+</p>
+<h3>
+ How to Read this Practice
+</h3>
+<p>
+ The best way to read this practice is to first familiarize yourself with its overall structure -- what it is in it and
+ how it is organized.&nbsp;
+</p>
+<p>
+ The best place to start is with the <a class="elementLink"
+ href="./../../practice.tech.evolutionary_arch.base/customcategories/key_concepts_1B502EBE.html"
+ guid="_Cv-PAOCdEdy1GK0fgbL-TA">Key Concepts</a>&nbsp;for the practice -- those concepts that are critical to understand
+ in order to adopt the practice.&nbsp; An especially important concept for the Evolutionary Architecture practice is <a
+ class="elementLinkWithType" href="./../../core.tech.common.base/guidances/concepts/software_architecture_59A08DE0.html"
+ guid="__O7tAMVvEduLYZUGfgZrkQ">Concept: Software Architecture</a>.&nbsp; Once you understand what architecture is, you
+ can turn your attention to the artifact produced by the practice, the <a class="elementLinkWithType"
+ href="./../../practice.tech.evolutionary_arch.base/workproducts/architecture_notebook_9BB92433.html"
+ guid="_0XAf0MlgEdmt3adZL5Dmdw">Artifact: Architecture Notebook</a>.&nbsp;&nbsp; Then you can&nbsp;review
+ the&nbsp;practices <a class="elementLink"
+ href="./../../practice.tech.evolutionary_arch.base/customcategories/tasks_D352B806.html"
+ guid="_TPZH0NcmEdy1nJEYZGzN4A">Tasks</a>.&nbsp; From the work products and the tasks, you can access applicable
+ guidance -- guidelines and tool mentors associated with each task provide details of how to perform the
+ task.&nbsp;Templates and checklists associated with the work products guide you in their completion and evaluation. You
+ can also access the guidance provided by the practice directly, via <a class="elementLink"
+ href="./../../practice.tech.evolutionary_arch.base/customcategories/guidance_9356A6C8.html"
+ guid="_HF_ykJ_7EdyBk-WQzMU-FQ">Guidance</a>&nbsp;folder.
+</p>
+<p>
+ Once you have an understanding of these key elements of the practice, you can take a look at the provided list of
+ enablement materials (see the&nbsp;"Additional Information" section of this document.
+</p>
+<p>
+ For step-by-step instructions on how to adopt this practice, see <a class="elementLinkWithType"
+ href="./../../practice.tech.evolutionary_arch.base/guidances/roadmaps/how_to_adopt_evolutionary_arch_practice_FEFA2CCF.html"
+ guid="_Odpz8NciEdy1nJEYZGzN4A">Roadmap: How to Adopt This Practice</a>.
+</p>
+<h3>
+ Additional Resources
+</h3>
+<p>
+ For more information on the evolutionary architecture approach, see the following:
+</p>
+<ul>
+ <li>
+ <a href="http://www.agilemodeling.com/essays/agileArchitecture.htm" target="_blank">Agile Architecture: Strategies
+ for Scaling Agile Development</a>
+ </li>
+ <li>
+ <a href="http://www.agilemodeling.com/essays/initialArchitectureModeling.htm" target="_blank">Architectural
+ Envisioning</a>
+ </li>
+ <li>
+ <a href="http://www.agiledata.org/essays/enterpriseArchitecture.html" target="_blank">Agile Enterprise
+ Architecture</a>
+ </li>
+ <li>
+ [*** Add more, as needed ***]<br />
+ </li>
+</ul></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/bookc.gif b/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/bookc.gif
new file mode 100644
index 0000000..7f2ab85
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/bookc.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/bookcL.gif b/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/bookcL.gif
new file mode 100644
index 0000000..6c5b064
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/bookcL.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/compass.gif b/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/compass.gif
new file mode 100644
index 0000000..39f306a
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/compass.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/compassL.gif b/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/compassL.gif
new file mode 100644
index 0000000..4117414
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/compassL.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/concept_dgm32.gif b/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/concept_dgm32.gif
new file mode 100644
index 0000000..fa195bd
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/concept_dgm32.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/concept_obj.gif b/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/concept_obj.gif
new file mode 100644
index 0000000..03af38b
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/concept_obj.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/pract_dgm32.gif b/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/pract_dgm32.gif
new file mode 100644
index 0000000..f597332
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/pract_dgm32.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/pract_obj.gif b/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/pract_obj.gif
new file mode 100644
index 0000000..fe8075a
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/pract_obj.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/task_dgm32.gif b/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/task_dgm32.gif
new file mode 100644
index 0000000..a91ea1c
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/task_dgm32.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/task_obj.gif b/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/task_obj.gif
new file mode 100644
index 0000000..7633d58
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/task_obj.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/workproduct_dgm32.gif b/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/workproduct_dgm32.gif
new file mode 100644
index 0000000..009c9af
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/workproduct_dgm32.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/workproduct_obj.gif b/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/workproduct_obj.gif
new file mode 100644
index 0000000..3e58c6f
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/customcategories/resources/workproduct_obj.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/guidances/checklists/architecture_notebook.xmi b/praclib/temp/practice.tech.evolutionary_arch.base/guidances/checklists/architecture_notebook.xmi
new file mode 100644
index 0000000..97e0509
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/guidances/checklists/architecture_notebook.xmi
@@ -0,0 +1,189 @@
+<?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"
+ 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 "
+ 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>
+ <li>
+ Is the description of the architecture complete, meaningful, and clear?
+ </li>
+ <li>
+ Is the&nbsp;architecture&nbsp;at an appropriate level of detail, given the objectives?
+ </li>
+ <li>
+ Are concepts&nbsp;handled in the simplest way possible?
+ </li>
+ <li>
+ Does&nbsp;the architecture clearly convey not only the solution but also the motivation and objectives related to
+ the&nbsp;decisions that have been made in shaping the architecture?
+ </li>
+ <li>
+ Are the key assumptions and decisions that the&nbsp;architecture is based on documented and visible to reviewers
+ and those who will use the architecture?
+ </li>
+ <li>
+ Is the architecture description current?
+ </li>
+ <li>
+ Have the design guidelines been followed?
+ </li>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_U-wp8NvXEdyrWIQpneun6w" name="Have the architectural goals, constraints and requirements been adequately described and handled?"
+ guid="_U-wp8NvXEdyrWIQpneun6w">
+ <sectionDescription><ul>
+ <li>
+ Have the <a class="elementLink" href="./../../../core.tech.common.base/guidances/concepts/arch_goals_CB41D8AE.html"
+ guid="_HlRqANpbEdyP58ppo1Ieaw">Architectural Goals</a>&nbsp;been clearly described?
+ </li>
+ <li>
+ Have any <a class="elementLink"
+ href="./../../../core.tech.common.base/guidances/concepts/arch_constraints_AE56B662.html"
+ guid="_jdKSsNpiEdyP58ppo1Ieaw">Architectural Constraints</a>&nbsp;been identified and documented?
+ </li>
+ <li>
+ Have the <a class="elementLink"
+ href="./../../../core.tech.common.base/guidances/concepts/arch_significant_requirements_1EE5D757.html"
+ guid="_HrZGIA4MEduibvKwrGxWxA">Architecturally Significant Requirements</a>&nbsp;been identified and are they
+ clearly described.
+ </li>
+ <li>
+ Is the architecture is consistent with the rarchitectural goals, constraints and requirements?
+ </li>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_UCJbQNvYEdyrWIQpneun6w" name="Have necessary architectural mechanisms been identified and described? "
+ guid="_UCJbQNvYEdyrWIQpneun6w">
+ <sectionDescription><ul>
+ <li>
+ Is it clear when&nbsp;each <a class="elementLink"
+ href="./../../../core.tech.common.base/guidances/concepts/arch_mechanism_2932DFB6.html"
+ guid="_mzxI0A4LEduibvKwrGxWxA">Architectural Mechanism</a>&nbsp;should be applied?
+ </li>
+ <li>
+ Is there a clearly defined design pattern in place to support&nbsp;each mechanism?
+ </li>
+ <li>
+ Does each mechanism adequately address the requirements it is intended to meet?
+ </li>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_hKAz8NvZEdyrWIQpneun6w" name="Have the system partitions been adequately defined?"
+ guid="_hKAz8NvZEdyrWIQpneun6w">
+ <sectionDescription><ul class="noindent">
+ <li>
+ Is partitioning approach clearly described and applied consistently?
+ </li>
+ <li>
+ Does the partitioning approach reduce complexity and improve understanding?
+ </li>
+ <li>
+ Have the partitions been defined to be highly cohesive within the partition, while the partitions themselves are
+ loosely coupled?
+ </li>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_eYXBINvYEdyrWIQpneun6w" name="Have the key elements been adequately defined?"
+ guid="_eYXBINvYEdyrWIQpneun6w">
+ <sectionDescription><ul>
+ <li>
+ Have the <a class="elementLink"
+ href="./../../../core.tech.common.base/guidances/concepts/key_abstractions_1474DBF2.html"
+ guid="_pLEGUNqGEdy88NBoQgfGyg">Key Abstractions</a>&nbsp;adequately defined?
+ </li>
+ <li>
+ Have the the key design elements (i.e., <a class="elementLink"
+ href="./../../../core.tech.common.base/guidances/concepts/component_CB167D48.html"
+ guid="_0YP18MlgEdmt3adZL5Dmdw">Component</a>s) adequately defined?
+ </li>
+ <li style="LIST-STYLE-TYPE: none">
+ <ul>
+ <li>
+ Do the components have well-defined interfaces?
+ </li>
+ <li>
+ Have the system’s responsibilities been allocated to the components?
+ </li>
+ <li>
+ Are the number and types of components reasonable?
+ </li>
+ </ul>
+ </li>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_KU3WQNvbEdyrWIQpneun6w" name="Have interfaces to external systems been adequately represented?"
+ guid="_KU3WQNvbEdyrWIQpneun6w">
+ <sectionDescription><p>
+ See <a class="elementLinkWithType"
+ href="./../../../core.tech.common.base/guidances/guidelines/repres_interfaces_to_ext_systems_51A34F6E.html"
+ guid="_0gjdYMlgEdmt3adZL5Dmdw">Guideline: Representing Interfaces to External Systems</a>
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_bQB24NvbEdyrWIQpneun6w" name="Has all reuse been identified?"
+ guid="_bQB24NvbEdyrWIQpneun6w">
+ <sectionDescription>Have all reusable assets been identified -- either those reused by the system, or those elements within the system that
+have been built to be reused.&nbsp; For more information, see <a class="elementLinkWithType"
+href="./../../../core.tech.common.base/guidances/guidelines/software_reuse_B6B04C26.html"
+guid="_vO2uoO0OEduUpsu85bVhiQ">Guideline: Software Reuse</a>.</sectionDescription>
+ </sections>
+ <sections xmi:id="_pgGfsNvaEdyrWIQpneun6w" name="Has the architecture been built to evolve?"
+ guid="_pgGfsNvaEdyrWIQpneun6w">
+ <sectionDescription><ul class="noindent">
+ <li>
+ Can the&nbsp;architecture easily evolve,&nbsp;so that&nbsp;expected changes can be easily accommodated?
+ </li>
+ <li>
+ Are all technical risks either mitigated or addressed in a contingency plan?
+ </li>
+ <li>
+ Has the&nbsp;architecture been overly structured to handle unlikely change at the expense of simplicity and
+ comprehensibility? (Hint: "Yes" to this question is not good.)
+ </li>
+</ul><br />
+<br /></sectionDescription>
+ </sections>
+ <sections xmi:id="_aWun4NjcEdydTt3eL7YyCQ" name="Can the architecture be delivered by the team?"
+ guid="_aWun4NjcEdydTt3eL7YyCQ">
+ <sectionDescription><ul>
+ <li>
+ Does the architecture provide a suitable basis for organizing the development teams?
+ </li>
+ <li>
+ Does each team have the skills required to implement their allocated components?
+ </li>
+ <li>
+ Are responsibilities divided well between teams?
+ </li>
+ <li>
+ Do all team members share the same understanding of the architecture as the one presented by the architect?
+ </li>
+ <li>
+ Can team members understand enough from the architecture to successfully design and code their allocated
+ components?
+ </li>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_9LIDYNvbEdyrWIQpneun6w" name="Has the software been adequately mapped to the hardware?"
+ guid="_9LIDYNvbEdyrWIQpneun6w">
+ <sectionDescription><ul class="noindent">
+ <li>
+ Have the deployable software components been mapped to physical nodes?
+ </li>
+</ul></sectionDescription>
+ </sections>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/guidances/concepts/resources/ArchMechanismsStatemachine.JPG b/praclib/temp/practice.tech.evolutionary_arch.base/guidances/concepts/resources/ArchMechanismsStatemachine.JPG
new file mode 100644
index 0000000..a1b1f17
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/guidances/concepts/resources/ArchMechanismsStatemachine.JPG
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/guidances/concepts/resources/security_patterns_overview.png b/praclib/temp/practice.tech.evolutionary_arch.base/guidances/concepts/resources/security_patterns_overview.png
new file mode 100644
index 0000000..f4c4b7e
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/guidances/concepts/resources/security_patterns_overview.png
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/guidances/concepts/resources/visual.gif b/praclib/temp/practice.tech.evolutionary_arch.base/guidances/concepts/resources/visual.gif
new file mode 100644
index 0000000..6f4674c
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/guidances/concepts/resources/visual.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/guidances/guidelines/evolutionary_arch_practice_enablement.xmi b/praclib/temp/practice.tech.evolutionary_arch.base/guidances/guidelines/evolutionary_arch_practice_enablement.xmi
new file mode 100644
index 0000000..1b0e3b9
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/guidances/guidelines/evolutionary_arch_practice_enablement.xmi
@@ -0,0 +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="-LoF65cvuspIEfwANs6TKvg"
+ name="new_guideline,_19AIoNchEdy1nJEYZGzN4A" guid="-LoF65cvuspIEfwANs6TKvg" changeDate="2008-02-09T12:03:39.234-0500"
+ version="7.2.0">
+ <mainDescription><p>
+ [*** Content TBD ***]
+</p><br /></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/guidances/guidelines/modeling_the_arch.xmi b/praclib/temp/practice.tech.evolutionary_arch.base/guidances/guidelines/modeling_the_arch.xmi
new file mode 100644
index 0000000..5d07222
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/guidances/guidelines/modeling_the_arch.xmi
@@ -0,0 +1,34 @@
+<?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="-mEJbo_5lG227hXMdftmX_A"
+ name="new_guideline_2,_HrgUQNcuEdy1nJEYZGzN4A" guid="-mEJbo_5lG227hXMdftmX_A"
+ changeDate="2008-02-15T11:17:10.703-0500" version="7.2.0">
+ <mainDescription><p>
+ When architecting a system, developing visual models of the architecture can be quite helpful as such models provide an
+ excellent high-level picture of the system, its <a class="elementLink"
+ href="./../../../core.tech.common.base/guidances/concepts/component_CB167D48.html"
+ guid="_0YP18MlgEdmt3adZL5Dmdw">Component</a>s and their relationships. Specifically, you may find it useful to develop
+ these three Unified Modeling Language (UML) diagrams:
+</p>
+<ul>
+ <li>
+ <strong>Layer map</strong> (represented as a class diagram using packages) that describes the upper-level layers of
+ the architecture
+ </li>
+ <li>
+ <strong>Deployment diagram</strong> (repesented by a deployment diagram) that outlines the&nbsp;expected network
+ topology
+ </li>
+ <li>
+ <strong>Key Abstractions diagram</strong> (repesented by a class diagram) that shows the key
+ abstractions/cpmponents&nbsp;and any obvious relationships among them
+ </li>
+</ul>
+<p>
+ For more information on visual modeling, see <a class="elementLinkWithType"
+ href="./../../../core.tech.common.base/guidances/guidelines/using_visual_modeling_DA1CA6E4.html"
+ guid="_0SsecNr8EdyXE6np2_hUMA">Guideline: Using Visual Modeling</a>.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/guidances/guidelines/resources/4plus1_2.jpg b/praclib/temp/practice.tech.evolutionary_arch.base/guidances/guidelines/resources/4plus1_2.jpg
new file mode 100644
index 0000000..24cfc97
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/guidances/guidelines/resources/4plus1_2.jpg
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/guidances/roadmaps/how_to_adopt_evolutionary_arch_practice.xmi b/praclib/temp/practice.tech.evolutionary_arch.base/guidances/roadmaps/how_to_adopt_evolutionary_arch_practice.xmi
new file mode 100644
index 0000000..4b5cddb
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/guidances/roadmaps/how_to_adopt_evolutionary_arch_practice.xmi
@@ -0,0 +1,62 @@
+<?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="-KXvzdy6aJTFPQRS-UK5dvA"
+ name="new_roadmap,_Odpz8NciEdy1nJEYZGzN4A" guid="-KXvzdy6aJTFPQRS-UK5dvA" changeDate="2008-02-17T08:09:46.937-0500"
+ version="7.2.0">
+ <mainDescription><h3>
+ Getting Started&nbsp;
+</h3>
+<p>
+ Begin by making sure the team, including key stakeholders, understands what software architecture is and the value for
+ capturing it in a separate artifact from the implementation itself.&nbsp; Thus, <a class="elementLinkWithType"
+ href="./../../../core.tech.common.base/guidances/concepts/software_architecture_59A08DE0.html"
+ guid="__O7tAMVvEduLYZUGfgZrkQ">Concept: Software Architecture</a>&nbsp;is a great place to start.&nbsp;
+</p>
+<p>
+ Once there is agreement that the architecture should be captured, it is important to come to an agreement on what
+ architectural information you want to capture and what format it should take.&nbsp; Review the <a
+ class="elementLinkWithType"
+ href="./../../../practice.tech.evolutionary_arch.base/workproducts/architecture_notebook_9BB92433.html"
+ guid="_0XAf0MlgEdmt3adZL5Dmdw">Artifact: Architecture Notebook</a>&nbsp;and associated guidance.&nbsp; Agree, as a
+ team, what you want to document.
+</p>
+<p>
+ Now you can turn your attention&nbsp;to deciding as a team how and when the architectural&nbsp;<a class="elementLink"
+ href="./../../../practice.tech.evolutionary_arch.base/customcategories/tasks_D352B806.html"
+ guid="_TPZH0NcmEdy1nJEYZGzN4A">Tasks</a>&nbsp;should be performed.&nbsp;
+</p>
+<ul>
+ <li>
+ If you are working on a new project and you are at the beginning of the lifecycle, you can try envisioning the
+ architecture (<a class="elementLinkWithType"
+ href="./../../../practice.tech.evolutionary_arch.base/tasks/envision_the_arch_FF123A81.html"
+ guid="_0f-1oMlgEdmt3adZL5Dmdw">Task: Envision the Architecture</a>) to be developed and then evolving the
+ architecture (<a class="elementLinkWithType"
+ href="./../../../practice.tech.evolutionary_arch.base/tasks/evolve_the_arch_7723A69E.html"
+ guid="_0gRJgMlgEdmt3adZL5Dmdw">Task: Evolve the Architecture</a>) as development proceeds.
+ </li>
+ <li>
+ If you are working on a project that is already underway, just take some time to document the decisions that have
+ already been made and continue to evolve the architecture as development proceeds. See <a
+ class="elementLinkWithType"
+ href="./../../../practice.tech.evolutionary_arch.base/tasks/evolve_the_arch_7723A69E.html"
+ guid="_0gRJgMlgEdmt3adZL5Dmdw">Task: Evolve the Architecture</a>.
+ </li>
+</ul>
+<h3>
+ Common Pitfalls
+</h3>
+<p>
+ Try to avoid spending too much time on developing extensive architectural documentation. Capture the key decisions and
+ the rationale for these decisions.&nbsp; Refer to more detailed documentation, where necessary.&nbsp; Try to keep the
+ documentation clear and concise.&nbsp; Make sure that the consumers of the architecture (the development team) are
+ comfortable with the format and content of the architecture.&nbsp; Is there more or different information they would
+ like see?&nbsp; Would they like to see less?
+</p>
+<p>
+ Make sure that you have periodic checkpoints where the architecture is reviewed and refined to match the developed
+ solution.&nbsp;
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/guidances/supportingmaterials/release_info_evolutionary_arch.xmi b/praclib/temp/practice.tech.evolutionary_arch.base/guidances/supportingmaterials/release_info_evolutionary_arch.xmi
new file mode 100644
index 0000000..47d31f6
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/guidances/supportingmaterials/release_info_evolutionary_arch.xmi
@@ -0,0 +1,162 @@
+<?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="-Iyj1LA3WbTQP_iQmRp7ibw"
+ name="release_info_evolutionary_arch,_rA1NMc3lEdyjXslGsagg_w" guid="-Iyj1LA3WbTQP_iQmRp7ibw"
+ changeDate="2008-02-17T07:32:50.000-0500" version="7.2.0">
+ <mainDescription><h3>
+ Version 1.0
+</h3>
+<p>
+ This initial release of the Evolutionary Architecture Practice is based on content from OpenUP v1.0 plus refinements to
+ structure the content into a practice and clean up content to remove redundancy and improve consistency.
+</p>
+<p>
+ The specific changes that were made are as follows:
+</p>
+<ul>
+ <li>
+ Created plug-ins and content packages to support practice library structure -- separate base and assign practice
+ plug-ins, separate role defn plug-in, etc.
+ </li>
+ <li>
+ Implemented delayed role assignment: Placed architect role in new role definition plug-in.&nbsp; Moved all role
+ assignments and assignments of tasks and work products to standard categories to new assign plug-in.
+ </li>
+ <li>
+ Implemented default navigation view approach. Mapped all elements to the navigation view building blocks so they
+ are included in a view
+ </li>
+ <li>
+ Removed term definitions for roles and work products -- their definition is enough.
+ </li>
+ <li>
+ Changed name of Task: Outline the Architecture to Task: Envision the Architecture.
+ </li>
+ <li>
+ Changed the name of Task: Refine the Architecture to Task: Evolve the Architecture.
+ </li>
+ <li>
+ Identified guidance that can be shared between architecture tasks and practices and defined the appropriate
+ practice elements in the common architecture guidance package in&nbsp;a separate common plug-in (e.g.,
+ core.tech.common.base)
+ </li>
+ <li>
+ Reviewed and re-factored of tasks -- moved task details to guidance where it can be shared between architecture
+ tasks and practices
+ </li>
+ <li>
+ Placed all content related to visual modeling in separate content packages, both in the common plug-ins, as well as
+ in the practice plug-ins.
+ </li>
+ <li>
+ Created new elements that are common to all practices: Custom category whose description is the "title page" for
+ the practice, How To Adopt page, Release Info page, etc.
+ </li>
+ <li>
+ Removed association to guidance from the architecture discipline.&nbsp; It is just a standard category.&nbsp; All
+ guidance is associated to roles, tasks, or WPs (or other guidance)
+ </li>
+ <li>
+ Cleaned up the content to reflect the latest authoring guidelines
+ </li>
+ <li style="LIST-STYLE-TYPE: none">
+ <ul>
+ <li>
+ Removed references to specific roles in all elements
+ </li>
+ <li>
+ Removed references to specific method assets (e.g., OpenUP) and specific lifecycles (e.g., RUP phases) from
+ the method element descriptions.
+ </li>
+ <li>
+ Replaced references to artifacts outside the practice with references to the appropriate slots
+ </li>
+ <li>
+ Eliminated redundancy between tasks, concepts and guidance.&nbsp; In many cases, this led to the deletion
+ of several guidance pages and the addition of several "common" guidance pages<br />
+ </li>
+ </ul>
+ </li>
+</ul>
+<p>
+ The following are the method elements that were added:
+</p>
+<ul>
+ <li>
+ Key concepts so they can be shared: 
+ <ul>
+ <li>
+ Concept: Analysis Mechanism
+ </li>
+ <li>
+ Concept: Architectural Goals
+ </li>
+ <li>
+ Concept: Architectural Constraints
+ </li>
+ <li>
+ Concept: Architecturally Significant Requirements
+ </li>
+ <li>
+ Concept: Key Abstractions
+ </li>
+ <li>
+ Concept: Architectural Views and Viewpoints
+ </li>
+ </ul>
+ </li>
+ <li>
+ Example: 4+1 Views of Software Architecture (just a rename and re-type of original Guideline: Architectural View)
+ </li>
+ <li>
+ Guideline: Representing Interfaces to External Systems (defined to share content between the Concept: Software
+ Architecture and the Task: Refine the Architecture)
+ </li>
+ <li>
+ Guideline: Using Visual Modeling (added to capture visual modeling techniques;&nbsp;content was originally in an
+ addendum to the Guideling: Abstract Away Complexity)
+ </li>
+ <li>
+ Guideline: Modeling the Architecture (added to capture information on visual architectural models)
+ </li>
+ <li>
+ Practice elements (elements common to all practices):
+ </li>
+ <li style="LIST-STYLE-TYPE: none">
+ <ul>
+ <li>
+ Roadmap: How to Adopt This Practice
+ </li>
+ <li>
+ Custom Category: Evolutionary Architecture Practice
+ </li>
+ <li>
+ Supporting Material: Evolutionary Architecture Practice Release Information<br />
+ </li>
+ </ul>
+ </li>
+</ul>
+<p>
+ The following are the method elements that were deleted:
+</p>
+<ul>
+ <li>
+ Guideline: Architectural Mechanisms (content merged with existing Concept: Architectural Mechanism to eliminate
+ redundancy)
+ </li>
+ <li>
+ Guideline: Determining Architecturally-Significant Requirements (content moved to new Concept: Architectural goals)
+ </li>
+ <li>
+ Guideline: Architectural View (replaced with new Example: 4+1 Views of Software Architecture)
+ </li>
+ <li>
+ Guideline: Outline the Architecture (content moved to more specific individual guidelines)
+ </li>
+ <li>
+ Guideline: Develop the Architecture (content moved to more specific individual guidelines<br />
+ </li>
+</ul></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/guidances/supportingmaterials/resources/whats_new.gif b/praclib/temp/practice.tech.evolutionary_arch.base/guidances/supportingmaterials/resources/whats_new.gif
new file mode 100644
index 0000000..7039631
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/guidances/supportingmaterials/resources/whats_new.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/guidances/templates/architecture_notebook.xmi b/praclib/temp/practice.tech.evolutionary_arch.base/guidances/templates/architecture_notebook.xmi
new file mode 100644
index 0000000..0babd7d
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/guidances/templates/architecture_notebook.xmi
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:GuidanceDescription 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="-h09djKXIOUJlez8h6UXrWw"
+ name=",_me8WcAANEdyRS9uciXlZ6g" guid="-h09djKXIOUJlez8h6UXrWw" changeDate="2007-05-11T18:20:56.100-0400">
+ <mainDescription><p>
+ Attached is a template applicable for describing the architecture for a small, co-located project.
+</p></mainDescription>
+ <attachments>resources/architecture_notebook_tpl.dot</attachments>
+</org.eclipse.epf.uma:GuidanceDescription>
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/guidances/templates/resources/architecture_notebook_tpl.dot b/praclib/temp/practice.tech.evolutionary_arch.base/guidances/templates/resources/architecture_notebook_tpl.dot
new file mode 100644
index 0000000..90bf6b5
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/guidances/templates/resources/architecture_notebook_tpl.dot
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/plugin.xmi b/praclib/temp/practice.tech.evolutionary_arch.base/plugin.xmi
new file mode 100644
index 0000000..1b99cc8
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/plugin.xmi
@@ -0,0 +1,308 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_4ggZgbPREduocbW-TPTq7A"
+ guid="_4ggZgbPREduocbW-TPTq7A">
+ <resourceDescriptors xmi:id="_m_D6YPL5Edm6Nvont3uinw" id="_17Ve8Nd6EdmIm-bsRSNCgw"
+ uri="guidances/checklists/architecture_notebook.xmi"/>
+ <resourceDescriptors xmi:id="_m-9zwvL5Edm6Nvont3uinw" id="_H4gOYKYTEdmvhNXG0Oc2uA"
+ uri="workproducts/architecture_notebook.xmi"/>
+ <resourceDescriptors xmi:id="_nGPgcPL5Edm6Nvont3uinw" id="_qDRSULBKEdm7Eph_l9Cn9w"
+ uri="tasks/envision_the_arch.xmi"/>
+ <resourceDescriptors xmi:id="_nGPgcfL5Edm6Nvont3uinw" id="_rUis8LBKEdm7Eph_l9Cn9w"
+ uri="tasks/evolve_the_arch.xmi"/>
+ <resourceDescriptors xmi:id="_XyiFAAAQEdyRS9uciXlZ6g" id="-h09djKXIOUJlez8h6UXrWw"
+ uri="guidances/templates/architecture_notebook.xmi"/>
+ <resourceDescriptors xmi:id="_v01uwM3lEdyjXslGsagg_w" id="-Iyj1LA3WbTQP_iQmRp7ibw"
+ uri="guidances/supportingmaterials/release_info_evolutionary_arch.xmi"/>
+ <resourceDescriptors xmi:id="_UKIOkNciEdy1nJEYZGzN4A" id="-KXvzdy6aJTFPQRS-UK5dvA"
+ uri="guidances/roadmaps/how_to_adopt_evolutionary_arch_practice.xmi"/>
+ <resourceDescriptors xmi:id="_2ymoAdcuEdy1nJEYZGzN4A" id="-mEJbo_5lG227hXMdftmX_A"
+ uri="guidances/guidelines/modeling_the_arch.xmi"/>
+ <resourceDescriptors xmi:id="_nualMdcwEdy1nJEYZGzN4A" id="-gEb0V8Q3YP6iExbEvpjZIg"
+ uri="customcategories/evolutionary_arch_practice.xmi"/>
+ <resourceDescriptors xmi:id="_tJV0MdfdEdy8T_PKWvNDBA" id="-5_3zlnRYAOz-wT6GBaWoNg"
+ uri="workproducts/architecture_notebook.vm.xmi"/>
+ <resourceDescriptors xmi:id="_wqBxQdqREdy88NBoQgfGyg" id="-tmKVpMZoAoS-Wkvbe_iHpQ"
+ uri="tasks/envision_the_arch.vm.xmi"/>
+ <resourceDescriptors xmi:id="_8KSvcdqREdy88NBoQgfGyg" id="-E459X-McFVuJGngiFPWf6w"
+ uri="tasks/refine_the_arch.vm.xmi"/>
+ <resourceDescriptors xmi:id="_gie0AdqTEdy88NBoQgfGyg" id="-KmIIyuXPr1pe5iREXAoMYw"
+ uri="workproducts/arch_notebook.res.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_4gaS4LPREduocbW-TPTq7A" name="practice.tech.evolutionary_arch.base"
+ guid="_4gaS4LPREduocbW-TPTq7A" briefDescription="The Evolutionary Architecture practice contains the method elements needed to analyze the major technical concerns that affect the solution and capture those architectural decisions to ensure that those decisions are assessed and communicated.
It is dependent on the core for slot definitions common work product definitions. It is dependent on the default navigation views so it can categorize its elements appropriately and is dependent on the copyright plug-in for access to the appropriate copyright."
+ changeDate="2008-01-28T16:24:45.656-0500">
+ <copyrightStatement href="uma://_iVydgENdEdy245g62lfWcA#_cTs20KzREduOqvpk_MDLfQ"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4gaS4bPREduocbW-TPTq7A"
+ name="Content" guid="_4gaS4bPREduocbW-TPTq7A">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4gaS4rPREduocbW-TPTq7A"
+ name="Categories" guid="_4gaS4rPREduocbW-TPTq7A">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4gaS47PREduocbW-TPTq7A"
+ name="Domains" guid="_4gaS47PREduocbW-TPTq7A"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4gaS5LPREduocbW-TPTq7A"
+ name="Disciplines" guid="_4gaS5LPREduocbW-TPTq7A"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4gaS5bPREduocbW-TPTq7A"
+ name="RoleSets" guid="_4gaS5bPREduocbW-TPTq7A"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4gaS5rPREduocbW-TPTq7A"
+ name="WP Types" guid="_4gaS5rPREduocbW-TPTq7A"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4gaS57PREduocbW-TPTq7A"
+ name="Tools" guid="_4gaS57PREduocbW-TPTq7A"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4gaS6LPREduocbW-TPTq7A"
+ name="StandardCategories" guid="_4gaS6LPREduocbW-TPTq7A"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4gaS6bPREduocbW-TPTq7A"
+ name="CustomCategories" guid="_4gaS6bPREduocbW-TPTq7A">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4gaS6rPREduocbW-TPTq7A"
+ name="Hidden" guid="_4gaS6rPREduocbW-TPTq7A">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_4gaS67PREduocbW-TPTq7A"
+ name="Custom Categories" guid="_4gaS67PREduocbW-TPTq7A" categorizedElements="_RBa6gJ-mEdyBk-WQzMU-FQ _G1sl0M3nEdyjXslGsagg_w"/>
+ </childPackages>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_RBa6gJ-mEdyBk-WQzMU-FQ"
+ name="evolutionary_arch_practice" guid="_RBa6gJ-mEdyBk-WQzMU-FQ" briefDescription="This practice analyzes the major technical concerns that affect the solution and captures those architectural decisions to ensure that those decisions are assessed and communicated."
+ presentationName="Evolutionary Architecture" shapeicon="customcategories/resources/pract_dgm32.gif"
+ nodeicon="customcategories/resources/pract_obj.gif" categorizedElements="_Odpz8NciEdy1nJEYZGzN4A _Cv-PAOCdEdy1GK0fgbL-TA _YLJ3MNcmEdy1nJEYZGzN4A _TPZH0NcmEdy1nJEYZGzN4A _HF_ykJ_7EdyBk-WQzMU-FQ _rA1NMc3lEdyjXslGsagg_w">
+ <presentation xmi:id="-gEb0V8Q3YP6iExbEvpjZIg" href="uma://-gEb0V8Q3YP6iExbEvpjZIg#-gEb0V8Q3YP6iExbEvpjZIg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_HF_ykJ_7EdyBk-WQzMU-FQ"
+ name="guidance" guid="_HF_ykJ_7EdyBk-WQzMU-FQ" presentationName="Guidance"
+ shapeicon="customcategories/resources/bookcL.gif" nodeicon="customcategories/resources/bookc.gif"
+ categorizedElements="_Wb51MNcoEdy1nJEYZGzN4A _9dW_ENdKEdyhuZi3112qsQ _IzV_4NdLEdyhuZi3112qsQ _J6RZcNdQEdyhuZi3112qsQ">
+ <methodElementProperty xmi:id="_SUr4kJ_7EdyBk-WQzMU-FQ" name="CategoryElementsSortType"
+ value="Manual"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_G1sl0M3nEdyjXslGsagg_w"
+ name="additions_to_nav_building_blocks" guid="_G1sl0M3nEdyjXslGsagg_w"
+ presentationName="Contributions to Navigation Building Blocks" categorizedElements="_Pr8NwM3nEdyjXslGsagg_w _B9jVsM3oEdyjXslGsagg_w _NhPbUM3oEdyjXslGsagg_w _zEzBENdQEdyhuZi3112qsQ _umVsQNQwEdyM_J8-fv54DA _slJQkNQwEdyM_J8-fv54DA __AL1ANdQEdyhuZi3112qsQ _JpBb8NdREdyhuZi3112qsQ"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_Pr8NwM3nEdyjXslGsagg_w"
+ name="release_info.evarch" guid="_Pr8NwM3nEdyjXslGsagg_w" variabilityType="contributes"
+ categorizedElements="_rA1NMc3lEdyjXslGsagg_w">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCIHYcRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_B9jVsM3oEdyjXslGsagg_w"
+ name="artifact_list.evarch" guid="_B9jVsM3oEdyjXslGsagg_w" variabilityType="contributes"
+ categorizedElements="_0XAf0MlgEdmt3adZL5Dmdw">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4YMRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_NhPbUM3oEdyjXslGsagg_w"
+ name="checklist_list.evarch" guid="_NhPbUM3oEdyjXslGsagg_w" variabilityType="contributes"
+ categorizedElements="_17PYUNd6EdmIm-bsRSNCgw">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_pGt9MMReEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_slJQkNQwEdyM_J8-fv54DA"
+ name="technical_practice_list.evarch" guid="_slJQkNQwEdyM_J8-fv54DA"
+ presentationName="Technical Practices" variabilityType="contributes"
+ categorizedElements="_RBa6gJ-mEdyBk-WQzMU-FQ">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_lBrxENQuEdyM_J8-fv54DA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_umVsQNQwEdyM_J8-fv54DA"
+ name="practice_list.evarch" guid="_umVsQNQwEdyM_J8-fv54DA" variabilityType="contributes"
+ categorizedElements="_RBa6gJ-mEdyBk-WQzMU-FQ">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCIHY8RdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_TPZH0NcmEdy1nJEYZGzN4A"
+ name="tasks" guid="_TPZH0NcmEdy1nJEYZGzN4A" presentationName="Tasks"
+ shapeicon="customcategories/resources/task_dgm32.gif" nodeicon="customcategories/resources/task_obj.gif"
+ categorizedElements="_0f-1oMlgEdmt3adZL5Dmdw _0gRJgMlgEdmt3adZL5Dmdw"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_YLJ3MNcmEdy1nJEYZGzN4A"
+ name="work_products" guid="_YLJ3MNcmEdy1nJEYZGzN4A" presentationName="Work Products"
+ shapeicon="customcategories/resources/workproduct_dgm32.gif" nodeicon="customcategories/resources/workproduct_obj.gif"
+ categorizedElements="_0XAf0MlgEdmt3adZL5Dmdw"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_Wb51MNcoEdy1nJEYZGzN4A"
+ name="guidelines" guid="_Wb51MNcoEdy1nJEYZGzN4A" briefDescription="Alphabetical list of guidelines for the practice."
+ presentationName="Guidelines" shapeicon="../core.default.nav_view.base/customcategories/resources/guide_dgm32.gif"
+ nodeicon="../core.default.nav_view.base/customcategories/resources/guide_obj.gif">
+ <methodElementProperty xmi:id="_tHbK4NcoEdy1nJEYZGzN4A" name="CategoryElementsSortType"
+ value="Alphabetic"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_OOB2AAouEdyhlpBPrduOMw#_we3F4ACpEdu8m4dIntu6jA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_OOB2AAouEdyhlpBPrduOMw#_vO2uoO0OEduUpsu85bVhiQ"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="#_HrgUQNcuEdy1nJEYZGzN4A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_9dW_ENdKEdyhuZi3112qsQ"
+ name="checklists" guid="_9dW_ENdKEdyhuZi3112qsQ" briefDescription="Alphabetical list of checklists for the practice."
+ presentationName="Checklists" shapeicon="../core.default.nav_view.base/customcategories/resources/checklist_dgm32.gif"
+ nodeicon="../core.default.nav_view.base/customcategories/resources/checklist_obj.gif"
+ categorizedElements="_17PYUNd6EdmIm-bsRSNCgw"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_IzV_4NdLEdyhuZi3112qsQ"
+ name="templates" guid="_IzV_4NdLEdyhuZi3112qsQ" briefDescription="Alphabetical list of included templates."
+ presentationName="Templates" shapeicon="../core.default.nav_view.base/customcategories/resources/template_dgm32.gif"
+ nodeicon="../core.default.nav_view.base/customcategories/resources/template_obj.gif"
+ categorizedElements="_me8WcAANEdyRS9uciXlZ6g"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_J6RZcNdQEdyhuZi3112qsQ"
+ name="examples" guid="_J6RZcNdQEdyhuZi3112qsQ" briefDescription="Alphabetical list of included examples."
+ presentationName="Examples" shapeicon="../core.default.nav_view.base/customcategories/resources/example_dgm32.gif"
+ nodeicon="../core.default.nav_view.base/customcategories/resources/example_obj.gif">
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Example" href="uma://_OOB2AAouEdyhlpBPrduOMw#_eQ_s8Om5Edupia_tZIXEqg"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Example" href="uma://_OOB2AAouEdyhlpBPrduOMw#_O39h0O9pEdu635i_iQ5Jag"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Example" href="uma://_OOB2AAouEdyhlpBPrduOMw#_4bC4cNs_EdyEW4klSH3vRA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_zEzBENdQEdyhuZi3112qsQ"
+ name="guideline_list.evarch" guid="_zEzBENdQEdyhuZi3112qsQ" variabilityType="contributes"
+ categorizedElements="_HrgUQNcuEdy1nJEYZGzN4A">
+ <methodElementProperty xmi:id="_5n0pMNdQEdyhuZi3112qsQ" name="CategoryElementsSortType"
+ value="Alphabetic"/>
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4ZcRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="__AL1ANdQEdyhuZi3112qsQ"
+ name="roadmap_list.evarch" guid="__AL1ANdQEdyhuZi3112qsQ" variabilityType="contributes"
+ categorizedElements="_Odpz8NciEdy1nJEYZGzN4A">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4ZsRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_JpBb8NdREdyhuZi3112qsQ"
+ name="template_list.evarch" guid="_JpBb8NdREdyhuZi3112qsQ" variabilityType="contributes"
+ categorizedElements="_me8WcAANEdyRS9uciXlZ6g">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4Z8RdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_Cv-PAOCdEdy1GK0fgbL-TA"
+ name="key_concepts" guid="_Cv-PAOCdEdy1GK0fgbL-TA" briefDescription="Alphabetical list of key concepts for the practice."
+ presentationName="Key Concepts" shapeicon="customcategories/resources/concept_dgm32.gif"
+ nodeicon="customcategories/resources/concept_obj.gif">
+ <methodElementProperty xmi:id="_Cw2_0OCdEdy1GK0fgbL-TA" name="CategoryElementsSortType"
+ value="Manual"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#__O7tAMVvEduLYZUGfgZrkQ"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_mzxI0A4LEduibvKwrGxWxA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_kgtcoNc8Edyd7OybSySFxg"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4gaS7LPREduocbW-TPTq7A"
+ name="CoreContent" guid="_4gaS7LPREduocbW-TPTq7A">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_xhaxgKtYEdytrdP46hWyHg"
+ name="Evolutionary Architecture Practice" guid="_xhaxgKtYEdytrdP46hWyHg">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="__EXZIKtYEdytrdP46hWyHg"
+ name="Architecture Modeling" guid="__EXZIKtYEdytrdP46hWyHg">
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_HrgUQNcuEdy1nJEYZGzN4A"
+ name="modeling_the_arch" guid="_HrgUQNcuEdy1nJEYZGzN4A" briefDescription="This guidelines provides some recommendations on the types of visual architecture models you may want to develop."
+ presentationName="Modeling the Architecture">
+ <presentation xmi:id="-mEJbo_5lG227hXMdftmX_A" href="uma://-mEJbo_5lG227hXMdftmX_A#-mEJbo_5lG227hXMdftmX_A"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_0SsecNr8EdyXE6np2_hUMA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_G0xGANfdEdy8T_PKWvNDBA"
+ name="architecture_notebook.vm" guid="_G0xGANfdEdy8T_PKWvNDBA" variabilityType="contributes"
+ variabilityBasedOnElement="_0XAf0MlgEdmt3adZL5Dmdw" guidelines="_HrgUQNcuEdy1nJEYZGzN4A">
+ <presentation xmi:id="-5_3zlnRYAOz-wT6GBaWoNg" href="uma://-5_3zlnRYAOz-wT6GBaWoNg#-5_3zlnRYAOz-wT6GBaWoNg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_s4ojQNqREdy88NBoQgfGyg"
+ name="envision_the_arch.vm" guid="_s4ojQNqREdy88NBoQgfGyg" variabilityType="contributes"
+ variabilityBasedOnElement="_0f-1oMlgEdmt3adZL5Dmdw" guidelines="_HrgUQNcuEdy1nJEYZGzN4A">
+ <presentation xmi:id="-tmKVpMZoAoS-Wkvbe_iHpQ" href="uma://-tmKVpMZoAoS-Wkvbe_iHpQ#-tmKVpMZoAoS-Wkvbe_iHpQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_1kmN0NqREdy88NBoQgfGyg"
+ name="refine_the_arch.vm" guid="_1kmN0NqREdy88NBoQgfGyg" variabilityType="contributes"
+ variabilityBasedOnElement="_0gRJgMlgEdmt3adZL5Dmdw" guidelines="_HrgUQNcuEdy1nJEYZGzN4A">
+ <presentation xmi:id="-E459X-McFVuJGngiFPWf6w" href="uma://-E459X-McFVuJGngiFPWf6w#-E459X-McFVuJGngiFPWf6w"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_NInusM3iEdyjXslGsagg_w"
+ name="Resources" guid="_NInusM3iEdyjXslGsagg_w" briefDescription="This package contains the resources (e.g., templates, examples, reports, etc.) associated with the Evolutionary Architecture Practice. These resources are in a separate pacakge to make them easy to de-select from a configuration and replace with customized resources.">
+ <contentElements xsi:type="org.eclipse.epf.uma:Template" xmi:id="_me8WcAANEdyRS9uciXlZ6g"
+ name="architecture_notebook" guid="_me8WcAANEdyRS9uciXlZ6g" briefDescription="Template for describing the architecture."
+ presentationName="Architecture Notebook">
+ <presentation xmi:id="-h09djKXIOUJlez8h6UXrWw" href="uma://-h09djKXIOUJlez8h6UXrWw#-h09djKXIOUJlez8h6UXrWw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_QHYwcM3jEdyjXslGsagg_w"
+ name="arch_notebook.res" guid="_QHYwcM3jEdyjXslGsagg_w" variabilityType="contributes"
+ variabilityBasedOnElement="_0XAf0MlgEdmt3adZL5Dmdw" templates="_me8WcAANEdyRS9uciXlZ6g">
+ <presentation xmi:id="-KmIIyuXPr1pe5iREXAoMYw" href="uma://-KmIIyuXPr1pe5iREXAoMYw#-KmIIyuXPr1pe5iREXAoMYw"/>
+ </contentElements>
+ </childPackages>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_0f-1oMlgEdmt3adZL5Dmdw"
+ name="envision_the_arch" guid="_0f-1oMlgEdmt3adZL5Dmdw" briefDescription="This task is where the initial "vision" for the architecture is developed through analysis of the architecturally significant requirements and identification of architectural constraints, decisions and objectives. "
+ presentationName="Envision the Architecture" output="_0XAf0MlgEdmt3adZL5Dmdw">
+ <presentation xmi:id="_qDRSULBKEdm7Eph_l9Cn9w" href="uma://_qDRSULBKEdm7Eph_l9Cn9w#_qDRSULBKEdm7Eph_l9Cn9w"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_HrZGIA4MEduibvKwrGxWxA"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_mzxI0A4LEduibvKwrGxWxA"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_HlRqANpbEdyP58ppo1Ieaw"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_jdKSsNpiEdyP58ppo1Ieaw"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_pLEGUNqGEdy88NBoQgfGyg"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_0gpkAMlgEdmt3adZL5Dmdw"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_vO2uoO0OEduUpsu85bVhiQ"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_we3F4ACpEdu8m4dIntu6jA"/>
+ <mandatoryInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_i3vkoLS-EduDY8LNbMCDBA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_0gRJgMlgEdmt3adZL5Dmdw"
+ name="evolve_the_arch" guid="_0gRJgMlgEdmt3adZL5Dmdw" briefDescription="Refine the architecture to an appropriate level of detail to support development."
+ presentationName="Evolve the Architecture" output="_0XAf0MlgEdmt3adZL5Dmdw">
+ <presentation xmi:id="_rUis8LBKEdm7Eph_l9Cn9w" href="uma://_rUis8LBKEdm7Eph_l9Cn9w#_rUis8LBKEdm7Eph_l9Cn9w"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_mzxI0A4LEduibvKwrGxWxA"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_HrZGIA4MEduibvKwrGxWxA"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_O1kAANvfEduv2KOT-Teh6w"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_HlRqANpbEdyP58ppo1Ieaw"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_pLEGUNqGEdy88NBoQgfGyg"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_0YP18MlgEdmt3adZL5Dmdw"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_jdKSsNpiEdyP58ppo1Ieaw"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_vO2uoO0OEduUpsu85bVhiQ"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_0gjdYMlgEdmt3adZL5Dmdw"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_we3F4ACpEdu8m4dIntu6jA"/>
+ <mandatoryInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_i3vkoLS-EduDY8LNbMCDBA"/>
+ <mandatoryInput xsi:type="org.eclipse.epf.uma:Artifact" href="#_0XAf0MlgEdmt3adZL5Dmdw"/>
+ <optionalInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_IcQOUEqdEdyi3_jfs__bIQ"/>
+ <optionalInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_Vux8UEfUEdyiPI8btkmvmw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Checklist" xmi:id="_17PYUNd6EdmIm-bsRSNCgw"
+ name="architecture_notebook" guid="_17PYUNd6EdmIm-bsRSNCgw" briefDescription="This checklist provides questions to help in evaluating whether architectural decisions have been captured appropriately."
+ presentationName="Architecture Notebook">
+ <presentation xmi:id="_17Ve8Nd6EdmIm-bsRSNCgw" href="uma://_17Ve8Nd6EdmIm-bsRSNCgw#_17Ve8Nd6EdmIm-bsRSNCgw"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_mzxI0A4LEduibvKwrGxWxA"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_jdKSsNpiEdyP58ppo1Ieaw"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_HlRqANpbEdyP58ppo1Ieaw"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_HrZGIA4MEduibvKwrGxWxA"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_pLEGUNqGEdy88NBoQgfGyg"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_0YP18MlgEdmt3adZL5Dmdw"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_vO2uoO0OEduUpsu85bVhiQ"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_0gjdYMlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_SPSs0NcSEdy1nJEYZGzN4A"
+ name="technical_architecture_slot.evarch" guid="_SPSs0NcSEdy1nJEYZGzN4A"
+ variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_8OD-cLPTEduocbW-TPTq7A"/>
+ <containedArtifacts xmi:id="_0XAf0MlgEdmt3adZL5Dmdw" name="architecture_notebook"
+ guid="_0XAf0MlgEdmt3adZL5Dmdw" briefDescription="This artifact describes the rationale, assumptions, explanations and implications of the decisions that were made in forming the architecture. "
+ presentationName="Architecture Notebook" checklists="_17PYUNd6EdmIm-bsRSNCgw">
+ <presentation xmi:id="_H4gOYKYTEdmvhNXG0Oc2uA" href="uma://_H4gOYKYTEdmvhNXG0Oc2uA#_H4gOYKYTEdmvhNXG0Oc2uA"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#__O7tAMVvEduLYZUGfgZrkQ"/>
+ </containedArtifacts>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Roadmap" xmi:id="_Odpz8NciEdy1nJEYZGzN4A"
+ name="how_to_adopt_evolutionary_arch_practice" guid="_Odpz8NciEdy1nJEYZGzN4A"
+ briefDescription="This roadmap describes how to adopt the Evolutionary Architecture Practice."
+ presentationName="How to Adopt This Practice">
+ <presentation xmi:id="-KXvzdy6aJTFPQRS-UK5dvA" href="uma://-KXvzdy6aJTFPQRS-UK5dvA#-KXvzdy6aJTFPQRS-UK5dvA"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#__O7tAMVvEduLYZUGfgZrkQ"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_rA1NMM3lEdyjXslGsagg_w"
+ name="Release Info" guid="_rA1NMM3lEdyjXslGsagg_w">
+ <contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="_rA1NMc3lEdyjXslGsagg_w"
+ name="release_info_evolutionary_arch" guid="_rA1NMc3lEdyjXslGsagg_w"
+ presentationName="Evolutionary Architecture Practice" nodeicon="guidances/supportingmaterials/resources/whats_new.gif">
+ <presentation xmi:id="-Iyj1LA3WbTQP_iQmRp7ibw" href="uma://-Iyj1LA3WbTQP_iQmRp7ibw#-Iyj1LA3WbTQP_iQmRp7ibw"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_4gaS7bPREduocbW-TPTq7A"
+ name="CapabilityPatterns" guid="_4gaS7bPREduocbW-TPTq7A">
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_ejTSsMQOEduMu5zRIJX95g"
+ name="Basic Technical Architecture Practice Patterns" guid="_ejTSsMQOEduMu5zRIJX95g"/>
+ </childPackages>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_4gaS7rPREduocbW-TPTq7A"
+ name="DeliveryProcesses" guid="_4gaS7rPREduocbW-TPTq7A"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_4gaS77PREduocbW-TPTq7A"
+ name="ProcessContributions" guid="_4gaS77PREduocbW-TPTq7A"/>
+ <bases href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2AAouEdyhlpBPrduOMw"/>
+ <bases href="uma://_iVydgENdEdy245g62lfWcA#_iVydgENdEdy245g62lfWcA"/>
+ <bases href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0ELXuEduGP_98XMd0fg"/>
+ <bases href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno4EKmEdyrauqpmnA8jQ"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/tasks/envision_the_arch.vm.xmi b/praclib/temp/practice.tech.evolutionary_arch.base/tasks/envision_the_arch.vm.xmi
new file mode 100644
index 0000000..bb76611
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/tasks/envision_the_arch.vm.xmi
@@ -0,0 +1,13 @@
+<?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.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="-tmKVpMZoAoS-Wkvbe_iHpQ"
+ name=",_s4ojQNqREdy88NBoQgfGyg" guid="-tmKVpMZoAoS-Wkvbe_iHpQ">
+ <keyConsiderations><p>
+ At this stage, you may find it useful to develop a draft version of your architectural models.&nbsp; For more
+ information, see <a class="elementLinkWithType"
+ href="./../../practice.tech.evolutionary_arch.base/guidances/guidelines/architecture_models_8BE6E55B.html"
+ guid="_HrgUQNcuEdy1nJEYZGzN4A">Guideline: Architecture Models</a>.
+</p></keyConsiderations>
+</org.eclipse.epf.uma:TaskDescription>
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/tasks/envision_the_arch.xmi b/praclib/temp/practice.tech.evolutionary_arch.base/tasks/envision_the_arch.xmi
new file mode 100644
index 0000000..33d8257
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/tasks/envision_the_arch.xmi
@@ -0,0 +1,229 @@
+<?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.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="_qDRSULBKEdm7Eph_l9Cn9w"
+ name="envision_the_arch,_0f-1oMlgEdmt3adZL5Dmdw" guid="_qDRSULBKEdm7Eph_l9Cn9w"
+ changeDate="2008-02-20T15:46:40.984-0500" version="1.0.0">
+ <mainDescription><p>
+ This task focuses on outlining the initial architectural decisions that will guide development and testing. It relies
+ on gathering experience gained in similar systems or problem domains to constrain and focus the architecture so that
+ effort is not wasted in re-inventing architecture.
+</p>
+<p>
+ The results are captured for future reference and are communicated across the team. It is important that the team has
+ enough information to understand the technical approach being taken.
+</p>
+<p>
+ Architectural envisioning is usually done at the beginning of the project. A few people get together in a room and
+ sketch out what they think the architecture will be. This envisioning effort sets the foundation for prototyping. If
+ the solution is similar to a previously produced solution (or is a well-known solution domain), then it will probably
+ be good enough to reference that example as evidence of the feasibility of the approach. In some cases, it may be
+ necessary to develop one or more prototypes to validate some of the decisions or clarify some of the requirements.
+</p>
+<p>
+ The work done here does not seek to produce a detailed and comprehensive technical specification for the system.
+ Rather, the approach should be to decide the overall technical approach at a high level. The conclusion of this work
+ should produce just enough information to communicate the architecture to the team, and to demonstrate its viability to
+ the customer. This allows the project to move forward, enabling you to refine and baseline the architecture.
+</p></mainDescription>
+ <keyConsiderations><p>
+ When envisioning the architecture, it is important to reduce the complexity of the&nbsp;solution by raising the levels
+ of abstraction.&nbsp; For more information, see <a class="elementLinkWithType"
+ href="./../../core.tech.common.base/guidances/guidelines/abstract_away_complexity_DBF13AE6.html"
+ guid="_we3F4ACpEdu8m4dIntu6jA">Guideline: Abstract Away Complexity</a>.
+</p>
+<p>
+ It is critical that this task be performed collaboratively with active involvement of other team members and project
+ stakeholders so that consensus and common understanding is reached. It is particularly vital to involve the
+ developer(s) throughout this task. The architecture effort&nbsp;is about providing leadership and coordination of the
+ technical work rather than putting in a solo performance.
+</p></keyConsiderations>
+ <sections xmi:id="_3nMQQA3rEduibvKwrGxWxA" name="Identify architectural goals" guid="_3nMQQA3rEduibvKwrGxWxA">
+ <sectionDescription><p>
+ Identifying architectural goals is all about deciding what architecturally-significant things you plan to focus
+ on.&nbsp; Look at the requirements and work with the team to describe the goals for the architecture. These goals
+ should be regularly reviewed to&nbsp;make sure&nbsp;that they are still valid and that the system is on track to
+ deliver them.
+</p>
+<p>
+ For more information, see <a class="elementLinkWithType"
+ href="./../../core.tech.common.base/guidances/concepts/arch_goals_CB41D8AE.html"
+ guid="_HlRqANpbEdyP58ppo1Ieaw">Concept: Architectural Goals</a>.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_I32E4MP2EdmWKcx6ixEiwg" name="Identify key abstractions" guid="_I32E4MP2EdmWKcx6ixEiwg">
+ <sectionDescription><p>
+ Identify the key concepts and abstractions that the system needs to handle. The requirements are good sources for key
+ abstractions.&nbsp; Don't spend too much time describing&nbsp;abstractions in detail at this initial stage, because
+ there is a risk that spending too much time will result in identifying classes and relationships that the solution does
+ not actually need.
+</p>
+<p>
+ When&nbsp;identifying&nbsp;key abstractions, it can be useful to also define any obvious relationships that exist
+ between them.&nbsp;These can be captured in a table or&nbsp;in diagrams (in a tool or whiteboard.&nbsp;In general, it
+ is not worth agonizing over defining a highly detailed set of relationships at this early stage in design. The
+ relationships will become more concrete and detailed later and will&nbsp;probably modify&nbsp;these
+ early&nbsp;assumptions.&nbsp;
+</p>
+<p>
+ For more information, see <a class="elementLinkWithType"
+ href="./../../core.tech.common.base/guidances/concepts/key_abstractions_1474DBF2.html"
+ guid="_pLEGUNqGEdy88NBoQgfGyg">Concept: Key Abstractions</a>.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_f0y2kM25Edym_ZFqrJcXUg" name="Identify architecturally significant requirements"
+ guid="_f0y2kM25Edym_ZFqrJcXUg">
+ <sectionDescription><p>
+ Identify which of the current requirements are architecturally significant.&nbsp;Explore and refine those&nbsp;that
+ must be implemented in order to realize the <a class="elementLink"
+ href="./../../core.tech.common.base/guidances/concepts/arch_goals_CB41D8AE.html"
+ guid="_HlRqANpbEdyP58ppo1Ieaw">Architectural Goals</a>. See <a class="elementLinkWithType"
+ href="./../../core.tech.common.base/guidances/concepts/arch_significant_requirements_1EE5D757.html"
+ guid="_HrZGIA4MEduibvKwrGxWxA">Concept: Architecturally Significant Requirements</a>&nbsp;for more information.
+</p>
+<p>
+ Architecturally significant requirements that are poorly understood or likely to change should be prioritized for
+ clarification and stabilization. In some cases, this means further requirements analysis should be done before
+ implementing the requirement. In other cases, some form of prototyping may be best.
+</p>
+<p>
+ In addition to identifying which of the requirements are architecturally significant, it is also important to propose
+ an approach for meeting those requirements.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_9o6Z4CSCEdqDjNgZyGMf5w" name="Identify constraints on the architecture"
+ guid="_9o6Z4CSCEdqDjNgZyGMf5w">
+ <sectionDescription><p>
+ Gather information about the existing&nbsp;environment and identify any constraints in the solution. List any
+ constraints on the architecture and any trade-offs between competing requirements and resources. Decide how the
+ architecture will meet these issues. Justify each of the decisions made and capture this information. Regularly review
+ the list of constraints to make sure that they are still valid and that no new ones have appeared.
+</p>
+<p>
+ For more information, see <a class="elementLinkWithType"
+ href="./../../core.tech.common.base/guidances/concepts/arch_constraints_AE56B662.html"
+ guid="_jdKSsNpiEdyP58ppo1Ieaw">Concept: Architectural Constraints</a>.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_B899cMP2EdmWKcx6ixEiwg" name="Identify reuse opportunities" guid="_B899cMP2EdmWKcx6ixEiwg">
+ <sectionDescription><p>
+ Survey, assess, and select available assets.&nbsp; Identify assets from other areas that may be reused in the current
+ architecture. For more information, see <a class="elementLinkWithType"
+ href="./../../practice.tech.evolutionary_design.base/guidances/guidelines/software_reuse_B6B04C26.html"
+ guid="_vO2uoO0OEduUpsu85bVhiQ">Guideline: Software Reuse</a>.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_FVrlsMP2EdmWKcx6ixEiwg" name="Define approach for partitioning the system"
+ guid="_FVrlsMP2EdmWKcx6ixEiwg">
+ <sectionDescription><p>
+ Decide how to partition the software, both in logical and physical terms. Partitioning your system helps you manage its
+ complexity by using the well-known "divide and conquer" strategy. By breaking the process into smaller and more
+ manageable pieces, you make development easier.
+</p>
+<p>
+ As a minimum, decide on:
+</p>
+<ul>
+ <li>
+ How to partition the software when managing development (the use of layering as a partitioning strategy, for
+ example).&nbsp; For more information, see <a class="elementLinkWithType"
+ href="./../../core.tech.common.base/guidances/guidelines/layering_F169CF07.html"
+ guid="_0gpkAMlgEdmt3adZL5Dmdw">Guideline: Layering</a>.
+ </li>
+ <li>
+ How the software will be composed at run time.
+ </li>
+</ul>
+<p>
+ For each software partition, briefly describe
+</p>
+<ul>
+ <li>
+ Its name and purpose.
+ </li>
+ <li>
+ Its relationships to other partitions.
+ </li>
+</ul>
+<p>
+ At this point, you do not need to identify the elements that should be placed in each of these partitions.&nbsp;
+ Instead, you define how many partitions you will need and how they should be related. Later, during&nbsp;design
+ activities, you decide which elements will populate these partitions.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_tmvWwE5cEducxZ_XZXh-vw" name="Define approach for deploying the system"
+ guid="_tmvWwE5cEducxZ_XZXh-vw">
+ <sectionDescription><p>
+ Describe the overall approach for how the software will be deployed over the nodes on the network. For example,
+ determine if the system needs to be accessed remotely, or has requirements that suggest distribution across multiple
+ nodes.
+</p>
+<p>
+ Some sources of information to consider are:
+</p>
+<ul>
+ <li>
+ users at geographical locations
+ </li>
+ <li>
+ organization of business data
+ </li>
+ <li>
+ service level requirements
+ </li>
+ <li>
+ constraints (such as requirements to interface with legacy systems)
+ </li>
+</ul>
+<p>
+ Work with stakeholders such as network support and deployment teams to ensure that the proposed approach is a good fit
+ for the wider technical environment.
+</p>
+<p>
+ Validate that the proposed deployment approach supports users (especially those users at remote locations if this is
+ required) performing typical&nbsp;usage scenarios&nbsp;while satisfying nonfunctional requirements and constraints.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_KBAsYMP2EdmWKcx6ixEiwg" name="Identify architectural mechanisms"
+ guid="_KBAsYMP2EdmWKcx6ixEiwg">
+ <sectionDescription><p>
+ Make a list of the&nbsp;technical services that the system needs to provide and capture some basic information about
+ each item on the list. It's generally a good idea to make an initial&nbsp;list of all the mechanisms required for the
+ project and then prioritize the development of those that need to be&nbsp;delivered to achieve the architectural goals.
+</p>
+<p>
+ At this point, usually only the analysis mechanisms are defined.&nbsp; However, specific <a class="elementLink"
+ href="./../../core.tech.common.base/guidances/concepts/arch_constraints_AE56B662.html"
+ guid="_jdKSsNpiEdyP58ppo1Ieaw">Architectural Constraints</a>&nbsp;may mean that some of those mechanisms can be
+ described as design mechanisms (even at this early stage).
+</p>
+<p>
+ For more information on architectural mechanisms, see <a class="elementLinkWithType"
+ href="./../../core.tech.common.base/guidances/concepts/arch_mechanism_2932DFB6.html"
+ guid="_mzxI0A4LEduibvKwrGxWxA">Concept: Architectural Mechanism</a>.&nbsp;
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_RKSLsNp3EdyItewP9R0w7Q" name="Identify interfaces to external systems"
+ guid="_RKSLsNp3EdyItewP9R0w7Q">
+ <sectionDescription><p>
+ At this point, identify the external systems with which this system must interact.&nbsp; An external system may be
+ anything from software to hardware units that the current system will use, such as printers, terminals, alarm devices,
+ and sensors.
+</p>
+<p>
+ Describe thpose interfaces at a high level, concentrating on the information that must pass between the systems.
+</p></sectionDescription>
+ </sections>
+ <purpose><p>
+ To outline a technical approach to the system that supports the project requirements, within the constraints placed on
+ the system and the development team.
+</p>
+<p>
+ To provide sufficient guidance and direction for the team to begin development.
+</p></purpose>
+ <alternatives><p>
+ This task&nbsp;is most&nbsp;needed when developing new and unprecedented systems. In systems where there is already a
+ well-defined architecture, this task may be omitted and replaced with a&nbsp;review of the existing architecture.
+</p></alternatives>
+</org.eclipse.epf.uma:TaskDescription>
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/tasks/evolve_the_arch.xmi b/praclib/temp/practice.tech.evolutionary_arch.base/tasks/evolve_the_arch.xmi
new file mode 100644
index 0000000..d54c8cb
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/tasks/evolve_the_arch.xmi
@@ -0,0 +1,195 @@
+<?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.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="_rUis8LBKEdm7Eph_l9Cn9w"
+ name="evolve_the_arch,_0gRJgMlgEdmt3adZL5Dmdw" guid="_rUis8LBKEdm7Eph_l9Cn9w"
+ changeDate="2008-02-15T13:49:15.750-0500" version="1.0.0">
+ <mainDescription><p>
+ This task&nbsp;builds upon the outlined architecture and makes concrete and unambiguous architectural decisions to
+ support development.&nbsp; It takes into&nbsp;account any design and implementation work products that have been
+ developed so far.&nbsp; In other words, the architecture evolves as the solution is designed and implemented, and the
+ architecture documentation is updated to reflect any changes made during development. This is&nbsp;a key,&nbsp;since
+ the actual implementation is the only real "proof" that the software architecture is viable and provides the definitive
+ basis for validating the suitability&nbsp;of the architecture.&nbsp; For more information, see <a
+ class="elementLinkWithType" href="./../../core.tech.common.base/guidances/concepts/executable_arch_D4E68CBD.html"
+ guid="_O1kAANvfEduv2KOT-Teh6w">Concept: Executable Architecture</a>.
+</p>
+<p>
+ The results are captured for future reference and are communicated across the team.
+</p></mainDescription>
+ <keyConsiderations><p>
+ When evolving the architecture, it is important to continue to reduce the complexity of the&nbsp;solution by raising
+ the levels of abstraction.&nbsp; For more information, see <a class="elementLinkWithType"
+ href="./../../core.tech.common.base/guidances/guidelines/abstract_away_complexity_DBF13AE6.html"
+ guid="_we3F4ACpEdu8m4dIntu6jA">Guideline: Abstract Away Complexity</a>.
+</p>
+<p>
+ You should also continue the collaboration with the whole&nbsp;team on the refining of the architecture in order to
+ promote consensus and a common understanding of the overall solution. You should be working to coordinate and guide the
+ technical activities of the team, rather than seeking to do all the work alone.&nbsp;Place special emphasis&nbsp;on
+ involving&nbsp;the developer(s) throughout this task since its the developed solution that will prove out the
+ architecture and may result in refinements to the architecture documentation.
+</p>
+<p>
+ Ensure that those who need to act upon the architectural work&nbsp;understand&nbsp;it and are able to work with
+ it.&nbsp;Make sure that the description of the architecture clearly conveys not only the solution but also the
+ motivation and objectives related to the&nbsp;decisions that have been made in shaping the architecture. This will make
+ it easier for others to understand the architecture and to adapt it over time.
+</p>
+<p>
+ You can communicate your decisions as many ways as you wish.&nbsp; For example:
+</p>
+<ul>
+ <li>
+ Publication of&nbsp;reference source code
+ </li>
+ <li>
+ Publication of&nbsp;reference models
+ </li>
+ <li>
+ Publication of&nbsp;software architecture documentation
+ </li>
+ <li>
+ Formal&nbsp;presentations of the material
+ </li>
+ <li>
+ Informal walkthroughs of the architecture
+ </li>
+</ul></keyConsiderations>
+ <sections xmi:id="_l92AYNpaEdyP58ppo1Ieaw" name="Refine the architectural goals and architecturally-significant requirements"
+ guid="_l92AYNpaEdyP58ppo1Ieaw">
+ <sectionDescription><p>
+ Work with the team, especially the stakeholders and the requirements team, to review the status of the <a
+ class="elementLink" href="./../../core.tech.common.base/guidances/concepts/arch_goals_CB41D8AE.html"
+ guid="_HlRqANpbEdyP58ppo1Ieaw">Architectural Goals</a>&nbsp;and <a class="elementLink"
+ href="./../../core.tech.common.base/guidances/concepts/arch_significant_requirements_1EE5D757.html"
+ guid="_HrZGIA4MEduibvKwrGxWxA">Architecturally Significant Requirements</a>&nbsp;and refine, as needed. It may be that
+ some new architecturally-significant requirements have been introduced or your architectural goals and priorities may
+ have changed.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_G_k1kBaqEduSTJywppIxVQ" name="Identify architecturally significant design elements"
+ guid="_G_k1kBaqEduSTJywppIxVQ">
+ <sectionDescription><p align="left">
+ Identify concrete&nbsp;design elements (such as <a class="elementLink"
+ href="./../../core.tech.common.base/guidances/concepts/component_CB167D48.html"
+ guid="_0YP18MlgEdmt3adZL5Dmdw">Component</a>s, classes and&nbsp;subsystems)&nbsp;and provide at least a name and brief
+ description for each.
+</p>
+<p align="left">
+ The following are some good sources for design elements:
+</p>
+<ul>
+ <li>
+ <div align="left">
+ <div align="left">
+ <a class="elementLink"
+ href="./../../core.tech.common.base/guidances/concepts/arch_significant_requirements_1EE5D757.html"
+ guid="_HrZGIA4MEduibvKwrGxWxA">Architecturally Significant Requirements</a>. Highlight the areas of the
+ architecture that participate in realizing, or implementing, the requirements.
+ </div>
+ </div>
+ </li>
+ <li>
+ <div align="left">
+ <div align="left">
+ <a class="elementLink"
+ href="./../../core.tech.common.base/guidances/concepts/key_abstractions_1474DBF2.html"
+ guid="_pLEGUNqGEdy88NBoQgfGyg">Key Abstractions</a>
+ </div>
+ </div>
+ </li>
+ <li>
+ <div align="left">
+ <div align="left">
+ Components that encapsulate the system's interface with external systems.&nbsp; For more information, see
+ <a class="elementLinkWithType"
+ href="./../../core.tech.common.base/guidances/guidelines/repres_interfaces_to_ext_systems_51A34F6E.html"
+ guid="_0gjdYMlgEdmt3adZL5Dmdw">Guideline: Representing Interfaces to External Systems</a>
+ </div>
+ </div>
+ </li>
+ <li>
+ Components that implement the <a class="elementLink"
+ href="./../../core.tech.common.base/guidances/concepts/arch_mechanism_2932DFB6.html"
+ guid="_mzxI0A4LEduibvKwrGxWxA">Architectural Mechanism</a>s
+ </li>
+ <li>
+ Architectural and key design <a class="elementLink"
+ href="./../../core.tech.common.base/guidances/concepts/pattern_10BE6D96.html"
+ guid="_0YJvUMlgEdmt3adZL5Dmdw">Pattern</a>s. Apply the chosen patterns to define a new set of elements that conform
+ to the patterns.
+ </li>
+</ul>
+<p>
+ Identifying components will help hide the complexity of the system and help you work at a higher level. Components need
+ to be internally cohesive and to provide external services through a limited interface.&nbsp; At this point, interfaces
+ do not need to be as detailed as a signature, but they do need to document what the elements need, what they can use,
+ and what they can depend on.
+</p>
+<p>
+ Component identification can be&nbsp;based on architectural layers, deployment choices, or key abstractions. Ask
+ yourself these questions:
+</p>
+<ul>
+ <li>
+ What is logically or functionally related (same use case or service, for example)?
+ </li>
+ <li>
+ What entities provide services to multiple others?
+ </li>
+ <li>
+ What entities depend on each other? Strongly or weakly?
+ </li>
+ <li>
+ What entities should you be able to exchange independently from others?
+ </li>
+ <li>
+ What will run on the same processor or network node?
+ </li>
+ <li>
+ What parts are constrained by similar performance requirements?
+ </li>
+</ul>
+<p>
+ When you identify a componentm be sure to briefly describe the functionality that should be allocated to the
+ components.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_0qoQ8CikEduQBKSg5n118w" name="Refine architectural mechanisms"
+ guid="_0qoQ8CikEduQBKSg5n118w">
+ <sectionDescription><p>
+ Refine&nbsp;the applicable <a class="elementLink"
+ href="./../../core.tech.common.base/guidances/concepts/arch_mechanism_2932DFB6.html"
+ guid="_mzxI0A4LEduibvKwrGxWxA">Architectural Mechanism</a>s, as needed to support the design.&nbsp; For example,
+ refining an analysis mechanism into a design mechanism and/or refining a design mechanism into an implementation
+ mecahanism.&nbsp;<br />
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_Vdln8MP3EdmWKcx6ixEiwg" name="Identify additional reuse opportunities"
+ guid="_Vdln8MP3EdmWKcx6ixEiwg">
+ <sectionDescription><p dir="ltr" style="MARGIN-RIGHT: 0px">
+ Continue to look for more opportunities to reuse existing assets.&nbsp; Where applicable, identify existing components
+ that could be built to be reused.
+</p>
+<p dir="ltr" style="MARGIN-RIGHT: 0px">
+ For more information, see <a class="elementLinkWithType"
+ href="./../../practice.tech.evolutionary_design.base/guidances/guidelines/software_reuse_B6B04C26.html"
+ guid="_vO2uoO0OEduUpsu85bVhiQ">Guideline: Software Reuse</a>.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_xIIVkMUbEdu5GrwIlTJV7g" name="Map the software to the hardware"
+ guid="_xIIVkMUbEdu5GrwIlTJV7g">
+ <sectionDescription><p align="left">
+ Produce a precise map of deployable software components to network nodes. Map the architecturally significant design
+ elements to the target deployment environment. Work with hardware and network specialists to ensure that the hardware
+ is sufficient to meet the needs of the system; and that any new hardware is available in time.
+</p>
+<p>
+ Validate that the nodes and connections are adequate to support the anticipated interactions between components on
+ different nodes, and between components and their stored data.
+</p></sectionDescription>
+ </sections>
+ <purpose>To make and document the architectural decisions necessary to support development.</purpose>
+</org.eclipse.epf.uma:TaskDescription>
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/tasks/refine_the_arch.vm.xmi b/praclib/temp/practice.tech.evolutionary_arch.base/tasks/refine_the_arch.vm.xmi
new file mode 100644
index 0000000..d3b281e
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/tasks/refine_the_arch.vm.xmi
@@ -0,0 +1,13 @@
+<?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.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="-E459X-McFVuJGngiFPWf6w"
+ name=",_1kmN0NqREdy88NBoQgfGyg" guid="-E459X-McFVuJGngiFPWf6w" changeDate="2008-02-13T19:15:20.609-0500">
+ <keyConsiderations><p>
+ As you evolve the architecture, you may wish to evolve your architectural models.&nbsp; For more information, see <a
+ class="elementLinkWithType"
+ href="./../../practice.tech.evolutionary_arch.base/guidances/guidelines/architecture_models_8BE6E55B.html"
+ guid="_HrgUQNcuEdy1nJEYZGzN4A">Guideline: Architecture Models</a>.
+</p></keyConsiderations>
+</org.eclipse.epf.uma:TaskDescription>
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/workproducts/arch_notebook.res.xmi b/praclib/temp/practice.tech.evolutionary_arch.base/workproducts/arch_notebook.res.xmi
new file mode 100644
index 0000000..970cdd2
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/workproducts/arch_notebook.res.xmi
@@ -0,0 +1,13 @@
+<?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"
+ 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>
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/workproducts/architecture_notebook.vm.xmi b/praclib/temp/practice.tech.evolutionary_arch.base/workproducts/architecture_notebook.vm.xmi
new file mode 100644
index 0000000..e4aed55
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/workproducts/architecture_notebook.vm.xmi
@@ -0,0 +1,12 @@
+<?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="-5_3zlnRYAOz-wT6GBaWoNg"
+ name="new_artifact,_G0xGANfdEdy8T_PKWvNDBA" guid="-5_3zlnRYAOz-wT6GBaWoNg" changeDate="2008-02-15T11:35:13.921-0500"
+ version="7.2.0">
+ <representationOptions>A&nbsp;set of architecture models could be developed as part of the architectural documentation.&nbsp;&nbsp;For more
+information, see&nbsp;&nbsp;<a class="elementLinkWithType"
+href="./../../practice.tech.evolutionary_arch.base/guidances/guidelines/modeling_the_arch_8BE6E55B.html"
+guid="_HrgUQNcuEdy1nJEYZGzN4A">Guideline: Modeling the Architecture</a>.</representationOptions>
+</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/praclib/temp/practice.tech.evolutionary_arch.base/workproducts/architecture_notebook.xmi b/praclib/temp/practice.tech.evolutionary_arch.base/workproducts/architecture_notebook.xmi
new file mode 100644
index 0000000..f8522c5
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_arch.base/workproducts/architecture_notebook.xmi
@@ -0,0 +1,47 @@
+<?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="_H4gOYKYTEdmvhNXG0Oc2uA"
+ name="architecture_notebook,_0XAf0MlgEdmt3adZL5Dmdw" guid="_H4gOYKYTEdmvhNXG0Oc2uA"
+ changeDate="2008-02-15T10:48:35.515-0500" version="1.0.0">
+ <mainDescription><p>
+ This artifact&nbsp;describes the <a class="elementLink"
+ href="./../../core.tech.common.base/guidances/concepts/software_architecture_59A08DE0.html"
+ guid="__O7tAMVvEduLYZUGfgZrkQ">Software Architecture</a>.
+</p>
+<p>
+ It provides a place for maintaining the list of architectural issues, along with the associated architectural
+ decisions, designs, patterns, code documented (or pointed at),etc. all&nbsp;at appropriate level to make it easy to
+ understand what architectural decisions have been made, and are still left to be made.
+</p></mainDescription>
+ <purpose>To capture and make architectural decisions, and explain those decisions to developers.&nbsp;</purpose>
+ <briefOutline><p>
+ At a minimum, this artifact should :
+</p>
+<ul>
+ <li>
+ Describe the goals and philosophy of the architecture
+ </li>
+ <li>
+ Identify assumptions and dependencies
+ </li>
+ <li>
+ Reference the architecturally significant requirements
+ </li>
+ <li>
+ Describe the architectural mechanisms, and
+ </li>
+ <li>
+ Describe decisions and constraints with their justifications.
+ </li>
+</ul>
+<p>
+ Consider adding more information when it's appropriate. A small project shouldn't spend lots of time documenting the
+ architecture, but all critical elements of the system must be communicated to current and future team members.
+</p>
+<p>
+ Consider including useful architectural views, references to architecturally significant areas of the design, key
+ abstractions, critical system interface descriptions, and a description of the architectural framework or pattern.
+</p></briefOutline>
+</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/praclib/temp/practice.tech.evolutionary_design.assign/.project b/praclib/temp/practice.tech.evolutionary_design.assign/.project
new file mode 100644
index 0000000..465d33a
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.assign/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>practice.tech.evolutionary_design.assign</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/practice.tech.evolutionary_design.assign/plugin.xmi b/praclib/temp/practice.tech.evolutionary_design.assign/plugin.xmi
new file mode 100644
index 0000000..365b658
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.assign/plugin.xmi
@@ -0,0 +1,92 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_XPLEAMudEdyRPtFYRAKVDg"
+ guid="_XPLEAMudEdyRPtFYRAKVDg">
+ <resourceDescriptors xmi:id="_Uf9gUPvuEdqf0-top1XJIg" id="-xbAirPdH1IOKcnklk8hdqw"
+ uri="roles/developer_vm.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_XPLD8MudEdyRPtFYRAKVDg" name="practice.tech.evolutionary_design.assign"
+ guid="_XPLD8MudEdyRPtFYRAKVDg" briefDescription="Assignments for the Evolutionary Design practice."
+ changeDate="2008-01-25T15:30:25.567-0800">
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_XPLD8cudEdyRPtFYRAKVDg"
+ name="Content" guid="_XPLD8cudEdyRPtFYRAKVDg">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_XPLD8sudEdyRPtFYRAKVDg"
+ name="Categories" guid="_XPLD8sudEdyRPtFYRAKVDg">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_XPLD88udEdyRPtFYRAKVDg"
+ name="Domains" guid="_XPLD88udEdyRPtFYRAKVDg">
+ <contentElements xsi:type="org.eclipse.epf.uma:Domain" xmi:id="__YEaAMueEdyRPtFYRAKVDg"
+ name="development_domain.assign" guid="__YEaAMueEdyRPtFYRAKVDg" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Domain" href="uma://_MRPloEFXEdy9ENCpSugIjA#_5JQLoK80Edy9cPK11VzBuQ"/>
+ <workProducts xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_0WuL8slgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_XPLD9MudEdyRPtFYRAKVDg"
+ name="Disciplines" guid="_XPLD9MudEdyRPtFYRAKVDg">
+ <contentElements xsi:type="org.eclipse.epf.uma:Discipline" xmi:id="_6ByR0MueEdyRPtFYRAKVDg"
+ name="development_discipline.assign" guid="_6ByR0MueEdyRPtFYRAKVDg"
+ variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Discipline" href="uma://_MRPloEFXEdy9ENCpSugIjA#_iGSHsVZ-EdyIUdvDLLUdeg"/>
+ <tasks href="uma://_Z2cK0LPPEduocbW-TPTq7A#_0fshwMlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_XPLD9cudEdyRPtFYRAKVDg"
+ name="RoleSets" guid="_XPLD9cudEdyRPtFYRAKVDg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_XPLD9sudEdyRPtFYRAKVDg"
+ name="WP Types" guid="_XPLD9sudEdyRPtFYRAKVDg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_XPLD98udEdyRPtFYRAKVDg"
+ name="Tools" guid="_XPLD98udEdyRPtFYRAKVDg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_XPLD-MudEdyRPtFYRAKVDg"
+ name="StandardCategories" guid="_XPLD-MudEdyRPtFYRAKVDg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_XPLD-cudEdyRPtFYRAKVDg"
+ name="CustomCategories" guid="_XPLD-cudEdyRPtFYRAKVDg">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_XPLD-sudEdyRPtFYRAKVDg"
+ name="Hidden" guid="_XPLD-sudEdyRPtFYRAKVDg">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_XPLD-8udEdyRPtFYRAKVDg"
+ name="Custom Categories" guid="_XPLD-8udEdyRPtFYRAKVDg"/>
+ </childPackages>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_XPLD_MudEdyRPtFYRAKVDg"
+ name="CoreContent" guid="_XPLD_MudEdyRPtFYRAKVDg">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_elKkoMueEdyRPtFYRAKVDg"
+ name="Role Assignments" guid="_elKkoMueEdyRPtFYRAKVDg">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Ks_WoOCiEdynptYdmll41Q"
+ name="Visual Modeling" guid="_Ks_WoOCiEdynptYdmll41Q" briefDescription="Role assignments for visual modeling.">
+ <contentElements xsi:type="org.eclipse.epf.uma:Role" xmi:id="_sypCEPvjEdqf0-top1XJIg"
+ name="developer_vm" guid="_sypCEPvjEdqf0-top1XJIg" variabilityType="contributes"
+ variabilityBasedOnElement="_iQSykMueEdyRPtFYRAKVDg">
+ <presentation xmi:id="-xbAirPdH1IOKcnklk8hdqw" href="uma://-xbAirPdH1IOKcnklk8hdqw#-xbAirPdH1IOKcnklk8hdqw"/>
+ </contentElements>
+ </childPackages>
+ <contentElements xsi:type="org.eclipse.epf.uma:Role" xmi:id="_iQSykMueEdyRPtFYRAKVDg"
+ name="developer.assign_wp" guid="_iQSykMueEdyRPtFYRAKVDg" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Role" href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
+ <responsibleFor xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_0WuL8slgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_texdMMueEdyRPtFYRAKVDg"
+ name="design_solution.assign_role" guid="_texdMMueEdyRPtFYRAKVDg" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Task" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_0fshwMlgEdmt3adZL5Dmdw"/>
+ <performedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0VxJsMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0X9iEMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_dTa6gMAYEdqX-s4mWhkyqQ"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0ZM4MclgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_XPLD_cudEdyRPtFYRAKVDg"
+ name="CapabilityPatterns" guid="_XPLD_cudEdyRPtFYRAKVDg"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_XPLD_sudEdyRPtFYRAKVDg"
+ name="DeliveryProcesses" guid="_XPLD_sudEdyRPtFYRAKVDg"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_XPLD_8udEdyRPtFYRAKVDg"
+ name="ProcessContributions" guid="_XPLD_8udEdyRPtFYRAKVDg"/>
+ <bases href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPloEFXEdy9ENCpSugIjA"/>
+ <bases href="uma://_A118oMYaEdyXeo04os5BOw#_A118oMYaEdyXeo04os5BOw"/>
+ <bases href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK0LPPEduocbW-TPTq7A"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/practice.tech.evolutionary_design.assign/roles/developer_vm.xmi b/praclib/temp/practice.tech.evolutionary_design.assign/roles/developer_vm.xmi
new file mode 100644
index 0000000..d26f2e6
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.assign/roles/developer_vm.xmi
@@ -0,0 +1,11 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:RoleDescription 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="-xbAirPdH1IOKcnklk8hdqw"
+ name="new_role,_sypCEPvjEdqf0-top1XJIg" guid="-xbAirPdH1IOKcnklk8hdqw" changeDate="2006-09-11T11:34:39.535-0700">
+ <skills><p>
+ In addition, to create a visual model of the system, this role needs the ability to&nbsp;render the design in the
+ Unified Modeling Language (UML).
+</p></skills>
+</org.eclipse.epf.uma:RoleDescription>
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/.project b/praclib/temp/practice.tech.evolutionary_design.base/.project
new file mode 100644
index 0000000..2bb8b66
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>practice.tech.evolutionary_design.base</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/customcategories/resources/bookc.gif b/praclib/temp/practice.tech.evolutionary_design.base/customcategories/resources/bookc.gif
new file mode 100644
index 0000000..7f2ab85
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/customcategories/resources/bookc.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/customcategories/resources/bookcL.gif b/praclib/temp/practice.tech.evolutionary_design.base/customcategories/resources/bookcL.gif
new file mode 100644
index 0000000..6c5b064
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/customcategories/resources/bookcL.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/customcategories/resources/pract_dgm32.gif b/praclib/temp/practice.tech.evolutionary_design.base/customcategories/resources/pract_dgm32.gif
new file mode 100644
index 0000000..f597332
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/customcategories/resources/pract_dgm32.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/customcategories/resources/pract_obj.gif b/praclib/temp/practice.tech.evolutionary_design.base/customcategories/resources/pract_obj.gif
new file mode 100644
index 0000000..fe8075a
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/customcategories/resources/pract_obj.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/guidances/checklists/design.xmi b/praclib/temp/practice.tech.evolutionary_design.base/guidances/checklists/design.xmi
new file mode 100644
index 0000000..b7ac323
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/guidances/checklists/design.xmi
@@ -0,0 +1,147 @@
+<?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"
+ 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">
+ <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>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_7DUXMNTQEduaE6F4-SvXzg" name="Is the design consistent?" guid="_7DUXMNTQEduaE6F4-SvXzg">
+ <sectionDescription><ul>
+ <li>
+ Does the design follow any design standards?
+ </li>
+ <li>
+ Does&nbsp;the design&nbsp;apply other idioms consistently?
+ </li>
+ <li>
+ Are the names of the design elements consistent and easy to interpret?
+ </li>
+ <li>
+ Does any part of the design contradict another part of it in such a way that puts the project at risk?
+ </li>
+ <li>
+ If the design is rendered visually, is the notation used to&nbsp;describe the design used consistently so that it
+ can be understood and is not ambiguous?
+ </li>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_V_LgsNTREduaE6F4-SvXzg" name="Is the design maintainable?" guid="_V_LgsNTREduaE6F4-SvXzg">
+ <sectionDescription><ul>
+ <li>
+ Is the design structured well enough to be maintained?
+ </li>
+ <li>
+ Is the design set up to appropriately accommodate expected changes? The design should not be overdone to handle
+ <em>any</em> possible change, just reasonably expected changes.
+ </li>
+ <li>
+ Have redundant areas of the design been removed so that the implementation does not contain redundant code?
+ </li>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_ySbT4NTREduaE6F4-SvXzg" name="Is the design 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>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_tywgENTQEduaE6F4-SvXzg" name="Does the design reflect 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>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_nMogoNTQEduaE6F4-SvXzg" name="Are the design elements 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>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_19E2INTQEduaE6F4-SvXzg" name="Can the system 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>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_F_AWwNTTEduaE6F4-SvXzg" name="Does 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>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_upZp0NT0EduaE6F4-SvXzg" name="Does 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>
+ </sections>
+ <sections xmi:id="_Nqih0NVREduaE6F4-SvXzg" name="Does the design support a coarse-grained perspective of the system?"
+ guid="_Nqih0NVREduaE6F4-SvXzg">
+ <sectionDescription><ul>
+ <li>
+ Can the design be understood as a set of higher-order subsystems?
+ </li>
+ <li>
+ Are the subsystem dependencies documented?
+ </li>
+ <li>
+ Are interfaces clearly defined for each subsystem? Is each subsystem designed so that its services can be accessed
+ through the interface without a need to access internal parts?
+ </li>
+ <li>
+ Is each subsystem designed so that someone can work within one part without having to understand the internal parts
+ of the other elements?
+ </li>
+</ul></sectionDescription>
+ </sections>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/guidances/checklists/design_vm.xmi b/praclib/temp/practice.tech.evolutionary_design.base/guidances/checklists/design_vm.xmi
new file mode 100644
index 0000000..6d0220e
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/guidances/checklists/design_vm.xmi
@@ -0,0 +1,118 @@
+<?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: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="-HQSI39vBrjpmQL1qHYOJtA"
+ name="new_checklist,_nnSXcD6SEduAL-bCqar_dg" guid="-HQSI39vBrjpmQL1qHYOJtA" version="1.0.0">
+ <sections xmi:id="_sG8ZoD6SEduAL-bCqar_dg" name="Packages and Organization" guid="_sG8ZoD6SEduAL-bCqar_dg">
+ <sectionDescription><p>
+ Is the package partitioning logical and consistent? Does it make sense to team members and stakeholders?
+</p>
+<p>
+ Do package names accurately describe the contents of the package and the role they play in the architecture? Do they
+ follow naming conventions?
+</p>
+<p>
+ Do public packages and interfaces provide a logically cohesive set of services?
+</p>
+<p>
+ Are all the contents of a package listed? Are the classes within a package cohesive?
+</p>
+<p>
+ Do package dependencies correspond to the dependencies of the contained classes?
+</p>
+<p>
+ Are there packages or classes within a package that can be separated into and independent or sub-package?<br />
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_tx6tsD6SEduAL-bCqar_dg" name="Views" guid="_tx6tsD6SEduAL-bCqar_dg">
+ <sectionDescription><p>
+ Does each diagram help the designer reason about the design, or communicate key design decisions to the team?
+</p>
+<p>
+ Are the relationships between diagrams clear when several diagrams are used to describe behavior?
+</p>
+<p>
+ Is it easy to navigate between related diagrams?
+</p>
+<p>
+ Does each diagram focus on a relevant perspective? For instance, does a set of diagrams show a single class and its
+ direct relationships, rather than using&nbsp;one or two diagrams to show all classes?
+</p>
+<p>
+ Is each diagram complete and minimal? Does it show everything relevant to that view and nothing more?
+</p>
+<p>
+ Are the diagrams tidy and easy to interpret, with a minimum of clutter?
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_yeFh4D6SEduAL-bCqar_dg" name="UML" guid="_yeFh4D6SEduAL-bCqar_dg">
+ <sectionDescription><p>
+ Does the visual model conform to UML standards so all stakeholders can understand the model over time? See the&nbsp;<a
+ href="http://www.uml.org/" target="_blank">OMG UML Resource Page</a>&nbsp;for more information.
+</p>
+<p>
+ Does the visual model conform to project or organization specific modeling standards?
+</p>Is the visual model internally consistent? For instance, if an object diagram shows a relationship between objects,
+does a corresponding relationship exist between the appropriate classes?<br />
+<p>
+ Does the name of each class clearly reflect the role it plays?
+</p>
+<p>
+ Does each class offer the required behavior?
+</p>
+<p>
+ Is there at least one&nbsp;realization association defined for each interface? The realization may represent a 3rd
+ party implementation of the subsystem.
+</p>
+<p>
+ Are&nbsp;there dependency associations from each subsystem to the interfaces it uses?
+</p>
+<p>
+ Is each operation in a subsystem interface described in a sequence diagram? Or at least mapped directly to an operation
+ in a class?
+</p>
+<p>
+ Does each class represent a single well defined abstraction?
+</p>
+<p>
+ Are generalization relationships used only to inherit definitions, not behavior (implementation)? In other words, is
+ behavior shared through the use of association, aggregation and containment relationships instead of generalization?
+</p>
+<p>
+ Are parent classes in generalization relationships abstract? Are the "leaf" classes in a generalization hierarchy the
+ only concrete classes?
+</p>
+<p>
+ Are stereotypes used consistently and meaningfully?
+</p>
+<p>
+ Do&nbsp;statecharts exist for classes with complex or restrictive state changes?
+</p>
+<p>
+ Do relationships have descriptive role or association names (one or the other but not both), and&nbsp;correct
+ multiplicities?
+</p>
+<p>
+ Are relationships between classes unidirectional whenever possible?<br />
+ &nbsp;
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_IsDY4D6TEduAL-bCqar_dg" name="Non-UML Visual Modeling" guid="_IsDY4D6TEduAL-bCqar_dg">
+ <sectionDescription><p>
+ Are the semantics of the visual modeling language clearly defined, documented, and accessible to team members? The
+ semantics should be meaninful to the users of the model.
+</p>
+<p>
+ Can the semantics of the modeling language be understood over time? Is the language documented well enough so that team
+ members can understand the model long after design decisions have taken place?
+</p>
+<p>
+ Are team members and stakeholders trained in the modeling language being used?
+</p>
+<p>
+ Does the visual model conform to the semantics of the visual modeling language? In other words, are the meanings
+ of&nbsp;the symbols in the diagrams&nbsp;consistent across the model and diagrams?&nbsp;
+</p></sectionDescription>
+ </sections>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/guidances/concepts/design.xmi b/praclib/temp/practice.tech.evolutionary_design.base/guidances/concepts/design.xmi
new file mode 100644
index 0000000..5a5ed4f
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/guidances/concepts/design.xmi
@@ -0,0 +1,118 @@
+<?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="-c5Uh71vXTPN-VmrGYVRV7w"
+ name=",_bFjlAPTYEduDKIuqTXQ8SA" guid="-c5Uh71vXTPN-VmrGYVRV7w" changeDate="2008-02-21T10:13:08.843-0800"
+ version="7.2.0">
+ <mainDescription><p>
+ Designing a system is about creating the internal structure and behavior of a system that's robust, extensible, and
+ high-quality. Good design improves quality and makes a system easier to maintain and extend, while a poor design can
+ significantly raise the cost of producing and maintaining the software.
+</p>
+<p>
+ Design is an abstraction of the code that presents the system from a perspective that makes it easier to address the
+ structure and behavior of the software. This can be done through viewing the code, but it's more difficult and less
+ effective to address structural and behavioral issues this way. Design can be visual models, simple sketches, text
+ descriptions, etc. The critical element of design is that it describes how different elements of the system interact to
+ fulfill the requirements.
+</p>
+<p>
+ The amount of design that's formally documented and maintained will vary depending on the criticality of the design and
+ how much of the design needs to be communicated to future team members. At a minimum, all architecturally significant
+ design elements should be documented and kept up-to-date with the implementation. These are critical aspects of the
+ system that are necessary for the understanding and maintenance of the software. Other important or complex structure
+ and behavior may be maintained as well. And some contracts may require that the entire design is throughly documented.
+</p>
+<p>
+ On many projects there will probably be aspects of the design that are only documented for the purpose of creating a
+ solution or walking through how certain behavior will be realized. It may not be worth the overhead of maintaining this
+ information as the design is transformed through refactoring and other influences. However, it may be useful to archive
+ the initial decisions, whiteboard images, or files so they can be referenced in the future if necessary. These can be
+ viewed as "old meeting minutes" that are stored for potential future reference. They may not reflect the current
+ design, but they may still provide useful insight.
+</p>
+<h3>
+ Multiple Passes
+</h3>
+<p>
+ The design will be revisited many times throughout an iterative lifecycle and even within an iteration. Each time some
+ design activity is being performed, it will be performed in the context of a specific goal. The goal might be to
+ identify a notional set of participants in a collaboration that can be exercised to realize the behavior required (an
+ analysis pass). The goal might be in the identification of some coarse-grained elements that are required to act out
+ some scenario (an architectural pass). Then a pass might be done within one of those components to identify the
+ elements within that will collaborate together to perform the behavior required (a more detailed design pass).<br />
+ <br />
+ Design might be performed in a particular context such as database context, user-interface context, or perhaps the
+ context of how some existing library will be applied. In these cases the design steps will be performed just to make
+ and communicate decisions regarding that context
+</p>
+<p>
+ Avoid analysis paralysis. Avoid refining, extending, and improving the design beyond a minimal version that suffices to
+ cover the needs of the requirements within the architecture. Design should be done in small chunks, proven via
+ implementation, improved via refactoring, and integrated into the baseline to provide value to the stakeholders.
+</p>
+<h3>
+ Design versus Architecture
+</h3>
+<p>
+ Design is a real thing, the construction of the system’s structure and behavior. Architecture [link to concept on
+ Software Architecture] defines principles, contexts, and constraints on the system’s construction. Architecture is
+ described in architecture artifacts, but it’s realized as design (visual or otherwise) and implementation.<br />
+ <br />
+ One way to look at architecture is that it helps to make the entire design more cohesive with itself by balancing the
+ needs of the entire system. Design tends to focus on one area at a time. Architecture helps assure the design is
+ consistent and appropriate to the goals of the system. For instance, there may be constraints placed on most of the
+ design to support the performance of one part of the system, such as improving access to a legacy system. Failure to
+ conform to those constraints in the design may cause the system to fail to meet the performance requirements of the
+ legacy system access. Conforming to the architecture assures that all the goals of the system are met by balancing
+ competing technical issues.
+</p>
+<h3>
+ Quality of Design
+</h3>
+<h4>
+ You Aren't Going to Need It
+</h4>
+<p>
+ The YAGNI principle is a good general approach to design. While designs should be robust enough to modify, re-use, and
+ maintain, it should also be as simple as possible. One of the ways to keep it simple is to make few assumptions about
+ what the design's going to need in the future. Don't assume you'll need something until you know you need it, then do a
+ good job of adding it. Add what's needed for the current requirement or iteration. Refactor the design as necessary
+ when more functionality needs to be added or the design must be made more complex to deal with new circumstances.
+</p>
+<h4>
+ Coupling and Cohesion
+</h4>
+<p>
+ Two of the most fundamental principles of design are coupling and cohesion. A good design contains elements that have
+ high cohesion and low coupling. High cohesion means that a single element, such as a class or subsystem, is composed of
+ parts that are closely related or work closely together to fulfill some purpose. Low coupling means that the elements
+ of a system have a minimum of dependencies on each other. A single element such as a subsystem should be easily
+ replaceable by another subsystem that provides similar behavior.<br />
+ <br />
+ For example, in a payroll system an Employee class would have high cohesion if it contained elements and functions such
+ as Name, Tax ID Number, and Monthly Salary. At first, it may seem as if the Calculate Paycheck functional would also be
+ cohesive. But when you consider that hourly employees must be paid overtime, sales people must have commission
+ calculated for them, etc, the function is less related to Employee and should probably be its own class or
+ subsystem.<br />
+ <br />
+ An example of low coupling would be if the Calculate Paycheck subsystem can be easily replaced by third party that may
+ be more robust and offer more features.<br />
+ <br />
+ Coupling and cohesion are so important to be aware of because they arise in so many design principles and design
+ strategies such as patterns.
+</p>
+<h4>
+ Open-Closed Principle
+</h4>
+<p>
+ Elements in the design should be “open” for extension but “closed” for modification. The goal of this principle is to
+ create software than can be extended without changing code&nbsp;<a class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/tech_references_6CCF393.html#MEY97"
+ guid="_9ToeIB83Edqsvps02rpOOg">[MEY97]</a>. This is because every change to software runs the risk of introducing bugs
+ into code that’s already correct. It also allows functionality to be re-used without having to know the details of the
+ implementation, reducing the time it takes to create something new. Keeping this principle in mind helps make a design
+ more maintainable.<br />
+</p>&nbsp;</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/guidances/concepts/resources/testFirstDesign.jpg b/praclib/temp/practice.tech.evolutionary_design.base/guidances/concepts/resources/testFirstDesign.jpg
new file mode 100644
index 0000000..6da383c
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/guidances/concepts/resources/testFirstDesign.jpg
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/analyze_the_design.xmi b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/analyze_the_design.xmi
new file mode 100644
index 0000000..2a8f79a
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/analyze_the_design.xmi
@@ -0,0 +1,130 @@
+<?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="-1vS_ELnQxGQKwfCrRYrc7w"
+ name="new_guideline,__MnggPTdEduDKIuqTXQ8SA" guid="-1vS_ELnQxGQKwfCrRYrc7w" changeDate="2008-02-15T07:35:47.343-0500">
+ <mainDescription><h1>
+ Identification of elements
+</h1>
+<p>
+ Identify the elements, based on the needs of the requirements. The identification of elements can stem from a static
+ perspective of walking through the requirements and identifying elements clearly called out, which is a form of domain
+ modeling. This can pull in other elements identified as being in the application domain or deemed necessary from
+ examining the requirements for the portion of the system being designed. This identification can also pull from key
+ abstractions identified while defining the architecture.
+</p>
+<p>
+ The identification of elements should also apply a dynamic perspective by walking through scenarios of use of the
+ system (or subsystem) and identifying elements needed to support the behavior. That behavior might be a scenario of use
+ from an external user perspective or, while designing a subsystem, a responsibility assigned to the subsystem that has
+ complex algorithmic behavior. Consider applying the <a class="elementLink"
+ href="./../../../core.tech.common.base/guidances/guidelines/entity_control_boundary_pattern_C4047897.html"
+ guid="_uF-QYEAhEdq_UJTvM1DM2Q">Entity-Control-Boundary Pattern</a> to identify the elements necessary to support the
+ scenario, or apply other patterns identified in the architecture that specify the elements that will be used to support
+ specific aspects of the scenario.
+</p>
+<p>
+ If you are designing a real-time system, include elements to represent events and signals that allow you to describe
+ the asynchronous triggers of behavior to which the system must respond. <b>Events</b> are specifications of interesting
+ occurrences in time and space that usually (if they are noteworthy) require some response from the system.
+ <b>Signals</b> represent asynchronous mechanisms used to communicate certain types of events within the system.
+</p>
+<p>
+ If there are existing elements from previous passes over the design or from selected frameworks or other reusable
+ elements, reuse them whenever possible. See <a class="elementLinkWithType"
+ href="./../../../nullsoftware_reuse_B6B04C26.html" guid="_vO2uoO0OEduUpsu85bVhiQ">Guideline: Software Reuse</a>.
+</p>
+<p>
+ After identifying the elements, give each one meaningful name. Each element should also have a description, so that the
+ team members who work together to refine the design and implement from the design will understand the role that each
+ element plays.
+</p>
+<p>
+ Based on this information, the identification of elements could be applied several times in designing just one part of
+ the system. Although there is no one correct strategy for multiple passes, they could be done at a coarse-grained level
+ and then a fine-grained level, or at an analysis (abstract) level and then a design level.
+</p>
+<h1>
+ Behavior of elements
+</h1>
+<p>
+ To identify the behavior of the elements, go through scenarios and assign behavior to the appropriate collaborating
+ participants. If a particular use of the system or subsystem can have multiple possible outcomes or variant sequences,
+ cover enough scenarios to ensure that the design is robust enough to support the possibilities.
+</p>
+<p>
+ When assigning behavior to elements, consider applying the <a class="elementLink"
+ href="./../../../core.tech.common.base/guidances/guidelines/entity_control_boundary_pattern_C4047897.html"
+ guid="_uF-QYEAhEdq_UJTvM1DM2Q">Entity-Control-Boundary Pattern</a>&nbsp;or other patterns identified in the
+ architecture.
+</p>
+<p>
+ Behavior can be represented as a simple statement of responsibility, or it can be a detailed operation specification.
+ Use the appropriate level of detail to communicate important design decisions while giving the freedom to make
+ appropriate implementation decisions as those tasks ensue.
+</p>
+<p>
+ Avoid too much identification of behavior solely from the perspective of domain modeling. Include only behavior that is
+ really needed -- behavior identified by going through required scenarios of system use.
+</p>
+<p>
+ Behavior must be understood as a responsibility of an element, as well as an interaction between two elements in the
+ context of some broader behavior of the system or subsystem. The latter part of this will lead the developer to
+ identify relationships that are necessary between the elements.
+</p>
+<h1>
+ Design element relationships
+</h1>
+<p>
+ The relationships between the elements necessary for the behavior must be designed. This can simply be the
+ identification of the ability to traverse from one element to another or else a need to manage an association between
+ the elements. Relationships can be designed in more detail, as appropriate. This can include: optionality,
+ multiplicity, whether the relationship is a simple dependency or managed association, and so on. These decisions that
+ drive implementation details are best made at the design level, where it is easier to see how all of the pieces fit
+ together.
+</p>
+<p>
+ Avoid defining too many relationships based on relationships in the application domain. Include only relationships that
+ are needed based on the requirements. On the other hand, a combination of requirements knowledge and domain knowledge
+ can lead to some detailed decisions on the relationships, such as optionality and multiplicity.
+</p>
+<h1>
+ Analysis classes and YAGNI
+</h1>
+<p>
+ Analysis classes are used to identify initial buckets where system functionality should go. They're the first pass at
+ understanding where system behavior will be realized in the design and implementation. For example, an entity class
+ might initially represent all of the behavior for an employee, such as storing personal information and calculating the
+ value of a paycheck. Few assumptions are made about how the final design will look at this point. Analysis classes are
+ about making sure required behavior is represented somewhere in the system, rather than about creating a perfect
+ design.
+</p>
+<p>
+ Analysis classes allow you to begin designing from abstractions, so that the details of the system depend on those
+ abstractions and not the other way around. In the Employee class, the notion of an employee should start with the idea
+ of someone who works for the company, who has responsibilities and receives benefits. It’s easier to create a design
+ from this simple idea. The complexity of the design should emerge from the abstract ideas of what the design needs to
+ do. This will also help keep coupling low and cohesion high.
+</p>
+<p>
+ YAGNI (You Aren't Going to Need It) is an approach to design where the developer creates only enough implementation and
+ design to address the required functionality. No assumptions are made about re-use or possible future uses of the
+ software. Software is improved when the system requirements demand more functionality or robustness.
+</p>
+<p>
+ The first classes created from a YAGNI perspective are much like analysis classes. You don't know how complex it may be
+ to calculate a paycheck for your employee, so you assume that functionality is highly cohesive with the rest of what
+ the Employee class must do. As you understanding of the requirement develops, the analysis class evolves into a set of
+ collaborating classes and patterns that better support the behavior of the system. For example, payroll calculations
+ could be moved into a pattern that handles all of the different types of paycheck calculations (overtime, commissions,
+ and so forth), thereby increasing the internal cohesion of the class.
+</p>
+<p>
+ Use analysis classes to define an initial place to put system behavior, and add only enough behavior to satisfy the
+ YAGNI perspective. Analysis classes will evolve into concrete design classes as more behavior is added and as the
+ design is refactored. See <a class="elementLinkWithType"
+ href="./../../../practice.tech.evolutionary_design.base/guidances/guidelines/evolve_the_design_3C9D6965.html"
+ guid="_C4U9QPTeEduDKIuqTXQ8SA">Guideline: Evolve the Design</a>.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/designing_visually.xmi b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/designing_visually.xmi
new file mode 100644
index 0000000..14d49c4
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/designing_visually.xmi
@@ -0,0 +1,198 @@
+<?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: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="-1xE2ZW3MjNAJ7jkaZNbkww"
+ name="visual_modeling,_1fM3AC9_EduW5uTjiIcspQ" guid="-1xE2ZW3MjNAJ7jkaZNbkww"
+ changeDate="2006-11-21T11:21:26.464-0800" version="1.0.0">
+ <mainDescription><h3>
+ Introduction
+</h3>
+<p>
+ Using visual modeling techniques to design software can help break down complex problems into a series of smaller,
+ easier to manage tasks. Sharing pictures rather than written documents or source code also helps the understanding and
+ communication of difficult concepts. Adopting standard modeling notations such as the UML increases this capability by
+ helping to make diagrams precise and unambiguous.
+</p>
+<p>
+ The degree of formality used when producing and disseminating models should vary according to your needs. Small,
+ collaborative teams modeling around whiteboards and capturing the results on a sheet of paper or with digital cameras
+ can yield good results. This can also help the team focus on producing software with the help of models; rather than
+ becoming sidetracked into over-engineering both the models and the solution. Modeling tools provide additional value to
+ projects, especially for more complex systems. Their specifics of use are outside the scope of this guideline, however.
+</p>
+<p>
+ This guideline does not describe a formal sequential progression through prescriptive design steps. Whether some or all
+ of these techniques are needed, or how long is spent on them will vary depending on real-world issues such as the
+ complexity of the requirements; the experience of the designer; and the way the team works.
+</p>
+<p>
+ This guideline uses a simplified scenario (Login) to help keep the focus on understanding the techniques rather than
+ the specific requirements. In the real-world, it is doubtful that much time would be spent modeling a simple problem.
+ Here is the use case diagram, for reference;
+</p>
+<p>
+ <img height="142" alt="User Login Use Case Model" src="./resources/UserLoginUCM.JPG" width="472" />
+</p>
+<h3>
+ Identify elements
+</h3>
+<p>
+ Render the identified design elements as classes in a UML diagram.&nbsp; Apply appropriate stereotypes and optionally
+ render the class using an icon specific to the stereotype to characterize the intent of the class in the design.&nbsp;
+ Name and briefly describe the classes in a few sentences. Do not spend too much time working on associations, as these
+ will be developed through working on collaborations in the next step.
+</p>
+<p>
+ Classes can be drawn as a basic UML rectangle or with a specific symbol associated with a particular stereotype.
+</p>
+<p>
+ The resulting class diagram should be conceptually similar to this one:
+</p>
+<p>
+ <img height="228" alt="Identify Elements - Initial Class Model" src="./resources/IdentifyElementsBCE.JPG"
+ width="290" />
+</p>
+<p>
+ For this example, the <a class="elementLink"
+ href="./../../../core.tech.slot.base/guidances/concepts/entity_control_boundary_pattern_C4047897.html"
+ guid="_uF-QYEAhEdq_UJTvM1DM2Q">Entity-Control-Boundary Pattern</a> has been used to derive two classes (LoginUI and
+ LoginController). In addition, two design elements already identified in the architecture (SecuritySystemInterface and
+ User) have also been incorporated.
+</p>
+<h3>
+ Determine how elements collaborate to realize the scenario
+</h3>
+<p>
+ When determining collaboration, two kinds of diagrams are useful.
+</p>
+<ul>
+ <li>
+ A dynamic object diagram, showing how the design elements collaborate to realize the requirements.
+ </li>
+ <li>
+ A static class diagram, showing the classes involved in realizing the requirements.
+ </li>
+</ul>
+<p>
+ Remember to also update any other impacted diagrams as appropriate, based on modifications or additions to the design.
+</p>
+<p>
+ Create a number of dynamic object diagrams that walk through how a set of objects collaborate to perform the behavior
+ of the scenarios.&nbsp; Even if just one scenario is being designed, this might take multiple diagrams to render it in
+ smaller, understandable chunks or from multiple contexts.
+</p>
+<p>
+ <img style="WIDTH: 776px; HEIGHT: 355px" height="355" alt="User Login Sequence Diagram"
+ src="./resources/UserLoginSeq.JPG" width="776" />
+</p>
+<p>
+ The above sequence diagram shows the user credentials being passed through to the security system for authentication.
+ Steps in the use case scenario are transformed into messages between the participating objects. The messages in this
+ example are not yet fully formed (there are no parameters or return values), so they are prefixed with “//” to show
+ that more work is needed.&nbsp; A sequence diagram was used in this example, but a communication diagram could have
+ been used.
+</p>
+<p>
+ It&nbsp;can be&nbsp;useful to create one or more static class diagrams that show the classes in the design that support
+ the realization.&nbsp; These class diagrams are often called View of Participating Classes diagrams, they provide a
+ focused view on the overall design by only showing the classes, relationships, operations, and attributes relevant to
+ the collaboration.
+</p>
+<p>
+ <img height="469" alt="Login VOPC" src="./resources/login_vopc.jpg" width="448" />
+</p>
+<p>
+ This diagram shows the operations and relationships that were identified by drawing the sequence diagram. The
+ relationships in this example&nbsp;have not been refined yet, so they are just shown as simple associations. Remember
+ to examine the diagram to verify that the design can support the behavior in the sequence diagram.
+</p>
+<p>
+ Working at this level of detail in the model during the early stages of design can be helpful. It keeps the diagrams
+ relatively simple and easy to understand. It makes them easier to draw in a workshop and easier to change during
+ discussion. It is often easier to add the detail once there is agreement on the fundamentals.
+</p>
+<h3>
+ Refine design decisions
+</h3>
+<p>
+ Once the fundamentals of the design are relatively stable, you can begin to add detail to the design. Some of this can
+ be performed in code or in the model. If modeling is chosen, then refine attributes, responsibilities and
+ relationships.
+</p>
+<h4>
+ Describe responsibilities
+</h4>
+<p>
+ Class responsibilities are either actions to be performed by an object or knowledge maintained and provided to other
+ objects. Each class will typically have several responsibilities; each responsibility will evolve into one or more
+ operations during design.
+</p>
+<p>
+ Responsibilities are derived from messages on interaction diagrams or from non-functional requirements that a class has
+ to support. Document a responsibility by giving it a name, and optionally a brief description (what it does).
+</p>
+<p>
+ These operations can be left as self-evident from their context, they can be given textual descriptions of the
+ algorithm required to perform the behavior, or they could spawn off another whole pass of this technique where a set of
+ classes that collaborate together to perform the internals of the operation are identified, etc.
+</p>
+<h4>
+ Describe attributes and associations
+</h4>
+<p>
+ A class may have to store simple data information, like: string, integer, and the like. For such simple type of
+ information, attributes are defined for classes. For a more complex or "behavioral” attribute, consider creating an
+ extra class and establish an association to it.
+</p>
+<p>
+ To perform their responsibilities, classes may depend on other classes to supply needed behavior. These other classes
+ might be ones already identified in this design session, they might be existing classes pulled from the architecture,
+ or the need for new classes might be conceived. Associations in a class diagram can be used to represent inter-class
+ relationships.
+</p>
+<p>
+ <img height="439" alt="Login VOPC (Refined)" src="./resources/login_vopc_refined.jpg" width="557" />
+</p>
+<p>
+ This diagram shows a number of refinements. The LoginUI class has been replaced by LoginForm. The User class has been
+ renamed UserCredentials and is created by the LoginForm class rather than LoginController. It is then used as a
+ parameter for subsequent messages rather than passing the individual attributes. The SecuritySystemInterface class has
+ been refined into two elements, ISystemSecurity, which provides a simple façade for interaction with the rests of the
+ design; and SecuritySystemProxy, which handles interaction with the external security system.
+</p>
+<h3>
+ Design internals
+</h3>
+<p>
+ The classes in the design are likely to need to be distributed amongst different packages and subsystems or components.
+</p>
+<p>
+ <img height="304" alt="User Login - Design Packages" src="./resources/dv_Packaging.JPG" width="571" />
+</p>
+<p>
+ In this example, the LoginForm, LoginController and UserCredentials elements have been placed in a package called
+ LocalSecurity. The SecuritySystemProxy is a part of a subsystem called SecuritySystemAdapter which realizes the
+ ISecuritySystem interface. The SecuritySystemAdapter wraps the legacy SecuritySystem, expressed here as a component
+ offering a validateUser interface.
+</p>
+<p>
+ Each of these packaged elements can be distributed amongst the team for further development work.
+</p>
+<h3>
+ Conclusion
+</h3>
+<p>
+ This guideline walked through the techniques in a concrete manner started with a scenario of a use case through to
+ distributing the classes identified into a set of packages. This example demonstrates a technique for designing
+ visually, but it should be considered as just one conceptual pass of design.&nbsp; One could as easily apply this
+ technique when defining the internals of how the SecuritySystemProxy class will collaborate with a set of classes to
+ validate the credentials.
+</p>
+<p>
+ When applying this guideline, work in small chunks and keep in mind the goal of delivering software to the users that
+ provides value. To deliver high-quality software requires consideration of how the pieces will work together to deliver
+ that value. But as soon as key decisions have been made and the decisions have been communicated to the appropriate
+ team members, the team should move on to implementing the source code to verify the design and deliver the value.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/evolve_the_design.xmi b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/evolve_the_design.xmi
new file mode 100644
index 0000000..20e1c01
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/evolve_the_design.xmi
@@ -0,0 +1,160 @@
+<?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="-8V5osHpRNG6Z7KPy8RGW1w"
+ name=",_C4U9QPTeEduDKIuqTXQ8SA" guid="-8V5osHpRNG6Z7KPy8RGW1w" changeDate="2007-05-31T11:32:35.160-0700">
+ <mainDescription><h1> Review the design </h1>
+<p> Design is best accomplished collaboratively, because it is a problem-solving 
+ activity with a range of&nbsp;parts and perspectives. There should be a constant 
+ level of review to ensure that the decisions make sense within the area being 
+ designed and in the design of the system overall. There also might be occasions 
+ where some area of design is reviewed by a set of interested or knowledgeable 
+ parties, such as the architect who will verify that the design conforms to an 
+ architectural decision or a developer who will be expected to implement the 
+ design. </p>
+<p> The design should be examined to ensure that it follows heuristics of quality 
+ design, such as loose coupling and high cohesion. Responsibilities should be 
+ appropriately distributed to elements in ways that there are no elements with 
+ too much responsibility and no elements that are left without any responsibilities. 
+ The design should be able to clearly communicate the design decisions, yet not 
+ delve into concerns best dealt with during implementation of code.</p>
+<p> Ensure that the design follows any project-specific guidelines and conforms 
+ to the architecture. Modifications to the design to improve it (based on issues 
+ identified in reviewing it) should apply <a class="elementLink" href="./../../../openup/guidances/guidelines/refactoring_33F165CA.html" guid="_OlyWoOX7Edu8VZPtlaU33g">Refactoring</a>&nbsp;to 
+ ensure that the design and any existing implementation of the design continues 
+ to fulfill its responsibilities. </p>
+Revisit the relationships between elements to improve the coupling in the design. 
+Remove redundant relationships, try to make relationships unidirectional, and 
+so forth. See <a class="elementLinkWithType" href="./../../../openup/guidances/guidelines/analyze_the_design_4C4750C0.html" guid="__MnggPTdEduDKIuqTXQ8SA">Guideline: 
+Analyze the Design</a> for more information. 
+<h1> Refine the design </h1>
+<p> After creating an implementation that includes a set of collaborating elements, 
+ with the behavior and relationships robust enough to pass developer tests, the 
+ design can be improved and transformed into a more robust and maintainable system. 
+</p>
+<p> The visibility of each operation should be selected to be as restrictive as 
+ possible. Based on walking through the scenario, it should be clear which operations 
+ must be available to other elements in the design and which can be considered 
+ behavior inside of the element that has the operation. Minimizing the number 
+ of public operations creates a more maintainable and understandable design. 
+</p>
+<p> With respect to parameters, the return value, and a description of how it 
+ perform the behavior, operations can be detailed at a lower level that drives 
+ the actual implementation, or that detail might be left to be handled when writing 
+ the code. </p>
+<p> Data attributes can be identified based on information needed to support behavior 
+ or based on additional requirements, such as information to be presented to 
+ the user or transmitted to another system. Avoid indiscriminate domain analysis, 
+ because there might be a great deal of data in the domain that is not needed 
+ to support the requirements. Data attributes can simply be identified or they 
+ can be designed in detail, with attribute types, initial values, and constraints. 
+ Decide on the visibility of the data attribute; operations to access and update 
+ the data can be added or deferred until implementation. </p>
+<p> Generalization and interfaces can be applied to simplify or otherwise improve 
+ the design. Ensure that the use of these techniques actually improves the design, 
+ rather than bogging it down with complexity. For example, common behavior can 
+ be factored into a parent class through generalization or out to a helper class 
+ through delegation. The latter solution can be more understandable and maintainable, 
+ because generalization is an inflexible relationship (see the section that follows 
+ on inheritance). </p>
+<p> The refinement of any portion of the design could include another pass through 
+ the design process. You might find that what was initially identified as a single 
+ behavior of an element warrants a detailed walkthrough of the collaborating 
+ elements to realize that behavior. </p>
+<p> When updating an existing design -- especially one that has had portions already 
+ implemented -- apply <a class="elementLink" href="./../../../openup/guidances/guidelines/refactoring_33F165CA.html" guid="_OlyWoOX7Edu8VZPtlaU33g">Refactoring</a> 
+ to ensure that the improved design continues to perform as expected. </p>
+<h2> Organize elements </h2>
+<p> In a design of any notable size, the elements must be organized into packages. 
+ Assign the elements to existing or new packages, and ensure that the visibility 
+ relationships between the packages support the navigation required between the 
+ elements. Decide whether each element should be visible to elements outside 
+ of the package. </p>
+<p> When structuring the design into packages, consider <a class="elementLink" href="./../../../openup/guidances/guidelines/layering_F169CF07.html" guid="_0gpkAMlgEdmt3adZL5Dmdw">Layering</a> 
+ and other patterns. Although all design work must conform to existing architectural 
+ decisions, the allocation of elements to packages and possible updates to package 
+ visibility are of significant architectural concern. The developer should collaborate 
+ with the architect to ensure that package-level decisions are in accordance 
+ with the rest of the architecture. </p>
+<p> This guideline first talks about the identification and design of the elements 
+ and then about organizing the elements into packages. However, this is not a 
+ strict order of events. There is nothing wrong with identifying a package structure 
+ for the system and then populating that structure with identified elements, 
+ as long as the actual elements identified are allowed to influence the resulting 
+ package structure. See the sections on identification and behavior of elements 
+ in <a class="elementLinkWithType" href="./../../../openup/guidances/guidelines/analyze_the_design_4C4750C0.html" guid="__MnggPTdEduDKIuqTXQ8SA">Guideline: 
+ Analyze the Design</a>. </p>
+<h2> Identify patterns </h2>
+<p> Identifying <a class="elementLink" href="./../../../openup/guidances/concepts/pattern_10BE6D96.html" guid="_0YJvUMlgEdmt3adZL5Dmdw">Pattern</a>s 
+ and seeking opportunities to leverage patterns are useful techniques. The value 
+ of patterns here is that they provide a shortcut to a robust design. For instance, 
+ when there's an interface realized by multiple classes, it’s possible that an 
+ Abstract Factory pattern will be useful, because the pattern encapsulates the 
+ logic of what class should be instantiated. The more experienced a developer 
+ is, the better the developer is at identifying opportunities to take advantage 
+ of, or leverage, patterns. </p>
+<p> The longer you use patterns, the easier it will be to identify opportunities 
+ to leverage them. At first, look for places where you can clearly specify the 
+ need for some behavior. Perhaps there's a place where some function or algorithm 
+ must be shared between many different classes. How can this behavior be shared 
+ over and over among heterogeneous classes? Or perhaps a third-party library 
+ is replacing a block of custom code. Is there a way to make this transition 
+ easier by creating an interface that can use either implementation? These are 
+ opportunities for finding or possibly creating a pattern. </p>
+<p>
+ See also <a class="elementLinkWithUserText" href="./../../../openup/guidances/supportingmaterials/references_6CCF393.html#GAM95" guid="_9ToeIB83Edqsvps02rpOOg">[GAM95]</a>&nbsp;and <a class="elementLinkWithUserText" href="./../../../openup/guidances/supportingmaterials/references_6CCF393.html#SHA05" guid="_9ToeIB83Edqsvps02rpOOg">[SHA05]</a>
+</p>
+<h1> Inheriting behavior versus inheriting interfaces </h1>
+<p> Inheritance (or generalization) is often used as a shortcut during implementation 
+ to quickly re-use behavior (code).</p>
+<p><b>Caution: </b><br />
+ Work hard to remove behavior inheritance in design. It will almost always cost 
+ more effort than it saves. </p>
+<p> Inheritance is a very rigid structure with strict rules. A class that inherits 
+ from another class is establishing an<b> is-a</b> relationship. The inheriting 
+ class is a type of the parent class-- the child has the same relationships and 
+ behaviors as the parent. In most hierarchies, it will be impossible to maintain 
+ this type of relationship. Exceptions quickly creep in, and it’s common to find 
+ child classes that remove or override behavior in the parent classes. This increases 
+ maintenance costs and makes it difficult to understand what each class does. 
+</p>
+<p>
+ It’s also too tempting to instantiate parent classes, which makes the parent class both abstract and concrete. If a
+ class has children, it must be abstract enough to support the generalized behavior of the children. But if it’s
+ instantiated, it must be concrete enough to provide specific behavior. It’s rarely possible to fulfill both of these
+ competing imperatives at the same time, and the design suffers.
+</p>
+<p>
+ Use association and aggregation relationships instead of inheriting behavior. Patterns are a good tool to leverage in
+ breaking up inheritance hierarchies.
+</p>
+<p> Inheriting interfaces is safe, because only the description and not the implementation 
+ of what needs to be done is reused. </p>
+<p>
+ Avoiding inheriting behavior is an application of the Open-Closed Principle. See <a class="elementLinkWithType" href="./../../../openup/guidances/concepts/design_E36137FA.html" guid="_bFjlAPTYEduDKIuqTXQ8SA">Concept: Design</a> for
+ more information.
+</p>
+<h1> <strong>Revisit the analysis</strong> </h1>
+<p> The <a class="elementLinkWithType" href="./../../../openup/guidances/guidelines/analyze_the_design_4C4750C0.html" guid="__MnggPTdEduDKIuqTXQ8SA">Guideline: 
+ Analyze the Design</a>&nbsp;describes techniques that are also useful when evolving 
+ a more robust design.<br />
+</p>
+<h2> <strong>Consider the architecture</strong> </h2>
+<p> The architecture must be considered in all design changes. The “best” design 
+ for a particular part of the solution may not be appropriate because of architectural 
+ constraints that must support the entire system. The architecture may also help 
+ to make design decisions, because it can be part of the selection criteria between 
+ two potential solutions. Developers should always be up-to-date with the architecture 
+ and review it often, particularly in early iterations. </p>
+<p> This guideline remarks on conforming to the architecture in various ways; 
+ it is written as though it is about designing within a pre-existing architecture. 
+ Although projects will often have pre-existing architectures available, a particular 
+ architecture is the result of design activities. Therefore, in addition to discussing 
+ conformance to some existing architecture, you must also consider the creation 
+ of the architecture, as well as updates and improvements based on the work of 
+ design. </p>
+<p> Also, see&nbsp;<a class="elementLinkWithUserText" href="./../../../openup/guidances/supportingmaterials/references_6CCF393.html#SHA05" guid="_9ToeIB83Edqsvps02rpOOg">[SHA05]</a> 
+ for a&nbsp;useful introduction to object-oriented techniques that should be 
+ applied when evolving a good design. </p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/refactoring.xmi b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/refactoring.xmi
new file mode 100644
index 0000000..0109ae8
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/refactoring.xmi
@@ -0,0 +1,88 @@
+<?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="-g0jWGmg-E0rCQEmnibTDIA"
+ name="new_guideline,_OlyWoOX7Edu8VZPtlaU33g" guid="-g0jWGmg-E0rCQEmnibTDIA" changeDate="2007-07-25T15:51:48.198-0400"
+ version="1.0.0">
+ <mainDescription><p>
+ Refactoring involves improving the design of existing code without changing the system's behavior. It is explicitly not
+ about adding or changing behavior, but about improving the design of existing behavior.
+</p>
+<p>
+ A full set of developer tests is required before refactoring can be safely applied. It is critical that the system
+ behavior be in a known, verifiably correct state before modifying the design so that you can improve the design without
+ fear that the modified implementation will break something. Refactoring is a safe transformation to improve code, but
+ it is safe only if there are tests that can verify that the system still works as intended.
+</p>
+<p>
+ Refactoring is initiated when an area that needs improvement is identified in the system by examining either the code
+ or&nbsp;some other&nbsp;representation of the design. The issues identified are sometimes called "smells."
+</p>
+<p>
+ Here are several smells to look for that might lead to refactoring:
+</p>
+<ul>
+ <li>
+ <b>Duplicated code:</b> Duplicated code makes the system harder to understand and harder to maintain.
+ </li>
+ <li>
+ <b>Large design element or method:</b> Large design elements or methods diminish the ability of people to
+ understand the design, reduce the potential for reuse, and make developer testing more difficult.
+ </li>
+ <li>
+ <b>Poorly named element:</b> Whether the element be a variable, function, class, or component, its name should
+ connote what it is so that the code can be maintained.
+ </li>
+ <li>
+ <b>Tight coupling:</b> Each design element should work with minimal concern for the internal aspects of other
+ design elements. Otherwise, changes to one element can have undesirable effects in other elements.
+ </li>
+</ul>
+<p>
+ As you can see from this list, refactoring can improve the "internals" of a design element, the interface of the
+ element, or the relationships and collaboration between elements. Also, many of the smells&nbsp;are characterized as
+ making the software more difficult to understand; whereas refactoring is about making the system simpler.
+</p>
+<p>
+ After an issue is identified, a refactoring method can be selected that will improve the situation. There are catalogs
+ of refactoring methods available that are change patterns that will fix common problems while retaining the behavior of
+ the system.
+</p>
+<p>
+ These are examples of refactoring methods:
+</p>
+<ul>
+ <li>
+ <b>Extract Method:</b> Pull out the duplicated code into its own single method or extract part of a large method
+ into its own method.
+ </li>
+ <li>
+ <b>Extract Class:</b> Pull some cohesive part of a class into its own class to reduce the size of a design element
+ that is too big.
+ </li>
+ <li>
+ <b>Rename Method</b>, <b>Rename Class</b>, or <b>Rename Variable:</b> Give a more meaningful name to an element to
+ make it more understandable.
+ </li>
+ <li>
+ <b>Extract Interface:</b> Create a clean interface to an element to reduce coupling.
+ </li>
+</ul>
+<p>
+ When refactoring has been applied, developer tests are run again to ensure that the system still behaves correctly. It
+ is important that the system is working correctly after each small refactoring. Although many refactorings can be put
+ together to drive broad change across the code base, the tests should run correctly between each refactoring applied.
+ Refactoring must be applied as small behavior-preserving transformations.
+</p>
+<p>
+ As mentioned previously, refactoring requires full developer test coverage of the area under consideration. There are
+ additional techniques that enable refactoring. Coding standards define a common style and make it easier to refactor
+ consistently. An attitude of&nbsp;collective code ownership within the team is important. Each developer should feel
+ that refactoring can be applied across the code base to improve the implementation.
+</p>
+<p>
+ For deeper coverage on this topic, including a listing of "smells" and a catalog of refactorings to respond to them,
+ see [<a class="elementLinkWithUserText" href="./../../../openup/guidances/supportingmaterials/references.html#FOW99"
+ guid="_9ToeIB83Edqsvps02rpOOg">FOW99</a>].
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/IdentifyElementsBCE.JPG b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/IdentifyElementsBCE.JPG
new file mode 100644
index 0000000..903bdea
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/IdentifyElementsBCE.JPG
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/PDMSample.JPG b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/PDMSample.JPG
new file mode 100644
index 0000000..5ad1683
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/PDMSample.JPG
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/UserLoginSeq.JPG b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/UserLoginSeq.JPG
new file mode 100644
index 0000000..0270965
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/UserLoginSeq.JPG
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/UserLoginUCM.JPG b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/UserLoginUCM.JPG
new file mode 100644
index 0000000..6e965d1
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/UserLoginUCM.JPG
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/co_dmec1.gif b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/co_dmec1.gif
new file mode 100644
index 0000000..b076e0b
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/co_dmec1.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/co_dmec2.gif b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/co_dmec2.gif
new file mode 100644
index 0000000..b8b7cd9
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/co_dmec2.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/co_dmec3.gif b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/co_dmec3.gif
new file mode 100644
index 0000000..bfd2a4b
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/co_dmec3.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/dv_Packaging.JPG b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/dv_Packaging.JPG
new file mode 100644
index 0000000..ae585d8
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/dv_Packaging.JPG
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/ebc_diagram.JPG b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/ebc_diagram.JPG
new file mode 100644
index 0000000..67970fe
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/ebc_diagram.JPG
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/jdbc1.gif b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/jdbc1.gif
new file mode 100644
index 0000000..1c2beb3
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/jdbc1.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/jdbc2.gif b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/jdbc2.gif
new file mode 100644
index 0000000..717c2b2
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/jdbc2.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/jdbc3.gif b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/jdbc3.gif
new file mode 100644
index 0000000..06f3a9d
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/jdbc3.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/jdbc4.gif b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/jdbc4.gif
new file mode 100644
index 0000000..cb79539
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/jdbc4.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/jdbc5.gif b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/jdbc5.gif
new file mode 100644
index 0000000..8559e50
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/jdbc5.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/jdbc6.gif b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/jdbc6.gif
new file mode 100644
index 0000000..13a7b72
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/jdbc6.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/login_vopc.jpg b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/login_vopc.jpg
new file mode 100644
index 0000000..0d46428
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/login_vopc.jpg
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/login_vopc_refined.jpg b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/login_vopc_refined.jpg
new file mode 100644
index 0000000..dafa9b7
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/login_vopc_refined.jpg
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/md_ucre3.gif b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/md_ucre3.gif
new file mode 100644
index 0000000..7f4cf27
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/md_ucre3.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/ucrea1.gif b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/ucrea1.gif
new file mode 100644
index 0000000..78190a2
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/resources/ucrea1.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/uc_realizations.xmi b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/uc_realizations.xmi
new file mode 100644
index 0000000..5f238a3
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/guidances/guidelines/uc_realizations.xmi
@@ -0,0 +1,94 @@
+<?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: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="-CFYVionNDLkMw6SG6runQA"
+ name="uc_realizations,_2uan8NbyEdqu5o2S60g5LA" guid="-CFYVionNDLkMw6SG6runQA"
+ changeDate="2006-09-26T15:24:33.595-0700">
+ <mainDescription><p>
+ A use-case realization represents how a use case will be implemented in terms of collaborating objects. This artifact
+ can take various forms. It may include, for example, a textual description (a document), class diagrams of
+ participating classes and subsystems, and interaction diagrams (communication and sequence diagrams) that illustrate
+ the flow of interactions between class and subsystem instances.
+</p>
+<p>
+ The reason for separating the use-case realization from its use case is that doing so allows the use cases to be
+ managed separately from their realizations. This is particularly important for larger projects, or families of systems
+ where the same use cases may be designed differently in different products within the product family. Consider the case
+ of a family of telephone switches which have many use cases in common, but which design and implement them differently
+ according to product positioning, performance and price.
+</p>
+<p>
+ For larger projects, separating the use case and its realization allows changes to the design of the use case without
+ affecting the baselined use case itself.
+</p>
+<p>
+ In a model, a use-case realization is represented as a UML collaboration that groups the diagrams and other information
+ (such as textual descriptions) that form part of the use-case realization.
+</p>
+<p>
+ UML diagrams that&nbsp;support use-case realizations can be produced in an analysis context, a&nbsp;design context, or
+ both, depending on the needs of the project. For each use case in the use-case model, there&nbsp;can be&nbsp;a use-case
+ realization in the analysis/design model with a realization relationship to the use case. In UML this is shown as a
+ dashed arrow, with an arrowhead like a generalization relationship, indicating that a realization is a kind of
+ inheritance, as well as a dependency.<br />
+</p>
+<p align="center">
+ <img height="109" alt="Use Case Realisations" src="./resources/ucrea1.gif" width="277" />
+</p>
+<p>
+ A use-case realization in the&nbsp;design can be traced to a use case in the use-case model.
+</p>
+<h4>
+ Class Diagrams Owned by a Use-Case Realization
+</h4>
+<p>
+ For each use-case realization there may be one or more class diagrams depicting its participating classes. A class and
+ its objects often participate in several use-case realizations. It is important&nbsp;while designing to coordinate all
+ the requirements on a class and its objects that different use-case realizations may have. The figure below shows an
+ analysis&nbsp;class diagram for the realization of the Receive Deposit Item use case. Note the use of
+ boundary-control-entity stereotypes to represent analysis classes (see <a class="elementLinkWithType"
+ href="./../../../core.tech.slot.base/guidances/concepts/entity_control_boundary_pattern_C4047897.html"
+ guid="_uF-QYEAhEdq_UJTvM1DM2Q">Concept: Entity-Control-Boundary Pattern</a>).
+</p>
+<p align="center">
+ <img height="213" alt="Class diagram for the realization of Receive Deposit Item" src="./resources/md_ucre3.gif"
+ width="328" />
+</p>
+<p align="center">
+ <strong>The use case Receive Deposit Item and its analysis-level class diagram</strong>.
+</p>
+<h4>
+ Communication and Sequence Diagrams Owned by a Use-Case Realization
+</h4>
+<p>
+ For each use-case realization there&nbsp;can be&nbsp;one or more interaction diagrams depicting its participating
+ objects and their interactions. There are two types of interaction diagrams: sequence diagrams and communication
+ diagrams. They express similar information, but show it in different ways. Sequence diagrams show the explicit sequence
+ of messages and are better when it is important to visualize the time ordering of messages, whereas communication
+ diagrams show the communication links between objects and are better for understanding all of the effects on a given
+ object and for algorithm design.
+</p>
+<p>
+ Realizing use cases through interaction diagrams helps to keep the design simple and cohesive. Assigning
+ responsibilities to classes on the basis of what the use-case scenario explicitly requires encourages the design to
+ contain the following:
+</p>
+<ul>
+ <li>
+ Only the functionality actually used in support of a use case scenario
+ </li>
+ <li>
+ Functionality that can be tested through an associated test case
+ </li>
+ <li>
+ Functionality that is more easily traceable to requirements and changes
+ </li>
+ <li>
+ Explicitly declared class dependencies that are easier to manage
+ </li>
+</ul>
+<p>
+ These factors help improve the overall quality of the system.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/guidances/roadmaps/how_to_adopt.xmi b/praclib/temp/practice.tech.evolutionary_design.base/guidances/roadmaps/how_to_adopt.xmi
new file mode 100644
index 0000000..f4367fd
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/guidances/roadmaps/how_to_adopt.xmi
@@ -0,0 +1,46 @@
+<?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: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="-QmIvs-rs3Fiyg7PVRx2IvQ"
+ name="new_roadmap,_irQiEOCsEdynptYdmll41Q" guid="-QmIvs-rs3Fiyg7PVRx2IvQ" changeDate="2008-02-29T10:26:19.750-0800"
+ version="7.2.0">
+ <mainDescription><p>
+ <strong>Getting Started</strong>
+</p>
+<p>
+ Begin by gaining an understanding of design patterns. There are good references in the <a class="elementLink"
+ href="./../../../practice.tech.evolutionary_design.base/guidances/supportingmaterials/enablement_33E69D6F.html"
+ guid="_FxgacOCqEdynptYdmll41Q">Enablement</a>&nbsp;materials. Patterns are essential to creating, managing, and
+ evolving designs. As the name implies, evolutionary design involves returning to the existing design over and over
+ again to refine, change, and improve previous thinking. It can be performed at the beginning of a development cycle
+ (before implementation), during a development cycle (while implementing code), after the cycle (when the developer
+ tests have&nbsp;successfully executed), or any combination of these. The team should determine where in the development
+ cycle the design will be performed.
+</p>
+<p>
+ Understand refactoring and the difference between code refactoring and design refactoring. There's no exact boundary
+ separating the two but there are some clear areas where the developer will wear the "design hat" when reworking the
+ design into a better structure. These areas will usually involve identifying where design patterns can replace or
+ enhance the existing design, or areas of the design where patterns can be identified and harvested for reuse.
+</p>
+<p>
+ <strong>Common Pitfalls</strong>
+</p>
+<p>
+ Evolutionary design emerges from refactoring existing design. This improves the design without changing the behavior of
+ the system. Failing to perform developer or unit testing is a high risk activity as you can't guarantee that:
+</p>
+<ul>
+ <li>
+ The original design works correctly
+ </li>
+ <li>
+ The refactored design works correctly
+ </li>
+</ul>
+<p>
+ So developer testing must be rigorously performed in order to verify the robustness of the design. Otherwise you may
+ waste a lot of time refactoring something that doesn't work, or refactoring the correct behavior out of the system.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/guidances/supportingmaterials/enablement.xmi b/praclib/temp/practice.tech.evolutionary_design.base/guidances/supportingmaterials/enablement.xmi
new file mode 100644
index 0000000..99053f8
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/guidances/supportingmaterials/enablement.xmi
@@ -0,0 +1,34 @@
+<?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="-WVSbWqzqT0OSgdmRnsjS9w"
+ name="new_supporting_material,_FxgacOCqEdynptYdmll41Q" guid="-WVSbWqzqT0OSgdmRnsjS9w"
+ changeDate="2008-02-21T10:24:27.729-0800" version="7.2.0">
+ <mainDescription><p>
+ Meyer, B., <em>Object-Oriented Software Construction</em>, Prentice Hall, 1997
+</p>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p>
+ A good primer on OO basics.
+ </p>
+</blockquote>
+<p>
+ Gamma, E., Helm, R., Johnson, R., Vlissides, J., <em>Design Patterns: Elements of Reusable Object-Oriented
+ Software</em>, Addison-Wesley Professional; 1995
+</p>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p>
+ The "bible" on learning what patterns are and how to describe them.
+ </p>
+</blockquote>
+<p>
+ Shalloway, J., Trott, J. <em>Design Patterns Explained</em> A New Perspective on Object-Oriented Design, Second
+ Edition, Addison Wesley, 2005
+</p>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p>
+ An excellent description of evolving design via patterns.
+ </p>
+</blockquote></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/guidances/supportingmaterials/release_info_evolutionary_design.xmi b/praclib/temp/practice.tech.evolutionary_design.base/guidances/supportingmaterials/release_info_evolutionary_design.xmi
new file mode 100644
index 0000000..a9e5d4d
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/guidances/supportingmaterials/release_info_evolutionary_design.xmi
@@ -0,0 +1,22 @@
+<?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="-xn-M2VApZPqzI5KflPNIVw"
+ name="new_supporting_material,_skRykMuYEdyRPtFYRAKVDg" guid="-xn-M2VApZPqzI5KflPNIVw"
+ changeDate="2008-01-25T14:56:42.458-0800">
+ <mainDescription><h3>
+ Evolutionary Design&nbsp;Practice
+</h3>
+<p>
+ Version 1.0
+</p>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p>
+ [*** NOT YET RELEASED ***]
+ </p>
+ <p>
+ This is the initial release of this practice.
+ </p>
+</blockquote></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/guidances/templates/design.xmi b/praclib/temp/practice.tech.evolutionary_design.base/guidances/templates/design.xmi
new file mode 100644
index 0000000..827c842
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/guidances/templates/design.xmi
@@ -0,0 +1,69 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:GuidanceDescription 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="-giTBOvJczHXweRzBQEo-7A"
+ name="new_template,_EOPcMAMUEdylNddAObilIA" guid="-giTBOvJczHXweRzBQEo-7A" changeDate="2007-06-22T10:44:44.614-0700">
+ <mainDescription><p> This template describes how the design can be organized to be understood from 
+ multiple perspectives. It also provides suggestions for how patterns and descriptions 
+ of small, reusable interactions can be used to minimize redundancy. </p>
+<p> It is important not to think of design as &quot;a document." Design information 
+ that is worth keeping for some duration must have a long-lived form. But that 
+ form might be as a repository in a visual modeling tool, or as subdirectories 
+ of whiteboard diagrams captured with a digital camera, or as an actual document 
+ that provides structure for images taken from a myriad of sources. </p>
+<p> This template describes the information that should be conveyed. Typically, 
+ it works best to convey the information graphically (either with UML or another 
+ unambiguous notation), or at least in words, at an abstract level. You can enhance 
+ this with code examples, but best not to render the design solely at the code 
+ level. </p>
+<p>
+ The structure of the design is suggested in this template.
+</p>
+<h1> Design structure </h1>
+<p style="COLOR: #0000ff"> [Describe the design from the highest level. This 
+ is commonly done with a diagram that shows a layered architecture.] </p>
+<h1> Subsystems </h1>
+<h2> [Sub-system1] </h2>
+<p style="COLOR: #0000ff"> [Describe the design of a portion of the system (a 
+ package or component, for instance). The design should capture both static and 
+ dynamic perspectives. </p>
+<p style="COLOR: #0000ff"> When capturing dynamic descriptions of behavior, look 
+ for reusable chunks of behavior that you can reference to simplify the design 
+ of the use-case realizations. </p>
+<p style="COLOR: #0000ff"> You can break this section down into lower-level subsections 
+ to describe lower-level, encapsulated subsystems.] </p>
+<h1> Patterns </h1>
+<h2> [Pattern1] </h2>
+<h3> Overview </h3>
+<p style="COLOR: #0000ff"> [Provide an overview of the pattern in words in some 
+ consistent form. The overview of a pattern can include the intent, motivation, 
+ and applicability.] </p>
+<h3> Structure </h3>
+<p style="COLOR: #0000ff"> [Describe the pattern from a static perspective. Include 
+ all of the participants and how they relate to one another, and call out the&nbsp;relevant 
+ data and behavior.] </p>
+<h3> Behavior </h3>
+<p style="COLOR: #0000ff"> [Describe the pattern from a dynamic perspective. Walk 
+ the reader through how the participants collaborate to support various scenarios.] 
+</p>
+Example 
+<p style="COLOR: #0000ff"> [Often, you can convey the nature of the pattern better 
+ with an additional concrete example.] </p>
+<h1> Use-case realizations </h1>
+<h2> [Realization1] </h2>
+<h3> View of participants </h3>
+<p style="COLOR: #0000ff"> [Describe the participating design elements from a 
+ static perspective, giving details such as behavior, relationships, and attributes 
+ relevant to this use-case realization.] </p>
+<h3> Basic scenario </h3>
+<p style="COLOR: #0000ff"> [For the main flow, describe how instances of the design 
+ elements collaborate to realize the use case. When using UML, this can be done 
+ with collaboration diagrams (sequence or communication).] </p>
+<h3> Additional scenarios </h3>
+<p style="COLOR: #0000ff"> [For other scenarios that must be described to convey 
+ an appropriate amount of information about how the use-case behavior will be 
+ realized, describe how instances of the design elements collaborate to realize 
+ the use case. When using UML, you can do this with collaboration diagrams (sequence 
+ or communication).] </p></mainDescription>
+</org.eclipse.epf.uma:GuidanceDescription>
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/plugin.xmi b/praclib/temp/practice.tech.evolutionary_design.base/plugin.xmi
new file mode 100644
index 0000000..26f3249
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/plugin.xmi
@@ -0,0 +1,269 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_Z20lULPPEduocbW-TPTq7A"
+ guid="_Z20lULPPEduocbW-TPTq7A">
+ <resourceDescriptors xmi:id="_nGJZ0vL5Edm6Nvont3uinw" id="_NrC20qeqEdmKDbQuyzCoqQ"
+ uri="tasks/design_solution.xmi"/>
+ <resourceDescriptors xmi:id="_bL9KAL3vEdqLRJZPGVbHDA" id="-_BAmniONtHWbpHQH7znR3g"
+ uri="tasks/design_solution.vm.xmi"/>
+ <resourceDescriptors xmi:id="_TVGdwDBGEduMqpUNhaTSRA" id="-1xE2ZW3MjNAJ7jkaZNbkww"
+ uri="guidances/guidelines/designing_visually.xmi"/>
+ <resourceDescriptors xmi:id="_eSrjED6TEduAL-bCqar_dg" id="-HQSI39vBrjpmQL1qHYOJtA"
+ uri="guidances/checklists/design_vm.xmi"/>
+ <resourceDescriptors xmi:id="_m-3tI_L5Edm6Nvont3uinw" id="_zxB-QKYcEdmvhNXG0Oc2uA"
+ uri="workproducts/design.xmi"/>
+ <resourceDescriptors xmi:id="_tCV2gPTfEduDKIuqTXQ8SA" id="-c5Uh71vXTPN-VmrGYVRV7w"
+ uri="guidances/concepts/design.xmi"/>
+ <resourceDescriptors xmi:id="_brXFwOX7Edu8VZPtlaU33g" id="-g0jWGmg-E0rCQEmnibTDIA"
+ uri="guidances/guidelines/refactoring.xmi"/>
+ <resourceDescriptors xmi:id="_tCiDwPTfEduDKIuqTXQ8SA" id="-1vS_ELnQxGQKwfCrRYrc7w"
+ uri="guidances/guidelines/analyze_the_design.xmi"/>
+ <resourceDescriptors xmi:id="_tCoKYPTfEduDKIuqTXQ8SA" id="-8V5osHpRNG6Z7KPy8RGW1w"
+ uri="guidances/guidelines/evolve_the_design.xmi"/>
+ <resourceDescriptors xmi:id="_Q6XUEAMVEdylNddAObilIA" id="-giTBOvJczHXweRzBQEo-7A"
+ uri="guidances/templates/design.xmi"/>
+ <resourceDescriptors xmi:id="_m-9zw_L5Edm6Nvont3uinw" id="_YIYIYMM1EdmSIPI87WLu3g"
+ uri="guidances/checklists/design.xmi"/>
+ <resourceDescriptors xmi:id="_y8FpMMuYEdyRPtFYRAKVDg" id="-xn-M2VApZPqzI5KflPNIVw"
+ uri="guidances/supportingmaterials/release_info_evolutionary_design.xmi"/>
+ <resourceDescriptors xmi:id="_wGHPkOCqEdynptYdmll41Q" id="-WVSbWqzqT0OSgdmRnsjS9w"
+ uri="guidances/supportingmaterials/enablement.xmi"/>
+ <resourceDescriptors xmi:id="_037t4OCsEdynptYdmll41Q" id="-QmIvs-rs3Fiyg7PVRx2IvQ"
+ uri="guidances/roadmaps/how_to_adopt.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_Z2cK0LPPEduocbW-TPTq7A" name="practice.tech.evolutionary_design.base"
+ guid="_Z2cK0LPPEduocbW-TPTq7A" briefDescription="This plug-in contains the method elements needed top perform basic software design."
+ changeDate="2008-01-25T14:59:23.189-0800">
+ <copyrightStatement href="uma://_iVydgENdEdy245g62lfWcA#_cTs20KzREduOqvpk_MDLfQ"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Z2cK0bPPEduocbW-TPTq7A"
+ name="Content" guid="_Z2cK0bPPEduocbW-TPTq7A">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Z2cK0rPPEduocbW-TPTq7A"
+ name="Categories" guid="_Z2cK0rPPEduocbW-TPTq7A">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Z2cK07PPEduocbW-TPTq7A"
+ name="Domains" guid="_Z2cK07PPEduocbW-TPTq7A"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Z2cK1LPPEduocbW-TPTq7A"
+ name="Disciplines" guid="_Z2cK1LPPEduocbW-TPTq7A"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Z2cK1bPPEduocbW-TPTq7A"
+ name="RoleSets" guid="_Z2cK1bPPEduocbW-TPTq7A"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Z2cK1rPPEduocbW-TPTq7A"
+ name="WP Types" guid="_Z2cK1rPPEduocbW-TPTq7A"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Z2cK17PPEduocbW-TPTq7A"
+ name="Tools" guid="_Z2cK17PPEduocbW-TPTq7A"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Z2cK2LPPEduocbW-TPTq7A"
+ name="StandardCategories" guid="_Z2cK2LPPEduocbW-TPTq7A"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Z2cK2bPPEduocbW-TPTq7A"
+ name="CustomCategories" guid="_Z2cK2bPPEduocbW-TPTq7A">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Z2cK2rPPEduocbW-TPTq7A"
+ name="Hidden" guid="_Z2cK2rPPEduocbW-TPTq7A">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_Z2cK27PPEduocbW-TPTq7A"
+ name="Custom Categories" guid="_Z2cK27PPEduocbW-TPTq7A" categorizedElements="_h6kZgMLzEdyBCJ57WNAp3w _cl5qUMuYEdyRPtFYRAKVDg"/>
+ </childPackages>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_h6kZgMLzEdyBCJ57WNAp3w"
+ name="evolutionary_design_practice" guid="_h6kZgMLzEdyBCJ57WNAp3w" presentationName="Evolutionary Design"
+ shapeicon="customcategories/resources/pract_dgm32.gif" nodeicon="customcategories/resources/pract_obj.gif"
+ categorizedElements="_irQiEOCsEdynptYdmll41Q _FxgacOCqEdynptYdmll41Q _0fshwMlgEdmt3adZL5Dmdw _0WuL8slgEdmt3adZL5Dmdw _JtvKAOCrEdynptYdmll41Q">
+ <methodElementProperty xmi:id="_5dFBkMLzEdyBCJ57WNAp3w" name="CategoryElementsSortType"
+ value="Manual"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_cl5qUMuYEdyRPtFYRAKVDg"
+ name="contributions_to_nav_building_blocks" guid="_cl5qUMuYEdyRPtFYRAKVDg"
+ presentationName="Contributions to Navigation Building Blocks" categorizedElements="_EZxoEMuZEdyRPtFYRAKVDg _sFpD4MuaEdyRPtFYRAKVDg _vSyVUMuaEdyRPtFYRAKVDg _yJe1oMuaEdyRPtFYRAKVDg _8WElcMuaEdyRPtFYRAKVDg _O0zKkMubEdyRPtFYRAKVDg _AT00cMubEdyRPtFYRAKVDg _K2S64NQxEdyM_J8-fv54DA"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_EZxoEMuZEdyRPtFYRAKVDg"
+ name="release_info.assign" guid="_EZxoEMuZEdyRPtFYRAKVDg" variabilityType="contributes"
+ categorizedElements="_skRykMuYEdyRPtFYRAKVDg">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCIHYcRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_sFpD4MuaEdyRPtFYRAKVDg"
+ name="concept_list.assign" guid="_sFpD4MuaEdyRPtFYRAKVDg" variabilityType="contributes"
+ categorizedElements="_bFjlAPTYEduDKIuqTXQ8SA">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4Y8RdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_vSyVUMuaEdyRPtFYRAKVDg"
+ name="checklist_list.assign" guid="_vSyVUMuaEdyRPtFYRAKVDg" variabilityType="contributes"
+ categorizedElements="_0XSzsMlgEdmt3adZL5Dmdw">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_pGt9MMReEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_yJe1oMuaEdyRPtFYRAKVDg"
+ name="guideline_list.assign" guid="_yJe1oMuaEdyRPtFYRAKVDg" variabilityType="contributes"
+ categorizedElements="__MnggPTdEduDKIuqTXQ8SA _C4U9QPTeEduDKIuqTXQ8SA _OlyWoOX7Edu8VZPtlaU33g _1fM3AC9_EduW5uTjiIcspQ">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4ZcRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_8WElcMuaEdyRPtFYRAKVDg"
+ name="artifact_list.assign" guid="_8WElcMuaEdyRPtFYRAKVDg" variabilityType="contributes"
+ categorizedElements="_0WuL8slgEdmt3adZL5Dmdw">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4YMRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_AT00cMubEdyRPtFYRAKVDg"
+ name="practice_list.assign" guid="_AT00cMubEdyRPtFYRAKVDg" variabilityType="contributes"
+ categorizedElements="_h6kZgMLzEdyBCJ57WNAp3w">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCIHY8RdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_O0zKkMubEdyRPtFYRAKVDg"
+ name="template_list.assign" guid="_O0zKkMubEdyRPtFYRAKVDg" variabilityType="contributes"
+ categorizedElements="_EOPcMAMUEdylNddAObilIA">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4Z8RdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_K2S64NQxEdyM_J8-fv54DA"
+ name="technical_practice_list" guid="_K2S64NQxEdyM_J8-fv54DA" presentationName="Technical Practices"
+ variabilityType="contributes" categorizedElements="_h6kZgMLzEdyBCJ57WNAp3w">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_lBrxENQuEdyM_J8-fv54DA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_JtvKAOCrEdynptYdmll41Q"
+ name="guidance" guid="_JtvKAOCrEdynptYdmll41Q" presentationName="Guidance"
+ shapeicon="customcategories/resources/bookcL.gif" nodeicon="customcategories/resources/bookc.gif"
+ categorizedElements="__MnggPTdEduDKIuqTXQ8SA _bFjlAPTYEduDKIuqTXQ8SA _EOPcMAMUEdylNddAObilIA _0XSzsMlgEdmt3adZL5Dmdw _C4U9QPTeEduDKIuqTXQ8SA _OlyWoOX7Edu8VZPtlaU33g">
+ <methodElementProperty xmi:id="_h6isQOCrEdynptYdmll41Q" name="CategoryElementsSortType"
+ value="MethodType"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Z2cK3LPPEduocbW-TPTq7A"
+ name="CoreContent" guid="_Z2cK3LPPEduocbW-TPTq7A">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_8A8e8NPREduegN_z1rVgJA"
+ name="Basic Software Design" guid="_8A8e8NPREduegN_z1rVgJA">
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_bFjlAPTYEduDKIuqTXQ8SA"
+ name="design" guid="_bFjlAPTYEduDKIuqTXQ8SA" briefDescription="This concept outlines important principles that should be taken into account when considering the design of a system."
+ presentationName="Design" checklists="_0XSzsMlgEdmt3adZL5Dmdw">
+ <presentation xmi:id="-c5Uh71vXTPN-VmrGYVRV7w" href="uma://-c5Uh71vXTPN-VmrGYVRV7w#-c5Uh71vXTPN-VmrGYVRV7w"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_Poc7IPDzEdqYgerqi84oCA"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#__O7tAMVvEduLYZUGfgZrkQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_OlyWoOX7Edu8VZPtlaU33g"
+ name="refactoring" guid="_OlyWoOX7Edu8VZPtlaU33g" briefDescription="This guideline describes how to apply the refactoring technique to improve the design of existing code."
+ presentationName="Refactoring" checklists="_0XSzsMlgEdmt3adZL5Dmdw">
+ <presentation xmi:id="-g0jWGmg-E0rCQEmnibTDIA" href="uma://-g0jWGmg-E0rCQEmnibTDIA#-g0jWGmg-E0rCQEmnibTDIA"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_Poc7IPDzEdqYgerqi84oCA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="__MnggPTdEduDKIuqTXQ8SA"
+ name="analyze_the_design" guid="__MnggPTdEduDKIuqTXQ8SA" briefDescription="This guideline describes how to approach creating a solution from requirements or change requests. A better solution will usually emerge when even a brief amount of time is spent analyzing the problem and considering approaches."
+ presentationName="Analyze the Design" conceptsAndPapers="_bFjlAPTYEduDKIuqTXQ8SA"
+ checklists="_0XSzsMlgEdmt3adZL5Dmdw">
+ <presentation xmi:id="-1vS_ELnQxGQKwfCrRYrc7w" href="uma://-1vS_ELnQxGQKwfCrRYrc7w#-1vS_ELnQxGQKwfCrRYrc7w"/>
+ <guidelines href="#_C4U9QPTeEduDKIuqTXQ8SA"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_uF-QYEAhEdq_UJTvM1DM2Q"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_vO2uoO0OEduUpsu85bVhiQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_C4U9QPTeEduDKIuqTXQ8SA"
+ name="evolve_the_design" guid="_C4U9QPTeEduDKIuqTXQ8SA" briefDescription="This guideline describes techniques to refine and evolve the design of the software. 
Good object-oriented techniques are applied within the context of the architecture 
to create a system design that's understandable, extensible, and maintainable."
+ presentationName="Evolve the Design" checklists="_0XSzsMlgEdmt3adZL5Dmdw">
+ <presentation xmi:id="-8V5osHpRNG6Z7KPy8RGW1w" href="uma://-8V5osHpRNG6Z7KPy8RGW1w#-8V5osHpRNG6Z7KPy8RGW1w"/>
+ <conceptsAndPapers href="#_bFjlAPTYEduDKIuqTXQ8SA"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_Poc7IPDzEdqYgerqi84oCA"/>
+ <guidelines href="#__MnggPTdEduDKIuqTXQ8SA"/>
+ <guidelines href="#_OlyWoOX7Edu8VZPtlaU33g"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_vO2uoO0OEduUpsu85bVhiQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_0fshwMlgEdmt3adZL5Dmdw"
+ name="design_solution" guid="_0fshwMlgEdmt3adZL5Dmdw" briefDescription="Identify the elements and devise the interactions, behavior, relations, and data necessary to realize some functionality."
+ presentationName="Design the Solution" output="_0WuL8slgEdmt3adZL5Dmdw"
+ optionalInput="_0WuL8slgEdmt3adZL5Dmdw">
+ <presentation xmi:id="_NrC20qeqEdmKDbQuyzCoqQ" href="uma://_NrC20qeqEdmKDbQuyzCoqQ#_NrC20qeqEdmKDbQuyzCoqQ"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_mzxI0A4LEduibvKwrGxWxA"/>
+ <conceptsAndPapers href="#_bFjlAPTYEduDKIuqTXQ8SA"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_w2ACwA4LEduibvKwrGxWxA"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_0LcUkA4LEduibvKwrGxWxA"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_0YJvUMlgEdmt3adZL5Dmdw"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_uF-QYEAhEdq_UJTvM1DM2Q"/>
+ <guidelines href="#__MnggPTdEduDKIuqTXQ8SA"/>
+ <guidelines href="#_C4U9QPTeEduDKIuqTXQ8SA"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_vO2uoO0OEduUpsu85bVhiQ"/>
+ <mandatoryInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_8OD-cLPTEduocbW-TPTq7A"/>
+ <mandatoryInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_i3vkoLS-EduDY8LNbMCDBA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_jJqygEqlEdyi3_jfs__bIQ"
+ name="software_design_slot.design" guid="_jJqygEqlEdyi3_jfs__bIQ" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_IcQOUEqdEdyi3_jfs__bIQ"/>
+ <containedArtifacts xmi:id="_0WuL8slgEdmt3adZL5Dmdw" name="design" guid="_0WuL8slgEdmt3adZL5Dmdw"
+ briefDescription="This artifact describes the realization of required system functionality and serves as an abstraction of the source code. "
+ presentationName="Design" conceptsAndPapers="_bFjlAPTYEduDKIuqTXQ8SA"
+ checklists="_0XSzsMlgEdmt3adZL5Dmdw" templates="_EOPcMAMUEdylNddAObilIA">
+ <presentation xmi:id="_zxB-QKYcEdmvhNXG0Oc2uA" href="uma://_zxB-QKYcEdmvhNXG0Oc2uA#_zxB-QKYcEdmvhNXG0Oc2uA"/>
+ </containedArtifacts>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Template" xmi:id="_EOPcMAMUEdylNddAObilIA"
+ name="design" guid="_EOPcMAMUEdylNddAObilIA" briefDescription="This is the informal template suggested for representing design."
+ presentationName="Design">
+ <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" briefDescription="This checklist provides questions to verify that the design is created in a consistent and complete manner."
+ presentationName="Design">
+ <presentation xmi:id="_YIYIYMM1EdmSIPI87WLu3g" href="uma://_YIYIYMM1EdmSIPI87WLu3g#_YIYIYMM1EdmSIPI87WLu3g"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="_skRykMuYEdyRPtFYRAKVDg"
+ name="release_info_evolutionary_design" guid="_skRykMuYEdyRPtFYRAKVDg"
+ presentationName="Evolutionary Design Release Information">
+ <presentation xmi:id="-xn-M2VApZPqzI5KflPNIVw" href="uma://-xn-M2VApZPqzI5KflPNIVw#-xn-M2VApZPqzI5KflPNIVw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="_FxgacOCqEdynptYdmll41Q"
+ name="enablement" guid="_FxgacOCqEdynptYdmll41Q" briefDescription="This material provides enablement material for learning to adopt the Evolutionary Design practice."
+ presentationName="Enablement">
+ <presentation xmi:id="-WVSbWqzqT0OSgdmRnsjS9w" href="uma://-WVSbWqzqT0OSgdmRnsjS9w#-WVSbWqzqT0OSgdmRnsjS9w"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Roadmap" xmi:id="_irQiEOCsEdynptYdmll41Q"
+ name="how_to_adopt" guid="_irQiEOCsEdynptYdmll41Q" briefDescription="This roadmap describes how to adopt the Evolutionary Development practice."
+ presentationName="How to Adopt This Practice">
+ <presentation xmi:id="-QmIvs-rs3Fiyg7PVRx2IvQ" href="uma://-QmIvs-rs3Fiyg7PVRx2IvQ#-QmIvs-rs3Fiyg7PVRx2IvQ"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_PGDx8PisEdmjyaJMRcPDWA"
+ name="Visual Modeling" guid="_PGDx8PisEdmjyaJMRcPDWA">
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_ZTGAYL3uEdqLRJZPGVbHDA"
+ name="design.vm" guid="_ZTGAYL3uEdqLRJZPGVbHDA" presentationName="(was design_vm)"
+ variabilityType="contributes" variabilityBasedOnElement="_0WuL8slgEdmt3adZL5Dmdw"
+ guidelines="_1fM3AC9_EduW5uTjiIcspQ"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_T8WvwL3vEdqLRJZPGVbHDA"
+ name="design_solution.vm" guid="_T8WvwL3vEdqLRJZPGVbHDA" briefDescription="Render the design visually to aid in solving the problem and communicating the solution."
+ orderingGuide="<?xml version="1.0" encoding="ASCII"?> <com.ibm.uma.edit.tng.util.model:OrderInfoCollection xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:com.ibm.uma.edit.tng.util.model="http:///com/ibm/uma/edit/tng/util/model.ecore"> <orderInfos name="sections" timestamp="1146255243164"> <gUIDs>_4Z7WYKuKEdmhFZtkg1nakg</gUIDs> <gUIDs>_YiTAIL3vEdqLRJZPGVbHDA</gUIDs> <gUIDs>_--6tYKuKEdmhFZtkg1nakg</gUIDs> <gUIDs>_RBAyANbzEdqu5o2S60g5LA</gUIDs> <gUIDs>_A_LU8KuLEdmhFZtkg1nakg</gUIDs> <gUIDs>_ObN0cNbzEdqu5o2S60g5LA</gUIDs> <gUIDs>_ENwJwKuLEdmhFZtkg1nakg</gUIDs> <gUIDs>_Gyf-cKuLEdmhFZtkg1nakg</gUIDs> <gUIDs>_JrHKUKuLEdmhFZtkg1nakg</gUIDs> <gUIDs>_KNZYAKuLEdmhFZtkg1nakg</gUIDs> <gUIDs>_OGYbwKuLEdmhFZtkg1nakg</gUIDs> </orderInfos> </com.ibm.uma.edit.tng.util.model:OrderInfoCollection> "
+ presentationName="(was design_solution_vm)" variabilityType="contributes"
+ variabilityBasedOnElement="_0fshwMlgEdmt3adZL5Dmdw">
+ <presentation xmi:id="-_BAmniONtHWbpHQH7znR3g" href="uma://-_BAmniONtHWbpHQH7znR3g#-_BAmniONtHWbpHQH7znR3g"/>
+ <guidelines href="#_1fM3AC9_EduW5uTjiIcspQ"/>
+ <guidelines href="uma://_-bv0ELXuEduGP_98XMd0fg#_z_wMgJI7Edyk6dG0ehkW5Q"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_1fM3AC9_EduW5uTjiIcspQ"
+ name="designing_visually" guid="_1fM3AC9_EduW5uTjiIcspQ" briefDescription="This guideline provides information on how to apply visual modeling to designing a system."
+ presentationName="Designing Visually">
+ <presentation xmi:id="-1xE2ZW3MjNAJ7jkaZNbkww" href="uma://-1xE2ZW3MjNAJ7jkaZNbkww#-1xE2ZW3MjNAJ7jkaZNbkww"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Checklist" xmi:id="_nnSXcD6SEduAL-bCqar_dg"
+ name="design_vm" guid="_nnSXcD6SEduAL-bCqar_dg" presentationName="Visual Modeling Design"
+ variabilityType="contributes" variabilityBasedOnElement="_0XSzsMlgEdmt3adZL5Dmdw">
+ <presentation xmi:id="-HQSI39vBrjpmQL1qHYOJtA" href="uma://-HQSI39vBrjpmQL1qHYOJtA#-HQSI39vBrjpmQL1qHYOJtA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_m42lMPTeEduDKIuqTXQ8SA"
+ name="analyze_the_design_vm" guid="_m42lMPTeEduDKIuqTXQ8SA" variabilityType="contributes"
+ variabilityBasedOnElement="__MnggPTdEduDKIuqTXQ8SA" guidelines="_1fM3AC9_EduW5uTjiIcspQ"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_jkvJEPTeEduDKIuqTXQ8SA"
+ name="evolve_the_design_vm" guid="_jkvJEPTeEduDKIuqTXQ8SA" variabilityType="contributes"
+ variabilityBasedOnElement="_C4U9QPTeEduDKIuqTXQ8SA" guidelines="_1fM3AC9_EduW5uTjiIcspQ"/>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_Z2cK3bPPEduocbW-TPTq7A"
+ name="CapabilityPatterns" guid="_Z2cK3bPPEduocbW-TPTq7A">
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_Wvf0oMQNEduMu5zRIJX95g"
+ name="Basic Development Practice Patterns" guid="_Wvf0oMQNEduMu5zRIJX95g"/>
+ </childPackages>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_Z2cK3rPPEduocbW-TPTq7A"
+ name="DeliveryProcesses" guid="_Z2cK3rPPEduocbW-TPTq7A"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_Z2cK37PPEduocbW-TPTq7A"
+ name="ProcessContributions" guid="_Z2cK37PPEduocbW-TPTq7A"/>
+ <bases href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0ELXuEduGP_98XMd0fg"/>
+ <bases href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2AAouEdyhlpBPrduOMw"/>
+ <bases href="uma://_iVydgENdEdy245g62lfWcA#_iVydgENdEdy245g62lfWcA"/>
+ <bases href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno4EKmEdyrauqpmnA8jQ"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/tasks/design_solution.vm.xmi b/praclib/temp/practice.tech.evolutionary_design.base/tasks/design_solution.vm.xmi
new file mode 100644
index 0000000..e27669b
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/tasks/design_solution.vm.xmi
@@ -0,0 +1,6 @@
+<?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.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="-_BAmniONtHWbpHQH7znR3g"
+ name=",_T8WvwL3vEdqLRJZPGVbHDA" guid="-_BAmniONtHWbpHQH7znR3g"/>
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/tasks/design_solution.xmi b/praclib/temp/practice.tech.evolutionary_design.base/tasks/design_solution.xmi
new file mode 100644
index 0000000..bafa517
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/tasks/design_solution.xmi
@@ -0,0 +1,240 @@
+<?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.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="_NrC20qeqEdmKDbQuyzCoqQ"
+ name="design_solution,_0fshwMlgEdmt3adZL5Dmdw" guid="_NrC20qeqEdmKDbQuyzCoqQ"
+ changeDate="2008-01-25T12:58:59.070-0500" version="1.0.0">
+ <mainDescription><p>
+ This task is about designing part of the system, not the whole system.&nbsp; It should be applied based upon some small
+ subset of requirements.&nbsp; The requirements driving the design could be scenario-based functional requirements,
+ non-functional requirements, or a combination.
+</p>
+<p>
+ This task can be applied in some specific context such as the database access elements required for some
+ scenario.&nbsp; In this case the task might be applied&nbsp;again later&nbsp;to deal with a different context on the
+ same requirements.&nbsp; Keep in mind that to actually build some functionality of value&nbsp;to the users, all
+ contexts will typically need to be designed and implemented. For example, to actually utilize some system capability it
+ will have to have been designed and implemented all its context such as user interface, business rules, database
+ access, etc.
+</p>
+<p>
+ For cohesion and completeness, this task is described as an end-to-end pass of designing a scenario of system usage. In
+ practice, this task will be revisited many times as the design is first considered, portions are implemented, more
+ design is performed based on what was learned, etc. The healthiest application of this task is in very close proximity
+ to the implementation.
+</p>
+<p>
+ If this task is being performed on an architecturally significant element the results of this design should be
+ referenced by the <a class="elementLink"
+ href="./../../core.tech.slot.base/workproducts/technical_architecture_slot_FF074CDD.html"
+ guid="_8OD-cLPTEduocbW-TPTq7A">[Technical Architecture]</a>.
+</p></mainDescription>
+ <keyConsiderations><p>
+ Each step in this task can cause all previous steps to be revisited in light of new information and decisions.&nbsp;
+ For example, while determining how elements collaborate&nbsp;you might find a gap in the requirements that causes you
+ to go back to the beginning after collaborating with the analyst, or when evaluating the design a reviewer
+ could&nbsp;note that a reusable element being used doesn't work as expected and that could cause you to identify new
+ elements to take its place.
+</p>
+<p>
+ Consider the architecture while performing this task.&nbsp; All design work must be done while regarding the
+ architecture within which the design exists.&nbsp; Furthermore, certain design elements will be deemed architecturally
+ significant; those elements will require updates to the architecture.
+</p>
+<p>
+ This task will be applied numerous times.&nbsp; Design is best performed in small chunks.
+</p>
+<p>
+ Even when starting the design for a particular project it&nbsp;is expected that there will be existing frameworks and
+ reusable elements.&nbsp; Every step of this task must give attention to the existing design and existing
+ implementation, utilizing existing elements when possible and emulating or improving existing elements as appropriate
+ while designing this portion of the solution.
+</p>
+<p>
+ Apply patterns throughout this task.&nbsp; Patterns represent proven designs and their usage promotes quality and
+ consistency across the design.
+</p></keyConsiderations>
+ <sections xmi:id="_4Z7WYKuKEdmhFZtkg1nakg" name="Understand requirement details"
+ guid="_4Z7WYKuKEdmhFZtkg1nakg">
+ <sectionDescription><p>
+ Examine the relevant&nbsp;<a class="elementLink"
+ href="./../../core.tech.slot.base/workproducts/technical_requirements_slot_2812F7EF.html"
+ guid="_i3vkoLS-EduDY8LNbMCDBA">[Technical Requirements]</a>&nbsp;to understand the scope of the design task and the
+ expectations on the <a class="elementLink"
+ href="./../../practice.tech.evolutionary_design.base/workproducts/design_D677D182.html"
+ guid="_0WuL8slgEdmt3adZL5Dmdw">Design</a>. Work with the Stakeholder and Analyst to clarify ambiguous or missing
+ information.
+</p>
+<p>
+ If the requirements are not represented in some sort of scenario form (for example a non-functional requirement might
+ not have a scenario associated with it), a scenario will have to be identified that appropriately exercises the
+ requirements under consideration.
+</p>
+<p>
+ If the requirements are&nbsp;determined to be&nbsp;incomplete or incorrect, work with the analyst to get the
+ requirements improved and possibly submit a change request against the requirements.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_Ci7aYFixEdusJoWkvSRO9Q" name="Understand the architecture" guid="_Ci7aYFixEdusJoWkvSRO9Q">
+ <sectionDescription><p>
+ Review the Architecture Notebook to identify changes and additions to the architecture. See&nbsp;<a
+ class="elementLinkWithType"
+ href="./../../practice.tech.evolutionary_design.base/guidances/guidelines/evolve_the_design_3C9D6965.html"
+ guid="_C4U9QPTeEduDKIuqTXQ8SA">Guideline: Evolve the Design</a>&nbsp;for more information. Work with the architect if
+ there is any uncertainty on the understanding of relevant parts of the architecture or of the conformance of the design
+ strategy.
+</p>
+<p>
+ This step can be skipped if there were no changes to the&nbsp;architecture in the previous iteration
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_--6tYKuKEdmhFZtkg1nakg" name="Identify design elements" guid="_--6tYKuKEdmhFZtkg1nakg">
+ <sectionDescription><p>
+ Identify the elements that collaborate together to provide the required behavior. This can start with the key
+ abstractions identified in the Architecture Notebook, design, domain analysis, and classical analysis of the
+ requirements (noun filtering) to derive the elements that would be required to fulfill them. The <a class="elementLink"
+ href="./../../core.tech.common.base/guidances/guidelines/entity_control_boundary_pattern_C4047897.html"
+ guid="_uF-QYEAhEdq_UJTvM1DM2Q">Entity-Control-Boundary Pattern</a> provides a good start for identifying elements. Also
+ see <a class="elementLinkWithType"
+ href="./../../practice.tech.evolutionary_design.base/guidances/guidelines/analyze_the_design_4C4750C0.html"
+ guid="__MnggPTdEduDKIuqTXQ8SA">Guideline: Analyze the Design</a>.
+</p>
+<p>
+ Existing elements of the design should be examined to see if they should participate in the collaboration. It is a
+ mistake to create all new elements in each execution of this task.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_A_LU8KuLEdmhFZtkg1nakg" name="Determine how elements collaborate to realize the scenario"
+ guid="_A_LU8KuLEdmhFZtkg1nakg">
+ <sectionDescription><p>
+ Walk through the scenario distributing responsibilities to the participating elements and ensuring that the elements
+ have the relationships required to collaborate.
+</p>
+<p>
+ These responsibilities can be simple statements of behavior assigned to elements; they need not be detailed operation
+ specifications with parameters, etc. Similarly, the relationships can just be defined at this step. This step is about
+ ensuring that a quality model is being created that is robust enough to support the requirements. See <a
+ class="elementLinkWithType"
+ href="./../../practice.tech.evolutionary_design.base/guidances/guidelines/analyze_the_design_4C4750C0.html"
+ guid="__MnggPTdEduDKIuqTXQ8SA">Guideline: Analyze the Design</a>.
+</p>
+<p>
+ Look to the architecture and previous design work to create a consistent collaboration. Work with the architect to
+ understand the details and motivations of the architecture. Look to reuse existing behavior and relations or to apply
+ similar structure to simplify the design of the overall system.&nbsp; For more information, see&nbsp; <a
+ class="elementLinkWithType" href="./../../core.tech.common.base/guidances/guidelines/software_reuse_B6B04C26.html"
+ guid="_vO2uoO0OEduUpsu85bVhiQ">Guideline: Software Reuse</a>.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_ENwJwKuLEdmhFZtkg1nakg" name="Refine design decisions" guid="_ENwJwKuLEdmhFZtkg1nakg">
+ <sectionDescription><p>
+ Refine the design to an appropriate level of detail to drive implementation and to ensure that it fits into the
+ architecture. In this step the design can take into consideration the actual implementation language and other
+ technical decisions. Revisit the identification of the elements and the collaborations that realize the scenarios if
+ necessary as this refinement takes into consideration details at a lower level of abstraction. Discuss testability
+ issues, such as design elements that are difficult to test or critical performance areas, with the tester and
+ architect.
+</p>
+<p>
+ Evolve the design by examining recent changes in the larger context of the design and determine if refactoring and
+ redesigning techniques will improve the robustness, flexibility, and understandability of the design. See&nbsp;<a
+ class="elementLinkWithType"
+ href="./../../practice.tech.evolutionary_design.base/guidances/guidelines/evolve_the_design_3C9D6965.html"
+ guid="_C4U9QPTeEduDKIuqTXQ8SA">Guideline: Evolve the Design</a> for guidance specific design decisions and on making
+ design improvements just when they're needed.
+</p>
+<p>
+ Incorporate <a class="elementLink" href="./../../core.tech.slot.base/guidances/concepts/arch_mech_2932DFB6.html"
+ guid="_mzxI0A4LEduibvKwrGxWxA">Architectural Mechanism</a>s from the architecture. Apply consistent structure of the
+ elements and organization of the behavior as in other areas of the design and use patterns identified in the
+ architecture.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_KNZYAKuLEdmhFZtkg1nakg" name="Design internals (for large or complex elements)"
+ guid="_KNZYAKuLEdmhFZtkg1nakg">
+ <sectionDescription><p>
+ Design large or complex elements or some complex internal behavior in more detail.
+</p>
+<p>
+ This might just involve devising an algorithm that could be performed to produce the desired behavior. Add additional
+ operations, attributes, and relationships to support the expectations of an element.
+</p>
+<p>
+ Design the state of the element over the course of its lifetime to ensure its proper behavior in various circumstances.
+ It may be useful to describe a state machine for elements with complex states.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_OGYbwKuLEdmhFZtkg1nakg" name="Communicate the design" guid="_OGYbwKuLEdmhFZtkg1nakg">
+ <sectionDescription><p>
+ Communicate&nbsp;the system's design to&nbsp;those who need to understand it. Though this is described here toward the
+ end of the task, communication should be going on throughout the steps. Working collaboratively is always better than
+ reviewing the work after it is complete.
+</p>
+<p>
+ Here are some ways to communicate&nbsp;the design:
+</p>
+<ul>
+ <li>
+ Formal models&nbsp;specified in UML.
+ </li>
+ <li>
+ Informal diagrams that render static structure and capture&nbsp;dynamic behavior.
+ </li>
+ <li>
+ Annotated code that communicates information about the static structure. This can be&nbsp;supplemented with textual
+ descriptions of collaborative behavior across code modules.
+ </li>
+ <li>
+ Data models to describe the database schema.
+ </li>
+</ul>
+<p>
+ Here are some examples of individuals&nbsp;who will need to understand the design of the system:
+</p>
+<ul>
+ <li>
+ Developers&nbsp;who will implement a solution based on the design.
+ </li>
+ <li>
+ Architects who can review the design to ensure that it conforms to the architecture or who might examine the design
+ for opportunities to improve the architecture.
+ </li>
+ <li>
+ Other designers who can examine the design for applicability to other parts of the system.
+ </li>
+ <li>
+ Developers or other designers who will be working on other parts of the system that will&nbsp;depend on the
+ elements designed in this task.
+ </li>
+ <li>
+ Other reviewers&nbsp;who will review the design for quality and adherence to standards.
+ </li>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_mUVt8BfnEduD353bkQ4frw" name="Evaluate the design" guid="_mUVt8BfnEduD353bkQ4frw">
+ <sectionDescription><p>
+ Evaluate the object design for coupling, cohesion, and other quality design measurements.
+</p>
+<p>
+ Consider the design from various angles to ensure that it is a high-quality, communicable design. Work with other
+ technical team members; an independent party can provide a fresh perspective. Use the tester and architect to provide
+ perspectives on design quality and adherence to the architecture. However, when identifying potential reviewers keep in
+ mind that if someone can add value by reviewing the design, then perhaps they could have added even more value by
+ actively participating in the design effort itself. If design flaws are identified, improve the design.
+</p>
+<p>
+ See <a class="elementLinkWithType"
+ href="./../../practice.tech.evolutionary_design.base/guidances/concepts/design_E36137FA.html"
+ guid="_bFjlAPTYEduDKIuqTXQ8SA">Concept: Design</a>, <a class="elementLinkWithType"
+ href="./../../practice.tech.evolutionary_design.base/guidances/guidelines/analyze_the_design_4C4750C0.html"
+ guid="__MnggPTdEduDKIuqTXQ8SA">Guideline: Analyze the Design</a>, and <a class="elementLinkWithType"
+ href="./../../practice.tech.evolutionary_design.base/guidances/guidelines/evolve_the_design_3C9D6965.html"
+ guid="_C4U9QPTeEduDKIuqTXQ8SA">Guideline: Evolve the Design</a>&nbsp;for more information.
+</p></sectionDescription>
+ </sections>
+ <purpose><p>
+ The purpose of&nbsp;this&nbsp;task&nbsp;is to describe the&nbsp;elements of the system so that they support the
+ required behavior, are of high quality, and fit within the architecture.
+</p></purpose>
+</org.eclipse.epf.uma:TaskDescription>
diff --git a/praclib/temp/practice.tech.evolutionary_design.base/workproducts/design.xmi b/praclib/temp/practice.tech.evolutionary_design.base/workproducts/design.xmi
new file mode 100644
index 0000000..8ea5748
--- /dev/null
+++ b/praclib/temp/practice.tech.evolutionary_design.base/workproducts/design.xmi
@@ -0,0 +1,55 @@
+<?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="_zxB-QKYcEdmvhNXG0Oc2uA"
+ name="design,_0WuL8slgEdmt3adZL5Dmdw" guid="_zxB-QKYcEdmvhNXG0Oc2uA" changeDate="2008-01-24T17:09:07.415-0800"
+ version="1.0.0">
+ <mainDescription><p>
+ This product can describe multiple static and dynamic views of the system for examination. Although various views may
+ focus on divergent, seemingly independent issues of how the system will be put together and work, they should fit
+ together without contradiction.
+</p>
+<p>
+ It describes the elements that will make up the implemented system. It communicates abstractions of particular portions
+ of the implementation and can describe an&nbsp;encapsulated subsystem, a high-level analysis of the system, a view of
+ the system in only one context, or other perspectives that explain a solution to a specific problem that needs to be
+ communicated.
+</p></mainDescription>
+ <purpose><p>
+ &nbsp;Describe the&nbsp;elements of the system&nbsp;so&nbsp;they can be examined and understood in ways
+ not&nbsp;possible by reading the source code.
+</p></purpose>
+ <impactOfNotHaving><p>
+ Implementation will proceed with fine-grained, inconsistent tactical decisions that lead to poor-quality software.
+</p></impactOfNotHaving>
+ <reasonsForNotNeeding>Some representation of the design will always be necessary. In circumstances where a project involves applying
+well-understood, existing strategies for architecture and design, it is possible that you will not need a <em>new</em>
+design. In those cases, you can simply refer to some existing design.</reasonsForNotNeeding>
+ <representationOptions><table>
+ <tr>
+ <th class="sectionTableHeading" scope="row">
+ </th>
+ <td class="sectionTableCell">
+ <p>
+ It is important that the author of this work product be able to analyze key decisions about the structure
+ and behavior of the system and communicate them to other collaborators. It is also important that these
+ decisions can be communicated at various levels of abstraction and granularity. Some aspects of the design
+ can be represented by source code, possibly with some extra annotations. But more abstract representations
+ of the design will be at a higher-level than source code.
+ </p>
+ <p>
+ The more abstract representation could use various representation options. UML could be used either
+ strictly or informally; it is a preferred notation based on its rich semantics and broad usage in the
+ industry. Other techniques could be used to communicate the design. Or the design could use a mix of
+ techniques as applicable.
+ </p>
+ <p>
+ Whether you record these representations on a white board or use a formal tool is not governed by this
+ process. But any representation, whether characterized as formal or informal, should unambiguously
+ communicate the technical decisions embodied by the design.
+ </p>
+ </td>
+ </tr>
+</table></representationOptions>
+</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/praclib/temp/practice.tech.shared_vision.assign/.project b/praclib/temp/practice.tech.shared_vision.assign/.project
new file mode 100644
index 0000000..4f5fa39
--- /dev/null
+++ b/praclib/temp/practice.tech.shared_vision.assign/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>practice.tech.shared_vision.assign</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/practice.tech.shared_vision.assign/plugin.xmi b/praclib/temp/practice.tech.shared_vision.assign/plugin.xmi
new file mode 100644
index 0000000..6d5dc1c
--- /dev/null
+++ b/praclib/temp/practice.tech.shared_vision.assign/plugin.xmi
@@ -0,0 +1,69 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_NjWMAMrmEdyd6uFrFHNXhA"
+ guid="_NjWMAMrmEdyd6uFrFHNXhA"/>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_NjNCEMrmEdyd6uFrFHNXhA" name="practice.tech.shared_vision.assign"
+ guid="_NjNCEMrmEdyd6uFrFHNXhA">
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_NjNCEcrmEdyd6uFrFHNXhA"
+ name="Content" guid="_NjNCEcrmEdyd6uFrFHNXhA">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_NjNCEsrmEdyd6uFrFHNXhA"
+ name="Categories" guid="_NjNCEsrmEdyd6uFrFHNXhA">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_NjNCE8rmEdyd6uFrFHNXhA"
+ name="Domains" guid="_NjNCE8rmEdyd6uFrFHNXhA"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_NjNCFMrmEdyd6uFrFHNXhA"
+ name="Disciplines" guid="_NjNCFMrmEdyd6uFrFHNXhA">
+ <contentElements xsi:type="org.eclipse.epf.uma:Discipline" xmi:id="_2a-s0MrmEdyd6uFrFHNXhA"
+ name="requirements_discipline.assign" guid="_2a-s0MrmEdyd6uFrFHNXhA"
+ variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Discipline" href="uma://_MRPloEFXEdy9ENCpSugIjA#_iGSHtVZ-EdyIUdvDLLUdeg"/>
+ <tasks href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_0fOAoMlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_NjNCFcrmEdyd6uFrFHNXhA"
+ name="RoleSets" guid="_NjNCFcrmEdyd6uFrFHNXhA"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_NjNCFsrmEdyd6uFrFHNXhA"
+ name="WP Types" guid="_NjNCFsrmEdyd6uFrFHNXhA"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_NjNCF8rmEdyd6uFrFHNXhA"
+ name="Tools" guid="_NjNCF8rmEdyd6uFrFHNXhA"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_NjNCGMrmEdyd6uFrFHNXhA"
+ name="StandardCategories" guid="_NjNCGMrmEdyd6uFrFHNXhA"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_NjNCGcrmEdyd6uFrFHNXhA"
+ name="CustomCategories" guid="_NjNCGcrmEdyd6uFrFHNXhA">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_NjNCGsrmEdyd6uFrFHNXhA"
+ name="Hidden" guid="_NjNCGsrmEdyd6uFrFHNXhA">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_NjNCG8rmEdyd6uFrFHNXhA"
+ name="Custom Categories" guid="_NjNCG8rmEdyd6uFrFHNXhA"/>
+ </childPackages>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_NjNCHMrmEdyd6uFrFHNXhA"
+ name="CoreContent" guid="_NjNCHMrmEdyd6uFrFHNXhA">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_hBEI8MrmEdyd6uFrFHNXhA"
+ name="Role Assignments" guid="_hBEI8MrmEdyd6uFrFHNXhA">
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_rJw3QMrmEdyd6uFrFHNXhA"
+ name="develop_technical_vision.assign_role" guid="_rJw3QMrmEdyd6uFrFHNXhA"
+ variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Task" href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_0fOAoMlgEdmt3adZL5Dmdw"/>
+ <performedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0VxJsMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0X9iEMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0a0o0MlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_dTa6gMAYEdqX-s4mWhkyqQ"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_NjNCHcrmEdyd6uFrFHNXhA"
+ name="CapabilityPatterns" guid="_NjNCHcrmEdyd6uFrFHNXhA"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_NjNCHsrmEdyd6uFrFHNXhA"
+ name="DeliveryProcesses" guid="_NjNCHsrmEdyd6uFrFHNXhA"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_NjNCH8rmEdyd6uFrFHNXhA"
+ name="ProcessContributions" guid="_NjNCH8rmEdyd6uFrFHNXhA"/>
+ <bases href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPloEFXEdy9ENCpSugIjA"/>
+ <bases href="uma://_A118oMYaEdyXeo04os5BOw#_A118oMYaEdyXeo04os5BOw"/>
+ <bases href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKMLS9EduDY8LNbMCDBA"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/practice.tech.shared_vision.base/.project b/praclib/temp/practice.tech.shared_vision.base/.project
new file mode 100644
index 0000000..9acd209
--- /dev/null
+++ b/praclib/temp/practice.tech.shared_vision.base/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>practice.tech.shared_vision.base</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/practice.tech.shared_vision.base/customcategories/resources/bookc.gif b/praclib/temp/practice.tech.shared_vision.base/customcategories/resources/bookc.gif
new file mode 100644
index 0000000..7f2ab85
--- /dev/null
+++ b/praclib/temp/practice.tech.shared_vision.base/customcategories/resources/bookc.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.shared_vision.base/customcategories/resources/bookcL.gif b/praclib/temp/practice.tech.shared_vision.base/customcategories/resources/bookcL.gif
new file mode 100644
index 0000000..6c5b064
--- /dev/null
+++ b/praclib/temp/practice.tech.shared_vision.base/customcategories/resources/bookcL.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.shared_vision.base/customcategories/resources/compass.gif b/praclib/temp/practice.tech.shared_vision.base/customcategories/resources/compass.gif
new file mode 100644
index 0000000..39f306a
--- /dev/null
+++ b/praclib/temp/practice.tech.shared_vision.base/customcategories/resources/compass.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.shared_vision.base/customcategories/resources/compassL.gif b/praclib/temp/practice.tech.shared_vision.base/customcategories/resources/compassL.gif
new file mode 100644
index 0000000..4117414
--- /dev/null
+++ b/praclib/temp/practice.tech.shared_vision.base/customcategories/resources/compassL.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.shared_vision.base/customcategories/resources/pract_dgm32.gif b/praclib/temp/practice.tech.shared_vision.base/customcategories/resources/pract_dgm32.gif
new file mode 100644
index 0000000..f597332
--- /dev/null
+++ b/praclib/temp/practice.tech.shared_vision.base/customcategories/resources/pract_dgm32.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.shared_vision.base/customcategories/resources/pract_obj.gif b/praclib/temp/practice.tech.shared_vision.base/customcategories/resources/pract_obj.gif
new file mode 100644
index 0000000..fe8075a
--- /dev/null
+++ b/praclib/temp/practice.tech.shared_vision.base/customcategories/resources/pract_obj.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.shared_vision.base/customcategories/shared_vision_practice.xmi b/praclib/temp/practice.tech.shared_vision.base/customcategories/shared_vision_practice.xmi
new file mode 100644
index 0000000..e17a211
--- /dev/null
+++ b/praclib/temp/practice.tech.shared_vision.base/customcategories/shared_vision_practice.xmi
@@ -0,0 +1,48 @@
+<?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="-8UPVWhGYXAQa93quxXqXiw"
+ name="shared_vision_practice,_a1LJAJ-lEdyBk-WQzMU-FQ" guid="-8UPVWhGYXAQa93quxXqXiw"
+ changeDate="2008-01-16T15:37:40.042-0800" version="7.2.0">
+ <mainDescription><h3>
+ Why adopt this practice
+</h3>
+<p>
+ It is not uncommon that misunderstandings and miscommunication about the project strategy may&nbsp;lead the project
+ team to develop a system that goes away from the original stakeholders' needs and vision. Without the correct context
+ for decision-making about the requirements, not only user's satisfaction may be compromised, but also the project may
+ be cancelled.
+</p>
+<p>
+ It is&nbsp;rather important that the development team and stakeholders have the same expectations. A shared vision
+ provides a common understanding of&nbsp;the problem being addressed,&nbsp;a view of the&nbsp;high-level stakeholder
+ requests and project constraints, and the background and context for requirements that will be later detailed. A shared
+ vision serves as input for communicating the fundamental "what and why" for the project, and provides a strategy
+ against which all future decisions should be validated.&nbsp;
+</p>
+<h3>
+ How it relates to other&nbsp;practices
+</h3>
+<p>
+ Although decoupled in the adoption sense, this practice is related to many other useful practices. For example:
+</p>
+<ul>
+ <li>
+ Requirements - the vision is one of the outcomes of stakeholder requests elicitation, but also an input while
+ gathering more fine-granular requirements. Stakeholders and development team use the vision to ensure consistency
+ while reviewing the requirements that have been identified and the ones that have been detailed.
+ </li>
+ <li>
+ Architecture -&nbsp;the vision provides the goals for the architecture and helps to identify which goals to address
+ through out project iterations.&nbsp;These goals will prioritize and guide&nbsp;the approach to
+ important&nbsp;technical decisions.
+ </li>
+ <li>
+ Project management&nbsp;- the vision captures a high-level view of the scope and constraints of the project, which
+ helps the team to discuss project (and iteration) priorities and estimates with stakeholders. The value delivered
+ by the team at the end of each iteration must align with stakeholders' expectations&nbsp;expressed by
+ the&nbsp;project vision.
+ </li>
+</ul></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.shared_vision.base/guidances/guidelines/resources/Which Req Gathering Technique.gif b/praclib/temp/practice.tech.shared_vision.base/guidances/guidelines/resources/Which Req Gathering Technique.gif
new file mode 100644
index 0000000..10b6366
--- /dev/null
+++ b/praclib/temp/practice.tech.shared_vision.base/guidances/guidelines/resources/Which Req Gathering Technique.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.shared_vision.base/guidances/guidelines/resources/Workshop Activity Diagram.GIF b/praclib/temp/practice.tech.shared_vision.base/guidances/guidelines/resources/Workshop Activity Diagram.GIF
new file mode 100644
index 0000000..228f102
--- /dev/null
+++ b/praclib/temp/practice.tech.shared_vision.base/guidances/guidelines/resources/Workshop Activity Diagram.GIF
Binary files differ
diff --git a/praclib/temp/practice.tech.shared_vision.base/guidances/supportingmaterials/release_info_shared_vision.xmi b/praclib/temp/practice.tech.shared_vision.base/guidances/supportingmaterials/release_info_shared_vision.xmi
new file mode 100644
index 0000000..d4a476c
--- /dev/null
+++ b/praclib/temp/practice.tech.shared_vision.base/guidances/supportingmaterials/release_info_shared_vision.xmi
@@ -0,0 +1,22 @@
+<?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="-xx_vVVKbIW-zVxgYjJWdRQ"
+ name="new_supporting_material,_GBAK8MuhEdyTA_Xoy-01eg" guid="-xx_vVVKbIW-zVxgYjJWdRQ"
+ changeDate="2008-01-25T15:56:29.331-0800">
+ <mainDescription><h3>
+ Shared Vision&nbsp;Practice
+</h3>
+<p>
+ Version 1.0
+</p>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p>
+ [*** NOT YET RELEASED ***]
+ </p>
+ <p>
+ This is the initial release of this practice.
+ </p>
+</blockquote></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.shared_vision.base/guidances/termdefinitions/feature.xmi b/praclib/temp/practice.tech.shared_vision.base/guidances/termdefinitions/feature.xmi
new file mode 100644
index 0000000..86be3d6
--- /dev/null
+++ b/praclib/temp/practice.tech.shared_vision.base/guidances/termdefinitions/feature.xmi
@@ -0,0 +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="-qpBnpWqiD7gjT08LjTMbsQ"
+ name="new_term_definition,_PgYREAeYEduWycDgioo5rg" guid="-qpBnpWqiD7gjT08LjTMbsQ"
+ changeDate="2007-11-09T09:51:42.038-0800" version="7.1.0">
+ <mainDescription>An externally observable service provided by the system that directly fulfills a <a class="elementLink"
+href="./../../../practice.tech.shared_vision.base/guidances/termdefinitions/stakeholder_need_F8F672BB.html"
+guid="_WUiFcAeYEduWycDgioo5rg">** stakeholder need</a>.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.shared_vision.base/guidances/termdefinitions/stakeholder_need.xmi b/praclib/temp/practice.tech.shared_vision.base/guidances/termdefinitions/stakeholder_need.xmi
new file mode 100644
index 0000000..29d5487
--- /dev/null
+++ b/praclib/temp/practice.tech.shared_vision.base/guidances/termdefinitions/stakeholder_need.xmi
@@ -0,0 +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.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="-1pmL5bC27rtWB84PXAgq9Q"
+ name="new_term_definition,_WUiFcAeYEduWycDgioo5rg" guid="-1pmL5bC27rtWB84PXAgq9Q"
+ version="7.1.0">
+ <mainDescription>The business or operational problem (opportunity) that must be fulfilled to justify purchase or use of the system.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.shared_vision.base/plugin.xmi b/praclib/temp/practice.tech.shared_vision.base/plugin.xmi
new file mode 100644
index 0000000..1de0f39
--- /dev/null
+++ b/praclib/temp/practice.tech.shared_vision.base/plugin.xmi
@@ -0,0 +1,175 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_Y9TKQbS9EduDY8LNbMCDBA"
+ guid="_Y9TKQbS9EduDY8LNbMCDBA">
+ <resourceDescriptors xmi:id="_nGJZ0PL5Edm6Nvont3uinw" id="_5rJ78Lj3Edmy88CC3LfB_w"
+ uri="tasks/develop_vision.xmi"/>
+ <resourceDescriptors xmi:id="_V1DNIO0KEdqHTdbLTmC5IQ" id="-fCBrf_5JlrmuKgyrCaKGOA"
+ uri="guidances/concepts/requirement_attributes.xmi"/>
+ <resourceDescriptors xmi:id="_J9HBcED3EdyoefaQkqWN_Q" id="_5rJ78Lj3Edmy88CC3LfB_w"
+ uri="tasks/develop_technical_vision.xmi"/>
+ <resourceDescriptors xmi:id="_kjwkoO0HEdqHTdbLTmC5IQ" id="-2o1pXjHpSEPN_rohLce5jA"
+ uri="guidances/checklists/general_requirements.xmi"/>
+ <resourceDescriptors xmi:id="_V7RtwNcNEdqz_d2XWoVt6Q" id="-pNA0DbSdSoUqnjQIiOeHcQ"
+ uri="guidances/guidelines/effective_req_reviews.xmi"/>
+ <resourceDescriptors xmi:id="_VbT-cAeYEduWycDgioo5rg" id="-qpBnpWqiD7gjT08LjTMbsQ"
+ uri="guidances/termdefinitions/feature.xmi"/>
+ <resourceDescriptors xmi:id="_d1sJwQeYEduWycDgioo5rg" id="-1pmL5bC27rtWB84PXAgq9Q"
+ uri="guidances/termdefinitions/stakeholder_need.xmi"/>
+ <resourceDescriptors xmi:id="_XkOuYL7uEdyHFv1R9eKrvQ" id="-8UPVWhGYXAQa93quxXqXiw"
+ uri="customcategories/shared_vision_practice.xmi"/>
+ <resourceDescriptors xmi:id="_Kcb0ccuhEdyTA_Xoy-01eg" id="-xx_vVVKbIW-zVxgYjJWdRQ"
+ uri="guidances/supportingmaterials/release_info_shared_vision.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_Y9TKMLS9EduDY8LNbMCDBA" name="practice.tech.shared_vision.base"
+ guid="_Y9TKMLS9EduDY8LNbMCDBA" briefDescription="This plug-in contains the requirements method elements that are needed to get concurrence on scope, features and stakeholder needs through a Vision."
+ changeDate="2008-01-25T15:45:37.815-0800">
+ <copyrightStatement href="uma://_iVydgENdEdy245g62lfWcA#_cTs20KzREduOqvpk_MDLfQ"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Y9TKMbS9EduDY8LNbMCDBA"
+ name="Content" guid="_Y9TKMbS9EduDY8LNbMCDBA">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Y9TKMrS9EduDY8LNbMCDBA"
+ name="Categories" guid="_Y9TKMrS9EduDY8LNbMCDBA">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Y9TKM7S9EduDY8LNbMCDBA"
+ name="Domains" guid="_Y9TKM7S9EduDY8LNbMCDBA"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Y9TKNLS9EduDY8LNbMCDBA"
+ name="Disciplines" guid="_Y9TKNLS9EduDY8LNbMCDBA"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Y9TKNbS9EduDY8LNbMCDBA"
+ name="RoleSets" guid="_Y9TKNbS9EduDY8LNbMCDBA"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Y9TKNrS9EduDY8LNbMCDBA"
+ name="WP Types" guid="_Y9TKNrS9EduDY8LNbMCDBA"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Y9TKN7S9EduDY8LNbMCDBA"
+ name="Tools" guid="_Y9TKN7S9EduDY8LNbMCDBA"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Y9TKOLS9EduDY8LNbMCDBA"
+ name="StandardCategories" guid="_Y9TKOLS9EduDY8LNbMCDBA"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Y9TKObS9EduDY8LNbMCDBA"
+ name="CustomCategories" guid="_Y9TKObS9EduDY8LNbMCDBA">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Y9TKOrS9EduDY8LNbMCDBA"
+ name="Hidden" guid="_Y9TKOrS9EduDY8LNbMCDBA">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_Y9TKO7S9EduDY8LNbMCDBA"
+ name="Custom Categories" guid="_Y9TKO7S9EduDY8LNbMCDBA" categorizedElements="_a1LJAJ-lEdyBk-WQzMU-FQ _SMSgQMuaEdyTA_Xoy-01eg"/>
+ </childPackages>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_a1LJAJ-lEdyBk-WQzMU-FQ"
+ name="shared_vision_practice" guid="_a1LJAJ-lEdyBk-WQzMU-FQ" briefDescription="This practice describes how to gain concurrence on scope, features, and stakeholder needs through a shared vision."
+ presentationName="Shared Vision" shapeicon="customcategories/resources/pract_dgm32.gif"
+ nodeicon="customcategories/resources/pract_obj.gif">
+ <methodElementProperty xmi:id="_gO33IMR8EdyxuNkGVhoXzg" name="CategoryElementsSortType"
+ value="MethodType"/>
+ <presentation xmi:id="-8UPVWhGYXAQa93quxXqXiw" href="uma://-8UPVWhGYXAQa93quxXqXiw#-8UPVWhGYXAQa93quxXqXiw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0WVxcMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Task" href="#_0fOAoMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_OOB2AAouEdyhlpBPrduOMw#_OnoNQNSAEdmLhZ9H5Plxyw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_SMSgQMuaEdyTA_Xoy-01eg"
+ name="contributions_to_nav_building_blocks" guid="_SMSgQMuaEdyTA_Xoy-01eg"
+ categorizedElements="_ITXhEMufEdyTA_Xoy-01eg _I5NZEMufEdyTA_Xoy-01eg _LRgtMMufEdyTA_Xoy-01eg _MLebEMufEdyTA_Xoy-01eg _Msju4MufEdyTA_Xoy-01eg _NhTlkMufEdyTA_Xoy-01eg _lL8B0NRFEdyM_J8-fv54DA"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_ITXhEMufEdyTA_Xoy-01eg"
+ name="release_info.assign" guid="_ITXhEMufEdyTA_Xoy-01eg" variabilityType="contributes"
+ categorizedElements="_GBAK8MuhEdyTA_Xoy-01eg">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCIHYcRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_I5NZEMufEdyTA_Xoy-01eg"
+ name="artifact_list.assign" guid="_I5NZEMufEdyTA_Xoy-01eg" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4YMRdEdyD76CYS6Ta7A"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0WVxcMlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_LRgtMMufEdyTA_Xoy-01eg"
+ name="checklist_list.assign" guid="_LRgtMMufEdyTA_Xoy-01eg" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_pGt9MMReEdyD76CYS6Ta7A"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Checklist" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0WoFUMlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_MLebEMufEdyTA_Xoy-01eg"
+ name="guideline_list.assign" guid="_MLebEMufEdyTA_Xoy-01eg" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4ZcRdEdyD76CYS6Ta7A"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_OOB2AAouEdyhlpBPrduOMw#_E-dPIL-GEdqb7N6KIeDL8Q"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_OOB2AAouEdyhlpBPrduOMw#_OnoNQNSAEdmLhZ9H5Plxyw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_OOB2AAouEdyhlpBPrduOMw#_1AOsMO0JEdqHTdbLTmC5IQ"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_OOB2AAouEdyhlpBPrduOMw#_6jXzYNcKEdqz_d2XWoVt6Q"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_Msju4MufEdyTA_Xoy-01eg"
+ name="template_list.assign" guid="_Msju4MufEdyTA_Xoy-01eg" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4Z8RdEdyD76CYS6Ta7A"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Template" href="uma://_OOB2AAouEdyhlpBPrduOMw#_DtlRQI5gEdyO5aWob1UGDA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_NhTlkMufEdyTA_Xoy-01eg"
+ name="practice_list.assign" guid="_NhTlkMufEdyTA_Xoy-01eg" variabilityType="contributes"
+ categorizedElements="_a1LJAJ-lEdyBk-WQzMU-FQ">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCIHY8RdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_lL8B0NRFEdyM_J8-fv54DA"
+ name="technical_practice_list" guid="_lL8B0NRFEdyM_J8-fv54DA" presentationName="Technical Practices"
+ variabilityType="contributes" categorizedElements="_a1LJAJ-lEdyBk-WQzMU-FQ">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_lBrxENQuEdyM_J8-fv54DA"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Y9TKPLS9EduDY8LNbMCDBA"
+ name="CoreContent" guid="_Y9TKPLS9EduDY8LNbMCDBA">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_qDsgQMOsEdupeqHTre3HvQ"
+ name="Tasks" guid="_qDsgQMOsEdupeqHTre3HvQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_0fOAoMlgEdmt3adZL5Dmdw"
+ name="develop_technical_vision" guid="_0fOAoMlgEdmt3adZL5Dmdw" briefDescription="Define the vision for the future system. Describe the problem and features based on stakeholder requests."
+ orderingGuide="<?xml version="1.0" encoding="ASCII"?> <com.ibm.uma.edit.tng.util.model:OrderInfoCollection xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:com.ibm.uma.edit.tng.util.model="http:///com/ibm/uma/edit/tng/util/model.ecore"> <orderInfos name="sections" timestamp="1115151259496"> <gUIDs>_sa5F4LwPEdm6DujQZORGLQ</gUIDs> <gUIDs>_tvzDULwPEdm6DujQZORGLQ</gUIDs> <gUIDs>_vGg-oLwPEdm6DujQZORGLQ</gUIDs> <gUIDs>_z7ZC4LwPEdm6DujQZORGLQ</gUIDs> <gUIDs>_u0DWcKhXEdmsY5hhGsDstg</gUIDs> <gUIDs>_yl_-EKhXEdmsY5hhGsDstg</gUIDs> <gUIDs>_zQUfoKuHEdmhFZtkg1nakg</gUIDs> <gUIDs>_1LVn0LwPEdm6DujQZORGLQ</gUIDs> <gUIDs>_2VixILwPEdm6DujQZORGLQ</gUIDs> <gUIDs>_yq-j4LwPEdm6DujQZORGLQ</gUIDs> </orderInfos> </com.ibm.uma.edit.tng.util.model:OrderInfoCollection> "
+ presentationName="Develop Technical Vision">
+ <presentation xmi:id="_5rJ78Lj3Edmy88CC3LfB_w" href="uma://_5rJ78Lj3Edmy88CC3LfB_w#_5rJ78Lj3Edmy88CC3LfB_w"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_E-dPIL-GEdqb7N6KIeDL8Q"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_OnoNQNSAEdmLhZ9H5Plxyw"/>
+ <output xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0WVxcMlgEdmt3adZL5Dmdw"/>
+ <optionalInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0WVxcMlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_yBdFENPTEduegN_z1rVgJA"
+ name="Guidance" guid="_yBdFENPTEduegN_z1rVgJA">
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_PgYREAeYEduWycDgioo5rg"
+ name="feature" guid="_PgYREAeYEduWycDgioo5rg" presentationName="feature">
+ <presentation xmi:id="-qpBnpWqiD7gjT08LjTMbsQ" href="uma://-qpBnpWqiD7gjT08LjTMbsQ#-qpBnpWqiD7gjT08LjTMbsQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_WUiFcAeYEduWycDgioo5rg"
+ name="stakeholder_need" guid="_WUiFcAeYEduWycDgioo5rg" presentationName="stakeholder need">
+ <presentation xmi:id="-1pmL5bC27rtWB84PXAgq9Q" href="uma://-1pmL5bC27rtWB84PXAgq9Q#-1pmL5bC27rtWB84PXAgq9Q"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_VbrjsEL-EdyP_Jn83ylwUQ"
+ name="Work Products" guid="_VbrjsEL-EdyP_Jn83ylwUQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_YvSCcEL-EdyP_Jn83ylwUQ"
+ name="technical_specification_slot.sv" guid="_YvSCcEL-EdyP_Jn83ylwUQ"
+ variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_i3vkoLS-EduDY8LNbMCDBA"/>
+ <containedArtifacts xmi:id="_gx-GgEL-EdyP_Jn83ylwUQ" name="vision.sv"
+ guid="_gx-GgEL-EdyP_Jn83ylwUQ" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0WVxcMlgEdmt3adZL5Dmdw"/>
+ </containedArtifacts>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_S6bmYMufEdyTA_Xoy-01eg"
+ name="Release Info" guid="_S6bmYMufEdyTA_Xoy-01eg">
+ <contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="_GBAK8MuhEdyTA_Xoy-01eg"
+ name="release_info_shared_vision" guid="_GBAK8MuhEdyTA_Xoy-01eg" presentationName="Shared Vision Practice">
+ <presentation xmi:id="-xx_vVVKbIW-zVxgYjJWdRQ" href="uma://-xx_vVVKbIW-zVxgYjJWdRQ#-xx_vVVKbIW-zVxgYjJWdRQ"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_Y9TKPbS9EduDY8LNbMCDBA"
+ name="CapabilityPatterns" guid="_Y9TKPbS9EduDY8LNbMCDBA"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_Y9TKPrS9EduDY8LNbMCDBA"
+ name="DeliveryProcesses" guid="_Y9TKPrS9EduDY8LNbMCDBA"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_Y9TKP7S9EduDY8LNbMCDBA"
+ name="ProcessContributions" guid="_Y9TKP7S9EduDY8LNbMCDBA"/>
+ <bases href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0ELXuEduGP_98XMd0fg"/>
+ <bases href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2AAouEdyhlpBPrduOMw"/>
+ <bases href="uma://_iVydgENdEdy245g62lfWcA#_iVydgENdEdy245g62lfWcA"/>
+ <bases href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPEEKmEdyrauqpmnA8jQ"/>
+ <bases href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno4EKmEdyrauqpmnA8jQ"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/practice.tech.shared_vision.base/tasks/develop_technical_vision.xmi b/praclib/temp/practice.tech.shared_vision.base/tasks/develop_technical_vision.xmi
new file mode 100644
index 0000000..047e46b
--- /dev/null
+++ b/praclib/temp/practice.tech.shared_vision.base/tasks/develop_technical_vision.xmi
@@ -0,0 +1,65 @@
+<?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.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="_5rJ78Lj3Edmy88CC3LfB_w"
+ name="develop_vision,_0fOAoMlgEdmt3adZL5Dmdw" guid="_5rJ78Lj3Edmy88CC3LfB_w" changeDate="2007-12-18T13:14:14.500-0800"
+ changeDescription="Review comments:|1. Conflicts with other GBS practices and work products|-. Removed "Define the system boundaries" - need to figure out how to get it |back in.|Removed from step 1:|Develop profiles of potential (or actual) users of the system that map to the |roles of human actors of the system that you are developing.|-. Removed "Identify constraints on the system"||Need to determine how to make this work with GS method's practices for these removed steps.|Some options:|- OpenUP could be doing something simpler than the GS Method approach that is ok to do as well (need to convince GBS)|- OpenUP could have a practice for doing these additional things that isn't part of the "basic vision", but can be added in by contributing steps|- OpenUP could go with a more basic practice for defining a vision, and not do these aspects|- The steps could be written as "optional things to do if you don't have a separate practice".||I like the first option best.||2. Removed "Update the vision" which occurs throughout the task.||3. Removed all the links to work items - we shoudn't assume it is there.||4. Removed hyperlinks to attached guidance. We need to make sure this convention is followed elsewhere.||5. Removed links to OpenUP-only guidance, such as "principles for collaborative development". Makes sense, but we need to make sure this convention is followed elsewhere."
+ version="1.0.0">
+ <keyConsiderations><p>
+ Use-case modeling&nbsp;is one technique that can prove useful in defining the system boundaries and system behavior.
+</p></keyConsiderations>
+ <sections xmi:id="_ceK-UED2EdyoefaQkqWN_Q" name="Identify Stakeholders " guid="_ceK-UED2EdyoefaQkqWN_Q">
+ <sectionDescription>Identify the stakeholders: decision-makers, customers, potential users, partners, domain experts, industry analysts and
+other interested parties. Briefly describe what stakeholders do and what their responsibilities are with regard to the
+system being developed.</sectionDescription>
+ </sections>
+ <sections xmi:id="_h7AacED2EdyoefaQkqWN_Q" name="Gain agreement on the problem to be solved "
+ guid="_h7AacED2EdyoefaQkqWN_Q">
+ <sectionDescription><p>
+ Avoid rushing into defining the solution. First, gain agreement on the definition of the problem by asking the
+ stakeholders what they see as the problem. Then search for root causes, or the “problem behind the problem”.
+ Use&nbsp;appropriate requirements gathering techniques. Formulate the problem statement. The purpose of this is to help
+ you distinguish solutions and answers from problems and questions.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_vbkccED2EdyoefaQkqWN_Q" name="Gather stakeholder requests " guid="_vbkccED2EdyoefaQkqWN_Q">
+ <sectionDescription><p>
+ Use the most appropriate technique to help you on requirements gathering.&nbsp;Each technique is applicable in a
+ particular situation or to a certain type of stakeholder.
+</p>
+<p>
+ If you can meet stakeholders in person, then you can conduct an interview or a brainstorming session. This face-to-face
+ collaboration is extremely valuable and reduces the chances of the project team misunderstanding the needs of the
+ stakeholders.
+</p>
+<p>
+ Some requirements may already be documented in other work products (such as in change requests or work items).&nbsp;
+ This can often be used as a solid starting position from which a full set of requirements can be created.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_yeVC0ED2EdyoefaQkqWN_Q" name="Define the scope of the solution"
+ guid="_yeVC0ED2EdyoefaQkqWN_Q">
+ <sectionDescription><p>
+ Analyze the scope in terms of processes, organizations, and systems.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_6uIV0ED2EdyoefaQkqWN_Q" name="Define features of the system "
+ guid="_6uIV0ED2EdyoefaQkqWN_Q">
+ <sectionDescription><p>
+ Work with stakeholders to capture&nbsp;a list&nbsp;of&nbsp;<a class="elementlinkwithusertext"
+ href="./../../practice.tech.shared_vision.base/guidances/termdefinitions/feature_4ED64AEE.html"
+ guid="_PgYREAeYEduWycDgioo5rg">features</a> that stakeholders want in the system, briefly describing them and giving <a
+ class="elementLinkWithUserText"
+ href="./../../core.tech.common.base/guidances/concepts/requirement_attributes_4AC73153.html"
+ guid="_VQ268O0KEdqHTdbLTmC5IQ">attributes</a> to help define their general status and priority in the project.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="__nDMkED2EdyoefaQkqWN_Q" name="Achieve concurrence " guid="__nDMkED2EdyoefaQkqWN_Q">
+ <sectionDescription>Conduct an effective requirements&nbsp;review&nbsp;with stakeholders and the development team&nbsp;to ensure agreement on
+the project vision, assess quality, and identify required changes.</sectionDescription>
+ </sections>
+ <purpose>The solution is proposed for a problem that everybody agrees on. Stakeholders collaborate with the development team to
+express and document their problems, needs, and potential features for the system to be, so the project team can better
+understand what has to be done.</purpose>
+</org.eclipse.epf.uma:TaskDescription>
diff --git a/praclib/temp/practice.tech.test_driven_development.assign/.project b/praclib/temp/practice.tech.test_driven_development.assign/.project
new file mode 100644
index 0000000..0d03d52
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.assign/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>practice.tech.test_driven_development.assign</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/practice.tech.test_driven_development.assign/plugin.xmi b/praclib/temp/practice.tech.test_driven_development.assign/plugin.xmi
new file mode 100644
index 0000000..b8423b6
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.assign/plugin.xmi
@@ -0,0 +1,96 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_005S0Mt1EdyRPtFYRAKVDg"
+ guid="_005S0Mt1EdyRPtFYRAKVDg"/>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_00zMMMt1EdyRPtFYRAKVDg" name="practice.tech.test_driven_development.assign"
+ guid="_00zMMMt1EdyRPtFYRAKVDg">
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_00zMMct1EdyRPtFYRAKVDg"
+ name="Content" guid="_00zMMct1EdyRPtFYRAKVDg">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_00zMMst1EdyRPtFYRAKVDg"
+ name="Categories" guid="_00zMMst1EdyRPtFYRAKVDg">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_00zMM8t1EdyRPtFYRAKVDg"
+ name="Domains" guid="_00zMM8t1EdyRPtFYRAKVDg">
+ <contentElements xsi:type="org.eclipse.epf.uma:Domain" xmi:id="_gpGG4MuAEdyRPtFYRAKVDg"
+ name="development_domain.assign" guid="_gpGG4MuAEdyRPtFYRAKVDg" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Domain" href="uma://_MRPloEFXEdy9ENCpSugIjA#_5JQLoK80Edy9cPK11VzBuQ"/>
+ <workProducts xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_kh9FcJ02EdyQ3oTO93enUw"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_00zMNMt1EdyRPtFYRAKVDg"
+ name="Disciplines" guid="_00zMNMt1EdyRPtFYRAKVDg">
+ <contentElements xsi:type="org.eclipse.epf.uma:Discipline" xmi:id="_TCegMMuAEdyRPtFYRAKVDg"
+ name="development_discipline.assign" guid="_TCegMMuAEdyRPtFYRAKVDg"
+ variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Discipline" href="uma://_MRPloEFXEdy9ENCpSugIjA#_iGSHsVZ-EdyIUdvDLLUdeg"/>
+ <tasks href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_znlIcJR9EdyVKbgqUOtqQA"/>
+ <tasks href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_Ht-z8JfJEdyZkIR-s-Y8wQ"/>
+ <tasks href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_R7atwJfIEdyZkIR-s-Y8wQ"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_00zMNct1EdyRPtFYRAKVDg"
+ name="RoleSets" guid="_00zMNct1EdyRPtFYRAKVDg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_00zMNst1EdyRPtFYRAKVDg"
+ name="WP Types" guid="_00zMNst1EdyRPtFYRAKVDg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_00zMN8t1EdyRPtFYRAKVDg"
+ name="Tools" guid="_00zMN8t1EdyRPtFYRAKVDg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_00zMOMt1EdyRPtFYRAKVDg"
+ name="StandardCategories" guid="_00zMOMt1EdyRPtFYRAKVDg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_00zMOct1EdyRPtFYRAKVDg"
+ name="CustomCategories" guid="_00zMOct1EdyRPtFYRAKVDg">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_00zMOst1EdyRPtFYRAKVDg"
+ name="Hidden" guid="_00zMOst1EdyRPtFYRAKVDg">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_00zMO8t1EdyRPtFYRAKVDg"
+ name="Custom Categories" guid="_00zMO8t1EdyRPtFYRAKVDg"/>
+ </childPackages>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_00zMPMt1EdyRPtFYRAKVDg"
+ name="CoreContent" guid="_00zMPMt1EdyRPtFYRAKVDg">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_LE8eYMt_EdyRPtFYRAKVDg"
+ name="Role Assignments" guid="_LE8eYMt_EdyRPtFYRAKVDg">
+ <contentElements xsi:type="org.eclipse.epf.uma:Role" xmi:id="_NuLxgMt_EdyRPtFYRAKVDg"
+ name="developer.assign_wp" guid="_NuLxgMt_EdyRPtFYRAKVDg" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Role" href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
+ <responsibleFor xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_kh9FcJ02EdyQ3oTO93enUw"/>
+ <responsibleFor xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_JqYbgJ01EdyQ3oTO93enUw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_qfziwMt_EdyRPtFYRAKVDg"
+ name="implement_developer_tests.assign_role" guid="_qfziwMt_EdyRPtFYRAKVDg"
+ variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Task" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_znlIcJR9EdyVKbgqUOtqQA"/>
+ <performedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0ZM4MclgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_yJ7V0Mt_EdyRPtFYRAKVDg"
+ name="implement_solution.assign_role" guid="_yJ7V0Mt_EdyRPtFYRAKVDg"
+ variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Task" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_Ht-z8JfJEdyZkIR-s-Y8wQ"/>
+ <performedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_dTa6gMAYEdqX-s4mWhkyqQ"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0ZM4MclgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_0RpQQMt_EdyRPtFYRAKVDg"
+ name="run_developer_tests.assign_role" guid="_0RpQQMt_EdyRPtFYRAKVDg"
+ variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Task" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_R7atwJfIEdyZkIR-s-Y8wQ"/>
+ <performedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_00zMPct1EdyRPtFYRAKVDg"
+ name="CapabilityPatterns" guid="_00zMPct1EdyRPtFYRAKVDg"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_00zMPst1EdyRPtFYRAKVDg"
+ name="DeliveryProcesses" guid="_00zMPst1EdyRPtFYRAKVDg"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_00zMP8t1EdyRPtFYRAKVDg"
+ name="ProcessContributions" guid="_00zMP8t1EdyRPtFYRAKVDg"/>
+ <bases href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPloEFXEdy9ENCpSugIjA"/>
+ <bases href="uma://_A118oMYaEdyXeo04os5BOw#_A118oMYaEdyXeo04os5BOw"/>
+ <bases href="uma://_fRdVEMYbEdyXeo04os5BOw#_fRdVEMYbEdyXeo04os5BOw"/>
+ <bases href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rEI7-Edy7q8CKc_B8eg"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/practice.tech.test_driven_development.base/.project b/praclib/temp/practice.tech.test_driven_development.base/.project
new file mode 100644
index 0000000..a06886a
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>practice.tech.test_driven_development.base</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/bookc.gif b/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/bookc.gif
new file mode 100644
index 0000000..7f2ab85
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/bookc.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/bookcL.gif b/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/bookcL.gif
new file mode 100644
index 0000000..6c5b064
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/bookcL.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/compass.gif b/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/compass.gif
new file mode 100644
index 0000000..39f306a
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/compass.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/compassL.gif b/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/compassL.gif
new file mode 100644
index 0000000..4117414
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/compassL.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/pract_dgm32.gif b/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/pract_dgm32.gif
new file mode 100644
index 0000000..f597332
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/pract_dgm32.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/pract_obj.gif b/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/pract_obj.gif
new file mode 100644
index 0000000..fe8075a
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/pract_obj.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/task_dgm32.gif b/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/task_dgm32.gif
new file mode 100644
index 0000000..a91ea1c
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/task_dgm32.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/task_obj.gif b/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/task_obj.gif
new file mode 100644
index 0000000..7633d58
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/task_obj.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/toolment_lg_dgm32.gif b/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/toolment_lg_dgm32.gif
new file mode 100644
index 0000000..c6c0098
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/toolment_lg_dgm32.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/toolment_obj.gif b/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/toolment_obj.gif
new file mode 100644
index 0000000..ed4c89a
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/toolment_obj.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/workproduct_dgm32.gif b/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/workproduct_dgm32.gif
new file mode 100644
index 0000000..009c9af
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/workproduct_dgm32.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/workproduct_obj.gif b/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/workproduct_obj.gif
new file mode 100644
index 0000000..3e58c6f
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/customcategories/resources/workproduct_obj.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.test_driven_development.base/customcategories/test_driven_dev_practice.xmi b/praclib/temp/practice.tech.test_driven_development.base/customcategories/test_driven_dev_practice.xmi
new file mode 100644
index 0000000..7a59a49
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/customcategories/test_driven_dev_practice.xmi
@@ -0,0 +1,51 @@
+<?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="-P_LlxVe57r9XOTpngB2ddQ"
+ name="test_driven_dev_practice,_dLtGEJ-mEdyBk-WQzMU-FQ" guid="-P_LlxVe57r9XOTpngB2ddQ"
+ authors="Jim Ruehlin" changeDate="2008-01-17T13:22:16.622-0800" version="7.2.0">
+ <mainDescription><p>
+ The Test Driven Development practice reduces time to market by reducing the amount of time needed to integrate and
+ stabilize builds. It improves productivity by finding and fixing errors close to the time they're introduced. And it
+ increases the overall quality of the software by guaranteeing all new code has been tested, and all existing code has
+ 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"
+ href="./../../practice.tech.test_driven_development.base/workproducts/developer_test_6A91CE05.html"
+ guid="_kh9FcJ02EdyQ3oTO93enUw">Developer Test</a>s.
+</p>
+<p>
+ TDD has&nbsp;a simple flow: Create a new test to validate a planned change/addition to the software. Run the test to
+ perform a sanity check - it should fail since no software has been written for it yet. Make a small change, refactor
+ the code,&nbsp;and run the test. Keep changing/refactoring/testing until the test passes and the code is in a robust,
+ well-factored state. Then begin the cycle again on a new small piece of the solution.
+</p>
+<p>
+ <img style="WIDTH: 281px; HEIGHT: 356px" height="259" src="http://www.agiledata.org/images/tddSteps.jpg" width="171"
+ border="0" /><br />
+</p><br />
+<p>
+ <strong>TDD Practice Information</strong>
+</p>
+<p>
+ See the <a class="elementLink"
+ href="./../../practice.tech.test_driven_development.base/guidances/roadmaps/tdd_practice_roadmap_7D642D12.html"
+ guid="_8yG48JRqEdyrdaw_xGakyw">How to Adopt the Test Driven Development Practice</a>&nbsp;for information on navigating
+ the TDD Practice.
+</p>
+<p>
+ <strong>History</strong>
+</p>
+<p>
+ TDD was originally part of Kent Beck's Extreme Programming process. It's now also used in many other Agile and
+ non-Agile contexts.
+</p></mainDescription>
+ <keyConsiderations>See&nbsp;<a class="elementLink"
+href="./../../practice.tech.test_driven_development.base/guidances/supportingmaterials/measurementsz_C281C60E.html"
+guid="_ApBRYMVFEdybJe13vGdZaA">Measurementsz</a>&nbsp;for information on adopting and measuring the team's capabilities in
+test driven development.</keyConsiderations>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.test_driven_development.base/guidances/checklists/implementation.xmi b/praclib/temp/practice.tech.test_driven_development.base/guidances/checklists/implementation.xmi
new file mode 100644
index 0000000..20fef1d
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/guidances/checklists/implementation.xmi
@@ -0,0 +1,70 @@
+<?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"
+ name="new_checklist,_OhJKUNWsEduaE6F4-SvXzg" guid="-cev1w72zE7XqPYsSv19prg" changeDate="2007-07-25T12:48:32.932-0700"
+ version="1.0.0">
+ <mainDescription><p>
+ The items in this checklist represent good practices for creating a high-quality implementation. Try to address every
+ item to the greatest extent possible to create the best implementation. 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>
+ This checklist is not something that should be considered only for heavyweight code reviews. Each developer should keep
+ the quality criteria embodied in these check items in mind while coding. When developers work together, the review
+ against these criteria should be done in real time so that quality is ensured up front as they are writing the code.
+</p>
+<p>
+ 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?"
+ 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>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_etwutJ01EdyQ3oTO93enUw" name="Is the implementation testable?"
+ guid="_etwutJ01EdyQ3oTO93enUw">
+ <sectionDescription><ul>
+ <li>
+ Can you test the expected behavior at the unit level?
+ </li>
+ <li>
+ Is the code written in a way that all paths can be exercised?
+ </li>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_etwutZ01EdyQ3oTO93enUw" name="Is the implementation correct?"
+ guid="_etwutZ01EdyQ3oTO93enUw">
+ <sectionDescription><ul>
+ <li>
+ Does the implementation pass all of the developer tests?
+ </li>
+ <li>
+ Does the implementation support the acceptance criteria of the test cases?
+ </li>
+ <li>
+ Is all code executable (no dead code areas)?
+ </li>
+</ul></sectionDescription>
+ </sections>
+ <sections xmi:id="_etwus501EdyQ3oTO93enUw" name="Is the implementation understandable?"
+ guid="_etwus501EdyQ3oTO93enUw">
+ <sectionDescription><p>
+ Is there no redundancy in the implementation? (Identify candidates for refactoring.)
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_etwusp01EdyQ3oTO93enUw" name="Is there no redundancy?" guid="_etwusp01EdyQ3oTO93enUw">
+ <sectionDescription><p>
+ Is there no redundancy in the implementation? (Identify candidates for refactoring.)
+</p></sectionDescription>
+ </sections>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/coding_standard.xmi b/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/coding_standard.xmi
new file mode 100644
index 0000000..d8ffea5
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/coding_standard.xmi
@@ -0,0 +1,58 @@
+<?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="-xo5gft-2zQGWhxjKcGxSQQ"
+ name="new_concept,_0lnRMMqOEduwrYVlQ9zp3w" guid="-xo5gft-2zQGWhxjKcGxSQQ" changeDate="2008-01-08T17:21:22.030-0800"
+ version="1.0.0">
+ <mainDescription><p>
+ Using a coding standard is a widely accepted software development practice. The need for this practice takes on added
+ importance in a highly collaborative environment. The team should have a standard way of naming and formatting things
+ so they can understand the code quickly and know where to look at all times. This enables shared code ownership since
+ any team member should be able to quickly understand the code written by others.&nbsp;
+</p>
+<p>
+ Ideally, the coding standard should be the result of team consensus. Involving the team members will aid adoption of
+ the standards.
+</p>
+<p>
+ Coding Standards cover such areas as:
+</p>
+<ul>
+ <li>
+ Naming standards. This includes the naming of elements all the way down to the smallest variable. In covering
+ larger-scale elements, this overlaps into what could be considered design standards.
+ </li>
+ <li>
+ File organization. This includes file naming conventions and how the files will be organized on the file system.
+ </li>
+ <li>
+ Comment standards. Too much emphasis on comments implies a lack of confidence that readable code is being written,
+ plus there is always a concern that the comments are not up to date. Yet, a consistent approach to comments
+ improves understandability and can support the ability to generate documentation from the code.
+ </li>
+ <li>
+ Coding conventions. Consistent application of specific code-level conventions and the exclusion of some considered
+ poor form improve the quality of the code.
+ </li>
+ <li>
+ White space. Though it can be argued to be less critical than the other items listed here, a consistent usage of
+ white space as indentation and blank lines also improves readability.
+ </li>
+</ul>
+<p>
+ In some cases, decisions will be arbitrary (like how much to indent). Each item in the standard should support one or
+ more goals, improved communication being one of the most critical goals. Once the team agrees on a standard, all
+ members of the teams are expected to follow it. With time, the team will use and modify the standard to develop a style
+ that is well adapted to the environment.
+</p>
+<p>
+ Though some standards can transcend any language, coding standards must be language specific for the most part.
+</p>
+<p>
+ For example coding standards, see the <a href="http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html"
+ target="_blank">Code Conventions for the JavaTM Programming Language</a> or these <a
+ href="http://blogs.msdn.com/brada/articles/361363.aspx" target="_blank">Internal Coding Guidelines</a> for .NET
+ development.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/collective_code_ownership.xmi b/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/collective_code_ownership.xmi
new file mode 100644
index 0000000..5a8b47e
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/collective_code_ownership.xmi
@@ -0,0 +1,26 @@
+<?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="-ykYi7xrRdC5O9qFXhU3doA"
+ name=",_xYMPoCZnEdyUaK463Ozu5g" guid="-ykYi7xrRdC5O9qFXhU3doA" changeDate="2008-01-16T12:27:16.541-0800">
+ <mainDescription><p>
+ With collective code ownership, any member of the team can change any piece of code in the system at any time. There
+ should not be a policy or norm that one person is responsible for one part of the code base so that others are not
+ allowed to modify it.
+</p>
+<p>
+ Fostering an environment where any developer might be expected to modify any piece of code to implement some
+ functionality, fix a bug, or improve the solution leads to a more collaborative team experience. Developers will become
+ familiar with more of the code and benefit from the experience of others. It drives a high-performance team and removes
+ hurdles so that changes can be made by those who need them when they need them. No one person can become the gatekeeper
+ or bottleneck for changes to some subsystem within the code base.
+</p>
+<p>
+ Collective code ownership works best if there are coding standards in place so that there are not problems, where one
+ developer's style is significantly different than another's (see <a class="elementLinkWithType"
+ href="./../../../practice.tech.test_driven_development.base/guidances/concepts/coding_standard_1FF691E0.html"
+ guid="_aGqAsJ01EdyQ3oTO93enUw">Concept: Coding Standard</a>). It is also critical that there are developer tests in
+ place to ensure that work on a unit of code does not break it.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/developer_testing.xmi b/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/developer_testing.xmi
new file mode 100644
index 0000000..2faef9b
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/developer_testing.xmi
@@ -0,0 +1,125 @@
+<?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="-EOoqKeF2SEXao6XhNXBD-w"
+ name=",_ADwlAJRtEdyrdaw_xGakyw" guid="-EOoqKeF2SEXao6XhNXBD-w" changeDate="2008-02-01T10:58:53.742-0800"
+ version="7.2.0">
+ <mainDescription><p>
+ Developer testing is the act of regression testing source code by developers. This is sometimes called "unit regression
+ testing" but many developer tests go beyond unit testing to address integration testing as well.
+</p>
+<h3>
+ Testing Philosophies
+</h3>
+<p>
+ Here are some important philosophies with regard to developer testing:
+</p>
+<ol>
+ <li>
+ The goal is to find defects. Successful tests find bugs, but correcting the bugs falls into other areas.
+ </li>
+ <li>
+ Test early and often. The cost of change rises exponentially the longer it takes to find and then remove a defect.
+ The implication is that you want to test as early as possible (the earliest you could possibly test is first, see
+ <a class="elementLinkWithType"
+ href="./../../../practice.tech.test_driven_development.base/guidances/guidelines/test_driven_development_F581182D.html"
+ guid="_5s_DUJ03EdyQ3oTO93enUw">Guideline: Test Driven Development</a>).
+ </li>
+ <li>
+ Testing builds confidence. Many people fear making a change to their code because they are afraid that they will
+ break it, but with a full test suite in place if you do break something you know you will detect it and then fix
+ it.
+ </li>
+ <li>
+ One test is worth a thousand opinions. You can say that your application works, but until you show the test results
+ 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.
+ </li>
+ <li>
+ You can validate all artifacts. You can test all your artifacts, not just your source code, although the focus of
+ this guidance is testing code.
+ </li>
+</ol>
+<h3>
+ Qualities of a Good Developer Test
+</h3>These are the qualities of a good developer test: 
+<ul class="noindent">
+ <li>
+ It runs fast. It has short setup, run time, and clean-up.
+ </li>
+ <li>
+ It runs in isolation. You should be able to reorder your tests.
+ </li>
+ <li>
+ It is understandable. Good tests have consistent and informative names and use data that makes them easy to read
+ and to understand.
+ </li>
+ <li>
+ It uses real data. For example, use copies of production data when appropriate, but remember that you'll typically
+ have to create some specific "artificial" test data as well.
+ </li>
+ <li>
+ It is minimally cohesive. The test represents one step toward your overall goal. The test should address one and
+ one only issue.
+ </li>
+</ul>
+<h3>
+ Approaches for Test Setup
+</h3>
+<p>
+ To successfully run a test, the system must be in a known state. To do this you will need objects or components in
+ memory, rows in the database, etc. that you will test against. The easiest approach is to hardcode the required data
+ and the setup code within the test itself. The primary advantage is that all the information that you need about the
+ test is in one place and that the test is potentially self-sufficient.
+</p>
+<p>
+ Another approach is to define an external data set which is loaded into memory or into the database at the beginning of
+ the test run. There are several advantages to this approach:
+</p>
+<ul>
+ <li>
+ It decouples the test data from the test.
+ </li>
+ <li>
+ More than one test can use the same data set.
+ </li>
+ <li>
+ It is easy to modify and/or multiply the test data.
+ </li>
+</ul>
+<p>
+ There are some disadvantages to this approach:
+</p>
+<ul>
+ <li>
+ Increased complexity for maintaining the external data
+ </li>
+ <li>
+ Potential coupling between test cases. When they share a common test data bed it becomes very easy to write tests
+ that depend on other tests running first, thereby coupling them together.
+ </li>
+</ul>
+<h3>
+ Coding for Testability
+</h3>
+<p>
+ Add&nbsp;<a class="elementLink"
+ href="./../../../practice.tech.test_driven_development.base/guidances/termdefinitions/code_instrumentation_3060875F.html"
+ guid="_lzAWkK9eEdyltJ0KgEd9WQ">code instrumentation</a> for testing and debugging. Pay special attention to the
+ implementation of the observation/control points, such as critical functions or objects, as these aspects might need
+ special support that has to be implemented in the iunder test.
+</p>
+<h3>
+ Reviewing Tests
+</h3>
+<p>
+ If a test will be long-lived, ask a person with less inside knowledge of the implementation element to run it and check
+ if there is enough support information. Review it with other people within the development team and other interested
+ parties as needed.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/resources/code_instrumentation_E6BE9793.html b/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/resources/code_instrumentation_E6BE9793.html
new file mode 100644
index 0000000..2daaaff
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/resources/code_instrumentation_E6BE9793.html
@@ -0,0 +1,79 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN""http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en" xml:lang="en" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
+<head>
+<META http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>Term Definition: code instrumentation</title>
+<meta name="uma.type" content="TermDefinition">
+<meta name="uma.name" content="code_instrumentation">
+<meta name="uma.presentationName" content="code instrumentation">
+<meta name="element_type" content="other">
+<meta name="filetype" content="description">
+<meta name="role" content="">
+<link rel="StyleSheet" href="./../../../css/default.css" type="text/css">
+<script src="./../../../scripts/ContentPageResource.js" type="text/javascript" language="JavaScript"></script><script src="./../../../scripts/ContentPageSection.js" type="text/javascript" language="JavaScript"></script><script src="./../../../scripts/ContentPageSubSection.js" type="text/javascript" language="JavaScript"></script><script src="./../../../scripts/ContentPageToolbar.js" type="text/javascript" language="JavaScript"></script><script src="./../../../scripts/contentPage.js" type="text/javascript" language="JavaScript"></script><script type="text/javascript" language="JavaScript">
+ var backPath = './../../../';
+ var imgPath = './../../../images/';
+ var nodeInfo=null;
+ contentPage.preload(imgPath, backPath, nodeInfo, '', false, false, false);
+ </script>
+</head>
+<body>
+<div id="breadcrumbs"></div>
+<table border="0" cellpadding="0" cellspacing="0" width="100%">
+<tr>
+<td valign="top"><a name="Top"></a>
+<div id="page-guid" value="_JiqnEJt1EdutoZjlV3a4Lg"></div>
+<table border="0" cellspacing="0" cellpadding="0" width="100%">
+<tr>
+<td class="pageTitle" nowrap="true">Term Definition: code instrumentation</td><td width="100%">
+<div align="right" id="contentPageToolbar"></div>
+</td><td width="100%" class="expandCollapseLink" align="right"><a name="mainIndex" href="./../../../index.htm"></a><script language="JavaScript" type="text/javascript" src="./../../../scripts/treebrowser.js"></script></td>
+</tr>
+</table>
+<table width="100%" border="0" cellpadding="0" cellspacing="0">
+<tr>
+<td class="pageTitleSeparator"><img src="./../../../images/shim.gif" alt="" title="" height="1"></td>
+</tr>
+</table>
+<div class="overview">
+<table width="97%" border="0" cellspacing="0" cellpadding="0">
+<tr>
+<td>
+<table class="overviewTable" border="0" cellspacing="0" cellpadding="0">
+<tr>
+<td valign="top"></td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Main Description</div>
+<div class="sectionContent">
+<table class="sectionTable" border="0" cellspacing="0" cellpadding="0">
+<tr valign="top">
+<td class="sectionTableSingleCell"><p>
+ "Extra" statements added to source code for the purposes of testing, debugging, tuning, or tracing.
+</p></td>
+</tr>
+</table>
+</div>
+<table class="copyright" border="0" cellspacing="0" cellpadding="0">
+<tr>
+<td class="copyright"><p>
+ This program and the accompanying materials are made available under the<br />
+ <a href="http://www.eclipse.org/org/documents/epl-v10.php" target="_blank">Eclipse Public License v1.0</a> which
+ accompanies this distribution.
+</p><p/><p>
+ <a class="elementLink" href="./../../../openup/guidances/supportingmaterials/openup_copyright_C3031062.html" guid="_UaGfECcTEduSX6N2jUafGA">OpenUP Copyright</a>.
+</p></td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+</body>
+<script type="text/javascript" language="JavaScript">
+ contentPage.onload();
+ </script>
+</html>
diff --git a/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/resources/design_subsystem_B26FD609.html b/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/resources/design_subsystem_B26FD609.html
new file mode 100644
index 0000000..d10767a
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/resources/design_subsystem_B26FD609.html
@@ -0,0 +1,579 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" lang="en" xml:lang="en">
+<head>
+<META http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>Guideline: Design Subsystem</title>
+<meta content="Guideline" name="uma.type">
+<meta content="design_subsystem" name="uma.name">
+<meta content="Design Subsystem" name="uma.presentationName">
+<meta name="element_type" content="other">
+<meta content="description" name="filetype">
+<meta name="role" content="">
+<link type="text/css" href="./../../../css/default.css" rel="StyleSheet">
+<script language="JavaScript" type="text/javascript" src="./../../../scripts/ContentPageResource.js"></script><script language="JavaScript" type="text/javascript" src="./../../../scripts/ContentPageSection.js"></script><script language="JavaScript" type="text/javascript" src="./../../../scripts/ContentPageSubSection.js"></script><script language="JavaScript" type="text/javascript" src="./../../../scripts/ContentPageToolbar.js"></script><script language="JavaScript" type="text/javascript" src="./../../../scripts/contentPage.js"></script><script language="JavaScript" type="text/javascript">
+ var backPath = './../../../';
+ var imgPath = './../../../images/';
+ var nodeInfo=[{view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_f6_YwN7DEdmsEI4YDGX2ag", "_qwxC8N7YEdmjRZts2c4ZjQ", "{DB21F5EF-810B-4994-B120-79FA8774FA9D}", "1.2314266786534317E-305"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_Jvt1cAIaEdqEutyfYo0quQ", "_jijhYAIaEdqEutyfYo0quQ", "_n7ZcgN7REdmjRZts2c4ZjQ", "{A3C60B25-9780-4BFA-81AF-C1AD40D8A833}", "1.2314266786534317E-305"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_jD8dUAIbEdqEutyfYo0quQ", "_2ClPcDIcEdqDs_9ORT1Rig", "1.2314266786534317E-305"]}, {view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_zRigkAILEdq-_NKqZM1EhA", "_qwxC8N7YEdmjRZts2c4ZjQ", "{DB21F5EF-810B-4994-B120-79FA8774FA9D}", "1.2314266786534317E-305"]}];
+ contentPage.preload(imgPath, backPath, nodeInfo, '', false, false, false);
+ </script>
+</head>
+<body>
+<div id="breadcrumbs"></div>
+<table width="100%" cellspacing="0" cellpadding="0" border="0">
+<tr>
+<td valign="top"><a name="Top"></a>
+<div id="page-guid" value="1.2314266786534317E-305"></div>
+<table width="100%" cellpadding="0" cellspacing="0" border="0">
+<tr>
+<td nowrap="true" class="pageTitle">Guideline: Design Subsystem</td><td width="100%">
+<div id="contentPageToolbar" align="right"></div>
+</td>
+</tr>
+</table>
+<table cellspacing="0" cellpadding="0" border="0" width="100%">
+<tr>
+<td class="pageTitleSeparator"><img height="1" title="" alt="" src="./../../../images/shim.gif"></td>
+</tr>
+</table>
+<div class="overview">
+<table cellpadding="0" cellspacing="0" border="0" width="97%">
+<tr>
+<td width="50"><img title="" alt="" src="./../../../images/guidance.gif"></td><td>
+<table cellpadding="0" cellspacing="0" border="0" class="overviewTable">
+<tr>
+<td valign="top">A Design Subsystem implements the concept of Software Component. This guideline explains how to identify and specify Design Subsystems.</td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Relationships</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Related Elements</th><td class="sectionTableCell">
+<ul>
+<li>
+<a href="./../../../core.base_rup/workproducts/rup_design_subsystem_1A8D169B.html" guid="{A3C60B25-9780-4BFA-81AF-C1AD40D8A833}">Design Subsystem</a>
+</li>
+<li>
+<a href="./../../../core.base_rup/roles/rup_designer_BA8DE74E.html" guid="{DB21F5EF-810B-4994-B120-79FA8774FA9D}">Designer</a>
+</li>
+</ul>
+</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Main Description</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<td class="sectionTableSingleCell"><a id="Top" name="Top"></a><a id="XE_layering__layering_guidelines_for_design_subsystems" name="XE_layering__layering_guidelines_for_design_subsystems"></a><a id="XE_design_subsystem__guidelines_for" name="XE_design_subsystem__guidelines_for"></a>
+<h3>
+ <a id="XE_design_subsystem__partitioning_patterns" name="XE_design_subsystem__partitioning_patterns"></a><a id="Subsystem Usage" name="Subsystem Usage">Subsystem Usage</a>
+</h3>
+<p>
+ <a id="XE_layering__partitioning_patterns" name="XE_layering__partitioning_patterns"></a>Subsystems can be used in a
+ number of complementary ways, to partition the system into units which
+</p>
+<ul>
+ <li>
+ can be independently ordered, configured, or delivered
+ </li>
+ <li>
+ can be independently developed, as long as the interfaces remain unchanged
+ </li>
+ <li>
+ can be independently deployed across a set of distributed computational nodes
+ </li>
+ <li>
+ can be independently changed without breaking other parts of the systems
+ </li>
+</ul>
+<p>
+ Thus, subsystems are ideal for modeling components - the replaceable units of assembly in component-based development -
+ that are larger than a single design class.
+</p>
+<p>
+ In addition, subsystems can
+</p>
+<ul>
+ <li>
+ partition the system into units which can provide restricted security over key resources
+ </li>
+ <li>
+ represent existing products or external systems in the design.
+ </li>
+</ul>
+<h3>
+ <a id="XE_design_subsystem__identifying_subsystems" name="XE_design_subsystem__identifying_subsystems"></a><a id="Identifying Subsystems" name="Identifying Subsystems">Identifying Subsystems</a>
+</h3>
+<p>
+ A complex analysis class is mapped to a design subsystem if it appears to embody behavior that cannot be the
+ responsibility of a single design class acting alone. A complex design class may also become a subsystem, if it is
+ likely to be implemented as a set of collaborating classes.
+</p>
+<p>
+ Subsystems are also a good means of identifying parts of the system that are to be developed independently by a
+ separate team. If the collaborating design elements can be completely contained within a package along with their
+ collaborations, a subsystem can provide a stronger form of encapsulation than that provided by a simple package. The
+ contents and collaborations within a subsystem are completely isolated behind one or more interfaces, so that the
+ client of the subsystem is only dependent upon the interface. The designer of the subsystem is then completely isolated
+ from external dependencies; the designer (or design team) is required to specify how the interface is realized, but
+ they are completely free to change the internal subsystem design without affecting external dependencies. In large
+ systems with largely independent teams, this degree of de-coupling combined with the architectural enforcement provided
+ by formal interfaces is a strong argument for the choice of subsystems over simple packages.
+</p>
+<p>
+ The design subsystem is used to encapsulate these collaborations in such a way that clients of the subsystem can be
+ completely unaware of the internal design of the subsystem, even as they use the services provided by the subsystem. If
+ the participating classes/subsystems in a collaboration interact only with each other to produce a well-defined set of
+ results, the collaboration and its collaborating design elements should be encapsulated within a subsystem.
+</p>
+<p>
+ This rule can be applied to subsets of collaborations as well. Anywhere part or all of a collaboration can be
+ encapsulated and simplified, doing so will make the design easier to understand.
+</p>
+<h4>
+ Hints
+</h4>
+<div align="center">
+ <table style="BORDER-RIGHT: rgb(128,128,128) 1px solid; BORDER-TOP: rgb(128,128,128) 1px solid; BORDER-LEFT: rgb(128,128,128) 1px solid; BORDER-BOTTOM: rgb(128,128,128) 1px solid" cellspacing="0" bordercolordark="#808080" cellpadding="4" width="85%" bordercolorlight="#808080" border="1">
+ <tbody>
+ <tr>
+ <th id="row0" scope="col" width="35%">
+ <blockquote>
+ <p class="tableheading" align="center">
+ Hint
+ </p>
+ </blockquote>
+ </th>
+ <td scope="col" headers="row0" width="65%">
+ <p class="tableheading" align="center">
+ Details
+ </p>
+ </td>
+ </tr>
+ <tr>
+ <th id="row1" width="35%">
+ Look for optionality
+ </th>
+ <td headers="row1" width="60%">
+ If a particular collaboration (or sub-collaboration) represents optional behavior, enclose it in a
+ subsystem. Features which may be removed, upgraded, or replaced with alternatives should be considered
+ independent.
+ </td>
+ </tr>
+ <tr>
+ <th id="row2" width="35%" rowspan="2">
+ Look to the user interface of the system.
+ </th>
+ <td headers="row2" width="60%">
+ If the user interface is relatively independent of the entity classes in the system (i.e. the two can
+ and will change independently), create subsystems which are horizontally integrated: group related user
+ interface boundary classes together in a subsystem, and group related entity classes together in
+ another subsystem.
+ </td>
+ </tr>
+ <tr>
+ <td headers="row2" width="65%">
+ If the user interface and the entity classes it displays are tightly coupled (i.e. a change in one
+ triggers a change in the other), create subsystems which are vertically integrated: enclose related
+ boundary and entity classes in common subsystem.
+ </td>
+ </tr>
+ <tr>
+ <th id="row3" width="35%" rowspan="2">
+ Look to the Actors
+ </th>
+ <td headers="row3" width="65%">
+ Separate functionality used by two different actors, since each actor may independently change their
+ requirements on the system.
+ </td>
+ </tr>
+ <tr>
+ <td headers="row3" width="65%">
+ Create subsystems to encapsulate access to an external system or device.
+ </td>
+ </tr>
+ <tr>
+ <th id="row5" width="35%">
+ Look for coupling and cohesion between design elements
+ </th>
+ <td headers="row5" width="65%">
+ Highly coupled or cohesive classes/subsystems collaborate to provide some set of services. Organize
+ highly coupled elements into subsystems, and separate elements along lines of weak coupling. In some
+ cases, weak coupling can be eliminated entirely by splitting classes into smaller classes with more
+ cohesive responsibilities, or repartitioning subsystems appropriately.
+ </td>
+ </tr>
+ <tr>
+ <th id="row6" width="35%">
+ Look at substitution
+ </th>
+ <td headers="row6" width="65%">
+ If there are several levels of service specified for a particular capability (example: high, medium and
+ low availability), represent each service level as a separate subsystem, each of which will realize the
+ same set of interfaces. By doing so, the subsystems are substitutable for one another.
+ </td>
+ </tr>
+ <tr>
+ <th id="row7" width="35%">
+ Look at distribution
+ </th>
+ <td headers="row7" width="65%">
+ <span style="mso-fareast-font-family: Times New Roman; mso-bidi-font-family: Times New Roman; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: HE">Although
+ there can be multiple instances of a particular subsystem, each executing on different nodes, in many
+ architectures it is not possible for a single instance of a component to be split across nodes. In the
+ cases where subsystem behavior must be split across nodes, it is recommended that you decompose the
+ subsystem into smaller subsystems (each representing a single component) with more restricted
+ functionality. <span style="mso-fareast-font-family: Times New Roman; mso-bidi-font-family: Times New Roman; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: HE; mso-spacerun: yes"> </span>
+ Determine the functionality that must reside upon each node and create a new subsystem to 'own' that
+ functionality, distributing the responsibilities and related elements of the original subsystem
+ appropriately. <span style="mso-fareast-font-family: Times New Roman; mso-bidi-font-family: Times New Roman; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: HE; mso-spacerun: yes"> </span>
+ The new subsystems are internal to the original subsystem.</span>
+ </td>
+ </tr>
+ </tbody>
+ </table><br />
+</div>
+<p>
+ Once the design has been organized into subsystems, update the use-case realizations accordingly.
+</p>
+<h3>
+ <a id="Modeling Subsystems" name="Modeling Subsystems">Modeling Subsystems</a>
+</h3>
+<p>
+ Design Subsystems are modeled using UML components. This construct provides the following modeling capabilities:
+</p>
+<ul>
+ <li>
+ can group classes to define a larger granularity part of a system
+ </li>
+ <li>
+ can separate the visible interfaces from internal implementation
+ </li>
+ <li>
+ can have execution at run-time
+ </li>
+</ul>
+<p>
+ Some other considerations are:
+</p>
+<ul>
+ <li>
+ Each Design Subsystem must be given a name and a short description.
+ </li>
+ <li>
+ The responsibilities of the original analysis class should be transferred to the newly-created subsystem, using the
+ description of the subsystem to document the responsibilities
+ </li>
+</ul>
+<p>
+ Note: UML 2.0 also defines a stereotype for component named <<subsystem>>, indicating that this may be
+ used, for example, to represent large scale structures. A RUP Design Subsystem may or may not be a large scale
+ structure; both are Design Subsystems from the RUP perspective. This is an issue for the software architect to decide
+ (whether to choose for example to label components that are composed of components as <<subsystem>>).
+</p>
+<h3>
+ <a id="Subsystems That Represent Existing Products" name="Subsystems That Represent Existing Products">Subsystems That
+ Represent Existing Products</a> <a href="#Top"><img height="20" alt="To top of page" src="./../../../core.base_rup/resources/top.gif" width="26" border="0" /></a>
+</h3>
+<p>
+ Where an existing product is one that exports interfaces, i.e. operations (and perhaps <a class="elementLinkWithUserText" href="./../../../core.base_rup/guidances/termdefinitions/reception_E5EE6A47.html" guid="_yS_Rg9nmEdmO6L4XMImrsA"><b>receptions</b></a>), but otherwise keeps all details of implementation hidden, then
+ it may be modeled as a subsystem in the logical view. Examples of products the system uses that you may be able
+ to represent by a subsystem include:
+</p>
+<ul>
+ <li>
+ Communication software (middleware).
+ </li>
+ <li>
+ Database access support (RDBMS mapping support).
+ </li>
+ <li>
+ Application-specific products.
+ </li>
+</ul>
+<p>
+ Some existing products such as collections of types and data structures (e.g. stacks, lists, queues) may be better
+ represented as packages, because they reveal more than behavior, and it is the particular contents of the package that
+ are important and useful and not the package itself, which is simply a container.
+</p>
+<p>
+ Common utilities, such as math libraries, could be represented as subsystems, if they simply export interfaces, but
+ whether this is necessary or makes sense depends on the designer's judgment about the nature of the thing
+ modeled. Subsystems are object-oriented constructs (as they are modeled components): a subsystem can have
+ instances (if the designer so indicates). UML provides another way to model groups of global variables and procedures
+ in the <a class="elementLink" href="./../../../core.base_rup/guidances/termdefinitions/utility_5BFC0972.html" guid="_ybVVMNnmEdmO6L4XMImrsA">utility</a>, which is a stereotype of class - the utility has no instances.
+</p>
+<p>
+ When defining the subsystem to represent the product, also define one or more interfaces to represent the product
+ interfaces.
+</p>
+<h3>
+ <a id="Subsystem Dependency Restrictions" name="Subsystem Dependency Restrictions">Subsystem Dependency
+ Restrictions</a> <a href="#Top"><img height="20" alt="To top of page" src="./../../../core.base_rup/resources/top.gif" width="26" border="0" /></a>
+</h3>
+<p>
+ Design Subsystems (modeled as UML components) differ from packages in their semantics: a subsystem provides behavior
+ through one or more interfaces which it realizes. Packages provide no behavior; they are simply containers of things
+ which provide behavior.
+</p>
+<p>
+ The reason for using a subsystem instead of a package is that subsystems encapsulate their contents, providing behavior
+ only through their interfaces. The benefit of this is that, unlike a package, the contents and internal behaviors of a
+ subsystem can be changed with complete freedom so long as the subsystem's interfaces remain constant. Subsystems also
+ provide a 'replaceable design' element: any two <<realization>> components that realize the same interfaces
+ (or <<specification>> component) are interchangeable.
+</p>
+<p>
+ In order to ensure that subsystems are replaceable elements in the model, a few rules need to be enforced:
+</p>
+<ul>
+ <li>
+ A subsystem should minimize exposing of its contents. Ideally no element contained by a subsystem should have
+ 'public' visibility, and thus no element outside the subsystem depends on the existence of a particular element
+ inside the subsystem. Some exceptions are as follows:
+ <ul>
+ <li>
+ In some technologies, the externals of a subsystem cannot be modeled as a UML interface. For example, a
+ Java interface is modeled as a stereotyped class.
+ </li>
+ <li>
+ The subsystem design may require exposing classes rather than UML interfaces. For example, a "delegate" or
+ "access" class can be used to hide a complex collaboration of other classes. While an ordinary package
+ could be used instead, a subsystem could be used in order to emphasize the intent to encapsulate behavior
+ and hide internal details.
+ </li>
+ </ul>
+ </li>
+ <li style="LIST-STYLE-TYPE: none">
+ <br />
+ When a subsystem's externals are not UML interfaces, it is often helpful to have a diagram (for example named
+ "External View") that shows the visible elements of the subsystem.
+ </li>
+ <li>
+ A subsystem should define its dependencies on subsystem interfaces (and publicly visible elements of subsystem in
+ the exceptional cases described above). In addition, a number of subsystems may share a set of interfaces or class
+ definitions in common, in which case those subsystems 'import' the contents of the packages which contain the
+ common elements. This is more common with packages in lower layers in the architecture, to ensure that common
+ definitions of classes which must pass between subsystems are consistently defined.
+ </li>
+</ul>
+<p>
+ An example of Subsystem and Package dependencies is shown below:
+</p>
+<p align="center">
+ <img alt="Diagram described in accompanying text." src="./../../../core.base_rup/guidances/guidelines/resources/md_dsub2.jpg" />
+</p>
+<p class="picturetext">
+ Subsystem and Package Dependencies in the Design Model
+</p>
+<h3>
+ <a id="Subsystem Specification and Realization" name="Subsystem Specification and Realization">Subsystem Specification
+ and Realization</a><a href="#Top"><img height="20" alt="To top of page" src="./../../../core.base_rup/resources/top.gif" width="26" border="0" /></a>
+</h3>
+<h4>
+ <a id="Definition" name="Definition">Definition</a><a href="#Top"><img height="20" alt="To top of page" src="./../../../core.base_rup/resources/top.gif" width="26" border="0" /></a>
+</h4>
+<p>
+ The UML ([<a class="elementLinkWithUserText" href="./../../../core.base_rup/customcategories/references_56F06DFD.html#UML04" guid="7.755968586980351E-308">UML04</a>]) states:
+</p>
+<blockquote>
+ <p>
+ A number of UML standard stereotypes exist that apply to component, e.g. <<specification>> and
+ <<realization>> to model components with distinct specification and realization definitions, where one
+ specification may have multiple realizations.
+ </p>
+ <p>
+ A Component stereotyped by <<specification>> specifies a domain of objects without defining the
+ physical implementation of those objects. It will only have provided and required interfaces, and is not intended
+ to have any realizing classes and sub components as part of its definition.
+ </p>
+ <p>
+ A Component stereotyped by <<realization>> specifies a domain of objects and that also defines the
+ physical implementation of those objects. For example, a Component stereotyped by <<realization>> will
+ only have realizing classes and sub components that implement behavior specified by a separate
+ <<specification>> Component.
+ </p>
+</blockquote>
+<p>
+ The separation of specification and realization essentially allows for two separate descriptions of the subsystem. The
+ specification serves as a contract that defines everything that a client needs to know to use the subsystem. The
+ realization is the detailed internal design intended to guide the implementer. If you wish to support multiple
+ realizations, create separate "realization" subsystems, and draw a realization from each realization subsystem to the
+ specification subsystem.
+</p>
+<h4>
+ <a id="When and how to use" name="When and how to use">When and how to use</a>
+</h4>
+<p>
+ If the internal state and behavior of the subsystem is relatively simple, it may be sufficient to specify the subsystem
+ by its exposed interfaces, state diagrams to describe the behavior, and descriptive text.
+</p>
+<p>
+ For more complex internal state and behavior, analysis classes can be used to specify the subsystem at a high level of
+ abstraction. For large systems of systems, the specification of a subsystem may also include use cases. See <a class="elementLink" href="./../../../core.base_rup/guidances/whitepapers/developing_large-scale_systems_with_the_rational_unified_process_7AA2AF65.html" guid="1.768223108034868E-305">Developing Large-Scale Systems with the Rational Unified Process</a>.
+</p>
+<p>
+ Providing a detailed specification separate from the realization tends to be most useful in the following situations:
+</p>
+<ul>
+ <li>
+ the subsystem realization's internal state or behavior is complex - and the specification needs to be expressed as
+ simply as possible in order for clients to use it effectively;
+ </li>
+ <li>
+ the subsystem is a reusable "assembly component" intended for assembly into a number of systems (see <a class="elementLinkWithType" href="./../../../core.base_rup/guidances/concepts/component_A2E2B3B1.html" guid="3.524150980437479E-305">Concept: Component</a>);
+ </li>
+ <li>
+ the subsystem's internals are expected to be developed by a separate organization;
+ </li>
+ <li>
+ multiple implementations of the subsystem need to be created;
+ </li>
+ <li>
+ the subsystem is expected to be replaced with another version that has significant internal changes without changes
+ to the externally visible behavior.
+ </li>
+</ul>
+<p>
+ Maintaining a separate specification takes effort, however - as one must ensure that the realization of the subsystem
+ is compliant with the specification. The criteria for when and if to create separate specification and realization
+ classes and collaborations should be defined in <a class="elementLinkWithUserText" href="./../../../core.base_rup/workproducts/rup_project_specific_guidelines_8DC8DA32.html" guid="{E5501201-7EE6-4243-AE91-73880FF76FC1}">Work Product: Project Specific Guidelines.</a>
+</p>
+<h4>
+ <a id="Dependencies" name="Dependencies">Dependencies</a>
+</h4>
+<p>
+ A specification should define its dependencies. These are the interfaces and visible elements from other subsystems and
+ packages that must be available in all compliant realizations of the subsystem.
+</p>
+<p>
+ A realization may have additional dependencies, introduced by the designer or implementer. For example, there may be an
+ opportunity to use a utility component to simplify the implementation - but the use of this utility component is a
+ detail that need not be exposed to clients. These additional dependencies should be captured on a separate diagram as
+ part of the realization.
+</p>
+<h4>
+ <a id="Relationship to Implementation" name="Relationship to Implementation">Relationship to Implementation</a>
+</h4>
+<p>
+ A fully detailed specification defines everything a client needs to use the subsystem. This means refining the exposed
+ interfaces and any publicly visible elements so that they are one-to-one with code. Analysis classes introduced to
+ specify the subsystem behavior should remain as high level abstractions, since they are intended to be independent of
+ any subsystems realizations.
+</p>
+<p>
+ The realization elements of a subsystem should align closely to the code.
+</p>
+<p>
+ See <a class="elementLinkWithType" href="./../../../core.base_rup/guidances/concepts/mapping_from_design_to_code_D1454680.html" guid="1.424219730601675E-305">Concept: Mapping from Design to Code</a> for some further discussion on this topic.
+</p>
+<h3>
+ <a id="UML_1x_Representation" name="UML_1x_Representation">UML 1.x Representation</a>
+</h3>
+<h4>
+ Modeling
+</h4>
+<p>
+ Design subsystems may be modeled as either UML 2.0 components or UML 1.5 subsystems. These constructs provide almost
+ equivalent modeling capabilities like modularity, encapsulation, and instances able to execute at run-time.
+</p>
+<p>
+ Some additional considerations about these modeling options are:
+</p>
+<ul>
+ <li>
+ UML 1.5 subsystems explicitly included the notion of "specification" and "realization" (defined above in the
+ section titled <a href="#Subsystem Specification and Realization">Subsystem Specification and
+ Realization</a>). The UML 2.0 components support the notion of specification (in the form of one or more provided
+ and required interfaces) and realization (internal implementation consisting of one or more classes and sub
+ components that realize its behavior).
+ </li>
+ <li>
+ UML 1.5 subsystems were also packages. UML 2.0 components have packaging capabilities, which means they may own and
+ import a potentially large set of model elements.
+ </li>
+</ul>
+<p>
+ However, by and large, these notations can be used interchangeably. Whether to represent Design Subsystems as UML 1.5
+ subsystems or UML 2.0 components is a decision that should be documented in the <a class="elementLink" href="./../../../core.base_rup/workproducts/rup_project_specific_guidelines_8DC8DA32.html" guid="{E5501201-7EE6-4243-AE91-73880FF76FC1}">Project-Specific Guidelines</a> tailored for your project.
+</p>
+<p>
+ If your visual modeling tool supports UML 1.5 packages but not UML 1.5 subsystems, a package stereotyped as
+ <<subsystem>> can be used to denote a subsystem.
+</p>
+<h4>
+ Subsystem Dependency Restrictions
+</h4>
+<p>
+ The same dependency restrictions and discussions mentioned in the section titled <a href="#Subsystem Dependency Restrictions">Subsystem Dependency Restrictions</a> also apply for design subsystems
+ being modeled as UML 1.5 subsystems.
+</p>
+<p>
+ An example of Subsystem and Package dependencies in UML 1.5 is shown below:
+</p><br />
+<br />
+<p align="center">
+ <img height="240" alt="Diagram described in accompanying text." src="./../../../core.base_rup/guidances/guidelines/resources/md_dsub1.gif" width="370" />
+</p>
+<p class="picturetext">
+ Subsystem and Package Dependencies in the Design Model<br />
+ <br />
+</p>
+<h4>
+ Subsystem Specification and Realization
+</h4>The UML 1.5 stated:
+<blockquote>
+ <p>
+ The contents of a subsystem are divided into two subsets: 1) specification elements and 2) realization elements.
+ The specification elements, together with the operations and receptions of the subsystem, are used for giving an
+ abstract specification of the behavior offered by the realization elements. The collection of realization elements
+ model the interior of the behavioral unit of the physical system.
+ </p>
+</blockquote>
+<p>
+ The separation of specification and realization essentially allows for two separate descriptions of the subsystem. The
+ specification serves as a contract that defines everything that a client needs to know to use the subsystem. The
+ realization is the detailed internal design intended to guide the implementer.
+</p>
+<p>
+ One option for modeling specifications and realizations, if not directly supported by the modeling environment, is to
+ place two packages, specification and realization, inside each subsystem.
+</p>
+<p>
+ One motivation for specifications is to support multiple realizations. This was not directly supported in the UML 1.x.
+ If you wish to support multiple realizations using UML 1.5 subsystems, create separate "realization" subsystems, and
+ draw a realization from each realization subsystem to the specification subsystem.
+</p>
+<p>
+ Basically, the same considerations for Specification and Realization that apply for UML 2.0, also apply here (see <a href="#When and How to Use">When and How to Use</a>, <a href="#Dependencies">Dependencies</a>, and <a href="#Relationship to Implementation">Relationship to Implementation</a> for explanation).
+</p>
+<h4>
+ Additional Information
+</h4>
+<p>
+ Refer to <a class="elementLink" href="./../../../core.base_rup/guidances/supportingmaterials/differences_between_uml_1_x_and_uml_2_0_CA70F2E6.html" guid="4.792914878943572E-306">Differences Between UML 1.x and UML 2.0 </a> for more information.<br />
+ <br />
+</p></td>
+</tr>
+</table>
+</div>
+<table cellpadding="0" cellspacing="0" border="0" class="copyright">
+<tr>
+<td class="copyright"><p>
+ © Copyright IBM Corp. 1987, 2006. All Rights Reserved.
+</p></td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+</body>
+<script language="JavaScript" type="text/javascript">
+ contentPage.onload();
+ </script>
+</html>
diff --git a/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/resources/mapping_from_design_to_code_D1454680.html b/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/resources/mapping_from_design_to_code_D1454680.html
new file mode 100644
index 0000000..9682936
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/resources/mapping_from_design_to_code_D1454680.html
@@ -0,0 +1,211 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" lang="en" xml:lang="en">
+<head>
+<META http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>Concept: Mapping from Design to Code</title>
+<meta content="Concept" name="uma.type">
+<meta content="mapping_from_design_to_code" name="uma.name">
+<meta content="Mapping from Design to Code" name="uma.presentationName">
+<meta name="element_type" content="concept">
+<meta content="description" name="filetype">
+<meta name="role" content="">
+<link type="text/css" href="./../../../css/default.css" rel="StyleSheet">
+<script language="JavaScript" type="text/javascript" src="./../../../scripts/ContentPageResource.js"></script><script language="JavaScript" type="text/javascript" src="./../../../scripts/ContentPageSection.js"></script><script language="JavaScript" type="text/javascript" src="./../../../scripts/ContentPageSubSection.js"></script><script language="JavaScript" type="text/javascript" src="./../../../scripts/ContentPageToolbar.js"></script><script language="JavaScript" type="text/javascript" src="./../../../scripts/contentPage.js"></script><script language="JavaScript" type="text/javascript">
+ var backPath = './../../../';
+ var imgPath = './../../../images/';
+ var nodeInfo=[{view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_f6_YwN7DEdmsEI4YDGX2ag", "_qwxC8N7YEdmjRZts2c4ZjQ", "{75501BAA-0CCE-4852-A7B2-B10CA71C002A}", "1.424219730601675E-305"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_kC0pcN7GEdm8G6yT7-Wdqw", "_yd3ExNnmEdmO6L4XMImrsA", "1.424219730601675E-305"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_jD8dUAIbEdqEutyfYo0quQ", "_vzRNgDIcEdqDs_9ORT1Rig", "1.424219730601675E-305"]}, {view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_zRigkAILEdq-_NKqZM1EhA", "_qwxC8N7YEdmjRZts2c4ZjQ", "{75501BAA-0CCE-4852-A7B2-B10CA71C002A}", "1.424219730601675E-305"]}, {view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_zRigkAILEdq-_NKqZM1EhA", "_IY0NkAISEdqTna4sZVFRow", "_yd3ExNnmEdmO6L4XMImrsA", "1.424219730601675E-305"]}];
+ contentPage.preload(imgPath, backPath, nodeInfo, '', false, false, false);
+ </script>
+</head>
+<body>
+<div id="breadcrumbs"></div>
+<table width="100%" cellspacing="0" cellpadding="0" border="0">
+<tr>
+<td valign="top"><a name="Top"></a>
+<div id="page-guid" value="1.424219730601675E-305"></div>
+<table width="100%" cellpadding="0" cellspacing="0" border="0">
+<tr>
+<td nowrap="true" class="pageTitle">Concept: Mapping from Design to Code</td><td width="100%">
+<div id="contentPageToolbar" align="right"></div>
+</td>
+</tr>
+</table>
+<table cellspacing="0" cellpadding="0" border="0" width="100%">
+<tr>
+<td class="pageTitleSeparator"><img height="1" title="" alt="" src="./../../../images/shim.gif"></td>
+</tr>
+</table>
+<div class="overview">
+<table cellpadding="0" cellspacing="0" border="0" width="97%">
+<tr>
+<td width="50"><img title="" alt="" src="./../../../images/concept.gif"></td><td>
+<table cellpadding="0" cellspacing="0" border="0" class="overviewTable">
+<tr>
+<td valign="top">This guideline describes some different options for moving from a design to the implementation, and discusses the benefits and drawbacks of these approaches. </td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Relationships</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Related Elements</th><td class="sectionTableCell">
+<ul>
+<li>
+<a href="./../../../core.base_rup/disciplines/rup_implementation_discipline_263E22DB.html" guid="_yd3ExNnmEdmO6L4XMImrsA">Implementation</a>
+</li>
+<li>
+<a href="./../../../core.base_rup/roles/rup_implementer_D145E819.html" guid="{75501BAA-0CCE-4852-A7B2-B10CA71C002A}">Implementer</a>
+</li>
+</ul>
+</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Main Description</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<td class="sectionTableSingleCell"><a id="Top" name="Top"></a><a id="XE_code__mapping_from_design" name="XE_code__mapping_from_design"></a>
+<h3>
+ <b><a id="Introduction" name="Introduction">Introduction</a></b>
+</h3>
+<p>
+ Design must define enough of the system so that it can be implemented unambiguously. What constitutes enough varies
+ from project to project and company to company.
+</p>
+<p>
+ In some cases the design resembles a sketch, elaborated only far enough to ensure that the implementer can proceed (a
+ "sketch and code" approach). The degree of specification varies with the expertise of the implementer, the complexity
+ of the design, and the risk that the design might be misconstrued.
+</p>
+<p>
+ In other cases, the design is elaborated to the point that the design can be transformed automatically into code. This
+ typically involves extensions to standard UML to represent language and/or environment specific semantics.
+</p>
+<p>
+ The design may also be hierarchical, such as the following:
+</p>
+<ul>
+ <li>
+ a high level design model which sketches an overview of the overall system
+ </li>
+ <li>
+ a subsystem specification model which precisely specifies the required interfaces and behavior of major subsystems
+ within the system
+ </li>
+ <li>
+ a detailed design model for the internals of subsystems
+ </li>
+</ul>
+<p>
+ The <a class="elementLink" href="./../../../core.base_rup/workproducts/rup_development_case_F4260B3A.html" guid="{F071C3D3-7054-457F-8A81-EFA6678CCDE1}">Development Case</a> should define how the Design Model is realized in
+ the project's specific process, and how/if the model relates to other models and to the implementation. Details should
+ be captured in the <a class="elementLink" href="./../../../core.base_rup/workproducts/rup_project_specific_guidelines_8DC8DA32.html" guid="{E5501201-7EE6-4243-AE91-73880FF76FC1}">Project-Specific Guidelines</a>.
+</p>
+<p>
+ The sections below describe some different options for relating a design and implementation, and discuss benefits and
+ drawbacks of these approaches.
+</p>
+<h3>
+ <b><a id="sketch" name="sketch">Sketch and Code</a></b>
+</h3>
+<p>
+ One common approach to design is to sketch out the design at a fairly abstract level, and then move directly to code.
+ Maintenance of the design model is manual.
+</p>
+<p>
+ In this approach, we let a design class be an abstraction of several code-level classes. We recommend that you map each
+ design class to one "head" class that, in turn, can use several "helper" classes to perform its behavior. You can use
+ "helper" classes to implement a complex attribute or to build a data structure that you need for the implementation of
+ an operation. In design, you don't model the "helper" classes and you only model the key attributes, relationships, and
+ operations defined by the head class. The purpose of such a model is to abstract away details that can be completed by
+ the implementer.
+</p>
+<p>
+ This approach is extended to apply to the other design model elements. You may have design interfaces which are more
+ abstract than the code-level interfaces, and so on.
+</p>
+<h3>
+ <b><a id="round" name="round">Round-Trip Engineering</a></b>
+</h3>
+<p>
+ In round-trip engineering environments, the design model evolves to a level of detail where it becomes a visual
+ representation of the code. The code and its visual representation are synchronized (with tool support).
+</p>
+<p>
+ The following are some options for representing a Design Model in a round-trip engineering context.
+</p>
+<p>
+ <b><a id="trace" name="trace">High Level Design Model and Detailed Design Model</a></b><a href="#Top"><img height="20" alt="To top of page" src="./../../../core.base_rup/resources/top.gif" width="26" border="0" /></a>
+</p>
+<p>
+ In this approach, there are two levels of design model maintained. Each high level design element is an abstraction of
+ one or more detailed elements in the round-tripped model. For example, a design class may map to one "head" class and
+ several "helper" classes, just as in the "sketch and code" approach described previously. Traceability from the high
+ level design model elements to round-trip model elements can help maintain consistency between the two models.
+</p>
+<p>
+ Although this can help abstract away less important details, this benefit must be balanced against the effort required
+ to maintain consistency between the models.
+</p>
+<p>
+ <b><a id="evolves" name="evolves">Single Evolving Design Model</a></b><a href="#Top"><img height="20" alt="To top of page" src="./../../../core.base_rup/resources/top.gif" width="26" border="0" /></a>
+</p>
+<p>
+ In this approach, there is a single Design Model. Initial sketches of design elements evolve to the point where they
+ can be synchronized with code. Diagrams, such as those used to describe design use-case realizations, initially
+ reference sketched design classes, but eventually reference language-specific classes. High level descriptions of the
+ design are maintained as needed, such as:
+</p>
+<ul>
+ <li>
+ diagrams of the logical structure of the system,
+ </li>
+ <li>
+ subsystem/component specifications,
+ </li>
+ <li>
+ design patterns / mechanisms.<br />
+ </li>
+</ul>
+<p>
+ Such a model is easier to maintain consistent with the implementation.
+</p>
+<h3>
+ <a id="specification" name="specification">Specification and Realization Models</a>
+</h3>
+<p>
+ A related approach is to define the design in terms of specifications for major subsystems, detailed to the point where
+ client implementations can compile against them.
+</p>
+<p>
+ The detailed design of the subsystem realization can be modeled and maintained separately from this specification
+ model.
+</p>
+<p>
+ See <a class="elementLinkWithType" href="./../../../core.base_rup/guidances/guidelines/design_subsystem_B26FD609.html" guid="1.2314266786534317E-305">Guideline: Design Subsystem</a> for guidelines related to subsystem specifications and
+ realizations, and when they should be used.
+</p><br />
+<br /></td>
+</tr>
+</table>
+</div>
+<table cellpadding="0" cellspacing="0" border="0" class="copyright">
+<tr>
+<td class="copyright"><p>
+ © Copyright IBM Corp. 1987, 2006. All Rights Reserved.
+</p></td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+</body>
+<script language="JavaScript" type="text/javascript">
+ contentPage.onload();
+ </script>
+</html>
diff --git a/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/resources/references_6CCF393.html b/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/resources/references_6CCF393.html
new file mode 100644
index 0000000..fd8d9f4
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/resources/references_6CCF393.html
@@ -0,0 +1,870 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN""http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en" xml:lang="en" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
+<head>
+<META http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>Supporting Material: References</title>
+<meta name="uma.type" content="SupportingMaterial">
+<meta name="uma.name" content="references">
+<meta name="uma.presentationName" content="References">
+<meta name="element_type" content="other">
+<meta name="filetype" content="description">
+<meta name="role" content="">
+<link rel="StyleSheet" href="./../../../css/default.css" type="text/css">
+<script src="./../../../scripts/ContentPageResource.js" type="text/javascript" language="JavaScript"></script><script src="./../../../scripts/ContentPageSection.js" type="text/javascript" language="JavaScript"></script><script src="./../../../scripts/ContentPageSubSection.js" type="text/javascript" language="JavaScript"></script><script src="./../../../scripts/ContentPageToolbar.js" type="text/javascript" language="JavaScript"></script><script src="./../../../scripts/contentPage.js" type="text/javascript" language="JavaScript"></script><script type="text/javascript" language="JavaScript">
+ var backPath = './../../../';
+ var imgPath = './../../../images/';
+ var nodeInfo=null;
+ contentPage.preload(imgPath, backPath, nodeInfo, '', false, false, false);
+ </script>
+</head>
+<body>
+<div id="breadcrumbs"></div>
+<table border="0" cellpadding="0" cellspacing="0" width="100%">
+<tr>
+<td valign="top"><a name="Top"></a>
+<div id="page-guid" value="_9ToeIB83Edqsvps02rpOOg"></div>
+<table border="0" cellspacing="0" cellpadding="0" width="100%">
+<tr>
+<td class="pageTitle" nowrap="true">References</td><td width="100%">
+<div align="right" id="contentPageToolbar"></div>
+</td><td width="100%" class="expandCollapseLink" align="right"><a name="mainIndex" href="./../../../index.htm"></a><script language="JavaScript" type="text/javascript" src="./../../../scripts/treebrowser.js"></script></td>
+</tr>
+</table>
+<table width="100%" border="0" cellpadding="0" cellspacing="0">
+<tr>
+<td class="pageTitleSeparator"><img src="./../../../images/shim.gif" alt="" title="" height="1"></td>
+</tr>
+</table>
+<div class="overview">
+<table width="97%" border="0" cellspacing="0" cellpadding="0">
+<tr>
+<td width="50"><img src="./../../../images/supportingmaterial.gif" alt="" title=""></td><td>
+<table class="overviewTable" border="0" cellspacing="0" cellpadding="0">
+<tr>
+<td valign="top">Additional references that may be useful, including books, method plug-ins, and commercial methodology products.</td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Main Description</div>
+<div class="sectionContent">
+<table class="sectionTable" border="0" cellspacing="0" cellpadding="0">
+<tr valign="top">
+<td class="sectionTableSingleCell"><table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="ADO03" name="ADO03">ADO03</a>
+ </td>
+ <td colspan="2">
+ Adolph, Bramble, Cockburn, and Pols <em>Patterns for Effective Use Cases</em>, Addison Wesley, 2003.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="ADO04" name="ADO04">ADO04</a>
+ </td>
+ <td colspan="2">
+ Adolph, Bramble, Cockburn, and Pols <em>Tutorial 17: Patterns for Writing Effective Use Cases</em>,
+ presented at the 19th Annual Conference on Object-Oriented Programming, Systems, Languages and
+ Applications, 2004.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="ALE77" name="ALE77">ALE77</a>
+ </td>
+ <td colspan="2">
+ Alexander, C. <em>A Pattern Language</em>, Oxford University Press, 1977
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="ALE79" name="ALE79">ALE79</a>
+ </td>
+ <td colspan="2">
+ Alexander, C., <em>A Timeless Way of Building</em>, Oxford University Press, 1979
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="ALL02" name="ALL02">ALL02</a>
+ </td>
+ <td colspan="2">
+ Allamaraju, S. <em>Architecture Paradox</em>, <a href="http://www.sei.cmu.edu/architecture/essays.html">http://www.sei.cmu.edu/architecture/essays.html</a>.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="ALU03" name="ALU03">ALU03</a>
+ </td>
+ <td colspan="2">
+ <p>
+ Alur, D., Crupi, J., Malks, D., <em>Core J2EE Patterns: Best Practices and Design Strategies</em>,
+ Prentice Hall/Sun Press, 2001.
+ </p>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="AMB02" name="AMB02">AMB02</a>
+ </td>
+ <td colspan="2">
+ Ambler, S.W.<em>Agile Modeling: Effective Practices for Extreme Programming and Unified Process</em>. Wiley
+ Publishing, 2002.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="AMB03" name="AMB03">AMB03</a>
+ </td>
+ <td colspan="2">
+ Ambler, S.W.<em>Agile Database Techniques: Effective Strategies for the Agile Software Developer</em>.
+ Wiley Publishing, 2003.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="AMB04" name="AMB04">AMB04</a>
+ </td>
+ <td colspan="2">
+ Ambler, S.W.<em>The Object Primer 3rd Edition: Agile Model Driven Development with UML 2</em>. Addison
+ Wesley, 2006.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="AMB06" name="AMB06">AMB06</a>
+ </td>
+ <td colspan="2">
+ Ambler, S.W. and Sadalage, P.J. <em>Refactoring Databases: Evolutionary Database Design</em>. Addison
+ Wesley, 2006.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="AMB07" name="AMB07">AMB07</a>
+ </td>
+ <td colspan="2">
+ Ambler, S.W.<em>The Agile End Game,</em> <a href="http://www.agilealliance.org/show/1819">http://www.agilealliance.org/show/1819</a>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="BEC05" name="BEC05">BEC05</a>
+ </td>
+ <td colspan="2">
+ Beck, K., Andres, C. <em>Extreme Programming Explained: Embrace Change, 2nd Edition</em>, Addison Wesley,
+ 2005.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="BOE88" name="BOE88">BOE88</a>
+ </td>
+ <td colspan="2">
+ Boehm, B., Papaccio, C. <em>Understanding and Controlling Software Cost</em>, IEEE Trans. on Software
+ Engineering, Oct. 1988.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="BOE95" name="BOE95">BOE95</a>
+ </td>
+ <td colspan="2">
+ Boehm, B. <em>Anchoring the Software Process</em>, <a href="http://sunset.usc.edu/publications/TECHRPTS/1995/usccse95-507/ASP.pdf">http://sunset.usc.edu/publications/TECHRPTS/1995/usccse95-507/ASP.pdf</a>
+ (Get <a href="http://www.adobe.com/products/acrobat/alternate.html">Adobe reader</a>.)
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="BRO87" name="BRO87">BRO87</a>
+ </td>
+ <td colspan="2">
+ Brooks, F.P <em>No Silver Bullet: Essence and Accidents of Software Engineering.</em>Computer, April. 1987,
+ pp. 10-19.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="BOO05" name="BOO05">BOO05</a>
+ </td>
+ <td colspan="2">
+ Booch, G., Rumbaugh, J., Jacobson, I.<em>The Unified Modeling Language User Guide</em>, Addison-Wesley
+ Professional, 2005
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="BUS96" name="BUS96">BUS96</a>
+ </td>
+ <td colspan="2">
+ Buschmann, F., Meunier, R., Rohnert, H.,Sommerlad, P., Stal, M., <em>Pattern-Oriented Software Architecture
+ -- A System of Patterns</em>, Wiley, 1996.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="COH05" name="COH05">COH05</a>
+ </td>
+ <td colspan="2">
+ Cohn, M., <em>Agile Estimation and Planning</em>, Addison Wesley Longman, 2005
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="COP95" name="COP95">COP95</a>
+ </td>
+ <td colspan="2">
+ Coplien, J., Schmidt, D., <em>Pattern Languages of Program Design</em>, Addison-Wesley Professional, 1995.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="CRO79" name="CRO79">CRO79</a>
+ </td>
+ <td colspan="2">
+ Crosby, Philip. <em>Quality is Free: The Art of Making Quality Certain</em>, McGraw-Hill, 1979.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="DER06" name="DER06">DER06</a>
+ </td>
+ <td colspan="2">
+ Derby, Esther and Larsen, Diana <em>Agile Retrospectives: Making Good Team Great</em>, Pragmatic Bookshelf,
+ Dallas, Texas, 2006.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="DEW92" name="DEW92">DEW92</a>
+ </td>
+ <td colspan="2">
+ Dewayne E. Perry and Alexander L. Wolf. <em>Foundations for the Study of Software Architecture</em>. ACM
+ SIGSOFT Software Engineering Notes, 17(4):40-52, October 1992.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="DSDM" name="DSDM">DSDM</a>
+ </td>
+ <td colspan="2">
+ DSDM Consortium, <em>DSDM</em><br />
+ <a href="http://www.dsdm.org/products/">http://www.dsdm.org/products/</a>
+ </td>
+ </tr>
+ </tbody>
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="FOW06" name="FOW06">FOW06</a>
+ </td>
+ <td colspan="2">
+ Fowler, Martin <em>Continuous Integration</em><br />
+ <a href="http://www.martinfowler.com/articles/continuousIntegration.html">http://www.martinfowler.com/articles/continuousIntegration.html</a>
+ </td>
+ </tr>
+ </tbody>
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="FOW99" name="FOW99">FOW99</a>
+ </td>
+ <td colspan="2">
+ Fowler, Martin, <em>Refactoring: Improving the Design of Existing Code</em>, Addison-Wesley Professional;
+ 1999
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="GAM95" name="GAM95">GAM95</a>
+ </td>
+ <td colspan="2">
+ Gamma, E., Helm, R., Johnson, R., Vlissides, J., <em>Design Patterns: Elements of Reusable Object-Oriented
+ Software</em>, Addison-Wesley Professional; 1995
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="GAB98" name="GAB98">GAB98</a>
+ </td>
+ <td colspan="2">
+ Gabriel, Richard P., <em>Patterns of Software: Tales from the Software Community</em>, Oxford University
+ Press, 1998.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="GAR93" name="GAR93">GAR93</a>
+ </td>
+ <td colspan="2">
+ David Garlan and Mary Shaw. <em>An Introduction to Software Architecture</em>, SEI Technical Report
+ CMU/SEI-94-TR-21.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="HIC03" name="HIC03">HIC03</a>
+ </td>
+ <td colspan="2">
+ Hickey A., Davis, A. <em>Elicitation Technique Selection: How Do the Experts Do It?</em>, International
+ Conference on Requirements Engineering (RE03), Los Alamitos, California: IEEE Computer Society Press,
+ September 2003.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="HUL05" name="HUL05">HUL05</a>
+ </td>
+ <td colspan="2">
+ Hull, E., Jackson, K. and Dick, J. <em>Requirements Engineering</em>, Second Edition. Springer, 2005.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="IEP1471" name="IEP1471">IEP1471</a>
+ </td>
+ <td colspan="2">
+ IEEE <em>Recommended Practice for Architectural Description</em>, IEEE Std P1471, 2000.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="JAZZ" name="JAZZ">JAZZ</a>
+ </td>
+ <td colspan="2">
+ The <em>Eclipse Way</em> is among others available through the JAZZ Project,<br />
+ <a href="http://www.jazz.net">http://www.jazz.net</a>
+ </td>
+ </tr>
+ </tbody>
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="KAN96" name="KAN96">KAN96</a>
+ </td>
+ <td colspan="2">
+ Kaner, Sam <em>The Facilitator's Guide to Participatory Decision-Making</em>, New Society Publishers,
+ Gabriola Island, BC, 1996.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="KAT93" name="KAT93">KAT93</a>
+ </td>
+ <td colspan="2">
+ Katzenbach, J.R. & Smith, D.K. <em>The wisdom of teams: Creating the high-performance
+ organization</em>, Harvard Business School, Boston, 1993.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="KAZ00" name="KAZ00">KAZ00</a>
+ </td>
+ <td colspan="2">
+ Kazman, R., Carriere, S. J., Woods, S. G. <a href="http://www.sei.cmu.edu/staff/rkazman/annals-scenario.pdf">Toward a Discipline of Scenario-Based
+ Architectural Engineering</a>,(Get <a href="http://www.adobe.com/products/acrobat/alternate.html">Adobe
+ reader</a>.) <a href="http://manta.cs.vt.edu./ase/">Annals of Software Engineering</a>, Vol. 9, 2000, 5-33.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="KAZ04" name="KAZ04">KAZ04</a>
+ </td>
+ <td colspan="2">
+ Kazman, R., Kruchten, P., Nord, R., Tomayko, J. <em>Integrating Software-Architecture-Centric Methods
+ into the Rational Unified Process</em>, CMU-SEI Technical Reports, 2004.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="KER01" name="KER01">KER01</a>
+ </td>
+ <td colspan="2">
+ Norman L. Kerth. <em>Project Retrospectives: A Handbook for Team Reviews</em>, Dorset House Publishers, New
+ York, 2001.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="KRO03" name="KRO03">KRO03</a>
+ </td>
+ <td colspan="2">
+ Kroll, P. and Kruchten, P. <em>The Rational Unified Process Made Easy</em>, Addison Wesley, 2003.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ KRO05
+ </td>
+ <td colspan="2">
+ Kroll, P. and MacIsaac, B. <em>Agility and Discipline Made Easy</em>, Addison Wesley, 2005.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="KRU95" name="KRU95">KRU95</a>
+ </td>
+ <td colspan="2">
+ Kruchten, Phillipe B., <em>The 4+1 View Model of Architecture</em>, IEEE Software, vol. 12, no. 6, pp
+ 42-50, November 1995
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="LAR03" name="LAR03">LAR03</a>
+ </td>
+ <td colspan="2">
+ Larman, Craig <em>Agile and Iterative Development: A Manager's Guide</em>, Addison Wesley, 2003
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="MAR03" name="MAR03">MAR03</a>
+ </td>
+ <td colspan="2">
+ <p>
+ Marick, B., <em>Exploration Through Example</em>, <a href="http://www.testing.com/cgi-bin/blog/2003/08/21#agile-testing-project-1">http://www.testing.com/cgi-bin/blog/2003/08/21#agile-testing-project-1</a>
+ </p>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="MEY97" name="MEY97">MEY97</a>
+ </td>
+ <td colspan="2">
+ Meyer, B., <em>Object-Oriented Software Construction</em>, Prentice Hall, 1997
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <p>
+ <a id="NBG01" name="NBG01">NBG01</a>
+ </p>
+ </td>
+ <td colspan="2">
+ Eric J. Naiburg and Robert A. Maksimchuk. <em>UML for Database Design</em>, New York, NY: Addison Wesley,
+ 2001
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="OOP96" name="OOP96">OOP96</a>
+ </td>
+ <td colspan="2">
+ The 1996 ACM Conference on Object-Oriented Programs, Systems, Languages and Applications (OOPSLA), <em>The
+ Origins of Pattern Theory, the Future of the Theory, And The Generation of a Living World.</em>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top" width="12%">
+ </td>
+ <td width="10%">
+ </td>
+ <td style="PADDING-BOTTOM: 10px" width="78%">
+ See <a href="http://www.patternlanguage.com/archive/ieee/ieeetext.htm">http://www.patternlanguage.com/archive/ieee/ieeetext.htm</a>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="PMI04" name="PMI04">PMI04</a>
+ </td>
+ <td colspan="2">
+ Project Management Institute, <em>A Guide to the Project Management Body of Knowledge</em>, Third Edition,
+ 2004.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="RUP06" name="RUP06">RUP06</a>
+ </td>
+ <td colspan="2">
+ IBM Rational 2006. <em>The Rational Unified Process.</em>
+ </td>
+ </tr>
+ <tr>
+ <td valign="top" width="12%">
+ </td>
+ <td width="10%">
+ </td>
+ <td style="PADDING-BOTTOM: 10px" width="78%">
+ A commercial methodology, also based on the Eclipse Process Framework, and advanced guidance on topics such
+ as business modeling, portfolio management, asset-based development, real-time design, user experience, and
+ so on.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="SCH04" name="SCH04">SCH04</a>
+ </td>
+ <td colspan="2">
+ Schwaber, K. <em>Agile Project Management with Scrum.</em> Microsoft Press 2004.
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="SEI99" name="SEI99">SEI99</a>
+ </td>
+ <td colspan="2">
+ SEI <em>Software Risk Evaluation (SRE) Method Description, v2.0</em>SEI, 1999<br />
+ <a href="http://www.sei.cmu.edu/pub/documents/99.reports/pdf/99tr029-body.pdf#search="software risk evaluation"">http://www.sei.cmu.edu/pub/documents/99.reports/pdf/99tr029-body.pdf#search=%22software%20risk%20evaluation%22</a>
+ (Get <a href="http://www.adobe.com/products/acrobat/alternate.html">Adobe reader</a>.)
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="SHA05" name="SHA05">SHA05</a>
+ </td>
+ <td colspan="2">
+ Shalloway, J., Trott, J. <em>Design Patterns Explained</em> A New Perspective on Object-Oriented Design,
+ Second Edition, Addison Wesley, 2005
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="SHO06" name="SHO06">SHO06</a>
+ </td>
+ <td colspan="2">
+ Shore, James <em>Successful Software</em><br />
+ <a href="http://www.jamesshore.com/Blog/Continuous-Integration-on-a-Dollar-a-Day.html">http://www.jamesshore.com/Blog/Continuous-Integration-on-a-Dollar-a-Day.html</a>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="STZ07" name="STZ07">STZ07</a>
+ </td>
+ <td colspan="2">
+ Schatz , Bob - <span class="sans" style="FONT-STYLE: italic">Successful Sprint Reviews</span><br />
+ <a href="http://www.scrumalliance.org/articles/48-successful-sprint-reviews">http://www.scrumalliance.org/articles/48-successful-sprint-reviews</a>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="SUT06" name="SUT06">SUT06</a>
+ </td>
+ <td colspan="2">
+ Sutherland, <font face="Arial, Helvetica, sans-serif">Jeff <em>- Why the Three questions in the Daily Scrum
+ Meeting?</em></font><br />
+ <a href="http://jeffsutherland.com/scrum/2006/06/why-three-questions-in-daily-scrum.html">http://jeffsutherland.com/scrum/2006/06/why-three-questions-in-daily-scrum.html</a>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="TAV84" name="TAV84">TAV84</a>
+ </td>
+ <td colspan="2">
+ Tavalato, P., K. Vincena <em>A Prototyping Methodology and its Tool</em>, in Approaches to Prototyping, R.
+ Budde, ed., Berlin: Springer-Verlag, 1984, pp. 434-446
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="TEL06" name="TEL06">TEL06</a>
+ </td>
+ <td colspan="2">
+ Telelogic, 2006. <em>Get It Right the First Time: Writing Better Requirements.</em>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="THA00" name="THA00">THA00</a>
+ </td>
+ <td colspan="2">
+ Thayer, Richard H. and Dorfman, Merlin <em>Software Requirements Engineering Second Edition</em>,
+ IEEE Computer Society, 2000
+ </td>
+ </tr>
+ </tbody>
+</table>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="UML05" name="UML05">UML05</a>
+ </td>
+ <td colspan="2">
+ OMG, 2005. <em>Unified Modeling Language 2.0: Superstructure.</em><br />
+ <a href="http://www.omg.org/docs/formal/05-07-04.pdf">http://www.omg.org/docs/formal/05-07-04.pdf</a> (Get
+ <a href="http://www.adobe.com/products/acrobat/alternate.html">Adobe reader</a>.)
+ </td>
+ </tr>
+ </tbody>
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="WIB04" name="WIB04">WIB04</a>
+ </td>
+ <td colspan="2">
+ Wiborg-Weber, D., Vignaud, J. L. <em>A Framework for Managing Component Based Development</em>, Telelogic
+ Whitepaper, 2004<br />
+ <a href="http://www.telelogic.com/download/index.cfm?id=4423">http://www.telelogic.com/download/index.cfm?id=4423</a>
+ </td>
+ </tr>
+ </tbody>
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="WIKP-MVC" name="WIKP-MVC">WIKP-MVC</a>
+ </td>
+ <td colspan="2">
+ Wikipedia <em>Model-view-controller</em><br />
+ <a href="http://en.wikipedia.org/wiki/Model-view-controller">http://en.wikipedia.org/wiki/Model-view-controller</a>
+ </td>
+ </tr>
+ </tbody>
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="WIKP-CI" name="WIKP-CI">WIKP-CI</a>
+ </td>
+ <td colspan="2">
+ Wikipedia <em>Continuous Integration</em><br />
+ <a href="http://en.wikipedia.org/wiki/Continuous_Integration">http://en.wikipedia.org/wiki/Continuous_Integration</a>
+ </td>
+ </tr>
+ </tbody>
+ <tbody>
+ <tr>
+ <td valign="top" width="12%">
+ <a id="YIP" name="YIP">YIP</a>
+ </td>
+ <td colspan="2">
+ YIP, Jason <em>It's Not Just Standing Up: Patterns of Daily Stand-up Meetings</em><br />
+ <a href="http://www.martinfowler.com/articles/itsNotJustStandingUp.html">http://www.martinfowler.com/articles/itsNotJustStandingUp.html</a>
+ </td>
+ </tr>
+ </tbody>
+</table></td>
+</tr>
+</table>
+</div>
+<table class="copyright" border="0" cellspacing="0" cellpadding="0">
+<tr>
+<td class="copyright"><p>
+ This program and the accompanying materials are made available under the<br />
+ <a href="http://www.eclipse.org/org/documents/epl-v10.php" target="_blank">Eclipse Public License v1.0</a> which
+ accompanies this distribution.
+</p><p/><p>
+ <a class="elementLink" href="./../../../openup/guidances/supportingmaterials/openup_copyright_C3031062.html" guid="_UaGfECcTEduSX6N2jUafGA">OpenUP Copyright</a>.
+</p></td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+</body>
+<script type="text/javascript" language="JavaScript">
+ contentPage.onload();
+ </script>
+</html>
diff --git a/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/resources/rup_development_case_F4260B3A.html b/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/resources/rup_development_case_F4260B3A.html
new file mode 100644
index 0000000..1ccba99
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/resources/rup_development_case_F4260B3A.html
@@ -0,0 +1,251 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" lang="en" xml:lang="en">
+<head>
+<META http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>Artifact: Development Case</title>
+<meta content="Artifact" name="uma.type">
+<meta content="rup_development_case" name="uma.name">
+<meta content="Development Case" name="uma.presentationName">
+<meta content="WorkProductType:process:Process" name="uma.category">
+<meta content="Artifact" name="element_type">
+<meta content="description" name="filetype">
+<meta name="role" content="">
+<link type="text/css" href="./../../css/default.css" rel="StyleSheet">
+<script language="JavaScript" type="text/javascript" src="./../../scripts/ContentPageResource.js"></script><script language="JavaScript" type="text/javascript" src="./../../scripts/ContentPageSection.js"></script><script language="JavaScript" type="text/javascript" src="./../../scripts/ContentPageSubSection.js"></script><script language="JavaScript" type="text/javascript" src="./../../scripts/ContentPageToolbar.js"></script><script language="JavaScript" type="text/javascript" src="./../../scripts/contentPage.js"></script><script language="JavaScript" type="text/javascript">
+ var backPath = './../../';
+ var imgPath = './../../images/';
+ var nodeInfo=[{view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_Jvt1cAIaEdqEutyfYo0quQ", "_EOvXUN7HEdm8G6yT7-Wdqw", "_5JJn0P_UEdmVCcs_BRqacA", "{345D1811-317B-47EC-AC9D-10E1072A7D68}", "{F071C3D3-7054-457F-8A81-EFA6678CCDE1}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_Jvt1cAIaEdqEutyfYo0quQ", "_jijhYAIaEdqEutyfYo0quQ", "_HXPBcCxnEdqYV4MWf8PiCw", "{F071C3D3-7054-457F-8A81-EFA6678CCDE1}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_Jvt1cAIaEdqEutyfYo0quQ", "_jijhYAIaEdqEutyfYo0quQ", "_HXPBcCxnEdqYV4MWf8PiCw", "{345D1811-317B-47EC-AC9D-10E1072A7D68}", "{F071C3D3-7054-457F-8A81-EFA6678CCDE1}"]}, {view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_4U33kAILEdq-_NKqZM1EhA", "_U8LVkAIUEdqEutyfYo0quQ", "_5JJn0P_UEdmVCcs_BRqacA", "{345D1811-317B-47EC-AC9D-10E1072A7D68}", "{F071C3D3-7054-457F-8A81-EFA6678CCDE1}"]}];
+ contentPage.preload(imgPath, backPath, nodeInfo, '', false, false, false);
+ </script>
+</head>
+<body>
+<div id="breadcrumbs"></div>
+<table width="100%" cellspacing="0" cellpadding="0" border="0">
+<tr>
+<td valign="top"><a name="Top"></a>
+<div id="page-guid" value="{F071C3D3-7054-457F-8A81-EFA6678CCDE1}"></div>
+<table width="100%" cellpadding="0" cellspacing="0" border="0">
+<tr>
+<td nowrap="true" class="pageTitle">Artifact: Development Case</td><td width="100%">
+<div id="contentPageToolbar" align="right"></div>
+</td>
+</tr>
+</table>
+<table cellspacing="0" cellpadding="0" border="0" width="100%">
+<tr>
+<td class="pageTitleSeparator"><img height="1" title="" alt="" src="./../../images/shim.gif"></td>
+</tr>
+</table>
+<div class="overview">
+<table cellpadding="0" cellspacing="0" border="0" width="97%">
+<tr>
+<td width="50"><img title="" alt="" src="./../../core.base_rup/workproducts/resources/doc_artf.jpg"></td><td>
+<table cellpadding="0" cellspacing="0" border="0" class="overviewTable">
+<tr>
+<td valign="top">This artifact describes the development process that you have chosen to follow in your project. </td>
+</tr>
+<tr>
+<td>Work Product Kinds: <a href="./../../core.base_rup/workproducttypes/process_E256BF65.html" guid="_HXPBcCxnEdqYV4MWf8PiCw">Process</a></td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Purpose</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<td class="sectionTableSingleCell"><a id="Top" name="Top"></a><a id="XE_development_case__as_artifact" name="XE_development_case__as_artifact"></a><a id="XE_development_case__purpose_of" name="XE_development_case__purpose_of"></a><a id="Purpose" name="Purpose"></a>
+<p>
+ The purpose of the Development Case is to capture the tailored process for an organization or for an individual
+ project. It describes how the process has been configured.
+</p></td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Relationships</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Container Artifact</th><td colspan="2" class="sectionTableCell">
+<li>
+<a href="./../../core.base_rup/workproducts/rup_development_process_A6449790.html" guid="{345D1811-317B-47EC-AC9D-10E1072A7D68}">Development Process</a>
+</li>
+</td>
+</tr>
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Roles</th><td width="42%" class="sectionTableCell"><span class="sectionTableCellHeading">Responsible:
+ </span>
+<ul>
+<li>
+<a href="./../../core.base_rup/roles/rup_process_engineer_5954DBA2.html" guid="{ADDC62A7-8E36-4DCE-9E5C-211B0950EBB5}">Process Engineer</a>
+</li>
+</ul>
+</td><td class="sectionTableCell"><span class="sectionTableCellHeading">Modified By:
+ </span>
+<ul>
+<li>
+<a href="./../../core.base_rup/roles/rup_process_engineer_5954DBA2.html" guid="{ADDC62A7-8E36-4DCE-9E5C-211B0950EBB5}">Process Engineer</a>
+</li>
+</ul>
+</td>
+</tr>
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Tasks</th><td width="42%" class="sectionTableCell"><span class="sectionTableCellHeading">Input To:
+ </span>
+<ul>
+<li>
+<a href="./../../core.base_rup/tasks/develop_development_case_B10E3391.html" guid="{F6999E01-701F-4D48-9E83-A063CB35912B}">Develop Development Case</a>
+</li>
+</ul>
+</td><td class="sectionTableCell"><span class="sectionTableCellHeading">Output From:
+ </span>
+<ul>
+<li>
+<a href="./../../core.base_rup/tasks/develop_development_case_B10E3391.html" guid="{F6999E01-701F-4D48-9E83-A063CB35912B}">Develop Development Case</a>
+</li>
+</ul>
+</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Description</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Main Description</th><td class="sectionTableCell"><p>
+ The Development Case describes the <a class="elementLink" href="./../../core.base_rup/workproducts/rup_development_process_A6449790.html" guid="{345D1811-317B-47EC-AC9D-10E1072A7D68}">Development Process</a> to be used for an organization or for a
+ project. It describes how the process applies to the context of the organization/project, and how the process has been
+ configured for the organization/project. The Development Case is used to capture organization or project-specific
+ aspects of the process. It provides an overview of the process to be followed and is something that should be
+ understood by everyone on the project.
+</p></td>
+</tr>
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Brief Outline</th><td class="sectionTableCell"><p>
+ The Development Case includes information on the RUP disciplines being used by the organization/project.
+</p>
+<p>
+ It usually contains the following organization/project-specific information:
+</p>
+<ul>
+ <li>
+ Information about how to use the work products for each discipline. For example, references to templates that the
+ organization/project is to use to describe the work products.
+ </li>
+ <li>
+ References to guidelines and information that the organization/project wants to use in addition to the information
+ contained in RUP.
+ </li>
+ <li>
+ References to content in RUP instead of repeating this information in the Development Case.
+ </li>
+</ul>
+<p>
+ In general, the development case should refer to the software development process and any organization/project-specific
+ process assets like guidelines, templates, etc. for details, as opposed to repeating the information, inline.
+</p>
+<p>
+ The development case also includes information on what was tailored and why.
+</p>
+<p>
+ <br />
+</p></td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Illustrations </div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Templates</th><td class="sectionTableCell">
+<ul>
+<li>
+<a href="./../../extend.formal_resources/guidances/templates/development_case_EAED8954.html" guid="1.7139777349961585E-305">Development Case</a>
+</li>
+<li>
+<a href="./../../core.informal_resources/guidances/templates/development_case_informal_4C5C78DE.html" guid="9.34727211175401E-305">Development Case (Informal)</a>
+</li>
+</ul>
+</td>
+</tr>
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Examples</th><td class="sectionTableCell">
+<ul>
+<li>
+<a href="./../../extend.formal_resources/guidances/examples/project_abc_development_case_443F1418.html" guid="2.8689881014614235E-305">Project ABC—Development Case</a>
+</li>
+<li>
+<a href="./../../core.informal_resources/guidances/examples/csps_development_case_-_inception_phase_3121E97F.html" guid="1.2849327955598506E-304">CSPS Development Case - Inception Phase</a>
+</li>
+</ul>
+</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Key Considerations</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<td class="sectionTableSingleCell"><p>
+ <font face="Helv" size="2">Depending on the level of tailoring being performed (see the tailoring levels defined in <a class="elementLinkWithType" href="./../../core.base_rup/guidances/concepts/tailoring_rup_F8F0EB23.html" guid="6.991505672198195E-305">Concept: Tailoring RUP</a>), the Development Case can be use as:</font>
+</p>
+<ul>
+ <li>
+ <font face="Helv" size="2">The vehicle for process tailoring (this is it's primary purpose and the one it has
+ historically been used for).</font>
+ </li>
+ <li>
+ <font face="Helv" size="2">A planning tool to get ready for a more extensive tailoring using <a class="elementLink" href="./../../core.base_rup/tools/rup_rational_method_composer_84A966EC.html" guid="_hAfB8COzEdq41POk0CQYwA">Rational Method Composer</a>.</font>
+ </li>
+</ul>
+<p>
+ The Development Case can then be included as part of the <a class="elementLink" href="./../../core.base_rup/workproducts/rup_development_process_A6449790.html" guid="{345D1811-317B-47EC-AC9D-10E1072A7D68}">Development Process</a> itself, or just archived as historical
+ documentation of what was added/removed/changed from the original process. The Development Case is generally
+ included as part of the development process in those instances when the process being tailored cannot be changed, or
+ when there is information that must be captured regarding the process that cannot be captured in the process itself.
+</p></td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Tailoring</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Representation Options</th><td class="sectionTableCell">For an example of where the Development Case has been integrated into a project web site, see the <a class="elementLinkWithType" href="./../../extend.formal_resources/guidances/examples/wylie_college_software_development_process_6579D2F2.html" guid="1.221234477392049E-305">Example: Wylie College Software Development Process</a>. </td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">More Information</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Guidelines</th><td class="sectionTableCell">
+<ul>
+<li>
+<a href="./../../core.base_rup/guidances/guidelines/classifying_work_products_4250A298.html" guid="7.27749388241665E-306">Classifying Work Products</a>
+</li>
+<li>
+<a href="./../../core.base_rup/guidances/guidelines/review_levels_72ACB304.html" guid="8.546224914239529E-306">Review Levels</a>
+</li>
+</ul>
+</td>
+</tr>
+</table>
+</div>
+<table cellpadding="0" cellspacing="0" border="0" class="copyright">
+<tr>
+<td class="copyright"><p>
+ © Copyright IBM Corp. 1987, 2006. All Rights Reserved.
+</p></td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+</body>
+<script language="JavaScript" type="text/javascript">
+ contentPage.onload();
+ </script>
+</html>
diff --git a/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/resources/rup_project_specific_guidelines_8DC8DA32.html b/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/resources/rup_project_specific_guidelines_8DC8DA32.html
new file mode 100644
index 0000000..5da392b
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/resources/rup_project_specific_guidelines_8DC8DA32.html
@@ -0,0 +1,291 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" lang="en" xml:lang="en">
+<head>
+<META http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>Artifact: Project-Specific Guidelines</title>
+<meta content="Artifact" name="uma.type">
+<meta content="rup_project_specific_guidelines" name="uma.name">
+<meta content="Project-Specific Guidelines" name="uma.presentationName">
+<meta content="WorkProductType:process:Process" name="uma.category">
+<meta content="Artifact" name="element_type">
+<meta content="description" name="filetype">
+<meta name="role" content="">
+<link type="text/css" href="./../../css/default.css" rel="StyleSheet">
+<script language="JavaScript" type="text/javascript" src="./../../scripts/ContentPageResource.js"></script><script language="JavaScript" type="text/javascript" src="./../../scripts/ContentPageSection.js"></script><script language="JavaScript" type="text/javascript" src="./../../scripts/ContentPageSubSection.js"></script><script language="JavaScript" type="text/javascript" src="./../../scripts/ContentPageToolbar.js"></script><script language="JavaScript" type="text/javascript" src="./../../scripts/contentPage.js"></script><script language="JavaScript" type="text/javascript">
+ var backPath = './../../';
+ var imgPath = './../../images/';
+ var nodeInfo=[{view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_Jvt1cAIaEdqEutyfYo0quQ", "_EOvXUN7HEdm8G6yT7-Wdqw", "_5JJn0P_UEdmVCcs_BRqacA", "{345D1811-317B-47EC-AC9D-10E1072A7D68}", "{E5501201-7EE6-4243-AE91-73880FF76FC1}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_Jvt1cAIaEdqEutyfYo0quQ", "_jijhYAIaEdqEutyfYo0quQ", "_HXPBcCxnEdqYV4MWf8PiCw", "{345D1811-317B-47EC-AC9D-10E1072A7D68}", "{E5501201-7EE6-4243-AE91-73880FF76FC1}"]}, {view: "view:_FCx1oN7CEdmsEI4YDGX2ag", path: ["_FCx1oN7CEdmsEI4YDGX2ag", "_Jvt1cAIaEdqEutyfYo0quQ", "_jijhYAIaEdqEutyfYo0quQ", "_HXPBcCxnEdqYV4MWf8PiCw", "{E5501201-7EE6-4243-AE91-73880FF76FC1}"]}, {view: "view:_LVCagP5WEdmAzesbYywanQ", path: ["_LVCagP5WEdmAzesbYywanQ", "_4U33kAILEdq-_NKqZM1EhA", "_U8LVkAIUEdqEutyfYo0quQ", "_5JJn0P_UEdmVCcs_BRqacA", "{345D1811-317B-47EC-AC9D-10E1072A7D68}", "{E5501201-7EE6-4243-AE91-73880FF76FC1}"]}];
+ contentPage.preload(imgPath, backPath, nodeInfo, '', false, false, false);
+ </script>
+</head>
+<body>
+<div id="breadcrumbs"></div>
+<table width="100%" cellspacing="0" cellpadding="0" border="0">
+<tr>
+<td valign="top"><a name="Top"></a>
+<div id="page-guid" value="{E5501201-7EE6-4243-AE91-73880FF76FC1}"></div>
+<table width="100%" cellpadding="0" cellspacing="0" border="0">
+<tr>
+<td nowrap="true" class="pageTitle">Artifact: Project-Specific Guidelines</td><td width="100%">
+<div id="contentPageToolbar" align="right"></div>
+</td>
+</tr>
+</table>
+<table cellspacing="0" cellpadding="0" border="0" width="100%">
+<tr>
+<td class="pageTitleSeparator"><img height="1" title="" alt="" src="./../../images/shim.gif"></td>
+</tr>
+</table>
+<div class="overview">
+<table cellpadding="0" cellspacing="0" border="0" width="97%">
+<tr>
+<td width="50"><img title="" alt="" src="./../../core.base_rup/workproducts/resources/doc_artf.jpg"></td><td>
+<table cellpadding="0" cellspacing="0" border="0" class="overviewTable">
+<tr>
+<td valign="top">This work product provides prescriptive guidance on how to perform a certain task or a set of task in the context of the project.</td>
+</tr>
+<tr>
+<td>Work Product Kinds: <a href="./../../core.base_rup/workproducttypes/process_E256BF65.html" guid="_HXPBcCxnEdqYV4MWf8PiCw">Process</a></td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Purpose</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<td class="sectionTableSingleCell"><a id="Top" name="Top"></a><a id="XE_project_specific_guidelines__artifact_definition" name="XE_project_specific_guidelines__artifact_definition"></a><a id="Purpose" name="Purpose"></a><a id="XE_project_specific_guidelines__purpose_of" name="XE_project_specific_guidelines__purpose_of"></a>
+<p>
+ The Project-Specific Guidelines are used by the project members when performing the tasks assigned to them. Any
+ tailoring decisions for the project's work products should be captured in the Project-Specific Guidelines.
+</p></td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Relationships</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Container Artifact</th><td colspan="2" class="sectionTableCell">
+<li>
+<a href="./../../core.base_rup/workproducts/rup_development_process_A6449790.html" guid="{345D1811-317B-47EC-AC9D-10E1072A7D68}">Development Process</a>
+</li>
+</td>
+</tr>
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Roles</th><td width="42%" class="sectionTableCell"><span class="sectionTableCellHeading">Responsible:
+ </span>
+<ul>
+<li>
+<a href="./../../core.base_rup/roles/rup_process_engineer_5954DBA2.html" guid="{ADDC62A7-8E36-4DCE-9E5C-211B0950EBB5}">Process Engineer</a>
+</li>
+</ul>
+</td><td class="sectionTableCell"><span class="sectionTableCellHeading">Modified By:
+ </span>
+<ul>
+<li>
+<a href="./../../core.base_rup/roles/rup_process_engineer_5954DBA2.html" guid="{ADDC62A7-8E36-4DCE-9E5C-211B0950EBB5}">Process Engineer</a>
+</li>
+</ul>
+</td>
+</tr>
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Tasks</th><td width="42%" class="sectionTableCell"><span class="sectionTableCellHeading">Input To:
+ </span>
+<ul>
+<li>
+<a href="./../../core.base_rup/tasks/analyze_test_failure_7E42EE55.html" guid="{EA0E3D2C-F87E-49CA-8832-F791886D5741}">Analyze Test Failure</a>
+</li>
+<li>
+<a href="./../../core.base_rup/tasks/architectural_analysis_2B9BE03.html" guid="{8CB48402-D4C5-4E17-BB33-507315CB1BBF}">Architectural Analysis</a>
+</li>
+<li>
+<a href="./../../core.base_rup/tasks/class_design_98F20FF9.html" guid="{27AE0601-2E95-4A6A-8EB3-0A4BA8E5626B}">Class Design</a>
+</li>
+<li>
+<a href="./../../core.base_rup/tasks/compile_software_development_plan_FADDE6C8.html" guid="{7B3D4BD7-93D5-4240-A449-47742FBB40A7}">Compile Software Development Plan</a>
+</li>
+<li>
+<a href="./../../core.base_rup/tasks/conduct_review_1D8A70F8.html" guid="{01C0BC09-C421-438A-B4C4-351C46A244C9}">Conduct Review</a>
+</li>
+<li>
+<a href="./../../core.base_rup/tasks/create_baseline_30FA138.html" guid="{F8256B31-5CE3-49C0-9DC2-ECB57DD48867}">Create Baselines</a>
+</li>
+<li>
+<a href="./../../core.base_rup/tasks/create_integration_workspace_791B9994.html" guid="{85EC2AE2-FEAF-4DAE-B633-A4D97A9136D2}">Create Integration Workspaces</a>
+</li>
+<li>
+<a href="./../../core.base_rup/tasks/database_design_8552DD3.html" guid="{2E74A414-49F5-4F27-BFCB-AA2DAC675F58}">Database Design</a>
+</li>
+<li>
+<a href="./../../core.base_rup/tasks/define_test_approach_51A370C3.html" guid="{87F96887-83EF-4F0F-8F79-E98043406B52}">Define Test Approach</a>
+</li>
+<li>
+<a href="./../../core.base_rup/tasks/design_user_interface_DAABE09F.html" guid="{7414C358-6188-4E5C-8C35-F9D4DF3E0123}">Design the User Interface</a>
+</li>
+<li>
+<a href="./../../extend.bus_model/tasks/detail_a_business_entity_11E120FA.html" guid="{06A9A8AA-171C-4A9C-8CD8-A366F32AA77F}">Detail a Business Entity</a>
+</li>
+<li>
+<a href="./../../extend.bus_model/tasks/detail_a_business_worker_B5309727.html" guid="{DCFC0362-DBB6-4858-A9E4-AF907780FD99}">Detail a Business Worker</a>
+</li>
+<li>
+<a href="./../../core.base_rup/tasks/identify_design_elements_E884AB82.html" guid="{97D7343A-6993-4AB7-8F86-4DAC8C9075C8}">Identify Design Elements</a>
+</li>
+<li>
+<a href="./../../core.base_rup/tasks/identify_testability_mechanisms_9EE13DB9.html" guid="{28208FC5-9C66-42D1-8E27-11DDE41EB654}">Identify Testability Mechanisms</a>
+</li>
+<li>
+<a href="./../../core.base_rup/tasks/identify_test_ideas_395DAB3B.html" guid="{6FAD9DF9-DE4E-4BA5-9B9B-482A2366D1B9}">Identify Test Ideas</a>
+</li>
+<li>
+<a href="./../../core.base_rup/tasks/implement_component_AE366827.html" guid="{3293F4F7-EFCD-4476-BFF1-81AC3812B512}">Implement Design Elements</a>
+</li>
+<li>
+<a href="./../../core.base_rup/tasks/implement_test_35C1B0AA.html" guid="{BC805E79-736B-42D5-BDC1-B95E7D002312}">Implement Test</a>
+</li>
+<li>
+<a href="./../../core.base_rup/tasks/implement_test_suite_94F58DEC.html" guid="{1C759E0D-B364-4095-A7CF-CD9E39301689}">Implement Test Suite</a>
+</li>
+<li>
+<a href="./../../core.base_rup/tasks/incorporate_design_elements_D3C582B5.html" guid="{5C647173-4E32-4594-96A9-2548B47722FA}">Incorporate Existing Design Elements</a>
+</li>
+<li>
+<a href="./../../core.base_rup/tasks/organize_review_3DD2D5E0.html" guid="{F080799F-6A5B-40B9-ACB1-654A7741CADD}">Organize Review</a>
+</li>
+<li>
+<a href="./../../core.base_rup/tasks/promote_baseline_623F1B0E.html" guid="{9139A97B-D458-490D-A9D5-CDBB86968475}">Promote Baselines</a>
+</li>
+<li>
+<a href="./../../core.base_rup/tasks/prototype_user_interface_C495CB55.html" guid="{76F14467-3F63-4B22-B672-6EA69D0E6C46}">Prototype the User-Interface</a>
+</li>
+<li>
+<a href="./../../core.base_rup/tasks/review_change_request_E7D91346.html" guid="{1CD358DF-3FFC-4281-B3EF-8E3CD76C5900}">Review Change Requests</a>
+</li>
+<li>
+<a href="./../../core.base_rup/tasks/review_code_27AD7580.html" guid="{9EC0DF69-EEE1-4B41-8F48-9FB6B0DB7F72}">Review Code</a>
+</li>
+<li>
+<a href="./../../core.base_rup/tasks/review_the_architecture_D27975CC.html" guid="{35BAFA92-EAF9-41E8-8BDE-AB9B61A68E04}">Review the Architecture</a>
+</li>
+<li>
+<a href="./../../extend.bus_model/tasks/review_the_business_object_model_1A938836.html" guid="{6B6B459B-A5EA-43B4-BE8E-ED8DC9A9E2C6}">Review the Business Analysis Model</a>
+</li>
+<li>
+<a href="./../../core.base_rup/tasks/review_the_design_34CB80A9.html" guid="{9574768B-7886-40C9-9938-A7E36E9B0739}">Review the Design</a>
+</li>
+<li>
+<a href="./../../core.base_rup/tasks/structure_implementation_model_E0E0DEF9.html" guid="{35272424-8A0A-4DDD-BA74-C91B80A8D046}">Structure the Implementation Model</a>
+</li>
+<li>
+<a href="./../../core.base_rup/tasks/structure_the_test_implementation_AAB73625.html" guid="{ED9DF0C0-744A-443A-AEBA-604382E05A5F}">Structure the Test Implementation</a>
+</li>
+<li>
+<a href="./../../core.base_rup/tasks/submit_change_request_29FC7F2E.html" guid="{1393CA8E-5CA4-4494-93FE-587F51931896}">Submit Change Request</a>
+</li>
+<li>
+<a href="./../../core.base_rup/tasks/subsystem_design_5D1BCC0C.html" guid="{CAA385CA-2BA2-40F2-8FE3-E21089D02119}">Subsystem Design</a>
+</li>
+<li>
+<a href="./../../core.base_rup/tasks/use_case_analysis_A6990185.html" guid="{28014615-A62F-452D-B821-30C7CAB0EC44}">Use-Case Analysis</a>
+</li>
+</ul>
+</td><td class="sectionTableCell"><span class="sectionTableCellHeading">Output From:
+ </span>
+<ul>
+<li>
+<a href="./../../core.base_rup/tasks/prepare_project_specific_guidelines_A9AD00DB.html" guid="{1E706674-C1E7-4F8D-BF06-35FFE49C5E42}">Prepare Guidelines for the Project</a>
+</li>
+</ul>
+</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Description</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Brief Outline</th><td class="sectionTableCell"><a id="BriefOutline" name="BriefOutline"></a><a id="XE_project_specific_guidelines__brief_outline_for" name="XE_project_specific_guidelines__brief_outline_for"></a>
+<p>
+ The outline is dependent on which work products the project will be producing. Usually there is at least one
+ section for each work product.
+</p></td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Illustrations </div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Examples</th><td class="sectionTableCell">
+<ul>
+<li>
+<a href="./../../extend.formal_resources/guidances/examples/ada_programming_guidelines_2CB877AB.html" guid="3.1104257136136616E-306">Ada Programming Guidelines</a>
+</li>
+<li>
+<a href="./../../extend.formal_resources/guidances/examples/c_programming_guidelines_B478FD25.html" guid="8.54208995842223E-307">C++ Programming Guidelines</a>
+</li>
+<li>
+<a href="./../../extend.formal_resources/guidances/examples/java_programming_guidelines_610E123D.html" guid="1.3628340882022857E-305">Java Programming Guidelines</a>
+</li>
+<li>
+<a href="./../../extend.formal_resources/guidances/examples/use_case_modeling_guidelines_5BA25C7E.html" guid="2.8656499327717044E-305">Use Case Modeling Guidelines</a>
+</li>
+<li>
+<a href="./../../core.informal_resources/guidances/examples/csps_creative_design_brief_-_inception_phase_CCF826E0.html" guid="2.378087492409832E-305">CSPS Creative Design Brief - Inception Phase</a>
+</li>
+<li>
+<a href="./../../core.informal_resources/guidances/examples/csps_design_comps_-_inception_phase_552DF77F.html" guid="2.3075412126614355E-305">CSPS Design Comps - Inception Phase</a>
+</li>
+</ul>
+</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Key Considerations</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<td class="sectionTableSingleCell"><p>
+ Guidelines are typically selected from an underlying repository controlled by the process group in the organization.
+ This work product is a place holder for the specific guidelines selected for the project.
+</p></td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Tailoring</div>
+<div class="sectionContent">
+<table cellpadding="0" cellspacing="0" border="0" class="sectionTable">
+<tr valign="top">
+<th scope="row" class="sectionTableHeading">Representation Options</th><td class="sectionTableCell"><a id="Tailoring" name="Tailoring"></a>
+<p>
+ Which guidelines to provide varies from project to project, and is based on what is available at the time of project
+ execution. Guidelines might be specific to the production of a certain work product, or they might describe a specific
+ technique.
+</p>
+<p>
+ Each guideline should be tailored to fit the specific context of the project.
+</p>
+<p>
+ <br />
+</p></td>
+</tr>
+</table>
+</div>
+<table cellpadding="0" cellspacing="0" border="0" class="copyright">
+<tr>
+<td class="copyright"><p>
+ © Copyright IBM Corp. 1987, 2006. All Rights Reserved.
+</p></td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+</body>
+<script language="JavaScript" type="text/javascript">
+ contentPage.onload();
+ </script>
+</html>
diff --git a/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/resources/test_first_design_21C77ADF.html b/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/resources/test_first_design_21C77ADF.html
new file mode 100644
index 0000000..ae64e54
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/resources/test_first_design_21C77ADF.html
@@ -0,0 +1,204 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN""http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en" xml:lang="en" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
+<head>
+<META http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>Guideline: Test-first Design</title>
+<meta name="uma.type" content="Guideline">
+<meta name="uma.name" content="test_first_design">
+<meta name="uma.presentationName" content="Test-first Design">
+<meta name="element_type" content="other">
+<meta name="filetype" content="description">
+<meta name="role" content="">
+<link rel="StyleSheet" href="./../../../css/default.css" type="text/css">
+<script src="./../../../scripts/ContentPageResource.js" type="text/javascript" language="JavaScript"></script><script src="./../../../scripts/ContentPageSection.js" type="text/javascript" language="JavaScript"></script><script src="./../../../scripts/ContentPageSubSection.js" type="text/javascript" language="JavaScript"></script><script src="./../../../scripts/ContentPageToolbar.js" type="text/javascript" language="JavaScript"></script><script src="./../../../scripts/contentPage.js" type="text/javascript" language="JavaScript"></script><script type="text/javascript" language="JavaScript">
+ var backPath = './../../../';
+ var imgPath = './../../../images/';
+ var nodeInfo=null;
+ contentPage.preload(imgPath, backPath, nodeInfo, '', false, false, false);
+ </script>
+</head>
+<body>
+<div id="breadcrumbs"></div>
+<table border="0" cellpadding="0" cellspacing="0" width="100%">
+<tr>
+<td valign="top"><a name="Top"></a>
+<div id="page-guid" value="_0Y6kUMlgEdmt3adZL5Dmdw"></div>
+<table border="0" cellspacing="0" cellpadding="0" width="100%">
+<tr>
+<td class="pageTitle" nowrap="true">Guideline: Test-first Design</td><td width="100%">
+<div align="right" id="contentPageToolbar"></div>
+</td><td width="100%" class="expandCollapseLink" align="right"><a name="mainIndex" href="./../../../index.htm"></a><script language="JavaScript" type="text/javascript" src="./../../../scripts/treebrowser.js"></script></td>
+</tr>
+</table>
+<table width="100%" border="0" cellpadding="0" cellspacing="0">
+<tr>
+<td class="pageTitleSeparator"><img src="./../../../images/shim.gif" alt="" title="" height="1"></td>
+</tr>
+</table>
+<div class="overview">
+<table width="97%" border="0" cellspacing="0" cellpadding="0">
+<tr>
+<td width="50"><img src="./../../../images/guidance.gif" alt="" title=""></td><td>
+<table class="overviewTable" border="0" cellspacing="0" cellpadding="0">
+<tr>
+<td valign="top">This guideline explains how to apply test-first design.</td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Relationships</div>
+<div class="sectionContent">
+<table class="sectionTable" border="0" cellspacing="0" cellpadding="0">
+<tr valign="top">
+<th class="sectionTableHeading" scope="row">Related Elements</th><td class="sectionTableCell">
+<ul>
+<li>
+<a href="./../../../openup/tasks/implement_solution_5D5698C8.html" guid="_0hyzgMlgEdmt3adZL5Dmdw">Implement the Solution</a>
+</li>
+<li>
+<a href="./../../../openup/tasks/implement_developer_tests_F186F76F.html" guid="_0iL1EMlgEdmt3adZL5Dmdw">Implement Developer Tests</a>
+</li>
+<li>
+<a href="./../../../openup/tasks/run_developer_tests_73D7DBC4.html" guid="_0iYCUMlgEdmt3adZL5Dmdw">Run Developer Tests</a>
+</li>
+<li>
+<a href="./../../../openup/guidances/guidelines/refactoring_33F165CA.html" guid="_OlyWoOX7Edu8VZPtlaU33g">Refactoring</a>
+</li>
+<li>
+<a href="./../../../openup/guidances/guidelines/evolve_the_design_3C9D6965.html" guid="_C4U9QPTeEduDKIuqTXQ8SA">Evolve the Design</a>
+</li>
+<li>
+<a href="./../../../openup/workproducts/developer_test_8470ED13.html" guid="_0YuXEclgEdmt3adZL5Dmdw">Developer Test</a>
+</li>
+<li>
+<a href="./../../../openup/disciplines/development_B5D1D8A.html" guid="_0TeDoMlgEdmt3adZL5Dmdw">Development</a>
+</li>
+</ul>
+</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Main Description</div>
+<div class="sectionContent">
+<table class="sectionTable" border="0" cellspacing="0" cellpadding="0">
+<tr valign="top">
+<td class="sectionTableSingleCell"><h3>
+ Introduction
+</h3>
+<p>
+ With Test-First Design (TFD) you do detailed design in a just-in-time (JIT) manner via writing a single test before
+ writing just enough production code to fulfill that test. When you have new functionality to add to your system,
+ perform the following steps:
+</p>
+<ol>
+ <li>
+ <strong>Quickly add a developer test</strong>. You need just enough implementation code to fail. For example,
+ a new method about to be added to a class could be created that just throws a fatal exception.
+ </li>
+ <li>
+ <strong>Run your tests</strong>. You will typically run the complete test suite, although for sake of speed you may
+ decide to run only a subset. The goal is to ensure that the new test does in fact fail.
+ </li>
+ <li>
+ <strong>Update your production code</strong>. The goal is to add just enough functionality so that the code
+ passes the new test.
+ </li>
+ <li>
+ <strong>Run your test suite again</strong>. If they tests fail you need to update your functional code and retest.
+ Once the tests pass, start over.
+ </li>
+</ol><br />
+<p>
+ <img height="600" alt="Test First Design Flow" src="./../../../openup/guidances/guidelines/./resources/test_first_design.jpg" width="294" />
+</p>
+<h4>
+ Why TFD?
+</h4>
+<p>
+ A significant advantage of TFD is that it enables you to take small steps when writing software, which is not only
+ safer it is also far more productive than writing code in large steps. For example, assume you add some new functional
+ code, compile, and test it. Chances are pretty good that your tests will be broken by defects that exist in the new
+ code. It is much easier to find, and then fix, those defects if you've written five new lines of code than fifty lines.
+ The implication is that the faster your compiler and regression test suite, the more attractive it is to proceed in
+ smaller and smaller steps.
+</p>
+<p>
+ There are other other common testing strategies (listed here in order of effectiveness).
+</p>
+<ol>
+ <li>
+ <strong>Write several tests first</strong>. This is a variant of TFD where you write more than one test before
+ writing just enough production code to fulfill those tests. The advantage is that you don't need to build your
+ system as often, potentially saving time. It has the disadvantage that you will write more production code at once,
+ increasing the difficulty of finding the cause of new bugs.
+ </li>
+ <li>
+ <strong>Test after the fact</strong>. With this approach you write some production code then you write enough
+ testing code to validate it. This has the advantage that you're at least still validating the code but has the
+ disadvantage that you lose the design benefit inherent in writing the testing code first.
+ </li>
+</ol><br />
+<h3>
+ Good Things to Know
+</h3>
+<p>
+ 1. An underlying assumption of TFD is that a unit-testing framework is available. Agile software developers often use
+ the xUnit family of open source tools, such as <a href="http://www.junit.org/"><strong>JUnit</strong></a> or <a href="http://www.vbunit.org/"><strong>VBUnit</strong></a>, although commercial tools are also viable options.
+</p>
+<p>
+ 2. Test-Driven Design (TDD) = TFD + <a class="elementLink" href="./../../../openup/guidances/concepts/refactoring_1B63BA3B.html" guid="_Poc7IPDzEdqYgerqi84oCA">Refactoring</a>
+</p>
+<p>
+ 3. TFD/TDD is commonly used with object-oriented business code, although this approach can be taken with procedural
+ code, user-interface code, and database code.
+</p></td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">More Information</div>
+<div class="sectionContent">
+<table class="sectionTable" border="0" cellspacing="0" cellpadding="0">
+<tr valign="top">
+<th class="sectionTableHeading" scope="row">Concepts</th><td class="sectionTableCell">
+<ul>
+<li>
+<a href="./../../../openup/guidances/concepts/refactoring_1B63BA3B.html" guid="_Poc7IPDzEdqYgerqi84oCA">Refactoring</a>
+</li>
+<li>
+<a href="./../../../openup/guidances/concepts/test_first_design_E01F3CB8.html" guid="_s7YkUBD2EdyfbNOwzwtrjw">Test-first Design</a>
+</li>
+</ul>
+</td>
+</tr>
+<tr valign="top">
+<th class="sectionTableHeading" scope="row">Guidelines</th><td class="sectionTableCell">
+<ul>
+<li>
+<a href="./../../../openup/guidances/guidelines/refactoring_33F165CA.html" guid="_OlyWoOX7Edu8VZPtlaU33g">Refactoring</a>
+</li>
+</ul>
+</td>
+</tr>
+</table>
+</div>
+<table class="copyright" border="0" cellspacing="0" cellpadding="0">
+<tr>
+<td class="copyright"><p>
+ This program and the accompanying materials are made available under the<br />
+ <a href="http://www.eclipse.org/org/documents/epl-v10.php" target="_blank">Eclipse Public License v1.0</a> which
+ accompanies this distribution.
+</p><p/><p>
+ <a class="elementLink" href="./../../../openup/guidances/supportingmaterials/openup_copyright_C3031062.html" guid="_UaGfECcTEduSX6N2jUafGA">OpenUP Copyright</a>.
+</p></td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+</body>
+<script type="text/javascript" language="JavaScript">
+ contentPage.onload();
+ </script>
+</html>
diff --git a/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/resources/top.gif b/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/resources/top.gif
new file mode 100644
index 0000000..615acf4
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/resources/top.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/test_driven_development.xmi b/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/test_driven_development.xmi
new file mode 100644
index 0000000..f5330ef
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/guidances/concepts/test_driven_development.xmi
@@ -0,0 +1,62 @@
+<?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="-1ydZfAL3PacfKwqzAF6hUw"
+ name="test_driven_development,_aI-NgJ04EdyQ3oTO93enUw" guid="-1ydZfAL3PacfKwqzAF6hUw"
+ changeDate="2007-11-27T14:32:00.173-0800">
+ <mainDescription><p>
+ Test driven development&nbsp;is the practice of writing&nbsp;developer tests and&nbsp;implementation code concurrently
+ and at a very fine level of granularity.
+</p>
+<p>
+ In&nbsp;test driven&nbsp;design, the developer first writes a small portion of a&nbsp;developer test, and then writes
+ just enough&nbsp;implementation code to make that&nbsp;developer test compile and execute. Then they write a little bit
+ more of the test and then add enough code to make that new bit compile and pass. This cycle can last somewhere between
+ 30 seconds and five minutes. Rarely does it grow to ten minutes. In each cycle, the tests come first. Once a unit test
+ is done, the&nbsp;developer goes on to the next test until there are no more tests to be written for the implementation
+ of the work item currently under development.
+</p>
+<p>
+ The practice of test driven development changes how&nbsp;the developer&nbsp;thinks. Tests are not written as an
+ afterthought. Instead, developer tests are written as part of the everyday, every minute way of building software.
+</p>
+<p>
+ What are&nbsp;the advantages of test driven design?
+</p>
+<ol>
+ <li>
+ Assumptions in the design are analyzed before the implementation code is written. To write developer tests, an
+ examination must be made of the behavior of each piece of code to be written, correct and incorrect behaviors must
+ be defined. In&nbsp;a way, writing the tests before the code can be considered a version of detailed design.
+ </li>
+ <li>
+ Code units designed&nbsp;for testability up front are cleaner and more loosely coupled.
+ </li>
+ <li>
+ Errors&nbsp;are found earlier. Errors or gaps in the requirements and design are identified before coding begins
+ when it could be more tempting to move ahead based on assumptions.
+ </li>
+ <li>
+ A clearer&nbsp;collaboration strategy between the developer and others that might be responsible for the
+ requirements, architecture, and design is put in place.&nbsp;During the creation of the tests, there must be a
+ meeting of the minds as to what&nbsp;has been specified. After that, the implementation can carry on with
+ confidence that there is a shared vision of what the code should do.
+ </li>
+ <li>
+ There are unambiguous criteria for completion of the code. When the tests pass, the code is working as specified.
+ Non-functional quality dimensions can be dealt with separately, but there is a clear moment when the code behaves
+ correctly.
+ </li>
+ <li>
+ The technique drives the developer to work in smaller increments with faster quality feedback. At any time the
+ developer is just one test away from having error-free code.
+ </li>
+ <li>
+ There is a separation of concerns and effort between getting code working and improving the quality of the code
+ that already runs correctly. Separating out these two areas of concern provides focus and time management support
+ to a developer who in one pass over the implementation makes it pass the tests as simply as possible and then in a
+ subsequent pass, looks for areas to improve.
+ </li>
+</ol></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.test_driven_development.base/guidances/examples/resources/tdd_in_context.bmp b/praclib/temp/practice.tech.test_driven_development.base/guidances/examples/resources/tdd_in_context.bmp
new file mode 100644
index 0000000..840d43e
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/guidances/examples/resources/tdd_in_context.bmp
Binary files differ
diff --git a/praclib/temp/practice.tech.test_driven_development.base/guidances/examples/using_tdd_in_context.xmi b/praclib/temp/practice.tech.test_driven_development.base/guidances/examples/using_tdd_in_context.xmi
new file mode 100644
index 0000000..e8bb436
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/guidances/examples/using_tdd_in_context.xmi
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:GuidanceDescription 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="-TQU5YH4LPnqigOWvXe8sLA"
+ name="new_example,_QeE7YMCsEdyHnYlsYwuJQw" guid="-TQU5YH4LPnqigOWvXe8sLA" authors="Jim Ruehlin"
+ changeDate="2008-02-01T09:56:43.078-0800" version="7.2.0">
+ <mainDescription><p>
+ The Test Driven Development practice is describes how to use TDD to create a high quality version of the
+ implementation. It should be used in conjunction with other practices or process elements to deliver high quality
+ software. This example illustrates one possible way of utilizing the TDD practice in conjunction with other practices.
+</p>
+<p>
+ This digram describes an evolutionary approach to developing the software by considering just a small part of the
+ system. A brief amount of time is spent considering the possible design, the code is implemented via the TDD practice
+ and&nbsp;the design is reviewed and refactored until high quality software is achieved. The new part of the system is
+ then integrated with the rest of the system, and another small part of the system is selected for development.&nbsp;
+</p>
+<p>
+ <img height="587" alt="" src="resources/tdd_in_context.bmp" width="598" />
+</p></mainDescription>
+</org.eclipse.epf.uma:GuidanceDescription>
diff --git a/praclib/temp/practice.tech.test_driven_development.base/guidances/guidelines/developer_testing.xmi b/praclib/temp/practice.tech.test_driven_development.base/guidances/guidelines/developer_testing.xmi
new file mode 100644
index 0000000..3bb5295
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/guidances/guidelines/developer_testing.xmi
@@ -0,0 +1,450 @@
+<?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="-wuu2cNRUPlrBuaO0OdzLFg"
+ name=",_ByOd4O6pEduvoopEslG-4g" guid="-wuu2cNRUPlrBuaO0OdzLFg" changeDate="2008-02-01T10:52:21.849-0800"
+ version="1.0.0">
+ <mainDescription><h3>
+ <a id="DeveloperTestingPitfalls" name="DeveloperTestingPitfalls"></a>Pitfalls Getting Started with Developer Testing
+</h3>
+<p>
+ Many developers who begin trying to do a substantially more thorough job of testing give up the effort shortly
+ thereafter. They find that it does not seem to be yielding value. Further, some developers who begin well with
+ developer testing find that they've created an unmaintainable test suite that is eventually abandoned.
+</p>
+<h4>
+ Establish expectations
+</h4>
+<p>
+ Those who find developer testing rewarding do it. Those who view it as a chore find ways to avoid it. This is simply in
+ the nature of most developers in most industries, and treating it as a shameful lack of discipline hasn't historically
+ been successful. Therefore, as a developer you should expect testing to be rewarding and do what it takes to make it
+ rewarding.
+</p>
+<p>
+ Ideal developer testing follows a very tight edit-test loop. You make a small change to the product, such as adding a
+ new method to a class, then you immediately rerun your tests. If any test breaks, you know exactly what code is the
+ cause. This easy, steady pace of development is the greatest reward of developer testing. A long debugging session
+ should be exceptional.
+</p>
+<p>
+ Because it's not unusual for a change made in one class to break something in another, you should expect to rerun not
+ just the changed class's tests, but many tests. Ideally, you rerun the complete test suite for your implementation
+ element many times per hour. Every time you make a significant change, you rerun the suite, watch the results, and
+ either proceed to the next change or fix the last change. Expect to spend some effort making that rapid feedback
+ possible.
+</p>
+<h4>
+ Automate your tests
+</h4>
+<p>
+ Running tests often is not practical if tests are manual. For some implementation elements, automated tests are easy.
+ An example would be an in-memory database. It communicates to its clients through an API and has no other interface to
+ the outside world. Tests for it would look something like this:
+</p>
+<blockquote>
+<pre>
+/* Check that elements can be added at most once. */
+// Setup
+Database db = new Database();
+db.add("key1", "value1");
+// Test
+boolean result = db.add("key1", "another value");
+expect(result == false);
+</pre>
+</blockquote>
+<p>
+ The tests are different from ordinary client code in only one way: instead of believing the results of API calls, they
+ check. If the API makes client code easy to write, it makes test code easy to write. If the test code is <i>not</i>
+ easy to write, you've received an early warning that the API could be improved. Test-first design is thus consistent
+ with the iterative processes' focus on addressing important risks early.
+</p>
+<p>
+ The more tightly connected the element is to the outside world, however, the harder it will be to test. There are two
+ common cases: graphical user interfaces and back-end components.
+</p>
+<h5>
+ Graphical user interfaces
+</h5>
+<p>
+ Suppose the database in the example above receives its data via a callback from a user-interface object. The callback
+ is invoked when the user fills in some text fields and pushes a button. Testing this by manually filling in the fields
+ and pushing the button isn't something you want to do many times an hour. You must arrange a way to deliver the input
+ under programmatic control, typically by "pushing" the button in code.
+</p>
+<p>
+ Pushing the button causes some code in the implementation element to be executed. Most likely, that code changes the
+ state of some user-interface objects. So you must also arrange a way to query those objects programmatically.
+</p>
+<h5>
+ Back-end components
+</h5>
+<p>
+ Suppose the element under test doesn't implement a database. Instead, it's a wrapper around a real, on-disk database.
+ Testing against that real database might be difficult. It might be hard to install and configure. Licenses for it might
+ be expensive. The database might slow down the tests enough that you're not inclined to run them often. In such cases,
+ it's worthwhile to "stub out" the database with a simpler element that does just enough to support the tests.
+</p>
+<p>
+ Stubs are also useful when a component that your element talks to isn't ready yet. You don't want your testing to wait
+ on someone else's code.
+</p>
+<h4>
+ Don't write your own tools
+</h4>
+<p>
+ Developer testing seems pretty straightforward. You set up some objects, make a call through an API, check the result,
+ and announce a test failure if the results aren't as expected. It's also convenient to have some way to group tests so
+ that they can be run individually or as complete suites. Tools that support those requirements are called <i>test
+ frameworks</i>.
+</p>
+<p>
+ Developer testing <b>is</b> straightforward, and the requirements for test frameworks are not complicated. If, however,
+ you yield to the temptation of writing your own test framework, you'll spend much more time tinkering with the
+ framework than you probably expect. There are many test frameworks available, both commercial and open source, and
+ there's no reason not to use one of those.
+</p>
+<h4>
+ Do create support code
+</h4>
+<p>
+ Test code tends to be repetitive. It's common to see sequences of code like this:
+</p>
+<blockquote>
+<pre>
+// null name not allowed
+retval = o.createName(""); 
+expect(retval == null);
+// leading spaces not allowed
+retval = o.createName(" l"); 
+expect(retval == null);
+// trailing spaces not allowed
+retval = o.createName("name "); 
+expect(retval == null);
+// first character may not be numeric
+retval = o.createName("5allpha"); 
+expect(retval == null);
+</pre>
+</blockquote>
+<p>
+ This code is created by copying one check, pasting it, then editing it to make another check.
+</p>
+<p>
+ The danger here is twofold. If the interface changes, much editing will have to be done. (In more complicated cases, a
+ simple global replacement won't suffice.) Also, if the code is at all complicated, the intent of the test can be lost
+ amid all the text.
+</p>
+<p>
+ When you find yourself repeating yourself, seriously consider factoring out the repetition into support code. Even
+ though the code above is a simple example, it's more readable and maintainable if written like this:
+</p>
+<blockquote>
+<pre>
+void expectNameRejected(MyClass o, String s) {
+Object retval = o.createName(s);
+expect(retval == null);
+}
+...
+// null name not allowed
+expectNameRejected(o, ""); 
+// leading spaces not allowed.
+expectNameRejected(o, " l"); 
+// trailing spaces not allowed.
+expectNameRejected(o, "name "); 
+// first character may not be numeric.
+expectNameRejected(o, "5alpha"); 
+</pre>
+</blockquote>
+<p>
+ Developers writing tests often err on the side of too much copying-and-pasting. If you suspect yourself of that
+ tendency, it's useful to consciously err in the other direction. Resolve that you will strip your code of all duplicate
+ text.
+</p>
+<h4>
+ Write the tests first
+</h4>
+<p>
+ Writing the tests after the code is a chore. The urge is to rush through it, to finish up and move on. Writing tests
+ before the code makes testing part of a positive feedback loop. As you implement more code, you see more tests passing
+ until finally all the tests pass and you're done. People who write tests first seem to be more successful, and it takes
+ no more time. For more on putting tests first, see <a class="elementLinkWithType"
+ href="./../../../practice.tech.test_driven_development.base/guidances/guidelines/test_driven_development_F581182D.html"
+ guid="_5s_DUJ03EdyQ3oTO93enUw">Guideline: Test Driven Development</a>.
+</p>
+<h4>
+ Keep the tests understandable
+</h4>
+<p>
+ You should expect that you, or someone else, will have to modify the tests later. A typical situation is that a later
+ iteration calls for a change to the element's behavior. As a simple example, suppose the element once declared a square
+ root method like this:
+</p>
+<blockquote>
+ <p>
+ <font size="+0">double sqrt(double x);</font>
+ </p>
+</blockquote>
+<p>
+ In that version, a negative argument caused <font size="+0">sqrt</font> to return NaN ("not a number" from the IEEE
+ 754-1985 <i>Standard for Binary Floating-Point Arithmetic</i>). In the new iteration, the square root method will
+ accept negative numbers and return a complex result:
+</p>
+<blockquote>
+ <p>
+ <font size="+0">Complex sqrt(double x);</font>
+ </p>
+</blockquote>
+<p>
+ Old tests for <font size="+0">sqrt</font> will have to change. That means understanding what they do, and updating them
+ so that they work with the new <font size="+0">sqrt</font>. When updating tests, you must take care not to destroy
+ their bug-finding power. One way that sometimes happens is this:
+</p>
+<blockquote>
+<pre>
+void testSQRT () {
+// Update these tests for Complex 
+// when I have time -- bem
+/*
+double result = sqrt(0.0);
+...
+*/
+}
+</pre>
+</blockquote>
+<p>
+ Other ways are more subtle: the tests are changed so that they actually run, but they no longer test what they were
+ originally intended to test. The end result, over many iterations, can be a test suite that is too weak to catch many
+ bugs. This is sometimes called "test suite decay". A decayed suite will be abandoned, because it's not worth the
+ upkeep.
+</p>
+<p>
+ Test suite decay is less likely in the direct tests for <font size="+0">sqrt</font> than in indirect tests. There will
+ be code that calls <font size="+0">sqrt</font>. That code will have tests. When <font size="+0">sqrt</font> changes,
+ some of those tests will fail. The person who changes <font size="+0">sqrt</font> will probably have to change those
+ tests. Because he's less familiar with them, and because their relationship to the change is less clear, he's more
+ likely to weaken them in the process of making them pass.
+</p>
+<p>
+ When you're creating support code for tests (as urged above), be careful: the support code should clarify, not obscure,
+ the purpose of the tests that use it. A common complaint about object-oriented programs is that there's no one place
+ where anything's done. If you look at any one method, all you discover is that it forwards its work somewhere else.
+ Such a structure has advantages, but it makes it harder for new people to understand the code. Unless they make an
+ effort, their changes are likely to be incorrect or to make the code even more complicated and fragile. The same is
+ true of test code, except that later maintainers are even less likely to take due care. You must head off the problem
+ by writing understandable tests.
+</p>
+<h4>
+ Match the test structure to the product structure
+</h4>
+<p>
+ Suppose someone has inherited your implementation element. They need to change a part of it. They may want to examine
+ the old tests to help them in their new design. They want to update the old tests before writing the code (test-first
+ design).
+</p>
+<p>
+ All those good intentions will go by the wayside if they can't find the appropriate tests. What they'll do is make the
+ change, see what tests fail, then fix those. That will contribute to test suite decay.
+</p>
+<p>
+ For that reason, it's important that the test suite be well structured, and that the location of tests be predictable
+ from the structure of the product. Most usually, developers arrange tests in a parallel hierarchy, with one test class
+ per product class. So if someone is changing a class named <font size="+0">Log</font>, they know the test class is
+ <font size="+0">TestLog</font>, and they know where the source file can be found.
+</p>
+<h4>
+ Let tests violate encapsulation
+</h4>
+<p>
+ You might limit your tests to interacting with your implementation element exactly as client code does, through the
+ same interface that client code uses. However, this has disadvantages. Suppose you're testing a simple class that
+ maintains a doubly linked list:
+</p>
+<p>
+ In particular, you're testing the <font size="+0">DoublyLinkedList.insertBefore(Object existing, Object
+ newObject)</font> method. In one of your tests, you want to insert an element in the middle of the list, then check if
+ it's been inserted successfully. The test uses the list above to create this updated list:
+</p>
+<p>
+ It checks the list correctness like this:
+</p>
+<blockquote>
+<pre>
+// the list is now one longer. 
+expect(list.size()==3);
+// the new element is in the correct position
+expect(list.get(1)==m);
+// check that other elements are still there.
+expect(list.get(0)==a);
+expect(list.get(2)==z);
+</pre>
+</blockquote>
+<p>
+ That seems sufficient, but it's not. Suppose the list implementation is incorrect and backward pointers are not set
+ correctly. That is, suppose the updated list actually looks like this:
+</p>
+<p>
+ If <font size="+0">DoublyLinkedList.get(int index)</font> traverses the list from the beginning to the end (likely),
+ the test would miss this failure. If the class provides <font size="+0">elementBefore</font> and <font
+ size="+0">elementAfter</font> methods, checking for such failures is straightforward:
+</p>
+<blockquote>
+<pre>
+// Check that links were all updated
+expect(list.elementAfter(a)==m);
+expect(list.elementAfter(m)==z);
+expect(list.elementBefore(z)==m); //this will fail
+expect(list.elementBefore(m)==a);
+</pre>
+</blockquote>
+<p>
+ But what if it doesn't provide those methods? You could devise more elaborate sequences of method calls that will fail
+ if the suspected defect is present. For example, this would work:
+</p>
+<blockquote>
+<pre>
+// Check whether back-link from Z is correct.
+list.insertBefore(z, x);
+// If it was incorrectly not updated, X will have 
+// been inserted just after A.
+expect(list.get(1)==m); 
+</pre>
+</blockquote>
+<p>
+ But such a test is more work to create and is likely to be significantly harder to maintain. (Unless you write good
+ comments, it will not be at all clear why the test is doing what it's doing.) There are two solutions:
+</p>
+<ol>
+ <li>
+ Add the <font size="+0">elementBefore</font> and <font size="+0">elementAfter</font> methods to the public
+ interface. But that effectively exposes the implementation to everyone and makes future change more difficult.
+ </li>
+ <li>
+ Let the tests "look under the hood" and check pointers directly.
+ </li>
+</ol>
+<p>
+ The latter is usually the best solution, even for a simple class like <font size="+0">DoublyLinkedList</font> and
+ especially for the more complex classes that occur in your products.
+</p>
+<p>
+ Typically, tests are put in the same package as the class they test. They are given protected or friend access.
+</p>
+<h3>
+ <a id="TestDesignMistakes" name="TestDesignMistakes"></a>Characteristic Test Design Mistakes
+</h3>
+<p>
+ Each test exercises an implementation element and checks for correct results. The design of the test-the inputs it uses
+ and how it checks for correctness-can be good at revealing defects, or it can inadvertently hide them. Here are some
+ characteristic test design mistakes.
+</p>
+<h4>
+ Failure to specify expected results in advance
+</h4>
+<p>
+ Suppose you're testing an implementation element that converts XML into HTML. A temptation is to take some sample XML,
+ run it through the conversion, then look at the results in a browser. If the screen looks right, you "bless" the HTML
+ by saving it as the official expected results. Thereafter, a test compares the actual output of the conversion to the
+ expected results.
+</p>
+<p>
+ This is a dangerous practice. Even sophisticated computer users are used to believing what the computer does. You are
+ likely to overlook mistakes in the screen appearance. (Not to mention that browsers are quite tolerant of misformatted
+ HTML.) By making that incorrect HTML the official expected results, you make sure that the test can never find the
+ problem.
+</p>
+<p>
+ It's less dangerous to doubly-check by looking directly at the HTML, but it's still dangerous. Because the output is
+ complicated, it will be easy to overlook errors. You'll find more defects if you write the expected output by hand
+ first.
+</p>
+<h4>
+ Failure to check the background
+</h4>
+<p>
+ Tests usually check that what should have been changed has been, but their creators often forget to check that what
+ should have been left alone has been left alone. For example, suppose a program is supposed to change the first 100
+ records in a file. It's a good idea to check that the 101<sup>st</sup> hasn't been changed.
+</p>
+<p>
+ In theory, you would check that nothing in the "background"-the entire file system, all of memory, everything reachable
+ through the network-has been left alone. In practice, you have to choose carefully what you can afford to check. But
+ it's important to make that choice.
+</p>
+<h4>
+ Failure to check persistence
+</h4>
+<p>
+ Just because the implementation element tells you a change has been made, that doesn't mean it has actually been
+ committed to the database. You need to check the database via another route.
+</p>
+<h4>
+ Failure to add variety
+</h4>
+<p>
+ A test might be designed to check the effect of three fields in a database record, but many other fields need to be
+ filled in to execute the test. Testers will often use the same values over and over again for these "irrelevant"
+ fields. For example, they'll always use the name of their lover in a text field, or 999 in a numeric field.
+</p>
+<p>
+ The problem is that sometimes what shouldn't matter actually does. Every so often, there's a bug that depends on some
+ obscure combination of unlikely inputs. If you always use the same inputs, you stand no chance of finding such bugs. If
+ you persistently vary inputs, you might. Quite often, it costs almost nothing to use a number different than 999 or to
+ use someone else's name. When varying the values used in tests costs almost nothing and it has some potential benefit,
+ then vary. (Note: It's unwise to use names of old lovers instead of your current one if your current lover works with
+ you.)
+</p>
+<p>
+ Here's another benefit. One plausible fault is for the program to use field <i>X</i> when it should have used field
+ <i>Y</i>. If both fields contain "Dawn", the fault can't be detected.
+</p>
+<h4>
+ Failure to use realistic data
+</h4>
+<p>
+ It's common to use made-up data in tests. That data is often unrealistically simple. For example, customer names might
+ be "Mickey", "Snoopy", and "Donald". Because that data is different from what real users enter - for example, it's
+ characteristically shorter - it can miss defects real customers will see. For example, these one-word names wouldn't
+ detect that the code doesn't handle names with spaces.
+</p>
+<p>
+ It's prudent to make a slight extra effort to use realistic data.
+</p>
+<h4>
+ Failure to notice that the code does nothing at all
+</h4>
+<p>
+ Suppose you initialize a database record to zero, run a calculation that should result in zero being stored in the
+ record, then check that the record is zero. What has your test demonstrated? The calculation might not have taken place
+ at all. Nothing might have been stored, and the test couldn't tell.
+</p>
+<p>
+ That example sounds unlikely. But this same mistake can crop up in subtler ways. For example, you might write a test
+ for a complicated installer program. The test is intended to check that all temporary files are removed after a
+ successful installation. But, because of all the installer options, in that test, one particular temporary file wasn't
+ created. Sure enough, that's the one the program forgot to remove.
+</p>
+<h4>
+ Failure to notice that the code does the wrong thing
+</h4>
+<p>
+ Sometimes a program does the right thing for the wrong reasons. As a trivial example, consider this code:
+</p>
+<blockquote>
+<pre>
+if (a &lt; b &amp;&amp; c) 
+return 2 * x;
+else
+return x * x;
+</pre>
+</blockquote>
+<p>
+ The logical expression is wrong, and you've written a test that causes it to evaluate incorrectly and take the wrong
+ branch. Unfortunately, purely by coincidence, the variable X has the value 2 in that test. So the result of the wrong
+ branch is accidentally correct - the same as the result the right branch would have given.
+</p>
+<p>
+ For each expected result, you should ask if there's a plausible way in which that result could be&nbsp;achieved for the
+ wrong reason. While it's often impossible to know, sometimes it's not.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.test_driven_development.base/guidances/guidelines/implementation_refactoring.xmi b/praclib/temp/practice.tech.test_driven_development.base/guidances/guidelines/implementation_refactoring.xmi
new file mode 100644
index 0000000..a71d2df
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/guidances/guidelines/implementation_refactoring.xmi
@@ -0,0 +1,86 @@
+<?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="-i7KKltG_fEgqAjlVlIBGFA"
+ name="implementation_refactoring,_YNx2sJ05EdyQ3oTO93enUw" guid="-i7KKltG_fEgqAjlVlIBGFA"
+ changeDate="2008-02-01T10:51:41.100-0800" version="1.0.0">
+ <mainDescription><p>
+ Refactoring involves improving the quality of existing code without changing the system's behavior. It is explicitly
+ not about adding or changing behavior, but about improving the implementation quality of existing behavior.
+</p>
+<p>
+ A full set of developer tests is required before refactoring can be safely applied. It is critical that the system
+ behavior be in a known, verifiably correct state before modifying the implementation so that you can improve the
+ quality without fear that the modified implementation will break something. Refactoring is a safe transformation to
+ improve code, but it is safe only if there are tests that can verify that the system still works as intended.
+</p>
+<p>
+ Refactoring is initiated when an area that needs improvement is identified in the system by examining either the code
+ or&nbsp;some other&nbsp;representation of the design. The issues identified are sometimes called "smells."
+</p>
+<p>
+ Here are several smells to look for that might lead to implementation refactoring:
+</p>
+<ul>
+ <li>
+ <b>Duplicated code:</b> Duplicated code makes the system harder to understand and harder to maintain.
+ </li>
+ <li>
+ <b>Large design element or method:</b> Large design elements or methods diminish the ability of people to
+ understand the code, reduce the potential for reuse, and make developer testing more difficult.
+ </li>
+ <li>
+ <b>Poorly named element:</b> Whether the element be a variable, function, class, or implementation element, its
+ name should connote what it is so that the code can be maintained.
+ </li>
+</ul>
+<p>
+ As you can see from this list, refactoring can improve the "internals" of an element or&nbsp;the interface of the
+ element. Also, many of the smells&nbsp;are characterized as making the software more difficult to understand; whereas
+ refactoring is about making the system simpler.
+</p>
+<p>
+ After an issue is identified, a refactoring method can be selected that will improve the situation. There are catalogs
+ of refactoring methods available that are change patterns that will fix common problems while retaining the behavior of
+ the system.
+</p>
+<p>
+ These are examples of refactoring methods:
+</p>
+<ul>
+ <li>
+ <b>Extract Method:</b> Pull out the duplicated code into its own single method or extract part of a large method
+ into its own method.
+ </li>
+ <li>
+ <b>Extract Class:</b> Pull some cohesive part of a class into its own class to reduce the size of a design element
+ that is too big.
+ </li>
+ <li>
+ <b>Rename Method</b>, <b>Rename Class</b>, or <b>Rename Variable:</b> Give a more meaningful name to an element to
+ make it more understandable.
+ </li>
+ <li>
+ <b>Extract Interface:</b> Create a clean interface.
+ </li>
+</ul>
+<p>
+ After refactoring has been applied, developer tests are run again to ensure that the system still behaves correctly. It
+ is important that the system is working correctly after each small refactoring. Although many refactorings can be put
+ together to drive broad change across the code base, the tests should run correctly between each refactoring applied.
+ Refactoring must be applied as small behavior-preserving transformations.
+</p>
+<p>
+ As mentioned previously, refactoring requires full developer test coverage of the area under consideration. There are
+ additional techniques that enable refactoring. Coding standards define a common style and make it easier to refactor
+ consistently. An attitude of&nbsp;collective code ownership within the team is important. Each developer should feel
+ that refactoring can be applied across the code base to improve the implementation.
+</p>
+<p>
+ For deeper coverage on this topic, including a listing of "smells" and a catalog of refactorings to respond to them,
+ see [<a class="elementLinkWithUserText"
+ href="./../../../openup/guidances/supportingmaterials/references_6CCF393.html#FOW99"
+ guid="_9ToeIB83Edqsvps02rpOOg">FOW99</a>].
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.test_driven_development.base/guidances/guidelines/mapping_design_to_code.xmi b/praclib/temp/practice.tech.test_driven_development.base/guidances/guidelines/mapping_design_to_code.xmi
new file mode 100644
index 0000000..fc9d0f3
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/guidances/guidelines/mapping_design_to_code.xmi
@@ -0,0 +1,118 @@
+<?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="-4HHmcQny_Q08Xj_3Q7Sfig"
+ name="new_concept,_mlKb8JyJEdy9brKHb521mQ" guid="-4HHmcQny_Q08Xj_3Q7Sfig" changeDate="2007-11-26T17:40:34.381-0800">
+ <mainDescription><h3>
+ <b><a id="Introduction" name="Introduction">Introduction</a></b>
+</h3>
+<p>
+ Design must define enough of the system so that it can be implemented unambiguously. What constitutes enough varies
+ from project to project and company to company.
+</p>
+<p>
+ In some cases the design resembles a sketch, elaborated only far enough to ensure that the implementer can proceed (a
+ "sketch and code" approach). The degree of specification varies with the expertise of the implementer, the complexity
+ of the design, and the risk that the design might be misconstrued.
+</p>
+<p>
+ In other cases, the design is elaborated to the point that the design can be transformed automatically into code. This
+ typically involves extensions to standard UML to represent language and/or environment specific semantics.
+</p>
+<p>
+ The design may also be hierarchical, such as the following:
+</p>
+<ul>
+ <li>
+ a high level design model which sketches an overview of the overall system
+ </li>
+ <li>
+ a subsystem specification model which precisely specifies the required interfaces and behavior of major subsystems
+ within the system
+ </li>
+ <li>
+ a detailed design model for the internals of subsystems
+ </li>
+</ul>
+<p>
+ The sections below describe some different options for relating a design and implementation, and discuss benefits and
+ drawbacks of these approaches.
+</p>
+<h3>
+ <b><a id="sketch" name="sketch">Sketch and Code</a></b>
+</h3>
+<p>
+ One common approach to design is to sketch out the design at a fairly abstract level, and then move directly to code.
+ Maintenance of the design model is manual.
+</p>
+<p>
+ In this approach, we let a design class be an abstraction of several code-level classes. We recommend that you map each
+ design class to one "head" class that, in turn, can use several "helper" classes to perform its behavior. You can use
+ "helper" classes to implement a complex attribute or to build a data structure that you need for the implementation of
+ an operation. In design, you don't model the "helper" classes and you only model the key attributes, relationships, and
+ operations defined by the head class. The purpose of such a model is to abstract away details that can be completed by
+ the implementer.
+</p>
+<p>
+ This approach is extended to apply to the other design model elements. You may have design interfaces which are more
+ abstract than the code-level interfaces, and so on.
+</p>
+<h3>
+ <b><a id="round" name="round">Round-Trip Engineering</a></b>
+</h3>
+<p>
+ In round-trip engineering environments, the design model evolves to a level of detail where it becomes a visual
+ representation of the code. The code and its visual representation are synchronized (with tool support).
+</p>
+<p>
+ The following are some options for representing a Design Model in a round-trip engineering context.
+</p>
+<p>
+ <b><a id="trace" name="trace">High Level Design Model and Detailed Design Model</a></b>
+</p>
+<p>
+ In this approach, there are two levels of design model maintained. Each high level design element is an abstraction of
+ one or more detailed elements in the round-tripped model. For example, a design class may map to one "head" class and
+ several "helper" classes, just as in the "sketch and code" approach described previously. Traceability from the high
+ level design model elements to round-trip model elements can help maintain consistency between the two models.
+</p>
+<p>
+ Although this can help abstract away less important details, this benefit must be balanced against the effort required
+ to maintain consistency between the models.
+</p>
+<p>
+ <b><a id="evolves" name="evolves">Single Evolving Design Model</a></b>
+</p>
+<p>
+ In this approach, there is a single Design Model. Initial sketches of design elements evolve to the point where they
+ can be synchronized with code. Diagrams, such as those used to describe design use-case realizations, initially
+ reference sketched design classes, but eventually reference language-specific classes. High level descriptions of the
+ design are maintained as needed, such as:
+</p>
+<ul>
+ <li>
+ diagrams of the logical structure of the system,
+ </li>
+ <li>
+ subsystem/component specifications,
+ </li>
+ <li>
+ design patterns / mechanisms.<br />
+ </li>
+</ul>
+<p>
+ Such a model is easier to maintain consistent with the implementation.
+</p>
+<h3>
+ <a id="specification" name="specification">Specification and Realization Models</a>
+</h3>
+<p>
+ A related approach is to define the design in terms of specifications for major subsystems, detailed to the point where
+ client implementations can compile against them.
+</p>
+<p>
+ The detailed design of the subsystem realization can be modeled and maintained separately from this specification
+ model.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.test_driven_development.base/guidances/guidelines/resources/refactoring_1B63BA3B.html b/praclib/temp/practice.tech.test_driven_development.base/guidances/guidelines/resources/refactoring_1B63BA3B.html
new file mode 100644
index 0000000..64935dd
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/guidances/guidelines/resources/refactoring_1B63BA3B.html
@@ -0,0 +1,184 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN""http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en" xml:lang="en" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
+<head>
+<META http-equiv="Content-Type" content="text/html; charset=utf-8">
+<title>Concept: Refactoring</title>
+<meta name="uma.type" content="Concept">
+<meta name="uma.name" content="refactoring">
+<meta name="uma.presentationName" content="Refactoring">
+<meta name="element_type" content="concept">
+<meta name="filetype" content="description">
+<meta name="role" content="">
+<link rel="StyleSheet" href="./../../../css/default.css" type="text/css">
+<script src="./../../../scripts/ContentPageResource.js" type="text/javascript" language="JavaScript"></script><script src="./../../../scripts/ContentPageSection.js" type="text/javascript" language="JavaScript"></script><script src="./../../../scripts/ContentPageSubSection.js" type="text/javascript" language="JavaScript"></script><script src="./../../../scripts/ContentPageToolbar.js" type="text/javascript" language="JavaScript"></script><script src="./../../../scripts/contentPage.js" type="text/javascript" language="JavaScript"></script><script type="text/javascript" language="JavaScript">
+ var backPath = './../../../';
+ var imgPath = './../../../images/';
+ var nodeInfo=null;
+ contentPage.preload(imgPath, backPath, nodeInfo, '', false, false, false);
+ </script>
+</head>
+<body>
+<div id="breadcrumbs"></div>
+<table border="0" cellpadding="0" cellspacing="0" width="100%">
+<tr>
+<td valign="top"><a name="Top"></a>
+<div id="page-guid" value="_Poc7IPDzEdqYgerqi84oCA"></div>
+<table border="0" cellspacing="0" cellpadding="0" width="100%">
+<tr>
+<td class="pageTitle" nowrap="true">Concept: Refactoring</td><td width="100%">
+<div align="right" id="contentPageToolbar"></div>
+</td><td width="100%" class="expandCollapseLink" align="right"><a name="mainIndex" href="./../../../index.htm"></a><script language="JavaScript" type="text/javascript" src="./../../../scripts/treebrowser.js"></script></td>
+</tr>
+</table>
+<table width="100%" border="0" cellpadding="0" cellspacing="0">
+<tr>
+<td class="pageTitleSeparator"><img src="./../../../images/shim.gif" alt="" title="" height="1"></td>
+</tr>
+</table>
+<div class="overview">
+<table width="97%" border="0" cellspacing="0" cellpadding="0">
+<tr>
+<td width="50"><img src="./../../../images/concept.gif" alt="" title=""></td><td>
+<table class="overviewTable" border="0" cellspacing="0" cellpadding="0">
+<tr>
+<td valign="top">This concept explains ways of improving the design of existing code in a way that does not alter its external behavior.</td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Relationships</div>
+<div class="sectionContent">
+<table class="sectionTable" border="0" cellspacing="0" cellpadding="0">
+<tr valign="top">
+<th class="sectionTableHeading" scope="row">Related Elements</th><td class="sectionTableCell">
+<ul>
+<li>
+<a href="./../../../openup/guidances/guidelines/refactoring_33F165CA.html" guid="_OlyWoOX7Edu8VZPtlaU33g">Refactoring</a>
+</li>
+<li>
+<a href="./../../../openup/guidances/guidelines/software_reuse_B6B04C26.html" guid="_vO2uoO0OEduUpsu85bVhiQ">Software Reuse</a>
+</li>
+<li>
+<a href="./../../../openup/guidances/concepts/design_E36137FA.html" guid="_bFjlAPTYEduDKIuqTXQ8SA">Design</a>
+</li>
+<li>
+<a href="./../../../openup/guidances/guidelines/evolve_the_design_3C9D6965.html" guid="_C4U9QPTeEduDKIuqTXQ8SA">Evolve the Design</a>
+</li>
+<li>
+<a href="./../../../openup/guidances/guidelines/test_first_design_21C77ADF.html" guid="_0Y6kUMlgEdmt3adZL5Dmdw">Test-first Design</a>
+</li>
+<li>
+<a href="./../../../openup/tasks/implement_solution_5D5698C8.html" guid="_0hyzgMlgEdmt3adZL5Dmdw">Implement the Solution</a>
+</li>
+<li>
+<a href="./../../../openup/tasks/design_solution_A97CE9EA.html" guid="_0fshwMlgEdmt3adZL5Dmdw">Design the Solution</a>
+</li>
+<li>
+<a href="./../../../openup/disciplines/development_B5D1D8A.html" guid="_0TeDoMlgEdmt3adZL5Dmdw">Development</a>
+</li>
+</ul>
+</td>
+</tr>
+</table>
+</div>
+<div class="sectionHeading">Main Description</div>
+<div class="sectionContent">
+<table class="sectionTable" border="0" cellspacing="0" cellpadding="0">
+<tr valign="top">
+<td class="sectionTableSingleCell"><p>
+ Refactoring is a disciplined way to restructure code when small changes are made to the code to improve its design. An
+ important aspect of a refactoring is that it improves the design while not changing the behavior of the design; a
+ refactoring neither adds nor removes functionality.
+</p>
+<p>
+ Refactoring enables you to evolve the code slowly over time, to take an iterative and incremental approach to
+ implementation.
+</p>
+<p>
+ These are the types of refactoring:
+</p>
+<ol>
+ <li>
+ Code refactoring. Often referred to simply as refactoring, this is the refactoring of programming source code.
+ Examples of code refactorings include Rename Method, Encapsulate Field, Extract Class, Introduce Assertion, and
+ Pushdown Method.
+ </li>
+ <li>
+ Database refactoring. A database refactoring is a simple change to a database schema that improves its design while
+ retaining both its behavioral and informational semantics. Examples of database refactorings include Rename Column,
+ Split Table, Move Method to Database, Replace LOB with Table, Introduce Column Constraint, and Use Official Data
+ Source.
+ </li>
+ <li>
+ User interface (UI) refactoring. A UI refactoring is a simple change to the UI which retains its semantics.
+ Examples of UI refactorings include Align Entry Fields, Apply Common Button Size, Apply Common Font, Indicate
+ Format, Reword in Active Voice, and Increase Color Contrast.
+ </li>
+</ol>
+<p>
+ Martin Fowler [<a class="elementLinkWithUserText" href="./../../../openup/guidances/supportingmaterials/references_6CCF393.html#FOW99" guid="_9ToeIB83Edqsvps02rpOOg">FOW99</a>] identifies four key reasons to refactor:
+</p>
+<ul>
+ <li>
+ Refactoring improves the design of software
+ </li>
+ <li>
+ Refactoring makes software easier to understand
+ </li>
+ <li>
+ Refactoring helps you find bugs
+ </li>
+ <li>
+ Refactoring helps you program faster
+ </li>
+</ul>
+<p>
+ Refactoring can improve the design of existing code, but it does not take the place of considering the design before
+ writing code. Refactoring instead changes the role of up-front design, allowing the strictly design work to be more
+ abstract. Small-scale, very tactical decisions can be made during the implementation of the solution with confidence
+ that refactoring will ensure a quality implementation at that level. The designing of the solution before
+ implementation will be more lightweight and focused on broad factors that will drive the implementation.
+</p>
+<p>
+ There is an additional benefit of refactoring: it changes the way a developer thinks about the implementation when not
+ refactoring. The basic task of implementing a solution becomes solely about getting the solution to pass its developer
+ tests in the simplest way possible. Then the design of that solution can be examined and refactored separately. Even if
+ these two things -- implementation of the solution and then improvement -- are just a minute apart, it can be freeing
+ for a developer to single-mindedly create code that causes a test to pass, and then separately single-mindedly improve
+ that code.
+</p>
+<p>
+ These are some additional resources:
+</p>
+<ul>
+ <li>
+ <a href="http://www.refactoring.com/" target="_blank">http://www.refactoring.com/</a>
+ </li>
+ <li>
+ <a href="http://www.agiledata.org/essays/databaseRefactoring.html">http://www.agiledata.org/essays/databaseRefactoring.html</a>
+ </li>
+</ul></td>
+</tr>
+</table>
+</div>
+<table class="copyright" border="0" cellspacing="0" cellpadding="0">
+<tr>
+<td class="copyright"><p>
+ This program and the accompanying materials are made available under the<br />
+ <a href="http://www.eclipse.org/org/documents/epl-v10.php" target="_blank">Eclipse Public License v1.0</a> which
+ accompanies this distribution.
+</p><p/><p>
+ <a class="elementLink" href="./../../../openup/guidances/supportingmaterials/openup_copyright_C3031062.html" guid="_UaGfECcTEduSX6N2jUafGA">OpenUP Copyright</a>.
+</p></td>
+</tr>
+</table>
+</td>
+</tr>
+</table>
+</body>
+<script type="text/javascript" language="JavaScript">
+ contentPage.onload();
+ </script>
+</html>
diff --git a/praclib/temp/practice.tech.test_driven_development.base/guidances/guidelines/resources/test_first_design.jpg b/praclib/temp/practice.tech.test_driven_development.base/guidances/guidelines/resources/test_first_design.jpg
new file mode 100644
index 0000000..6da383c
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/guidances/guidelines/resources/test_first_design.jpg
Binary files differ
diff --git a/praclib/temp/practice.tech.test_driven_development.base/guidances/guidelines/test_driven_development.xmi b/praclib/temp/practice.tech.test_driven_development.base/guidances/guidelines/test_driven_development.xmi
new file mode 100644
index 0000000..8698826
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/guidances/guidelines/test_driven_development.xmi
@@ -0,0 +1,69 @@
+<?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="-mItcFA1WMTAyJvkqMrXuMQ"
+ name="new_guideline,_5s_DUJ03EdyQ3oTO93enUw" guid="-mItcFA1WMTAyJvkqMrXuMQ" changeDate="2007-11-27T14:29:29.987-0800">
+ <mainDescription><h3>
+ Introduction
+</h3>
+<p>
+ With Test Driven Development (TDD) you do detailed design in a just-in-time (JIT) manner via writing a single test
+ before writing just enough production code to fulfill that test. When you have new functionality to add to your system,
+ perform the following steps:
+</p>
+<ol>
+ <li>
+ <strong>Quickly add a developer test</strong>. You need just enough implementation code to fail.&nbsp; For example,
+ a new method about to be added to a class could be created that just throws a fatal exception.
+ </li>
+ <li>
+ <strong>Run your tests</strong>. You will typically run the complete test suite, although for sake of speed you may
+ decide to run only a subset. The goal is to ensure that the new test does in fact fail.
+ </li>
+ <li>
+ <strong>Update your production code</strong>. The goal is to add just enough functionality so that&nbsp;the code
+ passes the new test.&nbsp;
+ </li>
+ <li>
+ <strong>Run your test suite again</strong>. If they tests fail you need to update your functional code and retest.
+ Once the tests pass, start over.
+ </li>
+</ol><br />
+<p>
+ <img height="600" alt="Test First Design Flow" src="./resources/test_first_design.jpg" width="294" />
+</p>
+<h4>
+ Why TDD?
+</h4>
+<p>
+ A significant advantage of TDD is that it enables you to take small steps when writing software, which is not only
+ safer it is also far more productive than writing code in large steps. For example, assume you add some new functional
+ code, compile, and test it. Chances are pretty good that your tests will be broken by defects that exist in the new
+ code. It is much easier to find, and then fix, those defects if you've written five new lines of code than fifty lines.
+ The implication is that the faster your compiler and regression test suite, the more attractive it is to proceed in
+ smaller and smaller steps.
+</p>
+<p>
+ There are other other common testing strategies (listed here in order of effectiveness).
+</p>
+<ol>
+ <li>
+ <strong>Write several tests first</strong>. This is a variant of TDD where you write more than one test before
+ writing just enough production code to fulfill those tests. The advantage is that you don't need to build your
+ system as often, potentially saving time. It has the disadvantage that you will write more production code at once,
+ increasing the difficulty of finding the cause of new bugs.
+ </li>
+ <li>
+ <strong>Test after the fact</strong>. With this approach you write some production code then you write enough
+ testing code to validate it. This has the advantage that you're at least still validating the code but has the
+ disadvantage that you lose the design benefit inherent in writing the testing code first.
+ </li>
+</ol>
+<p>
+ An underlying assumption of TFD is that a unit-testing framework is available. Agile software developers often use the
+ xUnit family of open source tools, such as <a href="http://www.junit.org/"><strong><u><font
+ color="#0000ff">JUnit</font></u></strong></a> or <a href="http://www.vbunit.org/"><strong><u><font
+ color="#0000ff">VBUnit</font></u></strong></a>, although commercial tools are also viable options.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.test_driven_development.base/guidances/guidelines/transforming_design_into_implementation.xmi b/praclib/temp/practice.tech.test_driven_development.base/guidances/guidelines/transforming_design_into_implementation.xmi
new file mode 100644
index 0000000..2a1ae46
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/guidances/guidelines/transforming_design_into_implementation.xmi
@@ -0,0 +1,47 @@
+<?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="-J3oP8D_DIAu9JUZzNOhuKQ"
+ name="transforming_design_into_implementation,_0Y0dsMlgEdmt3adZL5Dmdw" guid="-J3oP8D_DIAu9JUZzNOhuKQ"
+ authors="Jim Ruehlin" changeDate="2008-02-01T10:49:55.008-0800" version="1.0">
+ <mainDescription><p>
+ <b>Transforming</b> the design into code implements the system structure in the chosen source language. It also
+ implements the system behavior defined in the functional requirements. <b>Implementing</b> the system behavior means
+ writing the code that allows different parts of the application (classes or implementation element) to collaborate in
+ realizing the behavior of the system.
+</p>
+<p>
+ There are various techniques for automatically transforming design to implementation. Here are some examples:
+</p>
+<ul>
+ <li>
+ Standard patterns can be applied to generate design and code elements from related design and implementation. For
+ example, a standard transformation pattern can be applied to a data table to create Java&trade; classes to access the
+ data table. Another example is using an <a href="http://www.eclipse.org/emf/" target="_blank">Eclipse Modeling
+ Framework</a> to generate code for storing data that matches the model and to generate a user interface
+ implementation for populating data. A pattern or transformation engine can be used to create the implementation, or
+ the implementation can be done by hand. Pattern engines are easier and more reliable, but handwritten code
+ implementing a defined pattern will have fewer errors than handwritten code implementing a novel or unique design.
+ </li>
+ <li>
+ Models can be detailed and used to generate an implementation. Both structure (class and package diagrams) and
+ behavior diagrams (such as collaboration, state, and activity diagrams) can be used to generate executable code.
+ These initial versions can be further refined as needed.
+ </li>
+ <li>
+ The design may be platform-independent to varying degrees. Platform-specific design models or even code can be
+ generated by transformations that apply various rules to map high-level abstractions of platform-specific elements.
+ This is the focus of the Object Management Group (OMG) Model-Driven Architecture (MDA) <a
+ href="http://www.omg.org/" target="_blank">(http://www.omg.org</a>) initiative.
+ </li>
+ <li>
+ Platform-specific visual models can be used to generate an initial code framework. This framework can be further
+ elaborated with additional code not specified in the design.
+ </li>
+</ul>
+<p>
+ In all cases, however, some design abstraction (classes, implementation elements, and so on) is detailed to become the
+ implementation.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.test_driven_development.base/guidances/roadmaps/adopt_tdd_practice.xmi b/praclib/temp/practice.tech.test_driven_development.base/guidances/roadmaps/adopt_tdd_practice.xmi
new file mode 100644
index 0000000..ac21d24
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/guidances/roadmaps/adopt_tdd_practice.xmi
@@ -0,0 +1,119 @@
+<?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="-CGSI-WD83sE5swSmSDjAYA"
+ name="adopt_tdd_practice,_8yG48JRqEdyrdaw_xGakyw" guid="-CGSI-WD83sE5swSmSDjAYA"
+ authors="Jim Ruehlin" changeDate="2008-02-22T09:59:33.161-0800" version="7.2.0">
+ <mainDescription><h3>
+ Welcome to the Test Driven Development Practice
+</h3>
+<p>
+ If you've just installed the Test Driven Development practice, start by reviewing the concepts of <a
+ class="elementLink"
+ href="./../../../practice.tech.test_driven_development.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"
+ guid="_aI-NgJ04EdyQ3oTO93enUw">Test Driven Development</a>. These will introduce you to the basics of what you need to
+ know about developer testing in&nbsp;the context of&nbsp;TDD. For in-depth information, read this <a
+ class="elementLinkWithUserText"
+ href="./../../../practice.tech.test_driven_development.base/guidances/whitepapers/tdd_practice_whitepaper_5896CCF0.html"
+ 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
+ first.
+</p>
+<p>
+ Tools are critical for creating and managing unit tests. Educate the team on using new tools, and discover which
+ practices and features of the tools will work best in your environment.
+</p>
+<p>
+ Specify modest, attainable goals when adopting TDD. For instance, instead of insisting every code change must have a
+ developer test starting now, it may be better to limit TDD practices&nbsp;to a single important implementation element.
+ This will allow the team to come up to speed on tools and&nbsp;learn new development habits&nbsp;while minimizing the
+ impact on the overall schedule. After the team has gained some comfort with the new way of doing things (usually a
+ couple of weeks or a single iteration), your refined method for TDD can be applied to all new or changed code. Continue
+ increasing the team's capabilities with TDD by introducing new tools, constraints, monitoring, or methods in modest,
+ attainable increments. This also allows the team to experience success with new techniques, which usually leads to a
+ team that embraces rather than resists change.
+</p>
+<p>
+ Like all process changes, adopting TDD requires that team members change behaviors and develop new habits, such writing
+ code only when a test already exists to validate it. Developers will need the education provided by the links on this
+ page and the methods described in this practice to develop these new behaviors. They'll also need to have their new
+ behaviors enforced by the team as a whole, and/or by management, until constantly writing tests while writing code is a
+ habit. TDD is no different from other areas of process adoption. The managing body - bosses or the team - need to put
+ as much effort into creating new behaviors as the individual developers do.
+</p>
+<p>
+ <strong>TDD Adoption Scenario</strong>
+</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
+ 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.
+ </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,
+ 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.
+ </li>
+ <li>
+ Identify and prepare to collect the information or metrics that will tell you how well you're adopting this
+ practice. Make sure the metrics are easy to collect. Highly accurate metrics that are difficult to collect are
+ often abandonded, so provide no value. Coarser measurements that are easy to collect usually provide sufficent
+ information, and it's more likely they'll continue to be collected.
+ </li>
+ <li>
+ Identify the initial, modest&nbsp;goals for your TDD adoption, such as "An average of 2 tests per method for
+ implementation element X". The goal is to be successful at some incremental amount of adoption, not to adopt
+ everything in a single gulp. Make success a regular habit.
+ </li>
+ <li>
+ Select a critical system implementation element to start applying TDD on. Begin using new TDD tools and techniques
+ to develop and test the code.
+ </li>
+ <li>
+ Select a time frame to evaluate the adoption of new TDD techniques. It should be long enough to allow new habits to
+ start to develop, but short enough that changes can be made relativelly quickly. This will generally be sometime
+ between a couple of weeks to a couple of months.
+ </li>
+ <li>
+ Begin to use TDD as described in the practice. Write tests before writing system code.
+ </li>
+ <li>
+ Evaluate your TDD adoption based on the objectives and metrics you defined.
+ </li>
+ <li>
+ Make adjustments based on your evaluation. Eliminate tools or tool features that don't prove effective, and
+ increase practices that are efficient and improve quality.
+ </li>
+ <li>
+ Determine the next step in adoption. Early on, this will be to write tests for more and more implementation
+ elements until TDD is performed on all software for the system. Often, you'll be able to achieve this after just a
+ few evaluation cycles.
+ </li>
+ <li>
+ Continue to examine how your developer testing can be improved. Address problem areas in regular project review
+ meetings. Monitor testing sites (such as the ones referenced on this page), and have individual team members read
+ new articles and books about developer testing. They can report back to the group to generate insight and
+ discussion about more improvements that can be incrementally applied to your TDD practice.
+ </li>
+ <li>
+ Continue to extend or modify this practice to reflect how your team is performing TDD, and what the next increment
+ of adoption should be for your team.
+ </li>
+</ol><br /></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.test_driven_development.base/guidances/supportingmaterials/enablement.xmi b/praclib/temp/practice.tech.test_driven_development.base/guidances/supportingmaterials/enablement.xmi
new file mode 100644
index 0000000..502fd87
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/guidances/supportingmaterials/enablement.xmi
@@ -0,0 +1,46 @@
+<?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="-FCFgETFie9XAhzcc9ZXfSg"
+ name=",_q2WJkOFvEdys887i4S_24Q" guid="-FCFgETFie9XAhzcc9ZXfSg" changeDate="2008-02-22T09:59:43.225-0800">
+ <mainDescription><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
+ href="http://itc.conversationsnetwork.org/shows/detail301.html" target="_blank">Kent Beck presentation</a>. Kent Beck
+ is the creator of XP, which is where TDD was originally defined.
+</p>
+<p>
+ Here are some useful links to expand your understanding of TDD. Make use of these as you learn to enact TDD. Some of
+ these links are also good resources for on-going support and information.
+</p>
+<ul>
+ <li>
+ The <a href="http://en.wikipedia.org/wiki/Test_driven_development" target="_blank">TDD: Wikipedia</a> entry gives
+ an overview of TDD and links to other TDD resources.
+ </li>
+ <li>
+ <a href="http://blog.james-carr.org/?p=44" target="_blank">James Carr's TDD Anti-pattern Catalogue</a> lists some
+ things to avoid when adopting TDD.
+ </li>
+ <li>
+ The <a href="http://blog.james-carr.org/?p=44" target="_blank">TDD Mailing List</a> is a discussion forum for TDD
+ questions and issues.
+ </li>
+ <li>
+ <a href="http://www.testdriven.com/" target="_blank">Testdriven.com</a> is a developer testing site with a wealth
+ of information, news, and partner links about developer testing.
+ </li>
+</ul>
+<p>
+ Once you're familiar with the basics of TDD, browse the capability pattern for the <a class="elementLink"
+ href="./resources/test_driven_development_E3D820A5.html" guid="_k7ZugY8EEdy7q8CKc_B8eg">Test Driven Development
+ Practice</a>. This illustrates the flow between the testing and implementation tasks during test driven development.
+ Select a task to view more detail about what needs to be done to perform the task. If you'll be creating a capability
+ pattern or delivery process that includes TDD, see <a class="elementLink"
+ href="./../../../practice.tech.test_driven_development.base/guidances/examples/using_tdd_in_context_F77E5C22.html"
+ guid="_QeE7YMCsEdyHnYlsYwuJQw">Using the TDD Practice in Context</a>. This shows one example of how TDD can be used in
+ conjunction with other activities and capability patterns to create a pattern for developing software. This is only one
+ possible example - there are many was to use TDD with other development practices.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.test_driven_development.base/guidances/supportingmaterials/release_info_test_driven_development.xmi b/praclib/temp/practice.tech.test_driven_development.base/guidances/supportingmaterials/release_info_test_driven_development.xmi
new file mode 100644
index 0000000..a35aca4
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/guidances/supportingmaterials/release_info_test_driven_development.xmi
@@ -0,0 +1,22 @@
+<?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="-E53fUEmqkW0sT-FCrmpFDw"
+ name="new_supporting_material,__dz3oMuIEdyRPtFYRAKVDg" guid="-E53fUEmqkW0sT-FCrmpFDw"
+ changeDate="2008-01-25T14:24:48.686-0800">
+ <mainDescription><h3>
+ Test Driven Development Practice
+</h3>
+<p>
+ Version 1.0
+</p>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p>
+ [*** NOT YET RELEASED ***]
+ </p>
+ <p>
+ This is the initial release of this practice.
+ </p>
+</blockquote></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.test_driven_development.base/guidances/supportingmaterials/resources/compass.gif b/praclib/temp/practice.tech.test_driven_development.base/guidances/supportingmaterials/resources/compass.gif
new file mode 100644
index 0000000..39f306a
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/guidances/supportingmaterials/resources/compass.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.test_driven_development.base/guidances/supportingmaterials/resources/compassL.gif b/praclib/temp/practice.tech.test_driven_development.base/guidances/supportingmaterials/resources/compassL.gif
new file mode 100644
index 0000000..4117414
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/guidances/supportingmaterials/resources/compassL.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.test_driven_development.base/guidances/termdefinitions/code_instrumentation.xmi b/praclib/temp/practice.tech.test_driven_development.base/guidances/termdefinitions/code_instrumentation.xmi
new file mode 100644
index 0000000..c5096af
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/guidances/termdefinitions/code_instrumentation.xmi
@@ -0,0 +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.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="-xIKYtygbLRgQBa97lxIYxw"
+ name="new_term_definition,_lzAWkK9eEdyltJ0KgEd9WQ" guid="-xIKYtygbLRgQBa97lxIYxw"
+ changeDate="2007-12-20T16:49:57.835-0800">
+ <mainDescription>&nbsp;"Extra" statements added to source code for the purposes of testing, debugging, tuning,&nbsp;or tracing.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.test_driven_development.base/guidances/whitepapers/tdd_practice_whitepaper.xmi b/praclib/temp/practice.tech.test_driven_development.base/guidances/whitepapers/tdd_practice_whitepaper.xmi
new file mode 100644
index 0000000..2d8b327
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/guidances/whitepapers/tdd_practice_whitepaper.xmi
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:GuidanceDescription 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="-2zZV_0MAt_SKIDiWIY3-AA"
+ name="new_whitepaper,_t7IacJRmEdyrdaw_xGakyw" guid="-2zZV_0MAt_SKIDiWIY3-AA" changeDate="2007-11-30T10:22:31.717-0800"
+ version="7.2.0">
+ <mainDescription><p>
+ <span style="FONT-FAMILY: Times"><font size="2">The TDD whitepaper describes the TDD lifecycle as illustrated in this
+ diagram:</font></span>
+</p>
+<p>
+ <span style="FONT-FAMILY: Times"><strong><em>Note: This article describes Test Driven Design, so we may want to
+ reference an article that only descirbes implementation - this practice does not address design. Also, we need to add
+ refactoring to this image. The reference to the whitepaper should probably be changed in the final version to be a
+ shippable whitepaper that includes refactoring.</em></strong></span>
+</p>
+<p align="center">
+ <img src="http://www.agiledata.org/images/tddSteps.jpg" border="0" />
+</p></mainDescription>
+ <attachments><a href="http://www.agiledata.org/essays/tdd.html">Test Driven Design</a></attachments>
+</org.eclipse.epf.uma:GuidanceDescription>
diff --git a/praclib/temp/practice.tech.test_driven_development.base/plugin.xmi b/praclib/temp/practice.tech.test_driven_development.base/plugin.xmi
new file mode 100644
index 0000000..68a6b5a
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/plugin.xmi
@@ -0,0 +1,331 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_DaytUI7-Edy7q8CKc_B8eg"
+ guid="_DaytUI7-Edy7q8CKc_B8eg">
+ <resourceDescriptors xmi:id="_EwjdkJRoEdyrdaw_xGakyw" id="-2zZV_0MAt_SKIDiWIY3-AA"
+ uri="guidances/whitepapers/tdd_practice_whitepaper.xmi"/>
+ <resourceDescriptors xmi:id="_Ce744ZRrEdyrdaw_xGakyw" id="-CGSI-WD83sE5swSmSDjAYA"
+ uri="guidances/roadmaps/adopt_tdd_practice.xmi"/>
+ <resourceDescriptors xmi:id="_IFME0JRtEdyrdaw_xGakyw" id="-EOoqKeF2SEXao6XhNXBD-w"
+ uri="guidances/concepts/developer_testing.xmi"/>
+ <resourceDescriptors xmi:id="_cUUNkJSOEdyVKbgqUOtqQA" id="-UW-yTFk3AppqcGGU-Px63A"
+ uri="tasks/implement_developer_tests.xmi"/>
+ <resourceDescriptors xmi:id="_1JVNAJfIEdyZkIR-s-Y8wQ" id="-H6ob8eA7gz_mOsk8ulSFMQ"
+ uri="tasks/run_developer_tests.xmi"/>
+ <resourceDescriptors xmi:id="_azfFMZfJEdyZkIR-s-Y8wQ" id="-UaDGd7K2rQIFMwCrDuqQKQ"
+ uri="tasks/implement_solution.xmi"/>
+ <resourceDescriptors xmi:id="_wqS44JyJEdy9brKHb521mQ" id="-4HHmcQny_Q08Xj_3Q7Sfig"
+ uri="guidances/guidelines/mapping_design_to_code.xmi"/>
+ <resourceDescriptors xmi:id="_aI2ZEJ01EdyQ3oTO93enUw" id="-xo5gft-2zQGWhxjKcGxSQQ"
+ uri="guidances/concepts/coding_standard.xmi"/>
+ <resourceDescriptors xmi:id="_ewiV4J01EdyQ3oTO93enUw" id="-cev1w72zE7XqPYsSv19prg"
+ uri="guidances/checklists/implementation.xmi"/>
+ <resourceDescriptors xmi:id="_hIY-EZ01EdyQ3oTO93enUw" id="-J3oP8D_DIAu9JUZzNOhuKQ"
+ uri="guidances/guidelines/transforming_design_into_implementation.xmi"/>
+ <resourceDescriptors xmi:id="_kv_hcJ02EdyQ3oTO93enUw" id="-1QQ8ajRx-ZzZnCjhkuaMXQ"
+ uri="workproducts/developer_test.xmi"/>
+ <resourceDescriptors xmi:id="_ODebUZ04EdyQ3oTO93enUw" id="-mItcFA1WMTAyJvkqMrXuMQ"
+ uri="guidances/guidelines/test_driven_development.xmi"/>
+ <resourceDescriptors xmi:id="_aLEfQJ04EdyQ3oTO93enUw" id="-1ydZfAL3PacfKwqzAF6hUw"
+ uri="guidances/concepts/test_driven_development.xmi"/>
+ <resourceDescriptors xmi:id="_YaSosZ05EdyQ3oTO93enUw" id="-i7KKltG_fEgqAjlVlIBGFA"
+ uri="guidances/guidelines/implementation_refactoring.xmi"/>
+ <resourceDescriptors xmi:id="_4DGawJ-wEdyHNcWzRYqQMg" id="-P_LlxVe57r9XOTpngB2ddQ"
+ uri="customcategories/test_driven_dev_practice.xmi"/>
+ <resourceDescriptors xmi:id="_SYfpMK9fEdyltJ0KgEd9WQ" id="-xIKYtygbLRgQBa97lxIYxw"
+ uri="guidances/termdefinitions/code_instrumentation.xmi"/>
+ <resourceDescriptors xmi:id="_BkYGwMCtEdyHnYlsYwuJQw" id="-TQU5YH4LPnqigOWvXe8sLA"
+ uri="guidances/examples/using_tdd_in_context.xmi"/>
+ <resourceDescriptors xmi:id="_qXojsCZ3EdyUaK463Ozu5g" id="-ykYi7xrRdC5O9qFXhU3doA"
+ uri="guidances/concepts/collective_code_ownership.xmi"/>
+ <resourceDescriptors xmi:id="_MdWuYO6qEduvoopEslG-4g" id="-wuu2cNRUPlrBuaO0OdzLFg"
+ uri="guidances/guidelines/developer_testing.xmi"/>
+ <resourceDescriptors xmi:id="_GMGfcMVFEdybJe13vGdZaA" id="-z3O_gW_DHejhovzE53ctgw"
+ uri="guidances/supportingmaterials/measurements.xmi"/>
+ <resourceDescriptors xmi:id="_VvUJ0MuUEdyRPtFYRAKVDg" id="-E53fUEmqkW0sT-FCrmpFDw"
+ uri="guidances/supportingmaterials/release_info_test_driven_development.xmi"/>
+ <resourceDescriptors xmi:id="_DQIX4OFwEdys887i4S_24Q" id="-FCFgETFie9XAhzcc9ZXfSg"
+ uri="guidances/supportingmaterials/enablement.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_DZ1rEI7-Edy7q8CKc_B8eg" name="practice.tech.test_driven_development.base"
+ guid="_DZ1rEI7-Edy7q8CKc_B8eg" authors="Jim Ruehlin" changeDate="2008-01-25T14:22:48.564-0800">
+ <copyrightStatement href="uma://_iVydgENdEdy245g62lfWcA#_cTs20KzREduOqvpk_MDLfQ"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_DZ1rEY7-Edy7q8CKc_B8eg"
+ name="Content" guid="_DZ1rEY7-Edy7q8CKc_B8eg">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_DZ1rEo7-Edy7q8CKc_B8eg"
+ name="Categories" guid="_DZ1rEo7-Edy7q8CKc_B8eg">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_DZ1rE47-Edy7q8CKc_B8eg"
+ name="Domains" guid="_DZ1rE47-Edy7q8CKc_B8eg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_DZ1rFI7-Edy7q8CKc_B8eg"
+ name="Disciplines" guid="_DZ1rFI7-Edy7q8CKc_B8eg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_DZ1rFY7-Edy7q8CKc_B8eg"
+ name="RoleSets" guid="_DZ1rFY7-Edy7q8CKc_B8eg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_DZ1rFo7-Edy7q8CKc_B8eg"
+ name="WP Types" guid="_DZ1rFo7-Edy7q8CKc_B8eg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_DZ1rF47-Edy7q8CKc_B8eg"
+ name="Tools" guid="_DZ1rF47-Edy7q8CKc_B8eg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_DZ1rGI7-Edy7q8CKc_B8eg"
+ name="StandardCategories" guid="_DZ1rGI7-Edy7q8CKc_B8eg"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_DZ1rGY7-Edy7q8CKc_B8eg"
+ name="CustomCategories" guid="_DZ1rGY7-Edy7q8CKc_B8eg">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_DZ1rGo7-Edy7q8CKc_B8eg"
+ name="Hidden" guid="_DZ1rGo7-Edy7q8CKc_B8eg">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_DZ1rG47-Edy7q8CKc_B8eg"
+ name="Custom Categories" guid="_DZ1rG47-Edy7q8CKc_B8eg" categorizedElements="_dLtGEJ-mEdyBk-WQzMU-FQ _pKfmkMuIEdyRPtFYRAKVDg"/>
+ </childPackages>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_dLtGEJ-mEdyBk-WQzMU-FQ"
+ name="test_driven_dev_practice" guid="_dLtGEJ-mEdyBk-WQzMU-FQ" briefDescription="This practice develops tests prior to implementing the code and uses those tests to drive the implementation."
+ presentationName="Test-Driven Development " shapeicon="customcategories/resources/pract_dgm32.gif"
+ nodeicon="customcategories/resources/pract_obj.gif" categorizedElements="_8yG48JRqEdyrdaw_xGakyw _q2WJkOFvEdys887i4S_24Q _QeE7YMCsEdyHnYlsYwuJQw _gKaSQJ_7EdyBk-WQzMU-FQ _ngGGYJ_7EdyBk-WQzMU-FQ _tb7LoJ_7EdyBk-WQzMU-FQ">
+ <presentation xmi:id="-P_LlxVe57r9XOTpngB2ddQ" href="uma://-P_LlxVe57r9XOTpngB2ddQ#-P_LlxVe57r9XOTpngB2ddQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_gKaSQJ_7EdyBk-WQzMU-FQ"
+ name="tasks" guid="_gKaSQJ_7EdyBk-WQzMU-FQ" presentationName="Tasks"
+ shapeicon="customcategories/resources/task_dgm32.gif" nodeicon="customcategories/resources/task_obj.gif"
+ categorizedElements="_znlIcJR9EdyVKbgqUOtqQA _R7atwJfIEdyZkIR-s-Y8wQ _Ht-z8JfJEdyZkIR-s-Y8wQ"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_ngGGYJ_7EdyBk-WQzMU-FQ"
+ name="work_products" guid="_ngGGYJ_7EdyBk-WQzMU-FQ" presentationName="Work Products"
+ shapeicon="customcategories/resources/workproduct_dgm32.gif" nodeicon="customcategories/resources/workproduct_obj.gif"
+ categorizedElements="_kh9FcJ02EdyQ3oTO93enUw _2ZPqEKhNEdymmoKrEVbjiw"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_tb7LoJ_7EdyBk-WQzMU-FQ"
+ name="guidance" guid="_tb7LoJ_7EdyBk-WQzMU-FQ" presentationName="Guidance"
+ shapeicon="customcategories/resources/bookcL.gif" nodeicon="customcategories/resources/bookc.gif">
+ <methodElementProperty xmi:id="_y1LvUJ_7EdyBk-WQzMU-FQ" name="CategoryElementsSortType"
+ value="MethodType"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="#_aGqAsJ01EdyQ3oTO93enUw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="#_ADwlAJRtEdyrdaw_xGakyw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Checklist" href="#_etwusJ01EdyQ3oTO93enUw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="#_YNx2sJ05EdyQ3oTO93enUw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="#_mlKb8JyJEdy9brKHb521mQ"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="#_5s_DUJ03EdyQ3oTO93enUw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="#_hFhQQJ01EdyQ3oTO93enUw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Whitepaper" href="#_t7IacJRmEdyrdaw_xGakyw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="#_aI-NgJ04EdyQ3oTO93enUw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Roadmap" href="#_8yG48JRqEdyrdaw_xGakyw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="#_xYMPoCZnEdyUaK463Ozu5g"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Guideline" href="#_ByOd4O6pEduvoopEslG-4g"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_Poc7IPDzEdqYgerqi84oCA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_pKfmkMuIEdyRPtFYRAKVDg"
+ name="contributions_to_nav_building_blocks" guid="_pKfmkMuIEdyRPtFYRAKVDg"
+ presentationName="Contributions to Navigation Building Blocks" categorizedElements="_ffPy0MuUEdyRPtFYRAKVDg _Fso68MuVEdyRPtFYRAKVDg _LgV-8MuVEdyRPtFYRAKVDg _PMJiUMuVEdyRPtFYRAKVDg _UZjbUMuVEdyRPtFYRAKVDg _gvqcYMuVEdyRPtFYRAKVDg _lTPVQMuVEdyRPtFYRAKVDg _MeD5gMuXEdyRPtFYRAKVDg _RvGVUMuXEdyRPtFYRAKVDg _XsoqwMuXEdyRPtFYRAKVDg _alKngNQxEdyM_J8-fv54DA"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_ffPy0MuUEdyRPtFYRAKVDg"
+ name="release_info.assign" guid="_ffPy0MuUEdyRPtFYRAKVDg" variabilityType="contributes"
+ categorizedElements="__dz3oMuIEdyRPtFYRAKVDg">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCIHYcRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_Fso68MuVEdyRPtFYRAKVDg"
+ name="concept_list.assign" guid="_Fso68MuVEdyRPtFYRAKVDg" variabilityType="contributes"
+ categorizedElements="_aGqAsJ01EdyQ3oTO93enUw _xYMPoCZnEdyUaK463Ozu5g _ADwlAJRtEdyrdaw_xGakyw _aI-NgJ04EdyQ3oTO93enUw">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4Y8RdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_LgV-8MuVEdyRPtFYRAKVDg"
+ name="checklist_list.assign" guid="_LgV-8MuVEdyRPtFYRAKVDg" variabilityType="contributes"
+ categorizedElements="_etwusJ01EdyQ3oTO93enUw">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_pGt9MMReEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_PMJiUMuVEdyRPtFYRAKVDg"
+ name="example_list.assign" guid="_PMJiUMuVEdyRPtFYRAKVDg" variabilityType="contributes"
+ categorizedElements="_QeE7YMCsEdyHnYlsYwuJQw">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4ZMRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_UZjbUMuVEdyRPtFYRAKVDg"
+ name="guideline_list.assign" guid="_UZjbUMuVEdyRPtFYRAKVDg" variabilityType="contributes"
+ categorizedElements="_ByOd4O6pEduvoopEslG-4g _YNx2sJ05EdyQ3oTO93enUw _mlKb8JyJEdy9brKHb521mQ _5s_DUJ03EdyQ3oTO93enUw _hFhQQJ01EdyQ3oTO93enUw">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4ZcRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_gvqcYMuVEdyRPtFYRAKVDg"
+ name="whitepaper_list.assign" guid="_gvqcYMuVEdyRPtFYRAKVDg" variabilityType="contributes"
+ categorizedElements="_t7IacJRmEdyrdaw_xGakyw">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4acRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_lTPVQMuVEdyRPtFYRAKVDg"
+ name="roadmap_list.assign" guid="_lTPVQMuVEdyRPtFYRAKVDg" variabilityType="contributes"
+ categorizedElements="_8yG48JRqEdyrdaw_xGakyw">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4ZsRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_MeD5gMuXEdyRPtFYRAKVDg"
+ name="artifact_list.assign" guid="_MeD5gMuXEdyRPtFYRAKVDg" variabilityType="contributes"
+ categorizedElements="_kh9FcJ02EdyQ3oTO93enUw">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4YMRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_RvGVUMuXEdyRPtFYRAKVDg"
+ name="capability_pattern_list.assign" guid="_RvGVUMuXEdyRPtFYRAKVDg"
+ variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_h-lc4MReEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_XsoqwMuXEdyRPtFYRAKVDg"
+ name="practice_list.assign" guid="_XsoqwMuXEdyRPtFYRAKVDg" variabilityType="contributes"
+ categorizedElements="_dLtGEJ-mEdyBk-WQzMU-FQ">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCIHY8RdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_alKngNQxEdyM_J8-fv54DA"
+ name="technical_practice_list" guid="_alKngNQxEdyM_J8-fv54DA" presentationName="Technical Practices"
+ variabilityType="contributes" categorizedElements="_dLtGEJ-mEdyBk-WQzMU-FQ">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_lBrxENQuEdyM_J8-fv54DA"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_DZ1rHI7-Edy7q8CKc_B8eg"
+ name="CoreContent" guid="_DZ1rHI7-Edy7q8CKc_B8eg">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_iEvlIJMPEdyaRZQqSbPe-w"
+ name="Test Driven development" guid="_iEvlIJMPEdyaRZQqSbPe-w">
+ <contentElements xsi:type="org.eclipse.epf.uma:Whitepaper" xmi:id="_t7IacJRmEdyrdaw_xGakyw"
+ name="tdd_practice_whitepaper" guid="_t7IacJRmEdyrdaw_xGakyw" briefDescription="This whitepaper provides a detailed description of test driven development."
+ presentationName="Test Driven Development">
+ <presentation xmi:id="-2zZV_0MAt_SKIDiWIY3-AA" href="uma://-2zZV_0MAt_SKIDiWIY3-AA#-2zZV_0MAt_SKIDiWIY3-AA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Roadmap" xmi:id="_8yG48JRqEdyrdaw_xGakyw"
+ name="adopt_tdd_practice" guid="_8yG48JRqEdyrdaw_xGakyw" briefDescription="This roadmap describes how to adopt the Test Driven Development (TDD) Practice plug-in."
+ presentationName="How to Adopt this Practice" conceptsAndPapers="_ADwlAJRtEdyrdaw_xGakyw _aI-NgJ04EdyQ3oTO93enUw _t7IacJRmEdyrdaw_xGakyw"
+ examples="_QeE7YMCsEdyHnYlsYwuJQw">
+ <presentation xmi:id="-CGSI-WD83sE5swSmSDjAYA" href="uma://-CGSI-WD83sE5swSmSDjAYA#-CGSI-WD83sE5swSmSDjAYA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_ADwlAJRtEdyrdaw_xGakyw"
+ name="developer_testing" guid="_ADwlAJRtEdyrdaw_xGakyw" briefDescription="Developers regression test their code on a continuous basis to ensure that it works as expected."
+ presentationName="Developer Testing" guidelines="_5s_DUJ03EdyQ3oTO93enUw _ByOd4O6pEduvoopEslG-4g">
+ <presentation xmi:id="-EOoqKeF2SEXao6XhNXBD-w" href="uma://-EOoqKeF2SEXao6XhNXBD-w#-EOoqKeF2SEXao6XhNXBD-w"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_znlIcJR9EdyVKbgqUOtqQA"
+ name="implement_developer_tests" guid="_znlIcJR9EdyVKbgqUOtqQA" briefDescription="Implement one or more tests that enable the validation of the individual implementation elements through execution."
+ presentationName="Implement Developer Tests" conceptsAndPapers="_ADwlAJRtEdyrdaw_xGakyw"
+ output="_kh9FcJ02EdyQ3oTO93enUw">
+ <presentation xmi:id="-UW-yTFk3AppqcGGU-Px63A" href="uma://-UW-yTFk3AppqcGGU-Px63A#-UW-yTFk3AppqcGGU-Px63A"/>
+ <mandatoryInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_Vux8UEfUEdyiPI8btkmvmw"/>
+ <optionalInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_IcQOUEqdEdyi3_jfs__bIQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_R7atwJfIEdyZkIR-s-Y8wQ"
+ name="run_developer_tests" guid="_R7atwJfIEdyZkIR-s-Y8wQ" briefDescription="Run tests against the individual implementation elements to verify that their internal structures work as specified."
+ presentationName="Run Developer Tests" conceptsAndPapers="_ADwlAJRtEdyrdaw_xGakyw">
+ <presentation xmi:id="-H6ob8eA7gz_mOsk8ulSFMQ" href="uma://-H6ob8eA7gz_mOsk8ulSFMQ#-H6ob8eA7gz_mOsk8ulSFMQ"/>
+ <mandatoryInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_Vux8UEfUEdyiPI8btkmvmw"/>
+ <mandatoryInput xsi:type="org.eclipse.epf.uma:Artifact" href="#_kh9FcJ02EdyQ3oTO93enUw"/>
+ <output xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_fahB0EfUEdyiPI8btkmvmw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_Ht-z8JfJEdyZkIR-s-Y8wQ"
+ name="implement_solution" guid="_Ht-z8JfJEdyZkIR-s-Y8wQ" briefDescription="Implement source code to provide new functionality or fix defects."
+ presentationName="Implement Solution" guidelines="_mlKb8JyJEdy9brKHb521mQ">
+ <presentation xmi:id="-UaDGd7K2rQIFMwCrDuqQKQ" href="uma://-UaDGd7K2rQIFMwCrDuqQKQ#-UaDGd7K2rQIFMwCrDuqQKQ"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_Poc7IPDzEdqYgerqi84oCA"/>
+ <mandatoryInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_IcQOUEqdEdyi3_jfs__bIQ"/>
+ <mandatoryInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_i3vkoLS-EduDY8LNbMCDBA"/>
+ <output xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_Vux8UEfUEdyiPI8btkmvmw"/>
+ <output xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_i3vkoLS-EduDY8LNbMCDBA"/>
+ <optionalInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_Vux8UEfUEdyiPI8btkmvmw"/>
+ <optionalInput xsi:type="org.eclipse.epf.uma:Artifact" href="#_kh9FcJ02EdyQ3oTO93enUw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_mlKb8JyJEdy9brKHb521mQ"
+ name="mapping_design_to_code" guid="_mlKb8JyJEdy9brKHb521mQ" briefDescription="This guideline describes some different options for moving from a design to the implementation, and discusses the benefits and drawbacks of these approaches."
+ presentationName="Mapping from Design to Code">
+ <presentation xmi:id="-4HHmcQny_Q08Xj_3Q7Sfig" href="uma://-4HHmcQny_Q08Xj_3Q7Sfig#-4HHmcQny_Q08Xj_3Q7Sfig"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_aGqAsJ01EdyQ3oTO93enUw"
+ name="coding_standard" guid="_aGqAsJ01EdyQ3oTO93enUw" briefDescription="A standard describing various coding conventions used for consistent, quality, understandable implementation."
+ presentationName="Coding Standard">
+ <presentation xmi:id="-xo5gft-2zQGWhxjKcGxSQQ" href="uma://-xo5gft-2zQGWhxjKcGxSQQ#-xo5gft-2zQGWhxjKcGxSQQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Checklist" xmi:id="_etwusJ01EdyQ3oTO93enUw"
+ name="implementation" guid="_etwusJ01EdyQ3oTO93enUw" briefDescription="This checklist provides questions to verify that the implementation is created in a consistent and complete manner."
+ presentationName="Implementation">
+ <presentation xmi:id="-cev1w72zE7XqPYsSv19prg" href="uma://-cev1w72zE7XqPYsSv19prg#-cev1w72zE7XqPYsSv19prg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_hFhQQJ01EdyQ3oTO93enUw"
+ name="transforming_design_into_implementation" guid="_hFhQQJ01EdyQ3oTO93enUw"
+ briefDescription="This guideline describes various techniques for transforming design into implementation."
+ presentationName="Transforming design into implementation ">
+ <presentation xmi:id="-J3oP8D_DIAu9JUZzNOhuKQ" href="uma://-J3oP8D_DIAu9JUZzNOhuKQ#-J3oP8D_DIAu9JUZzNOhuKQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_kh9FcJ02EdyQ3oTO93enUw"
+ name="developer_test" guid="_kh9FcJ02EdyQ3oTO93enUw" briefDescription="A test that validates one specific aspect of an implementation element. "
+ presentationName="Developer Test" guidelines="_5s_DUJ03EdyQ3oTO93enUw">
+ <presentation xmi:id="-1QQ8ajRx-ZzZnCjhkuaMXQ" href="uma://-1QQ8ajRx-ZzZnCjhkuaMXQ#-1QQ8ajRx-ZzZnCjhkuaMXQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_5s_DUJ03EdyQ3oTO93enUw"
+ name="test_driven_development" guid="_5s_DUJ03EdyQ3oTO93enUw" briefDescription="This guideline explains how to apply test driven design."
+ presentationName="Test Driven Development" guidelines="_YNx2sJ05EdyQ3oTO93enUw _ByOd4O6pEduvoopEslG-4g">
+ <presentation xmi:id="-mItcFA1WMTAyJvkqMrXuMQ" href="uma://-mItcFA1WMTAyJvkqMrXuMQ#-mItcFA1WMTAyJvkqMrXuMQ"/>
+ <conceptsAndPapers href="#_aI-NgJ04EdyQ3oTO93enUw"/>
+ <conceptsAndPapers href="#_ADwlAJRtEdyrdaw_xGakyw"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_Poc7IPDzEdqYgerqi84oCA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_aI-NgJ04EdyQ3oTO93enUw"
+ name="test_driven_development" guid="_aI-NgJ04EdyQ3oTO93enUw" briefDescription="This concept describes a technique to bring test design chronologically in-line with software design."
+ presentationName="Test Driven Development">
+ <presentation xmi:id="-1ydZfAL3PacfKwqzAF6hUw" href="uma://-1ydZfAL3PacfKwqzAF6hUw#-1ydZfAL3PacfKwqzAF6hUw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_YNx2sJ05EdyQ3oTO93enUw"
+ name="implementation_refactoring" guid="_YNx2sJ05EdyQ3oTO93enUw" briefDescription="This guideline describes how to apply the refactoring technique to improve the quality of existing code."
+ presentationName="Implementation Refactoring" checklists="_etwusJ01EdyQ3oTO93enUw"
+ guidelines="_5s_DUJ03EdyQ3oTO93enUw">
+ <presentation xmi:id="-i7KKltG_fEgqAjlVlIBGFA" href="uma://-i7KKltG_fEgqAjlVlIBGFA#-i7KKltG_fEgqAjlVlIBGFA"/>
+ <conceptsAndPapers href="#_aGqAsJ01EdyQ3oTO93enUw"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_Poc7IPDzEdqYgerqi84oCA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_2n8hUKNTEdywLvvgt1gQ3Q"
+ name="software_implementation_slot.tdd" guid="_2n8hUKNTEdywLvvgt1gQ3Q"
+ variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_Vux8UEfUEdyiPI8btkmvmw"/>
+ <containedArtifacts xmi:id="_2ZPqEKhNEdymmoKrEVbjiw" name="implementation.tdd"
+ guid="_2ZPqEKhNEdymmoKrEVbjiw" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_JqYbgJ01EdyQ3oTO93enUw"/>
+ </containedArtifacts>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_lzAWkK9eEdyltJ0KgEd9WQ"
+ name="code_instrumentation" guid="_lzAWkK9eEdyltJ0KgEd9WQ" presentationName="code instrumentation">
+ <presentation xmi:id="-xIKYtygbLRgQBa97lxIYxw" href="uma://-xIKYtygbLRgQBa97lxIYxw#-xIKYtygbLRgQBa97lxIYxw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Example" xmi:id="_QeE7YMCsEdyHnYlsYwuJQw"
+ name="using_tdd_in_context" guid="_QeE7YMCsEdyHnYlsYwuJQw" briefDescription="This is one example of how the TDD practice can be used in conjunction with other practices in a development process."
+ presentationName="Using the TDD Practice in Context">
+ <presentation xmi:id="-TQU5YH4LPnqigOWvXe8sLA" href="uma://-TQU5YH4LPnqigOWvXe8sLA#-TQU5YH4LPnqigOWvXe8sLA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_xYMPoCZnEdyUaK463Ozu5g"
+ name="collective_code_ownership" guid="_xYMPoCZnEdyUaK463Ozu5g" briefDescription="This concept explains the value of an atmosphere where any team member can change any piece of code in the system."
+ presentationName="Collective Code Ownership" conceptsAndPapers="_aGqAsJ01EdyQ3oTO93enUw">
+ <presentation xmi:id="-ykYi7xrRdC5O9qFXhU3doA" href="uma://-ykYi7xrRdC5O9qFXhU3doA#-ykYi7xrRdC5O9qFXhU3doA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_ByOd4O6pEduvoopEslG-4g"
+ name="developer_testing" guid="_ByOd4O6pEduvoopEslG-4g" briefDescription="This guideline describes techniques for getting started with developer testing and characteristics of good developer tests."
+ presentationName="Developer Testing" conceptsAndPapers="_ADwlAJRtEdyrdaw_xGakyw"
+ guidelines="_5s_DUJ03EdyQ3oTO93enUw">
+ <presentation xmi:id="-wuu2cNRUPlrBuaO0OdzLFg" href="uma://-wuu2cNRUPlrBuaO0OdzLFg#-wuu2cNRUPlrBuaO0OdzLFg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="__dz3oMuIEdyRPtFYRAKVDg"
+ name="release_info_test_driven_development" guid="__dz3oMuIEdyRPtFYRAKVDg"
+ presentationName="Test Driven Development Release Information">
+ <presentation xmi:id="-E53fUEmqkW0sT-FCrmpFDw" href="uma://-E53fUEmqkW0sT-FCrmpFDw#-E53fUEmqkW0sT-FCrmpFDw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="_q2WJkOFvEdys887i4S_24Q"
+ name="enablement" guid="_q2WJkOFvEdys887i4S_24Q" briefDescription="This material provides enablement material for learning to adopt the Test Driven Design practice."
+ presentationName="Enablement">
+ <presentation xmi:id="-FCFgETFie9XAhzcc9ZXfSg" href="uma://-FCFgETFie9XAhzcc9ZXfSg#-FCFgETFie9XAhzcc9ZXfSg"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_DZ1rHY7-Edy7q8CKc_B8eg"
+ name="CapabilityPatterns" guid="_DZ1rHY7-Edy7q8CKc_B8eg"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_DZ1rHo7-Edy7q8CKc_B8eg"
+ name="DeliveryProcesses" guid="_DZ1rHo7-Edy7q8CKc_B8eg"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_DZ1rH47-Edy7q8CKc_B8eg"
+ name="ProcessContributions" guid="_DZ1rH47-Edy7q8CKc_B8eg"/>
+ <bases href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0ELXuEduGP_98XMd0fg"/>
+ <bases href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2AAouEdyhlpBPrduOMw"/>
+ <bases href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno4EKmEdyrauqpmnA8jQ"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/practice.tech.test_driven_development.base/resources/top.gif b/praclib/temp/practice.tech.test_driven_development.base/resources/top.gif
new file mode 100644
index 0000000..615acf4
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/resources/top.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.test_driven_development.base/tasks/implement_developer_tests.xmi b/praclib/temp/practice.tech.test_driven_development.base/tasks/implement_developer_tests.xmi
new file mode 100644
index 0000000..7444356
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/tasks/implement_developer_tests.xmi
@@ -0,0 +1,96 @@
+<?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.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="-UW-yTFk3AppqcGGU-Px63A"
+ name=",_znlIcJR9EdyVKbgqUOtqQA" guid="-UW-yTFk3AppqcGGU-Px63A" changeDate="2008-02-01T10:24:00.703-0800"
+ version="7.2.0">
+ <mainDescription><p>
+ Developer testing is different from other forms of testing in that it is based on the expected behavior of code units
+ rather than being directly based on the system requirements.
+</p>
+<p>
+ It is best to do this at a small scale, much smaller than the complete code base to be authored by a developer over the
+ course of an iteration. This can be done for one operation, one field added to a user interface, one stored procedure,
+ etc. As the code base is incrementally built, new tests will be authored and existing tests might be revisited to test
+ additional behavior.
+</p></mainDescription>
+ <keyConsiderations><ol>
+ <li>
+ Automate tests via a unit regression testing tool (for example, xUnit) so that tests may be run by developers
+ whenever they make changes to the code.
+ </li>
+ <li>
+ Test to the risk of the implementation element. For example, the more critical an element is, the more important it
+ is to test it thoroughly.
+ </li>
+ <li>
+ Pair with&nbsp;team members with testing skills&nbsp;in all steps of this task to gain insight on testing and
+ quality considerations.
+ </li>
+</ol>
+<p>
+ The&nbsp;<a class="elementLink" href="./../../core.mgmt.slot.base/workproducts/work_items_slot_F12BAC46.html"
+ guid="_1QZI8EfUEdyiPI8btkmvmw">[Work Items]</a> is implicitly used in implementation tasks to manage which requirements
+ or change requests are being realized in the code.
+</p></keyConsiderations>
+ <sections xmi:id="_C_j_EJR-EdyVKbgqUOtqQA" name="Refine scope and identify the test(s)"
+ guid="_C_j_EJR-EdyVKbgqUOtqQA">
+ <sectionDescription><p>
+ Select the increment of work to be tested and identify developer test(s)&nbsp;to verify that the software
+ implementation&nbsp;being developed behaves correctly. One source for the expected behavior for an implementation
+ element is the software design.
+</p>
+<p>
+ In identifying the&nbsp;tests or in any other part of this task, consider collaborating with a team member who is
+ well-versed in the issues of testing.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_Es64wJR-EdyVKbgqUOtqQA" name="Write the test setup" guid="_Es64wJR-EdyVKbgqUOtqQA">
+ <sectionDescription>To successfully run a test the system must be in a known state so that the correct behavior can be defined. Implement the
+setup logic that must be performed as part of the developer test.</sectionDescription>
+ </sections>
+ <sections xmi:id="_Fm4moJR-EdyVKbgqUOtqQA" name="Define the expected results" guid="_Fm4moJR-EdyVKbgqUOtqQA">
+ <sectionDescription><p>
+ Define the expected results of each test so that it can be verified.
+</p>
+<p>
+ After a test runs, you need to be able to compare the results of running the test against what was expected to happen.
+ The test is successful when the actual results match the expected results.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_GZaPwJR-EdyVKbgqUOtqQA" name="Write the test logic" guid="_GZaPwJR-EdyVKbgqUOtqQA">
+ <sectionDescription>Write the steps that perform the actual test(s).</sectionDescription>
+ </sections>
+ <sections xmi:id="_IMxq0JR-EdyVKbgqUOtqQA" name="Define the test response" guid="_IMxq0JR-EdyVKbgqUOtqQA">
+ <sectionDescription>Define the information the test(s) must produce to successfully indicate success or failure. Consider if a response of True
+or False is sufficient, or if a detailed message should be logged as well.</sectionDescription>
+ </sections>
+ <sections xmi:id="_JAiqEJR-EdyVKbgqUOtqQA" name="Write clean-up code" guid="_JAiqEJR-EdyVKbgqUOtqQA">
+ <sectionDescription>Identify, and then implement, the steps to be followed in order to restore the environment to the original state for each
+test. The goal is to ensure that there are no side effects from running the tests.</sectionDescription>
+ </sections>
+ <sections xmi:id="_KkDrQJR-EdyVKbgqUOtqQA" name="Test the test" guid="_KkDrQJR-EdyVKbgqUOtqQA">
+ <sectionDescription><p>
+ Verify that each developer test works correctly. To do this:
+</p>
+<ul>
+ <li>
+ Run the test(s), observe their behavior, and fix any defects in the tests.
+ </li>
+ <li>
+ Ensure that the expected results are defined properly and that they're being checked correctly.
+ </li>
+ <li>
+ Check the clean-up logic for each test.
+ </li>
+ <li>
+ Ensure that each developer test works within your test suite framework.
+ </li>
+</ul></sectionDescription>
+ </sections>
+ <purpose>Prepare to validate an implementation element (e.g. an operation, a class, a stored procedure) through unit testing. The
+result is one or more new developer tests.</purpose>
+ <alternatives>Rely on acceptance tests to validate your software. This will likely be time consuming, late, and not as effective as
+developer testing in identifying bugs and finding their location in the code.</alternatives>
+</org.eclipse.epf.uma:TaskDescription>
diff --git a/praclib/temp/practice.tech.test_driven_development.base/tasks/implement_solution.xmi b/praclib/temp/practice.tech.test_driven_development.base/tasks/implement_solution.xmi
new file mode 100644
index 0000000..a6f4834
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/tasks/implement_solution.xmi
@@ -0,0 +1,163 @@
+<?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.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="-UaDGd7K2rQIFMwCrDuqQKQ"
+ name=",_Ht-z8JfJEdyZkIR-s-Y8wQ" guid="-UaDGd7K2rQIFMwCrDuqQKQ" changeDate="2008-02-01T10:28:08.249-0800"
+ version="7.2.0">
+ <mainDescription><p>
+ Usually, this task is focused on a specific implementation&nbsp;element, such as a class or component, but it does not
+ need to be.
+</p>
+<p>
+ A portion of the design is implemented by performing this task. This task can be performed any number of times during
+ an iteration. In fact it is best to do this task in as small a scope as possible to tighten the loop between it and
+ related tasks involving developer testing and consideration of the design.
+</p></mainDescription>
+ <keyConsiderations><p>
+ It is best when developer tests already exist so there is an unambiguous definition of what behavior is considered
+ correct. The implementation should be immediately tested.
+</p>The <a class="elementLink" href="./../../core.mgmt.slot.base/workproducts/work_items_slot_F12BAC46.html"
+guid="_1QZI8EfUEdyiPI8btkmvmw">[Work Items]</a>&nbsp; is implicitly used in implementation tasks to manage which
+requirements or change requests are being realized in the code.<br /></keyConsiderations>
+ <sections xmi:id="_RiBg4JfJEdyZkIR-s-Y8wQ" name="Determine a strategy" guid="_RiBg4JfJEdyZkIR-s-Y8wQ">
+ <sectionDescription><p>
+ Determine a strategy based on the software design and developer tests&nbsp;for how you are going to implement the
+ solution. The fundamental options are:
+</p>
+<ol>
+ <li>
+ Apply existing, reusable assets.
+ </li>
+ <li>
+ Model the design in detail and generate the source code (by model transformation).
+ </li>
+ <li>
+ Write the source code.
+ </li>
+ <li>
+ Any combination of the above.
+ </li>
+</ol></sectionDescription>
+ </sections>
+ <sections xmi:id="_SW1pAJfJEdyZkIR-s-Y8wQ" name="Identify opportunities for reuse"
+ guid="_SW1pAJfJEdyZkIR-s-Y8wQ">
+ <sectionDescription><p>
+ Identify existing code or other implementation elements that can be reused in the portion of the implementation that
+ you are creating or changing. A comprehensive understanding of the overall design is helpful, because it is best to
+ leverage reuse opportunities when you have a thorough understanding of the proposed solution.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_IVaTAJ-uEdyHNcWzRYqQMg" name="Transform design into implementation"
+ guid="_IVaTAJ-uEdyHNcWzRYqQMg">
+ <sectionDescription><p>
+ If you are using sophisticated modeling tools, you should be able to generate a portion of the required source code
+ from the model. Note that programming is&nbsp;commonly required to complete the implementation after the design model
+ has been transformed into code.
+</p>
+<p>
+ Even without tools, there is&nbsp;typically some amount of code that can be created by rote by examining the design and
+ developer tests.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_TadCIJfJEdyZkIR-s-Y8wQ" name="Write source code" guid="_TadCIJfJEdyZkIR-s-Y8wQ">
+ <sectionDescription><p>
+ Write the source code to make the implementation conform to the design and expected behavior. You should strive to
+ reuse and/or generate code wherever possible, but you will still need to do some programming. To do so, consider the
+ following:
+</p>
+<ul>
+ <li>
+ Examine the technical requirements. Because some requirement information does not translate directly into your
+ design you should examine the requirement(s) to ensure that they are fully realized in the implementation.
+ </li>
+ <li>
+ Refactor your code to improve its design. Refactoring is a technique where you improve the quality of your code via
+ small, safe changes.
+ </li>
+ <li>
+ Tune the results of the existing implementation by improving performance, the user interface, security, and other
+ nonfunctional areas.
+ </li>
+ <li>
+ Add missing details, such as completing the logic of operations or adding supporting classes and data structures
+ </li>
+ <li>
+ Handle boundary conditions.
+ </li>
+ <li>
+ Deal with unusual circumstances or error states.
+ </li>
+ <li>
+ Restrict behavior (preventing users or client code from executing illegal flows, scenarios, or combinations of
+ options).
+ </li>
+ <li>
+ Add critical sections for multi-threaded or re-entrant code.
+ </li>
+</ul>
+<p>
+ Though many different considerations are listed here, there is one clear way to know when the source code is done. The
+ solution has been implemented when it passes the developer tests. Any other considerations can be taken care of in a
+ refactoring pass over the code to improve it once it is complete and correct.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_WpB28JfJEdyZkIR-s-Y8wQ" name="Evaluate the implementation" guid="_WpB28JfJEdyZkIR-s-Y8wQ">
+ <sectionDescription><p>
+ Verify that the implementation is fit for its purpose. Examine the code for its suitability to perform its intended
+ function. This is a quality assurance step that you perform in addition to testing which is described in other tasks.
+ Consider these strategies:
+</p>
+<ul>
+ <li>
+ Pair programming. By pairing to implement the code in the first place, you effectively evaluate the code as its
+ being written.
+ </li>
+ <li>
+ Read through the code for common mistakes. Consider keeping a checklist of common mistakes that you make, as a
+ reminder reference.
+ </li>
+ <li>
+ Use tools to check for implementation errors and inappropriate code. For example, use a static code rule checker or
+ set the compiler to the most detailed warning level.
+ </li>
+ <li>
+ Use tools that can visualize the code. Code visualization, such as the UML visualizations in the Eclipse IDE, help
+ developers identify issues such as excessive coupling or circular dependencies.
+ </li>
+ <li>
+ Perform informal, targeted code inspections. Ask colleagues to review small critical sections of code and code with
+ significant churn. Avoid reviewing large sections of code.
+ </li>
+ <li>
+ Use&nbsp;a tester to ensure the implementation is testable and understandable to testing resources.
+ </li>
+</ul>
+<p>
+ Improve the implementation based on the results of these evaluations.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_XjAL4JfJEdyZkIR-s-Y8wQ" name="Communicate significant decisions"
+ guid="_XjAL4JfJEdyZkIR-s-Y8wQ">
+ <sectionDescription><p>
+ Communicate the impact of unexpected changes to the design and requirements.
+</p>
+<p>
+ The issues and constraints that you uncover when you implement the system must be communicated to the team. The impact
+ of issues discovered during implementation must be incorporated into future decisions. If appropriate, update
+ requirements to reflect ambiguities that you identified and resolved in the implementation so they can be tested and
+ you can manage&nbsp;stakeholder expectations appropriately. Similarly, update the design to reflect new constraints and
+ issues uncovered during implementation to be sure that the new information is communicated to other developers.
+</p>
+<p>
+ Usually, there is no need for a change request if the required change is small and the same person is designing and
+ implementing the code element. That individual can make the design change directly. If the required change has a broad
+ impact, it may be necessary to communicate that change to the other team members through a change request.
+</p></sectionDescription>
+ </sections>
+ <purpose><p>
+ The purpose of this task is to produce an implementation for part of the solution (such as a class or component), or to
+ fix one or more defects. The result is typically new or modified source code, which is&nbsp;referred to the
+ implementation.
+</p></purpose>
+</org.eclipse.epf.uma:TaskDescription>
diff --git a/praclib/temp/practice.tech.test_driven_development.base/tasks/run_developer_tests.xmi b/praclib/temp/practice.tech.test_driven_development.base/tasks/run_developer_tests.xmi
new file mode 100644
index 0000000..dda390b
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/tasks/run_developer_tests.xmi
@@ -0,0 +1,63 @@
+<?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.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="-H6ob8eA7gz_mOsk8ulSFMQ"
+ name=",_R7atwJfIEdyZkIR-s-Y8wQ" guid="-H6ob8eA7gz_mOsk8ulSFMQ" changeDate="2008-01-03T16:01:19.313-0800"
+ 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 <a
+ class="elementLink" href="./../../core.tech.slot.base/workproducts/software_build_slot_38848FEE.html"
+ guid="_zjwzEKg_Edyn_rXSpKp-cg">[Software Build]</a>.
+</p>
+<p>
+ Pair with the Tester during all steps of this task to gain insight on testing and quality considerations.
+</p>
+<p>
+ The&nbsp;<a class="elementLink" href="./../../core.mgmt.slot.base/workproducts/work_items_slot_F12BAC46.html"
+ guid="_1QZI8EfUEdyiPI8btkmvmw">[Work Items]</a>&nbsp;is implicitly used in implementation tasks to manage which
+ requirements or change requests are being realized in the code.
+</p></keyConsiderations>
+ <sections xmi:id="_gjLBUJfIEdyZkIR-s-Y8wQ" name="Run developer tests" guid="_gjLBUJfIEdyZkIR-s-Y8wQ">
+ <sectionDescription><p>
+ Run the developer tests.&nbsp;The procedure will vary, depending on whether the test is manual or automated and whether
+ additional test components are necessary,&nbsp;such as&nbsp;drivers or stubs.
+</p>
+<p>
+ To run the tests, you need to make sure that you have initialized the test environment with all necessary elements,
+ such as software, hardware, tools, data, and so on.
+</p>
+<p>
+ Automated tests will often update a test results&nbsp;which you can evaluate to determine where your tests went wrong.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_haRocJfIEdyZkIR-s-Y8wQ" name="Evaluate test execution" guid="_haRocJfIEdyZkIR-s-Y8wQ">
+ <sectionDescription><p>
+ Evaluate the test execution by analyzing the test run.&nbsp;
+</p>
+<p>
+ Testing will&nbsp;complete either&nbsp;normally or abnormally.&nbsp; For correctly implemented tests, a normal
+ completion represents a passed test, though it could warrant additional examination of the test results log to
+ ensure&nbsp;the test&nbsp;ran as expected.&nbsp; Abnormal termination could be premature termination or just a test
+ that does not complete as intended.
+</p>
+<p>
+ Review the test log to understand any reported failures, warnings, or unexpected results. The cause of the problem(s)
+ might be that the implementation&nbsp;element being tested is faulty, a problem with the developer tests, or a problem
+ with the environment.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_itj1QJfIEdyZkIR-s-Y8wQ" name="Respond to test results" guid="_itj1QJfIEdyZkIR-s-Y8wQ">
+ <sectionDescription><p>
+ Determine the appropriate corrective action to recover from a "failed" developer test run. If the implementation
+ element under test is faulty, fix the problem if possible and rerun the tests. If the problem is serious and cannot be
+ immediately addressed, report the defect. If the developer test is faulty fix the test and rerun the tests. If there
+ was a problem with the environment, resolve it and then rerun&nbsp;the tests.
+</p>
+<p>
+ When the developer tests pass, communicate the results. If the passing of these tests represent completion of a
+ requirement, this could involve updating the status of a work item.
+</p></sectionDescription>
+ </sections>
+ <purpose>To verify that the implementation works as specified.</purpose>
+</org.eclipse.epf.uma:TaskDescription>
diff --git a/praclib/temp/practice.tech.test_driven_development.base/workproducts/developer_test.xmi b/praclib/temp/practice.tech.test_driven_development.base/workproducts/developer_test.xmi
new file mode 100644
index 0000000..e318f5b
--- /dev/null
+++ b/praclib/temp/practice.tech.test_driven_development.base/workproducts/developer_test.xmi
@@ -0,0 +1,82 @@
+<?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="-1QQ8ajRx-ZzZnCjhkuaMXQ"
+ name="developer_test,_0YuXEclgEdmt3adZL5Dmdw" guid="-1QQ8ajRx-ZzZnCjhkuaMXQ" changeDate="2008-02-22T10:41:50.489-0800"
+ version="1.0.0">
+ <mainDescription><p>
+ This artifact covers all of the steps that are required to validate a specific aspect of an implementation element. For
+ example, a test could&nbsp;assure that a method's parameters properly accept&nbsp;the uppermost and lowermost values
+ required. A developer test specifies test entries, execution conditions, and expected results. These details are
+ identified for the purpose of evaluating a particular aspect of a scenario.
+</p>
+<p>
+ The collection of developer tests for a specific implementation element should validate that the element performs as
+ specified.
+</p>
+<p>
+ The tests should be self-documenting in a way that makes it clear upon completion of the test whether the
+ implemenetation element has run correctly.
+</p></mainDescription>
+ <purpose>This artifact is used to evaluate whether or not an implementation element performs as specified.</purpose>
+ <impactOfNotHaving>Not having developer tests can inhibit iterative development, because there is no assurance that modified elements are
+still working correctly when you modify elements iteration by iteration.</impactOfNotHaving>
+ <reasonsForNotNeeding>If the tests can be embedded into the actual production code, you might not need a separate work product. Nonetheless, some
+level of support for developer testing is always necessary.</reasonsForNotNeeding>
+ <briefOutline><p>
+ There is no predefined template for this&nbsp;work product and a testing tool will&nbsp;affect how the work product is
+ handled, but here are some key issues that should be addressed:
+</p>
+<ul>
+ <li>
+ Setup
+ </li>
+ <li>
+ Inputs
+ </li>
+ <li>
+ Script
+ </li>
+ <li>
+ Expected Results
+ </li>
+ <li>
+ Evaluation Criteria
+ </li>
+ <li>
+ Clean-Up
+ </li>
+</ul></briefOutline>
+ <representationOptions><p align="left">
+ The following are recommendation and options for representing this work product.
+</p>
+<h4>
+ Recommendation: Automated Code Unit
+</h4>
+<p>
+ The most appropriate technique for running these tests is using code that tests the implementation element scenarios
+ fully and that you can run regularly as you update the system during development.
+</p>
+<p>
+ When code is the&nbsp;sole form of the tests, you must take care to ensure that the code is self-documenting, including
+ specifications of what conditions you are testing and what setup or clean-up is required for the test to run properly.
+</p>
+<h4>
+ Option: Manual Instructions
+</h4>
+<p>
+ In some cases, manual instructions can suffice. For example, when testing a user interface, a Developer could walk
+ through a script, explaining the implementation element. In this case, it can still be valuable to create a test
+ harness that goes straight to the user interface. That way, the Developer can follow the script without having to walk
+ through a complicated set of instructions to get to a particular screen or page.
+</p>
+<h4>
+ Option: Embedded Code
+</h4>
+<p>
+ Certain technologies (such as Java&trade; 5 Test Annotation) enable you to embed tests in the implementation. In those cases,
+ there will be a logical work product, but it will be assimilated into the code that you are testing. Here, too, take
+ into consideration that you must ensure that the code is self-documenting.
+</p></representationOptions>
+</org.eclipse.epf.uma:ArtifactDescription>
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.assign/.project b/praclib/temp/practice.tech.use_case_driven_dev.assign/.project
new file mode 100644
index 0000000..f7bcbce
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.assign/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>practice.tech.use_case_driven_dev.assign</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.assign/plugin.xmi b/praclib/temp/practice.tech.use_case_driven_dev.assign/plugin.xmi
new file mode 100644
index 0000000..35961ea
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.assign/plugin.xmi
@@ -0,0 +1,93 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_HZfOoMriEdyd6uFrFHNXhA"
+ guid="_HZfOoMriEdyd6uFrFHNXhA"/>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_HYAA4MriEdyd6uFrFHNXhA" name="practice.tech.use_case_driven_dev.assign"
+ guid="_HYAA4MriEdyd6uFrFHNXhA" changeDate="2008-01-24T17:10:26.798-0800">
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_HYAA4criEdyd6uFrFHNXhA"
+ name="Content" guid="_HYAA4criEdyd6uFrFHNXhA">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_HYAA4sriEdyd6uFrFHNXhA"
+ name="Categories" guid="_HYAA4sriEdyd6uFrFHNXhA">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_HYAA48riEdyd6uFrFHNXhA"
+ name="Domains" guid="_HYAA48riEdyd6uFrFHNXhA"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_HYAA5MriEdyd6uFrFHNXhA"
+ name="Disciplines" guid="_HYAA5MriEdyd6uFrFHNXhA">
+ <contentElements xsi:type="org.eclipse.epf.uma:Discipline" xmi:id="_gRTK0MrkEdyd6uFrFHNXhA"
+ name="requirements_discipline.assign" guid="_gRTK0MrkEdyd6uFrFHNXhA"
+ orderingGuide="<?xml version="1.0" encoding="ASCII"?>
<org.eclipse.epf.uma.edit.tng.util.model:OrderInfoCollection xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma.edit.tng.util.model="http:///com/ibm/uma/edit/tng/util/model.ecore">
 <orderInfos name="content elements" timestamp="1201224454948">
 <gUIDs>_P9cMUPV_EdmdHa9MmVPgqQ</gUIDs>
 <gUIDs>_SL7N0LPdEduocbW-TPTq7A</gUIDs>
 <gUIDs>_4z8Z0EbEEdyx8quJU3Grxg</gUIDs>
 </orderInfos>
</org.eclipse.epf.uma.edit.tng.util.model:OrderInfoCollection>
"
+ variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Discipline" href="uma://_MRPloEFXEdy9ENCpSugIjA#_iGSHtVZ-EdyIUdvDLLUdeg"/>
+ <tasks href="uma://_GbYfULPaEduocbW-TPTq7A#_P9cMUPV_EdmdHa9MmVPgqQ"/>
+ <tasks href="uma://_GbYfULPaEduocbW-TPTq7A#_SL7N0LPdEduocbW-TPTq7A"/>
+ <tasks href="uma://_GbYfULPaEduocbW-TPTq7A#_4z8Z0EbEEdyx8quJU3Grxg"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_HYAA5criEdyd6uFrFHNXhA"
+ name="RoleSets" guid="_HYAA5criEdyd6uFrFHNXhA"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_HYAA5sriEdyd6uFrFHNXhA"
+ name="WP Types" guid="_HYAA5sriEdyd6uFrFHNXhA"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_HYAA58riEdyd6uFrFHNXhA"
+ name="Tools" guid="_HYAA58riEdyd6uFrFHNXhA"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_HYAA6MriEdyd6uFrFHNXhA"
+ name="StandardCategories" guid="_HYAA6MriEdyd6uFrFHNXhA"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_HYAA6criEdyd6uFrFHNXhA"
+ name="CustomCategories" guid="_HYAA6criEdyd6uFrFHNXhA">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_HYAA6sriEdyd6uFrFHNXhA"
+ name="Hidden" guid="_HYAA6sriEdyd6uFrFHNXhA">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_HYAA68riEdyd6uFrFHNXhA"
+ name="Custom Categories" guid="_HYAA68riEdyd6uFrFHNXhA"/>
+ </childPackages>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_HYAA7MriEdyd6uFrFHNXhA"
+ name="CoreContent" guid="_HYAA7MriEdyd6uFrFHNXhA">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_gMspkMriEdyd6uFrFHNXhA"
+ name="Role Assignments" guid="_gMspkMriEdyd6uFrFHNXhA">
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_PtIqYMrjEdyd6uFrFHNXhA"
+ name="detail_system_wide_requirements.assign_role" guid="_PtIqYMrjEdyd6uFrFHNXhA"
+ variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Task" href="uma://_GbYfULPaEduocbW-TPTq7A#_4z8Z0EbEEdyx8quJU3Grxg"/>
+ <performedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0VxJsMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0X9iEMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_dTa6gMAYEdqX-s4mWhkyqQ"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0ZM4MclgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_UUTp0MrjEdyd6uFrFHNXhA"
+ name="detail_use_case_scenarios.assign_role" guid="_UUTp0MrjEdyd6uFrFHNXhA"
+ variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Task" href="uma://_GbYfULPaEduocbW-TPTq7A#_SL7N0LPdEduocbW-TPTq7A"/>
+ <performedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0VxJsMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0X9iEMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_dTa6gMAYEdqX-s4mWhkyqQ"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0ZM4MclgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_W3-gcMrjEdyd6uFrFHNXhA"
+ name="identify_and_outline_requirements.assign_role" guid="_W3-gcMrjEdyd6uFrFHNXhA"
+ variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Task" href="uma://_GbYfULPaEduocbW-TPTq7A#_P9cMUPV_EdmdHa9MmVPgqQ"/>
+ <performedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0VxJsMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0X9iEMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_dTa6gMAYEdqX-s4mWhkyqQ"/>
+ <additionallyPerformedBy href="uma://_A118oMYaEdyXeo04os5BOw#_0ZM4MclgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_HYAA7criEdyd6uFrFHNXhA"
+ name="CapabilityPatterns" guid="_HYAA7criEdyd6uFrFHNXhA"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_HYAA7sriEdyd6uFrFHNXhA"
+ name="DeliveryProcesses" guid="_HYAA7sriEdyd6uFrFHNXhA"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_HYAA78riEdyd6uFrFHNXhA"
+ name="ProcessContributions" guid="_HYAA78riEdyd6uFrFHNXhA"/>
+ <bases href="uma://_MRPloEFXEdy9ENCpSugIjA#_MRPloEFXEdy9ENCpSugIjA"/>
+ <bases href="uma://_A118oMYaEdyXeo04os5BOw#_A118oMYaEdyXeo04os5BOw"/>
+ <bases href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfULPaEduocbW-TPTq7A"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/.project b/praclib/temp/practice.tech.use_case_driven_dev.base/.project
new file mode 100644
index 0000000..d5e15c8
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>practice.tech.use_case_driven_dev.base</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/capabilitypatterns/use_case_driven_development_reference_workflow/content.xmi b/praclib/temp/practice.tech.use_case_driven_dev.base/capabilitypatterns/use_case_driven_development_reference_workflow/content.xmi
new file mode 100644
index 0000000..551ad67
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/capabilitypatterns/use_case_driven_development_reference_workflow/content.xmi
@@ -0,0 +1,7 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:ProcessDescription 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="-x6VfF-DqszjZdmkm9p3Lvw"
+ name="use_case_driven_development_workflow,_2sH7sbPaEduocbW-TPTq7A" guid="-x6VfF-DqszjZdmkm9p3Lvw"
+ version="7.1.0"/>
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/capabilitypatterns/use_case_driven_development_reference_workflow/model.xmi b/praclib/temp/practice.tech.use_case_driven_dev.base/capabilitypatterns/use_case_driven_development_reference_workflow/model.xmi
new file mode 100644
index 0000000..8a391d4
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/capabilitypatterns/use_case_driven_development_reference_workflow/model.xmi
@@ -0,0 +1,44 @@
+<?xml version="1.0" encoding="UTF-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.4/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.2.0" xmlns:epf="http://www.eclipse.org/epf"
+ epf:version="1.2.0">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_2syqEbPaEduocbW-TPTq7A"
+ guid="_2syqEbPaEduocbW-TPTq7A">
+ <resourceDescriptors xmi:id="_2syqErPaEduocbW-TPTq7A" id="-x6VfF-DqszjZdmkm9p3Lvw"
+ uri="content.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:ProcessComponent xmi:id="_2sH7sLPaEduocbW-TPTq7A" name="use_case_driven_development_reference_workflow"
+ guid="_2sH7sLPaEduocbW-TPTq7A">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_doAvwMO5EdupeqHTre3HvQ"
+ name="identify_and_outline_use_cases" guid="_doAvwMO5EdupeqHTre3HvQ" presentationName="Identify and Outline Use Cases"
+ superActivities="_2sH7sbPaEduocbW-TPTq7A" output="_eM_loNPfEduegN_z1rVgJA"/>
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_fUzowMO5EdupeqHTre3HvQ"
+ name="detail_use_case" guid="_fUzowMO5EdupeqHTre3HvQ" presentationName="Detail Use Case"
+ superActivities="_2sH7sbPaEduocbW-TPTq7A" output="_eM_loNPfEduegN_z1rVgJA">
+ <Task href="uma://_GbYfULPaEduocbW-TPTq7A#_SL7N0LPdEduocbW-TPTq7A"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_hOjYoMO5EdupeqHTre3HvQ"
+ name="detail_system_wide_requirements" guid="_hOjYoMO5EdupeqHTre3HvQ" presentationName="Detail System-Wide Requirements"
+ superActivities="_2sH7sbPaEduocbW-TPTq7A" mandatoryInput="_eM_lodPfEduegN_z1rVgJA"
+ output="_eM_lodPfEduegN_z1rVgJA"/>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_eM_loNPfEduegN_z1rVgJA"
+ name="use_case" guid="_eM_loNPfEduegN_z1rVgJA" presentationName="Use Case"
+ superActivities="_2sH7sbPaEduocbW-TPTq7A">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0VGbUMlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_eM_lodPfEduegN_z1rVgJA"
+ name="system_wide_requirements" guid="_eM_lodPfEduegN_z1rVgJA" presentationName="System-Wide Requirements"
+ superActivities="_2sH7sbPaEduocbW-TPTq7A">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_BVh9cL-CEdqb7N6KIeDL8Q"/>
+ </processElements>
+ <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_2sH7sbPaEduocbW-TPTq7A"
+ name="use_case_driven_development_reference_workflow" guid="_2sH7sbPaEduocbW-TPTq7A"
+ presentationName="Use-Case-Driven Development Workflow" breakdownElements="_doAvwMO5EdupeqHTre3HvQ _fUzowMO5EdupeqHTre3HvQ _hOjYoMO5EdupeqHTre3HvQ _eM_loNPfEduegN_z1rVgJA _eM_lodPfEduegN_z1rVgJA">
+ <presentation xmi:id="-x6VfF-DqszjZdmkm9p3Lvw" href="uma://-x6VfF-DqszjZdmkm9p3Lvw#-x6VfF-DqszjZdmkm9p3Lvw"/>
+ <defaultContext href="uma://_eoDDMEFqEdy9ENCpSugIjA#_cZuNwLS9EduDY8LNbMCDBA"/>
+ <validContext href="uma://_eoDDMEFqEdy9ENCpSugIjA#_cZuNwLS9EduDY8LNbMCDBA"/>
+ </process>
+ </org.eclipse.epf.uma:ProcessComponent>
+</xmi:XMI>
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/bookc.gif b/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/bookc.gif
new file mode 100644
index 0000000..7f2ab85
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/bookc.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/bookcL.gif b/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/bookcL.gif
new file mode 100644
index 0000000..6c5b064
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/bookcL.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/compass.gif b/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/compass.gif
new file mode 100644
index 0000000..39f306a
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/compass.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/compassL.gif b/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/compassL.gif
new file mode 100644
index 0000000..4117414
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/compassL.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/concept_dgm32.gif b/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/concept_dgm32.gif
new file mode 100644
index 0000000..fa195bd
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/concept_dgm32.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/concept_obj.gif b/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/concept_obj.gif
new file mode 100644
index 0000000..03af38b
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/concept_obj.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/pract_dgm32.gif b/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/pract_dgm32.gif
new file mode 100644
index 0000000..f597332
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/pract_dgm32.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/pract_obj.gif b/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/pract_obj.gif
new file mode 100644
index 0000000..fe8075a
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/pract_obj.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/task_dgm32.gif b/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/task_dgm32.gif
new file mode 100644
index 0000000..a91ea1c
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/task_dgm32.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/task_obj.gif b/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/task_obj.gif
new file mode 100644
index 0000000..7633d58
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/task_obj.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/workproduct_dgm32.gif b/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/workproduct_dgm32.gif
new file mode 100644
index 0000000..009c9af
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/workproduct_dgm32.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/workproduct_obj.gif b/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/workproduct_obj.gif
new file mode 100644
index 0000000..3e58c6f
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/resources/workproduct_obj.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/use_case_driven_dev_practice.xmi b/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/use_case_driven_dev_practice.xmi
new file mode 100644
index 0000000..323d735
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/customcategories/use_case_driven_dev_practice.xmi
@@ -0,0 +1,93 @@
+<?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="-AamnbYmwP0YHOBlj7huJjw"
+ name="use_case_driven_dev_practice,_lmNCoJ-lEdyBk-WQzMU-FQ" guid="-AamnbYmwP0YHOBlj7huJjw"
+ changeDate="2008-02-12T10:58:16.654-0800" version="7.2.0">
+ <mainDescription><h3>
+ Why Adopt this Practice
+</h3>
+<p>
+ Many organizations document requirements as a list of declarative statements (or "shall" statements) that lead the team
+ to focus on development of atomic functions and fine-grained assertions of need. Moreover, applications developed from
+ such requirements are often difficult to use and require more time for integration and testing than applications
+ developed using user-focused requirements.
+</p>
+<p>
+ A second, more serious organizational anti-pattern is no focus on requirements at all. Many organizations simply fail
+ to document requirements, leaving it to developers to discern from a perhaps vague vision document, or even nothing
+ more than a meeting or conversation, what the application or system to be developed must do.
+</p>
+<p>
+ This practice shows how to avoid these pitfalls by using use cases and scenarios to capture functional requirements.
+ That approach provides development of usage scenarios that clearly express behavior - or the interaction between users
+ and the system under development. Use cases categorize valuable and useful end-to-end, testable and collaborative
+ behavior in which the system is involved. Non-functional requirements, such as performance, stability, usability, and
+ so on, can still be captured using traditional techniques. This practice also explains how use cases and scenarios are
+ best developed in conjunction with - and used to drive - other development activities, including design and
+ testing.&nbsp;&nbsp;
+</p>
+<h3>
+ How to Read this Practice
+</h3>
+<p>
+ The best way to review a practice is to familiarize yourself with the enablement materials and then review key
+ concepts, work products, tasks, and the more detailed guidance, either by reviewing the guidance category directly, or
+ by navigating from tasks and work products to their related guidance.
+</p>
+<p>
+ You may first want to become familiar with general requirements concepts:
+</p>
+<ul>
+ <li>
+ <a class="elementLink" href="./../../core.tech.common.base/guidances/concepts/requirements_8006414F.html"
+ guid="_0Wh-sMlgEdmt3adZL5Dmdw">Requirements</a>
+ </li>
+</ul>
+<p>
+ Then become familiar with use cases:
+</p>
+<ul>
+ <li>
+ <a class="elementLink" href="./../../core.tech.common.base/guidances/concepts/use_case_BB199D1B.html"
+ guid="_KudM0NcJEdqz_d2XWoVt6Q">Use Case</a>
+ </li>
+ <li>
+ <a class="elementLink" href="./../../core.tech.common.base/guidances/concepts/actor_411726C.html"
+ guid="_zGqO0MDpEduTGJ8i4u8TMw">Actor</a>
+ </li>
+ <li>
+ <a class="elementLink" href="./../../core.tech.common.base/guidances/concepts/use_case_model_CD178AF9.html"
+ guid="_2jyfUAhVEduRe8TeoBmuGg">Use-Case Model</a>
+ </li>
+</ul>
+<p>
+ This practice focusses on the following work products:
+</p>
+<ul>
+ <li>
+ <a class="elementLink" href="./../../core.tech.common.base/workproducts/use_case_22BE66E2.html"
+ guid="_0VGbUMlgEdmt3adZL5Dmdw">Use Case</a>
+ </li>
+ <li>
+ <a class="elementLink" href="./../../core.tech.common.base/workproducts/system_wide_requirements_7D9DD47C.html"
+ guid="_BVh9cL-CEdqb7N6KIeDL8Q">System-Wide Requirements</a>
+ </li>
+</ul>
+<p>
+ Both work products go through similar states - they are identified and outlined, which allows them to be prioritized,
+ and then detailed. However, in general, a use case is detailed a scenario at a time. (This is particularly important
+ when following an iterative approach where a scenario is detailed "just in time" to be implemented, as opposed to the
+ approach of detailing all or most requirements up front). The tasks that drive these states are listed here: <a
+ class="elementLink" href="./../../practice.tech.use_case_driven_dev.base/customcategories/tasks_61FD663B.html"
+ guid="_K5oBwMSFEdyBt8f9agIerg">Tasks</a>.
+</p>
+<p>
+ In addition, guidelines and tool mentors associated with each task provide details of how to perform the
+ task.&nbsp;Templates and checklists associated with the work products guide you in their completion and evaluation.
+</p>
+<p>
+ Measurements can guide you on assessing how well you are following this practice.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/concepts/requirements.ucdd.xmi b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/concepts/requirements.ucdd.xmi
new file mode 100644
index 0000000..0dbddba
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/concepts/requirements.ucdd.xmi
@@ -0,0 +1,16 @@
+<?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="-4E4u3crgCavkHJqTClP8cA"
+ name="new_concept,_FlOgUEj8Edyi3_jfs__bIQ" guid="-4E4u3crgCavkHJqTClP8cA" changeDate="2007-11-13T16:04:54.621-0800"
+ version="7.1.0">
+ <mainDescription><p>
+ Quality requirements that apply to the system as a whole are captured as structured text in <a
+ class="elementLinkWithType"
+ href="./../../../core.tech.common.base/workproducts/system_wide_requirements_7D9DD47C.html"
+ guid="_BVh9cL-CEdqb7N6KIeDL8Q">Artifact: ** System-Wide Requirements</a>.&nbsp;Quality requirements that are closely
+ associated with a particular Use Case are often captured in the Use Case itself to simplify review, understanding, and
+ maintenance.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/concepts/resources/ATMUCdiagram.GIF b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/concepts/resources/ATMUCdiagram.GIF
new file mode 100644
index 0000000..c3428b5
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/concepts/resources/ATMUCdiagram.GIF
Binary files differ
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/concepts/resources/im_uc.gif b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/concepts/resources/im_uc.gif
new file mode 100644
index 0000000..f271c09
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/concepts/resources/im_uc.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/concepts/resources/md_acto2.gif b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/concepts/resources/md_acto2.gif
new file mode 100644
index 0000000..29ede3a
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/concepts/resources/md_acto2.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/concepts/resources/md_acto3.gif b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/concepts/resources/md_acto3.gif
new file mode 100644
index 0000000..43fbf21
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/concepts/resources/md_acto3.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/concepts/resources/ucprepst.gif b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/concepts/resources/ucprepst.gif
new file mode 100644
index 0000000..5f9e869
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/concepts/resources/ucprepst.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/concepts/resources/ucstrct.gif b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/concepts/resources/ucstrct.gif
new file mode 100644
index 0000000..4458bcb
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/concepts/resources/ucstrct.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/concepts/use_case.ucdd.xmi b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/concepts/use_case.ucdd.xmi
new file mode 100644
index 0000000..0ac3975
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/concepts/use_case.ucdd.xmi
@@ -0,0 +1,66 @@
+<?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="-wv4JAmTQ0R_KjP76LgDITg"
+ name="new_concept,_ryuL0LsbEdyfAY9BXNFkDg" guid="-wv4JAmTQ0R_KjP76LgDITg" changeDate="2008-01-04T15:23:23.667-0800">
+ <mainDescription><h3>
+ Specifying Use Cases
+</h3>
+<h4>
+ <a id="How to Find Use Cases" name="How to Find Use Cases">How to Find Use Cases</a>
+</h4>
+<p>
+ See the&nbsp;<a class="elementLinkWithType"
+ href="./../../../practice.tech.use_case_driven_dev.base/guidances/guidelines/find_and_outline_actors_and_ucs_BB5516A9.html"
+ guid="_eyL0wCu-EdqSxKAVa9kmvA">Guideline: *Find and Outline Actors and Use Cases</a>&nbsp;for guidance on finding
+ Actors and Use Cases.
+</p>
+<h4>
+ <a id="How a Use Case Evolves" name="How a Use Case Evolves">How a Use Case Evolves</a>
+</h4>
+<p>
+ See the <a class="elementLinkWithType"
+ href="./../../../practice.tech.use_case_driven_dev.base/guidances/guidelines/detail_ucs_and_scenarios_6BC56BB7.html"
+ guid="_4BJ_YCxSEdqjsdw1QLH_6Q">Guideline: ***Detail Use Cases and Scenarios</a>&nbsp;for guidance on evolving use
+ cases.
+</p>
+<h4>
+ Level of detail necessary in use cases&nbsp;
+</h4>
+<p>
+ There will often be use cases in your model that are so simple that they do not need a detailed description of the flow
+ of events, a step-by-step outline is quite enough. The criteria for making this decision is that you don't see
+ disagreement among user kind of readers on what the use case means, and that designers and testers are comfortable with
+ the level of detail provided by the step-by-step format. Examples are use cases that describe simple entry or retrieval
+ of some data from the system.
+</p>
+<p>
+ For more information on possible formats and level of detail captured for each use case see <a
+ class="elementLinkWithType"
+ href="./../../../practice.tech.use_case_driven_dev.base/guidances/guidelines/use_case_formats_FF4AE425.html"
+ guid="_qq0GMAXkEduj_7BEUj1JfQ">Guideline: *Use Case Formats</a>.
+</p>
+<h4>
+ <a id="XE_use_case__scope_of_a_use_case" name="XE_use_case__scope_of_a_use_case"></a><a id="The Scope of a Use Case"
+ name="The Scope of a Use Case">The Scope of a Use Case</a>
+</h4>
+<p>
+ It is often hard to decide if a set of user-system interactions, or dialog, is one or several use cases. Consider the
+ use of a recycling machine. The customer inserts deposit items, such as cans, bottles, and crates, into the recycling
+ machine. When she has inserted all her deposit items, she presses a button, and a receipt is printed. She can then
+ exchange this receipt for money.
+</p>
+<p>
+ Is it one use case to insert a deposit item, and another use case to require the receipt? Or is it all one use case?
+ There are two actions, but one without the other is of little value to the customer. Rather, it is the complete dialog
+ with all the insertions, and getting the receipt, that is of value for the customer (and makes sense to her). Thus, the
+ complete dialog, from inserting the first deposit item, to pressing the button and getting the receipt, is a complete
+ case of use, a use case.
+</p>
+<p>
+ Additionally, you want to keep the two actions together, to be able to review them at the same time, modify them
+ together, test them together, write manuals for them and in general manage them as a unit. This becomes very obvious in
+ larger systems.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/concepts/use_case.ucm.xmi b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/concepts/use_case.ucm.xmi
new file mode 100644
index 0000000..bde71eb
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/concepts/use_case.ucm.xmi
@@ -0,0 +1,19 @@
+<?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="-3kVaHsAKwWzKBx12XV-xTg"
+ name="new_concept,_jivyULseEdyfAY9BXNFkDg" guid="-3kVaHsAKwWzKBx12XV-xTg" changeDate="2008-01-04T15:42:07.577-0800">
+ <mainDescription><h3>
+ <a id="Use-Case Diagrams" name="Use-Case Diagrams">Use-Case Diagrams</a>
+</h3>
+<p>
+ You may choose to illustrate how a use case relates to actors and other use cases in a use-case diagram (in unusual
+ cases, more than one diagram). This is useful if the use case is involved with many actors, or has relationships to
+ many other use cases. A diagram of this kind is of "local" character, since it shows the use-case model from the
+ perspective of one use case only and is not intended to explain any general facts about the whole use-case model. Refer
+ to&nbsp;<a class="elementLinkWithType"
+ href="./../../../practice.tech.use_case_driven_dev.base/guidances/guidelines/use_case_model_4C64E97D.html"
+ guid="_0VAUsMlgEdmt3adZL5Dmdw">Guideline: *Use-Case Model</a> for more information.<br />
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/detail_ucs_and_scenarios.xmi b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/detail_ucs_and_scenarios.xmi
new file mode 100644
index 0000000..e246367
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/detail_ucs_and_scenarios.xmi
@@ -0,0 +1,165 @@
+<?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="-78ko4CuOJERKJF9ZvwMUBQ"
+ name="detail_ucs_and_scenarios,_4BJ_YCxSEdqjsdw1QLH_6Q" guid="-78ko4CuOJERKJF9ZvwMUBQ"
+ changeDate="2008-02-11T16:21:32.604-0800" version="1.0.0">
+ <mainDescription><h4>
+ Most efficient way to write use cases
+</h4>
+<p>
+ Because use cases model requirements, they are highly dynamic by nature. The more we examine a requirement, the more we
+ learn, and the more things change. To further complicate the issue, changes to one use case can lead to changes in
+ others. Therefore, we want a flexible, highly efficient method for writing use cases that eliminates unnecessary work
+ and rewriting.
+</p>
+<p>
+ An iterative, breadth-first approach, in which the use case is continuously evaluated before adding detail, is an
+ effective way to write use cases. This breadth-first approach involves two aspects: writing the set of use cases and
+ writing individual use cases.
+</p>
+<p>
+ <strong>Writing sets of use cases:</strong> Use cases exist in sets, and the relationships between the various use
+ cases and Actors&nbsp;are important. As you learn more about the Actors, you also learn more about the system's
+ boundaries and transactions. Likewise, as you learn more about the system's transactions, you learn more about its
+ Actors. Therefore, it is more efficient to write several use cases simultaneously than to write them sequentially. This
+ way, you can identify and understand the effects of the various use cases upon each other as you write them, rather
+ than as afterthoughts that require rewriting or elimination of previous work.
+</p>
+<p>
+ <strong>Writing individual use cases.</strong> Similarly, it makes sense to write each individual use case iteratively.
+ Starting with the main scenario, you can then identify various alternative and error flows that the use case might
+ follow, then evaluate, rearrange or eliminate them, and then add the details of the surviving scenarios.
+</p>
+<p>
+ Consider factors that can influence the format and level of detail for your use case description.
+</p>
+<h4>
+ Detail the flow of events of the main scenario
+</h4>
+<p>
+ As a starting point, use the step-by-step description of the use-case main scenario. Then, gradually add details to
+ this scenario, describing <strong>what</strong> the use case does, <strong>not how</strong> to solve problems internal
+ to the system.
+</p>
+<p>
+ A flow of events description explores:
+</p>
+<ul>
+ <li>
+ How and when the use case starts
+ </li>
+ <li>
+ When the use case interacts with the Actors, and what data they exchange
+ </li>
+ <li>
+ When the use case uses data stored in the system or stores data in the system
+ </li>
+ <li>
+ How and when the use case ends
+ </li>
+</ul>
+<p>
+ It does not describe:
+</p>
+<ul>
+ <li>
+ The GUI
+ </li>
+ <li>
+ Technical details of hardware or software
+ </li>
+ <li>
+ Design issues
+ </li>
+</ul>
+<h4>
+ Identify alternate flows
+</h4>
+<p>
+ A use case consists of a number of scenarios, each representing specific instances of the use case that correspond to
+ specific inputs from the Actor or to specific conditions in the environment. Each scenario describes alternate ways
+ that the system provides a behavior, or it may describe failure or exception cases.
+</p>
+<p>
+ As you detail the main scenario, identify alternate flows by asking these questions:
+</p>
+<ul>
+ <li>
+ Are there different options available, depending on input from the Actor? (for example, if the Actor enters an
+ invalid PIN number while accessing an ATM)
+ </li>
+ <li>
+ What business rules may come into play? (for instance, the Actor requests more money from the ATM than is available
+ in her account)
+ </li>
+ <li>
+ What could go wrong? (such as no network connection available when required to perform a transaction)
+ </li>
+</ul>
+<p>
+ It is best to develop these scenarios iteratively, as well. Begin by identifying them. Examine each possible scenario
+ to determine whether it is relevant, that it can actually happen, and that it is distinct from other scenarios.
+ Eliminate redundant or unnecessary scenarios, and then start elaborating on the more important ones.
+</p>
+<h4>
+ Structure the use case
+</h4>
+<p>
+ It is useful to structure the use case according to scenarios. This helps both to simplify communication and
+ maintenance and to permit the use cases to be implemented iteratively.
+</p>
+<p>
+ In addition to structuring the use cases according to scenarios, it is often useful to structure the scenarios
+ themselves into sub-flows. This provides an additional level of granularity for planning work and tracking progress.
+ Unless a sub-flow involves only a minor part of the complete flow of events (which can be described in the body of the
+ text), it is recommended that you describe each sub-flow in a separate section to the Flow of Events section. Sub-flows
+ that should be in a separate section include these examples:
+</p>
+<ul>
+ <li>
+ Sub-flows that occupy a large segment of a given flow of events.
+ </li>
+ <li>
+ Exceptional and alternate flows of events. This helps the use case's basic flow of events to stand out more
+ clearly.
+ </li>
+ <li>
+ Any sub-flow that can be executed at several intervals in the same flow of events.
+ </li>
+</ul>
+<h4>
+ Describe special requirements
+</h4>
+<p>
+ You should also capture any requirements that are related to the use case, but are not taken into consideration in the
+ flow of events of the use case. Such requirements are likely to be nonfunctional.
+</p>
+<p>
+ Typically, nonfunctional requirements that refer to a specific use case are captured in the special requirements
+ section of the use case.&nbsp;If there are nonfunctional requirements that apply to more than one use case, capture
+ these in the system-wide requirements specification.
+</p>
+<h4>
+ Describe preconditions and postconditions
+</h4>
+<p>
+ A <strong>precondition</strong> on a use case explains the state that the system must be in for the use case to be able
+ to start. Be careful in describing the system state. Avoid describing the detail of other, incidental activities that
+ may already have taken place.
+</p>
+<p>
+ A <strong>postcondition</strong> on a use case lists possible states that the system can be in at the end of the use
+ case execution. The system must be in one of those states. A postcondition also states actions that the system performs
+ at the end of the use case, regardless of what occurred in the use case. Post-Conditions may be categorized as Minimal
+ Guarantees&nbsp;or Success Guarantees.&nbsp; A Minimal Guarantee represents a condition that will be true when the use
+ case ends, regardless of how it terminates.&nbsp; A Success Guarantee represents a condition that will be true when the
+ use case ends successfully, regardless of which path it took.
+</p>
+<p>
+ Neither preconditions nor postconditions should be used to create a sequence of use cases. As a general rule, there
+ should never be a case where you have to first perform one use case and then another to have a meaningful flow of
+ events. If that is the case, correct the problem by reviewing the use cases.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/identify_and_outline_actors_and_ucs.xmi b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/identify_and_outline_actors_and_ucs.xmi
new file mode 100644
index 0000000..b6b9185
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/identify_and_outline_actors_and_ucs.xmi
@@ -0,0 +1,151 @@
+<?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="-Rcm_MlViENAvFFyIe9V3dQ"
+ name="identify_and_outline_actors_and_ucs,_eyL0wCu-EdqSxKAVa9kmvA" guid="-Rcm_MlViENAvFFyIe9V3dQ"
+ changeDate="2008-01-30T15:39:52.075-0800" version="1.0.0">
+ <mainDescription><h4>
+ Identifying actors
+</h4>
+<p>
+ Find the external entities with which the system under development must interact. Candidates include groups of users
+ who will require help from the system to perform their tasks and execute the system's primary or secondary functions,
+ as well as external hardware, software, and other systems.
+</p>
+<p>
+ Define each candidate actor by naming it and writing a brief description. Includes the actor's area of responsibility
+ and the goals that the actor will attempt to accomplish when using the system. Eliminate actor candidates who do not
+ have any goals.
+</p>
+<p>
+ These questions are useful in identifying actors:
+</p>
+<ul>
+ <li>
+ Who will supply, use, or remove information from the system?
+ </li>
+ <li>
+ Who will use the system?
+ </li>
+ <li>
+ Who is interested in a certain feature or service provided by the system?
+ </li>
+ <li>
+ Who will support and maintain the system?
+ </li>
+ <li>
+ What are the system's external resources?
+ </li>
+ <li>
+ What other systems will need to interact with the system under development?
+ </li>
+</ul>
+<p>
+ Review the list of stakeholders that you captured in the Vision statement. Not all stakeholders will be actors
+ (meaning, they will not all interact directly with the system under development), but this list of stakeholders is
+ useful for identifying candidates for actors.
+</p>
+<h4>
+ Identifying&nbsp;use cases
+</h4>
+<p>
+ The best way to find use cases is to consider what each actor requires of the system. For each actor, human or not,
+ ask:
+</p>
+<ul>
+ <li>
+ What are the goals that the actor will attempt to accomplish with the system?
+ </li>
+ <li>
+ What are the primary tasks that the actor wants the system to perform?
+ </li>
+ <li>
+ Will the actor create, store, change, remove, or read data in the system?
+ </li>
+ <li>
+ Will the actor need to inform the system about sudden external changes?
+ </li>
+ <li>
+ Does the actor need to be informed about certain occurrences, such as unavailability of a network resource,&nbsp;in
+ the system?
+ </li>
+ <li>
+ Will the actor perform a system startup or shutdown?
+ </li>
+</ul>
+<p>
+ Understanding how&nbsp;the target&nbsp;organization works and how this information system might be incorporated into
+ existing operations gives an idea of system's surroundings. That information may reveal other use case candidates.
+</p>
+<p>
+ Give a unique name and brief description that clearly describes the goals for each use case. If the candidate use case
+ does not have goals, ask yourself why it exists, and then either identify a goal or eliminate the use case.
+</p>
+<h4>
+ Outlining Use Cases
+</h4>
+<p>
+ Without going into details, write a first draft of the flow of events of the use cases identified as being of high
+ priority. Initially, write a simple step-by-step description of the basic flow of the use case. The step-by-step
+ description is a simple ordered list of interactions between the actor and the system. For example, the description of
+ the basic flow of the Withdraw Cash use case of an automated teller machine (ATM) would be something like this:
+</p>
+<ol>
+ <li>
+ The&nbsp;customer inserts a bank card.
+ </li>
+ <li>
+ The system validates the card and prompts the person to enter a personal identification number (PIN).
+ </li>
+ <li>
+ The customer&nbsp;enters a PIN.
+ </li>
+ <li>
+ The system validates the PIN and prompts the customer to select an action.
+ </li>
+ <li>
+ The customer selects Withdraw Cash.
+ </li>
+ <li>
+ The system prompts the customer to choose which account.
+ </li>
+ <li>
+ The customer selects the checking account.
+ </li>
+ <li>
+ The system prompts for an amount.
+ </li>
+ <li>
+ The customer enters the amount to withdraw.
+ </li>
+ <li>
+ The system validates the amount (assuming sufficient funds), and then issues cash and receipt.
+ </li>
+ <li>
+ The customer takes the cash and receipt, and then retrieves the bank card.
+ </li>
+ <li>
+ The use case ends.
+ </li>
+</ol>
+<p>
+ As you create this step-by-step description of the basic flow of events, you may discover alternative and exceptional
+ flows. For example, what happens if the customer enters an invalid PIN? Record the name and a brief description of each
+ alternate flow that you identified.
+</p>
+<h4>
+ Representing relationships between actors and use cases
+</h4>
+<p>
+ The relationship between actors and use cases should be captured, or documented&nbsp; There are several ways to do
+ this. If you are using a use-case model on the project, you can create use-case diagrams to show how&nbsp;actors and
+ use cases&nbsp;relate to each other.&nbsp; Refer to&nbsp;<a
+ href="./../../../practice.tech.use_case_driven_dev.base/guidances/guidelines/use_case_model_4C64E97D.html"
+ guid="_0VAUsMlgEdmt3adZL5Dmdw">Guideline: Use-Case Model</a>&nbsp;for more information.
+</p>
+<p>
+ If you are not using a use-case model for the project, make sure that each use case identifies the associated primary
+ and secondary actors.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/resources/comasso1.gif b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/resources/comasso1.gif
new file mode 100644
index 0000000..c276a59
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/resources/comasso1.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/resources/comasso2.gif b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/resources/comasso2.gif
new file mode 100644
index 0000000..561e593
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/resources/comasso2.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/resources/md_actg2.gif b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/resources/md_actg2.gif
new file mode 100644
index 0000000..547c9ae
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/resources/md_actg2.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/resources/md_coma2.gif b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/resources/md_coma2.gif
new file mode 100644
index 0000000..498451d
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/resources/md_coma2.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/resources/md_coma4.gif b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/resources/md_coma4.gif
new file mode 100644
index 0000000..6ce9867
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/resources/md_coma4.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/resources/md_ucre3.gif b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/resources/md_ucre3.gif
new file mode 100644
index 0000000..7f4cf27
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/resources/md_ucre3.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/resources/top.gif b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/resources/top.gif
new file mode 100644
index 0000000..615acf4
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/resources/top.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/resources/ucrea1.gif b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/resources/ucrea1.gif
new file mode 100644
index 0000000..78190a2
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/resources/ucrea1.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/system_wide_requirements.xmi b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/system_wide_requirements.xmi
new file mode 100644
index 0000000..ff03c6b
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/system_wide_requirements.xmi
@@ -0,0 +1,422 @@
+<?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: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="-BdYFG4-dbPBGFzF9z6KGPA"
+ name="supporting_requirements,_wr24gNcGEdqz_d2XWoVt6Q" guid="-BdYFG4-dbPBGFzF9z6KGPA"
+ changeDate="2006-12-21T09:43:46.709-0800" version="1.0.0">
+ <mainDescription><p>
+ There is a finite set of requirements to consider when it comes to gathering system-wide requirements, qualities, or
+ constraints. Many of them are unfamiliar to stakeholders; therefore, they may find it difficult to answer questions
+ related to topics such as availability, performance, scalability, or localization. You can use this guideline and the
+ associated checklist <a class="elementLinkWithType"
+ href="./../../../core.tech.slot.base/guidances/checklists/non_functional_or_system_wide_requirements_renamed_3158BF2F.html"
+ guid="_Vael8CGMEdu3VKXZx45D3A">Checklist: *Non-Functional or System-Wide Requirements</a>&nbsp;when speaking to
+ stakeholders to ensure that all topics are discussed. Make sure that stakeholders understand the costs of their
+ selections and do not end up wanting everything that is on the list.
+</p>
+<h3>
+ Functional
+</h3>
+<ul>
+ <li>
+ <p>
+ <strong>Auditing:</strong> Is there a need to track who used the system and when they used it? State
+ requirements for providing audit trails when running the system.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Authentication:</strong> Will access to the system be controlled? State requirements for
+ authentication.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Licensing:</strong> Will the system or parts of the system be licensed? If open-source software has
+ been used in the system, have all open-source agreements been respected? State requirements for acquiring,
+ installing, tracking, and monitoring licenses.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Printing:</strong> Will printing capability be required? State requirements for printing.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Reporting:</strong> Is reporting capability required? State requirements for reporting.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Scheduling:</strong> Will certain system actions need to be scheduled? State requirements for
+ scheduling capability.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Security:</strong> Will elements of the system or system data need to be secure? State requirements to
+ protect access to certain resources or information.
+ </p>
+ </li>
+</ul>
+<h3>
+ Usability
+</h3>
+<p>
+ Usability requirements are critical to the success of any system. Unfortunately, usability requirements are often the
+ most poorly specified requirements. Consider this common requirement: The system shall be easy to use. This doesn't
+ help much, because it cannot be verified.
+</p>
+<p>
+ While capturing usability requirements, it is a good idea to identify issues and concerns first, and then refine these
+ into verifiable requirements later (see <a class="elementLinkWithType"
+ href="./../../../core.tech.common.base/guidances/guidelines/writing_good_requirements_48248536.html"
+ guid="_6jXzYNcKEdqz_d2XWoVt6Q">Guideline: *Writing Requirements Statements</a>). According to a traditional definition,
+ usability consists of five factors:
+</p>
+<ul>
+ <li>
+ <p>
+ <strong>Ease of learning:</strong> A user with a specified level of experience must be able to learn how to use
+ the system in a specified amount of time.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Task efficiency:</strong> A user should be able to complete a specified task in a specified time (or
+ number of mouse clicks).
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Ease of remembering:</strong> A user should be able to remember how to accomplish specified tasks after
+ not using the system for a specified period of time.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Understandability:</strong> A user must be able to understand system prompts and messages and what the
+ system does.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Subjective satisfaction:</strong> A specified percentage of the user community must express
+ satisfaction with using the system.
+ </p>
+ </li>
+</ul>
+<p>
+ You may want to use the following method to identify and specify usability requirements:
+</p>
+<div style="MARGIN-LEFT: 2em">
+ <ol>
+ <li>
+ Identify the key usability issues by looking at critical tasks, user profiles, system goals, and previous
+ usability problems.
+ </li>
+ <li>
+ Choose the appropriate style to express the requirements: 
+ <ul>
+ <li>
+ <strong>Performance style:</strong> Specify how fast users can learn various tasks and how fast they
+ can perform the tasks after training.
+ </li>
+ <li>
+ <strong>Defect style:</strong> Rather than measuring task times, identify usability defects and
+ specifies how frequently they may occur.
+ </li>
+ <li>
+ <strong>Guideline style:</strong> Specify the general appearance and response time of the user
+ interface by reference to an accepted and well-defined standard
+ </li>
+ </ul>
+ </li>
+ <li>
+ Write the actual requirements, including performance criteria (see <a class="elementLinkWithType"
+ href="./../../../core.tech.common.base/guidances/guidelines/writing_good_requirements_48248536.html"
+ guid="_6jXzYNcKEdqz_d2XWoVt6Q">Guideline: *Writing Requirements Statements</a>&nbsp;for more information).
+ </li>
+ </ol>
+</div>
+<h3>
+ Reliability
+</h3>
+<p>
+ Reliability includes the system's ability to continue running under stress and adverse conditions. In the case of an
+ application, reliability relates to the amount of time that the software is available and running as opposed to time
+ unavailable. Specify reliability acceptance levels, as well as how they will be measured and evaluated. Describe
+ reliability criteria in measurable terms. This is usually expressed as the allowable time between failures or the total
+ allowable failure rate. Other important reliability considerations include:
+</p>
+<ul>
+ <li>
+ <p>
+ <strong>Accuracy:</strong> Specify requirements for the precision (resolution) and the accuracy (by some known
+ standard) that is required in any calculation performed or in system output.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Availability:</strong> Specify requirements for the percentage of time the system is available for use,
+ hours of use, maintenance access, and degraded-mode operations. Availability is typically specified in terms of
+ the Mean Time Between Failures (MTBF).
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Recoverability:</strong> Specify requirements for recovery from failure. This is typically specified in
+ terms of the Mean Time to Repair (MTTR).
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Frequency and severity of failures:</strong> Specify the maximum defect rate (typically expressed as
+ defects/KSLOC or defects/function-point) and severity of failures. Severity&nbsp;may be categorized in terms of
+ <strong>minor</strong>, <strong>significant</strong>, and <strong>critical</strong> defects. The requirements
+ must define each of these terms unambiguously. For example, a <strong>critical</strong> defect could be defined
+ as one that results in loss of data or complete inability to use certain functionality of the system.
+ </p>
+ </li>
+</ul>
+<h3>
+ Performance
+</h3>
+<ul>
+ <li>
+ <p>
+ <strong>Response times:</strong> Specify the amount of time available for the system to complete specified
+ tasks and transactions (average, maximum). Use units of measurement. <em>Examples:</em>
+ </p>
+ <ul>
+ <li>
+ Any interface between a user and the system shall have a maximum response time of 2 seconds.
+ </li>
+ <li>
+ The product shall download the new status parameters within 5 minutes of a change.<br />
+ </li>
+ </ul>
+ </li>
+ <li>
+ <strong>Throughput:</strong> Specify the capacity of the system to support a given flow of information (for
+ example, transactions per second).<br />
+ </li>
+ <li>
+ <strong>Capacity:</strong> Specify on the volumes that the product must be able to deal with and the numbers of
+ data stored by the product. Make sure that the requirement description is quantified, and thus can be tested. Use
+ unit of measurement such as: the number of customers or transactions the system can accommodate, resource usage
+ (memory, disk, . . . ) or degradation modes (what is the acceptable mode of operation when the system has been
+ degraded in some manner) <em>Examples:</em> 
+ <ul>
+ <li>
+ The product shall cater for 300 simultaneous users within the period from 9:00 AM to 11 AM.
+ </li>
+ <li>
+ Maximum loading at other periods will be 150.<br />
+ </li>
+ </ul>
+ </li>
+ <li>
+ <strong>Start-up:</strong> The time for the system to start up.<br />
+ </li>
+ <li>
+ <strong>Shut-down:</strong> The time for the system to shut down.
+ </li>
+</ul>
+<h3>
+ Supportability
+</h3>
+<ul>
+ <li>
+ <p>
+ <strong>Adaptability:</strong> Are there any special requirements regarding adaptation of the software
+ (including upgrading)? List requirements for the ease with which the system is adapted to new environments.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Compatibility:</strong> Are there any requirements regarding this system and its compatibility with
+ previous versions of this system or legacy systems that provide the same capability?
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Configurability:</strong> Will the product be configured after it has been deployed? In what way will
+ the system be configured?
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Installation:</strong> State any special requirements regarding system installation
+ </p>
+ </li>
+ <li>
+ <strong>Level of Support:</strong> What is the level of support that the product requires? This is often done using
+ a Help desk. If there are to be people who provide support for the product, is that support considered part of what
+ you are providing to the customer? Are there any requirements for that support? You might also build support into
+ the product itself, in which case this is the place to write those requirements. Consider the level of support that
+ you anticipate providing and what forms it might take.<br />
+ </li>
+ <li>
+ <strong>Maintainability:</strong> Are there any special requirements regarding system maintenance? What are the
+ requirements for the intended release cycle for the product and the form that the release will take? Quantify the
+ time necessary to make specified changes to the product. There may also be special requirements for
+ maintainability, such as&nbsp;a requirement that&nbsp;the product must be able to be maintained by its end-users or
+ developers who are not your development team. This has an effect on the way that the product is developed, and
+ there may be additional requirements for documentation or training. Describe the type of maintenance and the amount
+ of effort required. <em>Examples:</em><br />
+ </li>
+ <li style="LIST-STYLE-TYPE: none">
+ <ul>
+ <li>
+ A new weather station must be able to be added to the system overnight.
+ </li>
+ <li>
+ The maintenance releases will be offered to end-users once a year.<br />
+ </li>
+ </ul>
+ </li>
+ <li>
+ <strong>Scalability:</strong> What volumes of users and data will the system support? This specifies the expected
+ increases in size that the product must be able to handle As businesses grow (or are expected to grow), the
+ software products must increase their capacities to cope with the new volumes. This may be expressed as a profile
+ over time.<br />
+ </li>
+ <li>
+ <strong>Testability:</strong> Are there any special requirements regarding the testability of the system?
+ </li>
+</ul>
+<h3>
+ Constraints (+)
+</h3>
+<ul>
+ <li>
+ <p>
+ <strong>Design constraints:</strong> Are there any design decisions that have been mandated that the product
+ must adhered to?
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Third-party components:</strong> Specify any mandated legacy, COTS, or open-source components to be
+ used with the system.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Implementation languages:</strong> Specify requirements on the implementation languages to be used
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Platform support:</strong> Specify requirements on the platforms that the system will support
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Resource limits:</strong> Specify requirements on the use of system resources, such as memory and hard
+ disk space
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Physical Constraints:</strong> Specify requirements on the shape, size, and weight of the resulting
+ hardware to house the system
+ </p>
+ </li>
+</ul>
+<h3>
+ Interface Requirements (+)
+</h3>
+<p>
+ Describe both the user interface and interfaces with external systems.
+</p>
+<h4>
+ User interface
+</h4>
+<p>
+ Describe requirements related to user interfaces that are to be implemented by the software. The intention of this
+ section is to state the requirements, but not to describe the user interface itself, because interface design may
+ overlap the requirements-gathering process. This is particularly true if you are using prototyping as part of your
+ requirements gathering process. As you develop prototypes, it is important to capture the requirements that relate to
+ the look and feel of the user interface. In other words, be sure that you understand your client’s intentions for the
+ product’s look and feel. Record these as requirements, rather than merely using a prototype for approval.
+</p>
+<ul>
+ <li>
+ <p>
+ <strong>Look and feel:</strong> A description of the aesthetic appearance and layout of the interface. Your
+ client may have given you particular demands, such as style, colors, degree of interaction, and so on. This
+ section captures the requirements for the interface, rather than the design for the interface. The motivation
+ is to capture the expectations, the constraints, and the client’s demands for the interface before designing
+ it. <em>Examples:</em>
+ </p>
+ <ul>
+ <li>
+ The product shall have the same layout as the district maps from the engineering department.
+ </li>
+ <li>
+ The product shall use the company color.<br />
+ </li>
+ </ul>
+ </li>
+ <li>
+ <strong>Layout and navigation requirements:</strong> Specify requirements on major screen areas and how they should
+ be grouped together.<br />
+ </li>
+ <li>
+ <strong>Consistency:</strong> Consistency in the user interface enables users to predict what will happen. This
+ section states requirements on the use of mechanisms to be employed in the user interface. This applies both within
+ the system, and with other systems and can be applied at different levels: navigation controls, screen areas sizes
+ and shapes, placements for entering / presenting data, terminology<br />
+ </li>
+ <li>
+ <strong>User personalization and customization requirements:</strong> Requirements on content that should
+ automatically displayed to users or available based on user attributes. Sometimes users allowed to customize the
+ content displayed or to personalize displayed content.
+ </li>
+</ul>
+<h4>
+ Interfaces to external systems or devices
+</h4>
+<ul>
+ <li>
+ <p>
+ <strong>Software interfaces:</strong> Are there any external systems with which this system must interface? Are
+ there any constraints on the nature of the interface between this system and any external system, such as the
+ format of data passed between these systems? Do they use any particular protocol? Describe software interfaces
+ with other components. These may be purchased components, components reused from another application, or
+ components being developed for subsystems outside of the scope of the system under consideration, but with
+ which this it must interact. For each system, consider both provided and required interfaces.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Hardware interfaces:</strong> Define any hardware interfaces that are to be supported by the software,
+ including logical structure, physical addresses, expected behavior, and so on.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Communications interfaces:</strong> Describe any communications interfaces to other systems or devices,
+ such as local area networks (LANs), remote serial devices, and so on.
+ </p>
+ </li>
+</ul>
+<h3>
+ Business Rules (+)
+</h3>
+<p>
+ Besides technical requirements, also consider the particular business domain in which the system needs to fit.
+</p>
+<p>
+ Business rules or policies that the system must conform to may constrain system functionality. Business rules are
+ referred to by system use cases and can be in the form of decision tables, computation rules, decision trees,
+ algorithms, and so forth. Describing the rules in the flows of the use cases usually clutters the use-case
+ specifications. Therefore, they are normally captured in separate artifacts or as annexes related to the use-case
+ specifications. In many cases, a business rule applies to more then one use case. Shared business rules should be
+ stored in a single repository or&nbsp;document.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/uc_realizations.xmi b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/uc_realizations.xmi
new file mode 100644
index 0000000..1ed31a1
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/uc_realizations.xmi
@@ -0,0 +1,94 @@
+<?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="-CFYVionNDLkMw6SG6runQA"
+ name="uc_realizations,_2uan8NbyEdqu5o2S60g5LA" guid="-CFYVionNDLkMw6SG6runQA"
+ changeDate="2008-01-25T10:04:23.710-0800">
+ <mainDescription><p>
+ A use-case realization represents how a use case will be implemented in terms of collaborating objects. This artifact
+ can take various forms. It may include, for example, a textual description (a document), class diagrams of
+ participating classes and subsystems, and interaction diagrams (communication and sequence diagrams) that illustrate
+ the flow of interactions between class and subsystem instances.
+</p>
+<p>
+ The reason for separating the use-case realization from its use case is that doing so allows the use cases to be
+ managed separately from their realizations. This is particularly important for larger projects, or families of systems
+ where the same use cases may be designed differently in different products within the product family. Consider the case
+ of a family of telephone switches which have many use cases in common, but which design and implement them differently
+ according to product positioning, performance and price.
+</p>
+<p>
+ For larger projects, separating the use case and its realization allows changes to the design of the use case without
+ affecting the baselined use case itself.
+</p>
+<p>
+ In a model, a use-case realization is represented as a UML collaboration that groups the diagrams and other information
+ (such as textual descriptions) that form part of the use-case realization.
+</p>
+<p>
+ UML diagrams that&nbsp;support use-case realizations can be produced in an analysis context, a&nbsp;design context, or
+ both, depending on the needs of the project. For each use case in the use-case model, there&nbsp;can be&nbsp;a use-case
+ realization in the analysis/design model with a realization relationship to the use case. In UML this is shown as a
+ dashed arrow, with an arrowhead like a generalization relationship, indicating that a realization is a kind of
+ inheritance, as well as a dependency.<br />
+</p>
+<p align="center">
+ <img height="109" alt="Use Case Realisations" src="./resources/ucrea1.gif" width="277" />
+</p>
+<p>
+ A use-case realization in the&nbsp;design can be traced to a use case in the use-case model.
+</p>
+<h4>
+ Class Diagrams Owned by a Use-Case Realization
+</h4>
+<p>
+ For each use-case realization there may be one or more class diagrams depicting its participating classes. A class and
+ its objects often participate in several use-case realizations. It is important&nbsp;while designing to coordinate all
+ the requirements on a class and its objects that different use-case realizations may have. The figure below shows an
+ analysis&nbsp;class diagram for the realization of the Receive Deposit Item use case. Note the use of
+ boundary-control-entity stereotypes to represent analysis classes (see <a class="elementLinkWithType"
+ href="./../../../core.tech.common.base/guidances/guidelines/entity_control_boundary_pattern_C4047897.html"
+ guid="_uF-QYEAhEdq_UJTvM1DM2Q">Guideline: Entity-Control-Boundary Pattern</a>).
+</p>
+<p align="center">
+ <img height="213" alt="Class diagram for the realization of Receive Deposit Item" src="./resources/md_ucre3.gif"
+ width="328" />
+</p>
+<p align="center">
+ <strong>The use case Receive Deposit Item and its analysis-level class diagram</strong>.
+</p>
+<h4>
+ Communication and Sequence Diagrams Owned by a Use-Case Realization
+</h4>
+<p>
+ For each use-case realization there&nbsp;can be&nbsp;one or more interaction diagrams depicting its participating
+ objects and their interactions. There are two types of interaction diagrams: sequence diagrams and communication
+ diagrams. They express similar information, but show it in different ways. Sequence diagrams show the explicit sequence
+ of messages and are better when it is important to visualize the time ordering of messages, whereas communication
+ diagrams show the communication links between objects and are better for understanding all of the effects on a given
+ object and for algorithm design.
+</p>
+<p>
+ Realizing use cases through interaction diagrams helps to keep the design simple and cohesive. Assigning
+ responsibilities to classes on the basis of what the use-case scenario explicitly requires encourages the design to
+ contain the following:
+</p>
+<ul>
+ <li>
+ Only the functionality actually used in support of a use case scenario
+ </li>
+ <li>
+ Functionality that can be tested through an associated test case
+ </li>
+ <li>
+ Functionality that is more easily traceable to requirements and changes
+ </li>
+ <li>
+ Explicitly declared class dependencies that are easier to manage
+ </li>
+</ul>
+<p>
+ These factors help improve the overall quality of the system.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/use_case_formats.xmi b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/use_case_formats.xmi
new file mode 100644
index 0000000..5cbc113
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/use_case_formats.xmi
@@ -0,0 +1,370 @@
+<?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="-pQrBSyxJHLLodLbS4R_Zdw"
+ name="new_guideline,_qq0GMAXkEduj_7BEUj1JfQ" guid="-pQrBSyxJHLLodLbS4R_Zdw" changeDate="2008-02-11T16:35:46.905-0800"
+ version="7.1.0">
+ <mainDescription><h3>
+ Use Case Formats
+</h3>
+<p>
+ Use cases differ from project to project and person to person. A use case that works in one situation may be totally
+ unsuited for another. Different projects have different needs. (See <a class="elementLinkWithUserText"
+ href="./../../../core.tech.common.base/guidances/supportingmaterials/tech_references_6CCF393.html"
+ guid="_9ToeIB83Edqsvps02rpOOg">[ADO04]</a> for more information on use case formats.)
+</p>
+<p>
+ Some need rigorous documentation, including <strong>high-ceremony use cases</strong>, which are formal, highly
+ structured use cases. If the writers used a template, then they filled out all or almost all of its fields for each use
+ case. High-ceremony use cases are best suited for large, extremely complex, safety-critical systems, such as flight
+ control systems, telephone switches, and so forth. They are also used in development cultures that have high
+ documentation standards.
+</p>
+<p>
+ Other projects may be more agile and less formal, benefiting from <strong>low-ceremony use cases</strong>, which are
+ informal, less rigidly structured use cases. If the writers used a template, then they may have left many of the fields
+ blank. Low-ceremony use cases are best suited for smaller, less complex, less safety-critical systems where most of the
+ stakeholders have a strong background in the problem domain. Sometimes, simple descriptions suffice, such as use case
+ <strong>briefs</strong>.
+</p>
+<p>
+ It makes sense to write use cases iteratively. Starting with the basic details, you can then identify the various
+ alternative and error paths that the use case might follow so that you can evaluate, rearrange, or eliminate them, and
+ then elaborate or fill in the details of the courses that you intended to use. You can then write the use cases in one
+ or more of the following formats, progressively, until you reach the one with the level of detail required for a
+ specific project:
+</p>
+<ul>
+ <li>
+ <a id="Actor-Goal-List" name="Actor-Goal_List"><strong>Actor-Goal list</strong></a>: A format for the overview
+ </li>
+ <li>
+ <a id="Briefs" name="Briefs"><strong>Briefs:</strong></a> A format for writing summary use cases
+ </li>
+ <li>
+ <a id="Improvisational Score" name="Improvisational Score"><strong>Improvisational score:</strong></a> A format for
+ writing less formal, low-ceremony use cases
+ </li>
+ <li>
+ <a id="Symphonic Score" name="Symphonic Score"><strong>Symphonic score:</strong></a> A format for writing more
+ formal, high-ceremony use cases
+ </li>
+</ul>
+<h4>
+ Actor-Goal list
+</h4>
+<p>
+ <strong>Context:</strong> You have identified your actors and are trying to identify use cases.
+</p>
+<p>
+ <strong>Problem:</strong> Developing a set of use cases in an ad hoc manner can lead to unnecessary work, missing
+ features, and feature creep. Weight is one of the most important factors in space flight — so important that the United
+ States space agency, NASA, will not allow anything on a spacecraft that isn’t absolutely critical to the flight. If
+ something literally isn’t worth its weight, then it doesn’t go. Likewise, each use case adds cost to a system;
+ therefore, you need to be sure to include only those use cases that add some kind of value to your collection.
+</p>
+<p>
+ <strong>Forces:</strong>
+</p>
+<ul>
+ <li>
+ <p>
+ <strong>Simply listing actors or listing goals is not informative enough, but actors and goals together are
+ informative.</strong> The classical approach to writing use cases is to define a list of actors, then find use
+ cases for each. A variation on this theme is to itemize what the system must accomplish. Yet, neither approach
+ is adequate by itself. You need to know both who is using the system and why they are using it. Otherwise, you
+ introduce the potential of either feature creep or missed features. At the least, a set of use cases should
+ describe this association.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>A quick overview of the entire project structure is sufficient and necessary early in the use case
+ development cycle.</strong> Ideally, this overview should be as short as reasonably possible. It must contain
+ key information as to who requires each service and why they need it. Most other information is not very useful
+ at this stage of the project, because it runs the risk of quickly becoming obsolete, as well as discouraging
+ out-of-the-box (innovative) thinking. An overview helps the writers work through the entire set from a
+ high-level view, expanding some use cases, eliminating others, and combining still others into a more logical
+ grouping.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>You need to be able to expand each to a full use case on demand.</strong> A <em>seedling</em> use case
+ forms the basis for a full use case later in the iterative development cycle. Each seedling use case needs to
+ convey enough information so that someone, possibly other than the outline writer, can easily go back and
+ expand it into a more informative use case.
+ </p>
+ </li>
+</ul>
+<p>
+ <strong>Solution:</strong> Build an Actor-Goal list, which is a list of actors and their goals that gives you an
+ overview of entire project needs.
+</p>
+<ul>
+ <li>
+ <p>
+ Start by identifying the list of actors who will use the system, and then identify at least one goal for each.
+ Actors without goals indicate that you haven’t adequately defined the system. The actor is beyond the system’s
+ scope, doesn’t belong in the system, or is part of another actor.
+ </p>
+ </li>
+ <li>
+ <p>
+ Likewise, leftover goals can indicate that the system is too complex and you're trying to accomplish too much,
+ or that you haven’t adequately defined all of the necessary actors. Carefully evaluate the leftovers to see if
+ you are just overlooking some detail, or whether they don’t belong in the system.
+ </p>
+ </li>
+ <li>
+ <p>
+ Remove unassociated actors and goals from the list.
+ </p>
+ </li>
+</ul>
+<p>
+ Sometimes, this list may provide enough information to serve as use cases for very small, high-communicating,
+ low-ceremony project teams. Usually, the actor goal list is the first step of identifying use cases.
+</p>
+<h4>
+ Briefs
+</h4>
+<p>
+ <strong>Context:</strong> You have written an Actor-Goal list that outlines your use cases.
+</p>
+<p>
+ <strong>Problem:</strong> Relying solely on an overview to capture the important parts of a system’s behavior is
+ dangerous, because it provides only high-level information and can easily introduce ambiguity into a system.
+</p>
+<p>
+ <strong>Forces:</strong>
+</p>
+<ul>
+ <li>
+ <p>
+ <strong>Although valuable, an Actor-Goal list does not clearly describe a system.</strong> Usually, an outline
+ doesn’t provide enough precision to avoid ambiguity, which can wreak havoc on a project by leading to
+ unnecessary or erroneous development. Yet, an outline is helpful, because you still want an overview that you
+ can easily scan. Unfortunately, with the passing of time or sheer volume of work, it’s too easy to forget
+ details that were obvious to you earlier.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Iterative use case development requires creating placeholders for expansion.</strong> To develop use
+ cases iteratively, you start with sparse use cases, reorganize them, and flesh them out as the system takes
+ shape. Ideally, these placeholders should be clear enough to: 1) unambiguously describe their role in the
+ system, and 2) allow someone to expand the use case, even if they were not involved in writing them originally.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Because outlines are general by nature, do not spend a lot of time, energy, or money writing
+ them.</strong> Outlines provide an inexpensive method of documenting complex ideas in a manner that is easy to
+ follow, and they provide a mechanism for people outside of a project to understand the high-level concepts.
+ While it may take some effort to think things through, you don’t want to waste resources describing your ideas.
+ The system is still in a state of flux at this point, and it is too early to spend much time documenting its
+ shifting details.
+ </p>
+ </li>
+</ul>
+<p>
+ <strong>Solution:</strong> Write two to four sentences per use case, capturing key activities and key-extension
+ handling.
+</p>
+<ul>
+ <li>
+ <p>
+ Expand the Actor-Goal list into <strong>briefs</strong> by writing a two- to four-sentence use cases for each
+ entry in the list.
+ </p>
+ </li>
+ <li>
+ <p>
+ Briefly describe each use case’s main&nbsp;scenario and most important extensions.
+ </p>
+ </li>
+ <li>
+ <p>
+ Include enough information to eliminate ambiguity for at least the main&nbsp;scenario of the system.
+ </p>
+ </li>
+</ul>
+<h4>
+ Improvisational score
+</h4>
+<p>
+ <strong>Context:</strong> You are operating in well-known domains or in situations where writing high-ceremony use
+ cases would require all of your allotted development time.
+</p>
+<p>
+ <strong>Problem:</strong> Writing formal, high-ceremony use cases when lesser detail would suffice wastes time and
+ resources.
+</p>
+<p>
+ Jazz is considered to be “musician’s music,” and jazz players are usually highly skilled. Many jazz musicians prefer to
+ improvise in small, highly skilled teams, such as jazz quartets. To improvise effectively, the musicians must have a
+ thorough understanding of the conventions that form the given musical style, including chord sequences, rhythmic
+ patterns, and melodies. These conventions provide a basic framework for the musicians to interact as a team, while
+ still allowing room for spontaneous creativity.
+</p>
+<p>
+ Likewise, use cases do not always need to be specified in excruciating detail. A far-preferable strategy is simply to
+ define the basic structure of what the developers need to implement. The use cases act as placeholders that may be
+ elaborated later or simply improvised by the developer who implements the use case.
+</p>
+<p>
+ <strong>Forces:</strong>
+</p>
+<ul>
+ <li>
+ <p>
+ <strong>Briefs do not provide enough information.</strong> While useful, use-case briefs describe only the more
+ significant parts of behavior. Often, developers need more information, especially when working in unfamiliar
+ domains or in the heart of the system, where the actor has many choices to make and many paths to follow.
+ Briefs do not describe all of the important events that can happen, nor do they describe the details that go
+ into making choices along the way.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Fully elaborated use cases can be too expensive, time consuming, long to write, and boring to
+ read.</strong> It takes a lot of time and effort to write a formal, fully descriptive set of use cases.
+ Maintaining this set takes even longer. Often, a collection of use cases reaches the point of diminishing
+ returns long before it is completely written, much less formalized. Readers often prefer shorter, simpler use
+ cases over long, complicated ones, because overly detailed use cases can be overwhelming and, frankly speaking,
+ quite boring.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Many groups communicate well enough to resolve ambiguities on the fly.</strong> While briefs may be
+ insufficient, stakeholders don’t always need everything to be spelled out for them. Developers are usually
+ capable of asking questions and filling out the necessary detail from their own domain knowledge. Many people
+ can work with a fair level of ambiguity, and most organizations possess what is often referred to as their
+ “core competencies.” Mature organizations with strong domain knowledge can survive, and even thrive, using more
+ informal, less precise use cases.
+ </p>
+ </li>
+</ul>
+<p>
+ <strong>Solution:</strong> Specify the use cases at a low level of precision, allowing the developers to fill in the
+ missing details as necessary. The level of precision required depends on the background experiences of the development
+ team. Skip the less meaningful fields on the template, and write the Main Scenario section as a simple paragraph.
+ Describe key-extension handling in the next paragraph or two. Be prepared to resolve ambiguities and expand detail on
+ the fly throughout the project.
+</p>
+<p>
+ When you can rely upon open and frequent communication among the developers and customer, write the use case with less
+ detail and precision. The developers can fill in the gaps by asking users or by using knowledge of the domain. However,
+ the developers need a thorough understanding of the business context to be able to fill out the details themselves.
+ Even the most knowledgeable developer will still need access to the customers and users to get answers to questions and
+ clarify requirements.
+</p>
+<p>
+ Ideally, the project will be structured to enable effective communication between the customer and the developers.
+ Typically, this will involve having a small, co-located team, with the developers having easy access to the users
+ throughout the project. The risk of misunderstanding can be resolved by frequent incremental delivery if the
+ development organization has a relatively low-ceremony culture.
+</p>
+<p>
+ Jazz improvisation does not always work. It can become tedious and unpleasant to listen to, even for the committed
+ connoisseur. For this reason, you also need feedback from the audience to determine the success of the improvisations.
+ Multi-level or two-tier reviews are critical to success.
+</p>
+<p>
+ Improvisation may not always be suitable for the organizational culture, a full <strong>symphonic score</strong> may be
+ preferable in large, high-ceremony teams (see section that follows). For instance, I once watched a conductor toss his
+ baton away in disgust when a pianist improvised to such an extent that the orchestra could not follow the score. If the
+ organization deems the risk of improvising to be unacceptably high, then you can specify the use cases with a higher
+ level of detail and precision. You could start with a strategy of specifying low levels of detail and precision, and
+ then adapt as necessary.
+</p>
+<h4>
+ Symphonic score
+</h4>
+<p>
+ <strong>Context:</strong> Writing structure for high-ceremony situations, such as when there are many developers or
+ when development teams are geographically dispersed.
+</p>
+<p>
+ <strong>Problem:</strong> Writing low-ceremony use cases for high-ceremony situations raises the risk of
+ miscommunication to unacceptable levels.
+</p>
+<p>
+ A conductor’s version of a symphonic score contains the music for the entire orchestra, as well as any accompanying
+ vocals. The parts to be performed by different voices or instruments are written on a separate staff, with all of the
+ staves aligned, one above another. This score specifies each note and its associated timing in precise detail, so that
+ the orchestra can perform a symphony as the composer intended.
+</p>
+<p>
+ As with use cases, a score tells the musician what to play, not how to play it. For most symphonies, the orchestra will
+ not be able to meet the composer, so instead, they must rely upon the director to interpret the score and the
+ composer's intentions.
+</p>
+<p>
+ <strong>Forces:</strong>
+</p>
+<ul>
+ <li>
+ <p>
+ <strong>Certain development situations and cultures require high degrees of formality.</strong> Some
+ organizations operate in a highly formal manner, thus require a highly formal process. While this formality may
+ not be desirable, it is the company's way of doing business, so things need to be done that way. Other
+ organizations are highly formal because they do highly complex, life-critical work, where even small failures
+ could have disastrous consequences. For instance, no one would feel comfortable flying on an airliner with an
+ off-the-shelf, one-size-fits-all flight management system.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>The cost of repairing miscommunication is high.</strong> It is easy to write vague, inadequate use
+ cases full of ambiguity. Use cases can be too brief and ambiguous, or contain domain-specific details that may
+ be beyond the understanding of many stakeholders. Either way, they provide an opportunity for a
+ misunderstanding that leads to an incorrect implementation. The cost of correcting these mistakes depends on
+ when they are discovered. <em>Earlier</em> is cheaper than <em>later</em>, especially when later means
+ customers finding the problem in the delivered product. To avoid miscommunication, aim to write use cases that
+ are general enough for all of the stakeholders to follow, yet precise enough for the developers to use when
+ building the system.
+ </p>
+ </li>
+ <li>
+ <p>
+ <strong>Developers need detail for implementing steps, business rules, data fields, and, especially, for
+ handling extensions.</strong> No one has developed a program that can take a set of use cases as input, and
+ churn out a completed system. Even the best-case tools seem to require human intervention to flesh out details
+ and resolve ambiguities. Similarly, developers who do not understand the business context or lack domain
+ expertise may not be able to fully comprehend a product. In an ideal project, software developers would have
+ access to the domain experts to ask questions, so they could fill in any areas that may have been missed (see
+ <em>Improvisational score</em>, previously). But often, they do not ask. Therefore, they misunderstand the more
+ complex or ambiguous use cases in the set. To develop a system correctly, a team needs either access to domain
+ experts or additional information that describe the steps, business rules, data fields, and extension handling
+ that they are implementing.
+ </p>
+ </li>
+</ul>
+<p>
+ <strong>Solution:</strong> Specify your use cases with a high level of precision, explicitly filling in all of the
+ details in the use case template, while staying technology-neutral. The level of precision required depends on the
+ background experiences of the development team.
+</p>
+<p>
+ Intuition may tell you that if some detail is good, then more must be better. However, be careful about falling into
+ the trap of over-specifying details. It’s naive to believe that everyone who reads your use cases will be able to
+ understand them. Different people may interpret the use cases differently. Prepare for this eventuality in your
+ process, and avoid the tendency to over-specify your use cases. If you try to specify a use case in too much detail,
+ you may fall into the classic analysis paralysis trap.
+</p>
+<p>
+ People are often tempted to address the communication problem by trying to explain the business domain within the use
+ cases. In a similar manner, they include too much technical detail. Succumbing to these temptations by explaining the
+ business domain or including technical details is always a mistake, because it complicates the process and obfuscates
+ the requirements. The reader of the use cases cannot distinguish the real requirements from the boring background
+ information, so will soon get distracted and lose interest. Instead, include this information in an extra section.
+</p>
+<p>
+ If you are handing over the requirements to a development team whose members are unfamiliar with the domain, then you
+ will need an alternative strategy for teaching them the domain knowledge.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/use_case_model.xmi b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/use_case_model.xmi
new file mode 100644
index 0000000..b81cc01
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/guidelines/use_case_model.xmi
@@ -0,0 +1,296 @@
+<?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: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="_AGvpcMM3EdmSIPI87WLu3g"
+ name="uc_model,_0VAUsMlgEdmt3adZL5Dmdw" guid="_AGvpcMM3EdmSIPI87WLu3g" changeDate="2007-02-28T11:40:11.200-0800"
+ version="1.0.0">
+ <mainDescription><h3>
+ Introduction
+</h3>
+<p>
+ The key to successful iterative development is ensuring that the development team maximizes stakeholder value and
+ minimizes risk early in the lifecycle, while minimizing re-work later.&nbsp; This imposes some constraints on how we
+ develop the use-case model.
+</p>
+<p>
+ At one extreme is the classical waterfall approach, which attempts to&nbsp;detail all of the requirements prior to
+ design and implementation.&nbsp; This approach delays delivery of stakeholder value and risk reduction unnecessarily.
+</p>
+<p>
+ At the other extreme is&nbsp;beginning development prior to understanding what the system must do.&nbsp; This approach
+ results in significant, and costly, re-work later in the lifecycle.
+</p>
+<p>
+ A better approach is to detail only those requirements which will be the focus of development in the next iteration (or
+ two).&nbsp; Selection of these requirements is driven by value and risk, and thus requires as a minimum an abstract
+ understanding of the "big-picture".
+</p>
+<p>
+ The following discussion will outline the approach used to evolve the use-case model to achieve these goals.
+</p>
+<h3>
+ <a id="How the Use-Case Model Evolves" name="How the Use-Case Model Evolves">How the Use-Case Model Evolves</a>
+</h3>
+<p>
+ The recommended approach to evolving the use-case model takes a "breadth before depth" approach.&nbsp; In this
+ approach, one identifies the actors and use cases and outlines them quickly.&nbsp; Based on this knowledge, one can
+ then perform an initial assessment of risk and priorities and thus focus the effort of&nbsp;detailing&nbsp;the use
+ cases on the right areas.
+</p>
+<h4>
+ Inception
+</h4>
+<p>
+ The purpose of inception is to understand the scope of the system.&nbsp; We need to understand the main purpose of the
+ system, what is within the scope of the system, and what is external to the system.&nbsp; We should strive to list all
+ the primary actors and use cases, however we don't have the luxury of being able to detail all of these requirements at
+ this time.&nbsp; Strive to&nbsp;identify by name&nbsp;~80% of the primary actors and use cases and provide a brief
+ description (one - three sentences) for each.
+</p>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <h5>
+ Identify Stakeholders
+ </h5>
+ <p>
+ Begin by listing all the external stakeholders for the system.&nbsp; These individuals will be the source of the
+ requirements.
+ </p>
+ <h5>
+ Identify Actors
+ </h5>
+ <p>
+ Name and describe the primary actors.&nbsp; See <a class="elementLinkWithType"
+ href="./../../../opn.tech.prac.rqmts_with_use_cases/guidances/guidelines/find_and_outline_actors_and_ucs_BB5516A9.html"
+ guid="_eyL0wCu-EdqSxKAVa9kmvA">Guideline: *Find and Outline Actors and Use Cases</a>.
+ </p>
+ <h5>
+ Identify Use Cases
+ </h5>
+ <p>
+ For each actor, ask "what does this actor want to accomplish with the system"?&nbsp; This will reveal the primary
+ use cases for the system.&nbsp; Name and describe each of these as you discover them.
+ </p>
+ <h5>
+ Update the Use-Case Model
+ </h5>
+ <p>
+ Update the use case model to capture the actor and use case names and brief description.&nbsp; Capture the
+ relationship between the actors and use cases.
+ </p>
+ <h5>
+ Outline the Basic Flows
+ </h5>
+ <p>
+ For those use cases that are considered high priority by the stakeholders, or high risk by the development team,
+ capture a step-by-step description of the Basic Flow.&nbsp; Don't worry about structuring the flow at this
+ point.&nbsp; Focus on capturing the dialogue between the actor and the system and the key requirements for the
+ system.
+ </p>
+ <h5>
+ Identify Alternate Flows
+ </h5>
+ <p>
+ As you work through the Basic Flows, ask: "What can go wrong?"; "What options are available at this point?";
+ etc.&nbsp; These types of questions will reveal alternate flows.&nbsp; Capture these, giving each a name and brief
+ description.&nbsp; Fight the urge to detail these alternate flows at this time.
+ </p>
+ <h5>
+ Refactor the Use Case Model
+ </h5>
+ <p>
+ Based on the Basic Flows you have identified, determine if there is common behavior that could be factored out into
+ &lt;&lt;include&gt;&gt; use cases.&nbsp; Refactor the Use Case model accordingly.
+ </p>
+ <h5>
+ Prioritize Use Cases
+ </h5>
+ <p>
+ Given the abstract description you now have of the requirements, work with stakeholders to prioritize the use
+ cases.&nbsp; This will be the primary input to iteration planning.
+ </p>
+</blockquote>
+<h4>
+ Elaboration
+</h4>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p>
+ The purpose of elaboration is to demonstrate the feasibilty of&nbsp;the solution prior to committing additional
+ resources.&nbsp; To be successful, one should demonstrate that stakeholder value can be delivered and that the risk
+ of continuing is acceptable.&nbsp; We should strive to detail and implement ~20% of the scenarios.&nbsp; These
+ scenarios should be selected to achieve good coverage of the architecture (for example, a vertical slice through
+ the architecture, touching as many&nbsp;components and interfaces as possible, is preferred to elaborating the GUI
+ only).
+ </p>
+ <h5>
+ Detail Basic Flow
+ </h5>
+ <p>
+ For those UC selected for the next iteration, spend the time to detail the basic flow now.&nbsp; See <a
+ class="elementLinkWithType"
+ href="./../../../opn.tech.prac.rqmts_with_use_cases/guidances/guidelines/detail_ucs_and_scenarios_6BC56BB7.html"
+ guid="_4BJ_YCxSEdqjsdw1QLH_6Q">Guideline: ***Detail Use Cases and Scenarios</a>.
+ </p>
+ <h5>
+ Detail Alternate Flow
+ </h5>
+ <p>
+ For those alternate flows selected for the next iteration, spend the time to detail the flows now.
+ </p>
+ <h5>
+ Update the Use-Case Model
+ </h5>
+ <p>
+ Update the Use-Case Model to capture any refinements made as a result of your work.&nbsp; Depending upon the
+ complexity of the system, you may want to introduce packages to group the use cases in a logical manner to simplify
+ communications, iteration planning, and parallel development.
+ </p>
+</blockquote>
+<h4>
+ Construction
+</h4>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p>
+ The purpose of construction is to incrementally deliver functionality (and value).&nbsp; Working from the iteration
+ plan, continue detailing the remaining requirements.&nbsp; Shoot for completion of ~90 - ~95% of use cases by the
+ end of construction.
+ </p>
+ <h5>
+ Detail Basic Flows
+ </h5>
+ <p>
+ For those UC selected for the next iteration, spend the time to detail the basic flow now.&nbsp; See <a
+ class="elementLinkWithType"
+ href="./../../../opn.tech.prac.rqmts_with_use_cases/guidances/guidelines/detail_ucs_and_scenarios_6BC56BB7.html"
+ guid="_4BJ_YCxSEdqjsdw1QLH_6Q">Guideline: ***Detail Use Cases and Scenarios</a>.
+ </p>
+ <h5>
+ Detail Alternate Flows
+ </h5>
+ <p>
+ For those alternate flows selected for the next iteration, spend the time to detail the flows now.
+ </p>
+ <h5>
+ Update the Use-Case Model
+ </h5>
+ <p>
+ Update the Use-Case Model to capture any refinements made as a result of your work.
+ </p>
+</blockquote>
+<h4>
+ Transition
+</h4>
+<p>
+ The purpose of transition is to make the system operational in its intended environment.&nbsp; Some requirements will
+ still be uncovered at this point, but if we have done things right they should not stress the design.&nbsp; The
+ remaining ~5% to ~10% of use cases should be detailed and implemented in this phase.
+</p>
+<h3>
+ <a id="Avoiding Functional Decomposition" name="Avoiding Functional Decomposition">Avoiding Functional
+ Decomposition</a>
+</h3>
+<p>
+ A common pitfall for those new to use-case models is to perform a&nbsp;functional decomposition of the system. This
+ results in many small "use cases", that on their own do not deliver the "observable result of value" to the
+ actor.&nbsp; To avoid this, watch for the following symptoms:
+</p>
+<ul>
+ <li>
+ <strong>Small</strong> use cases, meaning that the description of the flow of events is only one or a few
+ sentences.
+ </li>
+ <li>
+ <strong>Many</strong> use cases, meaning that the number of use cases is some multiple of a hundred, rather than a
+ multiple of ten.
+ </li>
+ <li>
+ Use-case names that are constructions such as "do this operation on this particular data" or "do this function with
+ this particular data". For example, "Enter Personal Identification Number in an ATM machine" should not be modeled
+ as a separate use case for the ATM machine, because no one would use the system to do just this. A use case is a
+ complete flow of events that results in something of value to an actor.
+ </li>
+</ul>
+<p>
+ To avoid functional decomposition, make sure that the use-case model helps answer these kinds of questions:
+</p>
+<ul>
+ <li>
+ What is the context of the system?
+ </li>
+ <li>
+ Why are you building this system?
+ </li>
+ <li>
+ What does the user want the system to do?
+ </li>
+ <li>
+ How&nbsp;do the users benefit from the system?
+ </li>
+</ul>
+<h3>
+ <a id="Structuring the Use-Case Model" name="Structuring the Use-Case Model">Structuring the Use-Case Model</a>
+</h3>
+<p>
+ There are three main reasons for structuring the use-case model:
+</p>
+<ul>
+ <li>
+ To make the use cases easier to understand.
+ </li>
+ <li>
+ To partition common behavior described within many use cases
+ </li>
+ <li>
+ To make the use-case model easier to maintain.
+ </li>
+</ul>
+<p>
+ Structuring is not the first thing you do, however. There is no point in structuring the use cases until you know a bit
+ more about their behavior than a one-sentence description. You should at least have established a step-by-step outline
+ for the flow of events of the use case to make sure that your decisions are based on an accurate understanding of the
+ behavior.
+</p>
+<p>
+ There are several advanced modeling concepts available in the literature for&nbsp;structuring the use-case model,
+ however, following the principle of "keep-it-simple" only the most useful of these, namely the &lt;&lt;include&gt;&gt;
+ relationship is discussed in this process.&nbsp; This relationship permits one to factor out common behavior into a
+ separate use case that is "include" in other use cases.&nbsp; See <a class="elementLinkWithType"
+ href="./../../../core.tech.common.base/guidances/concepts/use_case_model_CD178AF9.html"
+ guid="_2jyfUAhVEduRe8TeoBmuGg">Concept: *Use-Case Model</a>&nbsp;for more&nbsp;details.
+</p>
+<p>
+ Another aspect of&nbsp;structuring the use-case model for easier understanding is grouping the use cases into packages.
+ The use-case model can be organized as a hierarchy of use-case packages. For more information on use-case packages, see
+ <a class="elementLinkWithType"
+ href="./../../../core.tech.common.base/guidances/concepts/use_case_model_CD178AF9.html"
+ guid="_2jyfUAhVEduRe8TeoBmuGg">Concept: *Use-Case Model</a>.
+</p>
+<h3>
+ <a id="Use Cases Are Always Related to Actors" name="Use Cases Are Always Related to Actors">Relationship Between Use
+ Cases and Actors</a>
+</h3>
+<p>
+ Running each use case includes communication with one or more actors. A use-case instance is always started by an actor
+ asking the system to do something. This implies that every use case should have communicates-associations with actors.
+ The reason for this rule is to enforce that the system provides only the functionality that users need and nothing
+ else. Having use cases that no one requests is an indication that something is wrong in the use-case model or in the
+ requirements.
+</p>
+<p>
+ However, there are some exceptions to this rule:
+</p>
+<ul>
+ <li>
+ An&nbsp;"included" use case might not interact with an actor if the base use case does.
+ </li>
+ <li>
+ A use case may be initiated according to a schedule (for example, once a week or once a day), which means that the
+ system clock is the initiator. The system clock is internal to the system; therefore, the use case is not initiated
+ by an actor but by an internal system event. If no other actor interaction occurs in the use case, it will not have
+ any associations to actors. However, for clarity, you can use "time" as an actor to show how the use case is
+ initiated in your use-case diagrams. <strong>CAUTION:</strong> if you have a lot of "time" actors in your model,
+ challenge them.&nbsp; Perhaps you missed a real actor, such as an administrator responsible for scheduling reports,
+ etc.
+ </li>
+</ul></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/roadmaps/how_to_adopt.xmi b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/roadmaps/how_to_adopt.xmi
new file mode 100644
index 0000000..e338381
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/roadmaps/how_to_adopt.xmi
@@ -0,0 +1,41 @@
+<?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: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="-3WNAtOgFvwsJtFvhDugsVA"
+ name="new_roadmap,_PJKZkMRfEdyBt8f9agIerg" guid="-3WNAtOgFvwsJtFvhDugsVA" changeDate="2008-02-29T10:35:38.187-0800"
+ version="7.2.0">
+ <mainDescription><h3>
+ Getting Started&nbsp;
+</h3>
+<p>
+ After getting some basic familiarity with the concept of use cases, consider identifying use cases in a workshop
+ environment, led by someone experienced in writing use cases. Detail one or a few example scenarios to serve as an
+ example for other use case authors, to set a standard for format, style, and level of detail.
+</p>
+<p>
+ Some teams prefer to identify all use cases and actors first, capturing those in an UML use-case diagram, or other sort
+ of visual notation. Then they iteratively detail the use cases assigned to the current or next iteration, by outlining
+ the steps in the use case main flow and alternative flows. When these steps and flows are detailed in the amount needed
+ for development to start, it is useful to group flows in what is called use-case scenarios. Some teams prefer to
+ identify scenarios first and then write the use cases in a more structured way later, by grouping related scenarios
+ together. Scenarios can be used as a unit of work assignment and progress measurement on how use cases are analyzed,
+ designed, implemented and tested throughout the project.
+</p>
+<p>
+ As you get more comfortable with this practice, consider supplementing your use cases with storyboards, activity
+ diagrams, and additional requirements techniques. Modeling use cases in UML diagrams or in modeling tools can be
+ helpful when there are lots of use cases, but start with a focus on the text and some key scenarios.
+</p>
+<h4>
+ Common Pitfalls
+</h4>
+<p>
+ Try to avoid applying&nbsp;functional decomposition approach to use cases. That may&nbsp;lead you to find too many use
+ cases,&nbsp;and use-case descriptions that are half page or&nbsp;less in length. On the other hand, finding too few use
+ cases&nbsp;may result in overloaded use cases. It&nbsp;may lead to long and complex use-case descriptions. Try to find
+ a balance that makes sense for your team, stakeholders and type of system you are developing. There are discussions
+ around what is&nbsp;the appropriate number of use cases for a system.&nbsp;The suggestion is that even large, complex
+ systems will have no more than a couple dozen use cases on average.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/supportingmaterials/practice_enablement.xmi b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/supportingmaterials/practice_enablement.xmi
new file mode 100644
index 0000000..76ba13e
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/supportingmaterials/practice_enablement.xmi
@@ -0,0 +1,42 @@
+<?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="-RIEhRIYgm6Ja2Jnth9IuhA"
+ name="new_supporting_material,_i--RUNXBEdylRpA9TBY1SQ" guid="-RIEhRIYgm6Ja2Jnth9IuhA"
+ changeDate="2008-02-12T11:02:46.950-0800" version="7.2.0">
+ <mainDescription><h3>
+ Books and Articles<br />
+ <br />
+</h3>
+<table width="100%" summary="layout table" border="0">
+ <tbody>
+ <tr>
+ <td colspan="2">
+ Kurt Bittner and Ian Spence 2003. <i>Use Case Modeling.</i> Addison Wesley Longman.
+ </td>
+ </tr>
+ <tr>
+ <td width="10%">
+ </td>
+ <td style="PADDING-BOTTOM: 10px" width="78%">
+ Comprehensive coverage of use case techniques and practices, including useful examples showing how use-case
+ specifications evolve over time.
+ </td>
+ </tr>
+ <tr>
+ <td colspan="2">
+ Alistair Cockburn 2001. <i>Writing Effective Use Cases.</i> Addison Wesley Longman.
+ </td>
+ </tr>
+ <tr>
+ <td width="10%">
+ </td>
+ <td style="PADDING-BOTTOM: 10px" width="78%">
+ Excellent guidance for those who need to write use cases. Multiple styles and techniques contrasted with
+ insight in an unbiased way. Many helpful tips to improve your use cases.
+ </td>
+ </tr>
+ </tbody>
+</table></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/supportingmaterials/release_info_uc_driven_dev.xmi b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/supportingmaterials/release_info_uc_driven_dev.xmi
new file mode 100644
index 0000000..0b5b303
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/supportingmaterials/release_info_uc_driven_dev.xmi
@@ -0,0 +1,23 @@
+<?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="-pnWJpKCphl8ewGRYM4tDOQ"
+ name="release_info_uc_driven_dev,_Z87SYMuXEdyTA_Xoy-01eg" guid="-pnWJpKCphl8ewGRYM4tDOQ"
+ changeDate="2008-01-25T14:47:35.279-0800" version="7.2.0">
+ <mainDescription><h3>
+ Use-Case Driven Development Practice
+</h3>
+<p>
+ Version 1.0
+</p>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p>
+ [*** NOT YET RELEASED ***]
+ </p>
+ <p>
+ This is the initial release of this practice.
+ </p><br />
+ <br />
+</blockquote><br /></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/supportingmaterials/resources/bookc.gif b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/supportingmaterials/resources/bookc.gif
new file mode 100644
index 0000000..7f2ab85
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/supportingmaterials/resources/bookc.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/supportingmaterials/resources/bookcL.gif b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/supportingmaterials/resources/bookcL.gif
new file mode 100644
index 0000000..6c5b064
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/supportingmaterials/resources/bookcL.gif
Binary files differ
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/termdefinitions/system_wide_requirement.xmi b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/termdefinitions/system_wide_requirement.xmi
new file mode 100644
index 0000000..46b544e
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/termdefinitions/system_wide_requirement.xmi
@@ -0,0 +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: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="-ketzwgDgY82DMyfuHqu3Cw"
+ name=",_U_olUEvDEdunZcj9T5hrMQ" guid="-ketzwgDgY82DMyfuHqu3Cw" changeDate="2006-12-21T09:32:14.441-0800"
+ version="1.0.0">
+ <mainDescription>System-wide requirements are requirements that&nbsp;define necessary system quality attributes&nbsp;such as performance,
+usability and reliability, as well as global functional requirements&nbsp;that are not captured in behavioral requirements
+artifacts such as use-cases.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/termdefinitions/use_case_scenario.xmi b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/termdefinitions/use_case_scenario.xmi
new file mode 100644
index 0000000..f219164
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/guidances/termdefinitions/use_case_scenario.xmi
@@ -0,0 +1,10 @@
+<?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: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="-t3jNM5ZWkYtzB8A4Chz2Vw"
+ name=",_oXmYMEvGEdunZcj9T5hrMQ" guid="-t3jNM5ZWkYtzB8A4Chz2Vw">
+ <mainDescription>Represents specific instances of the use case that correspond to specific inputs from the Actor or to specific conditions
+in the environment. Each scenario describes alternate ways that the system provides a behavior, or it may describe failure
+or exception cases</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/plugin.xmi b/praclib/temp/practice.tech.use_case_driven_dev.base/plugin.xmi
new file mode 100644
index 0000000..6e4945a
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/plugin.xmi
@@ -0,0 +1,367 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_GbYfYbPaEduocbW-TPTq7A"
+ guid="_GbYfYbPaEduocbW-TPTq7A">
+ <resourceDescriptors xmi:id="_7ymQsCxSEdqjsdw1QLH_6Q" id="-78ko4CuOJERKJF9ZvwMUBQ"
+ uri="guidances/guidelines/detail_ucs_and_scenarios.xmi"/>
+ <resourceDescriptors xmi:id="_BQ2N8CF7Edu3VKXZx45D3A" id="-BdYFG4-dbPBGFzF9z6KGPA"
+ uri="guidances/guidelines/system_wide_requirements.xmi"/>
+ <resourceDescriptors xmi:id="_gjU_EUvQEdunZcj9T5hrMQ" id="-ketzwgDgY82DMyfuHqu3Cw"
+ uri="guidances/termdefinitions/system_wide_requirement.xmi"/>
+ <resourceDescriptors xmi:id="_TgQIUUvmEdunZcj9T5hrMQ" id="-t3jNM5ZWkYtzB8A4Chz2Vw"
+ uri="guidances/termdefinitions/use_case_scenario.xmi"/>
+ <resourceDescriptors xmi:id="_jtUSACu-EdqSxKAVa9kmvA" id="-Rcm_MlViENAvFFyIe9V3dQ"
+ uri="guidances/guidelines/identify_and_outline_actors_and_ucs.xmi"/>
+ <resourceDescriptors xmi:id="__WjDgAXmEduZUPWQRyV4zQ" id="-pQrBSyxJHLLodLbS4R_Zdw"
+ uri="guidances/guidelines/use_case_formats.xmi"/>
+ <resourceDescriptors xmi:id="_ePUlgAFoEduDPKiaP0pu-Q" id="-Yt8TXGkE1rwydXR34apsrg"
+ uri="tasks/identify_and_outline_requirements.ucm.xmi"/>
+ <resourceDescriptors xmi:id="_QATTEPV_EdmdHa9MmVPgqQ" id="_P9iS8PV_EdmdHa9MmVPgqQ"
+ uri="tasks/identify_and_outline_requirements.xmi"/>
+ <resourceDescriptors xmi:id="_7IDxgEbEEdyx8quJU3Grxg" id="-9sNgONA1WJCxf12B40uDgw"
+ uri="tasks/detail_system_wide_requirements.xmi"/>
+ <resourceDescriptors xmi:id="_Atr9QUbFEdyx8quJU3Grxg" id="-locCQOxOUM8zej2tBD6M6Q"
+ uri="tasks/detail_use_case_scenarios.ucm.xmi"/>
+ <resourceDescriptors xmi:id="_GIeDcED9EdyoefaQkqWN_Q" id="-oFAa8Uu6tr_GkE_E0iycdQ"
+ uri="tasks/detail_use_case_scenarios.xmi"/>
+ <resourceDescriptors xmi:id="_RlhpcEj8Edyi3_jfs__bIQ" id="-4E4u3crgCavkHJqTClP8cA"
+ uri="guidances/concepts/requirements.ucdd.xmi"/>
+ <resourceDescriptors xmi:id="_m9t2kPL5Edm6Nvont3uinw" id="_AGvpcMM3EdmSIPI87WLu3g"
+ uri="guidances/guidelines/use_case_model.xmi"/>
+ <resourceDescriptors xmi:id="_BaPxINb2Edq_LtLvi4w2yw" id="-CFYVionNDLkMw6SG6runQA"
+ uri="guidances/guidelines/uc_realizations.xmi"/>
+ <resourceDescriptors xmi:id="_GXZKIaH-Edy1C4Jn7ybs3g" id="-AamnbYmwP0YHOBlj7huJjw"
+ uri="customcategories/use_case_driven_dev_practice.xmi"/>
+ <resourceDescriptors xmi:id="_hwxJQLscEdyfAY9BXNFkDg" id="-wv4JAmTQ0R_KjP76LgDITg"
+ uri="guidances/concepts/use_case.ucdd.xmi"/>
+ <resourceDescriptors xmi:id="_qlNIcbseEdyfAY9BXNFkDg" id="-3kVaHsAKwWzKBx12XV-xTg"
+ uri="guidances/concepts/use_case.ucm.xmi"/>
+ <resourceDescriptors xmi:id="_l0ilUcRfEdyBt8f9agIerg" id="-3WNAtOgFvwsJtFvhDugsVA"
+ uri="guidances/roadmaps/how_to_adopt.xmi"/>
+ <resourceDescriptors xmi:id="_Z_dB8cuXEdyTA_Xoy-01eg" id="-pnWJpKCphl8ewGRYM4tDOQ"
+ uri="guidances/supportingmaterials/release_info_uc_driven_dev.xmi"/>
+ <resourceDescriptors xmi:id="_6oT6INXBEdylRpA9TBY1SQ" id="-RIEhRIYgm6Ja2Jnth9IuhA"
+ uri="guidances/supportingmaterials/practice_enablement.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_GbYfULPaEduocbW-TPTq7A" name="practice.tech.use_case_driven_dev.base"
+ guid="_GbYfULPaEduocbW-TPTq7A" briefDescription="This plug-in contains the method elements needed if use cases are used as a requirements technique. It also contains guidelines for Use-Case-Driven Development and Testing. "
+ changeDate="2008-01-25T14:44:05.481-0800" changeDescription="Review comments:||1. Packaging for use case driven dev't practice should be:|	- a package for the practice as a whole (same name as plug-in)|	(tasks, work products, and guidance supporting these go in this package)|	- guidance filling slots can be in separate packages|		development_guidance|		test_guidance||2. Moved the uc checklist into common">
+ <copyrightStatement href="uma://_iVydgENdEdy245g62lfWcA#_cTs20KzREduOqvpk_MDLfQ"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_GbYfUbPaEduocbW-TPTq7A"
+ name="Content" guid="_GbYfUbPaEduocbW-TPTq7A">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_GbYfUrPaEduocbW-TPTq7A"
+ name="Categories" guid="_GbYfUrPaEduocbW-TPTq7A">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_GbYfU7PaEduocbW-TPTq7A"
+ name="Domains" guid="_GbYfU7PaEduocbW-TPTq7A"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_GbYfVLPaEduocbW-TPTq7A"
+ name="Disciplines" guid="_GbYfVLPaEduocbW-TPTq7A"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_GbYfVbPaEduocbW-TPTq7A"
+ name="RoleSets" guid="_GbYfVbPaEduocbW-TPTq7A"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_GbYfVrPaEduocbW-TPTq7A"
+ name="WP Types" guid="_GbYfVrPaEduocbW-TPTq7A"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_GbYfV7PaEduocbW-TPTq7A"
+ name="Tools" guid="_GbYfV7PaEduocbW-TPTq7A"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_GbYfWLPaEduocbW-TPTq7A"
+ name="StandardCategories" guid="_GbYfWLPaEduocbW-TPTq7A"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_GbYfWbPaEduocbW-TPTq7A"
+ name="CustomCategories" guid="_GbYfWbPaEduocbW-TPTq7A">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_GbYfWrPaEduocbW-TPTq7A"
+ name="Hidden" guid="_GbYfWrPaEduocbW-TPTq7A">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_GbYfW7PaEduocbW-TPTq7A"
+ name="Custom Categories" guid="_GbYfW7PaEduocbW-TPTq7A" categorizedElements="_lmNCoJ-lEdyBk-WQzMU-FQ _fj1tAMuWEdyTA_Xoy-01eg"/>
+ </childPackages>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_lmNCoJ-lEdyBk-WQzMU-FQ"
+ name="use_case_driven_dev_practice" guid="_lmNCoJ-lEdyBk-WQzMU-FQ" briefDescription="This practice describes how use cases can be used to capture requirements and drive design and testing."
+ presentationName="Use-Case Driven Development" shapeicon="customcategories/resources/pract_dgm32.gif"
+ nodeicon="customcategories/resources/pract_obj.gif" categorizedElements="_PJKZkMRfEdyBt8f9agIerg _i--RUNXBEdylRpA9TBY1SQ _W3uAYM-GEdymYdYa6iWnUQ _NrZl0MSFEdyBt8f9agIerg _K5oBwMSFEdyBt8f9agIerg _RK7AsMSFEdyBt8f9agIerg">
+ <presentation xmi:id="-AamnbYmwP0YHOBlj7huJjw" href="uma://-AamnbYmwP0YHOBlj7huJjw#-AamnbYmwP0YHOBlj7huJjw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_K5oBwMSFEdyBt8f9agIerg"
+ name="tasks" guid="_K5oBwMSFEdyBt8f9agIerg" presentationName="Tasks"
+ shapeicon="customcategories/resources/task_dgm32.gif" nodeicon="customcategories/resources/task_obj.gif"
+ categorizedElements="_P9cMUPV_EdmdHa9MmVPgqQ _SL7N0LPdEduocbW-TPTq7A _4z8Z0EbEEdyx8quJU3Grxg"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_NrZl0MSFEdyBt8f9agIerg"
+ name="work_products" guid="_NrZl0MSFEdyBt8f9agIerg" presentationName="Work Products"
+ shapeicon="customcategories/resources/workproduct_dgm32.gif" nodeicon="customcategories/resources/workproduct_obj.gif">
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0VGbUMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_W2SgEDR5EdutE_HNDTJk5Q"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_BVh9cL-CEdqb7N6KIeDL8Q"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_RK7AsMSFEdyBt8f9agIerg"
+ name="guidance" guid="_RK7AsMSFEdyBt8f9agIerg" presentationName="Guidance"
+ shapeicon="customcategories/resources/bookcL.gif" nodeicon="customcategories/resources/bookc.gif"
+ categorizedElements="_4BJ_YCxSEdqjsdw1QLH_6Q _eyL0wCu-EdqSxKAVa9kmvA _wr24gNcGEdqz_d2XWoVt6Q _qq0GMAXkEduj_7BEUj1JfQ _2uan8NbyEdqu5o2S60g5LA"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_fj1tAMuWEdyTA_Xoy-01eg"
+ name="contributions_to_nav_building_blocks" guid="_fj1tAMuWEdyTA_Xoy-01eg"
+ categorizedElements="_sgfwsMuWEdyTA_Xoy-01eg _tcGdUMuWEdyTA_Xoy-01eg _ud9i8MuWEdyTA_Xoy-01eg _u5iEoMuWEdyTA_Xoy-01eg _wDTJEMuWEdyTA_Xoy-01eg _prj5AMuYEdyTA_Xoy-01eg _DgjhEMuZEdyTA_Xoy-01eg _sn0ZUMuZEdyTA_Xoy-01eg _JhKYoMuZEdyTA_Xoy-01eg _jxw58NQxEdyM_J8-fv54DA"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_sgfwsMuWEdyTA_Xoy-01eg"
+ name="release_info.assign" guid="_sgfwsMuWEdyTA_Xoy-01eg" variabilityType="contributes"
+ categorizedElements="_Z87SYMuXEdyTA_Xoy-01eg">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCIHYcRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_tcGdUMuWEdyTA_Xoy-01eg"
+ name="artifact_list.assign" guid="_tcGdUMuWEdyTA_Xoy-01eg" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4YMRdEdyD76CYS6Ta7A"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_BVh9cL-CEdqb7N6KIeDL8Q"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_W2SgEDR5EdutE_HNDTJk5Q"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0VGbUMlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_ud9i8MuWEdyTA_Xoy-01eg"
+ name="checklist_list.assign" guid="_ud9i8MuWEdyTA_Xoy-01eg" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_pGt9MMReEdyD76CYS6Ta7A"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Checklist" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0VrDEMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Checklist" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0kNwINk1Edq2Q8qZoWbvGA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Checklist" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0U6OEMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Checklist" href="uma://_OOB2AAouEdyhlpBPrduOMw#_Vael8CGMEdu3VKXZx45D3A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_u5iEoMuWEdyTA_Xoy-01eg"
+ name="concept_list.assign" guid="_u5iEoMuWEdyTA_Xoy-01eg" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4Y8RdEdyD76CYS6Ta7A"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_zGqO0MDpEduTGJ8i4u8TMw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_KudM0NcJEdqz_d2XWoVt6Q"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_2jyfUAhVEduRe8TeoBmuGg"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_VXZ5wO0IEdqHTdbLTmC5IQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_wDTJEMuWEdyTA_Xoy-01eg"
+ name="example_list.assign" guid="_wDTJEMuWEdyTA_Xoy-01eg" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4ZMRdEdyD76CYS6Ta7A"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Example" href="uma://_OOB2AAouEdyhlpBPrduOMw#_JLOiIMNvEdu2IdAIaWZyAw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Example" href="uma://_OOB2AAouEdyhlpBPrduOMw#_t4QdAMNqEdu2IdAIaWZyAw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_prj5AMuYEdyTA_Xoy-01eg"
+ name="guideline_list.assign" guid="_prj5AMuYEdyTA_Xoy-01eg" variabilityType="contributes"
+ categorizedElements="_0VAUsMlgEdmt3adZL5Dmdw _4BJ_YCxSEdqjsdw1QLH_6Q _eyL0wCu-EdqSxKAVa9kmvA _wr24gNcGEdqz_d2XWoVt6Q _2uan8NbyEdqu5o2S60g5LA _qq0GMAXkEduj_7BEUj1JfQ">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4ZcRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_DgjhEMuZEdyTA_Xoy-01eg"
+ name="template_list.assign" guid="_DgjhEMuZEdyTA_Xoy-01eg" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4Z8RdEdyD76CYS6Ta7A"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Template" href="uma://_OOB2AAouEdyhlpBPrduOMw#_m7p-AI5fEdyO5aWob1UGDA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Template" href="uma://_OOB2AAouEdyhlpBPrduOMw#_3Y3XUI5fEdyO5aWob1UGDA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_JhKYoMuZEdyTA_Xoy-01eg"
+ name="practice_list.assign" guid="_JhKYoMuZEdyTA_Xoy-01eg" variabilityType="contributes"
+ categorizedElements="_lmNCoJ-lEdyBk-WQzMU-FQ">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCIHY8RdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_sn0ZUMuZEdyTA_Xoy-01eg"
+ name="roadmap_list.assign" guid="_sn0ZUMuZEdyTA_Xoy-01eg" variabilityType="contributes"
+ categorizedElements="_PJKZkMRfEdyBt8f9agIerg">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4ZsRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_W3uAYM-GEdymYdYa6iWnUQ"
+ name="key_concepts" guid="_W3uAYM-GEdymYdYa6iWnUQ" presentationName="Key Concepts"
+ shapeicon="customcategories/resources/concept_dgm32.gif" nodeicon="customcategories/resources/concept_obj.gif">
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0Wh-sMlgEdmt3adZL5Dmdw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_KudM0NcJEdqz_d2XWoVt6Q"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_zGqO0MDpEduTGJ8i4u8TMw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_2jyfUAhVEduRe8TeoBmuGg"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_jxw58NQxEdyM_J8-fv54DA"
+ name="technical_practice_list" guid="_jxw58NQxEdyM_J8-fv54DA" presentationName="Technical Practices"
+ variabilityType="contributes" categorizedElements="_lmNCoJ-lEdyBk-WQzMU-FQ">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_lBrxENQuEdyM_J8-fv54DA"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_GbYfXLPaEduocbW-TPTq7A"
+ name="CoreContent" guid="_GbYfXLPaEduocbW-TPTq7A">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_LVhzMLPcEduocbW-TPTq7A"
+ name="Use-Case Driven Development" guid="_LVhzMLPcEduocbW-TPTq7A">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_jAZJYNPCEduegN_z1rVgJA"
+ name="Use-Case Modeling" guid="_jAZJYNPCEduegN_z1rVgJA">
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_jAZJYtPCEduegN_z1rVgJA"
+ name="requirements_slot.ucm" guid="_jAZJYtPCEduegN_z1rVgJA" variabilityType="contributes"
+ variabilityBasedOnElement="_cTFV8LPbEduocbW-TPTq7A">
+ <containedArtifacts xmi:id="_BFFaEAo_EdyT57ElgMr6TA" name="use_case_model.ucm"
+ guid="_BFFaEAo_EdyT57ElgMr6TA" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Artifact"
+ href="uma://_OOB2AAouEdyhlpBPrduOMw#_W2SgEDR5EdutE_HNDTJk5Q"/>
+ <containedArtifacts xmi:id="_nDKmwMO-EdyM6MDjpGyC5g" name="use_case.ucm"
+ guid="_nDKmwMO-EdyM6MDjpGyC5g" variabilityType="contributes" variabilityBasedOnElement="_MuaqIAo-EdyT57ElgMr6TA"/>
+ </containedArtifacts>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_0VAUsMlgEdmt3adZL5Dmdw"
+ name="use_case_model" guid="_0VAUsMlgEdmt3adZL5Dmdw" briefDescription="This guideline describes how to develop and evolve the use-case model to capture the functional requirements for the system under development."
+ presentationName="Use-Case Model">
+ <presentation xmi:id="_AGvpcMM3EdmSIPI87WLu3g" href="uma://_AGvpcMM3EdmSIPI87WLu3g#_AGvpcMM3EdmSIPI87WLu3g"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_jivyULseEdyfAY9BXNFkDg"
+ name="use_case.ucm" guid="_jivyULseEdyfAY9BXNFkDg" variabilityType="contributes">
+ <presentation xmi:id="-3kVaHsAKwWzKBx12XV-xTg" href="uma://-3kVaHsAKwWzKBx12XV-xTg#-3kVaHsAKwWzKBx12XV-xTg"/>
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_KudM0NcJEdqz_d2XWoVt6Q"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_-pOLIEbEEdyx8quJU3Grxg"
+ name="detail_use_case_scenarios.ucm" guid="_-pOLIEbEEdyx8quJU3Grxg"
+ orderingGuide="<?xml version="1.0" encoding="ASCII"?>
<org.eclipse.epf.uma.edit.tng.util.model:OrderInfoCollection xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma.edit.tng.util.model="http:///com/ibm/uma/edit/tng/util/model.ecore">
 <orderInfos name="sections" timestamp="1195069025696">
 <gUIDs>_fAWPkJLZEdyk6dG0ehkW5Q</gUIDs>
 <gUIDs>_-pOLIUbEEdyx8quJU3Grxg</gUIDs>
 <gUIDs>_iEvYMJLaEdyk6dG0ehkW5Q</gUIDs>
 <gUIDs>_kojt4JLcEdyk6dG0ehkW5Q</gUIDs>
 </orderInfos>
</org.eclipse.epf.uma.edit.tng.util.model:OrderInfoCollection>
"
+ variabilityType="contributes" variabilityBasedOnElement="_SL7N0LPdEduocbW-TPTq7A">
+ <presentation xmi:id="-locCQOxOUM8zej2tBD6M6Q" href="uma://-locCQOxOUM8zej2tBD6M6Q#-locCQOxOUM8zej2tBD6M6Q"/>
+ <output xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_W2SgEDR5EdutE_HNDTJk5Q"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_txpV0AFmEduDPKiaP0pu-Q"
+ name="identify_and_outline_requirements.ucm" guid="_txpV0AFmEduDPKiaP0pu-Q"
+ orderingGuide="<?xml version="1.0" encoding="ASCII"?>
<org.eclipse.epf.uma.edit.tng.util.model:OrderInfoCollection xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma.edit.tng.util.model="http:///com/ibm/uma/edit/tng/util/model.ecore">
 <orderInfos name="sections" timestamp="1199391793298">
 <gUIDs>_ckG-cCY-EdqNHcQ-rAojXw</gUIDs>
 <gUIDs>_GAr3IOz3Edq2wJOsmRwmhg</gUIDs>
 <gUIDs>_fDbgkCY-EdqNHcQ-rAojXw</gUIDs>
 <gUIDs>_N66nkApAEdyT57ElgMr6TA</gUIDs>
 <gUIDs>_CD_a8JJKEdyk6dG0ehkW5Q</gUIDs>
 <gUIDs>_Ql45gEI6Edyrh7YaMjqrlA</gUIDs>
 <gUIDs>_0WhHsN-eEdqiM_wFaqLjNg</gUIDs>
 </orderInfos>
</org.eclipse.epf.uma.edit.tng.util.model:OrderInfoCollection>
"
+ variabilityType="contributes" variabilityBasedOnElement="_P9cMUPV_EdmdHa9MmVPgqQ">
+ <presentation xmi:id="-Yt8TXGkE1rwydXR34apsrg" href="uma://-Yt8TXGkE1rwydXR34apsrg#-Yt8TXGkE1rwydXR34apsrg"/>
+ <output xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_W2SgEDR5EdutE_HNDTJk5Q"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_X-RNUMuXEdyTA_Xoy-01eg"
+ name="Release Info" guid="_X-RNUMuXEdyTA_Xoy-01eg">
+ <contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="_Z87SYMuXEdyTA_Xoy-01eg"
+ name="release_info_uc_driven_dev" guid="_Z87SYMuXEdyTA_Xoy-01eg" presentationName="Use-Case Driven Development Practice">
+ <presentation xmi:id="-pnWJpKCphl8ewGRYM4tDOQ" href="uma://-pnWJpKCphl8ewGRYM4tDOQ#-pnWJpKCphl8ewGRYM4tDOQ"/>
+ </contentElements>
+ </childPackages>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_cTFV8LPbEduocbW-TPTq7A"
+ name="requirements_slot.ucdd" guid="_cTFV8LPbEduocbW-TPTq7A" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_gX_0gNjhEdyQUcK-3ySmyA"/>
+ <containedArtifacts xmi:id="_MuaqIAo-EdyT57ElgMr6TA" name="use_case.ucdd"
+ guid="_MuaqIAo-EdyT57ElgMr6TA" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0VGbUMlgEdmt3adZL5Dmdw"/>
+ </containedArtifacts>
+ <containedArtifacts xmi:id="_9ZeScEL-EdyP_Jn83ylwUQ" name="system_wide_requirements.ucdd"
+ guid="_9ZeScEL-EdyP_Jn83ylwUQ" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_BVh9cL-CEdqb7N6KIeDL8Q"/>
+ </containedArtifacts>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_4z8Z0EbEEdyx8quJU3Grxg"
+ name="detail_system_wide_requirements" guid="_4z8Z0EbEEdyx8quJU3Grxg"
+ briefDescription="This task details one or more requirement that does not apply to a specific use case."
+ orderingGuide="<?xml version="1.0" encoding="ASCII"?> <com.ibm.uma.edit.tng.util.model:OrderInfoCollection xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:com.ibm.uma.edit.tng.util.model="http:///com/ibm/uma/edit/tng/util/model.ecore"> <orderInfos name="sections" timestamp="1113334493908"> <gUIDs>_yqm4kKuJEdmhFZtkg1nakg</gUIDs> <gUIDs>_zg2kEKuJEdmhFZtkg1nakg</gUIDs> <gUIDs>_1GGDkKuJEdmhFZtkg1nakg</gUIDs> <gUIDs>_35vP4KuJEdmhFZtkg1nakg</gUIDs> <gUIDs>_5mtIAKuJEdmhFZtkg1nakg</gUIDs> <gUIDs>_7g3HkKuJEdmhFZtkg1nakg</gUIDs> </orderInfos> </com.ibm.uma.edit.tng.util.model:OrderInfoCollection> "
+ presentationName="Detail System-Wide Requirements">
+ <presentation xmi:id="-9sNgONA1WJCxf12B40uDgw" href="uma://-9sNgONA1WJCxf12B40uDgw#-9sNgONA1WJCxf12B40uDgw"/>
+ <guidelines href="#_wr24gNcGEdqz_d2XWoVt6Q"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_E-dPIL-GEdqb7N6KIeDL8Q"/>
+ <mandatoryInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_BVh9cL-CEdqb7N6KIeDL8Q"/>
+ <output xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_BVh9cL-CEdqb7N6KIeDL8Q"/>
+ <output xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_Wn7HcNcEEdqz_d2XWoVt6Q"/>
+ <optionalInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0VGbUMlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_SL7N0LPdEduocbW-TPTq7A"
+ name="detail_use_case_scenarios" guid="_SL7N0LPdEduocbW-TPTq7A" briefDescription="This task describes how to detail a use-case scenarios for the system."
+ presentationName="Detail Use-Case Scenarios">
+ <presentation xmi:id="-oFAa8Uu6tr_GkE_E0iycdQ" href="uma://-oFAa8Uu6tr_GkE_E0iycdQ#-oFAa8Uu6tr_GkE_E0iycdQ"/>
+ <guidelines href="#_4BJ_YCxSEdqjsdw1QLH_6Q"/>
+ <guidelines href="#_qq0GMAXkEduj_7BEUj1JfQ"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_E-dPIL-GEdqb7N6KIeDL8Q"/>
+ <mandatoryInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0VGbUMlgEdmt3adZL5Dmdw"/>
+ <output xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0VGbUMlgEdmt3adZL5Dmdw"/>
+ <output xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_Wn7HcNcEEdqz_d2XWoVt6Q"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Task" xmi:id="_P9cMUPV_EdmdHa9MmVPgqQ"
+ name="identify_and_outline_requirements" guid="_P9cMUPV_EdmdHa9MmVPgqQ"
+ briefDescription="This task describes how to identify and outline the requirements for the system so that the scope of work may be determined."
+ presentationName="Identify and Outline Requirements">
+ <presentation xmi:id="_P9iS8PV_EdmdHa9MmVPgqQ" href="uma://_P9iS8PV_EdmdHa9MmVPgqQ#_P9iS8PV_EdmdHa9MmVPgqQ"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_0Wh-sMlgEdmt3adZL5Dmdw"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_VXZ5wO0IEdqHTdbLTmC5IQ"/>
+ <guidelines href="#_eyL0wCu-EdqSxKAVa9kmvA"/>
+ <guidelines href="#_wr24gNcGEdqz_d2XWoVt6Q"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_OnoNQNSAEdmLhZ9H5Plxyw"/>
+ <guidelines href="uma://_OOB2AAouEdyhlpBPrduOMw#_E-dPIL-GEdqb7N6KIeDL8Q"/>
+ <output xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_BVh9cL-CEdqb7N6KIeDL8Q"/>
+ <output xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0VGbUMlgEdmt3adZL5Dmdw"/>
+ <output xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_Wn7HcNcEEdqz_d2XWoVt6Q"/>
+ <optionalInput xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_i3vkoLS-EduDY8LNbMCDBA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_FlOgUEj8Edyi3_jfs__bIQ"
+ name="requirements.ucdd" guid="_FlOgUEj8Edyi3_jfs__bIQ" variabilityType="contributes">
+ <presentation xmi:id="-4E4u3crgCavkHJqTClP8cA" href="uma://-4E4u3crgCavkHJqTClP8cA#-4E4u3crgCavkHJqTClP8cA"/>
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0Wh-sMlgEdmt3adZL5Dmdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_4BJ_YCxSEdqjsdw1QLH_6Q"
+ name="detail_ucs_and_scenarios" guid="_4BJ_YCxSEdqjsdw1QLH_6Q" briefDescription="This guideline provides help on detailing use cases and scenarios."
+ presentationName="Detail Use Cases and Scenarios" guidelines="_qq0GMAXkEduj_7BEUj1JfQ">
+ <presentation xmi:id="-78ko4CuOJERKJF9ZvwMUBQ" href="uma://-78ko4CuOJERKJF9ZvwMUBQ#-78ko4CuOJERKJF9ZvwMUBQ"/>
+ <conceptsAndPapers href="uma://_OOB2AAouEdyhlpBPrduOMw#_KudM0NcJEdqz_d2XWoVt6Q"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_eyL0wCu-EdqSxKAVa9kmvA"
+ name="identify_and_outline_actors_and_ucs" guid="_eyL0wCu-EdqSxKAVa9kmvA"
+ briefDescription="This guideline describes how to find and outline actors and use cases."
+ presentationName="Identify and Outline Actors and Use Cases">
+ <presentation xmi:id="-Rcm_MlViENAvFFyIe9V3dQ" href="uma://-Rcm_MlViENAvFFyIe9V3dQ#-Rcm_MlViENAvFFyIe9V3dQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_wr24gNcGEdqz_d2XWoVt6Q"
+ name="system_wide_requirements" guid="_wr24gNcGEdqz_d2XWoVt6Q" briefDescription="This guideline explains how to develop and use the system-wide requirements specification."
+ presentationName="Developing System-Wide Requirements Specification">
+ <presentation xmi:id="-BdYFG4-dbPBGFzF9z6KGPA" href="uma://-BdYFG4-dbPBGFzF9z6KGPA#-BdYFG4-dbPBGFzF9z6KGPA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_qq0GMAXkEduj_7BEUj1JfQ"
+ name="use_case_formats" guid="_qq0GMAXkEduj_7BEUj1JfQ" briefDescription="This guideline describes different use case formats and associated levels of detail that you may want to use, depending upon the nature of the project."
+ presentationName="Use Case Formats">
+ <presentation xmi:id="-pQrBSyxJHLLodLbS4R_Zdw" href="uma://-pQrBSyxJHLLodLbS4R_Zdw#-pQrBSyxJHLLodLbS4R_Zdw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_U_olUEvDEdunZcj9T5hrMQ"
+ name="system_wide_requirement" guid="_U_olUEvDEdunZcj9T5hrMQ" presentationName="system-wide requirements">
+ <presentation xmi:id="-ketzwgDgY82DMyfuHqu3Cw" href="uma://-ketzwgDgY82DMyfuHqu3Cw#-ketzwgDgY82DMyfuHqu3Cw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:TermDefinition" xmi:id="_oXmYMEvGEdunZcj9T5hrMQ"
+ name="use_case_scenario" guid="_oXmYMEvGEdunZcj9T5hrMQ" presentationName="use-case scenario">
+ <presentation xmi:id="-t3jNM5ZWkYtzB8A4Chz2Vw" href="uma://-t3jNM5ZWkYtzB8A4Chz2Vw#-t3jNM5ZWkYtzB8A4Chz2Vw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_ryuL0LsbEdyfAY9BXNFkDg"
+ name="use_case.ucdd" guid="_ryuL0LsbEdyfAY9BXNFkDg" variabilityType="contributes">
+ <presentation xmi:id="-wv4JAmTQ0R_KjP76LgDITg" href="uma://-wv4JAmTQ0R_KjP76LgDITg#-wv4JAmTQ0R_KjP76LgDITg"/>
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Concept" href="uma://_OOB2AAouEdyhlpBPrduOMw#_KudM0NcJEdqz_d2XWoVt6Q"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Roadmap" xmi:id="_PJKZkMRfEdyBt8f9agIerg"
+ name="how_to_adopt" guid="_PJKZkMRfEdyBt8f9agIerg" briefDescription="This roadmap describes how to adopt the Use-Case Driven Development Practice."
+ presentationName="How to Adopt this Practice">
+ <presentation xmi:id="-3WNAtOgFvwsJtFvhDugsVA" href="uma://-3WNAtOgFvwsJtFvhDugsVA#-3WNAtOgFvwsJtFvhDugsVA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_2uan8NbyEdqu5o2S60g5LA"
+ name="uc_realizations" guid="_2uan8NbyEdqu5o2S60g5LA" briefDescription="A use-case realization represents how a use case will be implemented in terms of collaborating objects. This guideline describes its purpose and UML notation."
+ presentationName="Use-Cases Realizations">
+ <presentation xmi:id="-CFYVionNDLkMw6SG6runQA" href="uma://-CFYVionNDLkMw6SG6runQA#-CFYVionNDLkMw6SG6runQA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Guideline" xmi:id="_sVnoIMtvEdyTA_Xoy-01eg"
+ name="design_guidance_slot.ucdd" guid="_sVnoIMtvEdyTA_Xoy-01eg" variabilityType="contributes"
+ guidelines="_2uan8NbyEdqu5o2S60g5LA">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Guideline" href="uma://_-bv0ELXuEduGP_98XMd0fg#_z_wMgJI7Edyk6dG0ehkW5Q"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="_i--RUNXBEdylRpA9TBY1SQ"
+ name="practice_enablement" guid="_i--RUNXBEdylRpA9TBY1SQ" briefDescription="This supporting material suggests approaches to get you enabled on the Use-Case Driven Development Practice."
+ presentationName="Enablement">
+ <presentation xmi:id="-RIEhRIYgm6Ja2Jnth9IuhA" href="uma://-RIEhRIYgm6Ja2Jnth9IuhA#-RIEhRIYgm6Ja2Jnth9IuhA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Artifact" xmi:id="_TL5KINjiEdyQUcK-3ySmyA"
+ name="technical_specificaton_slot.ucdd" guid="_TL5KINjiEdyQUcK-3ySmyA"
+ variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_i3vkoLS-EduDY8LNbMCDBA"/>
+ <containedArtifacts xmi:id="_Nk7zwNaUEdyjTeYRQ0TIqg" name="glossary.ucdd"
+ guid="_Nk7zwNaUEdyjTeYRQ0TIqg" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_Wn7HcNcEEdqz_d2XWoVt6Q"/>
+ </containedArtifacts>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_GbYfXbPaEduocbW-TPTq7A"
+ name="CapabilityPatterns" guid="_GbYfXbPaEduocbW-TPTq7A"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_GbYfXrPaEduocbW-TPTq7A"
+ name="DeliveryProcesses" guid="_GbYfXrPaEduocbW-TPTq7A"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_GbYfX7PaEduocbW-TPTq7A"
+ name="ProcessContributions" guid="_GbYfX7PaEduocbW-TPTq7A"/>
+ <bases href="uma://_-bv0ELXuEduGP_98XMd0fg#_-bv0ELXuEduGP_98XMd0fg"/>
+ <bases href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2AAouEdyhlpBPrduOMw"/>
+ <bases href="uma://_iRbPEEKmEdyrauqpmnA8jQ#_iRbPEEKmEdyrauqpmnA8jQ"/>
+ <bases href="uma://_iVydgENdEdy245g62lfWcA#_iVydgENdEdy245g62lfWcA"/>
+ <bases href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-gEMXEdyP_Jn83ylwUQ"/>
+ <bases href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno4EKmEdyrauqpmnA8jQ"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/tasks/detail_system_wide_requirements.xmi b/praclib/temp/practice.tech.use_case_driven_dev.base/tasks/detail_system_wide_requirements.xmi
new file mode 100644
index 0000000..fe8d7e6
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/tasks/detail_system_wide_requirements.xmi
@@ -0,0 +1,32 @@
+<?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.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="-9sNgONA1WJCxf12B40uDgw"
+ name="detail_system_wide_requirements,_4z8Z0EbEEdyx8quJU3Grxg" guid="-9sNgONA1WJCxf12B40uDgw"
+ changeDate="2007-11-14T10:42:54.904-0800" version="1.0.0">
+ <keyConsiderations>To avoid unnecessary rework, only those requirements that are scheduled for implementation in the near term (in the next
+iteration or two) should be detailed.</keyConsiderations>
+ <sections xmi:id="_4z8Z1EbEEdyx8quJU3Grxg" name="Detail system-wide requirements "
+ guid="_4z8Z1EbEEdyx8quJU3Grxg">
+ <sectionDescription><p>
+ Some&nbsp;system-wide requirements&nbsp;may need to be clarified or described in more detail.&nbsp;New
+ requirements&nbsp;may&nbsp;be discovered&nbsp;while the use cases and scenarios are detailed, and new requirements may
+ have been submitted as change requests.&nbsp;Collaborate with stakeholders to capture, refine and validate those
+ requirements that will have an impact on near term, planned&nbsp;work or are deemed architecturally significant.&nbsp;
+</p><br /></sectionDescription>
+ </sections>
+ <sections xmi:id="_4z8Z0UbEEdyx8quJU3Grxg" name="Detail glossary terms" guid="_4z8Z0UbEEdyx8quJU3Grxg">
+ <sectionDescription>Review the system-wide requirements and collaborate with stakeholders to ensure that you define newly discovered domain
+terms, or ambiguous terms properly in the glossary. If your understanding of the domain has improved, refine existing
+glossary terms.</sectionDescription>
+ </sections>
+ <sections xmi:id="_4z8Z0kbEEdyx8quJU3Grxg" name="Achieve concurrence" guid="_4z8Z0kbEEdyx8quJU3Grxg">
+ <sectionDescription><p>
+ Review the&nbsp;detailed system-wide requirements with relevant stakeholders and the development team to ensure
+ consistency with the&nbsp;agreed vision.&nbsp;Assess quality and identify any required changes.
+</p></sectionDescription>
+ </sections>
+ <purpose>The purpose of this task is to describe one or more system-wide requirements in sufficient detail to validate understanding
+of the requirements, to ensure concurrence with stakeholder expectations, and to permit software development to begin.</purpose>
+</org.eclipse.epf.uma:TaskDescription>
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/tasks/detail_use_case_scenarios.ucm.xmi b/praclib/temp/practice.tech.use_case_driven_dev.base/tasks/detail_use_case_scenarios.ucm.xmi
new file mode 100644
index 0000000..d6b9234
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/tasks/detail_use_case_scenarios.ucm.xmi
@@ -0,0 +1,24 @@
+<?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.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="-locCQOxOUM8zej2tBD6M6Q"
+ name="detail_use_case_scenarios.ucm,_-pOLIEbEEdyx8quJU3Grxg" guid="-locCQOxOUM8zej2tBD6M6Q"
+ version="1.0.0">
+ <sections xmi:id="_-pOLIUbEEdyx8quJU3Grxg" name="Update Use-Case Model" guid="_-pOLIUbEEdyx8quJU3Grxg">
+ <sectionDescription><p>
+ Based on your work detailing use cases and scenarios, update the <a class="elementLink"
+ href="./../../core.tech.common.base/workproducts/use_case_model_85965D1B.html" guid="_W2SgEDR5EdutE_HNDTJk5Q">Use-Case
+ Model</a>.&nbsp;Add, remove or update&nbsp;<a class="elementLinkWithUserText"
+ href="./../../core.tech.common.base/guidances/concepts/actor_411726C.html" guid="_zGqO0MDpEduTGJ8i4u8TMw">Actors</a>
+ and <a class="elementLink" href="./../../core.tech.common.base/workproducts/use_case_22BE66E2.html"
+ guid="_0VGbUMlgEdmt3adZL5Dmdw">Use Case</a>s as required.&nbsp;<br />
+ For more information on creating and structuring your use case model see <a class="elementLinkWithType"
+ href="./../../practice.tech.use_case_driven_dev.base/guidances/guidelines/use_case_model_4C64E97D.html"
+ guid="_0VAUsMlgEdmt3adZL5Dmdw">Guideline: *Use-Case Model</a>.&nbsp;For assistance in assessing the quality of your
+ use-case model see <a class="elementLinkWithType"
+ href="./../../core.tech.common.base/guidances/checklists/use_case_model_27A2D1CF.html"
+ guid="_0U6OEMlgEdmt3adZL5Dmdw">Checklist: **Use-Case Model</a>.
+</p></sectionDescription>
+ </sections>
+</org.eclipse.epf.uma:TaskDescription>
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/tasks/detail_use_case_scenarios.xmi b/praclib/temp/practice.tech.use_case_driven_dev.base/tasks/detail_use_case_scenarios.xmi
new file mode 100644
index 0000000..f95126f
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/tasks/detail_use_case_scenarios.xmi
@@ -0,0 +1,41 @@
+<?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.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="-oFAa8Uu6tr_GkE_E0iycdQ"
+ name="detail_use_case_scenarios,_SL7N0LPdEduocbW-TPTq7A" guid="-oFAa8Uu6tr_GkE_E0iycdQ"
+ changeDate="2007-12-18T14:40:22.003-0800" changeDescription="Review comments:||1. Step 2 was a copy of step 1.|2. Step 1 - excessive linking - remove 2nd paragraph|"
+ version="7.1.0">
+ <keyConsiderations><p>
+ To avoid unnecessary rework, only those use-case scenarios that are scheduled for implementation in the near term (in
+ the next iteration or two) should be detailed.&nbsp;
+</p>
+<p>
+ Not all use-case scenarios require detailing.
+</p></keyConsiderations>
+ <sections xmi:id="_fAWPkJLZEdyk6dG0ehkW5Q" name="Detail use cases and scenarios"
+ guid="_fAWPkJLZEdyk6dG0ehkW5Q">
+ <sectionDescription><p>
+ Some&nbsp;use cases and scenarios may need to be described in more detail to validate the understanding of the
+ requirements and to permit software development to begin. This does not imply that all&nbsp;use cases and scenarios
+ will be detailed prior to commencing implementation on them. The level of detail captured will vary depending upon the
+ needs of the project and the complexity of the use case.&nbsp;Capture the use case and scenarios details in the use
+ case specification.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_iEvYMJLaEdyk6dG0ehkW5Q" name="Detail glossary terms" guid="_iEvYMJLaEdyk6dG0ehkW5Q">
+ <sectionDescription><p>
+ Review the flow of the use case or scenario. If information is exchanged, be specific about what is passed back and
+ forth. Collaborate with stakeholders to ensure that you define newly discovered domain terms, or ambiguous terms
+ properly in the&nbsp;glossary. If your understanding of the domain has improved, refine existing glossary terms.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_kojt4JLcEdyk6dG0ehkW5Q" name="Achieve concurrence" guid="_kojt4JLcEdyk6dG0ehkW5Q">
+ <sectionDescription><p>
+ Review the&nbsp;detailed use case and scenarios with relevant stakeholders and the development team to ensure
+ consistency with the agreed vision.&nbsp;Assess quality and identify any required changes.
+</p></sectionDescription>
+ </sections>
+ <purpose>The purpose of this task is to describe&nbsp;use-case scenarios in sufficient detail to validate understanding of the
+requirements, to ensure concurrence with stakeholder expectations, and to permit software development to begin.</purpose>
+</org.eclipse.epf.uma:TaskDescription>
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/tasks/identify_and_outline_requirements.ucm.xmi b/praclib/temp/practice.tech.use_case_driven_dev.base/tasks/identify_and_outline_requirements.ucm.xmi
new file mode 100644
index 0000000..227f54e
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/tasks/identify_and_outline_requirements.ucm.xmi
@@ -0,0 +1,27 @@
+<?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.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="-Yt8TXGkE1rwydXR34apsrg"
+ name="identify_and_outline_requirements.ucm,_txpV0AFmEduDPKiaP0pu-Q" guid="-Yt8TXGkE1rwydXR34apsrg"
+ version="1.0.0">
+ <sections xmi:id="_N66nkApAEdyT57ElgMr6TA" name="Identify and capture Use Cases and Actors in a Use-Case Model"
+ guid="_N66nkApAEdyT57ElgMr6TA">
+ <sectionDescription><p>
+ Find and define the line that divides the solution and the real world that surrounds the solution. Collaborate with the
+ project manager&nbsp;and architect, since decisions concerning system boundaries will have a major impact on cost,
+ schedule and system architecture.
+</p>
+<p>
+ Collaborate&nbsp;with stakeholders to identify interfaces, as well as input and output information exchanged with
+ users, machines, or systems. Identify and capture&nbsp;the <a class="elementLink"
+ href="./../../core.tech.common.base/guidances/concepts/actor_411726C.html" guid="_zGqO0MDpEduTGJ8i4u8TMw">Actor</a>s
+ and <a class="elementLink" href="./../../core.tech.common.base/workproducts/use_case_22BE66E2.html"
+ guid="_0VGbUMlgEdmt3adZL5Dmdw">Use Case</a>s in the <a class="elementLink"
+ href="./../../core.tech.common.base/workproducts/use_case_model_85965D1B.html"
+ guid="_W2SgEDR5EdutE_HNDTJk5Q">Use-Case Model</a>. See <a class="elementLinkWithType"
+ href="./../../practice.tech.use_case_driven_dev.base/guidances/guidelines/find_and_outline_actors_and_ucs_BB5516A9.html"
+ guid="_eyL0wCu-EdqSxKAVa9kmvA">Guideline: *Find and Outline Actors and Use Cases</a>&nbsp;for more information.
+</p></sectionDescription>
+ </sections>
+</org.eclipse.epf.uma:TaskDescription>
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/tasks/identify_and_outline_requirements.xmi b/praclib/temp/practice.tech.use_case_driven_dev.base/tasks/identify_and_outline_requirements.xmi
new file mode 100644
index 0000000..8764d84
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/tasks/identify_and_outline_requirements.xmi
@@ -0,0 +1,76 @@
+<?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.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="_P9iS8PV_EdmdHa9MmVPgqQ"
+ name="identify_and_outline_requirements,_P9cMUPV_EdmdHa9MmVPgqQ" guid="_P9iS8PV_EdmdHa9MmVPgqQ"
+ changeDate="2008-02-11T14:20:35.062-0800" changeDescription="We need to solve the relationship to work items list"
+ version="1.0.0">
+ <sections xmi:id="_ckG-cCY-EdqNHcQ-rAojXw" name="Gather information" guid="_ckG-cCY-EdqNHcQ-rAojXw">
+ <sectionDescription><p>
+ Use various techniques to make gathering requirements easier. Face-to-face meetings with stakeholders is the most
+ effective way to understand stakeholder needs and to gather and validate requirements, but you must prepare in order
+ for these meetings to run efficiently.
+</p>
+<p>
+ Be prepared by gathering and reviewing information related to the problem domain, problem statement, business
+ environment and key stakeholders. Most of this information should be available in the vision.&nbsp;Also review the
+ exisiting requirements repository for stakeholder requests.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_GAr3IOz3Edq2wJOsmRwmhg" name="Identify and capture domain terms"
+ guid="_GAr3IOz3Edq2wJOsmRwmhg">
+ <sectionDescription>If there are ambiguous or domain-specific terms that need to be clearly defined, make sure you work closely with
+stakeholders&nbsp;to capture these&nbsp;terms in the glossary and that you use these terms consistently.</sectionDescription>
+ </sections>
+ <sections xmi:id="_fDbgkCY-EdqNHcQ-rAojXw" name="Identify the types of requirements relevant to your system "
+ guid="_fDbgkCY-EdqNHcQ-rAojXw">
+ <sectionDescription><p>
+ Requirements can be broadly classified as either functional or non-functional requirements. The former specify what the
+ system must do. The latter specify constraints on the solution such as usability, reliability, performance,
+ supportability, interfaces with legacy systems, etc. Depending upon the domain there may be regulatory requirements
+ that apply.
+</p>
+<p>
+ Collaborate with stakeholders to identify the types of requirements relevant to your system. This will help you assess
+ the completeness of your requirement set.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_CD_a8JJKEdyk6dG0ehkW5Q" name="Identify and capture use cases and scenarios"
+ guid="_CD_a8JJKEdyk6dG0ehkW5Q">
+ <sectionDescription><p>
+ Collaborate with stakeholders to identify and capture&nbsp;the use cases and scenarios relevant&nbsp;to your system.
+ Capture references to these requirements in the <a class="elementLink"
+ href="./../../core.mgmt.slot.base/workproducts/work_items_slot_F12BAC46.html" guid="_1QZI8EfUEdyiPI8btkmvmw">[Work
+ Items]</a>, so that you can prioritize the work.
+</p>
+<p>
+ See&nbsp;<a class="elementLink"
+ href="./../../practice.tech.use_case_driven_dev.base/guidances/guidelines/identify_and_outline_actors_and_ucs_BB5516A9.html"
+ guid="_eyL0wCu-EdqSxKAVa9kmvA">Identify and Outline Actors and Use Cases</a> for more information.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_Ql45gEI6Edyrh7YaMjqrlA" name="Identify and capture system-wide requirements "
+ guid="_Ql45gEI6Edyrh7YaMjqrlA">
+ <sectionDescription><p>
+ Collaborate with stakeholders to identify and capture&nbsp;the other types of requirements relevant to your system.
+ Capture references to the requirements&nbsp;in the&nbsp;<a class="elementLink"
+ href="./../../core.mgmt.slot.base/workproducts/work_items_slot_F12BAC46.html" guid="_1QZI8EfUEdyiPI8btkmvmw">[Work
+ Items]</a>&nbsp;so that you can prioritize the work.
+</p>
+<p>
+ See <a class="elementLink"
+ href="./../../practice.tech.use_case_driven_dev.base/guidances/guidelines/system_wide_requirements_8ED0BB6B.html"
+ guid="_wr24gNcGEdqz_d2XWoVt6Q">Developing System-Wide Requirements Specification</a> for more information.
+</p></sectionDescription>
+ </sections>
+ <sections xmi:id="_0WhHsN-eEdqiM_wFaqLjNg" name="Achieve concurrence" guid="_0WhHsN-eEdqiM_wFaqLjNg">
+ <sectionDescription>Conduct a review&nbsp;of the&nbsp;requirements with relevant stakeholders and the development team to ensure consistency
+with the agreed vision, assess quality, and identify any required changes.</sectionDescription>
+ </sections>
+ <purpose>The purpose of this task is to identify and capture functional and non-functional requirements for the system. These
+requirements form the basis of communication and agreement between the stakeholders and the development team on what the
+system must do to satisfy stakeholder needs. The goal is to understand the requirements at a high-level so that the initial
+scope of work can be determined.&nbsp;Further analysis will be performed to detail these requirements prior to
+implementation.</purpose>
+</org.eclipse.epf.uma:TaskDescription>
diff --git a/praclib/temp/practice.tech.use_case_driven_dev.base/workproducts/resources/supporting_reguirements2.gif b/praclib/temp/practice.tech.use_case_driven_dev.base/workproducts/resources/supporting_reguirements2.gif
new file mode 100644
index 0000000..cf4c368
--- /dev/null
+++ b/praclib/temp/practice.tech.use_case_driven_dev.base/workproducts/resources/supporting_reguirements2.gif
Binary files differ
diff --git a/praclib/temp/process.openup.base/.project b/praclib/temp/process.openup.base/.project
new file mode 100644
index 0000000..6cbab2d
--- /dev/null
+++ b/praclib/temp/process.openup.base/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>process.openup.base</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/process.openup.base/capabilitypatterns/agree_technical_approach/content.xmi b/praclib/temp/process.openup.base/capabilitypatterns/agree_technical_approach/content.xmi
new file mode 100644
index 0000000..df9fa95
--- /dev/null
+++ b/praclib/temp/process.openup.base/capabilitypatterns/agree_technical_approach/content.xmi
@@ -0,0 +1,46 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:ProcessDescription 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="-BZ8afnvoVBJs82vzcOBaCw"
+ name="agree_technical_approach,_4ouDUdOEEdyqlogshP8l4g" guid="-BZ8afnvoVBJs82vzcOBaCw"
+ version="7.2.0">
+ <mainDescription><p>
+ The goal of this activity is to define a technical approach to the system that supports the project requirements,
+ within the constraints placed on the system and the development team. The architect should do the following:
+</p>
+<ul>
+ <li>
+ Work with the team to create an initial sketch of the technical approach to the proposed system
+ </li>
+ <li>
+ Ensure that the technical decisions are adequately captured and communicated
+ </li>
+ <li>
+ Ensure that the team has enough information to understand the approach that your are taking
+ </li>
+</ul>
+<p>
+ The work done here does not seek to produce a detailed and comprehensive technical specification for the system.
+ Rather, the approach should be to decide the overall technical approach at a high level.
+</p>
+<p>
+ You should focus on proving the architecture with working software. If the solution is similar to a previously produced
+ solution (or is a well-known solution domain), then it will probably be good enough to reference that example as
+ evidence of the feasibility of the approach. In some cases, it may be necessary to develop one or more prototypes to
+ validate some of the decisions or clarify some of the requirements.
+</p>
+<p>
+ The conclusion of this work should produce just enough information to communicate the architecture to the team, and to
+ demonstrate its viability to the customer. This allows the project to move forward, enabling you to refine and baseline
+ the architecture.
+</p></mainDescription>
+ <howtoStaff><p>
+ This activity is best carried out collaboratively by the team, with the architect acting as a focal point for
+ coordinating and facilitating the decisions.
+</p></howtoStaff>
+ <usageNotes><p>
+ The major effort occurs early in the project; thereafter, you should assess the system regularly to ensure that the
+ design is still on track with the architecture.
+</p></usageNotes>
+</org.eclipse.epf.uma:ProcessDescription>
diff --git a/praclib/temp/process.openup.base/capabilitypatterns/agree_technical_approach/model.xmi b/praclib/temp/process.openup.base/capabilitypatterns/agree_technical_approach/model.xmi
new file mode 100644
index 0000000..4f9e42f
--- /dev/null
+++ b/praclib/temp/process.openup.base/capabilitypatterns/agree_technical_approach/model.xmi
@@ -0,0 +1,73 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_4q9fAdOEEdyqlogshP8l4g"
+ guid="_4q9fAdOEEdyqlogshP8l4g">
+ <resourceDescriptors xmi:id="_4q9fAtOEEdyqlogshP8l4g" id="-BZ8afnvoVBJs82vzcOBaCw"
+ uri="content.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:ProcessComponent xmi:id="_4ouDUNOEEdyqlogshP8l4g" name="agree_technical_approach"
+ guid="_4ouDUNOEEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_BWWIgdOKEdyqlogshP8l4g"
+ name="architect" guid="_BWWIgdOKEdyqlogshP8l4g" presentationName="Architect"
+ isPlanned="false" superActivities="_4ouDUdOEEdyqlogshP8l4g" responsibleFor="_BWf5gtOKEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0X9iEMlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_BWf5gtOKEdyqlogshP8l4g"
+ name="architecture_notebook" guid="_BWf5gtOKEdyqlogshP8l4g" presentationName="Architecture Notebook"
+ isPlanned="false" superActivities="_4ouDUdOEEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_4gaS4LPREduocbW-TPTq7A#_0XAf0MlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_n75CcdfeEdy8T_PKWvNDBA"
+ name="analyst" guid="_n75CcdfeEdy8T_PKWvNDBA" presentationName="Analyst" isPlanned="false"
+ superActivities="_4ouDUdOEEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0VxJsMlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_n75CctfeEdy8T_PKWvNDBA"
+ name="developer" guid="_n75CctfeEdy8T_PKWvNDBA" presentationName="Developer"
+ isPlanned="false" superActivities="_4ouDUdOEEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_n75Cc9feEdy8T_PKWvNDBA"
+ name="project_manager" guid="_n75Cc9feEdy8T_PKWvNDBA" presentationName="Project Manager"
+ isPlanned="false" superActivities="_4ouDUdOEEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0a0o0MlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_n75CdNfeEdy8T_PKWvNDBA"
+ name="stakeholder" guid="_n75CdNfeEdy8T_PKWvNDBA" presentationName="Stakeholder"
+ isPlanned="false" superActivities="_4ouDUdOEEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_dTa6gMAYEdqX-s4mWhkyqQ"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_n75CddfeEdy8T_PKWvNDBA"
+ name="technical_specification_slot" guid="_n75CddfeEdy8T_PKWvNDBA" presentationName="[Technical Specification]"
+ isPlanned="false" superActivities="_4ouDUdOEEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_i3vkoLS-EduDY8LNbMCDBA"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_sjccUN_1EdyOsumnGvWsEg"
+ name="envision_the_arch" guid="_sjccUN_1EdyOsumnGvWsEg" presentationName="Envision the Architecture"
+ superActivities="_4ouDUdOEEdyqlogshP8l4g" additionallyPerformedBy="_n75CcdfeEdy8T_PKWvNDBA _n75CctfeEdy8T_PKWvNDBA _n75Cc9feEdy8T_PKWvNDBA _n75CdNfeEdy8T_PKWvNDBA"
+ mandatoryInput="_n75CddfeEdy8T_PKWvNDBA" output="_BWf5gtOKEdyqlogshP8l4g"
+ performedPrimarilyBy="_BWWIgdOKEdyqlogshP8l4g">
+ <Task href="uma://_4gaS4LPREduocbW-TPTq7A#_0f-1oMlgEdmt3adZL5Dmdw"/>
+ <selectedSteps href="uma://_qDRSULBKEdm7Eph_l9Cn9w#_3nMQQA3rEduibvKwrGxWxA"/>
+ <selectedSteps href="uma://_qDRSULBKEdm7Eph_l9Cn9w#_I32E4MP2EdmWKcx6ixEiwg"/>
+ <selectedSteps href="uma://_qDRSULBKEdm7Eph_l9Cn9w#_f0y2kM25Edym_ZFqrJcXUg"/>
+ <selectedSteps href="uma://_qDRSULBKEdm7Eph_l9Cn9w#_9o6Z4CSCEdqDjNgZyGMf5w"/>
+ <selectedSteps href="uma://_qDRSULBKEdm7Eph_l9Cn9w#_B899cMP2EdmWKcx6ixEiwg"/>
+ <selectedSteps href="uma://_qDRSULBKEdm7Eph_l9Cn9w#_FVrlsMP2EdmWKcx6ixEiwg"/>
+ <selectedSteps href="uma://_qDRSULBKEdm7Eph_l9Cn9w#_tmvWwE5cEducxZ_XZXh-vw"/>
+ <selectedSteps href="uma://_qDRSULBKEdm7Eph_l9Cn9w#_KBAsYMP2EdmWKcx6ixEiwg"/>
+ <selectedSteps href="uma://_qDRSULBKEdm7Eph_l9Cn9w#_RKSLsNp3EdyItewP9R0w7Q"/>
+ </processElements>
+ <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_4ouDUdOEEdyqlogshP8l4g"
+ name="agree_technical_approach" guid="_4ouDUdOEEdyqlogshP8l4g" briefDescription="Reach agreement on a viable technical approach to developing the solution."
+ presentationName="Agree on Technical Approach" breakdownElements="_BWWIgdOKEdyqlogshP8l4g _BWf5gtOKEdyqlogshP8l4g _n75CcdfeEdy8T_PKWvNDBA _n75CctfeEdy8T_PKWvNDBA _n75Cc9feEdy8T_PKWvNDBA _n75CdNfeEdy8T_PKWvNDBA _n75CddfeEdy8T_PKWvNDBA _sjccUN_1EdyOsumnGvWsEg">
+ <presentation xmi:id="-BZ8afnvoVBJs82vzcOBaCw" href="uma://-BZ8afnvoVBJs82vzcOBaCw#-BZ8afnvoVBJs82vzcOBaCw"/>
+ <defaultContext href="uma://_5pP3a9_fEdyOsumnGvWsEg#_gExDwNQxEdyk9oc_L5Vk0g"/>
+ <validContext href="uma://_5pP3a9_fEdyOsumnGvWsEg#_gExDwNQxEdyk9oc_L5Vk0g"/>
+ </process>
+ </org.eclipse.epf.uma:ProcessComponent>
+</xmi:XMI>
diff --git a/praclib/temp/process.openup.base/capabilitypatterns/construction_phase_iteration/content.xmi b/praclib/temp/process.openup.base/capabilitypatterns/construction_phase_iteration/content.xmi
new file mode 100644
index 0000000..60aec43
--- /dev/null
+++ b/praclib/temp/process.openup.base/capabilitypatterns/construction_phase_iteration/content.xmi
@@ -0,0 +1,95 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xmi:XMI 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">
+ <org.eclipse.epf.uma:ProcessDescription xmi:id="-pszgT2UQY1AzlzJLFM1S5g" name="construction_phase_iteration,_RQi0AdONEdyqlogshP8l4g"
+ guid="-pszgT2UQY1AzlzJLFM1S5g" version="7.2.0">
+ <mainDescription><p>
+ The <a href="./../../practice.tech.evolutionary_arch.base/workproducts/architecture_notebook_9BB92433.html"
+ guid="_0XAf0MlgEdmt3adZL5Dmdw">architecture</a> should be stable when the Construction phase starts, allowing the
+ remaining requirements to be implemented on top of it. Another advantage of validating the architecture and eliminating
+ as many risks as possible during Elaboration is that it provides more predictability in Construction, which allows the
+ <a class="elementlinkwithusertext" href="./../../core.default.role_def.base/roles/project_manager_E657F936.html"
+ guid="_0a0o0MlgEdmt3adZL5Dmdw">project manager</a> to focus on team efficiency and cost reduction.
+</p>
+<p>
+ Functionality is continuously implemented, tested, and integrated, resulting in <a class="elementLinkWithUserText"
+ href="./../../practice.tech.continuous_integration.base/workproducts/build_95D7D8FD.html"
+ guid="_0YuXEMlgEdmt3adZL5Dmdw">builds</a> that are more and more complete and stable. You may deploy a beta or
+ prerelease to a sampling of the intended audience at the end of Construction. Delivery of the actual release is the
+ main focus of the next phase.
+</p>
+<p>
+ The following table summarizes the&nbsp;Construction phase objectives and&nbsp;what activities address each objective:
+</p>
+<p align="center">
+ <strong>Construction phase objectives and activities</strong>
+</p>
+<table cellspacing="0" cellpadding="0" width="648" align="center" border="1">
+ <tbody>
+ <tr>
+ <td class="Normal" valign="top" width="300">
+ <p style="TEXT-ALIGN: justify">
+ <b>Phase objectives</b>
+ </p>
+ </td>
+ <td class="Normal" valign="top" width="348">
+ <p style="TEXT-ALIGN: justify">
+ <b>Activities that address objectives</b>
+ </p>
+ </td>
+ </tr>
+ <tr>
+ <td class="Normal" valign="top" width="300">
+ Iteratively develop a complete product that is ready to transition to the user community<br />
+ </td>
+ <td class="Normal" valign="top" width="348">
+ <p style="TEXT-ALIGN: justify">
+ <a class="elementLink"
+ href="./../../process.openup.base/capabilitypatterns/identify_and_refine_requirements_7FA6CB14.html"
+ guid="_xxcpgdOEEdyqlogshP8l4g">Identify and Refine Requirements</a>
+ </p>
+ <p style="TEXT-ALIGN: justify">
+ <a class="elementLink"
+ href="./../../process.openup.base/capabilitypatterns/develop_solution_4FBB0E6E.html"
+ guid="_RXGoodOFEdyqlogshP8l4g">Develop Solution Increment</a>
+ </p>
+ <p style="TEXT-ALIGN: justify">
+ <a class="elementLink"
+ href="./../../process.openup.base/capabilitypatterns/test_solution_D16D88FC.html"
+ guid="_buG4sdOFEdyqlogshP8l4g">Test Solution</a>
+ </p>
+ </td>
+ </tr>
+ <tr>
+ <td class="Normal" valign="top" width="300">
+ Minimize development costs and achieve some degree of parallelism<br />
+ </td>
+ <td class="Normal" valign="top" width="348">
+ <p style="TEXT-ALIGN: justify">
+ <a class="elementLink"
+ href="./../../process.openup.base/capabilitypatterns/plan_manage_iteration_F9713A62.html"
+ guid="_oZgCsdOEEdyqlogshP8l4g">Plan and Manage Iteration</a><br />
+ </p>
+ <p style="TEXT-ALIGN: justify">
+ <a class="elementLink"
+ href="./../../process.openup.base/capabilitypatterns/develop_solution_4FBB0E6E.html"
+ guid="_RXGoodOFEdyqlogshP8l4g">Develop Solution Increment</a>
+ </p>
+ <p style="TEXT-ALIGN: justify">
+ <a class="elementLink"
+ href="./../../process.openup.base/capabilitypatterns/test_solution_D16D88FC.html"
+ guid="_buG4sdOFEdyqlogshP8l4g">Test Solution</a>
+ </p>
+ </td>
+ </tr>
+ </tbody>
+</table><br />
+<br /></mainDescription>
+ </org.eclipse.epf.uma:ProcessDescription>
+ <org.eclipse.epf.uma:ProcessDescription xmi:id="-2VY1Jl_Sw2Mmk8IfX0ONNw" name="identify_and_refine_requirements,_xxcpgdOEEdyqlogshP8l4g"
+ guid="-2VY1Jl_Sw2Mmk8IfX0ONNw" version="7.2.0"/>
+ <org.eclipse.epf.uma:ActivityDescription xmi:id="-2VY1Jl_Sw2Mmk8IfX0ONNw" name="identify_and_refine_requirements,_xxcpgdOEEdyqlogshP8l4g"
+ guid="-2VY1Jl_Sw2Mmk8IfX0ONNw" version="7.2.0"/>
+</xmi:XMI>
diff --git a/praclib/temp/process.openup.base/capabilitypatterns/construction_phase_iteration/diagram.xmi b/praclib/temp/process.openup.base/capabilitypatterns/construction_phase_iteration/diagram.xmi
new file mode 100644
index 0000000..2ca50fe
--- /dev/null
+++ b/praclib/temp/process.openup.base/capabilitypatterns/construction_phase_iteration/diagram.xmi
@@ -0,0 +1,386 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xmi:XMI xmi:version="2.0"
+ xmlns:xmi="http://www.omg.org/XMI" xmlns:ecore="http://www.eclipse.org/emf/2002/Ecore"
+ xmlns:notation="http://www.eclipse.org/gmf/runtime/1.0.1/notation" xmlns:uml="http://www.eclipse.org/uml2/2.1.0/UML">
+ <uml:Activity xmi:id="_YwV9YNUBEdylRpA9TBY1SQ" name="construction_phase_iteration">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_YwV9YdUBEdylRpA9TBY1SQ" source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_YwV9YtUBEdylRpA9TBY1SQ"
+ key="uri" value="uma://_RQi0ANONEdyqlogshP8l4g#_RQi0AdONEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_YwV9Y9UBEdylRpA9TBY1SQ"
+ key="type" value="Activity"/>
+ </eAnnotations>
+ <node xmi:type="uml:StructuredActivityNode" xmi:id="_Yx-8INUBEdylRpA9TBY1SQ" name="Plan and Manage Iteration"
+ outgoing="_sqrvcNUCEdylRpA9TBY1SQ" incoming="_sKDHkNUCEdylRpA9TBY1SQ">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_Yx-8IdUBEdylRpA9TBY1SQ"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_Yx-8ItUBEdylRpA9TBY1SQ"
+ key="uri" value="uma://_RQi0ANONEdyqlogshP8l4g#_3s7aYdONEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_Yx-8I9UBEdylRpA9TBY1SQ"
+ key="type" value="Activity"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:StructuredActivityNode" xmi:id="_Yx-8JNUBEdylRpA9TBY1SQ" name="Identify and Refine Requirements"
+ outgoing="_p7JAANUCEdylRpA9TBY1SQ" incoming="_phqJANUCEdylRpA9TBY1SQ">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_Yx-8JdUBEdylRpA9TBY1SQ"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_Yx-8JtUBEdylRpA9TBY1SQ"
+ key="uri" value="uma://_RQi0ANONEdyqlogshP8l4g#_AP_nodOOEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_Yx-8J9UBEdylRpA9TBY1SQ"
+ key="type" value="Activity"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:StructuredActivityNode" xmi:id="_Yx-8KNUBEdylRpA9TBY1SQ" name="Develop Solution Increment"
+ outgoing="_q4rmUNUCEdylRpA9TBY1SQ" incoming="_qcOT0NUCEdylRpA9TBY1SQ">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_Yx-8KdUBEdylRpA9TBY1SQ"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_Yx-8KtUBEdylRpA9TBY1SQ"
+ key="uri" value="uma://_RQi0ANONEdyqlogshP8l4g#_CqFrgdOOEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_Yx-8K9UBEdylRpA9TBY1SQ"
+ key="type" value="Activity"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:StructuredActivityNode" xmi:id="_Yx-8LNUBEdylRpA9TBY1SQ" name="Test Solution"
+ outgoing="_rz_YANUCEdylRpA9TBY1SQ" incoming="_rePKcNUCEdylRpA9TBY1SQ">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_Yx-8LdUBEdylRpA9TBY1SQ"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_Yx-8LtUBEdylRpA9TBY1SQ"
+ key="uri" value="uma://_RQi0ANONEdyqlogshP8l4g#_HhjJsdOOEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_Yx-8L9UBEdylRpA9TBY1SQ"
+ key="type" value="Activity"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:StructuredActivityNode" xmi:id="_Yx-8MNUBEdylRpA9TBY1SQ" name="Ongoing Tasks"
+ outgoing="_toYGwNUCEdylRpA9TBY1SQ" incoming="_tLBcYNUCEdylRpA9TBY1SQ">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_Yx-8MdUBEdylRpA9TBY1SQ"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_Yx-8MtUBEdylRpA9TBY1SQ"
+ key="uri" value="uma://_RQi0ANONEdyqlogshP8l4g#_GQejYdOOEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_Yx-8M9UBEdylRpA9TBY1SQ"
+ key="type" value="Activity"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:ForkNode" xmi:id="_goaQYNUCEdylRpA9TBY1SQ" outgoing="_phqJANUCEdylRpA9TBY1SQ _qcOT0NUCEdylRpA9TBY1SQ _rePKcNUCEdylRpA9TBY1SQ _sKDHkNUCEdylRpA9TBY1SQ _tLBcYNUCEdylRpA9TBY1SQ"
+ incoming="_o_1OUNUCEdylRpA9TBY1SQ"/>
+ <node xmi:type="uml:JoinNode" xmi:id="_hGWwoNUCEdylRpA9TBY1SQ" outgoing="_ua5I0NUCEdylRpA9TBY1SQ"
+ incoming="_p7JAANUCEdylRpA9TBY1SQ _q4rmUNUCEdylRpA9TBY1SQ _rz_YANUCEdylRpA9TBY1SQ _sqrvcNUCEdylRpA9TBY1SQ _toYGwNUCEdylRpA9TBY1SQ"/>
+ <node xmi:type="uml:InitialNode" xmi:id="_nPn08NUCEdylRpA9TBY1SQ" outgoing="_o_1OUNUCEdylRpA9TBY1SQ"/>
+ <node xmi:type="uml:ActivityFinalNode" xmi:id="_n3jXoNUCEdylRpA9TBY1SQ" incoming="_ua5I0NUCEdylRpA9TBY1SQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_o_1OUNUCEdylRpA9TBY1SQ" source="_nPn08NUCEdylRpA9TBY1SQ"
+ target="_goaQYNUCEdylRpA9TBY1SQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_phqJANUCEdylRpA9TBY1SQ" source="_goaQYNUCEdylRpA9TBY1SQ"
+ target="_Yx-8JNUBEdylRpA9TBY1SQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_p7JAANUCEdylRpA9TBY1SQ" source="_Yx-8JNUBEdylRpA9TBY1SQ"
+ target="_hGWwoNUCEdylRpA9TBY1SQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_qcOT0NUCEdylRpA9TBY1SQ" source="_goaQYNUCEdylRpA9TBY1SQ"
+ target="_Yx-8KNUBEdylRpA9TBY1SQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_q4rmUNUCEdylRpA9TBY1SQ" source="_Yx-8KNUBEdylRpA9TBY1SQ"
+ target="_hGWwoNUCEdylRpA9TBY1SQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_rePKcNUCEdylRpA9TBY1SQ" source="_goaQYNUCEdylRpA9TBY1SQ"
+ target="_Yx-8LNUBEdylRpA9TBY1SQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_rz_YANUCEdylRpA9TBY1SQ" source="_Yx-8LNUBEdylRpA9TBY1SQ"
+ target="_hGWwoNUCEdylRpA9TBY1SQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_sKDHkNUCEdylRpA9TBY1SQ" source="_goaQYNUCEdylRpA9TBY1SQ"
+ target="_Yx-8INUBEdylRpA9TBY1SQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_sqrvcNUCEdylRpA9TBY1SQ" source="_Yx-8INUBEdylRpA9TBY1SQ"
+ target="_hGWwoNUCEdylRpA9TBY1SQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_tLBcYNUCEdylRpA9TBY1SQ" source="_goaQYNUCEdylRpA9TBY1SQ"
+ target="_Yx-8MNUBEdylRpA9TBY1SQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_toYGwNUCEdylRpA9TBY1SQ" source="_Yx-8MNUBEdylRpA9TBY1SQ"
+ target="_hGWwoNUCEdylRpA9TBY1SQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_ua5I0NUCEdylRpA9TBY1SQ" source="_hGWwoNUCEdylRpA9TBY1SQ"
+ target="_n3jXoNUCEdylRpA9TBY1SQ"/>
+ </uml:Activity>
+ <notation:Diagram xmi:id="_YwV9ZNUBEdylRpA9TBY1SQ" type="AD" element="_YwV9YNUBEdylRpA9TBY1SQ"
+ name="construction_phase_iteration" measurementUnit="Pixel">
+ <children xmi:type="notation:Node" xmi:id="_L-T_4NUCEdylRpA9TBY1SQ" type="1007"
+ element="_Yx-8INUBEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_L-T_5tUCEdylRpA9TBY1SQ" type="4005"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_L-T_4dUCEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_L-T_4tUCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_L-T_49UCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_L-T_5NUCEdylRpA9TBY1SQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_L-T_5dUCEdylRpA9TBY1SQ"
+ x="372" y="96"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_L-T_59UCEdylRpA9TBY1SQ" type="1007"
+ element="_Yx-8JNUBEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_L-T_7dUCEdylRpA9TBY1SQ" type="4005"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_L-T_6NUCEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_L-T_6dUCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_L-T_6tUCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_L-T_69UCEdylRpA9TBY1SQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_L-T_7NUCEdylRpA9TBY1SQ"
+ x="63" y="108"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_L-T_7tUCEdylRpA9TBY1SQ" type="1007"
+ element="_Yx-8KNUBEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_L-T_9NUCEdylRpA9TBY1SQ" type="4005"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_L-T_79UCEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_L-T_8NUCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_L-T_8dUCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_L-T_8tUCEdylRpA9TBY1SQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_L-T_89UCEdylRpA9TBY1SQ"
+ x="192" y="180"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_L-T_9dUCEdylRpA9TBY1SQ" type="1007"
+ element="_Yx-8LNUBEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_L-T_-9UCEdylRpA9TBY1SQ" type="4005"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_L-T_9tUCEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_L-T_99UCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_L-T_-NUCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_L-T_-dUCEdylRpA9TBY1SQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_L-T_-tUCEdylRpA9TBY1SQ"
+ x="324" y="240"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_L-T__NUCEdylRpA9TBY1SQ" type="1007"
+ element="_Yx-8MNUBEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_L-dw4NUCEdylRpA9TBY1SQ" type="4005"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_L-T__dUCEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_L-T__tUCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_L-T__9UCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_L-UAANUCEdylRpA9TBY1SQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_L-UAAdUCEdylRpA9TBY1SQ"
+ x="504" y="180"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_goaQYdUCEdylRpA9TBY1SQ" type="1003"
+ element="_goaQYNUCEdylRpA9TBY1SQ">
+ <styles xmi:type="notation:FontStyle" xmi:id="_goaQYtUCEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_goaQY9UCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_goaQZNUCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_goaQZdUCEdylRpA9TBY1SQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_goaQZtUCEdylRpA9TBY1SQ"
+ x="72" y="60" width="529"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_hGWwodUCEdylRpA9TBY1SQ" type="1006"
+ element="_hGWwoNUCEdylRpA9TBY1SQ">
+ <styles xmi:type="notation:FontStyle" xmi:id="_hGWwotUCEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_hGWwo9UCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_hGWwpNUCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_hGWwpdUCEdylRpA9TBY1SQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_hGWwptUCEdylRpA9TBY1SQ"
+ x="72" y="324" width="529"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_nPw-4NUCEdylRpA9TBY1SQ" type="1004"
+ element="_nPn08NUCEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_nPw-5tUCEdylRpA9TBY1SQ" type="4003">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_nPw-59UCEdylRpA9TBY1SQ"
+ y="5"/>
+ </children>
+ <styles xmi:type="notation:FontStyle" xmi:id="_nPw-4dUCEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_nPw-4tUCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_nPw-49UCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_nPw-5NUCEdylRpA9TBY1SQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_nPw-5dUCEdylRpA9TBY1SQ"
+ x="324" y="12"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_n3jXodUCEdylRpA9TBY1SQ" type="1001"
+ element="_n3jXoNUCEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_n3jXp9UCEdylRpA9TBY1SQ" type="4001">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_n3jXqNUCEdylRpA9TBY1SQ"
+ y="5"/>
+ </children>
+ <styles xmi:type="notation:FontStyle" xmi:id="_n3jXotUCEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_n3jXo9UCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_n3jXpNUCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_n3jXpdUCEdylRpA9TBY1SQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_n3jXptUCEdylRpA9TBY1SQ"
+ x="324" y="360"/>
+ </children>
+ <styles xmi:type="notation:PageStyle" xmi:id="_YwV9ZdUBEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:GuideStyle" xmi:id="_YwV9ZtUBEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_YwV9Z9UBEdylRpA9TBY1SQ"/>
+ <edges xmi:type="notation:Edge" xmi:id="_o_1OUdUCEdylRpA9TBY1SQ" type="3001" element="_o_1OUNUCEdylRpA9TBY1SQ"
+ source="_nPw-4NUCEdylRpA9TBY1SQ" target="_goaQYdUCEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_o_1OVtUCEdylRpA9TBY1SQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_o_1OV9UCEdylRpA9TBY1SQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_o_1OUtUCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_o_1OU9UCEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_o_1OVNUCEdylRpA9TBY1SQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_o_1OVdUCEdylRpA9TBY1SQ"
+ points="[1, 10, 0, -28]$[1, 37, 0, -1]"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_phqJAdUCEdylRpA9TBY1SQ" type="3001" element="_phqJANUCEdylRpA9TBY1SQ"
+ source="_goaQYdUCEdylRpA9TBY1SQ" target="_L-T_59UCEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_phqJBtUCEdylRpA9TBY1SQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_phqJB9UCEdylRpA9TBY1SQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_phqJAtUCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_phqJA9UCEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_phqJBNUCEdylRpA9TBY1SQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_phqJBdUCEdylRpA9TBY1SQ"
+ points="[0, 4, 0, -49]$[-3, 44, -3, -9]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_phqJCNUCEdylRpA9TBY1SQ"
+ id="(0.1436673,0.625)"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_phqJCdUCEdylRpA9TBY1SQ"
+ id="(0.46706587,0.16981132)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_p7JAAdUCEdylRpA9TBY1SQ" type="3001" element="_p7JAANUCEdylRpA9TBY1SQ"
+ source="_L-T_59UCEdylRpA9TBY1SQ" target="_hGWwodUCEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_p7JABtUCEdylRpA9TBY1SQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_p7JAB9UCEdylRpA9TBY1SQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_p7JAAtUCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_p7JAA9UCEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_p7JABNUCEdylRpA9TBY1SQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_p7JABdUCEdylRpA9TBY1SQ"
+ points="[-3, 27, 0, -164]$[-61, 190, -58, -1]"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_p7SJ8NUCEdylRpA9TBY1SQ"
+ id="(0.13988657,0.375)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_qcXdwNUCEdylRpA9TBY1SQ" type="3001" element="_qcOT0NUCEdylRpA9TBY1SQ"
+ source="_goaQYdUCEdylRpA9TBY1SQ" target="_L-T_7tUCEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_qcXdxdUCEdylRpA9TBY1SQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_qcXdxtUCEdylRpA9TBY1SQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_qcXdwdUCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_qcXdwtUCEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_qcXdw9UCEdylRpA9TBY1SQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_qcXdxNUCEdylRpA9TBY1SQ"
+ points="[-2, 4, 56, -138]$[-57, 116, 1, -26]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_cjnv0NUDEdylRpA9TBY1SQ"
+ id="(0.36483932,0.875)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_q41XUNUCEdylRpA9TBY1SQ" type="3001" element="_q4rmUNUCEdylRpA9TBY1SQ"
+ source="_L-T_7tUCEdylRpA9TBY1SQ" target="_hGWwodUCEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_q41XVdUCEdylRpA9TBY1SQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_q41XVtUCEdylRpA9TBY1SQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_q41XUdUCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_q41XUtUCEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_q41XU9UCEdylRpA9TBY1SQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_q41XVNUCEdylRpA9TBY1SQ"
+ points="[-2, 27, 0, -92]$[-22, 118, -20, -1]"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_q41XV9UCEdylRpA9TBY1SQ"
+ id="(0.34971645,0.0)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_rePKcdUCEdylRpA9TBY1SQ" type="3001" element="_rePKcNUCEdylRpA9TBY1SQ"
+ source="_goaQYdUCEdylRpA9TBY1SQ" target="_L-T_9dUCEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_rePKdtUCEdylRpA9TBY1SQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_rePKd9UCEdylRpA9TBY1SQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_rePKctUCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_rePKc9UCEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_rePKdNUCEdylRpA9TBY1SQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_rePKddUCEdylRpA9TBY1SQ"
+ points="[1, 4, -38, -198]$[36, 176, -3, -26]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_h-rDQNUDEdylRpA9TBY1SQ"
+ id="(0.536862,0.875)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_rz_YAdUCEdylRpA9TBY1SQ" type="3001" element="_rz_YANUCEdylRpA9TBY1SQ"
+ source="_L-T_9dUCEdylRpA9TBY1SQ" target="_hGWwodUCEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_rz_YBtUCEdylRpA9TBY1SQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_rz_YB9UCEdylRpA9TBY1SQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_rz_YAtUCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_rz_YA9UCEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_rz_YBNUCEdylRpA9TBY1SQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_rz_YBdUCEdylRpA9TBY1SQ"
+ points="[-5, 27, 34, -35]$[244, 60, 283, -2]"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_eAwcMNUDEdylRpA9TBY1SQ"
+ id="(0.536862,0.125)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_sKDHkdUCEdylRpA9TBY1SQ" type="3001" element="_sKDHkNUCEdylRpA9TBY1SQ"
+ source="_goaQYdUCEdylRpA9TBY1SQ" target="_L-T_4NUCEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_sKDHltUCEdylRpA9TBY1SQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_sKDHl9UCEdylRpA9TBY1SQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_sKDHktUCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_sKDHk9UCEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_sKDHlNUCEdylRpA9TBY1SQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_sKDHldUCEdylRpA9TBY1SQ"
+ points="[11, 4, -108, -40]$[119, 32, 0, -12]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_fG8oMNUDEdylRpA9TBY1SQ"
+ id="(0.70321363,0.0)"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_sKDHmNUCEdylRpA9TBY1SQ"
+ id="(0.5,0.2264151)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_sqrvcdUCEdylRpA9TBY1SQ" type="3001" element="_sqrvcNUCEdylRpA9TBY1SQ"
+ source="_L-T_4NUCEdylRpA9TBY1SQ" target="_hGWwodUCEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_sq05YNUCEdylRpA9TBY1SQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_sq05YdUCEdylRpA9TBY1SQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_sqrvctUCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_sqrvc9UCEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_sqrvdNUCEdylRpA9TBY1SQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_sqrvddUCEdylRpA9TBY1SQ"
+ points="[8, 27, 0, -175]$[8, 202, 0, 0]"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_sq05YtUCEdylRpA9TBY1SQ"
+ id="(0.7088847,0.125)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_tLKmUNUCEdylRpA9TBY1SQ" type="3001" element="_tLBcYNUCEdylRpA9TBY1SQ"
+ source="_goaQYdUCEdylRpA9TBY1SQ" target="_L-T__NUCEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_tLKmVdUCEdylRpA9TBY1SQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_tLKmVtUCEdylRpA9TBY1SQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_tLKmUdUCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_tLKmUtUCEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_tLKmU9UCEdylRpA9TBY1SQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_tLKmVNUCEdylRpA9TBY1SQ"
+ points="[-1, 6, 12, -125]$[-14, 118, -1, -13]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_tLKmV9UCEdylRpA9TBY1SQ"
+ id="(0.8922495,0.625)"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_tLKmWNUCEdylRpA9TBY1SQ"
+ id="(0.4868421,0.24528302)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_toYGwdUCEdylRpA9TBY1SQ" type="3001" element="_toYGwNUCEdylRpA9TBY1SQ"
+ source="_L-T__NUCEdylRpA9TBY1SQ" target="_hGWwodUCEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_toYGxtUCEdylRpA9TBY1SQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_toYGx9UCEdylRpA9TBY1SQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_toYGwtUCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_toYGw9UCEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_toYGxNUCEdylRpA9TBY1SQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_toYGxdUCEdylRpA9TBY1SQ"
+ points="[-2, 27, 0, -98]$[59, 126, 61, 1]"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_toYGyNUCEdylRpA9TBY1SQ"
+ id="(0.8920354,0.875)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_ubC50NUCEdylRpA9TBY1SQ" type="3001" element="_ua5I0NUCEdylRpA9TBY1SQ"
+ source="_hGWwodUCEdylRpA9TBY1SQ" target="_n3jXodUCEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_ubC51dUCEdylRpA9TBY1SQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_ubC51tUCEdylRpA9TBY1SQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_ubC50dUCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_ubC50tUCEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_ubC509UCEdylRpA9TBY1SQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_ubC51NUCEdylRpA9TBY1SQ"
+ points="[1, 4, -10, -53]$[11, 55, 0, -2]"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_ubC519UCEdylRpA9TBY1SQ"
+ id="(0.5416667,0.083333336)"/>
+ </edges>
+ </notation:Diagram>
+</xmi:XMI>
diff --git a/praclib/temp/process.openup.base/capabilitypatterns/construction_phase_iteration/model.xmi b/praclib/temp/process.openup.base/capabilitypatterns/construction_phase_iteration/model.xmi
new file mode 100644
index 0000000..ceed375
--- /dev/null
+++ b/praclib/temp/process.openup.base/capabilitypatterns/construction_phase_iteration/model.xmi
@@ -0,0 +1,171 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_RSetsdONEdyqlogshP8l4g"
+ guid="_RSetsdONEdyqlogshP8l4g">
+ <resourceDescriptors xmi:id="_RSetstONEdyqlogshP8l4g" id="-pszgT2UQY1AzlzJLFM1S5g"
+ uri="content.xmi"/>
+ <resourceDescriptors xmi:id="_FHm20dOOEdyqlogshP8l4g" id="-2VY1Jl_Sw2Mmk8IfX0ONNw"
+ uri="content.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:ProcessComponent xmi:id="_RQi0ANONEdyqlogshP8l4g" name="construction_phase_iteration"
+ guid="_RQi0ANONEdyqlogshP8l4g">
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_3s7aYNONEdyqlogshP8l4g"
+ name="plan_manage_iteration" guid="_3s7aYNONEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_3s7aYdONEdyqlogshP8l4g"
+ name="plan_manage_iteration" guid="_3s7aYdONEdyqlogshP8l4g" superActivities="_RQi0AdONEdyqlogshP8l4g"
+ variabilityType="extends">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://_oZgCsNOEEdyqlogshP8l4g#_oZgCsdOEEdyqlogshP8l4g"/>
+ </processElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_AP_noNOOEdyqlogshP8l4g"
+ name="identify_and_refine_requirements" guid="_AP_noNOOEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_AP_nodOOEdyqlogshP8l4g"
+ name="identify_and_refine_requirements" guid="_AP_nodOOEdyqlogshP8l4g" presentationName="Identify and Refine Requirements"
+ superActivities="_RQi0AdONEdyqlogshP8l4g" breakdownElements="_AQJYodOOEdyqlogshP8l4g _AQJYotOOEdyqlogshP8l4g _AQJYo9OOEdyqlogshP8l4g _AQJYpNOOEdyqlogshP8l4g _AQJYpdOOEdyqlogshP8l4g _AQJYp9OOEdyqlogshP8l4g _AQJYqNOOEdyqlogshP8l4g _AQJYqdOOEdyqlogshP8l4g _AQJYqtOOEdyqlogshP8l4g _AQJYoNOOEdyqlogshP8l4g _AVhA0NOOEdyqlogshP8l4g _AVhA0dOOEdyqlogshP8l4g _AVhA0tOOEdyqlogshP8l4g _AVhA09OOEdyqlogshP8l4g _AVhA1NOOEdyqlogshP8l4g">
+ <presentation xmi:id="-2VY1Jl_Sw2Mmk8IfX0ONNw" href="uma://-pszgT2UQY1AzlzJLFM1S5g#-2VY1Jl_Sw2Mmk8IfX0ONNw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_AQJYoNOOEdyqlogshP8l4g"
+ name="identify_and_outline_requirements" guid="_AQJYoNOOEdyqlogshP8l4g"
+ presentationName="Identify and Outline Requirements" superActivities="_AP_nodOOEdyqlogshP8l4g"
+ additionallyPerformedBy="_AQJYotOOEdyqlogshP8l4g _AQJYo9OOEdyqlogshP8l4g _AQJYpNOOEdyqlogshP8l4g _AQJYpdOOEdyqlogshP8l4g"
+ optionalInput="_AVhA09OOEdyqlogshP8l4g" output="_AQJYp9OOEdyqlogshP8l4g _AQJYqNOOEdyqlogshP8l4g _AQJYqdOOEdyqlogshP8l4g _AQJYqtOOEdyqlogshP8l4g"
+ performedPrimarilyBy="_AQJYodOOEdyqlogshP8l4g">
+ <Task href="uma://_GbYfULPaEduocbW-TPTq7A#_P9cMUPV_EdmdHa9MmVPgqQ"/>
+ <selectedSteps href="uma://_P9iS8PV_EdmdHa9MmVPgqQ#_ckG-cCY-EdqNHcQ-rAojXw"/>
+ <selectedSteps href="uma://_P9iS8PV_EdmdHa9MmVPgqQ#_GAr3IOz3Edq2wJOsmRwmhg"/>
+ <selectedSteps href="uma://_P9iS8PV_EdmdHa9MmVPgqQ#_fDbgkCY-EdqNHcQ-rAojXw"/>
+ <selectedSteps href="uma://-Yt8TXGkE1rwydXR34apsrg#_N66nkApAEdyT57ElgMr6TA"/>
+ <selectedSteps href="uma://_P9iS8PV_EdmdHa9MmVPgqQ#_CD_a8JJKEdyk6dG0ehkW5Q"/>
+ <selectedSteps href="uma://_P9iS8PV_EdmdHa9MmVPgqQ#_Ql45gEI6Edyrh7YaMjqrlA"/>
+ <selectedSteps href="uma://_P9iS8PV_EdmdHa9MmVPgqQ#_0WhHsN-eEdqiM_wFaqLjNg"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_AQJYodOOEdyqlogshP8l4g"
+ name="analyst" guid="_AQJYodOOEdyqlogshP8l4g" presentationName="Analyst"
+ isPlanned="false" superActivities="_AP_nodOOEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0VxJsMlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_AQJYotOOEdyqlogshP8l4g"
+ name="architect" guid="_AQJYotOOEdyqlogshP8l4g" presentationName="Architect"
+ isPlanned="false" superActivities="_AP_nodOOEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0X9iEMlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_AQJYo9OOEdyqlogshP8l4g"
+ name="developer" guid="_AQJYo9OOEdyqlogshP8l4g" presentationName="Developer"
+ isPlanned="false" superActivities="_AP_nodOOEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_AQJYpNOOEdyqlogshP8l4g"
+ name="stakeholder" guid="_AQJYpNOOEdyqlogshP8l4g" presentationName="Stakeholder"
+ isPlanned="false" superActivities="_AP_nodOOEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_dTa6gMAYEdqX-s4mWhkyqQ"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_AQJYpdOOEdyqlogshP8l4g"
+ name="tester" guid="_AQJYpdOOEdyqlogshP8l4g" presentationName="Tester" isPlanned="false"
+ superActivities="_AP_nodOOEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0ZM4MclgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_AQJYp9OOEdyqlogshP8l4g"
+ name="system_wide_requirements" guid="_AQJYp9OOEdyqlogshP8l4g" presentationName="System-Wide Requirements"
+ isPlanned="false" superActivities="_AP_nodOOEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_BVh9cL-CEdqb7N6KIeDL8Q"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_AQJYqNOOEdyqlogshP8l4g"
+ name="use_case" guid="_AQJYqNOOEdyqlogshP8l4g" presentationName="Use Case"
+ isPlanned="false" superActivities="_AP_nodOOEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0VGbUMlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_AQJYqdOOEdyqlogshP8l4g"
+ name="glossary" guid="_AQJYqdOOEdyqlogshP8l4g" presentationName="Glossary"
+ isPlanned="false" superActivities="_AP_nodOOEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_Wn7HcNcEEdqz_d2XWoVt6Q"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_AQJYqtOOEdyqlogshP8l4g"
+ name="use_case_model" guid="_AQJYqtOOEdyqlogshP8l4g" presentationName="Use-Case Model"
+ isPlanned="false" superActivities="_AP_nodOOEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_W2SgEDR5EdutE_HNDTJk5Q"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_AVhA0NOOEdyqlogshP8l4g"
+ name="detail_use_case_scenarios" guid="_AVhA0NOOEdyqlogshP8l4g" presentationName="Detail Use-Case Scenarios"
+ superActivities="_AP_nodOOEdyqlogshP8l4g" additionallyPerformedBy="_AQJYotOOEdyqlogshP8l4g _AQJYo9OOEdyqlogshP8l4g _AQJYpNOOEdyqlogshP8l4g _AQJYpdOOEdyqlogshP8l4g"
+ mandatoryInput="_AQJYqNOOEdyqlogshP8l4g" output="_AQJYqNOOEdyqlogshP8l4g _AQJYqdOOEdyqlogshP8l4g _AQJYqtOOEdyqlogshP8l4g"
+ performedPrimarilyBy="_AQJYodOOEdyqlogshP8l4g">
+ <Task href="uma://_GbYfULPaEduocbW-TPTq7A#_SL7N0LPdEduocbW-TPTq7A"/>
+ <selectedSteps href="uma://-oFAa8Uu6tr_GkE_E0iycdQ#_fAWPkJLZEdyk6dG0ehkW5Q"/>
+ <selectedSteps href="uma://-locCQOxOUM8zej2tBD6M6Q#_-pOLIUbEEdyx8quJU3Grxg"/>
+ <selectedSteps href="uma://-oFAa8Uu6tr_GkE_E0iycdQ#_iEvYMJLaEdyk6dG0ehkW5Q"/>
+ <selectedSteps href="uma://-oFAa8Uu6tr_GkE_E0iycdQ#_kojt4JLcEdyk6dG0ehkW5Q"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_AVhA0dOOEdyqlogshP8l4g"
+ name="detail_system_wide_requirements" guid="_AVhA0dOOEdyqlogshP8l4g" presentationName="Detail System-Wide Requirements"
+ superActivities="_AP_nodOOEdyqlogshP8l4g" additionallyPerformedBy="_AQJYotOOEdyqlogshP8l4g _AQJYo9OOEdyqlogshP8l4g _AQJYpNOOEdyqlogshP8l4g _AQJYpdOOEdyqlogshP8l4g"
+ mandatoryInput="_AQJYp9OOEdyqlogshP8l4g" optionalInput="_AQJYqNOOEdyqlogshP8l4g"
+ output="_AQJYp9OOEdyqlogshP8l4g _AQJYqdOOEdyqlogshP8l4g" performedPrimarilyBy="_AQJYodOOEdyqlogshP8l4g">
+ <Task href="uma://_GbYfULPaEduocbW-TPTq7A#_4z8Z0EbEEdyx8quJU3Grxg"/>
+ <selectedSteps href="uma://-9sNgONA1WJCxf12B40uDgw#_4z8Z1EbEEdyx8quJU3Grxg"/>
+ <selectedSteps href="uma://-9sNgONA1WJCxf12B40uDgw#_4z8Z0UbEEdyx8quJU3Grxg"/>
+ <selectedSteps href="uma://-9sNgONA1WJCxf12B40uDgw#_4z8Z0kbEEdyx8quJU3Grxg"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_AVhA0tOOEdyqlogshP8l4g"
+ name="create_test_cases" guid="_AVhA0tOOEdyqlogshP8l4g" presentationName="Create Test Cases"
+ superActivities="_AP_nodOOEdyqlogshP8l4g" additionallyPerformedBy="_AQJYodOOEdyqlogshP8l4g _AQJYo9OOEdyqlogshP8l4g _AQJYpNOOEdyqlogshP8l4g"
+ mandatoryInput="_AVhA09OOEdyqlogshP8l4g" optionalInput="_AVhA1NOOEdyqlogshP8l4g"
+ output="_AVhA1NOOEdyqlogshP8l4g" performedPrimarilyBy="_AQJYpdOOEdyqlogshP8l4g">
+ <Task href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_0iwc0clgEdmt3adZL5Dmdw"/>
+ <selectedSteps href="uma://_NrVKsKeqEdmKDbQuyzCoqQ#_IJFSsKuSEdmhFZtkg1nakg"/>
+ <selectedSteps href="uma://_NrVKsKeqEdmKDbQuyzCoqQ#_aDe_ILGcEdubqf8m_Zrvvg"/>
+ <selectedSteps href="uma://_NrVKsKeqEdmKDbQuyzCoqQ#_LpbM8KuSEdmhFZtkg1nakg"/>
+ <selectedSteps href="uma://_NrVKsKeqEdmKDbQuyzCoqQ#_NK18YKuSEdmhFZtkg1nakg"/>
+ <selectedSteps href="uma://_NrVKsKeqEdmKDbQuyzCoqQ#_Ok_mMKuSEdmhFZtkg1nakg"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_AVhA09OOEdyqlogshP8l4g"
+ name="technical_specification_slot" guid="_AVhA09OOEdyqlogshP8l4g" presentationName="[Technical Specification]"
+ isPlanned="false" superActivities="_AP_nodOOEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_i3vkoLS-EduDY8LNbMCDBA"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_AVhA1NOOEdyqlogshP8l4g"
+ name="test_case" guid="_AVhA1NOOEdyqlogshP8l4g" presentationName="Test Case"
+ isPlanned="false" superActivities="_AP_nodOOEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZS-0MlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_CqFrgNOOEdyqlogshP8l4g"
+ name="develop_solution" guid="_CqFrgNOOEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_CqFrgdOOEdyqlogshP8l4g"
+ name="develop_solution" guid="_CqFrgdOOEdyqlogshP8l4g" superActivities="_RQi0AdONEdyqlogshP8l4g"
+ variabilityType="extends">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://_RXGooNOFEdyqlogshP8l4g#_RXGoodOFEdyqlogshP8l4g"/>
+ </processElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_GQejYNOOEdyqlogshP8l4g"
+ name="ongoing_tasks" guid="_GQejYNOOEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_GQejYdOOEdyqlogshP8l4g"
+ name="ongoing_tasks" guid="_GQejYdOOEdyqlogshP8l4g" superActivities="_RQi0AdONEdyqlogshP8l4g"
+ variabilityType="extends">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://__ZInMNOEEdyqlogshP8l4g#__ZInMdOEEdyqlogshP8l4g"/>
+ </processElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_HhjJsNOOEdyqlogshP8l4g"
+ name="test_solution" guid="_HhjJsNOOEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_HhjJsdOOEdyqlogshP8l4g"
+ name="test_solution" guid="_HhjJsdOOEdyqlogshP8l4g" superActivities="_RQi0AdONEdyqlogshP8l4g"
+ variabilityType="extends">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://_buG4sNOFEdyqlogshP8l4g#_buG4sdOFEdyqlogshP8l4g"/>
+ </processElements>
+ </childPackages>
+ <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_RQi0AdONEdyqlogshP8l4g"
+ name="construction_phase_iteration" guid="_RQi0AdONEdyqlogshP8l4g" briefDescription="This iteration template defines the activities (and associated roles and work products) performed in a typical iteration in the Construction phase."
+ presentationName="Construction Phase Iteration" breakdownElements="_3s7aYdONEdyqlogshP8l4g _AP_nodOOEdyqlogshP8l4g _CqFrgdOOEdyqlogshP8l4g _HhjJsdOOEdyqlogshP8l4g _GQejYdOOEdyqlogshP8l4g">
+ <presentation xmi:id="-pszgT2UQY1AzlzJLFM1S5g" href="uma://-pszgT2UQY1AzlzJLFM1S5g#-pszgT2UQY1AzlzJLFM1S5g"/>
+ <defaultContext href="uma://_Sw_vnNnREdyNj6EOmqy5Rg#_gExDwNQxEdyk9oc_L5Vk0g"/>
+ <validContext href="uma://_Sw_vnNnREdyNj6EOmqy5Rg#_gExDwNQxEdyk9oc_L5Vk0g"/>
+ </process>
+ </org.eclipse.epf.uma:ProcessComponent>
+</xmi:XMI>
diff --git a/praclib/temp/process.openup.base/capabilitypatterns/develop_architecture/content.xmi b/praclib/temp/process.openup.base/capabilitypatterns/develop_architecture/content.xmi
new file mode 100644
index 0000000..f8063ca
--- /dev/null
+++ b/praclib/temp/process.openup.base/capabilitypatterns/develop_architecture/content.xmi
@@ -0,0 +1,42 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:ProcessDescription 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="-VFp5B68iro5ga1pz4nbQFw"
+ name="develop_architecture,_KaeNsdOFEdyqlogshP8l4g" guid="-VFp5B68iro5ga1pz4nbQFw"
+ version="7.2.0">
+ <mainDescription><p>
+ This activity refines the initial high-level architecture into working software. The objective is to produce stable
+ software that adequately addresses the technical risks in scope.
+</p>
+<p>
+ The architect and developers work together to:
+</p>
+<ul>
+ <li>
+ Refine the initial sketch of the architecture into concrete design elements
+ </li>
+ <li>
+ Ensure that the architecture decisions are adequately captured and communicated
+ </li>
+ <li>
+ Ensure that the team has enough information to enable software to be developed
+ </li>
+ <li>
+ Ensure that the requirements that were prioritized for the current iteration are adequately addressed in the
+ software
+ </li>
+</ul>
+<p>
+ In an iterative project, the team should not attempt to develop the architecture for the entire project in a single
+ pass. Rather, they should focus on meeting the requirements in scope for the current iteration, while making decisions
+ in the context of the wider project.
+</p></mainDescription>
+ <howtoStaff><p>
+ These activities are best carried out as a collaborative effort by the team, with the architect acting as a focal point
+ for coordinating and facilitating the decisions.
+</p></howtoStaff>
+ <usageNotes><p>
+ The work is best done in several sessions, perhaps performed over a few days.
+</p></usageNotes>
+</org.eclipse.epf.uma:ProcessDescription>
diff --git a/praclib/temp/process.openup.base/capabilitypatterns/develop_architecture/model.xmi b/praclib/temp/process.openup.base/capabilitypatterns/develop_architecture/model.xmi
new file mode 100644
index 0000000..ab68515
--- /dev/null
+++ b/praclib/temp/process.openup.base/capabilitypatterns/develop_architecture/model.xmi
@@ -0,0 +1,78 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_KdJuQNOFEdyqlogshP8l4g"
+ guid="_KdJuQNOFEdyqlogshP8l4g">
+ <resourceDescriptors xmi:id="_KdJuQdOFEdyqlogshP8l4g" id="-VFp5B68iro5ga1pz4nbQFw"
+ uri="content.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:ProcessComponent xmi:id="_KaeNsNOFEdyqlogshP8l4g" name="develop_architecture"
+ guid="_KaeNsNOFEdyqlogshP8l4g">
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_TV_k8NOKEdyqlogshP8l4g"
+ name="develop_solution" guid="_TV_k8NOKEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_TV_k8dOKEdyqlogshP8l4g"
+ name="develop_solution" guid="_TV_k8dOKEdyqlogshP8l4g" superActivities="_KaeNsdOFEdyqlogshP8l4g"
+ variabilityType="extends">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://_RXGooNOFEdyqlogshP8l4g#_RXGoodOFEdyqlogshP8l4g"/>
+ </processElements>
+ </childPackages>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_Ei9OcdOKEdyqlogshP8l4g"
+ name="architect" guid="_Ei9OcdOKEdyqlogshP8l4g" presentationName="Architect"
+ isPlanned="false" superActivities="_KaeNsdOFEdyqlogshP8l4g" responsibleFor="_EjG_cNOKEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0X9iEMlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_EjG_cNOKEdyqlogshP8l4g"
+ name="architecture_notebook" guid="_EjG_cNOKEdyqlogshP8l4g" presentationName="Architecture Notebook"
+ isPlanned="false" superActivities="_KaeNsdOFEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_4gaS4LPREduocbW-TPTq7A#_0XAf0MlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_6RuKMN_1EdyOsumnGvWsEg"
+ name="evolve_the_arch" guid="_6RuKMN_1EdyOsumnGvWsEg" presentationName="Evolve the Architecture"
+ superActivities="_KaeNsdOFEdyqlogshP8l4g" additionallyPerformedBy="_6RuKMd_1EdyOsumnGvWsEg _6RuKMt_1EdyOsumnGvWsEg"
+ mandatoryInput="_6R37MN_1EdyOsumnGvWsEg _EjG_cNOKEdyqlogshP8l4g" optionalInput="_6R37Md_1EdyOsumnGvWsEg _6R37Mt_1EdyOsumnGvWsEg"
+ output="_EjG_cNOKEdyqlogshP8l4g" performedPrimarilyBy="_Ei9OcdOKEdyqlogshP8l4g">
+ <Task href="uma://_4gaS4LPREduocbW-TPTq7A#_0gRJgMlgEdmt3adZL5Dmdw"/>
+ <selectedSteps href="uma://_rUis8LBKEdm7Eph_l9Cn9w#_l92AYNpaEdyP58ppo1Ieaw"/>
+ <selectedSteps href="uma://_rUis8LBKEdm7Eph_l9Cn9w#_G_k1kBaqEduSTJywppIxVQ"/>
+ <selectedSteps href="uma://_rUis8LBKEdm7Eph_l9Cn9w#_0qoQ8CikEduQBKSg5n118w"/>
+ <selectedSteps href="uma://_rUis8LBKEdm7Eph_l9Cn9w#_Vdln8MP3EdmWKcx6ixEiwg"/>
+ <selectedSteps href="uma://_rUis8LBKEdm7Eph_l9Cn9w#_xIIVkMUbEdu5GrwIlTJV7g"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_6RuKMd_1EdyOsumnGvWsEg"
+ name="developer" guid="_6RuKMd_1EdyOsumnGvWsEg" presentationName="Developer"
+ isPlanned="false" superActivities="_KaeNsdOFEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_6RuKMt_1EdyOsumnGvWsEg"
+ name="project_manager" guid="_6RuKMt_1EdyOsumnGvWsEg" presentationName="Project Manager"
+ isPlanned="false" superActivities="_KaeNsdOFEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0a0o0MlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6R37MN_1EdyOsumnGvWsEg"
+ name="technical_specification_slot" guid="_6R37MN_1EdyOsumnGvWsEg" presentationName="[Technical Specification]"
+ isPlanned="false" superActivities="_KaeNsdOFEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_i3vkoLS-EduDY8LNbMCDBA"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6R37Md_1EdyOsumnGvWsEg"
+ name="software_design_slot" guid="_6R37Md_1EdyOsumnGvWsEg" presentationName="[Software Design]"
+ isPlanned="false" superActivities="_KaeNsdOFEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_IcQOUEqdEdyi3_jfs__bIQ"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_6R37Mt_1EdyOsumnGvWsEg"
+ name="software_implementation_slot" guid="_6R37Mt_1EdyOsumnGvWsEg" presentationName="[Software Implementation]"
+ isPlanned="false" superActivities="_KaeNsdOFEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_Vux8UEfUEdyiPI8btkmvmw"/>
+ </processElements>
+ <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_KaeNsdOFEdyqlogshP8l4g"
+ name="develop_architecture" guid="_KaeNsdOFEdyqlogshP8l4g" briefDescription="Develop the architecturally significant requirements prioritzed for this iteration."
+ presentationName="Develop the Architecture" breakdownElements="_Ei9OcdOKEdyqlogshP8l4g _EjG_cNOKEdyqlogshP8l4g _TV_k8dOKEdyqlogshP8l4g _6RuKMN_1EdyOsumnGvWsEg _6RuKMd_1EdyOsumnGvWsEg _6RuKMt_1EdyOsumnGvWsEg _6R37MN_1EdyOsumnGvWsEg _6R37Md_1EdyOsumnGvWsEg _6R37Mt_1EdyOsumnGvWsEg">
+ <presentation xmi:id="-VFp5B68iro5ga1pz4nbQFw" href="uma://-VFp5B68iro5ga1pz4nbQFw#-VFp5B68iro5ga1pz4nbQFw"/>
+ <defaultContext href="uma://_5pP3a9_fEdyOsumnGvWsEg#_gExDwNQxEdyk9oc_L5Vk0g"/>
+ <validContext href="uma://_5pP3a9_fEdyOsumnGvWsEg#_gExDwNQxEdyk9oc_L5Vk0g"/>
+ </process>
+ </org.eclipse.epf.uma:ProcessComponent>
+</xmi:XMI>
diff --git a/praclib/temp/process.openup.base/capabilitypatterns/develop_solution/content.xmi b/praclib/temp/process.openup.base/capabilitypatterns/develop_solution/content.xmi
new file mode 100644
index 0000000..fd7186a
--- /dev/null
+++ b/praclib/temp/process.openup.base/capabilitypatterns/develop_solution/content.xmi
@@ -0,0 +1,112 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:ProcessDescription 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="-ux7ytJ8wsCQm5rzKYxNA7Q"
+ name="develop_solution,_RXGoodOFEdyqlogshP8l4g" guid="-ux7ytJ8wsCQm5rzKYxNA7Q"
+ version="7.2.0">
+ <mainDescription><h3>
+ Introduction
+</h3>
+<p>
+ Run this activity as a way to perform goal-based planning and execution. Work is taken on by developers, and work
+ progress is tracked based on the goals achieved using the designed, developer-tested, and integrated source code.
+</p>
+<h4>
+ Context of what is being developed
+</h4>
+<p>
+ A context can be specified when a requirement is assigned to be developed, thus specifying how broadly a requirement is
+ to be developed in an iteration. Development may focus on a layer (such as the user interface, business logic, or
+ database access), on a component, and so on.
+</p>
+<p>
+ Whether a context is specified or not, the developer's responsibility is to create a design and implementation for that
+ requirement.&nbsp;The developer&nbsp;also writes and runs developer tests against the implementation to make sure that
+ it works as designed, both as a unit and integrated into the code base.
+</p>
+<h4>
+ Overview of workflow
+</h4>
+<p>
+ Typical changes require some effort in designing the solution before moving into implementation, even if it is only a
+ mental exercise that results in no long-term work product. The design for trivial changes to the existing
+ implementation (to, for example, support some requirement) might be self-evident in the context of the existing
+ architecture and design.
+</p>
+<p>
+ Once the organization of the technical solution is clear, define developer tests that will verify the implementation.
+ This test-driven approach ensures that design considerations have in fact taken place before the solution is coded. The
+ tests are run up front and, if they fail, clearly define the criteria to determine if the implementation works as
+ intended.
+</p>
+<p>
+ Failed tests lead to&nbsp;an implementation of the solution, upon completion of which you run the tests again. This
+ innermost loop of implementation and developer testing is repeated until the tests pass.
+</p>
+<p>
+ Passing the tests does not necessarily mean that the solution is a high-quality, appropriate solution. It is proper to
+ revisit the design at this point. That path loops back through the process, since any changes to the design could
+ affect the developer tests and implementation.
+</p>
+<p>
+ Once the tests pass and the design of the solution is appropriate, there is one more possible loopback. It is best to
+ keep the test-driven, evolutionary design inner loops as tight as possible. Come up with some small-scale design
+ solution for a part of the work item, define a test or two for the implementation of that one part of the solution,
+ pass that test, verify the quality, and then continue on in a test-first manner until that part of the design is
+ working. Then, in the outermost loop of the activity, go back to the work item and design another chunk to get closer
+ to completion.
+</p></mainDescription>
+ <purpose><ul>
+ <li>
+ For developers: To create a solution for the work item for which they are responsible
+ </li>
+ <li>
+ For project managers: To have a goal-based way of tracking project status
+ </li>
+</ul></purpose>
+ <usageNotes><p>
+ This activity occurs multiple times during each iteration. Usually, there is one instance for each work item planned
+ for that iteration. When instantiated in a project plan, the pattern becomes a development task to be taken on by one
+ or more developers, and you should rename it to include the actual requirement name. Optionally, the words <b>Solution
+ Increment</b>&nbsp;may be suppressed, then you can instantiate the pattern this way:
+</p>
+<blockquote>
+ <p align="left">
+ Develop requirement_name (within context_name context)
+ </p>
+</blockquote>
+<p>
+ If a context is specified, there will be one instance of this pattern for each requirement for each context.
+</p>
+<blockquote>
+ <p>
+ <b>Example</b>
+ </p>
+ <ol>
+ <li>
+ Develop scenario 1 (within user interface context)
+ </li>
+ <li>
+ Develop scenario 1 (within business logic and database access context)
+ </li>
+ <li>
+ Develop scenario 2
+ </li>
+ <li>
+ Develop supplemental requirement 1
+ </li>
+ </ol>
+</blockquote>
+<p>
+ Note that there are four instances of this pattern in the preceding example:
+</p>
+<ul>
+ <li>
+ The first two are related to the same requirement (scenario 1) but within two different contexts
+ </li>
+ <li>
+ The last two are related to different requirements, with no context specified.
+ </li>
+</ul></usageNotes>
+</org.eclipse.epf.uma:ProcessDescription>
diff --git a/praclib/temp/process.openup.base/capabilitypatterns/develop_solution/diagram.xmi b/praclib/temp/process.openup.base/capabilitypatterns/develop_solution/diagram.xmi
new file mode 100644
index 0000000..2cf0224
--- /dev/null
+++ b/praclib/temp/process.openup.base/capabilitypatterns/develop_solution/diagram.xmi
@@ -0,0 +1,556 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xmi:XMI xmi:version="2.0"
+ xmlns:xmi="http://www.omg.org/XMI" xmlns:ecore="http://www.eclipse.org/emf/2002/Ecore"
+ xmlns:notation="http://www.eclipse.org/gmf/runtime/1.0.1/notation" xmlns:uml="http://www.eclipse.org/uml2/2.1.0/UML">
+ <uml:Activity xmi:id="_CCbpoNQSEdyk9oc_L5Vk0g" name="develop_solution">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_CCbpodQSEdyk9oc_L5Vk0g" source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_CCbpotQSEdyk9oc_L5Vk0g"
+ key="uri" value="uma://_RXGooNOFEdyqlogshP8l4g#_RXGoodOFEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_CCbpo9QSEdyk9oc_L5Vk0g"
+ key="type" value="Activity"/>
+ </eAnnotations>
+ <node xmi:type="uml:ActivityParameterNode" xmi:id="_CWt3kNQSEdyk9oc_L5Vk0g" name="Design the Solution"
+ outgoing="_6NZKkNQSEdyk9oc_L5Vk0g" incoming="_2b7EENQSEdyk9oc_L5Vk0g _7Rg6ANQSEdyk9oc_L5Vk0g">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_CWt3kdQSEdyk9oc_L5Vk0g"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_CWt3ktQSEdyk9oc_L5Vk0g"
+ key="uri" value="uma://_RXGooNOFEdyqlogshP8l4g#_frOcQNOKEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_CWt3k9QSEdyk9oc_L5Vk0g"
+ key="type" value="Task"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:ActivityParameterNode" xmi:id="_CWt3lNQSEdyk9oc_L5Vk0g" name="Implement Developer Tests"
+ outgoing="_0ZYkkNQSEdyk9oc_L5Vk0g" incoming="_5-H_gNQSEdyk9oc_L5Vk0g">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_CWt3ldQSEdyk9oc_L5Vk0g"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_CWt3ltQSEdyk9oc_L5Vk0g"
+ key="uri" value="uma://_RXGooNOFEdyqlogshP8l4g#_gXo2UNOKEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_CWt3l9QSEdyk9oc_L5Vk0g"
+ key="type" value="Task"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:ActivityParameterNode" xmi:id="_CWt3mNQSEdyk9oc_L5Vk0g" name="Implement Solution"
+ outgoing="_1O0-0NQSEdyk9oc_L5Vk0g" incoming="_uqnD4NQSEdyk9oc_L5Vk0g">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_CWt3mdQSEdyk9oc_L5Vk0g"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_CWt3mtQSEdyk9oc_L5Vk0g"
+ key="uri" value="uma://_RXGooNOFEdyqlogshP8l4g#_hVe-oNOKEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_CWt3m9QSEdyk9oc_L5Vk0g"
+ key="type" value="Task"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:ActivityParameterNode" xmi:id="_CWt3nNQSEdyk9oc_L5Vk0g" name="Run Developer Tests"
+ outgoing="_uMN3sNQSEdyk9oc_L5Vk0g" incoming="_0yFYcNQSEdyk9oc_L5Vk0g">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_CWt3ndQSEdyk9oc_L5Vk0g"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_CWt3ntQSEdyk9oc_L5Vk0g"
+ key="uri" value="uma://_RXGooNOFEdyqlogshP8l4g#_iRZNQNOKEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_CWt3n9QSEdyk9oc_L5Vk0g"
+ key="type" value="Task"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:ActivityParameterNode" xmi:id="_CWt3oNQSEdyk9oc_L5Vk0g" name="Integrate and Create Build"
+ outgoing="_TBG70NQTEdyk9oc_L5Vk0g" incoming="_9A5M8NQSEdyk9oc_L5Vk0g">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_CWt3odQSEdyk9oc_L5Vk0g"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_CWt3otQSEdyk9oc_L5Vk0g"
+ key="uri" value="uma://_RXGooNOFEdyqlogshP8l4g#_cXtwwNQREdyk9oc_L5Vk0g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_CWt3o9QSEdyk9oc_L5Vk0g"
+ key="type" value="Task"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:DecisionNode" xmi:id="_QjHr4NQSEdyk9oc_L5Vk0g" outgoing="_5p6qENQSEdyk9oc_L5Vk0g _7Rg6ANQSEdyk9oc_L5Vk0g"
+ incoming="_C0TWANQTEdyk9oc_L5Vk0g"/>
+ <node xmi:type="uml:DecisionNode" xmi:id="_VJgBINQSEdyk9oc_L5Vk0g" outgoing="_uqnD4NQSEdyk9oc_L5Vk0g _17lXINQSEdyk9oc_L5Vk0g"
+ incoming="_uMN3sNQSEdyk9oc_L5Vk0g"/>
+ <node xmi:type="uml:DecisionNode" xmi:id="_Vs0JkNQSEdyk9oc_L5Vk0g" outgoing="_2b7EENQSEdyk9oc_L5Vk0g _9A5M8NQSEdyk9oc_L5Vk0g _Q1-KYNo8EdyzZqGyZ7hwdw"
+ incoming="_17lXINQSEdyk9oc_L5Vk0g"/>
+ <node xmi:type="uml:ActivityFinalNode" xmi:id="_XXEE4NQSEdyk9oc_L5Vk0g" incoming="_TUi1MNQTEdyk9oc_L5Vk0g"/>
+ <node xmi:type="uml:InitialNode" xmi:id="_XtJpoNQSEdyk9oc_L5Vk0g" outgoing="_CbJ2MNQTEdyk9oc_L5Vk0g"/>
+ <node xmi:type="uml:MergeNode" xmi:id="_zLiRYNQSEdyk9oc_L5Vk0g" outgoing="_0yFYcNQSEdyk9oc_L5Vk0g"
+ incoming="_0ZYkkNQSEdyk9oc_L5Vk0g _1O0-0NQSEdyk9oc_L5Vk0g"/>
+ <node xmi:type="uml:MergeNode" xmi:id="_41-EoNQSEdyk9oc_L5Vk0g" outgoing="_5-H_gNQSEdyk9oc_L5Vk0g"
+ incoming="_5p6qENQSEdyk9oc_L5Vk0g _6NZKkNQSEdyk9oc_L5Vk0g"/>
+ <node xmi:type="uml:MergeNode" xmi:id="_BI91kNQTEdyk9oc_L5Vk0g" outgoing="_C0TWANQTEdyk9oc_L5Vk0g"
+ incoming="_CbJ2MNQTEdyk9oc_L5Vk0g _R8y_INQTEdyk9oc_L5Vk0g"/>
+ <node xmi:type="uml:ActivityParameterNode" xmi:id="_GEVz0No8EdyzZqGyZ7hwdw" name="Integrate and Create Build"
+ outgoing="_b_MvgN9IEdyXPePcD0t0WQ" incoming="_Q1-KYNo8EdyzZqGyZ7hwdw">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_GEVz0do8EdyzZqGyZ7hwdw"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_GEVz0to8EdyzZqGyZ7hwdw"
+ key="uri" value="uma://_RXGooNOFEdyqlogshP8l4g#_Dlo8wNo8EdyzZqGyZ7hwdw"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_GEVz09o8EdyzZqGyZ7hwdw"
+ key="type" value="Task"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:DecisionNode" xmi:id="_GERT0N9JEdyXPePcD0t0WQ" outgoing="_R8y_INQTEdyk9oc_L5Vk0g _TUi1MNQTEdyk9oc_L5Vk0g"
+ incoming="_b_MvgN9IEdyXPePcD0t0WQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_uMN3sNQSEdyk9oc_L5Vk0g" source="_CWt3nNQSEdyk9oc_L5Vk0g"
+ target="_VJgBINQSEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_uqnD4NQSEdyk9oc_L5Vk0g" source="_VJgBINQSEdyk9oc_L5Vk0g"
+ target="_CWt3mNQSEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_0ZYkkNQSEdyk9oc_L5Vk0g" source="_CWt3lNQSEdyk9oc_L5Vk0g"
+ target="_zLiRYNQSEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_0yFYcNQSEdyk9oc_L5Vk0g" source="_zLiRYNQSEdyk9oc_L5Vk0g"
+ target="_CWt3nNQSEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_1O0-0NQSEdyk9oc_L5Vk0g" source="_CWt3mNQSEdyk9oc_L5Vk0g"
+ target="_zLiRYNQSEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_17lXINQSEdyk9oc_L5Vk0g" name="[test pass]"
+ source="_VJgBINQSEdyk9oc_L5Vk0g" target="_Vs0JkNQSEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_2b7EENQSEdyk9oc_L5Vk0g" name="[code needs refactoring]"
+ source="_Vs0JkNQSEdyk9oc_L5Vk0g" target="_CWt3kNQSEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_5p6qENQSEdyk9oc_L5Vk0g" name="[trivial change]"
+ source="_QjHr4NQSEdyk9oc_L5Vk0g" target="_41-EoNQSEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_5-H_gNQSEdyk9oc_L5Vk0g" source="_41-EoNQSEdyk9oc_L5Vk0g"
+ target="_CWt3lNQSEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_6NZKkNQSEdyk9oc_L5Vk0g" source="_CWt3kNQSEdyk9oc_L5Vk0g"
+ target="_41-EoNQSEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_7Rg6ANQSEdyk9oc_L5Vk0g" name="[typical change]"
+ source="_QjHr4NQSEdyk9oc_L5Vk0g" target="_CWt3kNQSEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_9A5M8NQSEdyk9oc_L5Vk0g" name="[code is well designed]"
+ source="_Vs0JkNQSEdyk9oc_L5Vk0g" target="_CWt3oNQSEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_CbJ2MNQTEdyk9oc_L5Vk0g" source="_XtJpoNQSEdyk9oc_L5Vk0g"
+ target="_BI91kNQTEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_C0TWANQTEdyk9oc_L5Vk0g" source="_BI91kNQTEdyk9oc_L5Vk0g"
+ target="_QjHr4NQSEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_R8y_INQTEdyk9oc_L5Vk0g" name="[more work to do]"
+ source="_GERT0N9JEdyXPePcD0t0WQ" target="_BI91kNQTEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_TBG70NQTEdyk9oc_L5Vk0g" source="_CWt3oNQSEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_TUi1MNQTEdyk9oc_L5Vk0g" name="[work complete]"
+ source="_GERT0N9JEdyXPePcD0t0WQ" target="_XXEE4NQSEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_Q1-KYNo8EdyzZqGyZ7hwdw" name="[code is well-designed]"
+ source="_Vs0JkNQSEdyk9oc_L5Vk0g" target="_GEVz0No8EdyzZqGyZ7hwdw"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_b_MvgN9IEdyXPePcD0t0WQ" source="_GEVz0No8EdyzZqGyZ7hwdw"
+ target="_GERT0N9JEdyXPePcD0t0WQ"/>
+ </uml:Activity>
+ <notation:Diagram xmi:id="_CDVBgNQSEdyk9oc_L5Vk0g" type="AD" element="_CCbpoNQSEdyk9oc_L5Vk0g"
+ name="develop_solution" measurementUnit="Pixel">
+ <children xmi:type="notation:Node" xmi:id="_GCC50NQSEdyk9oc_L5Vk0g" type="1009"
+ element="_CWt3kNQSEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_GCC51tQSEdyk9oc_L5Vk0g" type="4008"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_GCC50dQSEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_GCC50tQSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_GCC509QSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_GCC51NQSEdyk9oc_L5Vk0g" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_GCC51dQSEdyk9oc_L5Vk0g"
+ x="264" y="180"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_GCC519QSEdyk9oc_L5Vk0g" type="1009"
+ element="_CWt3lNQSEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_GCC53dQSEdyk9oc_L5Vk0g" type="4008"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_GCC52NQSEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_GCC52dQSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_GCC52tQSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_GCC529QSEdyk9oc_L5Vk0g" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_GCC53NQSEdyk9oc_L5Vk0g"
+ x="72" y="240"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_GCC53tQSEdyk9oc_L5Vk0g" type="1009"
+ element="_CWt3mNQSEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_GCC55NQSEdyk9oc_L5Vk0g" type="4008"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_GCC539QSEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_GCC54NQSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_GCC54dQSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_GCC54tQSEdyk9oc_L5Vk0g" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_GCC549QSEdyk9oc_L5Vk0g"
+ x="84" y="576"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_GCC55dQSEdyk9oc_L5Vk0g" type="1009"
+ element="_CWt3nNQSEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_GCMq0NQSEdyk9oc_L5Vk0g" type="4008"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_GCC55tQSEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_GCC559QSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_GCC56NQSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_GCC56dQSEdyk9oc_L5Vk0g" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_GCC56tQSEdyk9oc_L5Vk0g"
+ x="84" y="408"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_QjHr4dQSEdyk9oc_L5Vk0g" type="1005"
+ element="_QjHr4NQSEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_QjHr59QSEdyk9oc_L5Vk0g" type="4004"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_QjHr4tQSEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_QjHr49QSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_QjHr5NQSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_QjHr5dQSEdyk9oc_L5Vk0g" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_QjHr5tQSEdyk9oc_L5Vk0g"
+ x="108" y="84"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_VJgBIdQSEdyk9oc_L5Vk0g" type="1005"
+ element="_VJgBINQSEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_VJpyINQSEdyk9oc_L5Vk0g" type="4004"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_VJgBItQSEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_VJgBI9QSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_VJgBJNQSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_VJgBJdQSEdyk9oc_L5Vk0g" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_VJgBJtQSEdyk9oc_L5Vk0g"
+ x="108" y="480"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_Vs0JkdQSEdyk9oc_L5Vk0g" type="1005"
+ element="_Vs0JkNQSEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_Vs96kNQSEdyk9oc_L5Vk0g" type="4004"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_Vs0JktQSEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_Vs0Jk9QSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_Vs0JlNQSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_Vs0JldQSEdyk9oc_L5Vk0g" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_Vs0JltQSEdyk9oc_L5Vk0g"
+ x="288" y="480"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_XXN14NQSEdyk9oc_L5Vk0g" type="1001"
+ element="_XXEE4NQSEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_XXN15tQSEdyk9oc_L5Vk0g" type="4001">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_XXN159QSEdyk9oc_L5Vk0g"
+ y="5"/>
+ </children>
+ <styles xmi:type="notation:FontStyle" xmi:id="_XXN14dQSEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_XXN14tQSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_XXN149QSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_XXN15NQSEdyk9oc_L5Vk0g" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_XXN15dQSEdyk9oc_L5Vk0g"
+ x="612" y="324"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_XtTaoNQSEdyk9oc_L5Vk0g" type="1004"
+ element="_XtJpoNQSEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_XtTaptQSEdyk9oc_L5Vk0g" type="4003">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_XtTap9QSEdyk9oc_L5Vk0g"
+ y="5"/>
+ </children>
+ <styles xmi:type="notation:FontStyle" xmi:id="_XtTaodQSEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_XtTaotQSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_XtTao9QSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_XtTapNQSEdyk9oc_L5Vk0g" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_XtTapdQSEdyk9oc_L5Vk0g"
+ x="372" y="12"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_zLiRYdQSEdyk9oc_L5Vk0g" type="1002"
+ element="_zLiRYNQSEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_zLiRZ9QSEdyk9oc_L5Vk0g" type="4002"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_zLiRYtQSEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_zLiRY9QSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_zLiRZNQSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_zLiRZdQSEdyk9oc_L5Vk0g" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_zLiRZtQSEdyk9oc_L5Vk0g"
+ x="108" y="324"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_41-EodQSEdyk9oc_L5Vk0g" type="1002"
+ element="_41-EoNQSEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_41-Ep9QSEdyk9oc_L5Vk0g" type="4002"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_41-EotQSEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_41-Eo9QSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_41-EpNQSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_41-EpdQSEdyk9oc_L5Vk0g" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_41-EptQSEdyk9oc_L5Vk0g"
+ x="108" y="168"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_BI91kdQTEdyk9oc_L5Vk0g" type="1002"
+ element="_BI91kNQTEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_BI91l9QTEdyk9oc_L5Vk0g" type="4002"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_BI91ktQTEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_BI91k9QTEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_BI91lNQTEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_BI91ldQTEdyk9oc_L5Vk0g" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_BI91ltQTEdyk9oc_L5Vk0g"
+ x="360" y="48"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_GDJhANo8EdyzZqGyZ7hwdw" visible="false"
+ type="1009" element="_CWt3oNQSEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_GDTSANo8EdyzZqGyZ7hwdw" type="4008"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_GDJhAdo8EdyzZqGyZ7hwdw" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_GDJhAto8EdyzZqGyZ7hwdw"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_GDJhA9o8EdyzZqGyZ7hwdw"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_GDJhBNo8EdyzZqGyZ7hwdw" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_GDJhBdo8EdyzZqGyZ7hwdw"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_GEfk0No8EdyzZqGyZ7hwdw" type="1009"
+ element="_GEVz0No8EdyzZqGyZ7hwdw">
+ <children xmi:type="notation:Node" xmi:id="_GEfk1to8EdyzZqGyZ7hwdw" type="4008"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_GEfk0do8EdyzZqGyZ7hwdw" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_GEfk0to8EdyzZqGyZ7hwdw"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_GEfk09o8EdyzZqGyZ7hwdw"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_GEfk1No8EdyzZqGyZ7hwdw" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_GEfk1do8EdyzZqGyZ7hwdw"
+ x="408" y="228"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_GERT0d9JEdyXPePcD0t0WQ" type="1005"
+ element="_GERT0N9JEdyXPePcD0t0WQ">
+ <children xmi:type="notation:Node" xmi:id="_GERT199JEdyXPePcD0t0WQ" type="4004"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_GERT0t9JEdyXPePcD0t0WQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_GERT099JEdyXPePcD0t0WQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_GERT1N9JEdyXPePcD0t0WQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_GERT1d9JEdyXPePcD0t0WQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_GERT1t9JEdyXPePcD0t0WQ"
+ x="593" y="224"/>
+ </children>
+ <styles xmi:type="notation:PageStyle" xmi:id="_CDVBgdQSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:GuideStyle" xmi:id="_CDVBgtQSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_CDVBg9QSEdyk9oc_L5Vk0g"/>
+ <edges xmi:type="notation:Edge" xmi:id="_uMN3sdQSEdyk9oc_L5Vk0g" type="3001" element="_uMN3sNQSEdyk9oc_L5Vk0g"
+ source="_GCC55dQSEdyk9oc_L5Vk0g" target="_VJgBIdQSEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_uMN3ttQSEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_uMN3t9QSEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_uMN3stQSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_uMN3s9QSEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_uMN3tNQSEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_uMN3tdQSEdyk9oc_L5Vk0g"
+ points="[0, 43, -1, -44]$[0, 62, -1, -25]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_uMXosNQSEdyk9oc_L5Vk0g"
+ id="(0.44859812,0.18867925)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_uqwN0NQSEdyk9oc_L5Vk0g" type="3001" element="_uqnD4NQSEdyk9oc_L5Vk0g"
+ source="_VJgBIdQSEdyk9oc_L5Vk0g" target="_GCC53tQSEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_uqwN1dQSEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_uqwN1tQSEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_uqwN0dQSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_uqwN0tQSEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_uqwN09QSEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_uqwN1NQSEdyk9oc_L5Vk0g"
+ points="[-1, 25, 2, -72]$[-1, 71, 2, -26]"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_0ZYkkdQSEdyk9oc_L5Vk0g" type="3001" element="_0ZYkkNQSEdyk9oc_L5Vk0g"
+ source="_GCC519QSEdyk9oc_L5Vk0g" target="_zLiRYdQSEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_0ZYkltQSEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_0ZYkl9QSEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_0ZYkktQSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_0ZYkk9QSEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_0ZYklNQSEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_0ZYkldQSEdyk9oc_L5Vk0g"
+ points="[0, 41, -1, -56]$[0, 122, -1, 25]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_0ZYkmNQSEdyk9oc_L5Vk0g"
+ id="(0.44117647,0.2264151)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_0yFYcdQSEdyk9oc_L5Vk0g" type="3001" element="_0yFYcNQSEdyk9oc_L5Vk0g"
+ source="_zLiRYdQSEdyk9oc_L5Vk0g" target="_GCC55dQSEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_0yFYdtQSEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_0yFYd9QSEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_0yFYctQSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_0yFYc9QSEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_0yFYdNQSEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_0yFYddQSEdyk9oc_L5Vk0g"
+ points="[4, 25, 0, -60]$[4, 59, 0, -26]"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_1O0-0dQSEdyk9oc_L5Vk0g" type="3001" element="_1O0-0NQSEdyk9oc_L5Vk0g"
+ source="_GCC53tQSEdyk9oc_L5Vk0g" target="_zLiRYdQSEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_1O0-1tQSEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_1O0-19QSEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_1O0-0tQSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_1O0-09QSEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_1O0-1NQSEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_1O0-1dQSEdyk9oc_L5Vk0g"
+ points="[-37, 0, -33, 244]$[-82, 0, -78, 244]$[-82, -244, -78, 0]$[-13, -244, -9, 0]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_1O-IwNQSEdyk9oc_L5Vk0g"
+ id="(0.39784947,0.24528302)"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_1O-IwdQSEdyk9oc_L5Vk0g"
+ id="(0.18,0.42)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_17lXIdQSEdyk9oc_L5Vk0g" type="3001" element="_17lXINQSEdyk9oc_L5Vk0g"
+ source="_VJgBIdQSEdyk9oc_L5Vk0g" target="_Vs0JkdQSEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_17lXJtQSEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_17lXJ9QSEdyk9oc_L5Vk0g"
+ x="-18" y="-18"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_17lXItQSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_17lXI9QSEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_17lXJNQSEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_17lXJdQSEdyk9oc_L5Vk0g"
+ points="[25, -1, -107, -1]$[107, -1, -25, -1]"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_2b7EEdQSEdyk9oc_L5Vk0g" type="3001" element="_2b7EENQSEdyk9oc_L5Vk0g"
+ source="_Vs0JkdQSEdyk9oc_L5Vk0g" target="_GCC50NQSEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_2b7EFtQSEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_2b7EF9QSEdyk9oc_L5Vk0g"
+ x="-10" y="59"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_2b7EEtQSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_2b7EE9QSEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_2b7EFNQSEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_2b7EFdQSEdyk9oc_L5Vk0g"
+ points="[-1, -25, 0, 334]$[-1, -385, 0, -26]"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_5p6qEdQSEdyk9oc_L5Vk0g" type="3001" element="_5p6qENQSEdyk9oc_L5Vk0g"
+ source="_QjHr4dQSEdyk9oc_L5Vk0g" target="_41-EodQSEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_5p6qFtQSEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_5p6qF9QSEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_5p6qEtQSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_5p6qE9QSEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_5p6qFNQSEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_5p6qFdQSEdyk9oc_L5Vk0g"
+ points="[-1, 25, -1, -59]$[-1, 59, -1, -25]"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_5-H_gdQSEdyk9oc_L5Vk0g" type="3001" element="_5-H_gNQSEdyk9oc_L5Vk0g"
+ source="_41-EodQSEdyk9oc_L5Vk0g" target="_GCC519QSEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_5-H_htQSEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_5-H_h9QSEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_5-H_gtQSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_5-H_g9QSEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_5-H_hNQSEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_5-H_hdQSEdyk9oc_L5Vk0g"
+ points="[5, 25, 0, -35]$[3, 47, -2, -13]"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_5-RwgNQSEdyk9oc_L5Vk0g"
+ id="(0.4852941,0.24528302)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_6Ni7kNQSEdyk9oc_L5Vk0g" type="3001" element="_6NZKkNQSEdyk9oc_L5Vk0g"
+ source="_GCC50NQSEdyk9oc_L5Vk0g" target="_41-EodQSEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_6Ni7ldQSEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_6Ni7ltQSEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_6Ni7kdQSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_6Ni7ktQSEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_6Ni7k9QSEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_6Ni7lNQSEdyk9oc_L5Vk0g"
+ points="[-40, 6, 119, -19]$[-134, 21, 25, -4]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_6Ni7l9QSEdyk9oc_L5Vk0g"
+ id="(0.41237113,0.2264151)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_7Rg6AdQSEdyk9oc_L5Vk0g" type="3001" element="_7Rg6ANQSEdyk9oc_L5Vk0g"
+ source="_QjHr4dQSEdyk9oc_L5Vk0g" target="_GCC50NQSEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_7Rg6BtQSEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_7Rg6B9QSEdyk9oc_L5Vk0g"
+ x="-37" y="-18"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_7Rg6AtQSEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_7Rg6A9QSEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_7Rg6BNQSEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_7Rg6BdQSEdyk9oc_L5Vk0g"
+ points="[25, 0, -154, -97]$[172, 0, -7, -97]$[172, 71, -7, -26]"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_CbJ2MdQTEdyk9oc_L5Vk0g" type="3001" element="_CbJ2MNQTEdyk9oc_L5Vk0g"
+ source="_XtTaoNQSEdyk9oc_L5Vk0g" target="_BI91kdQTEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_CbJ2NtQTEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_CbJ2N9QTEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_CbJ2MtQTEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_CbJ2M9QTEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_CbJ2NNQTEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_CbJ2NdQTEdyk9oc_L5Vk0g"
+ points="[3, 10, -25, -58]$[3, 62, -25, -6]"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_C0dHANQTEdyk9oc_L5Vk0g" type="3001" element="_C0TWANQTEdyk9oc_L5Vk0g"
+ source="_BI91kdQTEdyk9oc_L5Vk0g" target="_QjHr4dQSEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_C0dHBdQTEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_C0dHBtQTEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_C0dHAdQTEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_C0dHAtQTEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_C0dHA9QTEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_C0dHBNQTEdyk9oc_L5Vk0g"
+ points="[-25, -6, 227, -42]$[-252, -6, 0, -42]$[-252, 11, 0, -25]"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_R8y_IdQTEdyk9oc_L5Vk0g" type="3001" element="_R8y_INQTEdyk9oc_L5Vk0g"
+ source="_GERT0d9JEdyXPePcD0t0WQ" target="_BI91kdQTEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_R8y_JtQTEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_R8y_J9QTEdyk9oc_L5Vk0g"
+ x="116" y="18"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_R8y_ItQTEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_R8y_I9QTEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_R8y_JNQTEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_R8y_JdQTEdyk9oc_L5Vk0g"
+ points="[0, -9, 232, 151]$[0, -160, 232, 0]$[-207, -160, 25, 0]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_P21aEN9JEdyXPePcD0t0WQ"
+ id="(0.48,0.18)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_TUsmMNQTEdyk9oc_L5Vk0g" type="3001" element="_TUi1MNQTEdyk9oc_L5Vk0g"
+ source="_GERT0d9JEdyXPePcD0t0WQ" target="_XXN14NQSEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_TUsmNdQTEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_TUsmNtQTEdyk9oc_L5Vk0g"
+ x="-4" y="-50"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_TUsmMdQTEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_TUsmMtQTEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_TUsmM9QTEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_TUsmNNQTEdyk9oc_L5Vk0g"
+ points="[2, 8, 0, -62]$[2, 38, 0, -32]$[2, 58, 0, -12]"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_GD5H4No8EdyzZqGyZ7hwdw" type="3001" element="_9A5M8NQSEdyk9oc_L5Vk0g"
+ source="_Vs0JkdQSEdyk9oc_L5Vk0g" target="_GDJhANo8EdyzZqGyZ7hwdw">
+ <children xmi:type="notation:Node" xmi:id="_GD5H5do8EdyzZqGyZ7hwdw" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_GD5H5to8EdyzZqGyZ7hwdw"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_GD5H4do8EdyzZqGyZ7hwdw"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_GD5H4to8EdyzZqGyZ7hwdw" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_GD5H49o8EdyzZqGyZ7hwdw" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_GD5H5No8EdyzZqGyZ7hwdw"
+ points="[0, 0, 0, 0]$[0, 0, 0, 0]"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_Q2HUUNo8EdyzZqGyZ7hwdw" type="3001" element="_Q1-KYNo8EdyzZqGyZ7hwdw"
+ source="_Vs0JkdQSEdyk9oc_L5Vk0g" target="_GEfk0No8EdyzZqGyZ7hwdw">
+ <children xmi:type="notation:Node" xmi:id="_Q2HUVdo8EdyzZqGyZ7hwdw" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_Q2HUVto8EdyzZqGyZ7hwdw"
+ x="2" y="63"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_Q2HUUdo8EdyzZqGyZ7hwdw"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_Q2HUUto8EdyzZqGyZ7hwdw" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_Q2HUU9o8EdyzZqGyZ7hwdw" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_Q2HUVNo8EdyzZqGyZ7hwdw"
+ points="[5, 0, -131, 263]$[128, 0, -8, 263]$[128, -222, -8, 41]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_Q2HUV9o8EdyzZqGyZ7hwdw"
+ id="(0.9,0.46)"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_Q2HUWNo8EdyzZqGyZ7hwdw"
+ id="(0.46564886,0.2264151)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_b_Mvgd9IEdyXPePcD0t0WQ" type="3001" element="_b_MvgN9IEdyXPePcD0t0WQ"
+ source="_GEfk0No8EdyzZqGyZ7hwdw" target="_GERT0d9JEdyXPePcD0t0WQ">
+ <children xmi:type="notation:Node" xmi:id="_b_Mvht9IEdyXPePcD0t0WQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_b_Mvh99IEdyXPePcD0t0WQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_b_Mvgt9IEdyXPePcD0t0WQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_b_Mvg99IEdyXPePcD0t0WQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_b_MvhN9IEdyXPePcD0t0WQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_b_Mvhd9IEdyXPePcD0t0WQ"
+ points="[38, 41, -134, -144]$[171, 160, -1, -25]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_b_WggN9IEdyXPePcD0t0WQ"
+ id="(0.48854962,0.2264151)"/>
+ </edges>
+ </notation:Diagram>
+</xmi:XMI>
diff --git a/praclib/temp/process.openup.base/capabilitypatterns/develop_solution/model.xmi b/praclib/temp/process.openup.base/capabilitypatterns/develop_solution/model.xmi
new file mode 100644
index 0000000..b22a161
--- /dev/null
+++ b/praclib/temp/process.openup.base/capabilitypatterns/develop_solution/model.xmi
@@ -0,0 +1,155 @@
+<?xml version="1.0" encoding="UTF-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.4/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.2.0" xmlns:epf="http://www.eclipse.org/epf"
+ epf:version="1.2.0">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_RZo_QdOFEdyqlogshP8l4g"
+ guid="_RZo_QdOFEdyqlogshP8l4g">
+ <resourceDescriptors xmi:id="_RZo_QtOFEdyqlogshP8l4g" id="-ux7ytJ8wsCQm5rzKYxNA7Q"
+ uri="content.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:ProcessComponent xmi:id="_RXGooNOFEdyqlogshP8l4g" name="develop_solution"
+ guid="_RXGooNOFEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_frOcQNOKEdyqlogshP8l4g"
+ name="design_solution" guid="_frOcQNOKEdyqlogshP8l4g" presentationName="Design the Solution"
+ superActivities="_RXGoodOFEdyqlogshP8l4g" additionallyPerformedBy="_frYNQdOKEdyqlogshP8l4g _frYNQtOKEdyqlogshP8l4g _frYNQ9OKEdyqlogshP8l4g _frYNRNOKEdyqlogshP8l4g"
+ mandatoryInput="_frh-QNOKEdyqlogshP8l4g _frh-QdOKEdyqlogshP8l4g" optionalInput="_frh-QtOKEdyqlogshP8l4g"
+ output="_frh-QtOKEdyqlogshP8l4g" performedPrimarilyBy="_frYNQNOKEdyqlogshP8l4g">
+ <Task href="uma://_Z2cK0LPPEduocbW-TPTq7A#_0fshwMlgEdmt3adZL5Dmdw"/>
+ <selectedSteps href="uma://_NrC20qeqEdmKDbQuyzCoqQ#_4Z7WYKuKEdmhFZtkg1nakg"/>
+ <selectedSteps href="uma://_NrC20qeqEdmKDbQuyzCoqQ#_--6tYKuKEdmhFZtkg1nakg"/>
+ <selectedSteps href="uma://_NrC20qeqEdmKDbQuyzCoqQ#_A_LU8KuLEdmhFZtkg1nakg"/>
+ <selectedSteps href="uma://_NrC20qeqEdmKDbQuyzCoqQ#_ENwJwKuLEdmhFZtkg1nakg"/>
+ <selectedSteps href="uma://_NrC20qeqEdmKDbQuyzCoqQ#_KNZYAKuLEdmhFZtkg1nakg"/>
+ <selectedSteps href="uma://_NrC20qeqEdmKDbQuyzCoqQ#_OGYbwKuLEdmhFZtkg1nakg"/>
+ <selectedSteps href="uma://_NrC20qeqEdmKDbQuyzCoqQ#_Ci7aYFixEdusJoWkvSRO9Q"/>
+ <selectedSteps href="uma://_NrC20qeqEdmKDbQuyzCoqQ#_mUVt8BfnEduD353bkQ4frw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_frYNQNOKEdyqlogshP8l4g"
+ name="developer" guid="_frYNQNOKEdyqlogshP8l4g" presentationName="Developer"
+ isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g" responsibleFor="_aJ1X4No7EdyzZqGyZ7hwdw _gX7xQtOKEdyqlogshP8l4g _frh-QtOKEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_frYNQdOKEdyqlogshP8l4g"
+ name="analyst" guid="_frYNQdOKEdyqlogshP8l4g" presentationName="Analyst" isPlanned="false"
+ superActivities="_RXGoodOFEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0VxJsMlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_frYNQtOKEdyqlogshP8l4g"
+ name="architect" guid="_frYNQtOKEdyqlogshP8l4g" presentationName="Architect"
+ isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0X9iEMlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_frYNQ9OKEdyqlogshP8l4g"
+ name="stakeholder" guid="_frYNQ9OKEdyqlogshP8l4g" presentationName="Stakeholder"
+ isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_dTa6gMAYEdqX-s4mWhkyqQ"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_frYNRNOKEdyqlogshP8l4g"
+ name="tester" guid="_frYNRNOKEdyqlogshP8l4g" presentationName="Tester" isPlanned="false"
+ superActivities="_RXGoodOFEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0ZM4MclgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_frh-QNOKEdyqlogshP8l4g"
+ name="technical_architecture_slot" guid="_frh-QNOKEdyqlogshP8l4g" presentationName="[Technical Architecture]"
+ isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_8OD-cLPTEduocbW-TPTq7A"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_frh-QdOKEdyqlogshP8l4g"
+ name="technical_specification_slot" guid="_frh-QdOKEdyqlogshP8l4g" presentationName="[Technical Specification]"
+ isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_i3vkoLS-EduDY8LNbMCDBA"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_frh-QtOKEdyqlogshP8l4g"
+ name="design" guid="_frh-QtOKEdyqlogshP8l4g" presentationName="Design" isPlanned="false"
+ superActivities="_RXGoodOFEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_Z2cK0LPPEduocbW-TPTq7A#_0WuL8slgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_gXo2UNOKEdyqlogshP8l4g"
+ name="implement_developer_tests" guid="_gXo2UNOKEdyqlogshP8l4g" presentationName="Implement Developer Tests"
+ superActivities="_RXGoodOFEdyqlogshP8l4g" additionallyPerformedBy="_frYNRNOKEdyqlogshP8l4g"
+ mandatoryInput="_gX7xQNOKEdyqlogshP8l4g" optionalInput="_gX7xQdOKEdyqlogshP8l4g"
+ output="_gX7xQtOKEdyqlogshP8l4g" performedPrimarilyBy="_frYNQNOKEdyqlogshP8l4g">
+ <Task href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_znlIcJR9EdyVKbgqUOtqQA"/>
+ <selectedSteps href="uma://-UW-yTFk3AppqcGGU-Px63A#_C_j_EJR-EdyVKbgqUOtqQA"/>
+ <selectedSteps href="uma://-UW-yTFk3AppqcGGU-Px63A#_Es64wJR-EdyVKbgqUOtqQA"/>
+ <selectedSteps href="uma://-UW-yTFk3AppqcGGU-Px63A#_Fm4moJR-EdyVKbgqUOtqQA"/>
+ <selectedSteps href="uma://-UW-yTFk3AppqcGGU-Px63A#_GZaPwJR-EdyVKbgqUOtqQA"/>
+ <selectedSteps href="uma://-UW-yTFk3AppqcGGU-Px63A#_IMxq0JR-EdyVKbgqUOtqQA"/>
+ <selectedSteps href="uma://-UW-yTFk3AppqcGGU-Px63A#_JAiqEJR-EdyVKbgqUOtqQA"/>
+ <selectedSteps href="uma://-UW-yTFk3AppqcGGU-Px63A#_KkDrQJR-EdyVKbgqUOtqQA"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_gX7xQNOKEdyqlogshP8l4g"
+ name="software_implementation_slot" guid="_gX7xQNOKEdyqlogshP8l4g" presentationName="[Software Implementation]"
+ isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_Vux8UEfUEdyiPI8btkmvmw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_gX7xQdOKEdyqlogshP8l4g"
+ name="software_design_slot" guid="_gX7xQdOKEdyqlogshP8l4g" presentationName="[Software Design]"
+ isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_IcQOUEqdEdyi3_jfs__bIQ"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_gX7xQtOKEdyqlogshP8l4g"
+ name="developer_test" guid="_gX7xQtOKEdyqlogshP8l4g" presentationName="Developer Test"
+ isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_kh9FcJ02EdyQ3oTO93enUw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_hVe-oNOKEdyqlogshP8l4g"
+ name="implement_solution" guid="_hVe-oNOKEdyqlogshP8l4g" presentationName="Implement Solution"
+ superActivities="_RXGoodOFEdyqlogshP8l4g" additionallyPerformedBy="_frYNQ9OKEdyqlogshP8l4g _frYNRNOKEdyqlogshP8l4g"
+ mandatoryInput="_gX7xQdOKEdyqlogshP8l4g _frh-QdOKEdyqlogshP8l4g" optionalInput="_gX7xQNOKEdyqlogshP8l4g _gX7xQtOKEdyqlogshP8l4g"
+ output="_gX7xQNOKEdyqlogshP8l4g _frh-QdOKEdyqlogshP8l4g" performedPrimarilyBy="_frYNQNOKEdyqlogshP8l4g">
+ <Task href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_Ht-z8JfJEdyZkIR-s-Y8wQ"/>
+ <selectedSteps href="uma://-UaDGd7K2rQIFMwCrDuqQKQ#_RiBg4JfJEdyZkIR-s-Y8wQ"/>
+ <selectedSteps href="uma://-UaDGd7K2rQIFMwCrDuqQKQ#_SW1pAJfJEdyZkIR-s-Y8wQ"/>
+ <selectedSteps href="uma://-UaDGd7K2rQIFMwCrDuqQKQ#_IVaTAJ-uEdyHNcWzRYqQMg"/>
+ <selectedSteps href="uma://-UaDGd7K2rQIFMwCrDuqQKQ#_TadCIJfJEdyZkIR-s-Y8wQ"/>
+ <selectedSteps href="uma://-UaDGd7K2rQIFMwCrDuqQKQ#_WpB28JfJEdyZkIR-s-Y8wQ"/>
+ <selectedSteps href="uma://-UaDGd7K2rQIFMwCrDuqQKQ#_XjAL4JfJEdyZkIR-s-Y8wQ"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_iRZNQNOKEdyqlogshP8l4g"
+ name="run_developer_tests" guid="_iRZNQNOKEdyqlogshP8l4g" presentationName="Run Developer Tests"
+ superActivities="_RXGoodOFEdyqlogshP8l4g" mandatoryInput="_gX7xQNOKEdyqlogshP8l4g _gX7xQtOKEdyqlogshP8l4g"
+ output="_iRiXMNOKEdyqlogshP8l4g" performedPrimarilyBy="_frYNQNOKEdyqlogshP8l4g">
+ <Task href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_R7atwJfIEdyZkIR-s-Y8wQ"/>
+ <selectedSteps href="uma://-H6ob8eA7gz_mOsk8ulSFMQ#_gjLBUJfIEdyZkIR-s-Y8wQ"/>
+ <selectedSteps href="uma://-H6ob8eA7gz_mOsk8ulSFMQ#_haRocJfIEdyZkIR-s-Y8wQ"/>
+ <selectedSteps href="uma://-H6ob8eA7gz_mOsk8ulSFMQ#_itj1QJfIEdyZkIR-s-Y8wQ"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_iRiXMNOKEdyqlogshP8l4g"
+ name="technical_test_results_slot" guid="_iRiXMNOKEdyqlogshP8l4g" presentationName="[Technical Test Results]"
+ isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_fahB0EfUEdyiPI8btkmvmw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_aJ1X4No7EdyzZqGyZ7hwdw"
+ name="build" guid="_aJ1X4No7EdyzZqGyZ7hwdw" presentationName="Build" isPlanned="false"
+ superActivities="_RXGoodOFEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_D-ExQMktEdygFZkm1d5NtQ#_0YuXEMlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_Dlo8wNo8EdyzZqGyZ7hwdw"
+ name="integrate_and_create_build" guid="_Dlo8wNo8EdyzZqGyZ7hwdw" presentationName="Integrate and Create Build"
+ superActivities="_RXGoodOFEdyqlogshP8l4g" mandatoryInput="_Dlo8wdo8EdyzZqGyZ7hwdw _gX7xQNOKEdyqlogshP8l4g"
+ output="_aJ1X4No7EdyzZqGyZ7hwdw" performedPrimarilyBy="_frYNQNOKEdyqlogshP8l4g">
+ <Task href="uma://_D-ExQMktEdygFZkm1d5NtQ#_kkZBgJOKEdyaRbFYa4AN4A"/>
+ <selectedSteps href="uma://-01L_eCnHjKmBPsGcdk8XTg#_kkZBhZOKEdyaRbFYa4AN4A"/>
+ <selectedSteps href="uma://-01L_eCnHjKmBPsGcdk8XTg#_kkZBgpOKEdyaRbFYa4AN4A"/>
+ <selectedSteps href="uma://-01L_eCnHjKmBPsGcdk8XTg#_kkZBhJOKEdyaRbFYa4AN4A"/>
+ <selectedSteps href="uma://-01L_eCnHjKmBPsGcdk8XTg#_kkZBgZOKEdyaRbFYa4AN4A"/>
+ <selectedSteps href="uma://-01L_eCnHjKmBPsGcdk8XTg#_kkZBg5OKEdyaRbFYa4AN4A"/>
+ <selectedSteps href="uma://-01L_eCnHjKmBPsGcdk8XTg#_kkZBhpOKEdyaRbFYa4AN4A"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_Dlo8wdo8EdyzZqGyZ7hwdw"
+ name="test_script" guid="_Dlo8wdo8EdyzZqGyZ7hwdw" presentationName="Test Script"
+ isPlanned="false" superActivities="_RXGoodOFEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZfMEMlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_RXGoodOFEdyqlogshP8l4g"
+ name="develop_solution" guid="_RXGoodOFEdyqlogshP8l4g" briefDescription="Design, implement, test, and integrate the solution for a requirement within a given context."
+ presentationName="Develop Solution Increment" breakdownElements="_frOcQNOKEdyqlogshP8l4g _frYNQNOKEdyqlogshP8l4g _frYNQdOKEdyqlogshP8l4g _frYNQtOKEdyqlogshP8l4g _frYNQ9OKEdyqlogshP8l4g _frYNRNOKEdyqlogshP8l4g _frh-QNOKEdyqlogshP8l4g _frh-QdOKEdyqlogshP8l4g _frh-QtOKEdyqlogshP8l4g _gXo2UNOKEdyqlogshP8l4g _gX7xQNOKEdyqlogshP8l4g _gX7xQdOKEdyqlogshP8l4g _gX7xQtOKEdyqlogshP8l4g _hVe-oNOKEdyqlogshP8l4g _iRZNQNOKEdyqlogshP8l4g _iRiXMNOKEdyqlogshP8l4g _aJ1X4No7EdyzZqGyZ7hwdw _Dlo8wNo8EdyzZqGyZ7hwdw _Dlo8wdo8EdyzZqGyZ7hwdw">
+ <presentation xmi:id="-ux7ytJ8wsCQm5rzKYxNA7Q" href="uma://-ux7ytJ8wsCQm5rzKYxNA7Q#-ux7ytJ8wsCQm5rzKYxNA7Q"/>
+ <defaultContext href="uma://_8Pz_Kdo7EdyzZqGyZ7hwdw#_gExDwNQxEdyk9oc_L5Vk0g"/>
+ <validContext href="uma://_8Pz_Kdo7EdyzZqGyZ7hwdw#_gExDwNQxEdyk9oc_L5Vk0g"/>
+ </process>
+ </org.eclipse.epf.uma:ProcessComponent>
+</xmi:XMI>
diff --git a/praclib/temp/process.openup.base/capabilitypatterns/elaboration_phase_iteration/content.xmi b/praclib/temp/process.openup.base/capabilitypatterns/elaboration_phase_iteration/content.xmi
new file mode 100644
index 0000000..7ae4c14
--- /dev/null
+++ b/praclib/temp/process.openup.base/capabilitypatterns/elaboration_phase_iteration/content.xmi
@@ -0,0 +1,87 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:ProcessDescription 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="-TceMuWXdZ1TV2gERYKpA5g"
+ name="elaboration_phase_iteration,_aUsVEdONEdyqlogshP8l4g" guid="-TceMuWXdZ1TV2gERYKpA5g"
+ version="7.2.0">
+ <mainDescription><p>
+ Most activities during a typical iteration in Elaboration phase happen in parallel. Essentially, the main objectives
+ for Elaboration are related to better understanding the requirements, creating and establishing a baseline of the
+ architecture for the system, and mitigating top-priority risks.
+</p>
+<p>
+ The following table summarizes the&nbsp;Elaboration phase objectives and&nbsp;what activities address each objective:
+</p>
+<p align="center">
+ <strong>Elaboration phase objectives and activities</strong>
+</p><br />
+<br />
+<table cellspacing="0" cellpadding="0" width="648" align="center" border="1">
+ <tbody>
+ <tr>
+ <td class="Normal" valign="top" width="300">
+ <p style="TEXT-ALIGN: justify">
+ <b>Phase objectives</b>
+ </p>
+ </td>
+ <td class="Normal" valign="top" width="348">
+ <p style="TEXT-ALIGN: justify">
+ <b>Activities that address objectives</b>
+ </p>
+ </td>
+ </tr>
+ <tr>
+ <td class="Normal" valign="top" width="300">
+ Get a more detailed understanding of the requirements
+ </td>
+ <td class="Normal" valign="top" width="348">
+ <p>
+ <a class="elementLink"
+ href="./../../process.openup.base/capabilitypatterns/identify_and_refine_requirements_7FA6CB14.html"
+ guid="_xxcpgdOEEdyqlogshP8l4g">Identify and Refine Requirements</a>
+ </p>
+ </td>
+ </tr>
+ <tr>
+ <td class="Normal" valign="top" width="300">
+ Design, implement, validate, and baseline an architecture
+ </td>
+ <td class="Normal" valign="top" width="348">
+ <p style="TEXT-ALIGN: justify">
+ <a class="elementLink"
+ href="./../../process.openup.base/capabilitypatterns/develop_architecture_C7BBA35B.html"
+ guid="_KaeNsdOFEdyqlogshP8l4g">Develop the Architecture</a>
+ </p>
+ <p style="TEXT-ALIGN: justify">
+ <a class="elementLink"
+ href="./../../process.openup.base/capabilitypatterns/develop_solution_4FBB0E6E.html"
+ guid="_RXGoodOFEdyqlogshP8l4g">Develop Solution Increment</a>
+ </p>
+ <p style="TEXT-ALIGN: justify">
+ <a class="elementLink"
+ href="./../../process.openup.base/capabilitypatterns/test_solution_D16D88FC.html"
+ guid="_buG4sdOFEdyqlogshP8l4g">Test Solution</a>
+ </p>
+ </td>
+ </tr>
+ <tr>
+ <td class="Normal" valign="top" width="300">
+ Mitigate essential risks, and produce accurate schedule and cost estimates
+ </td>
+ <td class="Normal" valign="top" width="348">
+ <a class="elementLink"
+ href="./../../process.openup.base/capabilitypatterns/plan_manage_iteration_F9713A62.html"
+ guid="_oZgCsdOEEdyqlogshP8l4g">Plan and Manage Iteration</a><br />
+ </td>
+ </tr>
+ </tbody>
+</table><br />
+<br /></mainDescription>
+ <alternatives>There will be iterations when projects risks are being addressed by creating software, but they may not be architecturally
+significant. In this case, <a class="elementLinkWithType" href="./resources/develop_solution_633E2E80.html"
+guid="_h2-iAfimEdmugcVr9AdHjQ" >Capability Pattern: Develop Solution Increment</a> will be performed outside the context of
+the architecture. For the most part, Develop Solution will be performed in the context of <a class="elementLinkWithType"
+href="./resources/develop_architecture_AF0A71D5.html" guid="_0sx7islgEdmt3adZL5Dmdw">Capability Pattern: Develop the
+Architecture</a> during the Elaboration phase.</alternatives>
+</org.eclipse.epf.uma:ProcessDescription>
diff --git a/praclib/temp/process.openup.base/capabilitypatterns/elaboration_phase_iteration/diagram.xmi b/praclib/temp/process.openup.base/capabilitypatterns/elaboration_phase_iteration/diagram.xmi
new file mode 100644
index 0000000..e139ae4
--- /dev/null
+++ b/praclib/temp/process.openup.base/capabilitypatterns/elaboration_phase_iteration/diagram.xmi
@@ -0,0 +1,433 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xmi:XMI xmi:version="2.0"
+ xmlns:xmi="http://www.omg.org/XMI" xmlns:ecore="http://www.eclipse.org/emf/2002/Ecore"
+ xmlns:notation="http://www.eclipse.org/gmf/runtime/1.0.1/notation" xmlns:uml="http://www.eclipse.org/uml2/2.1.0/UML">
+ <uml:Activity xmi:id="_jgBTYNQVEdyk9oc_L5Vk0g" name="elaboration_phase_iteration">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_jgBTYdQVEdyk9oc_L5Vk0g" source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_jgBTYtQVEdyk9oc_L5Vk0g"
+ key="uri" value="uma://_aUsVENONEdyqlogshP8l4g#_aUsVEdONEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_jgBTY9QVEdyk9oc_L5Vk0g"
+ key="type" value="Activity"/>
+ </eAnnotations>
+ <node xmi:type="uml:StructuredActivityNode" xmi:id="_jhhIMNQVEdyk9oc_L5Vk0g" name="Plan and Manage Iteration"
+ outgoing="__cMDUNQVEdyk9oc_L5Vk0g" incoming="_-4L-YNQVEdyk9oc_L5Vk0g">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_jhhIMdQVEdyk9oc_L5Vk0g"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_jhhIMtQVEdyk9oc_L5Vk0g"
+ key="uri" value="uma://_aUsVENONEdyqlogshP8l4g#_XayTQdOOEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_jhhIM9QVEdyk9oc_L5Vk0g"
+ key="type" value="Activity"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:StructuredActivityNode" xmi:id="_jhhINNQVEdyk9oc_L5Vk0g" name="Identify and Refine Requirements"
+ outgoing="_79wNkNQVEdyk9oc_L5Vk0g" incoming="_7l_04NQVEdyk9oc_L5Vk0g">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_jhhINdQVEdyk9oc_L5Vk0g"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_jhhINtQVEdyk9oc_L5Vk0g"
+ key="uri" value="uma://_aUsVENONEdyqlogshP8l4g#_YwLY4dOOEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_jhhIN9QVEdyk9oc_L5Vk0g"
+ key="type" value="Activity"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:StructuredActivityNode" xmi:id="_jhhIONQVEdyk9oc_L5Vk0g" name="Develop the Architecture"
+ outgoing="_9aEakNQVEdyk9oc_L5Vk0g" incoming="_8bU6YNQVEdyk9oc_L5Vk0g">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_jhhIOdQVEdyk9oc_L5Vk0g"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_jhhIOtQVEdyk9oc_L5Vk0g"
+ key="uri" value="uma://_aUsVENONEdyqlogshP8l4g#_aSrtcdOOEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_jhhIO9QVEdyk9oc_L5Vk0g"
+ key="type" value="Activity"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:StructuredActivityNode" xmi:id="_jhhIPNQVEdyk9oc_L5Vk0g" name="Develop Solution Increment"
+ outgoing="_-UL5cNQVEdyk9oc_L5Vk0g" incoming="_97r54NQVEdyk9oc_L5Vk0g">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_jhhIPdQVEdyk9oc_L5Vk0g"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_jhhIPtQVEdyk9oc_L5Vk0g"
+ key="uri" value="uma://_aUsVENONEdyqlogshP8l4g#_eyv_UdOOEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_jhhIP9QVEdyk9oc_L5Vk0g"
+ key="type" value="Activity"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:StructuredActivityNode" xmi:id="_jhhIQNQVEdyk9oc_L5Vk0g" name="Test Solution"
+ outgoing="_AqwvQNQWEdyk9oc_L5Vk0g" incoming="_AUNQcNQWEdyk9oc_L5Vk0g">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_jhhIQdQVEdyk9oc_L5Vk0g"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_jhhIQtQVEdyk9oc_L5Vk0g"
+ key="uri" value="uma://_aUsVENONEdyqlogshP8l4g#_f4VuYdOOEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_jhhIQ9QVEdyk9oc_L5Vk0g"
+ key="type" value="Activity"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:StructuredActivityNode" xmi:id="_jhhIRNQVEdyk9oc_L5Vk0g" name="Ongoing Tasks"
+ outgoing="_BcXLUNQWEdyk9oc_L5Vk0g" incoming="_BFgKgNQWEdyk9oc_L5Vk0g">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_jhhIRdQVEdyk9oc_L5Vk0g"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_jhhIRtQVEdyk9oc_L5Vk0g"
+ key="uri" value="uma://_aUsVENONEdyqlogshP8l4g#_g8cPsdOOEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_jhhIR9QVEdyk9oc_L5Vk0g"
+ key="type" value="Activity"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:InitialNode" xmi:id="_0CSL0NQVEdyk9oc_L5Vk0g" outgoing="_6J-i0NQVEdyk9oc_L5Vk0g"/>
+ <node xmi:type="uml:ActivityFinalNode" xmi:id="_0b1UQNQVEdyk9oc_L5Vk0g" incoming="_65xoENQVEdyk9oc_L5Vk0g"/>
+ <node xmi:type="uml:ForkNode" xmi:id="_1hvzcNQVEdyk9oc_L5Vk0g" outgoing="_7l_04NQVEdyk9oc_L5Vk0g _8bU6YNQVEdyk9oc_L5Vk0g _97r54NQVEdyk9oc_L5Vk0g _-4L-YNQVEdyk9oc_L5Vk0g _AUNQcNQWEdyk9oc_L5Vk0g _BFgKgNQWEdyk9oc_L5Vk0g"
+ incoming="_6J-i0NQVEdyk9oc_L5Vk0g"/>
+ <node xmi:type="uml:JoinNode" xmi:id="_2GpQQNQVEdyk9oc_L5Vk0g" outgoing="_65xoENQVEdyk9oc_L5Vk0g"
+ incoming="_79wNkNQVEdyk9oc_L5Vk0g _9aEakNQVEdyk9oc_L5Vk0g _-UL5cNQVEdyk9oc_L5Vk0g __cMDUNQVEdyk9oc_L5Vk0g _AqwvQNQWEdyk9oc_L5Vk0g _BcXLUNQWEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_6J-i0NQVEdyk9oc_L5Vk0g" source="_0CSL0NQVEdyk9oc_L5Vk0g"
+ target="_1hvzcNQVEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_65xoENQVEdyk9oc_L5Vk0g" source="_2GpQQNQVEdyk9oc_L5Vk0g"
+ target="_0b1UQNQVEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_7l_04NQVEdyk9oc_L5Vk0g" source="_1hvzcNQVEdyk9oc_L5Vk0g"
+ target="_jhhINNQVEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_79wNkNQVEdyk9oc_L5Vk0g" source="_jhhINNQVEdyk9oc_L5Vk0g"
+ target="_2GpQQNQVEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_8bU6YNQVEdyk9oc_L5Vk0g" source="_1hvzcNQVEdyk9oc_L5Vk0g"
+ target="_jhhIONQVEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_9aEakNQVEdyk9oc_L5Vk0g" source="_jhhIONQVEdyk9oc_L5Vk0g"
+ target="_2GpQQNQVEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_97r54NQVEdyk9oc_L5Vk0g" source="_1hvzcNQVEdyk9oc_L5Vk0g"
+ target="_jhhIPNQVEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_-UL5cNQVEdyk9oc_L5Vk0g" source="_jhhIPNQVEdyk9oc_L5Vk0g"
+ target="_2GpQQNQVEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_-4L-YNQVEdyk9oc_L5Vk0g" source="_1hvzcNQVEdyk9oc_L5Vk0g"
+ target="_jhhIMNQVEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="__cMDUNQVEdyk9oc_L5Vk0g" source="_jhhIMNQVEdyk9oc_L5Vk0g"
+ target="_2GpQQNQVEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_AUNQcNQWEdyk9oc_L5Vk0g" source="_1hvzcNQVEdyk9oc_L5Vk0g"
+ target="_jhhIQNQVEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_AqwvQNQWEdyk9oc_L5Vk0g" source="_jhhIQNQVEdyk9oc_L5Vk0g"
+ target="_2GpQQNQVEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_BFgKgNQWEdyk9oc_L5Vk0g" source="_1hvzcNQVEdyk9oc_L5Vk0g"
+ target="_jhhIRNQVEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_BcXLUNQWEdyk9oc_L5Vk0g" source="_jhhIRNQVEdyk9oc_L5Vk0g"
+ target="_2GpQQNQVEdyk9oc_L5Vk0g"/>
+ </uml:Activity>
+ <notation:Diagram xmi:id="_jgBTZNQVEdyk9oc_L5Vk0g" type="AD" element="_jgBTYNQVEdyk9oc_L5Vk0g"
+ name="elaboration_phase_iteration" measurementUnit="Pixel">
+ <children xmi:type="notation:Node" xmi:id="_qF5bMNQVEdyk9oc_L5Vk0g" type="1007"
+ element="_jhhIMNQVEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_qF5bNtQVEdyk9oc_L5Vk0g" type="4005"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_qF5bMdQVEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_qF5bMtQVEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_qF5bM9QVEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_qF5bNNQVEdyk9oc_L5Vk0g" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_qF5bNdQVEdyk9oc_L5Vk0g"
+ x="456" y="156"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_qF5bN9QVEdyk9oc_L5Vk0g" type="1007"
+ element="_jhhINNQVEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_qF5bPdQVEdyk9oc_L5Vk0g" type="4005"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_qF5bONQVEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_qF5bOdQVEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_qF5bOtQVEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_qF5bO9QVEdyk9oc_L5Vk0g" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_qF5bPNQVEdyk9oc_L5Vk0g"
+ x="36" y="156"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_qF5bPtQVEdyk9oc_L5Vk0g" type="1007"
+ element="_jhhIONQVEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_qF5bRNQVEdyk9oc_L5Vk0g" type="4005"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_qF5bP9QVEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_qF5bQNQVEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_qF5bQdQVEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_qF5bQtQVEdyk9oc_L5Vk0g" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_qF5bQ9QVEdyk9oc_L5Vk0g"
+ x="180" y="204"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_qF5bRdQVEdyk9oc_L5Vk0g" type="1007"
+ element="_jhhIPNQVEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_qF5bS9QVEdyk9oc_L5Vk0g" type="4005"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_qF5bRtQVEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_qF5bR9QVEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_qF5bSNQVEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_qF5bSdQVEdyk9oc_L5Vk0g" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_qF5bStQVEdyk9oc_L5Vk0g"
+ x="288" y="240"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_qF5bTNQVEdyk9oc_L5Vk0g" type="1007"
+ element="_jhhIQNQVEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_qF5bUtQVEdyk9oc_L5Vk0g" type="4005"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_qF5bTdQVEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_qF5bTtQVEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_qF5bT9QVEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_qF5bUNQVEdyk9oc_L5Vk0g" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_qF5bUdQVEdyk9oc_L5Vk0g"
+ x="408" y="300"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_qF5bU9QVEdyk9oc_L5Vk0g" type="1007"
+ element="_jhhIRNQVEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_qF5bWdQVEdyk9oc_L5Vk0g" type="4005"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_qF5bVNQVEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_qF5bVdQVEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_qF5bVtQVEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_qF5bV9QVEdyk9oc_L5Vk0g" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_qF5bWNQVEdyk9oc_L5Vk0g"
+ x="576" y="228"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_0CSL0dQVEdyk9oc_L5Vk0g" type="1004"
+ element="_0CSL0NQVEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_0CSL19QVEdyk9oc_L5Vk0g" type="4003">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_0CSL2NQVEdyk9oc_L5Vk0g"
+ y="5"/>
+ </children>
+ <styles xmi:type="notation:FontStyle" xmi:id="_0CSL0tQVEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_0CSL09QVEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_0CSL1NQVEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_0CSL1dQVEdyk9oc_L5Vk0g" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_0CSL1tQVEdyk9oc_L5Vk0g"
+ x="343" y="56"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_0b1UQdQVEdyk9oc_L5Vk0g" type="1001"
+ element="_0b1UQNQVEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_0b1UR9QVEdyk9oc_L5Vk0g" type="4001">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_0b1USNQVEdyk9oc_L5Vk0g"
+ y="5"/>
+ </children>
+ <styles xmi:type="notation:FontStyle" xmi:id="_0b1UQtQVEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_0b1UQ9QVEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_0b1URNQVEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_0b1URdQVEdyk9oc_L5Vk0g" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_0b1URtQVEdyk9oc_L5Vk0g"
+ x="347" y="419"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_1hvzcdQVEdyk9oc_L5Vk0g" type="1003"
+ element="_1hvzcNQVEdyk9oc_L5Vk0g">
+ <styles xmi:type="notation:FontStyle" xmi:id="_1hvzctQVEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_1hvzc9QVEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_1hvzdNQVEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_1hvzddQVEdyk9oc_L5Vk0g" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_1hvzdtQVEdyk9oc_L5Vk0g"
+ x="36" y="108" width="637"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_2GpQQdQVEdyk9oc_L5Vk0g" type="1006"
+ element="_2GpQQNQVEdyk9oc_L5Vk0g">
+ <styles xmi:type="notation:FontStyle" xmi:id="_2GpQQtQVEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_2GpQQ9QVEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_2GpQRNQVEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_2GpQRdQVEdyk9oc_L5Vk0g" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_2GpQRtQVEdyk9oc_L5Vk0g"
+ x="36" y="372" width="637"/>
+ </children>
+ <styles xmi:type="notation:PageStyle" xmi:id="_jgBTZdQVEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:GuideStyle" xmi:id="_jgBTZtQVEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_jgBTZ9QVEdyk9oc_L5Vk0g"/>
+ <edges xmi:type="notation:Edge" xmi:id="_6J-i0dQVEdyk9oc_L5Vk0g" type="3001" element="_6J-i0NQVEdyk9oc_L5Vk0g"
+ source="_0CSL0dQVEdyk9oc_L5Vk0g" target="_1hvzcdQVEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_6J-i1tQVEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_6J-i19QVEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_6J-i0tQVEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_6J-i09QVEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_6J-i1NQVEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_6J-i1dQVEdyk9oc_L5Vk0g"
+ points="[1, 10, 0, -36]$[1, 42, 0, -4]"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_65xoEdQVEdyk9oc_L5Vk0g" type="3001" element="_65xoENQVEdyk9oc_L5Vk0g"
+ source="_2GpQQdQVEdyk9oc_L5Vk0g" target="_0b1UQdQVEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_65xoFtQVEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_65xoF9QVEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_65xoEtQVEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_65xoE9QVEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_65xoFNQVEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_65xoFdQVEdyk9oc_L5Vk0g"
+ points="[0, 4, -5, -51]$[-7, 57, -12, 2]"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_7l_04dQVEdyk9oc_L5Vk0g" type="3001" element="_7l_04NQVEdyk9oc_L5Vk0g"
+ source="_1hvzcdQVEdyk9oc_L5Vk0g" target="_qF5bN9QVEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_7l_05tQVEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_7l_059QVEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_7l_04tQVEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_7l_049QVEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_7l_05NQVEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_7l_05dQVEdyk9oc_L5Vk0g"
+ points="[0, 5, 0, -52]$[-3, 45, -3, -12]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_7l_06NQVEdyk9oc_L5Vk0g"
+ id="(0.1255887,0.375)"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_7l_06dQVEdyk9oc_L5Vk0g"
+ id="(0.4790419,0.2264151)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_79wNkdQVEdyk9oc_L5Vk0g" type="3001" element="_79wNkNQVEdyk9oc_L5Vk0g"
+ source="_qF5bN9QVEdyk9oc_L5Vk0g" target="_2GpQQdQVEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_79wNltQVEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_79wNl9QVEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_79wNktQVEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_79wNk9QVEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_79wNlNQVEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_79wNldQVEdyk9oc_L5Vk0g"
+ points="[0, 27, 0, -166]$[-83, 193, -83, 0]"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_79wNmNQVEdyk9oc_L5Vk0g"
+ id="(0.13029827,0.375)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_8bU6YdQVEdyk9oc_L5Vk0g" type="3001" element="_8bU6YNQVEdyk9oc_L5Vk0g"
+ source="_1hvzcdQVEdyk9oc_L5Vk0g" target="_qF5bPtQVEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_8bU6ZtQVEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_8bU6Z9QVEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_8bU6YtQVEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_8bU6Y9QVEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_8bU6ZNQVEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_8bU6ZdQVEdyk9oc_L5Vk0g"
+ points="[-4, 4, 107, -114]$[-110, 92, 1, -26]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_o8hmMNUDEdylRpA9TBY1SQ"
+ id="(0.31711146,0.125)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_9aEakdQVEdyk9oc_L5Vk0g" type="3001" element="_9aEakNQVEdyk9oc_L5Vk0g"
+ source="_qF5bPtQVEdyk9oc_L5Vk0g" target="_2GpQQdQVEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_9aEaltQVEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_9aEal9QVEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_9aEaktQVEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_9aEak9QVEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_9aEalNQVEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_9aEaldQVEdyk9oc_L5Vk0g"
+ points="[-8, 27, -119, -119]$[-207, 144, -318, -2]"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_peWg4NUDEdylRpA9TBY1SQ"
+ id="(0.3233909,0.125)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_97r54dQVEdyk9oc_L5Vk0g" type="3001" element="_97r54NQVEdyk9oc_L5Vk0g"
+ source="_1hvzcdQVEdyk9oc_L5Vk0g" target="_qF5bRdQVEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_97r55tQVEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_97r559QVEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_97r54tQVEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_97r549QVEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_97r55NQVEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_97r55dQVEdyk9oc_L5Vk0g"
+ points="[-2, 4, 0, -149]$[-6, 140, -4, -13]"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_97r56NQVEdyk9oc_L5Vk0g"
+ id="(0.46715328,0.24528302)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_-UL5cdQVEdyk9oc_L5Vk0g" type="3001" element="_-UL5cNQVEdyk9oc_L5Vk0g"
+ source="_qF5bRdQVEdyk9oc_L5Vk0g" target="_2GpQQdQVEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_-UL5dtQVEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_-UL5d9QVEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_-UL5ctQVEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_-UL5c9QVEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_-UL5dNQVEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_-UL5ddQVEdyk9oc_L5Vk0g"
+ points="[6, 27, 8, -71]$[317, 96, 319, -2]"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_-4L-YdQVEdyk9oc_L5Vk0g" type="3001" element="_-4L-YNQVEdyk9oc_L5Vk0g"
+ source="_1hvzcdQVEdyk9oc_L5Vk0g" target="_qF5bMNQVEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_-4L-ZtQVEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_-4L-Z9QVEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_-4L-YtQVEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_-4L-Y9QVEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_-4L-ZNQVEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_-4L-ZdQVEdyk9oc_L5Vk0g"
+ points="[9, 4, -134, -66]$[143, 44, 0, -26]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_MUM3kNQWEdyk9oc_L5Vk0g"
+ id="(0.7566719,0.125)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="__cMDUdQVEdyk9oc_L5Vk0g" type="3001" element="__cMDUNQVEdyk9oc_L5Vk0g"
+ source="_qF5bMNQVEdyk9oc_L5Vk0g" target="_2GpQQdQVEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="__cMDVtQVEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="__cMDV9QVEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="__cMDUtQVEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="__cMDU9QVEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="__cMDVNQVEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="__cMDVdQVEdyk9oc_L5Vk0g"
+ points="[1, 27, -9, -164]$[61, 190, 51, -1]"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="__cMDWNQVEdyk9oc_L5Vk0g"
+ id="(0.75981164,0.125)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_AUNQcdQWEdyk9oc_L5Vk0g" type="3001" element="_AUNQcNQWEdyk9oc_L5Vk0g"
+ source="_1hvzcdQVEdyk9oc_L5Vk0g" target="_qF5bTNQVEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_AUNQdtQWEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_AUNQd9QWEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_AUNQctQWEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_AUNQc9QWEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_AUNQdNQWEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_AUNQddQWEdyk9oc_L5Vk0g"
+ points="[2, 4, -88, -215]$[96, 193, 6, -26]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_qUmMYNUDEdylRpA9TBY1SQ"
+ id="(0.64364207,0.875)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_AqwvQdQWEdyk9oc_L5Vk0g" type="3001" element="_AqwvQNQWEdyk9oc_L5Vk0g"
+ source="_qF5bTNQVEdyk9oc_L5Vk0g" target="_2GpQQdQVEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_Aq6gQ9QWEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_Aq6gRNQWEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_AqwvQtQWEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_Aq6gQNQWEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_Aq6gQdQWEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_Aq6gQtQWEdyk9oc_L5Vk0g"
+ points="[-1, 27, 89, -18]$[229, 44, 319, -1]"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_KCsvANQWEdyk9oc_L5Vk0g"
+ id="(0.63265306,0.125)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_BFgKgdQWEdyk9oc_L5Vk0g" type="3001" element="_BFgKgNQWEdyk9oc_L5Vk0g"
+ source="_1hvzcdQVEdyk9oc_L5Vk0g" target="_qF5bU9QVEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_BFgKhtQWEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_BFgKh9QWEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_BFgKgtQWEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_BFgKg9QWEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_BFgKhNQWEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_BFgKhdQWEdyk9oc_L5Vk0g"
+ points="[3, 7, -51, -138]$[56, 119, 2, -26]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_BFgKiNQWEdyk9oc_L5Vk0g"
+ id="(0.9136578,0.0)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_BcXLUdQWEdyk9oc_L5Vk0g" type="3001" element="_BcXLUNQWEdyk9oc_L5Vk0g"
+ source="_qF5bU9QVEdyk9oc_L5Vk0g" target="_2GpQQdQVEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_BcXLVtQWEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_BcXLV9QWEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_BcXLUtQWEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_BcXLU9QWEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_BcXLVNQWEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_BcXLVdQWEdyk9oc_L5Vk0g"
+ points="[3, 27, 0, -94]$[59, 121, 56, 0]"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_BcXLWNQWEdyk9oc_L5Vk0g"
+ id="(0.9120879,0.375)"/>
+ </edges>
+ </notation:Diagram>
+</xmi:XMI>
diff --git a/praclib/temp/process.openup.base/capabilitypatterns/elaboration_phase_iteration/model.xmi b/praclib/temp/process.openup.base/capabilitypatterns/elaboration_phase_iteration/model.xmi
new file mode 100644
index 0000000..2206f10
--- /dev/null
+++ b/praclib/temp/process.openup.base/capabilitypatterns/elaboration_phase_iteration/model.xmi
@@ -0,0 +1,76 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_aYkvgNONEdyqlogshP8l4g"
+ guid="_aYkvgNONEdyqlogshP8l4g">
+ <resourceDescriptors xmi:id="_aYkvgdONEdyqlogshP8l4g" id="-TceMuWXdZ1TV2gERYKpA5g"
+ uri="content.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:ProcessComponent xmi:id="_aUsVENONEdyqlogshP8l4g" name="elaboration_phase_iteration"
+ guid="_aUsVENONEdyqlogshP8l4g">
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_XayTQNOOEdyqlogshP8l4g"
+ name="plan_manage_iteration" guid="_XayTQNOOEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_XayTQdOOEdyqlogshP8l4g"
+ name="plan_manage_iteration" guid="_XayTQdOOEdyqlogshP8l4g" superActivities="_aUsVEdONEdyqlogshP8l4g"
+ variabilityType="extends">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://_oZgCsNOEEdyqlogshP8l4g#_oZgCsdOEEdyqlogshP8l4g"/>
+ </processElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_YwLY4NOOEdyqlogshP8l4g"
+ name="identify_and_refine_requirements" guid="_YwLY4NOOEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_YwLY4dOOEdyqlogshP8l4g"
+ name="identify_and_refine_requirements" guid="_YwLY4dOOEdyqlogshP8l4g" superActivities="_aUsVEdONEdyqlogshP8l4g"
+ variabilityType="extends">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://_xxcpgNOEEdyqlogshP8l4g#_xxcpgdOEEdyqlogshP8l4g"/>
+ </processElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_aSrtcNOOEdyqlogshP8l4g"
+ name="develop_architecture" guid="_aSrtcNOOEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_aSrtcdOOEdyqlogshP8l4g"
+ name="develop_architecture" guid="_aSrtcdOOEdyqlogshP8l4g" superActivities="_aUsVEdONEdyqlogshP8l4g"
+ variabilityType="extends">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://_KaeNsNOFEdyqlogshP8l4g#_KaeNsdOFEdyqlogshP8l4g"/>
+ </processElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_eyv_UNOOEdyqlogshP8l4g"
+ name="develop_solution" guid="_eyv_UNOOEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_eyv_UdOOEdyqlogshP8l4g"
+ name="develop_solution" guid="_eyv_UdOOEdyqlogshP8l4g" superActivities="_aUsVEdONEdyqlogshP8l4g"
+ variabilityType="extends">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://_RXGooNOFEdyqlogshP8l4g#_RXGoodOFEdyqlogshP8l4g"/>
+ </processElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_f4VuYNOOEdyqlogshP8l4g"
+ name="test_solution" guid="_f4VuYNOOEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_f4VuYdOOEdyqlogshP8l4g"
+ name="test_solution" guid="_f4VuYdOOEdyqlogshP8l4g" superActivities="_aUsVEdONEdyqlogshP8l4g"
+ variabilityType="extends">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://_buG4sNOFEdyqlogshP8l4g#_buG4sdOFEdyqlogshP8l4g"/>
+ </processElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_g8cPsNOOEdyqlogshP8l4g"
+ name="ongoing_tasks" guid="_g8cPsNOOEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_g8cPsdOOEdyqlogshP8l4g"
+ name="ongoing_tasks" guid="_g8cPsdOOEdyqlogshP8l4g" superActivities="_aUsVEdONEdyqlogshP8l4g"
+ variabilityType="extends">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://__ZInMNOEEdyqlogshP8l4g#__ZInMdOEEdyqlogshP8l4g"/>
+ </processElements>
+ </childPackages>
+ <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_aUsVEdONEdyqlogshP8l4g"
+ name="elaboration_phase_iteration" guid="_aUsVEdONEdyqlogshP8l4g" briefDescription="This iteration template defines the activities (and associated roles and work products) performed in a typical iteration in the Elaboration phase."
+ presentationName="Elaboration Phase Iteration" breakdownElements="_XayTQdOOEdyqlogshP8l4g _YwLY4dOOEdyqlogshP8l4g _aSrtcdOOEdyqlogshP8l4g _eyv_UdOOEdyqlogshP8l4g _f4VuYdOOEdyqlogshP8l4g _g8cPsdOOEdyqlogshP8l4g">
+ <presentation xmi:id="-TceMuWXdZ1TV2gERYKpA5g" href="uma://-TceMuWXdZ1TV2gERYKpA5g#-TceMuWXdZ1TV2gERYKpA5g"/>
+ <defaultContext href="uma://_0NAjrNUAEdylRpA9TBY1SQ#_gExDwNQxEdyk9oc_L5Vk0g"/>
+ <validContext href="uma://_0NAjrNUAEdylRpA9TBY1SQ#_gExDwNQxEdyk9oc_L5Vk0g"/>
+ </process>
+ </org.eclipse.epf.uma:ProcessComponent>
+</xmi:XMI>
diff --git a/praclib/temp/process.openup.base/capabilitypatterns/identify_and_refine_requirements/content.xmi b/praclib/temp/process.openup.base/capabilitypatterns/identify_and_refine_requirements/content.xmi
new file mode 100644
index 0000000..0624b64
--- /dev/null
+++ b/praclib/temp/process.openup.base/capabilitypatterns/identify_and_refine_requirements/content.xmi
@@ -0,0 +1,46 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:ProcessDescription 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="-yNrF2Ac8VgD0WjoUxGOsIQ"
+ name="identify_and_refine_requirements,_xxcpgdOEEdyqlogshP8l4g" guid="-yNrF2Ac8VgD0WjoUxGOsIQ"
+ version="7.2.0">
+ <mainDescription><p>
+ This activity describes the tasks you perform to gather, specify, analyze, and validate a subset of system's
+ requirements prior to implementation and verification. This does not imply that all requirements are detailed prior to
+ commencing implementation. Rather, you perform this activity throughout the lifecycle with <a class="elementLink"
+ href="./../../core.default.role_def.base/roles/stakeholder_9FFD4106.html"
+ guid="_dTa6gMAYEdqX-s4mWhkyqQ">Stakeholder</a>s and the entire development team collaborating to ensure that a clear,
+ consistent, correct, verifiable, and feasible set of requirements is available, as needed, to drive implementation and
+ verification.
+</p>
+<p>
+ During <b>Inception</b>, the focus is on gaining agreement on the problem to be solved, gathering stakeholder needs,
+ and capturing high-level system features (see activity <a class="elementLink"
+ href="./resources/initiate_project_D9C03857.html" guid="_0pWNA8lgEdmt3adZL5Dmdw">Initiate Project</a>).
+</p>
+<p>
+ During <b>Elaboration</b>, the focus shifts to defining the solution. This consists of finding those requirements that
+ have the most value to stakeholders, that are particularly challenging or risky, or that are architecturally
+ significant (See <a class="elementLinkWithType"
+ href="./../../practice.tech.use_case_driven_dev.base/tasks/identify_and_outline_requirements_90D272B9.html"
+ guid="_P9cMUPV_EdmdHa9MmVPgqQ">Task: ** Identify and Outline Requirements</a>). You then describe requirements (that
+ are prioritized, via the <a class="elementLink"
+ href="./../../practice.mgmt.iterative_dev.base/workproducts/work_items_list_39D03CC8.html"
+ guid="_rGNWsCbSEdqh1LYUOGRh2A">Work Items List</a>, for implementation in the early iterations) in sufficient detail to
+ validate the development team's understanding of the requirements, to ensure concurrence with stakeholders, and to
+ permit software development to begin (see <a class="elementLinkWithType"
+ href="./../../legacy.obsoleted_from_openup/tasks/detail_requirements_9747F71E.html"
+ guid="_0e1mIMlgEdmt3adZL5Dmdw">Task: * Detail Requirements</a>). For each of these requirements, define associated test
+ cases to ensure that the requirements are verifiable, and to provide the guidance needed for verification and
+ validation (see <a class="elementLinkWithType"
+ href="./../../practice.tech.agile_testing.base/tasks/create_test_cases_D39E98A1.html"
+ guid="_0iwc0clgEdmt3adZL5Dmdw">Task: Create Test Cases</a>).
+</p>
+<p>
+ During Construction, the focus shifts to refining the system definition. This consists of detailing the remaining
+ requirements and associated test cases as necessary to drive implementation and verification, and managing requirements
+ change (see activity <a class="elementLink" href="./resources/ongoing_tasks_91569239.html"
+ guid="_0pJ_xslgEdmt3adZL5Dmdw">Ongoing Tasks</a>).
+</p></mainDescription>
+</org.eclipse.epf.uma:ProcessDescription>
diff --git a/praclib/temp/process.openup.base/capabilitypatterns/identify_and_refine_requirements/model.xmi b/praclib/temp/process.openup.base/capabilitypatterns/identify_and_refine_requirements/model.xmi
new file mode 100644
index 0000000..39e76d8
--- /dev/null
+++ b/praclib/temp/process.openup.base/capabilitypatterns/identify_and_refine_requirements/model.xmi
@@ -0,0 +1,124 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_xzZKQdOEEdyqlogshP8l4g"
+ guid="_xzZKQdOEEdyqlogshP8l4g">
+ <resourceDescriptors xmi:id="_xzZKQtOEEdyqlogshP8l4g" id="-yNrF2Ac8VgD0WjoUxGOsIQ"
+ uri="content.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:ProcessComponent xmi:id="_xxcpgNOEEdyqlogshP8l4g" name="identify_and_refine_requirements"
+ guid="_xxcpgNOEEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_EOm5oNOLEdyqlogshP8l4g"
+ name="identify_and_outline_requirements" guid="_EOm5oNOLEdyqlogshP8l4g" presentationName="Identify and Outline Requirements"
+ superActivities="_xxcpgdOEEdyqlogshP8l4g" additionallyPerformedBy="_EOwqodOLEdyqlogshP8l4g _EOwqotOLEdyqlogshP8l4g _EOwqo9OLEdyqlogshP8l4g _EOwqpNOLEdyqlogshP8l4g"
+ optionalInput="_HDOWUdOLEdyqlogshP8l4g" output="_EOwqptOLEdyqlogshP8l4g _EOwqp9OLEdyqlogshP8l4g _EOwqqNOLEdyqlogshP8l4g _EOwqqdOLEdyqlogshP8l4g"
+ performedPrimarilyBy="_EOwqoNOLEdyqlogshP8l4g">
+ <Task href="uma://_GbYfULPaEduocbW-TPTq7A#_P9cMUPV_EdmdHa9MmVPgqQ"/>
+ <selectedSteps href="uma://_P9iS8PV_EdmdHa9MmVPgqQ#_ckG-cCY-EdqNHcQ-rAojXw"/>
+ <selectedSteps href="uma://_P9iS8PV_EdmdHa9MmVPgqQ#_GAr3IOz3Edq2wJOsmRwmhg"/>
+ <selectedSteps href="uma://_P9iS8PV_EdmdHa9MmVPgqQ#_fDbgkCY-EdqNHcQ-rAojXw"/>
+ <selectedSteps href="uma://-Yt8TXGkE1rwydXR34apsrg#_N66nkApAEdyT57ElgMr6TA"/>
+ <selectedSteps href="uma://_P9iS8PV_EdmdHa9MmVPgqQ#_CD_a8JJKEdyk6dG0ehkW5Q"/>
+ <selectedSteps href="uma://_P9iS8PV_EdmdHa9MmVPgqQ#_Ql45gEI6Edyrh7YaMjqrlA"/>
+ <selectedSteps href="uma://_P9iS8PV_EdmdHa9MmVPgqQ#_0WhHsN-eEdqiM_wFaqLjNg"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_EOwqoNOLEdyqlogshP8l4g"
+ name="analyst" guid="_EOwqoNOLEdyqlogshP8l4g" presentationName="Analyst" isPlanned="false"
+ superActivities="_xxcpgdOEEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0VxJsMlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_EOwqodOLEdyqlogshP8l4g"
+ name="architect" guid="_EOwqodOLEdyqlogshP8l4g" presentationName="Architect"
+ isPlanned="false" superActivities="_xxcpgdOEEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0X9iEMlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_EOwqotOLEdyqlogshP8l4g"
+ name="developer" guid="_EOwqotOLEdyqlogshP8l4g" presentationName="Developer"
+ isPlanned="false" superActivities="_xxcpgdOEEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_EOwqo9OLEdyqlogshP8l4g"
+ name="stakeholder" guid="_EOwqo9OLEdyqlogshP8l4g" presentationName="Stakeholder"
+ isPlanned="false" superActivities="_xxcpgdOEEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_dTa6gMAYEdqX-s4mWhkyqQ"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_EOwqpNOLEdyqlogshP8l4g"
+ name="tester" guid="_EOwqpNOLEdyqlogshP8l4g" presentationName="Tester" isPlanned="false"
+ superActivities="_xxcpgdOEEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0ZM4MclgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_EOwqptOLEdyqlogshP8l4g"
+ name="system_wide_requirements" guid="_EOwqptOLEdyqlogshP8l4g" presentationName="System-Wide Requirements"
+ isPlanned="false" superActivities="_xxcpgdOEEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_BVh9cL-CEdqb7N6KIeDL8Q"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_EOwqp9OLEdyqlogshP8l4g"
+ name="use_case" guid="_EOwqp9OLEdyqlogshP8l4g" presentationName="Use Case"
+ isPlanned="false" superActivities="_xxcpgdOEEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0VGbUMlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_EOwqqNOLEdyqlogshP8l4g"
+ name="glossary" guid="_EOwqqNOLEdyqlogshP8l4g" presentationName="Glossary"
+ isPlanned="false" superActivities="_xxcpgdOEEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_Wn7HcNcEEdqz_d2XWoVt6Q"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_EOwqqdOLEdyqlogshP8l4g"
+ name="use_case_model" guid="_EOwqqdOLEdyqlogshP8l4g" presentationName="Use-Case Model"
+ isPlanned="false" superActivities="_xxcpgdOEEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_W2SgEDR5EdutE_HNDTJk5Q"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_FX7SINOLEdyqlogshP8l4g"
+ name="detail_use_case_scenarios" guid="_FX7SINOLEdyqlogshP8l4g" presentationName="Detail Use-Case Scenarios"
+ superActivities="_xxcpgdOEEdyqlogshP8l4g" additionallyPerformedBy="_EOwqodOLEdyqlogshP8l4g _EOwqotOLEdyqlogshP8l4g _EOwqo9OLEdyqlogshP8l4g _EOwqpNOLEdyqlogshP8l4g"
+ mandatoryInput="_EOwqp9OLEdyqlogshP8l4g" output="_EOwqp9OLEdyqlogshP8l4g _EOwqqNOLEdyqlogshP8l4g _EOwqqdOLEdyqlogshP8l4g"
+ performedPrimarilyBy="_EOwqoNOLEdyqlogshP8l4g">
+ <Task href="uma://_GbYfULPaEduocbW-TPTq7A#_SL7N0LPdEduocbW-TPTq7A"/>
+ <selectedSteps href="uma://-oFAa8Uu6tr_GkE_E0iycdQ#_fAWPkJLZEdyk6dG0ehkW5Q"/>
+ <selectedSteps href="uma://-locCQOxOUM8zej2tBD6M6Q#_-pOLIUbEEdyx8quJU3Grxg"/>
+ <selectedSteps href="uma://-oFAa8Uu6tr_GkE_E0iycdQ#_iEvYMJLaEdyk6dG0ehkW5Q"/>
+ <selectedSteps href="uma://-oFAa8Uu6tr_GkE_E0iycdQ#_kojt4JLcEdyk6dG0ehkW5Q"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_F68foNOLEdyqlogshP8l4g"
+ name="detail_system_wide_requirements" guid="_F68foNOLEdyqlogshP8l4g" presentationName="Detail System-Wide Requirements"
+ superActivities="_xxcpgdOEEdyqlogshP8l4g" additionallyPerformedBy="_EOwqodOLEdyqlogshP8l4g _EOwqotOLEdyqlogshP8l4g _EOwqo9OLEdyqlogshP8l4g _EOwqpNOLEdyqlogshP8l4g"
+ mandatoryInput="_EOwqptOLEdyqlogshP8l4g" optionalInput="_EOwqp9OLEdyqlogshP8l4g"
+ output="_EOwqptOLEdyqlogshP8l4g _EOwqqNOLEdyqlogshP8l4g" performedPrimarilyBy="_EOwqoNOLEdyqlogshP8l4g">
+ <Task href="uma://_GbYfULPaEduocbW-TPTq7A#_4z8Z0EbEEdyx8quJU3Grxg"/>
+ <selectedSteps href="uma://-9sNgONA1WJCxf12B40uDgw#_4z8Z1EbEEdyx8quJU3Grxg"/>
+ <selectedSteps href="uma://-9sNgONA1WJCxf12B40uDgw#_4z8Z0UbEEdyx8quJU3Grxg"/>
+ <selectedSteps href="uma://-9sNgONA1WJCxf12B40uDgw#_4z8Z0kbEEdyx8quJU3Grxg"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_HDOWUNOLEdyqlogshP8l4g"
+ name="create_test_cases" guid="_HDOWUNOLEdyqlogshP8l4g" presentationName="Create Test Cases"
+ superActivities="_xxcpgdOEEdyqlogshP8l4g" additionallyPerformedBy="_EOwqoNOLEdyqlogshP8l4g _EOwqotOLEdyqlogshP8l4g _EOwqo9OLEdyqlogshP8l4g"
+ mandatoryInput="_HDOWUdOLEdyqlogshP8l4g" optionalInput="_HDOWUtOLEdyqlogshP8l4g"
+ output="_HDOWUtOLEdyqlogshP8l4g" performedPrimarilyBy="_EOwqpNOLEdyqlogshP8l4g">
+ <Task href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_0iwc0clgEdmt3adZL5Dmdw"/>
+ <selectedSteps href="uma://_NrVKsKeqEdmKDbQuyzCoqQ#_IJFSsKuSEdmhFZtkg1nakg"/>
+ <selectedSteps href="uma://_NrVKsKeqEdmKDbQuyzCoqQ#_aDe_ILGcEdubqf8m_Zrvvg"/>
+ <selectedSteps href="uma://_NrVKsKeqEdmKDbQuyzCoqQ#_LpbM8KuSEdmhFZtkg1nakg"/>
+ <selectedSteps href="uma://_NrVKsKeqEdmKDbQuyzCoqQ#_NK18YKuSEdmhFZtkg1nakg"/>
+ <selectedSteps href="uma://_NrVKsKeqEdmKDbQuyzCoqQ#_Ok_mMKuSEdmhFZtkg1nakg"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_HDOWUdOLEdyqlogshP8l4g"
+ name="technical_specification_slot" guid="_HDOWUdOLEdyqlogshP8l4g" presentationName="[Technical Specification]"
+ isPlanned="false" superActivities="_xxcpgdOEEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_i3vkoLS-EduDY8LNbMCDBA"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_HDOWUtOLEdyqlogshP8l4g"
+ name="test_case" guid="_HDOWUtOLEdyqlogshP8l4g" presentationName="Test Case"
+ isPlanned="false" superActivities="_xxcpgdOEEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZS-0MlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_xxcpgdOEEdyqlogshP8l4g"
+ name="identify_and_refine_requirements" guid="_xxcpgdOEEdyqlogshP8l4g" briefDescription="sDetail a set of requirements (one or more use cases, scenarios or system-wide requirements)."
+ presentationName="Identify and Refine Requirements" breakdownElements="_EOm5oNOLEdyqlogshP8l4g _EOwqoNOLEdyqlogshP8l4g _EOwqodOLEdyqlogshP8l4g _EOwqotOLEdyqlogshP8l4g _EOwqo9OLEdyqlogshP8l4g _EOwqpNOLEdyqlogshP8l4g _EOwqptOLEdyqlogshP8l4g _EOwqp9OLEdyqlogshP8l4g _EOwqqNOLEdyqlogshP8l4g _EOwqqdOLEdyqlogshP8l4g _FX7SINOLEdyqlogshP8l4g _F68foNOLEdyqlogshP8l4g _HDOWUNOLEdyqlogshP8l4g _HDOWUdOLEdyqlogshP8l4g _HDOWUtOLEdyqlogshP8l4g">
+ <presentation xmi:id="-yNrF2Ac8VgD0WjoUxGOsIQ" href="uma://-yNrF2Ac8VgD0WjoUxGOsIQ#-yNrF2Ac8VgD0WjoUxGOsIQ"/>
+ <defaultContext href="uma://_Sw_vnNnREdyNj6EOmqy5Rg#_gExDwNQxEdyk9oc_L5Vk0g"/>
+ <validContext href="uma://_Sw_vnNnREdyNj6EOmqy5Rg#_gExDwNQxEdyk9oc_L5Vk0g"/>
+ </process>
+ </org.eclipse.epf.uma:ProcessComponent>
+</xmi:XMI>
diff --git a/praclib/temp/process.openup.base/capabilitypatterns/inception_phase_iteration/content.xmi b/praclib/temp/process.openup.base/capabilitypatterns/inception_phase_iteration/content.xmi
new file mode 100644
index 0000000..defc3ce
--- /dev/null
+++ b/praclib/temp/process.openup.base/capabilitypatterns/inception_phase_iteration/content.xmi
@@ -0,0 +1,114 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:ProcessDescription 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="-SMF3QeQbQRdkgCVMy0OpuQ"
+ name="inception_phase_iteration,_h0Gs8dONEdyqlogshP8l4g" guid="-SMF3QeQbQRdkgCVMy0OpuQ"
+ version="7.2.0">
+ <mainDescription><p>
+ The project starts with the assumption that you have:
+</p>
+<ul>
+ <li>
+ Created the business case
+ </li>
+ <li>
+ Identified the <a class="elementlinkwithusertext"
+ href="./../../core.default.role_def.base/roles/project_manager_E657F936.html"
+ guid="_0a0o0MlgEdmt3adZL5Dmdw">project manager</a>
+ </li>
+ <li>
+ Defined the team (at least for the first iteration)
+ </li>
+ <li>
+ Put in place the development environment (including tools and infrastructure)
+ </li>
+ <li>
+ Prepared your organization to follow the <a class="elementlinkwithusertext"
+ href="./resources/openup_lifecycle_2CB8A7DA.html" guid="_0uyGoMlgEdmt3adZL5Dmdw">delivery process</a> suggested by
+ the published process description
+ </li>
+</ul>
+<p>
+ The number and length of each Inception iteration will vary depending upon the needs of the project.
+</p>
+<p>
+ The following table summarizes the&nbsp;Inception phase objectives and&nbsp;what activities address each objective:
+</p>
+<p align="center">
+ <strong>Inception phase objectives and activities</strong>
+</p><br />
+<br />
+<table cellspacing="1" cellpadding="0" align="center" border="1">
+ <tbody>
+ <tr>
+ <td class="Normal" valign="top" width="295">
+ <b>Phase objectives</b>
+ </td>
+ <td class="Normal" valign="top" width="295">
+ <b>Activities that address objectives</b>
+ </td>
+ </tr>
+ <tr>
+ <td class="Normal" valign="top" width="295">
+ Understand what to build
+ </td>
+ <td class="Normal" valign="top" width="295">
+ <p>
+ <a class="elementLink"
+ href="./../../process.openup.base/capabilitypatterns/identify_and_refine_requirements_7FA6CB14.html"
+ guid="_xxcpgdOEEdyqlogshP8l4g">Identify and Refine Requirements</a>
+ </p>
+ </td>
+ </tr>
+ <tr>
+ <td class="Normal" valign="top" width="295">
+ Identify key system functionality
+ </td>
+ <td class="Normal" valign="top" width="295">
+ <p>
+ <a class="elementLink"
+ href="./../../process.openup.base/capabilitypatterns/initiate_project_37A47ADB.html"
+ guid="_eWxZgdOEEdyqlogshP8l4g">Initiate Project</a>
+ </p>
+ <p>
+ <a class="elementLink"
+ href="./../../process.openup.base/capabilitypatterns/identify_and_refine_requirements_7FA6CB14.html"
+ guid="_xxcpgdOEEdyqlogshP8l4g">Identify and Refine Requirements</a>
+ </p>
+ </td>
+ </tr>
+ <tr>
+ <td class="Normal" valign="top" width="295">
+ Determine at least one possible solution
+ </td>
+ <td class="Normal" valign="top" width="295">
+ <a class="elementLink"
+ href="./../../process.openup.base/capabilitypatterns/agree_technical_approach_7096F6A3.html"
+ guid="_4ouDUdOEEdyqlogshP8l4g">Agree on Technical Approach</a>
+ </td>
+ </tr>
+ <tr>
+ <td class="Normal" valign="top" width="295">
+ Understand the cost, schedule, and risks associated with the project
+ </td>
+ <td class="Normal" valign="top" width="295">
+ <p>
+ <a class="elementLink"
+ href="./../../process.openup.base/capabilitypatterns/initiate_project_37A47ADB.html"
+ guid="_eWxZgdOEEdyqlogshP8l4g">Initiate Project</a>
+ </p>
+ <p>
+ <a class="elementLink"
+ href="./../../process.openup.base/capabilitypatterns/plan_manage_iteration_F9713A62.html"
+ guid="_oZgCsdOEEdyqlogshP8l4g">Plan and Manage Iteration</a>
+ </p>
+ </td>
+ </tr>
+ </tbody>
+</table><br />
+<br /></mainDescription>
+ <alternatives>This iteration template does not include any activities that result in any implementation. In some projects there will have
+to be some implementation work done to meet the objectives of Inception. In those cases, additional activities should be
+added to handle that.</alternatives>
+</org.eclipse.epf.uma:ProcessDescription>
diff --git a/praclib/temp/process.openup.base/capabilitypatterns/inception_phase_iteration/diagram.xmi b/praclib/temp/process.openup.base/capabilitypatterns/inception_phase_iteration/diagram.xmi
new file mode 100644
index 0000000..5efc3be
--- /dev/null
+++ b/praclib/temp/process.openup.base/capabilitypatterns/inception_phase_iteration/diagram.xmi
@@ -0,0 +1,339 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xmi:XMI xmi:version="2.0"
+ xmlns:xmi="http://www.omg.org/XMI" xmlns:ecore="http://www.eclipse.org/emf/2002/Ecore"
+ xmlns:notation="http://www.eclipse.org/gmf/runtime/1.0.1/notation" xmlns:uml="http://www.eclipse.org/uml2/2.1.0/UML">
+ <uml:Activity xmi:id="_gUavgNQUEdyk9oc_L5Vk0g" name="inception_phase_iteration">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_gUavgdQUEdyk9oc_L5Vk0g" source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_gUavgtQUEdyk9oc_L5Vk0g"
+ key="uri" value="uma://_h0Gs8NONEdyqlogshP8l4g#_h0Gs8dONEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_gUavg9QUEdyk9oc_L5Vk0g"
+ key="type" value="Activity"/>
+ </eAnnotations>
+ <node xmi:type="uml:StructuredActivityNode" xmi:id="_gWXQQNQUEdyk9oc_L5Vk0g" name="Initiate Project"
+ outgoing="_BaHlENQVEdyk9oc_L5Vk0g" incoming="_2UpFcNQUEdyk9oc_L5Vk0g">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_gWXQQdQUEdyk9oc_L5Vk0g"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_gWXQQtQUEdyk9oc_L5Vk0g"
+ key="uri" value="uma://_h0Gs8NONEdyqlogshP8l4g#_nfpeAdOOEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_gWXQQ9QUEdyk9oc_L5Vk0g"
+ key="type" value="Activity"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:StructuredActivityNode" xmi:id="_gWXQRNQUEdyk9oc_L5Vk0g" name="Plan and Manage Iteration"
+ outgoing="_5XTlMNQUEdyk9oc_L5Vk0g" incoming="_454CUNQUEdyk9oc_L5Vk0g">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_gWXQRdQUEdyk9oc_L5Vk0g"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_gWXQRtQUEdyk9oc_L5Vk0g"
+ key="uri" value="uma://_h0Gs8NONEdyqlogshP8l4g#_uxDPEdOOEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_gWXQR9QUEdyk9oc_L5Vk0g"
+ key="type" value="Activity"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:StructuredActivityNode" xmi:id="_gWXQSNQUEdyk9oc_L5Vk0g" name="Identify and Refine Requirements"
+ outgoing="_3x3RYNQUEdyk9oc_L5Vk0g" incoming="_21XM4NQUEdyk9oc_L5Vk0g">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_gWXQSdQUEdyk9oc_L5Vk0g"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_gWXQStQUEdyk9oc_L5Vk0g"
+ key="uri" value="uma://_h0Gs8NONEdyqlogshP8l4g#_vyeP0dOOEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_gWXQS9QUEdyk9oc_L5Vk0g"
+ key="type" value="Activity"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:StructuredActivityNode" xmi:id="_gWXQTNQUEdyk9oc_L5Vk0g" name="Agree on Technical Approach"
+ outgoing="_4TewsNQUEdyk9oc_L5Vk0g" incoming="_3QseANQUEdyk9oc_L5Vk0g">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_gWXQTdQUEdyk9oc_L5Vk0g"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_gWXQTtQUEdyk9oc_L5Vk0g"
+ key="uri" value="uma://_h0Gs8NONEdyqlogshP8l4g#_w-Bc8dOOEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_gWXQT9QUEdyk9oc_L5Vk0g"
+ key="type" value="Activity"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:InitialNode" xmi:id="_qzIxINQUEdyk9oc_L5Vk0g" outgoing="_1z6-ANQUEdyk9oc_L5Vk0g"/>
+ <node xmi:type="uml:ActivityFinalNode" xmi:id="_rPrjMNQUEdyk9oc_L5Vk0g" incoming="_5uTv8NQUEdyk9oc_L5Vk0g"/>
+ <node xmi:type="uml:ForkNode" xmi:id="_soIj4NQUEdyk9oc_L5Vk0g" outgoing="_2UpFcNQUEdyk9oc_L5Vk0g _454CUNQUEdyk9oc_L5Vk0g"
+ incoming="_1z6-ANQUEdyk9oc_L5Vk0g"/>
+ <node xmi:type="uml:ForkNode" xmi:id="_tb_CsNQUEdyk9oc_L5Vk0g" outgoing="_21XM4NQUEdyk9oc_L5Vk0g _3QseANQUEdyk9oc_L5Vk0g"
+ incoming="_BaHlENQVEdyk9oc_L5Vk0g"/>
+ <node xmi:type="uml:JoinNode" xmi:id="_vG9WwNQUEdyk9oc_L5Vk0g" outgoing="_5uTv8NQUEdyk9oc_L5Vk0g"
+ incoming="_3x3RYNQUEdyk9oc_L5Vk0g _4TewsNQUEdyk9oc_L5Vk0g _5XTlMNQUEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_1z6-ANQUEdyk9oc_L5Vk0g" source="_qzIxINQUEdyk9oc_L5Vk0g"
+ target="_soIj4NQUEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_2UpFcNQUEdyk9oc_L5Vk0g" source="_soIj4NQUEdyk9oc_L5Vk0g"
+ target="_gWXQQNQUEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_21XM4NQUEdyk9oc_L5Vk0g" source="_tb_CsNQUEdyk9oc_L5Vk0g"
+ target="_gWXQSNQUEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_3QseANQUEdyk9oc_L5Vk0g" source="_tb_CsNQUEdyk9oc_L5Vk0g"
+ target="_gWXQTNQUEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_3x3RYNQUEdyk9oc_L5Vk0g" source="_gWXQSNQUEdyk9oc_L5Vk0g"
+ target="_vG9WwNQUEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_4TewsNQUEdyk9oc_L5Vk0g" source="_gWXQTNQUEdyk9oc_L5Vk0g"
+ target="_vG9WwNQUEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_454CUNQUEdyk9oc_L5Vk0g" source="_soIj4NQUEdyk9oc_L5Vk0g"
+ target="_gWXQRNQUEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_5XTlMNQUEdyk9oc_L5Vk0g" source="_gWXQRNQUEdyk9oc_L5Vk0g"
+ target="_vG9WwNQUEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_5uTv8NQUEdyk9oc_L5Vk0g" source="_vG9WwNQUEdyk9oc_L5Vk0g"
+ target="_rPrjMNQUEdyk9oc_L5Vk0g"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_BaHlENQVEdyk9oc_L5Vk0g" source="_gWXQQNQUEdyk9oc_L5Vk0g"
+ target="_tb_CsNQUEdyk9oc_L5Vk0g"/>
+ </uml:Activity>
+ <notation:Diagram xmi:id="_gUavhNQUEdyk9oc_L5Vk0g" type="AD" element="_gUavgNQUEdyk9oc_L5Vk0g"
+ name="inception_phase_iteration" measurementUnit="Pixel">
+ <children xmi:type="notation:Node" xmi:id="_mXjWoNQUEdyk9oc_L5Vk0g" type="1007"
+ element="_gWXQQNQUEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_mXjWptQUEdyk9oc_L5Vk0g" type="4005"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_mXjWodQUEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_mXjWotQUEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_mXjWo9QUEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_mXjWpNQUEdyk9oc_L5Vk0g" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_mXjWpdQUEdyk9oc_L5Vk0g"
+ x="144" y="156"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_mXjWp9QUEdyk9oc_L5Vk0g" type="1007"
+ element="_gWXQRNQUEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_mXjWrdQUEdyk9oc_L5Vk0g" type="4005"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_mXjWqNQUEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_mXjWqdQUEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_mXjWqtQUEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_mXjWq9QUEdyk9oc_L5Vk0g" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_mXjWrNQUEdyk9oc_L5Vk0g"
+ x="396" y="252"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_mXjWrtQUEdyk9oc_L5Vk0g" type="1007"
+ element="_gWXQSNQUEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_mXtHoNQUEdyk9oc_L5Vk0g" type="4005"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_mXjWr9QUEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_mXjWsNQUEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_mXjWsdQUEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_mXjWstQUEdyk9oc_L5Vk0g" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_mXjWs9QUEdyk9oc_L5Vk0g"
+ x="24" y="288"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_mXtHodQUEdyk9oc_L5Vk0g" type="1007"
+ element="_gWXQTNQUEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_mXtHp9QUEdyk9oc_L5Vk0g" type="4005"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_mXtHotQUEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_mXtHo9QUEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_mXtHpNQUEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_mXtHpdQUEdyk9oc_L5Vk0g" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_mXtHptQUEdyk9oc_L5Vk0g"
+ x="180" y="372"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_qzIxIdQUEdyk9oc_L5Vk0g" type="1004"
+ element="_qzIxINQUEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_qzIxJ9QUEdyk9oc_L5Vk0g" type="4003">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_qzIxKNQUEdyk9oc_L5Vk0g"
+ y="5"/>
+ </children>
+ <styles xmi:type="notation:FontStyle" xmi:id="_qzIxItQUEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_qzIxI9QUEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_qzIxJNQUEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_qzIxJdQUEdyk9oc_L5Vk0g" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_qzIxJtQUEdyk9oc_L5Vk0g"
+ x="276" y="48"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_rPrjMdQUEdyk9oc_L5Vk0g" type="1001"
+ element="_rPrjMNQUEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_rPrjN9QUEdyk9oc_L5Vk0g" type="4001">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_rPrjONQUEdyk9oc_L5Vk0g"
+ y="5"/>
+ </children>
+ <styles xmi:type="notation:FontStyle" xmi:id="_rPrjMtQUEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_rPrjM9QUEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_rPrjNNQUEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_rPrjNdQUEdyk9oc_L5Vk0g" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_rPrjNtQUEdyk9oc_L5Vk0g"
+ x="276" y="528"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_soIj4dQUEdyk9oc_L5Vk0g" type="1003"
+ element="_soIj4NQUEdyk9oc_L5Vk0g">
+ <styles xmi:type="notation:FontStyle" xmi:id="_soIj4tQUEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_soIj49QUEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_soIj5NQUEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_soIj5dQUEdyk9oc_L5Vk0g" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_soIj5tQUEdyk9oc_L5Vk0g"
+ x="24" y="108" width="505"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_tb_CsdQUEdyk9oc_L5Vk0g" type="1003"
+ element="_tb_CsNQUEdyk9oc_L5Vk0g">
+ <styles xmi:type="notation:FontStyle" xmi:id="_tb_CstQUEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_tb_Cs9QUEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_tb_CtNQUEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_tb_CtdQUEdyk9oc_L5Vk0g" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_tb_CttQUEdyk9oc_L5Vk0g"
+ x="24" y="233" width="301"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_vG9WwdQUEdyk9oc_L5Vk0g" type="1006"
+ element="_vG9WwNQUEdyk9oc_L5Vk0g">
+ <styles xmi:type="notation:FontStyle" xmi:id="_vG9WwtQUEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_vG9Ww9QUEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_vG9WxNQUEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_vG9WxdQUEdyk9oc_L5Vk0g" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_vG9WxtQUEdyk9oc_L5Vk0g"
+ x="24" y="468" width="505"/>
+ </children>
+ <styles xmi:type="notation:PageStyle" xmi:id="_gUavhdQUEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:GuideStyle" xmi:id="_gUavhtQUEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_gUavh9QUEdyk9oc_L5Vk0g"/>
+ <edges xmi:type="notation:Edge" xmi:id="_1z6-AdQUEdyk9oc_L5Vk0g" type="3001" element="_1z6-ANQUEdyk9oc_L5Vk0g"
+ source="_qzIxIdQUEdyk9oc_L5Vk0g" target="_soIj4dQUEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_1z6-BtQUEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_1z6-B9QUEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_1z6-AtQUEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_1z6-A9QUEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_1z6-BNQUEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_1z6-BdQUEdyk9oc_L5Vk0g"
+ points="[-1, 10, 9, -44]$[243, 52, 253, -2]"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_2UpFcdQUEdyk9oc_L5Vk0g" type="3001" element="_2UpFcNQUEdyk9oc_L5Vk0g"
+ source="_soIj4dQUEdyk9oc_L5Vk0g" target="_mXjWoNQUEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_2UpFdtQUEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_2UpFd9QUEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_2UpFctQUEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_2UpFc9QUEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_2UpFdNQUEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_2UpFddQUEdyk9oc_L5Vk0g"
+ points="[-6, 4, 91, -66]$[-62, 45, 35, -25]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_JQFbwNQVEdyk9oc_L5Vk0g"
+ id="(0.3069307,0.0)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_21XM4dQUEdyk9oc_L5Vk0g" type="3001" element="_21XM4NQUEdyk9oc_L5Vk0g"
+ source="_tb_CsdQUEdyk9oc_L5Vk0g" target="_mXjWrtQUEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_21XM5tQUEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_21XM59QUEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_21XM4tQUEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_21XM49QUEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_21XM5NQUEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_21XM5dQUEdyk9oc_L5Vk0g"
+ points="[-4, 4, 64, -60]$[-69, 51, -1, -13]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_8QGXQNQUEdyk9oc_L5Vk0g"
+ id="(0.24584718,0.375)"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_21gW0NQUEdyk9oc_L5Vk0g"
+ id="(0.49101797,0.24528302)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_3QseAdQUEdyk9oc_L5Vk0g" type="3001" element="_3QseANQUEdyk9oc_L5Vk0g"
+ source="_tb_CsdQUEdyk9oc_L5Vk0g" target="_mXtHodQUEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_3QseBtQUEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_3QseB9QUEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_3QseAtQUEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_3QseA9QUEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_3QseBNQUEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_3QseBdQUEdyk9oc_L5Vk0g"
+ points="[1, 8, -23, -157]$[18, 139, -6, -26]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_3QseCNQUEdyk9oc_L5Vk0g"
+ id="(0.7973422,0.375)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_3x3RYdQUEdyk9oc_L5Vk0g" type="3001" element="_3x3RYNQUEdyk9oc_L5Vk0g"
+ source="_mXjWrtQUEdyk9oc_L5Vk0g" target="_vG9WwdQUEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_3yBCYNQUEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_3yBCYdQUEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_3x3RYtQUEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_3x3RY9QUEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_3x3RZNQUEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_3x3RZdQUEdyk9oc_L5Vk0g"
+ points="[3, 27, 0, -130]$[-83, 156, -86, -1]"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_3yBCYtQUEdyk9oc_L5Vk0g"
+ id="(0.17029703,0.375)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_4TewsdQUEdyk9oc_L5Vk0g" type="3001" element="_4TewsNQUEdyk9oc_L5Vk0g"
+ source="_mXtHodQUEdyk9oc_L5Vk0g" target="_vG9WwdQUEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_4TewttQUEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_4Tewt9QUEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_4TewstQUEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_4Tews9QUEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_4TewtNQUEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_4TewtdQUEdyk9oc_L5Vk0g"
+ points="[0, 27, 7, -43]$[0, 59, 7, -11]$[0, 70, 7, 0]"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_4TewuNQUEdyk9oc_L5Vk0g"
+ id="(0.44554454,0.0)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_454CUdQUEdyk9oc_L5Vk0g" type="3001" element="_454CUNQUEdyk9oc_L5Vk0g"
+ source="_soIj4dQUEdyk9oc_L5Vk0g" target="_mXjWp9QUEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_454CVtQUEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_454CV9QUEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_454CUtQUEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_454CU9QUEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_454CVNQUEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_454CVdQUEdyk9oc_L5Vk0g"
+ points="[-4, 2, 0, -146]$[-7, 138, -3, -10]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_454CWNQUEdyk9oc_L5Vk0g"
+ id="(0.86336637,0.75)"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_454CWdQUEdyk9oc_L5Vk0g"
+ id="(0.46153846,0.18867925)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_5XTlMdQUEdyk9oc_L5Vk0g" type="3001" element="_5XTlMNQUEdyk9oc_L5Vk0g"
+ source="_mXjWp9QUEdyk9oc_L5Vk0g" target="_vG9WwdQUEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_5XTlNtQUEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_5XTlN9QUEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_5XTlMtQUEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_5XTlM9QUEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_5XTlNNQUEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_5XTlNdQUEdyk9oc_L5Vk0g"
+ points="[0, 27, 0, -164]$[0, 63, 0, -128]$[0, 190, 0, -1]"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_5XTlONQUEdyk9oc_L5Vk0g"
+ id="(0.86534655,0.125)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_5uTv8dQUEdyk9oc_L5Vk0g" type="3001" element="_5uTv8NQUEdyk9oc_L5Vk0g"
+ source="_vG9WwdQUEdyk9oc_L5Vk0g" target="_rPrjMdQUEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_5uTv9tQUEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_5uTv99QUEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_5uTv8tQUEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_5uTv89QUEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_5uTv9NQUEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_5uTv9dQUEdyk9oc_L5Vk0g"
+ points="[1, 4, -11, -64]$[0, 66, -12, -2]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_9yG8kNQUEdyk9oc_L5Vk0g"
+ id="(0.52079207,0.0)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_BbnZ4dQVEdyk9oc_L5Vk0g" type="3001" element="_BaHlENQVEdyk9oc_L5Vk0g"
+ source="_mXjWoNQUEdyk9oc_L5Vk0g" target="_tb_CsdQUEdyk9oc_L5Vk0g">
+ <children xmi:type="notation:Node" xmi:id="_BbnZ5tQVEdyk9oc_L5Vk0g" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_BbnZ59QVEdyk9oc_L5Vk0g"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_BbnZ4tQVEdyk9oc_L5Vk0g"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_BbnZ49QVEdyk9oc_L5Vk0g" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_BbnZ5NQVEdyk9oc_L5Vk0g" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_BbnZ5dQVEdyk9oc_L5Vk0g"
+ points="[7, 27, -9, -31]$[7, 51, -9, -7]"/>
+ </edges>
+ </notation:Diagram>
+</xmi:XMI>
diff --git a/praclib/temp/process.openup.base/capabilitypatterns/inception_phase_iteration/model.xmi b/praclib/temp/process.openup.base/capabilitypatterns/inception_phase_iteration/model.xmi
new file mode 100644
index 0000000..15f4a7d
--- /dev/null
+++ b/praclib/temp/process.openup.base/capabilitypatterns/inception_phase_iteration/model.xmi
@@ -0,0 +1,62 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_h3rlYdONEdyqlogshP8l4g"
+ guid="_h3rlYdONEdyqlogshP8l4g">
+ <resourceDescriptors xmi:id="_h3rlYtONEdyqlogshP8l4g" id="-SMF3QeQbQRdkgCVMy0OpuQ"
+ uri="content.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:ProcessComponent xmi:id="_h0Gs8NONEdyqlogshP8l4g" name="inception_phase_iteration"
+ guid="_h0Gs8NONEdyqlogshP8l4g">
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_nfpeANOOEdyqlogshP8l4g"
+ name="initiate_project" guid="_nfpeANOOEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_nfpeAdOOEdyqlogshP8l4g"
+ name="initiate_project" guid="_nfpeAdOOEdyqlogshP8l4g" superActivities="_h0Gs8dONEdyqlogshP8l4g"
+ variabilityType="extends">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://_eWxZgNOEEdyqlogshP8l4g#_eWxZgdOEEdyqlogshP8l4g"/>
+ </processElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_uxDPENOOEdyqlogshP8l4g"
+ name="plan_manage_iteration" guid="_uxDPENOOEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_uxDPEdOOEdyqlogshP8l4g"
+ name="plan_manage_iteration" guid="_uxDPEdOOEdyqlogshP8l4g" superActivities="_h0Gs8dONEdyqlogshP8l4g"
+ variabilityType="extends">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://_oZgCsNOEEdyqlogshP8l4g#_oZgCsdOEEdyqlogshP8l4g"/>
+ </processElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_vyeP0NOOEdyqlogshP8l4g"
+ name="identify_and_refine_requirements" guid="_vyeP0NOOEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_vyeP0dOOEdyqlogshP8l4g"
+ name="identify_and_refine_requirements" guid="_vyeP0dOOEdyqlogshP8l4g" superActivities="_h0Gs8dONEdyqlogshP8l4g"
+ linkToPredecessor="_Ba3L8NQVEdyk9oc_L5Vk0g" variabilityType="extends">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://_xxcpgNOEEdyqlogshP8l4g#_xxcpgdOEEdyqlogshP8l4g"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_Ba3L8NQVEdyk9oc_L5Vk0g"
+ guid="_Ba3L8NQVEdyk9oc_L5Vk0g" pred="_nfpeAdOOEdyqlogshP8l4g"/>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_w-Bc8NOOEdyqlogshP8l4g"
+ name="agree_technical_approach" guid="_w-Bc8NOOEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_w-Bc8dOOEdyqlogshP8l4g"
+ name="agree_technical_approach" guid="_w-Bc8dOOEdyqlogshP8l4g" superActivities="_h0Gs8dONEdyqlogshP8l4g"
+ linkToPredecessor="_BbnZ4NQVEdyk9oc_L5Vk0g" variabilityType="extends">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://_4ouDUNOEEdyqlogshP8l4g#_4ouDUdOEEdyqlogshP8l4g"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_BbnZ4NQVEdyk9oc_L5Vk0g"
+ guid="_BbnZ4NQVEdyk9oc_L5Vk0g" pred="_nfpeAdOOEdyqlogshP8l4g"/>
+ </childPackages>
+ <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_h0Gs8dONEdyqlogshP8l4g"
+ name="inception_phase_iteration" guid="_h0Gs8dONEdyqlogshP8l4g" briefDescription="This iteration template defines the activities (and associated roles and work products) performed in a typical iteration in the Inception phase."
+ presentationName="Inception Phase Iteration" breakdownElements="_nfpeAdOOEdyqlogshP8l4g _uxDPEdOOEdyqlogshP8l4g _vyeP0dOOEdyqlogshP8l4g _w-Bc8dOOEdyqlogshP8l4g">
+ <presentation xmi:id="-SMF3QeQbQRdkgCVMy0OpuQ" href="uma://-SMF3QeQbQRdkgCVMy0OpuQ#-SMF3QeQbQRdkgCVMy0OpuQ"/>
+ <defaultContext href="uma://_0NAjrNUAEdylRpA9TBY1SQ#_gExDwNQxEdyk9oc_L5Vk0g"/>
+ <validContext href="uma://_0NAjrNUAEdylRpA9TBY1SQ#_gExDwNQxEdyk9oc_L5Vk0g"/>
+ </process>
+ </org.eclipse.epf.uma:ProcessComponent>
+</xmi:XMI>
diff --git a/praclib/temp/process.openup.base/capabilitypatterns/initiate_project/content.xmi b/praclib/temp/process.openup.base/capabilitypatterns/initiate_project/content.xmi
new file mode 100644
index 0000000..da8032d
--- /dev/null
+++ b/praclib/temp/process.openup.base/capabilitypatterns/initiate_project/content.xmi
@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:ProcessDescription 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="-kpXvvHptrggypeoQEamfhw"
+ name="initiate_project,_eWxZgdOEEdyqlogshP8l4g" guid="-kpXvvHptrggypeoQEamfhw"
+ version="7.2.0">
+ <mainDescription><p>
+ This activity takes place at the beginning of the first iteration, when the project starts. The goal of this activity
+ is to establish the vision for both the project and the project plan at a high level of granularity.
+</p>
+<p>
+ The people in the roles involved at this time collaborate to perform this activity:
+</p>
+<ul>
+ <li>
+ The <a class="elementlinkwithusertext" href="./../../core.default.role_def.base/roles/analyst_39D7C49B.html"
+ guid="_0VxJsMlgEdmt3adZL5Dmdw">Analyst</a> and <a class="elementlinkwithusertext"
+ href="./../../core.default.role_def.base/roles/stakeholder_9FFD4106.html"
+ guid="_dTa6gMAYEdqX-s4mWhkyqQ">Stakeholder</a> roles work together to define the <a class="elementLinkWithUserText"
+ href="./../../core.tech.common.base/workproducts/vision_2E71B03C.html" guid="_0WVxcMlgEdmt3adZL5Dmdw">vision</a>
+ for the project, capturing the customer needs and features for the system under development. Needs and features are
+ captured to the extent required to reach agreement about the scope of the project.
+ </li>
+ <li>
+ The project manager (collaborating and reaching agreement with the development team and stakeholders) proposes a
+ high-level <a class="elementLinkWithUserText"
+ href="./../../practice.mgmt.two_level_project_planning.base/workproducts/project_plan_1CDBB7E4.html"
+ guid="_0a6vcMlgEdmt3adZL5Dmdw">project plan</a> that includes the <a class="elementLinkWithUserText"
+ href="./../../practice.mgmt.risk_value_lifecycle.base/guidances/concepts/phase_milestones_5678231E.html"
+ guid="_HNxbwMBJEdqSgKaj2SZBmg">milestones</a> for the four phases, and time-boxed iterations for each phase. This
+ plan, along with the allocation of staff to the project, evolves throughout the phases and defines the pace of the
+ project.
+ </li>
+</ul></mainDescription>
+</org.eclipse.epf.uma:ProcessDescription>
diff --git a/praclib/temp/process.openup.base/capabilitypatterns/initiate_project/model.xmi b/praclib/temp/process.openup.base/capabilitypatterns/initiate_project/model.xmi
new file mode 100644
index 0000000..2a0e252
--- /dev/null
+++ b/praclib/temp/process.openup.base/capabilitypatterns/initiate_project/model.xmi
@@ -0,0 +1,86 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_eZJ_INOEEdyqlogshP8l4g"
+ guid="_eZJ_INOEEdyqlogshP8l4g">
+ <resourceDescriptors xmi:id="_eZJ_IdOEEdyqlogshP8l4g" id="-kpXvvHptrggypeoQEamfhw"
+ uri="content.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:ProcessComponent xmi:id="_eWxZgNOEEdyqlogshP8l4g" name="initiate_project"
+ guid="_eWxZgNOEEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_sopKYNOJEdyqlogshP8l4g"
+ name="develop_technical_vision" guid="_sopKYNOJEdyqlogshP8l4g" presentationName="Develop Technical Vision"
+ superActivities="_eWxZgdOEEdyqlogshP8l4g" additionallyPerformedBy="_soyUUdOJEdyqlogshP8l4g _soyUUtOJEdyqlogshP8l4g _soyUU9OJEdyqlogshP8l4g"
+ optionalInput="_soyUVNOJEdyqlogshP8l4g" output="_soyUVNOJEdyqlogshP8l4g" performedPrimarilyBy="_soyUUNOJEdyqlogshP8l4g">
+ <Task href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_0fOAoMlgEdmt3adZL5Dmdw"/>
+ <selectedSteps href="uma://_5rJ78Lj3Edmy88CC3LfB_w#_ceK-UED2EdyoefaQkqWN_Q"/>
+ <selectedSteps href="uma://_5rJ78Lj3Edmy88CC3LfB_w#_h7AacED2EdyoefaQkqWN_Q"/>
+ <selectedSteps href="uma://_5rJ78Lj3Edmy88CC3LfB_w#_vbkccED2EdyoefaQkqWN_Q"/>
+ <selectedSteps href="uma://_5rJ78Lj3Edmy88CC3LfB_w#_yeVC0ED2EdyoefaQkqWN_Q"/>
+ <selectedSteps href="uma://_5rJ78Lj3Edmy88CC3LfB_w#_6uIV0ED2EdyoefaQkqWN_Q"/>
+ <selectedSteps href="uma://_5rJ78Lj3Edmy88CC3LfB_w#__nDMkED2EdyoefaQkqWN_Q"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_soyUUNOJEdyqlogshP8l4g"
+ name="analyst" guid="_soyUUNOJEdyqlogshP8l4g" presentationName="Analyst" isPlanned="false"
+ superActivities="_eWxZgdOEEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0VxJsMlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_soyUUdOJEdyqlogshP8l4g"
+ name="architect" guid="_soyUUdOJEdyqlogshP8l4g" presentationName="Architect"
+ isPlanned="false" superActivities="_eWxZgdOEEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0X9iEMlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_soyUUtOJEdyqlogshP8l4g"
+ name="project_manager" guid="_soyUUtOJEdyqlogshP8l4g" presentationName="Project Manager"
+ isPlanned="false" superActivities="_eWxZgdOEEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0a0o0MlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_soyUU9OJEdyqlogshP8l4g"
+ name="stakeholder" guid="_soyUU9OJEdyqlogshP8l4g" presentationName="Stakeholder"
+ isPlanned="false" superActivities="_eWxZgdOEEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_dTa6gMAYEdqX-s4mWhkyqQ"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_soyUVNOJEdyqlogshP8l4g"
+ name="vision" guid="_soyUVNOJEdyqlogshP8l4g" presentationName="Vision" isPlanned="false"
+ superActivities="_eWxZgdOEEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0WVxcMlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_t7pDUNOJEdyqlogshP8l4g"
+ name="plan_the_project" guid="_t7pDUNOJEdyqlogshP8l4g" presentationName="Plan Project"
+ superActivities="_eWxZgdOEEdyqlogshP8l4g" additionallyPerformedBy="_soyUUNOJEdyqlogshP8l4g _soyUUdOJEdyqlogshP8l4g _t7pDUdOJEdyqlogshP8l4g _soyUU9OJEdyqlogshP8l4g _t7pDUtOJEdyqlogshP8l4g"
+ mandatoryInput="_tzWYwNnFEdyNWvE4rz3mXQ" performedPrimarilyBy="_soyUUtOJEdyqlogshP8l4g">
+ <Task href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_0lC70MlgEdmt3adZL5Dmdw"/>
+ <selectedSteps href="uma://_fPbdIKe2Edmzde8VFK5bxg#_gu-PgIyBEdyhZb-MhCJrlA"/>
+ <selectedSteps href="uma://_fPbdIKe2Edmzde8VFK5bxg#_jknm8IyBEdyhZb-MhCJrlA"/>
+ <selectedSteps href="uma://_fPbdIKe2Edmzde8VFK5bxg#_lrYj0MBAEdqSgKaj2SZBmg"/>
+ <selectedSteps href="uma://_fPbdIKe2Edmzde8VFK5bxg#_uu1coIyBEdyhZb-MhCJrlA"/>
+ <selectedSteps href="uma://_fPbdIKe2Edmzde8VFK5bxg#_xWBhUIyBEdyhZb-MhCJrlA"/>
+ <selectedSteps href="uma://_fPbdIKe2Edmzde8VFK5bxg#_zeN84IyBEdyhZb-MhCJrlA"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_t7pDUdOJEdyqlogshP8l4g"
+ name="developer" guid="_t7pDUdOJEdyqlogshP8l4g" presentationName="Developer"
+ isPlanned="false" superActivities="_eWxZgdOEEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_t7pDUtOJEdyqlogshP8l4g"
+ name="tester" guid="_t7pDUtOJEdyqlogshP8l4g" presentationName="Tester" isPlanned="false"
+ superActivities="_eWxZgdOEEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0ZM4MclgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_tzWYwNnFEdyNWvE4rz3mXQ"
+ name="technical_specification_slot" guid="_tzWYwNnFEdyNWvE4rz3mXQ" presentationName="[Technical Specification]"
+ isPlanned="false" superActivities="_eWxZgdOEEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_i3vkoLS-EduDY8LNbMCDBA"/>
+ </processElements>
+ <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_eWxZgdOEEdyqlogshP8l4g"
+ name="initiate_project" guid="_eWxZgdOEEdyqlogshP8l4g" briefDescription="Kick off the project and gain agreement with the stakeholders on the scope of the project, and an initial plan for achieving it. This activity bundles tasks required to define the vision and create a project plan."
+ presentationName="Initiate Project" breakdownElements="_sopKYNOJEdyqlogshP8l4g _soyUUNOJEdyqlogshP8l4g _soyUUdOJEdyqlogshP8l4g _soyUUtOJEdyqlogshP8l4g _soyUU9OJEdyqlogshP8l4g _soyUVNOJEdyqlogshP8l4g _t7pDUNOJEdyqlogshP8l4g _t7pDUdOJEdyqlogshP8l4g _t7pDUtOJEdyqlogshP8l4g _tzWYwNnFEdyNWvE4rz3mXQ">
+ <presentation xmi:id="-kpXvvHptrggypeoQEamfhw" href="uma://-kpXvvHptrggypeoQEamfhw#-kpXvvHptrggypeoQEamfhw"/>
+ <defaultContext href="uma://_Sw_vnNnREdyNj6EOmqy5Rg#_gExDwNQxEdyk9oc_L5Vk0g"/>
+ <validContext href="uma://_Sw_vnNnREdyNj6EOmqy5Rg#_gExDwNQxEdyk9oc_L5Vk0g"/>
+ </process>
+ </org.eclipse.epf.uma:ProcessComponent>
+</xmi:XMI>
diff --git a/praclib/temp/process.openup.base/capabilitypatterns/ongoing_tasks/content.xmi b/praclib/temp/process.openup.base/capabilitypatterns/ongoing_tasks/content.xmi
new file mode 100644
index 0000000..27f50f5
--- /dev/null
+++ b/praclib/temp/process.openup.base/capabilitypatterns/ongoing_tasks/content.xmi
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:ProcessDescription 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="-aXudKqi6rjimd3UsF0smZA"
+ name="ongoing_tasks,__ZInMdOEEdyqlogshP8l4g" guid="-aXudKqi6rjimd3UsF0smZA" version="7.2.0">
+ <mainDescription><p>
+ This activity includes a single task, <a class="elementLink"
+ href="./../../legacy.practice.mgmt.chg_mgmt.base/tasks/request_change_A048C387.html"
+ guid="_0mwzEclgEdmt3adZL5Dmdw">Request Change</a>. This task may occur any time during the lifecycle in response to an
+ observed defect, a desired enhancement, or a change request. It is not planned, which means that it does not appear as
+ a scheduled activity on the project plan, iteration plan, or work items list. Nevertheless, it is a critical activity
+ that must be performed to ensure project success, because your environment is not static.
+</p>
+<p>
+ <a class="elementLink" href="./../../core.default.role_def.base/roles/any_role_C36B701F.html"
+ guid="_0dsWoMlgEdmt3adZL5Dmdw">Any Role</a> may perform this task, however the most common sources of <a
+ class="elementLink" href="./../../legacy.practice.mgmt.chg_mgmt.base/guidances/concepts/change_requests_AD4868FE.html"
+ guid="_6jdvECb3Edqh1LYUOGRh2A">Change Requests</a> are <a class="elementLink"
+ href="./../../core.default.role_def.base/roles/stakeholder_9FFD4106.html"
+ guid="_dTa6gMAYEdqX-s4mWhkyqQ">Stakeholder</a>s (enhancement requests and change requests) and <a class="elementLink"
+ href="./../../core.default.role_def.base/roles/tester_9859B590.html" guid="_0ZM4MclgEdmt3adZL5Dmdw">Tester</a>s (defect
+ reports).
+</p></mainDescription>
+</org.eclipse.epf.uma:ProcessDescription>
diff --git a/praclib/temp/process.openup.base/capabilitypatterns/ongoing_tasks/model.xmi b/praclib/temp/process.openup.base/capabilitypatterns/ongoing_tasks/model.xmi
new file mode 100644
index 0000000..e893bbb
--- /dev/null
+++ b/praclib/temp/process.openup.base/capabilitypatterns/ongoing_tasks/model.xmi
@@ -0,0 +1,35 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="__ctfodOEEdyqlogshP8l4g"
+ guid="__ctfodOEEdyqlogshP8l4g">
+ <resourceDescriptors xmi:id="__ctfotOEEdyqlogshP8l4g" id="-aXudKqi6rjimd3UsF0smZA"
+ uri="content.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:ProcessComponent xmi:id="__ZInMNOEEdyqlogshP8l4g" name="ongoing_tasks"
+ guid="__ZInMNOEEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_HGqkMNnTEdyNj6EOmqy5Rg"
+ name="request_change" guid="_HGqkMNnTEdyNj6EOmqy5Rg" presentationName="Request Change"
+ superActivities="__ZInMdOEEdyqlogshP8l4g" optionalInput="_HGqkMdnTEdyNj6EOmqy5Rg"
+ output="_HGqkMdnTEdyNj6EOmqy5Rg">
+ <Task href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_0mwzEclgEdmt3adZL5Dmdw"/>
+ <selectedSteps href="uma://_Nr0S4KeqEdmKDbQuyzCoqQ#_qEkewKuoEdmEGLSmmpF1Sg"/>
+ <selectedSteps href="uma://_Nr0S4KeqEdmKDbQuyzCoqQ#_r2aP0KuoEdmEGLSmmpF1Sg"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_HGqkMdnTEdyNj6EOmqy5Rg"
+ name="work_items_list" guid="_HGqkMdnTEdyNj6EOmqy5Rg" presentationName="Work Items List"
+ isPlanned="false" superActivities="__ZInMdOEEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_rGNWsCbSEdqh1LYUOGRh2A"/>
+ </processElements>
+ <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="__ZInMdOEEdyqlogshP8l4g"
+ name="ongoing_tasks" guid="__ZInMdOEEdyqlogshP8l4g" briefDescription="Perform ongoing tasks that are not necessarily part of the project schedule."
+ presentationName="Ongoing Tasks" breakdownElements="_HGqkMNnTEdyNj6EOmqy5Rg _HGqkMdnTEdyNj6EOmqy5Rg">
+ <presentation xmi:id="-aXudKqi6rjimd3UsF0smZA" href="uma://-aXudKqi6rjimd3UsF0smZA#-aXudKqi6rjimd3UsF0smZA"/>
+ <defaultContext href="uma://_Sw_vnNnREdyNj6EOmqy5Rg#_gExDwNQxEdyk9oc_L5Vk0g"/>
+ <validContext href="uma://_Sw_vnNnREdyNj6EOmqy5Rg#_gExDwNQxEdyk9oc_L5Vk0g"/>
+ </process>
+ </org.eclipse.epf.uma:ProcessComponent>
+</xmi:XMI>
diff --git a/praclib/temp/process.openup.base/capabilitypatterns/plan_manage_iteration/content.xmi b/praclib/temp/process.openup.base/capabilitypatterns/plan_manage_iteration/content.xmi
new file mode 100644
index 0000000..8915feb
--- /dev/null
+++ b/praclib/temp/process.openup.base/capabilitypatterns/plan_manage_iteration/content.xmi
@@ -0,0 +1,40 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:ProcessDescription 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="-b6sTuOuA7eFhaR_H3EfgBw"
+ name="plan_manage_iteration,_oZgCsdOEEdyqlogshP8l4g" guid="-b6sTuOuA7eFhaR_H3EfgBw"
+ version="7.2.0">
+ <mainDescription><p>
+ This activity is performed throughout the project lifecycle. The goal of this activity is to identify risks and issues
+ early enough that they can be mitigated, to establish the goals for the iteration, and to support the development team
+ in reaching these goals.
+</p>
+<p>
+ The <a class="elementlinkwithusertext" href="./../../core.default.role_def.base/roles/project_manager_E657F936.html"
+ guid="_0a0o0MlgEdmt3adZL5Dmdw">project manager</a> and the team launch the iteration. The prioritization of work for a
+ given iteration takes place. The project manager, <a class="elementlinkwithusertext"
+ href="./../../core.default.role_def.base/roles/stakeholder_9FFD4106.html"
+ guid="_dTa6gMAYEdqX-s4mWhkyqQ">stakeholders</a>, and team members agree on what is supposed to be developed during that
+ iteration.
+</p>
+<p>
+ Team members sign up for the work items they will develop in that iteration. Each team member breaks down the work
+ items into development tasks and estimates the effort. This provides a more accurate estimate of the amount of time
+ that will be spent, and of what can be realistically achieved, in a given iteration.
+</p>
+<p>
+ As the iteration runs, the team meets regularly to report status of work completed, the work to do next, and issues
+ blocking the progress. In some projects, this status checking occurs in daily meetings, which allows for a more precise
+ understanding of how the work in an iteration is progressing. As necessary, the team makes corrections to achieve what
+ was planned. The overall idea is that risks and issues are identified and managed throughout the iteration, and
+ everyone knows the project status in a timely manner.
+</p>
+<p>
+ During iteration assessments, the key success criterion is the demonstration that planned functionality has been
+ implemented. Lessons learned are captured in order to modify the project or improve the process. If the iteration end
+ coincides with the phase end, make sure the objectives for that phase have been met (see <a class="elementLinkWithType"
+ href="./../../practice.mgmt.risk_value_lifecycle.base/guidances/concepts/phase_milestones_5678231E.html"
+ guid="_HNxbwMBJEdqSgKaj2SZBmg">Concept: Phase Milestones</a> for more information).
+</p></mainDescription>
+</org.eclipse.epf.uma:ProcessDescription>
diff --git a/praclib/temp/process.openup.base/capabilitypatterns/plan_manage_iteration/model.xmi b/praclib/temp/process.openup.base/capabilitypatterns/plan_manage_iteration/model.xmi
new file mode 100644
index 0000000..c2c5243
--- /dev/null
+++ b/praclib/temp/process.openup.base/capabilitypatterns/plan_manage_iteration/model.xmi
@@ -0,0 +1,118 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_ob4oUdOEEdyqlogshP8l4g"
+ guid="_ob4oUdOEEdyqlogshP8l4g">
+ <resourceDescriptors xmi:id="_ob4oUtOEEdyqlogshP8l4g" id="-b6sTuOuA7eFhaR_H3EfgBw"
+ uri="content.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:ProcessComponent xmi:id="_oZgCsNOEEdyqlogshP8l4g" name="plan_manage_iteration"
+ guid="_oZgCsNOEEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_y05RQNOJEdyqlogshP8l4g"
+ name="plan_iteration" guid="_y05RQNOJEdyqlogshP8l4g" presentationName="Plan Iteration"
+ superActivities="_oZgCsdOEEdyqlogshP8l4g" additionallyPerformedBy="_y1CbMdOJEdyqlogshP8l4g _y1CbMtOJEdyqlogshP8l4g _y1CbM9OJEdyqlogshP8l4g _y1CbNNOJEdyqlogshP8l4g _y1CbNdOJEdyqlogshP8l4g"
+ mandatoryInput="_y1MMMNOJEdyqlogshP8l4g _y1MMMdOJEdyqlogshP8l4g _y1MMMtOJEdyqlogshP8l4g"
+ optionalInput="_y1MMM9OJEdyqlogshP8l4g _LxTaQNnGEdyNWvE4rz3mXQ" performedPrimarilyBy="_y1CbMNOJEdyqlogshP8l4g">
+ <Task href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_0keUEMlgEdmt3adZL5Dmdw"/>
+ <selectedSteps href="uma://_Wk7noKe1EdmGSrcKGOYDGg#_7bz7AIyAEdyhZb-MhCJrlA"/>
+ <selectedSteps href="uma://_Wk7noKe1EdmGSrcKGOYDGg#_-wJZkIyAEdyhZb-MhCJrlA"/>
+ <selectedSteps href="uma://_Wk7noKe1EdmGSrcKGOYDGg#_CtKCMMBHEdqSgKaj2SZBmg"/>
+ <selectedSteps href="uma://_Wk7noKe1EdmGSrcKGOYDGg#_307v0MMsEdmdo9HxCRR_Gw"/>
+ <selectedSteps href="uma://_Wk7noKe1EdmGSrcKGOYDGg#_HzNVgIyBEdyhZb-MhCJrlA"/>
+ <selectedSteps href="uma://_Wk7noKe1EdmGSrcKGOYDGg#_7Hqr4MMsEdmdo9HxCRR_Gw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_y1CbMNOJEdyqlogshP8l4g"
+ name="project_manager" guid="_y1CbMNOJEdyqlogshP8l4g" presentationName="Project Manager"
+ isPlanned="false" superActivities="_oZgCsdOEEdyqlogshP8l4g" responsibleFor="_y1MMMtOJEdyqlogshP8l4g _y1MMMdOJEdyqlogshP8l4g _y1MMMNOJEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0a0o0MlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_y1CbMdOJEdyqlogshP8l4g"
+ name="analyst" guid="_y1CbMdOJEdyqlogshP8l4g" presentationName="Analyst" isPlanned="false"
+ superActivities="_oZgCsdOEEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0VxJsMlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_y1CbMtOJEdyqlogshP8l4g"
+ name="architect" guid="_y1CbMtOJEdyqlogshP8l4g" presentationName="Architect"
+ isPlanned="false" superActivities="_oZgCsdOEEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0X9iEMlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_y1CbM9OJEdyqlogshP8l4g"
+ name="developer" guid="_y1CbM9OJEdyqlogshP8l4g" presentationName="Developer"
+ isPlanned="false" superActivities="_oZgCsdOEEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_y1CbNNOJEdyqlogshP8l4g"
+ name="stakeholder" guid="_y1CbNNOJEdyqlogshP8l4g" presentationName="Stakeholder"
+ isPlanned="false" superActivities="_oZgCsdOEEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_dTa6gMAYEdqX-s4mWhkyqQ"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_y1CbNdOJEdyqlogshP8l4g"
+ name="tester" guid="_y1CbNdOJEdyqlogshP8l4g" presentationName="Tester" isPlanned="false"
+ superActivities="_oZgCsdOEEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0ZM4MclgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_y1MMMNOJEdyqlogshP8l4g"
+ name="iteration_plan" guid="_y1MMMNOJEdyqlogshP8l4g" presentationName="Iteration Plan"
+ isPlanned="false" superActivities="_oZgCsdOEEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_0aQBEslgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_y1MMMdOJEdyqlogshP8l4g"
+ name="risk_list" guid="_y1MMMdOJEdyqlogshP8l4g" presentationName="Risk List"
+ isPlanned="false" superActivities="_oZgCsdOEEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_Ckay8Cc_EduIsqH1Q6ZuqA"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_y1MMMtOJEdyqlogshP8l4g"
+ name="work_items_list" guid="_y1MMMtOJEdyqlogshP8l4g" presentationName="Work Items List"
+ isPlanned="false" superActivities="_oZgCsdOEEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_rGNWsCbSEdqh1LYUOGRh2A"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_y1MMM9OJEdyqlogshP8l4g"
+ name="technical_architecture_slot" guid="_y1MMM9OJEdyqlogshP8l4g" presentationName="[Technical Architecture]"
+ isPlanned="false" superActivities="_oZgCsdOEEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_8OD-cLPTEduocbW-TPTq7A"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_zjF0ANOJEdyqlogshP8l4g"
+ name="manage_iteration" guid="_zjF0ANOJEdyqlogshP8l4g" presentationName="Manage Iteration"
+ superActivities="_oZgCsdOEEdyqlogshP8l4g" additionallyPerformedBy="_y1CbMdOJEdyqlogshP8l4g _y1CbMtOJEdyqlogshP8l4g _y1CbM9OJEdyqlogshP8l4g _y1CbNNOJEdyqlogshP8l4g _y1CbNdOJEdyqlogshP8l4g"
+ mandatoryInput="_y1MMMNOJEdyqlogshP8l4g _y1MMMdOJEdyqlogshP8l4g _y1MMMtOJEdyqlogshP8l4g"
+ output="_y1MMMNOJEdyqlogshP8l4g _y1MMMdOJEdyqlogshP8l4g _y1MMMtOJEdyqlogshP8l4g"
+ performedPrimarilyBy="_y1CbMNOJEdyqlogshP8l4g">
+ <Task href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_8S2aICbYEdqh1LYUOGRh2A"/>
+ <selectedSteps href="uma://-PbfqVxB_j9KN-Jx39_pEUA#_OE65ICuxEdqTIKp3l5PtzQ"/>
+ <selectedSteps href="uma://-PbfqVxB_j9KN-Jx39_pEUA#_oIZdkCbZEdqh1LYUOGRh2A"/>
+ <selectedSteps href="uma://-PbfqVxB_j9KN-Jx39_pEUA#_xiFJwCbZEdqh1LYUOGRh2A"/>
+ <selectedSteps href="uma://-PbfqVxB_j9KN-Jx39_pEUA#_Br6VECuxEdqTIKp3l5PtzQ"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_0Qiv4NOJEdyqlogshP8l4g"
+ name="assess_results" guid="_0Qiv4NOJEdyqlogshP8l4g" presentationName="Assess Results"
+ superActivities="_oZgCsdOEEdyqlogshP8l4g" additionallyPerformedBy="_y1CbMdOJEdyqlogshP8l4g _y1CbMtOJEdyqlogshP8l4g _y1CbM9OJEdyqlogshP8l4g _y1CbNNOJEdyqlogshP8l4g _y1CbNdOJEdyqlogshP8l4g"
+ mandatoryInput="_y1MMMNOJEdyqlogshP8l4g _y1MMMtOJEdyqlogshP8l4g" optionalInput="_LxTaQNnGEdyNWvE4rz3mXQ _LxTaQdnGEdyNWvE4rz3mXQ"
+ performedPrimarilyBy="_y1CbMNOJEdyqlogshP8l4g">
+ <Task href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_0l53cMlgEdmt3adZL5Dmdw"/>
+ <selectedSteps href="uma://_a3uz4LBYEdm7Eph_l9Cn9w#_o28GgMMsEdmdo9HxCRR_Gw"/>
+ <selectedSteps href="uma://_a3uz4LBYEdm7Eph_l9Cn9w#_iSiDEIx4Edyzd4h-mxj9YA"/>
+ <selectedSteps href="uma://_a3uz4LBYEdm7Eph_l9Cn9w#_iL7cQEpqEdup0IY9DKDPkg"/>
+ <selectedSteps href="uma://_a3uz4LBYEdm7Eph_l9Cn9w#_1YHH8DLqEdueZPye-FaNgA"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_LxTaQNnGEdyNWvE4rz3mXQ"
+ name="technical_specification_slot" guid="_LxTaQNnGEdyNWvE4rz3mXQ" presentationName="[Technical Specification]"
+ isPlanned="false" superActivities="_oZgCsdOEEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_i3vkoLS-EduDY8LNbMCDBA"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_LxTaQdnGEdyNWvE4rz3mXQ"
+ name="technical_test_results_slot" guid="_LxTaQdnGEdyNWvE4rz3mXQ" presentationName="[Technical Test Results]"
+ isPlanned="false" superActivities="_oZgCsdOEEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_fahB0EfUEdyiPI8btkmvmw"/>
+ </processElements>
+ <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_oZgCsdOEEdyqlogshP8l4g"
+ name="plan_manage_iteration" guid="_oZgCsdOEEdyqlogshP8l4g" briefDescription="Initiate the iteration and allow team members to sign up for development tasks. Monitor and communicate project status to external stakeholders. Identify and handle exceptions and problems."
+ presentationName="Plan and Manage Iteration" breakdownElements="_y05RQNOJEdyqlogshP8l4g _y1CbMNOJEdyqlogshP8l4g _y1CbMdOJEdyqlogshP8l4g _y1CbMtOJEdyqlogshP8l4g _y1CbM9OJEdyqlogshP8l4g _y1CbNNOJEdyqlogshP8l4g _y1CbNdOJEdyqlogshP8l4g _y1MMMNOJEdyqlogshP8l4g _y1MMMdOJEdyqlogshP8l4g _y1MMMtOJEdyqlogshP8l4g _y1MMM9OJEdyqlogshP8l4g _zjF0ANOJEdyqlogshP8l4g _0Qiv4NOJEdyqlogshP8l4g _LxTaQNnGEdyNWvE4rz3mXQ _LxTaQdnGEdyNWvE4rz3mXQ">
+ <presentation xmi:id="-b6sTuOuA7eFhaR_H3EfgBw" href="uma://-b6sTuOuA7eFhaR_H3EfgBw#-b6sTuOuA7eFhaR_H3EfgBw"/>
+ <defaultContext href="uma://_Sw_vnNnREdyNj6EOmqy5Rg#_gExDwNQxEdyk9oc_L5Vk0g"/>
+ <validContext href="uma://_Sw_vnNnREdyNj6EOmqy5Rg#_gExDwNQxEdyk9oc_L5Vk0g"/>
+ </process>
+ </org.eclipse.epf.uma:ProcessComponent>
+</xmi:XMI>
diff --git a/praclib/temp/process.openup.base/capabilitypatterns/test_solution/content.xmi b/praclib/temp/process.openup.base/capabilitypatterns/test_solution/content.xmi
new file mode 100644
index 0000000..473cd0a
--- /dev/null
+++ b/praclib/temp/process.openup.base/capabilitypatterns/test_solution/content.xmi
@@ -0,0 +1,39 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:ProcessDescription 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="--GUCGSJomnx0WV9XKvVyXQ"
+ name="test_solution,_buG4sdOFEdyqlogshP8l4g" guid="--GUCGSJomnx0WV9XKvVyXQ" version="7.2.0">
+ <mainDescription><p>
+ This activity is repeated throughout the project lifecycle. The main goal of this activity is to validate that the
+ current build of the system satisfies the requirements allocated to it.
+</p>
+<p>
+ Throughout the iterations, your intent is to validate that the implemented requirements reflect a robust architecture,
+ and that the remaining requirements are consistently implemented on top of that architecture. As developers implement
+ the solution for the requirements in a given iteration, unit test the integrated source code. Then, a <a
+ class="elementlinkwithusertext" href="./../../core.default.role_def.base/roles/tester_9859B590.html"
+ guid="_0ZM4MclgEdmt3adZL5Dmdw">tester</a> conducts system-level testing in parallel with development to make sure that
+ the solution, which is continuously being integrated, satisfies the intent specified in the test cases. The tester
+ defines what techniques to use, what the data input is, and what <a class="elementLinkWithUserText"
+ href="./../../core.tech.common.base/guidances/guidelines/test_suite_D54EEBED.html" guid="_0aDz0MlgEdmt3adZL5Dmdw">test
+ suites</a> to create. As tests run, defects are identified and added to the <a class="elementLinkWithUserText"
+ href="./../../practice.mgmt.iterative_dev.base/workproducts/work_items_list_39D03CC8.html"
+ guid="_rGNWsCbSEdqh1LYUOGRh2A">work items list</a>, so that they can be prioritized as part of the work that you will
+ do during iterations.
+</p>
+<p>
+ <a class="elementLinkWithType" href="./../../core.default.role_def.base/roles/stakeholder_9FFD4106.html"
+ guid="_dTa6gMAYEdqX-s4mWhkyqQ">Role: Stakeholder</a>s and end-users also may also be involved in performing tests to
+ accept the release.
+</p></mainDescription>
+ <purpose>Develop and run test scripts to validate that the system satisfies the requirements.</purpose>
+ <howtoStaff><p>
+ The staff performing this activity must be integrated into the team.
+</p></howtoStaff>
+ <usageNotes><p>
+ Testing must occur throughout the process and throughout each iteration. Testing is not a final inspection to be
+ performed at the end of the project. As requirements are implemented and integrated into a build, you should test them
+ as soon as possible.
+</p></usageNotes>
+</org.eclipse.epf.uma:ProcessDescription>
diff --git a/praclib/temp/process.openup.base/capabilitypatterns/test_solution/model.xmi b/praclib/temp/process.openup.base/capabilitypatterns/test_solution/model.xmi
new file mode 100644
index 0000000..51ba612
--- /dev/null
+++ b/praclib/temp/process.openup.base/capabilitypatterns/test_solution/model.xmi
@@ -0,0 +1,87 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_bwfeUdOFEdyqlogshP8l4g"
+ guid="_bwfeUdOFEdyqlogshP8l4g">
+ <resourceDescriptors xmi:id="_bwfeUtOFEdyqlogshP8l4g" id="--GUCGSJomnx0WV9XKvVyXQ"
+ uri="content.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:ProcessComponent xmi:id="_buG4sNOFEdyqlogshP8l4g" name="test_solution"
+ guid="_buG4sNOFEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_Viv68NOLEdyqlogshP8l4g"
+ name="implement_tests" guid="_Viv68NOLEdyqlogshP8l4g" presentationName="Implement Tests"
+ superActivities="_buG4sdOFEdyqlogshP8l4g" additionallyPerformedBy="_Viv68tOLEdyqlogshP8l4g _Viv689OLEdyqlogshP8l4g _Viv69NOLEdyqlogshP8l4g"
+ mandatoryInput="_Vi5r8NOLEdyqlogshP8l4g" optionalInput="_Vi5r8dOLEdyqlogshP8l4g _Vi5r8tOLEdyqlogshP8l4g"
+ output="_Vi5r8dOLEdyqlogshP8l4g" performedPrimarilyBy="_Viv68dOLEdyqlogshP8l4g">
+ <Task href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_0jO98MlgEdmt3adZL5Dmdw"/>
+ <selectedSteps href="uma://_NrbRUKeqEdmKDbQuyzCoqQ#_A56NkKRKEdyLP-jEVj8Kyw"/>
+ <selectedSteps href="uma://_NrbRUKeqEdmKDbQuyzCoqQ#_WucQ4KRKEdyLP-jEVj8Kyw"/>
+ <selectedSteps href="uma://_NrbRUKeqEdmKDbQuyzCoqQ#_VN5M0KuSEdmhFZtkg1nakg"/>
+ <selectedSteps href="uma://_NrbRUKeqEdmKDbQuyzCoqQ#_WvBoYKuSEdmhFZtkg1nakg"/>
+ <selectedSteps href="uma://_NrbRUKeqEdmKDbQuyzCoqQ#_2IA70KRKEdyLP-jEVj8Kyw"/>
+ <selectedSteps href="uma://_NrbRUKeqEdmKDbQuyzCoqQ#_X0dmcKuSEdmhFZtkg1nakg"/>
+ <selectedSteps href="uma://_NrbRUKeqEdmKDbQuyzCoqQ#_ABwoIKRLEdyLP-jEVj8Kyw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_Viv68dOLEdyqlogshP8l4g"
+ name="tester" guid="_Viv68dOLEdyqlogshP8l4g" presentationName="Tester" isPlanned="false"
+ superActivities="_buG4sdOFEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0ZM4MclgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_Viv68tOLEdyqlogshP8l4g"
+ name="analyst" guid="_Viv68tOLEdyqlogshP8l4g" presentationName="Analyst" isPlanned="false"
+ superActivities="_buG4sdOFEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0VxJsMlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_Viv689OLEdyqlogshP8l4g"
+ name="developer" guid="_Viv689OLEdyqlogshP8l4g" presentationName="Developer"
+ isPlanned="false" superActivities="_buG4sdOFEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_0YDosMlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:RoleDescriptor" xmi:id="_Viv69NOLEdyqlogshP8l4g"
+ name="stakeholder" guid="_Viv69NOLEdyqlogshP8l4g" presentationName="Stakeholder"
+ isPlanned="false" superActivities="_buG4sdOFEdyqlogshP8l4g">
+ <Role href="uma://_A118oMYaEdyXeo04os5BOw#_dTa6gMAYEdqX-s4mWhkyqQ"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_Vi5r8NOLEdyqlogshP8l4g"
+ name="test_case" guid="_Vi5r8NOLEdyqlogshP8l4g" presentationName="Test Case"
+ isPlanned="false" superActivities="_buG4sdOFEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZS-0MlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_Vi5r8dOLEdyqlogshP8l4g"
+ name="test_script" guid="_Vi5r8dOLEdyqlogshP8l4g" presentationName="Test Script"
+ isPlanned="false" superActivities="_buG4sdOFEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZfMEMlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_Vi5r8tOLEdyqlogshP8l4g"
+ name="software_implementation_slot" guid="_Vi5r8tOLEdyqlogshP8l4g" presentationName="[Software Implementation]"
+ isPlanned="false" superActivities="_buG4sdOFEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_-bv0ELXuEduGP_98XMd0fg#_Vux8UEfUEdyiPI8btkmvmw"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:TaskDescriptor" xmi:id="_WttSMNOLEdyqlogshP8l4g"
+ name="run_tests" guid="_WttSMNOLEdyqlogshP8l4g" presentationName="Run Tests"
+ superActivities="_buG4sdOFEdyqlogshP8l4g" mandatoryInput="_Vi5r8dOLEdyqlogshP8l4g _Vi5r8tOLEdyqlogshP8l4g"
+ output="_WttSMdOLEdyqlogshP8l4g" performedPrimarilyBy="_Viv68dOLEdyqlogshP8l4g">
+ <Task href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_0jVEkMlgEdmt3adZL5Dmdw"/>
+ <selectedSteps href="uma://_NrbRUqeqEdmKDbQuyzCoqQ#_xVhnwKRLEdyLP-jEVj8Kyw"/>
+ <selectedSteps href="uma://_NrbRUqeqEdmKDbQuyzCoqQ#_1L1yAKRLEdyLP-jEVj8Kyw"/>
+ <selectedSteps href="uma://_NrbRUqeqEdmKDbQuyzCoqQ#_gV408KuSEdmhFZtkg1nakg"/>
+ <selectedSteps href="uma://_NrbRUqeqEdmKDbQuyzCoqQ#_sQaC4DO2EduqsLmIADMQ9g"/>
+ <selectedSteps href="uma://_NrbRUqeqEdmKDbQuyzCoqQ#_3t6oADO2EduqsLmIADMQ9g"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkProductDescriptor" xmi:id="_WttSMdOLEdyqlogshP8l4g"
+ name="test_log" guid="_WttSMdOLEdyqlogshP8l4g" presentationName="Test Log"
+ isPlanned="false" superActivities="_buG4sdOFEdyqlogshP8l4g">
+ <WorkProduct xsi:type="org.eclipse.epf.uma:Artifact" href="uma://_OOB2AAouEdyhlpBPrduOMw#_0ZlSsMlgEdmt3adZL5Dmdw"/>
+ </processElements>
+ <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_buG4sdOFEdyqlogshP8l4g"
+ name="test_solution" guid="_buG4sdOFEdyqlogshP8l4g" briefDescription="From a system perspective, test and evaluate the developed requirements."
+ presentationName="Test Solution" breakdownElements="_Viv68NOLEdyqlogshP8l4g _Viv68dOLEdyqlogshP8l4g _Viv68tOLEdyqlogshP8l4g _Viv689OLEdyqlogshP8l4g _Viv69NOLEdyqlogshP8l4g _Vi5r8NOLEdyqlogshP8l4g _Vi5r8dOLEdyqlogshP8l4g _Vi5r8tOLEdyqlogshP8l4g _WttSMNOLEdyqlogshP8l4g _WttSMdOLEdyqlogshP8l4g">
+ <presentation xmi:id="--GUCGSJomnx0WV9XKvVyXQ" href="uma://--GUCGSJomnx0WV9XKvVyXQ#--GUCGSJomnx0WV9XKvVyXQ"/>
+ <defaultContext href="uma://_Sw_vnNnREdyNj6EOmqy5Rg#_gExDwNQxEdyk9oc_L5Vk0g"/>
+ <validContext href="uma://_Sw_vnNnREdyNj6EOmqy5Rg#_gExDwNQxEdyk9oc_L5Vk0g"/>
+ </process>
+ </org.eclipse.epf.uma:ProcessComponent>
+</xmi:XMI>
diff --git a/praclib/temp/process.openup.base/capabilitypatterns/transition_phase_iteration/content.xmi b/praclib/temp/process.openup.base/capabilitypatterns/transition_phase_iteration/content.xmi
new file mode 100644
index 0000000..26eb35a
--- /dev/null
+++ b/praclib/temp/process.openup.base/capabilitypatterns/transition_phase_iteration/content.xmi
@@ -0,0 +1,85 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:ProcessDescription 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="-ybGHhzGQT4fXY7TTaBPxug"
+ name="transition_phase_iteration,_pzQU0dONEdyqlogshP8l4g" guid="-ybGHhzGQT4fXY7TTaBPxug"
+ version="7.2.0">
+ <mainDescription><p>
+ In the Transition phase, the main objectives are to fine-tune the functionality, performance, and overall quality of
+ the beta product from the end of the Construction phase.
+</p>
+<p>
+ The following table summarizes the&nbsp;Transition phase objectives and&nbsp;what activities address each objective:
+</p>
+<p align="center">
+ <strong>Transition phase objectives and activities</strong>
+</p><br />
+<br />
+<table cellspacing="0" cellpadding="0" width="648" align="center" border="1">
+ <tbody>
+ <tr>
+ <td class="Normal" valign="top" width="300">
+ <p style="TEXT-ALIGN: justify">
+ <b>Phase objectives</b>
+ </p>
+ </td>
+ <td class="Normal" valign="top" width="348">
+ <p style="TEXT-ALIGN: justify">
+ <b>Activities that address objectives</b>
+ </p>
+ </td>
+ </tr>
+ <tr>
+ <td class="Normal" valign="top" width="300" height="62">
+ Beta test to validate that user expectations are met
+ </td>
+ <td class="Normal" valign="top" width="348">
+ <p style="TEXT-ALIGN: justify">
+ <a class="elementLink"
+ href="./../../process.openup.base/capabilitypatterns/ongoing_tasks_CA154C21.html"
+ guid="__ZInMdOEEdyqlogshP8l4g">Ongoing Tasks</a>
+ </p>
+ <p style="TEXT-ALIGN: justify">
+ <a class="elementLink"
+ href="./../../process.openup.base/capabilitypatterns/develop_solution_4FBB0E6E.html"
+ guid="_RXGoodOFEdyqlogshP8l4g">Develop Solution Increment</a>
+ </p>
+ <p style="TEXT-ALIGN: justify">
+ <a class="elementLink"
+ href="./../../process.openup.base/capabilitypatterns/test_solution_D16D88FC.html"
+ guid="_buG4sdOFEdyqlogshP8l4g">Test Solution</a>
+ </p>
+ </td>
+ </tr>
+ <tr>
+ <td class="Normal" valign="top" width="300">
+ Achieve stakeholder concurrence that deployment is complete
+ </td>
+ <td class="Normal" valign="top" width="348">
+ <p>
+ <a class="elementLink"
+ href="./../../process.openup.base/capabilitypatterns/plan_manage_iteration_F9713A62.html"
+ guid="_oZgCsdOEEdyqlogshP8l4g">Plan and Manage Iteration</a>
+ </p>
+ <p style="TEXT-ALIGN: justify">
+ <a class="elementLink"
+ href="./../../process.openup.base/capabilitypatterns/test_solution_D16D88FC.html"
+ guid="_buG4sdOFEdyqlogshP8l4g">Test Solution</a>
+ </p>
+ </td>
+ </tr>
+ <tr>
+ <td class="Normal" valign="top" width="300">
+ Improve future project performance through lessons learned
+ </td>
+ <td class="Normal" valign="top" width="348">
+ <a class="elementLink"
+ href="./../../process.openup.base/capabilitypatterns/plan_manage_iteration_F9713A62.html"
+ guid="_oZgCsdOEEdyqlogshP8l4g">Plan and Manage Iteration</a>
+ </td>
+ </tr>
+ </tbody>
+</table><br />
+<br /></mainDescription>
+</org.eclipse.epf.uma:ProcessDescription>
diff --git a/praclib/temp/process.openup.base/capabilitypatterns/transition_phase_iteration/diagram.xmi b/praclib/temp/process.openup.base/capabilitypatterns/transition_phase_iteration/diagram.xmi
new file mode 100644
index 0000000..614589f
--- /dev/null
+++ b/praclib/temp/process.openup.base/capabilitypatterns/transition_phase_iteration/diagram.xmi
@@ -0,0 +1,331 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xmi:XMI xmi:version="2.0"
+ xmlns:xmi="http://www.omg.org/XMI" xmlns:ecore="http://www.eclipse.org/emf/2002/Ecore"
+ xmlns:notation="http://www.eclipse.org/gmf/runtime/1.0.1/notation" xmlns:uml="http://www.eclipse.org/uml2/2.1.0/UML">
+ <uml:Activity xmi:id="_6nb-MNUCEdylRpA9TBY1SQ" name="transition_phase_iteration">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_6nb-MdUCEdylRpA9TBY1SQ" source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_6nb-MtUCEdylRpA9TBY1SQ"
+ key="uri" value="uma://_pzQU0NONEdyqlogshP8l4g#_pzQU0dONEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_6nb-M9UCEdylRpA9TBY1SQ"
+ key="type" value="Activity"/>
+ </eAnnotations>
+ <node xmi:type="uml:StructuredActivityNode" xmi:id="_6ofHENUCEdylRpA9TBY1SQ" name="Plan and Manage Iteration"
+ outgoing="_RsnxENUDEdylRpA9TBY1SQ" incoming="_RPHVsNUDEdylRpA9TBY1SQ">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_6ofHEdUCEdylRpA9TBY1SQ"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_6ofHEtUCEdylRpA9TBY1SQ"
+ key="uri" value="uma://_pzQU0NONEdyqlogshP8l4g#_5v_o4dOOEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_6ofHE9UCEdylRpA9TBY1SQ"
+ key="type" value="Activity"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:StructuredActivityNode" xmi:id="_6ofHFNUCEdylRpA9TBY1SQ" name="Develop Solution Increment"
+ outgoing="_QGsVENUDEdylRpA9TBY1SQ" incoming="_PzxZENUDEdylRpA9TBY1SQ">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_6ofHFdUCEdylRpA9TBY1SQ"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_6ofHFtUCEdylRpA9TBY1SQ"
+ key="uri" value="uma://_pzQU0NONEdyqlogshP8l4g#_-iix4dOOEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_6ofHF9UCEdylRpA9TBY1SQ"
+ key="type" value="Activity"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:StructuredActivityNode" xmi:id="_6ofHGNUCEdylRpA9TBY1SQ" name="Test Solution"
+ outgoing="_Q5NXINUDEdylRpA9TBY1SQ" incoming="_Qf4RINUDEdylRpA9TBY1SQ">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_6ofHGdUCEdylRpA9TBY1SQ"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_6ofHGtUCEdylRpA9TBY1SQ"
+ key="uri" value="uma://_pzQU0NONEdyqlogshP8l4g#_AZ58IdOPEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_6ofHG9UCEdylRpA9TBY1SQ"
+ key="type" value="Activity"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:StructuredActivityNode" xmi:id="_6ofHHNUCEdylRpA9TBY1SQ" name="Ongoing Tasks"
+ outgoing="_STN3ANUDEdylRpA9TBY1SQ" incoming="_SDHlgNUDEdylRpA9TBY1SQ">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_6ofHHdUCEdylRpA9TBY1SQ"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_6ofHHtUCEdylRpA9TBY1SQ"
+ key="uri" value="uma://_pzQU0NONEdyqlogshP8l4g#_CoJVUdOPEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_6ofHH9UCEdylRpA9TBY1SQ"
+ key="type" value="Activity"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:ForkNode" xmi:id="_IVlJMNUDEdylRpA9TBY1SQ" outgoing="_PzxZENUDEdylRpA9TBY1SQ _Qf4RINUDEdylRpA9TBY1SQ _RPHVsNUDEdylRpA9TBY1SQ _SDHlgNUDEdylRpA9TBY1SQ"
+ incoming="_Oqv7gNUDEdylRpA9TBY1SQ"/>
+ <node xmi:type="uml:JoinNode" xmi:id="_KP6u8NUDEdylRpA9TBY1SQ" outgoing="_PMIKQNUDEdylRpA9TBY1SQ"
+ incoming="_QGsVENUDEdylRpA9TBY1SQ _Q5NXINUDEdylRpA9TBY1SQ _RsnxENUDEdylRpA9TBY1SQ _STN3ANUDEdylRpA9TBY1SQ"/>
+ <node xmi:type="uml:InitialNode" xmi:id="_NBQOINUDEdylRpA9TBY1SQ" outgoing="_Oqv7gNUDEdylRpA9TBY1SQ"/>
+ <node xmi:type="uml:ActivityFinalNode" xmi:id="_NdHDsNUDEdylRpA9TBY1SQ" incoming="_PMIKQNUDEdylRpA9TBY1SQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_Oqv7gNUDEdylRpA9TBY1SQ" source="_NBQOINUDEdylRpA9TBY1SQ"
+ target="_IVlJMNUDEdylRpA9TBY1SQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_PMIKQNUDEdylRpA9TBY1SQ" source="_KP6u8NUDEdylRpA9TBY1SQ"
+ target="_NdHDsNUDEdylRpA9TBY1SQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_PzxZENUDEdylRpA9TBY1SQ" source="_IVlJMNUDEdylRpA9TBY1SQ"
+ target="_6ofHFNUCEdylRpA9TBY1SQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_QGsVENUDEdylRpA9TBY1SQ" source="_6ofHFNUCEdylRpA9TBY1SQ"
+ target="_KP6u8NUDEdylRpA9TBY1SQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_Qf4RINUDEdylRpA9TBY1SQ" source="_IVlJMNUDEdylRpA9TBY1SQ"
+ target="_6ofHGNUCEdylRpA9TBY1SQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_Q5NXINUDEdylRpA9TBY1SQ" source="_6ofHGNUCEdylRpA9TBY1SQ"
+ target="_KP6u8NUDEdylRpA9TBY1SQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_RPHVsNUDEdylRpA9TBY1SQ" source="_IVlJMNUDEdylRpA9TBY1SQ"
+ target="_6ofHENUCEdylRpA9TBY1SQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_RsnxENUDEdylRpA9TBY1SQ" source="_6ofHENUCEdylRpA9TBY1SQ"
+ target="_KP6u8NUDEdylRpA9TBY1SQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_SDHlgNUDEdylRpA9TBY1SQ" source="_IVlJMNUDEdylRpA9TBY1SQ"
+ target="_6ofHHNUCEdylRpA9TBY1SQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_STN3ANUDEdylRpA9TBY1SQ" source="_6ofHHNUCEdylRpA9TBY1SQ"
+ target="_KP6u8NUDEdylRpA9TBY1SQ"/>
+ </uml:Activity>
+ <notation:Diagram xmi:id="_6nb-NNUCEdylRpA9TBY1SQ" type="AD" element="_6nb-MNUCEdylRpA9TBY1SQ"
+ name="transition_phase_iteration" measurementUnit="Pixel">
+ <children xmi:type="notation:Node" xmi:id="_9_gtQNUCEdylRpA9TBY1SQ" type="1007"
+ element="_6ofHENUCEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_9_gtRtUCEdylRpA9TBY1SQ" type="4005"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_9_gtQdUCEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_9_gtQtUCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_9_gtQ9UCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_9_gtRNUCEdylRpA9TBY1SQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_9_gtRdUCEdylRpA9TBY1SQ"
+ x="228" y="120"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_9_gtR9UCEdylRpA9TBY1SQ" type="1007"
+ element="_6ofHFNUCEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_9_p3MNUCEdylRpA9TBY1SQ" type="4005"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_9_gtSNUCEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_9_gtSdUCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_9_gtStUCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_9_gtS9UCEdylRpA9TBY1SQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_9_gtTNUCEdylRpA9TBY1SQ"
+ x="36" y="120"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_9_p3MdUCEdylRpA9TBY1SQ" type="1007"
+ element="_6ofHGNUCEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_9_p3N9UCEdylRpA9TBY1SQ" type="4005"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_9_p3MtUCEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_9_p3M9UCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_9_p3NNUCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_9_p3NdUCEdylRpA9TBY1SQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_9_p3NtUCEdylRpA9TBY1SQ"
+ x="180" y="192"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_9_p3ONUCEdylRpA9TBY1SQ" type="1007"
+ element="_6ofHHNUCEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_9_p3PtUCEdylRpA9TBY1SQ" type="4005"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_9_p3OdUCEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_9_p3OtUCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_9_p3O9UCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_9_p3PNUCEdylRpA9TBY1SQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_9_p3PdUCEdylRpA9TBY1SQ"
+ x="396" y="156"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_IVlJMdUDEdylRpA9TBY1SQ" type="1003"
+ element="_IVlJMNUDEdylRpA9TBY1SQ">
+ <styles xmi:type="notation:FontStyle" xmi:id="_IVlJMtUDEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_IVlJM9UDEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_IVlJNNUDEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_IVlJNdUDEdylRpA9TBY1SQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_IVlJNtUDEdylRpA9TBY1SQ"
+ x="28" y="82" width="465"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_KP6u8dUDEdylRpA9TBY1SQ" type="1006"
+ element="_KP6u8NUDEdylRpA9TBY1SQ">
+ <styles xmi:type="notation:FontStyle" xmi:id="_KP6u8tUDEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_KP6u89UDEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_KP6u9NUDEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_KP6u9dUDEdylRpA9TBY1SQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_KP6u9tUDEdylRpA9TBY1SQ"
+ x="36" y="264" width="461"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_NBQOIdUDEdylRpA9TBY1SQ" type="1004"
+ element="_NBQOINUDEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_NBQOJ9UDEdylRpA9TBY1SQ" type="4003">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_NBQOKNUDEdylRpA9TBY1SQ"
+ y="5"/>
+ </children>
+ <styles xmi:type="notation:FontStyle" xmi:id="_NBQOItUDEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_NBQOI9UDEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_NBQOJNUDEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_NBQOJdUDEdylRpA9TBY1SQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_NBQOJtUDEdylRpA9TBY1SQ"
+ x="246" y="40"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_NdHDsdUDEdylRpA9TBY1SQ" type="1001"
+ element="_NdHDsNUDEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_NdHDt9UDEdylRpA9TBY1SQ" type="4001">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_NdHDuNUDEdylRpA9TBY1SQ"
+ y="5"/>
+ </children>
+ <styles xmi:type="notation:FontStyle" xmi:id="_NdHDstUDEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_NdHDs9UDEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_NdHDtNUDEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_NdHDtdUDEdylRpA9TBY1SQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_NdHDttUDEdylRpA9TBY1SQ"
+ x="252" y="300"/>
+ </children>
+ <styles xmi:type="notation:PageStyle" xmi:id="_6nb-NdUCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:GuideStyle" xmi:id="_6nb-NtUCEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_6nb-N9UCEdylRpA9TBY1SQ"/>
+ <edges xmi:type="notation:Edge" xmi:id="_Oqv7gdUDEdylRpA9TBY1SQ" type="3001" element="_Oqv7gNUDEdylRpA9TBY1SQ"
+ source="_NBQOIdUDEdylRpA9TBY1SQ" target="_IVlJMdUDEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_Oqv7htUDEdylRpA9TBY1SQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_Oqv7h9UDEdylRpA9TBY1SQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_Oqv7gtUDEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_Oqv7g9UDEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_Oqv7hNUDEdylRpA9TBY1SQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_Oqv7hdUDEdylRpA9TBY1SQ"
+ points="[-1, 10, -5, -26]$[-228, 34, -232, -2]"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_PMR7QNUDEdylRpA9TBY1SQ" type="3001" element="_PMIKQNUDEdylRpA9TBY1SQ"
+ source="_KP6u8dUDEdylRpA9TBY1SQ" target="_NdHDsdUDEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_PMR7RdUDEdylRpA9TBY1SQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_PMR7RtUDEdylRpA9TBY1SQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_PMR7QdUDEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_PMR7QtUDEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_PMR7Q9UDEdylRpA9TBY1SQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_PMR7RNUDEdylRpA9TBY1SQ"
+ points="[-7, 4, -5, -40]$[-14, 39, -12, -5]"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_Pz6jANUDEdylRpA9TBY1SQ" type="3001" element="_PzxZENUDEdylRpA9TBY1SQ"
+ source="_IVlJMdUDEdylRpA9TBY1SQ" target="_9_gtR9UCEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_Pz6jBdUDEdylRpA9TBY1SQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_Pz6jBtUDEdylRpA9TBY1SQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_Pz6jAdUDEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_Pz6jAtUDEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_Pz6jA9UDEdylRpA9TBY1SQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_Pz6jBNUDEdylRpA9TBY1SQ"
+ points="[3, 3, 0, -40]$[3, 33, 0, -10]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_Pz6jB9UDEdylRpA9TBY1SQ"
+ id="(0.15698925,0.625)"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_Pz6jCNUDEdylRpA9TBY1SQ"
+ id="(0.49635038,0.18867925)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_QGsVEdUDEdylRpA9TBY1SQ" type="3001" element="_QGsVENUDEdylRpA9TBY1SQ"
+ source="_9_gtR9UCEdylRpA9TBY1SQ" target="_KP6u8dUDEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_QGsVFtUDEdylRpA9TBY1SQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_QGsVF9UDEdylRpA9TBY1SQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_QGsVEtUDEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_QGsVE9UDEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_QGsVFNUDEdylRpA9TBY1SQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_QGsVFdUDEdylRpA9TBY1SQ"
+ points="[-3, 27, 0, -94]$[-68, 121, -65, 0]"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_QG2GENUDEdylRpA9TBY1SQ"
+ id="(0.14099783,0.375)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_Qf4RIdUDEdylRpA9TBY1SQ" type="3001" element="_Qf4RINUDEdylRpA9TBY1SQ"
+ source="_IVlJMdUDEdylRpA9TBY1SQ" target="_9_p3MdUCEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_Qf4RJtUDEdylRpA9TBY1SQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_Qf4RJ9UDEdylRpA9TBY1SQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_Qf4RItUDEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_Qf4RI9UDEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_Qf4RJNUDEdylRpA9TBY1SQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_Qf4RJdUDEdylRpA9TBY1SQ"
+ points="[-2, 4, 47, -113]$[-50, 106, -1, -11]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_XmhjsNUDEdylRpA9TBY1SQ"
+ id="(0.37634408,0.125)"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_QgBbENUDEdylRpA9TBY1SQ"
+ id="(0.46969697,0.20754717)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_Q5NXIdUDEdylRpA9TBY1SQ" type="3001" element="_Q5NXINUDEdylRpA9TBY1SQ"
+ source="_9_p3MdUCEdylRpA9TBY1SQ" target="_KP6u8dUDEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_Q5NXJtUDEdylRpA9TBY1SQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_Q5NXJ9UDEdylRpA9TBY1SQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_Q5NXItUDEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_Q5NXI9UDEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_Q5NXJNUDEdylRpA9TBY1SQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_Q5NXJdUDEdylRpA9TBY1SQ"
+ points="[0, 41, -55, -23]$[-175, 62, -230, -2]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_Q5XIINUDEdylRpA9TBY1SQ"
+ id="(0.46969697,0.2264151)"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_V8H3YNUDEdylRpA9TBY1SQ"
+ id="(0.37527114,0.125)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_RPHVsdUDEdylRpA9TBY1SQ" type="3001" element="_RPHVsNUDEdylRpA9TBY1SQ"
+ source="_IVlJMdUDEdylRpA9TBY1SQ" target="_9_gtQNUCEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_RPHVttUDEdylRpA9TBY1SQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_RPHVt9UDEdylRpA9TBY1SQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_RPHVstUDEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_RPHVs9UDEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_RPHVtNUDEdylRpA9TBY1SQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_RPHVtdUDEdylRpA9TBY1SQ"
+ points="[3, 4, -27, -41]$[28, 34, -2, -11]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_T3gUQNUDEdylRpA9TBY1SQ"
+ id="(0.5827957,0.125)"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_RPRGsNUDEdylRpA9TBY1SQ"
+ id="(0.47692308,0.20754717)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_RsnxEdUDEdylRpA9TBY1SQ" type="3001" element="_RsnxENUDEdylRpA9TBY1SQ"
+ source="_9_gtQNUCEdylRpA9TBY1SQ" target="_KP6u8dUDEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_RsnxFtUDEdylRpA9TBY1SQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_RsnxF9UDEdylRpA9TBY1SQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_RsnxEtUDEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_RsnxE9UDEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_RsnxFNUDEdylRpA9TBY1SQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_RsnxFdUDEdylRpA9TBY1SQ"
+ points="[-4, 27, 23, -95]$[204, 121, 231, -1]"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_UuMEoNUDEdylRpA9TBY1SQ"
+ id="(0.53362256,0.875)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_SDHlgdUDEdylRpA9TBY1SQ" type="3001" element="_SDHlgNUDEdylRpA9TBY1SQ"
+ source="_IVlJMdUDEdylRpA9TBY1SQ" target="_9_p3ONUCEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_SDHlhtUDEdylRpA9TBY1SQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_SDHlh9UDEdylRpA9TBY1SQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_SDHlgtUDEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_SDHlg9UDEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_SDHlhNUDEdylRpA9TBY1SQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_SDHlhdUDEdylRpA9TBY1SQ"
+ points="[6, 4, -7, -85]$[6, 63, -7, -26]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_SDHliNUDEdylRpA9TBY1SQ"
+ id="(0.8795699,0.5)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_STXA8NUDEdylRpA9TBY1SQ" type="3001" element="_STN3ANUDEdylRpA9TBY1SQ"
+ source="_9_p3ONUCEdylRpA9TBY1SQ" target="_KP6u8dUDEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_STXA9dUDEdylRpA9TBY1SQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_STXA9tUDEdylRpA9TBY1SQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_STXA8dUDEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_STXA8tUDEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_STXA89UDEdylRpA9TBY1SQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_STXA9NUDEdylRpA9TBY1SQ"
+ points="[-12, 27, 29, -67]$[47, 95, 88, 1]"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_STXA99UDEdylRpA9TBY1SQ"
+ id="(0.86334056,0.375)"/>
+ </edges>
+ </notation:Diagram>
+</xmi:XMI>
diff --git a/praclib/temp/process.openup.base/capabilitypatterns/transition_phase_iteration/model.xmi b/praclib/temp/process.openup.base/capabilitypatterns/transition_phase_iteration/model.xmi
new file mode 100644
index 0000000..db2ba29
--- /dev/null
+++ b/praclib/temp/process.openup.base/capabilitypatterns/transition_phase_iteration/model.xmi
@@ -0,0 +1,58 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_p2--QdONEdyqlogshP8l4g"
+ guid="_p2--QdONEdyqlogshP8l4g">
+ <resourceDescriptors xmi:id="_p2--QtONEdyqlogshP8l4g" id="-ybGHhzGQT4fXY7TTaBPxug"
+ uri="content.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:ProcessComponent xmi:id="_pzQU0NONEdyqlogshP8l4g" name="transition_phase_iteration"
+ guid="_pzQU0NONEdyqlogshP8l4g">
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_5v_o4NOOEdyqlogshP8l4g"
+ name="plan_manage_iteration" guid="_5v_o4NOOEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_5v_o4dOOEdyqlogshP8l4g"
+ name="plan_manage_iteration" guid="_5v_o4dOOEdyqlogshP8l4g" superActivities="_pzQU0dONEdyqlogshP8l4g"
+ variabilityType="extends">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://_oZgCsNOEEdyqlogshP8l4g#_oZgCsdOEEdyqlogshP8l4g"/>
+ </processElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_-iix4NOOEdyqlogshP8l4g"
+ name="develop_solution" guid="_-iix4NOOEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_-iix4dOOEdyqlogshP8l4g"
+ name="develop_solution" guid="_-iix4dOOEdyqlogshP8l4g" superActivities="_pzQU0dONEdyqlogshP8l4g"
+ variabilityType="extends">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://_RXGooNOFEdyqlogshP8l4g#_RXGoodOFEdyqlogshP8l4g"/>
+ </processElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_AZ58INOPEdyqlogshP8l4g"
+ name="test_solution" guid="_AZ58INOPEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_AZ58IdOPEdyqlogshP8l4g"
+ name="test_solution" guid="_AZ58IdOPEdyqlogshP8l4g" superActivities="_pzQU0dONEdyqlogshP8l4g"
+ variabilityType="extends">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://_buG4sNOFEdyqlogshP8l4g#_buG4sdOFEdyqlogshP8l4g"/>
+ </processElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_CoJVUNOPEdyqlogshP8l4g"
+ name="ongoing_tasks" guid="_CoJVUNOPEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:Activity" xmi:id="_CoJVUdOPEdyqlogshP8l4g"
+ name="ongoing_tasks" guid="_CoJVUdOPEdyqlogshP8l4g" superActivities="_pzQU0dONEdyqlogshP8l4g"
+ variabilityType="extends">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://__ZInMNOEEdyqlogshP8l4g#__ZInMdOEEdyqlogshP8l4g"/>
+ </processElements>
+ </childPackages>
+ <process xsi:type="org.eclipse.epf.uma:CapabilityPattern" xmi:id="_pzQU0dONEdyqlogshP8l4g"
+ name="transition_phase_iteration" guid="_pzQU0dONEdyqlogshP8l4g" briefDescription="This iteration template defines the activities (and associated roles and work products) performed in a typical iteration in the Transition phase."
+ presentationName="Transition Phase Iteration" breakdownElements="_5v_o4dOOEdyqlogshP8l4g _-iix4dOOEdyqlogshP8l4g _AZ58IdOPEdyqlogshP8l4g _CoJVUdOPEdyqlogshP8l4g">
+ <presentation xmi:id="-ybGHhzGQT4fXY7TTaBPxug" href="uma://-ybGHhzGQT4fXY7TTaBPxug#-ybGHhzGQT4fXY7TTaBPxug"/>
+ <defaultContext href="uma://_0NAjrNUAEdylRpA9TBY1SQ#_gExDwNQxEdyk9oc_L5Vk0g"/>
+ <validContext href="uma://_0NAjrNUAEdylRpA9TBY1SQ#_gExDwNQxEdyk9oc_L5Vk0g"/>
+ </process>
+ </org.eclipse.epf.uma:ProcessComponent>
+</xmi:XMI>
diff --git a/praclib/temp/process.openup.base/deliveryprocesses/openup_lifecycle/content.xmi b/praclib/temp/process.openup.base/deliveryprocesses/openup_lifecycle/content.xmi
new file mode 100644
index 0000000..a723d8c
--- /dev/null
+++ b/praclib/temp/process.openup.base/deliveryprocesses/openup_lifecycle/content.xmi
@@ -0,0 +1,74 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<org.eclipse.epf.uma:DeliveryProcessDescription 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="-dV7s6ZJXratblG37Lbu0mw"
+ name="openup_lifecycle,_SuWj4dOPEdyqlogshP8l4g" guid="-dV7s6ZJXratblG37Lbu0mw"
+ version="7.2.0">
+ <mainDescription><p>
+ OpenUP is an iterative process with <a class="elementlinkwithusertext"
+ href="./../../core.mgmt.common.base/guidances/concepts/core_principle_evolve_BFD9AEB4.html"
+ guid="_GXiogMvoEdqukPpotm3DYg">iterations</a> distributed throughout four <a class="elementLinkWithUserText"
+ href="./../../practice.mgmt.risk_value_lifecycle.base/guidances/concepts/phase_85B003C3.html"
+ guid="__7xOEC7aEdqHMdmRzC0-2g">phases</a>: <a class="elementLinkWithUserText"
+ href="./../../practice.mgmt.risk_value_lifecycle.base/guidances/concepts/inception_phase_C4456871.html"
+ guid="_0hmKgBOMEduCNqgZdt_OaA">Inception</a>, <a class="elementLinkWithUserText"
+ href="./../../practice.mgmt.risk_value_lifecycle.base/guidances/concepts/elaboration_phase_BE880435.html"
+ guid="_2plxwBOMEduCNqgZdt_OaA">Elaboration</a>, <a class="elementLinkWithUserText"
+ href="./../../practice.mgmt.risk_value_lifecycle.base/guidances/concepts/construction_phase_873B6559.html"
+ guid="_48EKsBOMEduCNqgZdt_OaA">Construction</a>, and <a class="elementLinkWithUserText"
+ href="./../../practice.mgmt.risk_value_lifecycle.base/guidances/concepts/transition_phase_DD5986E5.html"
+ guid="__ca5UBOMEduCNqgZdt_OaA">Transition</a>.
+</p>
+<p>
+ Each phase may have as many iterations as needed (depending on the degree of novelty of the business domain, the
+ technology being used, architectural complexity, and project size, to name a few factors).
+</p>
+<p>
+ To offer a quick start for teams to plan their iterations, OpenUP provides work breakdown structure (WBS) templates for
+ each iteration, and a WBS template for an end-to-end process.
+</p>
+<p>
+ Iterations may have variable lengths, depending on project characteristics. One-month iterations are typically
+ recommended, because this timeframe provides:
+</p>
+<ul>
+ <li>
+ A reasonable amount of time for projects to deliver meaningful increments in functionality.
+ </li>
+ <li>
+ Early and frequent customer feedback.
+ </li>
+ <li>
+ Timely management of risks and issues during the course of the project.
+ </li>
+</ul>
+<p>
+ OpenUP is intended to offer process guidance to small, co-located teams.
+</p></mainDescription>
+ <purpose><p>
+ This delivery process is intended to:
+</p>
+<ul>
+ <li>
+ Promote collaboration (both internal and external to the team), to align interests and share understanding
+ </li>
+ <li>
+ Help the team focus on the architecture early, to minimize risks and organize development
+ </li>
+ <li>
+ Help the team balance competing priorities to maximize stakeholder value
+ </li>
+ <li>
+ Help the team evolve the product to continuously obtain feedback and improve
+ </li>
+ <li>
+ <div id="comment_text_7">
+ Allow project managers to track status based on goals
+ </div>
+ </li>
+ <li>
+ Allow team members to understand how to perform their work to achieve project goals
+ </li>
+</ul></purpose>
+</org.eclipse.epf.uma:DeliveryProcessDescription>
diff --git a/praclib/temp/process.openup.base/deliveryprocesses/openup_lifecycle/diagram.xmi b/praclib/temp/process.openup.base/deliveryprocesses/openup_lifecycle/diagram.xmi
new file mode 100644
index 0000000..26ba438
--- /dev/null
+++ b/praclib/temp/process.openup.base/deliveryprocesses/openup_lifecycle/diagram.xmi
@@ -0,0 +1,900 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<xmi:XMI xmi:version="2.0"
+ xmlns:xmi="http://www.omg.org/XMI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xmlns:ecore="http://www.eclipse.org/emf/2002/Ecore" xmlns:notation="http://www.eclipse.org/gmf/runtime/1.0.1/notation"
+ xmlns:org.eclipse.epf.diagram.model="http://www.eclipse.org/epf/diagram/1.0.0/diagram.ecore"
+ xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.4/uma.ecore" xmlns:uml="http://www.eclipse.org/uml2/2.1.0/UML">
+ <uml:Activity xmi:id="_SC1U0NUHEdylRpA9TBY1SQ" name="openup_lifecycle">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_SC1U0dUHEdylRpA9TBY1SQ" source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_SC1U0tUHEdylRpA9TBY1SQ"
+ key="uri" value="uma://_SuWj4NOPEdyqlogshP8l4g#_SuWj4dOPEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_SC1U09UHEdylRpA9TBY1SQ"
+ key="type" value="Activity"/>
+ </eAnnotations>
+ <node xmi:type="uml:StructuredActivityNode" xmi:id="_SFzwUNUHEdylRpA9TBY1SQ" name="Inception Phase Iteration [1..n]"
+ outgoing="_xRcF4NUHEdylRpA9TBY1SQ" incoming="_wiWLQNUHEdylRpA9TBY1SQ">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_SFzwUdUHEdylRpA9TBY1SQ"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_SFzwUtUHEdylRpA9TBY1SQ"
+ key="uri" value="uma://_SuWj4NOPEdyqlogshP8l4g#_kYVSUdOPEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_SFzwU9UHEdylRpA9TBY1SQ"
+ key="type" value="Iteration"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:ActivityParameterNode" xmi:id="_SFzwVNUHEdylRpA9TBY1SQ" name="Lifecycle Objectives Milestone"
+ outgoing="_zoF0MNUHEdylRpA9TBY1SQ" incoming="_xRcF4NUHEdylRpA9TBY1SQ">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_SFzwVdUHEdylRpA9TBY1SQ"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_SFzwVtUHEdylRpA9TBY1SQ"
+ key="uri" value="uma://_SuWj4NOPEdyqlogshP8l4g#_l_0NgNOPEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_SFzwV9UHEdylRpA9TBY1SQ"
+ key="type" value="Milestone"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:StructuredActivityNode" xmi:id="_SFzwWNUHEdylRpA9TBY1SQ" name="Elaboration Phase Iteration [1..n]"
+ outgoing="_0FTUoNUHEdylRpA9TBY1SQ" incoming="_zoF0MNUHEdylRpA9TBY1SQ">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_SFzwWdUHEdylRpA9TBY1SQ"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_SFzwWtUHEdylRpA9TBY1SQ"
+ key="uri" value="uma://_SuWj4NOPEdyqlogshP8l4g#_51ewYdOPEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_SFzwW9UHEdylRpA9TBY1SQ"
+ key="type" value="Iteration"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:ActivityParameterNode" xmi:id="_SFzwXNUHEdylRpA9TBY1SQ" name="Lifecycle Architecture Milestone"
+ outgoing="_1ngHMNUHEdylRpA9TBY1SQ" incoming="_0FTUoNUHEdylRpA9TBY1SQ">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_SFzwXdUHEdylRpA9TBY1SQ"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_SFzwXtUHEdylRpA9TBY1SQ"
+ key="uri" value="uma://_SuWj4NOPEdyqlogshP8l4g#_9P2lgNOPEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_SFzwX9UHEdylRpA9TBY1SQ"
+ key="type" value="Milestone"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:StructuredActivityNode" xmi:id="_SFzwYNUHEdylRpA9TBY1SQ" name="Construction Phase Iteration [1..n]"
+ outgoing="_2D9ZsNUHEdylRpA9TBY1SQ" incoming="_1ngHMNUHEdylRpA9TBY1SQ">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_SFzwYdUHEdylRpA9TBY1SQ"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_SFzwYtUHEdylRpA9TBY1SQ"
+ key="uri" value="uma://_SuWj4NOPEdyqlogshP8l4g#_6togYdOPEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_SFzwY9UHEdylRpA9TBY1SQ"
+ key="type" value="Iteration"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:ActivityParameterNode" xmi:id="_SFzwZNUHEdylRpA9TBY1SQ" name="Initial Operational Capability Milestone"
+ outgoing="_6BSK4NUHEdylRpA9TBY1SQ" incoming="_2D9ZsNUHEdylRpA9TBY1SQ">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_SFzwZdUHEdylRpA9TBY1SQ"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_SFzwZtUHEdylRpA9TBY1SQ"
+ key="uri" value="uma://_SuWj4NOPEdyqlogshP8l4g#_Ik_RwNOQEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_SFzwZ9UHEdylRpA9TBY1SQ"
+ key="type" value="Milestone"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:StructuredActivityNode" xmi:id="_SFzwaNUHEdylRpA9TBY1SQ" name="Transition Phase Iteration [1..n]"
+ outgoing="_6vCBsNUHEdylRpA9TBY1SQ" incoming="_6BSK4NUHEdylRpA9TBY1SQ">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_SFzwadUHEdylRpA9TBY1SQ"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_SFzwatUHEdylRpA9TBY1SQ"
+ key="uri" value="uma://_SuWj4NOPEdyqlogshP8l4g#_7bg6EdOPEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_SFzwa9UHEdylRpA9TBY1SQ"
+ key="type" value="Iteration"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:ActivityParameterNode" xmi:id="_SFzwbNUHEdylRpA9TBY1SQ" name="Product Release Milestone"
+ outgoing="_9LWTINUHEdylRpA9TBY1SQ" incoming="_6vCBsNUHEdylRpA9TBY1SQ">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_SFzwbdUHEdylRpA9TBY1SQ"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_SFzwbtUHEdylRpA9TBY1SQ"
+ key="uri" value="uma://_SuWj4NOPEdyqlogshP8l4g#_SYGxoNOQEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_SFzwb9UHEdylRpA9TBY1SQ"
+ key="type" value="Milestone"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:InitialNode" xmi:id="_trWwANUHEdylRpA9TBY1SQ" outgoing="_wiWLQNUHEdylRpA9TBY1SQ"/>
+ <node xmi:type="uml:ActivityFinalNode" xmi:id="_uWbGQNUHEdylRpA9TBY1SQ" incoming="_9LWTINUHEdylRpA9TBY1SQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_wiWLQNUHEdylRpA9TBY1SQ" source="_trWwANUHEdylRpA9TBY1SQ"
+ target="_SFzwUNUHEdylRpA9TBY1SQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_xRcF4NUHEdylRpA9TBY1SQ" name="" source="_SFzwUNUHEdylRpA9TBY1SQ"
+ target="_SFzwVNUHEdylRpA9TBY1SQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_zoF0MNUHEdylRpA9TBY1SQ" source="_SFzwVNUHEdylRpA9TBY1SQ"
+ target="_SFzwWNUHEdylRpA9TBY1SQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_0FTUoNUHEdylRpA9TBY1SQ" source="_SFzwWNUHEdylRpA9TBY1SQ"
+ target="_SFzwXNUHEdylRpA9TBY1SQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_1ngHMNUHEdylRpA9TBY1SQ" source="_SFzwXNUHEdylRpA9TBY1SQ"
+ target="_SFzwYNUHEdylRpA9TBY1SQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_2D9ZsNUHEdylRpA9TBY1SQ" source="_SFzwYNUHEdylRpA9TBY1SQ"
+ target="_SFzwZNUHEdylRpA9TBY1SQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_6BSK4NUHEdylRpA9TBY1SQ" source="_SFzwZNUHEdylRpA9TBY1SQ"
+ target="_SFzwaNUHEdylRpA9TBY1SQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_6vCBsNUHEdylRpA9TBY1SQ" source="_SFzwaNUHEdylRpA9TBY1SQ"
+ target="_SFzwbNUHEdylRpA9TBY1SQ"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_9LWTINUHEdylRpA9TBY1SQ" source="_SFzwbNUHEdylRpA9TBY1SQ"
+ target="_uWbGQNUHEdylRpA9TBY1SQ"/>
+ </uml:Activity>
+ <notation:Diagram xmi:id="_SC1U1NUHEdylRpA9TBY1SQ" type="AD" element="_SC1U0NUHEdylRpA9TBY1SQ"
+ name="openup_lifecycle" measurementUnit="Pixel">
+ <children xmi:type="notation:Node" xmi:id="_Ytnx0NUHEdylRpA9TBY1SQ" type="1011"
+ element="_SFzwUNUHEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_Ytnx1tUHEdylRpA9TBY1SQ" type="4010"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_Ytnx0dUHEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_Ytnx0tUHEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_Ytnx09UHEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_Ytnx1NUHEdylRpA9TBY1SQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_Ytnx1dUHEdylRpA9TBY1SQ"
+ x="144" y="60"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_Ytnx19UHEdylRpA9TBY1SQ" type="1012"
+ element="_SFzwVNUHEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_Ytnx3dUHEdylRpA9TBY1SQ" type="4011"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_Ytnx2NUHEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_Ytnx2dUHEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_Ytnx2tUHEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_Ytnx29UHEdylRpA9TBY1SQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_Ytnx3NUHEdylRpA9TBY1SQ"
+ x="144" y="192"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_Ytnx3tUHEdylRpA9TBY1SQ" type="1011"
+ element="_SFzwWNUHEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_Ytnx5NUHEdylRpA9TBY1SQ" type="4010"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_Ytnx39UHEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_Ytnx4NUHEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_Ytnx4dUHEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_Ytnx4tUHEdylRpA9TBY1SQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_Ytnx49UHEdylRpA9TBY1SQ"
+ x="312" y="60"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_Ytnx5dUHEdylRpA9TBY1SQ" type="1012"
+ element="_SFzwXNUHEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_Ytw7wNUHEdylRpA9TBY1SQ" type="4011"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_Ytnx5tUHEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_Ytnx59UHEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_Ytnx6NUHEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_Ytnx6dUHEdylRpA9TBY1SQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_Ytnx6tUHEdylRpA9TBY1SQ"
+ x="300" y="192"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_Ytw7wdUHEdylRpA9TBY1SQ" type="1011"
+ element="_SFzwYNUHEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_Ytw7x9UHEdylRpA9TBY1SQ" type="4010"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_Ytw7wtUHEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_Ytw7w9UHEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_Ytw7xNUHEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_Ytw7xdUHEdylRpA9TBY1SQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_Ytw7xtUHEdylRpA9TBY1SQ"
+ x="480" y="60"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_Ytw7yNUHEdylRpA9TBY1SQ" type="1012"
+ element="_SFzwZNUHEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_Ytw7ztUHEdylRpA9TBY1SQ" type="4011"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_Ytw7ydUHEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_Ytw7ytUHEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_Ytw7y9UHEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_Ytw7zNUHEdylRpA9TBY1SQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_Ytw7zdUHEdylRpA9TBY1SQ"
+ x="468" y="192"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_Ytw7z9UHEdylRpA9TBY1SQ" type="1011"
+ element="_SFzwaNUHEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_Ytw71dUHEdylRpA9TBY1SQ" type="4010"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_Ytw70NUHEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_Ytw70dUHEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_Ytw70tUHEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_Ytw709UHEdylRpA9TBY1SQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_Ytw71NUHEdylRpA9TBY1SQ"
+ x="660" y="60"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_Ytw71tUHEdylRpA9TBY1SQ" type="1012"
+ element="_SFzwbNUHEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_Ytw73NUHEdylRpA9TBY1SQ" type="4011"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_Ytw719UHEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_Ytw72NUHEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_Ytw72dUHEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_Ytw72tUHEdylRpA9TBY1SQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_Ytw729UHEdylRpA9TBY1SQ"
+ x="664" y="193"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_trWwAdUHEdylRpA9TBY1SQ" type="1004"
+ element="_trWwANUHEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_trWwB9UHEdylRpA9TBY1SQ" type="4003">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_trWwCNUHEdylRpA9TBY1SQ"
+ y="5"/>
+ </children>
+ <styles xmi:type="notation:FontStyle" xmi:id="_trWwAtUHEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_trWwA9UHEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_trWwBNUHEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_trWwBdUHEdylRpA9TBY1SQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_trWwBtUHEdylRpA9TBY1SQ"
+ x="86" y="70"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_uWbGQdUHEdylRpA9TBY1SQ" type="1001"
+ element="_uWbGQNUHEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_uWbGR9UHEdylRpA9TBY1SQ" type="4001">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_uWbGSNUHEdylRpA9TBY1SQ"
+ y="5"/>
+ </children>
+ <styles xmi:type="notation:FontStyle" xmi:id="_uWbGQtUHEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_uWbGQ9UHEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_uWbGRNUHEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_uWbGRdUHEdylRpA9TBY1SQ" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_uWbGRtUHEdylRpA9TBY1SQ"
+ x="828" y="192"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_V_F5kNUIEdylRpA9TBY1SQ" type="Text">
+ <children xmi:type="notation:Node" xmi:id="_V_F5k9UIEdylRpA9TBY1SQ" type="DiagramName">
+ <element xsi:nil="true"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_V_F5lNUIEdylRpA9TBY1SQ" type="Description">
+ <element xsi:nil="true"/>
+ </children>
+ <styles xmi:type="notation:ShapeStyle" xmi:id="_V_F5kdUIEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8" description="[last iteration in Inception]" lineColor="0"/>
+ <element xsi:nil="true"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_V_F5ktUIEdylRpA9TBY1SQ"
+ x="223" y="132" width="73" height="37"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_gzG1wNUIEdylRpA9TBY1SQ" type="Text">
+ <children xmi:type="notation:Node" xmi:id="_gzG1w9UIEdylRpA9TBY1SQ" type="DiagramName">
+ <element xsi:nil="true"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_gzG1xNUIEdylRpA9TBY1SQ" type="Description">
+ <element xsi:nil="true"/>
+ </children>
+ <styles xmi:type="notation:ShapeStyle" xmi:id="_gzG1wdUIEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8" description="[last iteration in Elaboration]" lineColor="0"/>
+ <element xsi:nil="true"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_gzG1wtUIEdylRpA9TBY1SQ"
+ x="378" y="129" width="73" height="37"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_nM5CUNUIEdylRpA9TBY1SQ" type="Text">
+ <children xmi:type="notation:Node" xmi:id="_nM5CU9UIEdylRpA9TBY1SQ" type="DiagramName">
+ <element xsi:nil="true"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_nM5CVNUIEdylRpA9TBY1SQ" type="Description">
+ <element xsi:nil="true"/>
+ </children>
+ <styles xmi:type="notation:ShapeStyle" xmi:id="_nM5CUdUIEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8" description="[last iteration in Construction]" lineColor="0"/>
+ <element xsi:nil="true"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_nM5CUtUIEdylRpA9TBY1SQ"
+ x="564" y="133" width="78" height="31"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_slthINUIEdylRpA9TBY1SQ" type="Text">
+ <children xmi:type="notation:Node" xmi:id="_slthI9UIEdylRpA9TBY1SQ" type="DiagramName">
+ <element xsi:nil="true"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_slthJNUIEdylRpA9TBY1SQ" type="Description">
+ <element xsi:nil="true"/>
+ </children>
+ <styles xmi:type="notation:ShapeStyle" xmi:id="_slthIdUIEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8" description="[last iteration in Transition]" lineColor="0"/>
+ <element xsi:nil="true"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_slthItUIEdylRpA9TBY1SQ"
+ x="732" y="130" width="71" height="36"/>
+ </children>
+ <styles xmi:type="notation:PageStyle" xmi:id="_SC1U1dUHEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:GuideStyle" xmi:id="_SC1U1tUHEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_SC1U19UHEdylRpA9TBY1SQ"/>
+ <edges xmi:type="notation:Edge" xmi:id="_wiWLQdUHEdylRpA9TBY1SQ" type="3001" element="_wiWLQNUHEdylRpA9TBY1SQ"
+ source="_trWwAdUHEdylRpA9TBY1SQ" target="_Ytnx0NUHEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_wiWLRtUHEdylRpA9TBY1SQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_wiWLR9UHEdylRpA9TBY1SQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_wiWLQtUHEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_wiWLQ9UHEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_wiWLRNUHEdylRpA9TBY1SQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_wiWLRdUHEdylRpA9TBY1SQ"
+ points="[10, 0, -114, -6]$[121, -20, -3, -26]"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_xVKIQNUHEdylRpA9TBY1SQ" type="3001" element="_xRcF4NUHEdylRpA9TBY1SQ"
+ source="_Ytnx0NUHEdylRpA9TBY1SQ" target="_Ytnx19UHEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_xVKIRdUHEdylRpA9TBY1SQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_xVKIRtUHEdylRpA9TBY1SQ"
+ x="-2" y="101"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_xVKIQdUHEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_xVKIQtUHEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_xVKIQ9UHEdylRpA9TBY1SQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_xVKIRNUHEdylRpA9TBY1SQ"
+ points="[17, 27, -56, -93]$[66, 94, -7, -26]"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_zrXxsdUHEdylRpA9TBY1SQ" type="3001" element="_zoF0MNUHEdylRpA9TBY1SQ"
+ source="_Ytnx19UHEdylRpA9TBY1SQ" target="_Ytnx3tUHEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_zrg7oNUHEdylRpA9TBY1SQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_zrg7odUHEdylRpA9TBY1SQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_zrXxstUHEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_zrXxs9UHEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_zrXxtNUHEdylRpA9TBY1SQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_zrXxtdUHEdylRpA9TBY1SQ"
+ points="[54, -26, -118, 106]$[113, -54, -59, 78]$[152, -105, -20, 27]"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="__02PgNUIEdylRpA9TBY1SQ"
+ id="(0.33950618,0.9622642)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_0JBXANUHEdylRpA9TBY1SQ" type="3001" element="_0FTUoNUHEdylRpA9TBY1SQ"
+ source="_Ytnx3tUHEdylRpA9TBY1SQ" target="_Ytnx5dUHEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_0JBXBdUHEdylRpA9TBY1SQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_0JBXBtUHEdylRpA9TBY1SQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_0JBXAdUHEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_0JBXAtUHEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_0JBXA9UHEdylRpA9TBY1SQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_0JBXBNUHEdylRpA9TBY1SQ"
+ points="[14, 27, -40, -80]$[48, 94, -6, -13]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_BR6f4NUIEdylRpA9TBY1SQ"
+ id="(0.38271606,0.9433962)"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_0JBXB9UHEdylRpA9TBY1SQ"
+ id="(0.4601227,0.24528302)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_1qxdodUHEdylRpA9TBY1SQ" type="3001" element="_1ngHMNUHEdylRpA9TBY1SQ"
+ source="_Ytnx5dUHEdylRpA9TBY1SQ" target="_Ytw7wdUHEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_1qxdptUHEdylRpA9TBY1SQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_1qxdp9UHEdylRpA9TBY1SQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_1qxdotUHEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_1qxdo9UHEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_1qxdpNUHEdylRpA9TBY1SQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_1qxdpdUHEdylRpA9TBY1SQ"
+ points="[65, -26, -119, 106]$[112, -45, -72, 87]$[162, -105, -22, 27]"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_2HsDINUHEdylRpA9TBY1SQ" type="3001" element="_2D9ZsNUHEdylRpA9TBY1SQ"
+ source="_Ytw7wdUHEdylRpA9TBY1SQ" target="_Ytw7yNUHEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_2HsDJdUHEdylRpA9TBY1SQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_2HsDJtUHEdylRpA9TBY1SQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_2HsDIdUHEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_2HsDItUHEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_2HsDI9UHEdylRpA9TBY1SQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_2HsDJNUHEdylRpA9TBY1SQ"
+ points="[15, 27, -53, -93]$[60, 94, -8, -26]"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_6EkIYdUHEdylRpA9TBY1SQ" type="3001" element="_6BSK4NUHEdylRpA9TBY1SQ"
+ source="_Ytw7yNUHEdylRpA9TBY1SQ" target="_Ytw7z9UHEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_6EkIZtUHEdylRpA9TBY1SQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_6EkIZ9UHEdylRpA9TBY1SQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_6EkIYtUHEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_6EkIY9UHEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_6EkIZNUHEdylRpA9TBY1SQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_6EkIZdUHEdylRpA9TBY1SQ"
+ points="[67, -26, -110, 106]$[116, -45, -61, 87]$[158, -105, -19, 27]"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_6y51ENUHEdylRpA9TBY1SQ" type="3001" element="_6vCBsNUHEdylRpA9TBY1SQ"
+ source="_Ytw7z9UHEdylRpA9TBY1SQ" target="_Ytw71tUHEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_6y51FdUHEdylRpA9TBY1SQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_6y51FtUHEdylRpA9TBY1SQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_6y51EdUHEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_6y51EtUHEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_6y51E9UHEdylRpA9TBY1SQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_6y51FNUHEdylRpA9TBY1SQ"
+ points="[19, 27, -54, -93]$[78, 94, 5, -26]"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_9LWTIdUHEdylRpA9TBY1SQ" type="3001" element="_9LWTINUHEdylRpA9TBY1SQ"
+ source="_Ytw71tUHEdylRpA9TBY1SQ" target="_uWbGQdUHEdylRpA9TBY1SQ">
+ <children xmi:type="notation:Node" xmi:id="_9LWTJtUHEdylRpA9TBY1SQ" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_9LWTJ9UHEdylRpA9TBY1SQ"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_9LWTItUHEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_9LWTI9UHEdylRpA9TBY1SQ" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_9LWTJNUHEdylRpA9TBY1SQ" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_9LWTJdUHEdylRpA9TBY1SQ"
+ points="[67, -6, -53, 1]$[108, -11, -12, -4]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_CnXacNUJEdylRpA9TBY1SQ"
+ id="(0.8507463,0.3207547)"/>
+ </edges>
+ </notation:Diagram>
+ <org.eclipse.epf.diagram.model:ActivityDetailDiagram xmi:id="_7Z35ANUIEdylRpA9TBY1SQ"
+ autoLayout="true">
+ <linkedElement xmi:type="org.eclipse.epf.uma:DeliveryProcess" href="uma://_SuWj4NOPEdyqlogshP8l4g#_SuWj4dOPEdyqlogshP8l4g"/>
+ </org.eclipse.epf.diagram.model:ActivityDetailDiagram>
+ <notation:Diagram xmi:id="_7Z35AdUIEdylRpA9TBY1SQ" type="ADD" element="_7Z35ANUIEdylRpA9TBY1SQ"
+ name="openup_lifecycle" measurementUnit="Pixel">
+ <styles xmi:type="notation:PageStyle" xmi:id="_7Z35AtUIEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:GuideStyle" xmi:id="_7Z35A9UIEdylRpA9TBY1SQ"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_7Z35BNUIEdylRpA9TBY1SQ"/>
+ </notation:Diagram>
+ <uml:Activity xmi:id="_d8SJMN_2EdyOsumnGvWsEg" name="elaboration_phase_iteration">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_d8SJMd_2EdyOsumnGvWsEg" source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_d8SJMt_2EdyOsumnGvWsEg"
+ key="uri" value="uma://_SuWj4NOPEdyqlogshP8l4g#_51ewYdOPEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_d8SJM9_2EdyOsumnGvWsEg"
+ key="type" value="Iteration"/>
+ </eAnnotations>
+ <node xmi:type="uml:JoinNode" xmi:id="_d8SJNN_2EdyOsumnGvWsEg" outgoing="_d8SJXN_2EdyOsumnGvWsEg"
+ incoming="_d8SJUN_2EdyOsumnGvWsEg _d8SJUt_2EdyOsumnGvWsEg _d8SJVN_2EdyOsumnGvWsEg _d8SJVt_2EdyOsumnGvWsEg _d8SJWN_2EdyOsumnGvWsEg _d8SJWt_2EdyOsumnGvWsEg"/>
+ <node xmi:type="uml:ForkNode" xmi:id="_d8SJNd_2EdyOsumnGvWsEg" outgoing="_d8SJUd_2EdyOsumnGvWsEg _d8SJU9_2EdyOsumnGvWsEg _d8SJVd_2EdyOsumnGvWsEg _d8SJV9_2EdyOsumnGvWsEg _d8SJWd_2EdyOsumnGvWsEg _d8SJW9_2EdyOsumnGvWsEg"
+ incoming="_d8SJXd_2EdyOsumnGvWsEg"/>
+ <node xmi:type="uml:ActivityFinalNode" xmi:id="_d8SJNt_2EdyOsumnGvWsEg" incoming="_d8SJXN_2EdyOsumnGvWsEg"/>
+ <node xmi:type="uml:InitialNode" xmi:id="_d8SJN9_2EdyOsumnGvWsEg" outgoing="_d8SJXd_2EdyOsumnGvWsEg"/>
+ <node xmi:type="uml:StructuredActivityNode" xmi:id="_d8SJON_2EdyOsumnGvWsEg" name="Ongoing Tasks"
+ outgoing="_d8SJUN_2EdyOsumnGvWsEg" incoming="_d8SJUd_2EdyOsumnGvWsEg">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_d8SJOd_2EdyOsumnGvWsEg"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_d8SJOt_2EdyOsumnGvWsEg"
+ key="uri" value="uma://_aUsVENONEdyqlogshP8l4g#_g8cPsdOOEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_d8SJO9_2EdyOsumnGvWsEg"
+ key="type" value="Activity"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:StructuredActivityNode" xmi:id="_d8SJPN_2EdyOsumnGvWsEg" name="Test Solution"
+ outgoing="_d8SJUt_2EdyOsumnGvWsEg" incoming="_d8SJU9_2EdyOsumnGvWsEg">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_d8SJPd_2EdyOsumnGvWsEg"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_d8SJPt_2EdyOsumnGvWsEg"
+ key="uri" value="uma://_aUsVENONEdyqlogshP8l4g#_f4VuYdOOEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_d8SJP9_2EdyOsumnGvWsEg"
+ key="type" value="Activity"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:StructuredActivityNode" xmi:id="_d8SJQN_2EdyOsumnGvWsEg" name="Develop Solution Increment"
+ outgoing="_d8SJVt_2EdyOsumnGvWsEg" incoming="_d8SJV9_2EdyOsumnGvWsEg">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_d8SJQd_2EdyOsumnGvWsEg"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_d8SJQt_2EdyOsumnGvWsEg"
+ key="uri" value="uma://_aUsVENONEdyqlogshP8l4g#_eyv_UdOOEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_d8SJQ9_2EdyOsumnGvWsEg"
+ key="type" value="Activity"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:StructuredActivityNode" xmi:id="_d8SJRN_2EdyOsumnGvWsEg" name="Develop the Architecture"
+ outgoing="_d8SJWN_2EdyOsumnGvWsEg" incoming="_d8SJWd_2EdyOsumnGvWsEg">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_d8SJRd_2EdyOsumnGvWsEg"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_d8SJRt_2EdyOsumnGvWsEg"
+ key="uri" value="uma://_aUsVENONEdyqlogshP8l4g#_aSrtcdOOEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_d8SJR9_2EdyOsumnGvWsEg"
+ key="type" value="Activity"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:StructuredActivityNode" xmi:id="_d8SJSN_2EdyOsumnGvWsEg" name="Identify and Refine Requirements"
+ outgoing="_d8SJWt_2EdyOsumnGvWsEg" incoming="_d8SJW9_2EdyOsumnGvWsEg">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_d8SJSd_2EdyOsumnGvWsEg"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_d8SJSt_2EdyOsumnGvWsEg"
+ key="uri" value="uma://_aUsVENONEdyqlogshP8l4g#_YwLY4dOOEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_d8SJS9_2EdyOsumnGvWsEg"
+ key="type" value="Activity"/>
+ </eAnnotations>
+ </node>
+ <node xmi:type="uml:StructuredActivityNode" xmi:id="_d8SJTN_2EdyOsumnGvWsEg" name="Plan and Manage Iteration"
+ outgoing="_d8SJVN_2EdyOsumnGvWsEg" incoming="_d8SJVd_2EdyOsumnGvWsEg">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_d8SJTd_2EdyOsumnGvWsEg"
+ source="uma_element">
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_d8SJTt_2EdyOsumnGvWsEg"
+ key="uri" value="uma://_aUsVENONEdyqlogshP8l4g#_XayTQdOOEdyqlogshP8l4g"/>
+ <details xmi:type="ecore:EStringToStringMapEntry" xmi:id="_d8SJT9_2EdyOsumnGvWsEg"
+ key="type" value="Activity"/>
+ </eAnnotations>
+ </node>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_d8SJUN_2EdyOsumnGvWsEg" source="_d8SJON_2EdyOsumnGvWsEg"
+ target="_d8SJNN_2EdyOsumnGvWsEg"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_d8SJUd_2EdyOsumnGvWsEg" source="_d8SJNd_2EdyOsumnGvWsEg"
+ target="_d8SJON_2EdyOsumnGvWsEg"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_d8SJUt_2EdyOsumnGvWsEg" source="_d8SJPN_2EdyOsumnGvWsEg"
+ target="_d8SJNN_2EdyOsumnGvWsEg"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_d8SJU9_2EdyOsumnGvWsEg" source="_d8SJNd_2EdyOsumnGvWsEg"
+ target="_d8SJPN_2EdyOsumnGvWsEg"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_d8SJVN_2EdyOsumnGvWsEg" source="_d8SJTN_2EdyOsumnGvWsEg"
+ target="_d8SJNN_2EdyOsumnGvWsEg"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_d8SJVd_2EdyOsumnGvWsEg" source="_d8SJNd_2EdyOsumnGvWsEg"
+ target="_d8SJTN_2EdyOsumnGvWsEg"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_d8SJVt_2EdyOsumnGvWsEg" source="_d8SJQN_2EdyOsumnGvWsEg"
+ target="_d8SJNN_2EdyOsumnGvWsEg"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_d8SJV9_2EdyOsumnGvWsEg" source="_d8SJNd_2EdyOsumnGvWsEg"
+ target="_d8SJQN_2EdyOsumnGvWsEg"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_d8SJWN_2EdyOsumnGvWsEg" source="_d8SJRN_2EdyOsumnGvWsEg"
+ target="_d8SJNN_2EdyOsumnGvWsEg"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_d8SJWd_2EdyOsumnGvWsEg" source="_d8SJNd_2EdyOsumnGvWsEg"
+ target="_d8SJRN_2EdyOsumnGvWsEg"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_d8SJWt_2EdyOsumnGvWsEg" source="_d8SJSN_2EdyOsumnGvWsEg"
+ target="_d8SJNN_2EdyOsumnGvWsEg"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_d8SJW9_2EdyOsumnGvWsEg" source="_d8SJNd_2EdyOsumnGvWsEg"
+ target="_d8SJSN_2EdyOsumnGvWsEg"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_d8SJXN_2EdyOsumnGvWsEg" source="_d8SJNN_2EdyOsumnGvWsEg"
+ target="_d8SJNt_2EdyOsumnGvWsEg"/>
+ <edge xmi:type="uml:ControlFlow" xmi:id="_d8SJXd_2EdyOsumnGvWsEg" source="_d8SJN9_2EdyOsumnGvWsEg"
+ target="_d8SJNd_2EdyOsumnGvWsEg"/>
+ </uml:Activity>
+ <notation:Diagram xmi:id="_d8SJXt_2EdyOsumnGvWsEg" type="AD" element="_d8SJMN_2EdyOsumnGvWsEg"
+ name="elaboration_phase_iteration" measurementUnit="Pixel">
+ <children xmi:type="notation:Node" xmi:id="_d8SJX9_2EdyOsumnGvWsEg" type="1007"
+ element="_d8SJTN_2EdyOsumnGvWsEg">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_d8SJYN_2EdyOsumnGvWsEg"
+ source="inherited"/>
+ <children xmi:type="notation:Node" xmi:id="_d8SJYd_2EdyOsumnGvWsEg" type="4005"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_d8SJYt_2EdyOsumnGvWsEg" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_d8SJY9_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_d8SJZN_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_d8SJZd_2EdyOsumnGvWsEg" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_d8SJZt_2EdyOsumnGvWsEg"
+ x="456" y="156"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_d8SJZ9_2EdyOsumnGvWsEg" type="1007"
+ element="_d8SJSN_2EdyOsumnGvWsEg">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_d8SJaN_2EdyOsumnGvWsEg"
+ source="inherited"/>
+ <children xmi:type="notation:Node" xmi:id="_d8SJad_2EdyOsumnGvWsEg" type="4005"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_d8SJat_2EdyOsumnGvWsEg" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_d8SJa9_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_d8SJbN_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_d8SJbd_2EdyOsumnGvWsEg" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_d8SJbt_2EdyOsumnGvWsEg"
+ x="36" y="156"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_d8SJb9_2EdyOsumnGvWsEg" type="1007"
+ element="_d8SJRN_2EdyOsumnGvWsEg">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_d8SJcN_2EdyOsumnGvWsEg"
+ source="inherited"/>
+ <children xmi:type="notation:Node" xmi:id="_d8SJcd_2EdyOsumnGvWsEg" type="4005"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_d8SJct_2EdyOsumnGvWsEg" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_d8SJc9_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_d8SJdN_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_d8SJdd_2EdyOsumnGvWsEg" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_d8SJdt_2EdyOsumnGvWsEg"
+ x="180" y="204"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_d8SJd9_2EdyOsumnGvWsEg" type="1007"
+ element="_d8SJQN_2EdyOsumnGvWsEg">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_d8SJeN_2EdyOsumnGvWsEg"
+ source="inherited"/>
+ <children xmi:type="notation:Node" xmi:id="_d8SJed_2EdyOsumnGvWsEg" type="4005"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_d8SJet_2EdyOsumnGvWsEg" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_d8SJe9_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_d8SJfN_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_d8SJfd_2EdyOsumnGvWsEg" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_d8SJft_2EdyOsumnGvWsEg"
+ x="288" y="240"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_d8SJf9_2EdyOsumnGvWsEg" type="1007"
+ element="_d8SJPN_2EdyOsumnGvWsEg">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_d8SJgN_2EdyOsumnGvWsEg"
+ source="inherited"/>
+ <children xmi:type="notation:Node" xmi:id="_d8SJgd_2EdyOsumnGvWsEg" type="4005"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_d8SJgt_2EdyOsumnGvWsEg" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_d8SJg9_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_d8SJhN_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_d8SJhd_2EdyOsumnGvWsEg" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_d8SJht_2EdyOsumnGvWsEg"
+ x="408" y="300"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_d8SJh9_2EdyOsumnGvWsEg" type="1007"
+ element="_d8SJON_2EdyOsumnGvWsEg">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_d8SJiN_2EdyOsumnGvWsEg"
+ source="inherited"/>
+ <children xmi:type="notation:Node" xmi:id="_d8SJid_2EdyOsumnGvWsEg" type="4005"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_d8SJit_2EdyOsumnGvWsEg" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_d8SJi9_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_d8SJjN_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_d8SJjd_2EdyOsumnGvWsEg" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_d8SJjt_2EdyOsumnGvWsEg"
+ x="576" y="228"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_d8SJj9_2EdyOsumnGvWsEg" type="1004"
+ element="_d8SJN9_2EdyOsumnGvWsEg">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_d8SJkN_2EdyOsumnGvWsEg"
+ source="inherited"/>
+ <children xmi:type="notation:Node" xmi:id="_d8SJkd_2EdyOsumnGvWsEg" type="4003">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_d8SJkt_2EdyOsumnGvWsEg"
+ y="5"/>
+ </children>
+ <styles xmi:type="notation:FontStyle" xmi:id="_d8SJk9_2EdyOsumnGvWsEg" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_d8SJlN_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_d8SJld_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_d8SJlt_2EdyOsumnGvWsEg" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_d8SJl9_2EdyOsumnGvWsEg"
+ x="343" y="56"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_d8SJmN_2EdyOsumnGvWsEg" type="1001"
+ element="_d8SJNt_2EdyOsumnGvWsEg">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_d8SJmd_2EdyOsumnGvWsEg"
+ source="inherited"/>
+ <children xmi:type="notation:Node" xmi:id="_d8SJmt_2EdyOsumnGvWsEg" type="4001">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_d8SJm9_2EdyOsumnGvWsEg"
+ y="5"/>
+ </children>
+ <styles xmi:type="notation:FontStyle" xmi:id="_d8SJnN_2EdyOsumnGvWsEg" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_d8SJnd_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_d8SJnt_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_d8SJn9_2EdyOsumnGvWsEg" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_d8SJoN_2EdyOsumnGvWsEg"
+ x="347" y="419"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_d8SJod_2EdyOsumnGvWsEg" type="1003"
+ element="_d8SJNd_2EdyOsumnGvWsEg">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_d8SJot_2EdyOsumnGvWsEg"
+ source="inherited"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_d8SJo9_2EdyOsumnGvWsEg" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_d8SJpN_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_d8SJpd_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_d8SJpt_2EdyOsumnGvWsEg" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_d8SJp9_2EdyOsumnGvWsEg"
+ x="36" y="108" width="637"/>
+ </children>
+ <children xmi:type="notation:Node" xmi:id="_d8SJqN_2EdyOsumnGvWsEg" type="1006"
+ element="_d8SJNN_2EdyOsumnGvWsEg">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_d8SJqd_2EdyOsumnGvWsEg"
+ source="inherited"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_d8SJqt_2EdyOsumnGvWsEg" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_d8SJq9_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:FillStyle" xmi:id="_d8SJrN_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_d8SJrd_2EdyOsumnGvWsEg" lineColor="0"/>
+ <layoutConstraint xmi:type="notation:Bounds" xmi:id="_d8SJrt_2EdyOsumnGvWsEg"
+ x="36" y="372" width="637"/>
+ </children>
+ <styles xmi:type="notation:PageStyle" xmi:id="_d8SJr9_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:GuideStyle" xmi:id="_d8SJsN_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:DescriptionStyle" xmi:id="_d8SJsd_2EdyOsumnGvWsEg"/>
+ <edges xmi:type="notation:Edge" xmi:id="_d8SJst_2EdyOsumnGvWsEg" type="3001" element="_d8SJXd_2EdyOsumnGvWsEg"
+ source="_d8SJj9_2EdyOsumnGvWsEg" target="_d8SJod_2EdyOsumnGvWsEg">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_d8SJs9_2EdyOsumnGvWsEg"
+ source="inherited"/>
+ <children xmi:type="notation:Node" xmi:id="_d8SJtN_2EdyOsumnGvWsEg" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_d8SJtd_2EdyOsumnGvWsEg"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_d8SJtt_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_d8SJt9_2EdyOsumnGvWsEg" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_d8SJuN_2EdyOsumnGvWsEg" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_d8SJud_2EdyOsumnGvWsEg"
+ points="[1, 10, 0, -36]$[1, 42, 0, -4]"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_d8SJut_2EdyOsumnGvWsEg" type="3001" element="_d8SJXN_2EdyOsumnGvWsEg"
+ source="_d8SJqN_2EdyOsumnGvWsEg" target="_d8SJmN_2EdyOsumnGvWsEg">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_d8SJu9_2EdyOsumnGvWsEg"
+ source="inherited"/>
+ <children xmi:type="notation:Node" xmi:id="_d8SJvN_2EdyOsumnGvWsEg" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_d8SJvd_2EdyOsumnGvWsEg"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_d8SJvt_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_d8SJv9_2EdyOsumnGvWsEg" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_d8SJwN_2EdyOsumnGvWsEg" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_d8SJwd_2EdyOsumnGvWsEg"
+ points="[0, 4, -5, -51]$[-7, 57, -12, 2]"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_d8SJwt_2EdyOsumnGvWsEg" type="3001" element="_d8SJW9_2EdyOsumnGvWsEg"
+ source="_d8SJod_2EdyOsumnGvWsEg" target="_d8SJZ9_2EdyOsumnGvWsEg">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_d8SJw9_2EdyOsumnGvWsEg"
+ source="inherited"/>
+ <children xmi:type="notation:Node" xmi:id="_d8SJxN_2EdyOsumnGvWsEg" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_d8SJxd_2EdyOsumnGvWsEg"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_d8SJxt_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_d8SJx9_2EdyOsumnGvWsEg" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_d8SJyN_2EdyOsumnGvWsEg" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_d8SJyd_2EdyOsumnGvWsEg"
+ points="[0, 5, 0, -52]$[-3, 45, -3, -12]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_d8SJyt_2EdyOsumnGvWsEg"
+ id="(0.1255887,0.375)"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_d8SJy9_2EdyOsumnGvWsEg"
+ id="(0.4790419,0.2264151)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_d8SJzN_2EdyOsumnGvWsEg" type="3001" element="_d8SJWt_2EdyOsumnGvWsEg"
+ source="_d8SJZ9_2EdyOsumnGvWsEg" target="_d8SJqN_2EdyOsumnGvWsEg">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_d8SJzd_2EdyOsumnGvWsEg"
+ source="inherited"/>
+ <children xmi:type="notation:Node" xmi:id="_d8SJzt_2EdyOsumnGvWsEg" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_d8SJz9_2EdyOsumnGvWsEg"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_d8SJ0N_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_d8SJ0d_2EdyOsumnGvWsEg" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_d8SJ0t_2EdyOsumnGvWsEg" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_d8SJ09_2EdyOsumnGvWsEg"
+ points="[0, 27, 0, -166]$[-83, 193, -83, 0]"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_d8SJ1N_2EdyOsumnGvWsEg"
+ id="(0.13029827,0.375)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_d8SJ1d_2EdyOsumnGvWsEg" type="3001" element="_d8SJWd_2EdyOsumnGvWsEg"
+ source="_d8SJod_2EdyOsumnGvWsEg" target="_d8SJb9_2EdyOsumnGvWsEg">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_d8SJ1t_2EdyOsumnGvWsEg"
+ source="inherited"/>
+ <children xmi:type="notation:Node" xmi:id="_d8SJ19_2EdyOsumnGvWsEg" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_d8SJ2N_2EdyOsumnGvWsEg"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_d8SJ2d_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_d8SJ2t_2EdyOsumnGvWsEg" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_d8SJ29_2EdyOsumnGvWsEg" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_d8SJ3N_2EdyOsumnGvWsEg"
+ points="[-4, 4, 107, -114]$[-110, 92, 1, -26]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_d8SJ3d_2EdyOsumnGvWsEg"
+ id="(0.31711146,0.125)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_d8SJ3t_2EdyOsumnGvWsEg" type="3001" element="_d8SJWN_2EdyOsumnGvWsEg"
+ source="_d8SJb9_2EdyOsumnGvWsEg" target="_d8SJqN_2EdyOsumnGvWsEg">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_d8SJ39_2EdyOsumnGvWsEg"
+ source="inherited"/>
+ <children xmi:type="notation:Node" xmi:id="_d8SJ4N_2EdyOsumnGvWsEg" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_d8SJ4d_2EdyOsumnGvWsEg"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_d8SJ4t_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_d8SJ49_2EdyOsumnGvWsEg" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_d8SJ5N_2EdyOsumnGvWsEg" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_d8SJ5d_2EdyOsumnGvWsEg"
+ points="[-8, 27, -119, -119]$[-207, 144, -318, -2]"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_d8SJ5t_2EdyOsumnGvWsEg"
+ id="(0.3233909,0.125)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_d8SJ59_2EdyOsumnGvWsEg" type="3001" element="_d8SJV9_2EdyOsumnGvWsEg"
+ source="_d8SJod_2EdyOsumnGvWsEg" target="_d8SJd9_2EdyOsumnGvWsEg">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_d8SJ6N_2EdyOsumnGvWsEg"
+ source="inherited"/>
+ <children xmi:type="notation:Node" xmi:id="_d8SJ6d_2EdyOsumnGvWsEg" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_d8SJ6t_2EdyOsumnGvWsEg"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_d8SJ69_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_d8SJ7N_2EdyOsumnGvWsEg" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_d8SJ7d_2EdyOsumnGvWsEg" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_d8SJ7t_2EdyOsumnGvWsEg"
+ points="[-2, 4, 0, -149]$[-6, 140, -4, -13]"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_d8SJ79_2EdyOsumnGvWsEg"
+ id="(0.46715328,0.24528302)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_d8SJ8N_2EdyOsumnGvWsEg" type="3001" element="_d8SJVt_2EdyOsumnGvWsEg"
+ source="_d8SJd9_2EdyOsumnGvWsEg" target="_d8SJqN_2EdyOsumnGvWsEg">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_d8SJ8d_2EdyOsumnGvWsEg"
+ source="inherited"/>
+ <children xmi:type="notation:Node" xmi:id="_d8SJ8t_2EdyOsumnGvWsEg" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_d8SJ89_2EdyOsumnGvWsEg"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_d8SJ9N_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_d8SJ9d_2EdyOsumnGvWsEg" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_d8SJ9t_2EdyOsumnGvWsEg" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_d8SJ99_2EdyOsumnGvWsEg"
+ points="[6, 27, 8, -71]$[317, 96, 319, -2]"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_d8SJ-N_2EdyOsumnGvWsEg" type="3001" element="_d8SJVd_2EdyOsumnGvWsEg"
+ source="_d8SJod_2EdyOsumnGvWsEg" target="_d8SJX9_2EdyOsumnGvWsEg">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_d8SJ-d_2EdyOsumnGvWsEg"
+ source="inherited"/>
+ <children xmi:type="notation:Node" xmi:id="_d8SJ-t_2EdyOsumnGvWsEg" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_d8SJ-9_2EdyOsumnGvWsEg"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_d8SJ_N_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_d8SJ_d_2EdyOsumnGvWsEg" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_d8SJ_t_2EdyOsumnGvWsEg" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_d8SJ_9_2EdyOsumnGvWsEg"
+ points="[9, 4, -134, -66]$[143, 44, 0, -26]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_d8SKAN_2EdyOsumnGvWsEg"
+ id="(0.7566719,0.125)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_d8SKAd_2EdyOsumnGvWsEg" type="3001" element="_d8SJVN_2EdyOsumnGvWsEg"
+ source="_d8SJX9_2EdyOsumnGvWsEg" target="_d8SJqN_2EdyOsumnGvWsEg">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_d8SKAt_2EdyOsumnGvWsEg"
+ source="inherited"/>
+ <children xmi:type="notation:Node" xmi:id="_d8SKA9_2EdyOsumnGvWsEg" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_d8SKBN_2EdyOsumnGvWsEg"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_d8SKBd_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_d8SKBt_2EdyOsumnGvWsEg" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_d8SKB9_2EdyOsumnGvWsEg" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_d8SKCN_2EdyOsumnGvWsEg"
+ points="[1, 27, -9, -164]$[61, 190, 51, -1]"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_d8SKCd_2EdyOsumnGvWsEg"
+ id="(0.75981164,0.125)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_d8SKCt_2EdyOsumnGvWsEg" type="3001" element="_d8SJU9_2EdyOsumnGvWsEg"
+ source="_d8SJod_2EdyOsumnGvWsEg" target="_d8SJf9_2EdyOsumnGvWsEg">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_d8SKC9_2EdyOsumnGvWsEg"
+ source="inherited"/>
+ <children xmi:type="notation:Node" xmi:id="_d8SKDN_2EdyOsumnGvWsEg" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_d8SKDd_2EdyOsumnGvWsEg"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_d8SKDt_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_d8SKD9_2EdyOsumnGvWsEg" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_d8SKEN_2EdyOsumnGvWsEg" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_d8SKEd_2EdyOsumnGvWsEg"
+ points="[2, 4, -88, -215]$[96, 193, 6, -26]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_d8SKEt_2EdyOsumnGvWsEg"
+ id="(0.64364207,0.875)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_d8SKE9_2EdyOsumnGvWsEg" type="3001" element="_d8SJUt_2EdyOsumnGvWsEg"
+ source="_d8SJf9_2EdyOsumnGvWsEg" target="_d8SJqN_2EdyOsumnGvWsEg">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_d8SKFN_2EdyOsumnGvWsEg"
+ source="inherited"/>
+ <children xmi:type="notation:Node" xmi:id="_d8SKFd_2EdyOsumnGvWsEg" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_d8SKFt_2EdyOsumnGvWsEg"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_d8SKF9_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_d8SKGN_2EdyOsumnGvWsEg" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_d8SKGd_2EdyOsumnGvWsEg" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_d8SKGt_2EdyOsumnGvWsEg"
+ points="[-1, 27, 89, -18]$[229, 44, 319, -1]"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_d8SKG9_2EdyOsumnGvWsEg"
+ id="(0.63265306,0.125)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_d8SKHN_2EdyOsumnGvWsEg" type="3001" element="_d8SJUd_2EdyOsumnGvWsEg"
+ source="_d8SJod_2EdyOsumnGvWsEg" target="_d8SJh9_2EdyOsumnGvWsEg">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_d8SKHd_2EdyOsumnGvWsEg"
+ source="inherited"/>
+ <children xmi:type="notation:Node" xmi:id="_d8SKHt_2EdyOsumnGvWsEg" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_d8SKH9_2EdyOsumnGvWsEg"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_d8SKIN_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_d8SKId_2EdyOsumnGvWsEg" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_d8SKIt_2EdyOsumnGvWsEg" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_d8SKI9_2EdyOsumnGvWsEg"
+ points="[3, 7, -51, -138]$[56, 119, 2, -26]"/>
+ <sourceAnchor xmi:type="notation:IdentityAnchor" xmi:id="_d8SKJN_2EdyOsumnGvWsEg"
+ id="(0.9136578,0.0)"/>
+ </edges>
+ <edges xmi:type="notation:Edge" xmi:id="_d8SKJd_2EdyOsumnGvWsEg" type="3001" element="_d8SJUN_2EdyOsumnGvWsEg"
+ source="_d8SJh9_2EdyOsumnGvWsEg" target="_d8SJqN_2EdyOsumnGvWsEg">
+ <eAnnotations xmi:type="ecore:EAnnotation" xmi:id="_d8SKJt_2EdyOsumnGvWsEg"
+ source="inherited"/>
+ <children xmi:type="notation:Node" xmi:id="_d8SKJ9_2EdyOsumnGvWsEg" type="4012">
+ <layoutConstraint xmi:type="notation:Location" xmi:id="_d8SKKN_2EdyOsumnGvWsEg"
+ y="40"/>
+ </children>
+ <styles xmi:type="notation:RoutingStyle" xmi:id="_d8SKKd_2EdyOsumnGvWsEg"/>
+ <styles xmi:type="notation:FontStyle" xmi:id="_d8SKKt_2EdyOsumnGvWsEg" fontName="Arial"
+ fontHeight="8"/>
+ <styles xmi:type="notation:LineStyle" xmi:id="_d8SKK9_2EdyOsumnGvWsEg" lineColor="0"/>
+ <bendpoints xmi:type="notation:RelativeBendpoints" xmi:id="_d8SKLN_2EdyOsumnGvWsEg"
+ points="[3, 27, 0, -94]$[59, 121, 56, 0]"/>
+ <targetAnchor xmi:type="notation:IdentityAnchor" xmi:id="_d8SKLd_2EdyOsumnGvWsEg"
+ id="(0.9120879,0.375)"/>
+ </edges>
+ </notation:Diagram>
+</xmi:XMI>
diff --git a/praclib/temp/process.openup.base/deliveryprocesses/openup_lifecycle/model.xmi b/praclib/temp/process.openup.base/deliveryprocesses/openup_lifecycle/model.xmi
new file mode 100644
index 0000000..f42cc05
--- /dev/null
+++ b/praclib/temp/process.openup.base/deliveryprocesses/openup_lifecycle/model.xmi
@@ -0,0 +1,92 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_SwvJgdOPEdyqlogshP8l4g"
+ guid="_SwvJgdOPEdyqlogshP8l4g">
+ <resourceDescriptors xmi:id="_Sw46gNOPEdyqlogshP8l4g" id="-dV7s6ZJXratblG37Lbu0mw"
+ uri="content.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:ProcessComponent xmi:id="_SuWj4NOPEdyqlogshP8l4g" name="openup_lifecycle"
+ guid="_SuWj4NOPEdyqlogshP8l4g">
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_kYVSUNOPEdyqlogshP8l4g"
+ name="inception_phase_iteration" guid="_kYVSUNOPEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:Iteration" xmi:id="_kYVSUdOPEdyqlogshP8l4g"
+ name="inception_phase_iteration" guid="_kYVSUdOPEdyqlogshP8l4g" presentationName="Inception Phase Iteration [1..n]"
+ superActivities="_SuWj4dOPEdyqlogshP8l4g" variabilityType="extends">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://_h0Gs8NONEdyqlogshP8l4g#_h0Gs8dONEdyqlogshP8l4g"/>
+ </processElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_51ewYNOPEdyqlogshP8l4g"
+ name="elaboration_phase_iteration" guid="_51ewYNOPEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:Iteration" xmi:id="_51ewYdOPEdyqlogshP8l4g"
+ name="elaboration_phase_iteration" guid="_51ewYdOPEdyqlogshP8l4g" presentationName="Elaboration Phase Iteration [1..n]"
+ superActivities="_SuWj4dOPEdyqlogshP8l4g" linkToPredecessor="_zrXxsNUHEdylRpA9TBY1SQ"
+ variabilityType="extends">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://_aUsVENONEdyqlogshP8l4g#_aUsVEdONEdyqlogshP8l4g"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_zrXxsNUHEdylRpA9TBY1SQ"
+ guid="_zrXxsNUHEdylRpA9TBY1SQ" pred="_l_0NgNOPEdyqlogshP8l4g"/>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_6togYNOPEdyqlogshP8l4g"
+ name="construction_phase_iteration" guid="_6togYNOPEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:Iteration" xmi:id="_6togYdOPEdyqlogshP8l4g"
+ name="construction_phase_iteration" guid="_6togYdOPEdyqlogshP8l4g" presentationName="Construction Phase Iteration [1..n]"
+ superActivities="_SuWj4dOPEdyqlogshP8l4g" linkToPredecessor="_1qxdoNUHEdylRpA9TBY1SQ"
+ variabilityType="extends">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://_RQi0ANONEdyqlogshP8l4g#_RQi0AdONEdyqlogshP8l4g"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_1qxdoNUHEdylRpA9TBY1SQ"
+ guid="_1qxdoNUHEdylRpA9TBY1SQ" pred="_9P2lgNOPEdyqlogshP8l4g"/>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_7bg6ENOPEdyqlogshP8l4g"
+ name="transition_phase_iteration" guid="_7bg6ENOPEdyqlogshP8l4g">
+ <processElements xsi:type="org.eclipse.epf.uma:Iteration" xmi:id="_7bg6EdOPEdyqlogshP8l4g"
+ name="transition_phase_iteration" guid="_7bg6EdOPEdyqlogshP8l4g" presentationName="Transition Phase Iteration [1..n]"
+ superActivities="_SuWj4dOPEdyqlogshP8l4g" linkToPredecessor="_6EkIYNUHEdylRpA9TBY1SQ"
+ variabilityType="extends">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://_pzQU0NONEdyqlogshP8l4g#_pzQU0dONEdyqlogshP8l4g"/>
+ </processElements>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_6EkIYNUHEdylRpA9TBY1SQ"
+ guid="_6EkIYNUHEdylRpA9TBY1SQ" pred="_Ik_RwNOQEdyqlogshP8l4g"/>
+ </childPackages>
+ <processElements xsi:type="org.eclipse.epf.uma:Milestone" xmi:id="_l_0NgNOPEdyqlogshP8l4g"
+ name="lifecycle_objectives_milestone" guid="_l_0NgNOPEdyqlogshP8l4g" presentationName="Lifecycle Objectives Milestone"
+ superActivities="_SuWj4dOPEdyqlogshP8l4g" linkToPredecessor="_xUuDYNUHEdylRpA9TBY1SQ"/>
+ <processElements xsi:type="org.eclipse.epf.uma:Milestone" xmi:id="_9P2lgNOPEdyqlogshP8l4g"
+ name="lifecycle_architecture_milestone" guid="_9P2lgNOPEdyqlogshP8l4g" presentationName="Lifecycle Architecture Milestone"
+ superActivities="_SuWj4dOPEdyqlogshP8l4g" linkToPredecessor="_0IkrENUHEdylRpA9TBY1SQ"/>
+ <processElements xsi:type="org.eclipse.epf.uma:Milestone" xmi:id="_Ik_RwNOQEdyqlogshP8l4g"
+ name="initial_operational_capability_milestone" guid="_Ik_RwNOQEdyqlogshP8l4g"
+ presentationName="Initial Operational Capability Milestone" superActivities="_SuWj4dOPEdyqlogshP8l4g"
+ linkToPredecessor="_2HPXMNUHEdylRpA9TBY1SQ"/>
+ <processElements xsi:type="org.eclipse.epf.uma:Milestone" xmi:id="_SYGxoNOQEdyqlogshP8l4g"
+ name="product_release_milestone" guid="_SYGxoNOQEdyqlogshP8l4g" presentationName="Product Release Milestone"
+ superActivities="_SuWj4dOPEdyqlogshP8l4g" linkToPredecessor="_6yT_MNUHEdylRpA9TBY1SQ"/>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_xUuDYNUHEdylRpA9TBY1SQ"
+ guid="_xUuDYNUHEdylRpA9TBY1SQ" pred="_kYVSUdOPEdyqlogshP8l4g"/>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_0IkrENUHEdylRpA9TBY1SQ"
+ guid="_0IkrENUHEdylRpA9TBY1SQ" pred="_51ewYdOPEdyqlogshP8l4g"/>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_2HPXMNUHEdylRpA9TBY1SQ"
+ guid="_2HPXMNUHEdylRpA9TBY1SQ" pred="_6togYdOPEdyqlogshP8l4g"/>
+ <processElements xsi:type="org.eclipse.epf.uma:WorkOrder" xmi:id="_6yT_MNUHEdylRpA9TBY1SQ"
+ guid="_6yT_MNUHEdylRpA9TBY1SQ" pred="_7bg6EdOPEdyqlogshP8l4g"/>
+ <process xsi:type="org.eclipse.epf.uma:DeliveryProcess" xmi:id="_SuWj4dOPEdyqlogshP8l4g"
+ name="openup_lifecycle" guid="_SuWj4dOPEdyqlogshP8l4g" briefDescription="This delivery process defines an end-to-end software development lifecycle that supports the core principles of OpenUP. It is designed to support small, co-located teams in their daily activities."
+ presentationName="OpenUP Lifecycle" breakdownElements="_kYVSUdOPEdyqlogshP8l4g _l_0NgNOPEdyqlogshP8l4g _51ewYdOPEdyqlogshP8l4g _9P2lgNOPEdyqlogshP8l4g _6togYdOPEdyqlogshP8l4g _Ik_RwNOQEdyqlogshP8l4g _7bg6EdOPEdyqlogshP8l4g _SYGxoNOQEdyqlogshP8l4g">
+ <presentation xmi:id="-dV7s6ZJXratblG37Lbu0mw" href="uma://-dV7s6ZJXratblG37Lbu0mw#-dV7s6ZJXratblG37Lbu0mw"/>
+ <includesPatterns href="uma://_h0Gs8NONEdyqlogshP8l4g#_h0Gs8dONEdyqlogshP8l4g"/>
+ <includesPatterns href="uma://_aUsVENONEdyqlogshP8l4g#_aUsVEdONEdyqlogshP8l4g"/>
+ <includesPatterns href="uma://_RQi0ANONEdyqlogshP8l4g#_RQi0AdONEdyqlogshP8l4g"/>
+ <includesPatterns href="uma://_pzQU0NONEdyqlogshP8l4g#_pzQU0dONEdyqlogshP8l4g"/>
+ <defaultContext href="uma://_0NAjrNUAEdylRpA9TBY1SQ#_gExDwNQxEdyk9oc_L5Vk0g"/>
+ <validContext href="uma://_0NAjrNUAEdylRpA9TBY1SQ#_gExDwNQxEdyk9oc_L5Vk0g"/>
+ </process>
+ </org.eclipse.epf.uma:ProcessComponent>
+</xmi:XMI>
diff --git a/praclib/temp/process.openup.base/plugin.xmi b/praclib/temp/process.openup.base/plugin.xmi
new file mode 100644
index 0000000..105a04a
--- /dev/null
+++ b/praclib/temp/process.openup.base/plugin.xmi
@@ -0,0 +1,192 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_Z7teENQ1EdyQ89W1tgswSQ"
+ guid="_Z7teENQ1EdyQ89W1tgswSQ">
+ <subManagers xmi:id="_h3rlYdONEdyqlogshP8l4g" href="uma://_h0Gs8NONEdyqlogshP8l4g#_h3rlYdONEdyqlogshP8l4g"/>
+ <subManagers xmi:id="_RZo_QdOFEdyqlogshP8l4g" href="uma://_RXGooNOFEdyqlogshP8l4g#_RZo_QdOFEdyqlogshP8l4g"/>
+ <subManagers xmi:id="_eZJ_INOEEdyqlogshP8l4g" href="uma://_eWxZgNOEEdyqlogshP8l4g#_eZJ_INOEEdyqlogshP8l4g"/>
+ <subManagers xmi:id="_KdJuQNOFEdyqlogshP8l4g" href="uma://_KaeNsNOFEdyqlogshP8l4g#_KdJuQNOFEdyqlogshP8l4g"/>
+ <subManagers xmi:id="_bwfeUdOFEdyqlogshP8l4g" href="uma://_buG4sNOFEdyqlogshP8l4g#_bwfeUdOFEdyqlogshP8l4g"/>
+ <subManagers xmi:id="_xzZKQdOEEdyqlogshP8l4g" href="uma://_xxcpgNOEEdyqlogshP8l4g#_xzZKQdOEEdyqlogshP8l4g"/>
+ <subManagers xmi:id="_p2--QdONEdyqlogshP8l4g" href="uma://_pzQU0NONEdyqlogshP8l4g#_p2--QdONEdyqlogshP8l4g"/>
+ <subManagers xmi:id="_aYkvgNONEdyqlogshP8l4g" href="uma://_aUsVENONEdyqlogshP8l4g#_aYkvgNONEdyqlogshP8l4g"/>
+ <subManagers xmi:id="_RSetsdONEdyqlogshP8l4g" href="uma://_RQi0ANONEdyqlogshP8l4g#_RSetsdONEdyqlogshP8l4g"/>
+ <subManagers xmi:id="_4q9fAdOEEdyqlogshP8l4g" href="uma://_4ouDUNOEEdyqlogshP8l4g#_4q9fAdOEEdyqlogshP8l4g"/>
+ <subManagers xmi:id="_ob4oUdOEEdyqlogshP8l4g" href="uma://_oZgCsNOEEdyqlogshP8l4g#_ob4oUdOEEdyqlogshP8l4g"/>
+ <subManagers xmi:id="__ctfodOEEdyqlogshP8l4g" href="uma://__ZInMNOEEdyqlogshP8l4g#__ctfodOEEdyqlogshP8l4g"/>
+ <subManagers xmi:id="_SwvJgdOPEdyqlogshP8l4g" href="uma://_SuWj4NOPEdyqlogshP8l4g#_SwvJgdOPEdyqlogshP8l4g"/>
+ <resourceDescriptors xmi:id="_h15csNONEdyqlogshP8l4g" id="_h0Gs8NONEdyqlogshP8l4g"
+ uri="capabilitypatterns/inception_phase_iteration/model.xmi"/>
+ <resourceDescriptors xmi:id="_RXQZoNOFEdyqlogshP8l4g" id="_RXGooNOFEdyqlogshP8l4g"
+ uri="capabilitypatterns/develop_solution/model.xmi"/>
+ <resourceDescriptors xmi:id="_eW6jcdOEEdyqlogshP8l4g" id="_eWxZgNOEEdyqlogshP8l4g"
+ uri="capabilitypatterns/initiate_project/model.xmi"/>
+ <resourceDescriptors xmi:id="_KaeNs9OFEdyqlogshP8l4g" id="_KaeNsNOFEdyqlogshP8l4g"
+ uri="capabilitypatterns/develop_architecture/model.xmi"/>
+ <resourceDescriptors xmi:id="_buG4s9OFEdyqlogshP8l4g" id="_buG4sNOFEdyqlogshP8l4g"
+ uri="capabilitypatterns/test_solution/model.xmi"/>
+ <resourceDescriptors xmi:id="_xxmagdOEEdyqlogshP8l4g" id="_xxcpgNOEEdyqlogshP8l4g"
+ uri="capabilitypatterns/identify_and_refine_requirements/model.xmi"/>
+ <resourceDescriptors xmi:id="_p0wJodONEdyqlogshP8l4g" id="_pzQU0NONEdyqlogshP8l4g"
+ uri="capabilitypatterns/transition_phase_iteration/model.xmi"/>
+ <resourceDescriptors xmi:id="_aWVT0dONEdyqlogshP8l4g" id="_aUsVENONEdyqlogshP8l4g"
+ uri="capabilitypatterns/elaboration_phase_iteration/model.xmi"/>
+ <resourceDescriptors xmi:id="_RQi0A9ONEdyqlogshP8l4g" id="_RQi0ANONEdyqlogshP8l4g"
+ uri="capabilitypatterns/construction_phase_iteration/model.xmi"/>
+ <resourceDescriptors xmi:id="_4ouDU9OEEdyqlogshP8l4g" id="_4ouDUNOEEdyqlogshP8l4g"
+ uri="capabilitypatterns/agree_technical_approach/model.xmi"/>
+ <resourceDescriptors xmi:id="_oZpModOEEdyqlogshP8l4g" id="_oZgCsNOEEdyqlogshP8l4g"
+ uri="capabilitypatterns/plan_manage_iteration/model.xmi"/>
+ <resourceDescriptors xmi:id="__ZSYMdOEEdyqlogshP8l4g" id="__ZInMNOEEdyqlogshP8l4g"
+ uri="capabilitypatterns/ongoing_tasks/model.xmi"/>
+ <resourceDescriptors xmi:id="_SuWj49OPEdyqlogshP8l4g" id="_SuWj4NOPEdyqlogshP8l4g"
+ uri="deliveryprocesses/openup_lifecycle/model.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_Z7teANQ1EdyQ89W1tgswSQ" name="process.openup.base"
+ guid="_Z7teANQ1EdyQ89W1tgswSQ" changeDate="2008-02-05T13:59:23.484-0800">
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Z7teAdQ1EdyQ89W1tgswSQ"
+ name="Content" guid="_Z7teAdQ1EdyQ89W1tgswSQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Z7teAtQ1EdyQ89W1tgswSQ"
+ name="Categories" guid="_Z7teAtQ1EdyQ89W1tgswSQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Z7teA9Q1EdyQ89W1tgswSQ"
+ name="Domains" guid="_Z7teA9Q1EdyQ89W1tgswSQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Z7teBNQ1EdyQ89W1tgswSQ"
+ name="Disciplines" guid="_Z7teBNQ1EdyQ89W1tgswSQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Z7teBdQ1EdyQ89W1tgswSQ"
+ name="RoleSets" guid="_Z7teBdQ1EdyQ89W1tgswSQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Z7teBtQ1EdyQ89W1tgswSQ"
+ name="WP Types" guid="_Z7teBtQ1EdyQ89W1tgswSQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Z7teB9Q1EdyQ89W1tgswSQ"
+ name="Tools" guid="_Z7teB9Q1EdyQ89W1tgswSQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Z7teCNQ1EdyQ89W1tgswSQ"
+ name="StandardCategories" guid="_Z7teCNQ1EdyQ89W1tgswSQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Z7teCdQ1EdyQ89W1tgswSQ"
+ name="CustomCategories" guid="_Z7teCdQ1EdyQ89W1tgswSQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Z7teCtQ1EdyQ89W1tgswSQ"
+ name="Hidden" guid="_Z7teCtQ1EdyQ89W1tgswSQ">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_Z7teC9Q1EdyQ89W1tgswSQ"
+ name="Custom Categories" guid="_Z7teC9Q1EdyQ89W1tgswSQ" categorizedElements="_XMZT4NQ8EdyQ89W1tgswSQ"/>
+ </childPackages>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_XMZT4NQ8EdyQ89W1tgswSQ"
+ name="contributions_to_view_building_blocks" guid="_XMZT4NQ8EdyQ89W1tgswSQ"
+ presentationName="Contributions to View Building Blocks" categorizedElements="_c0j2QNQ8EdyQ89W1tgswSQ _-iiz0NQ8EdyQ89W1tgswSQ"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_c0j2QNQ8EdyQ89W1tgswSQ"
+ name="capability_pattern_list.assign" guid="_c0j2QNQ8EdyQ89W1tgswSQ"
+ variabilityType="contributes">
+ <methodElementProperty xmi:id="_9MtpUNQ8EdyQ89W1tgswSQ" name="CategoryElementsSortType"
+ value="Alphabetic"/>
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_h-lc4MReEdyD76CYS6Ta7A"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://_eWxZgNOEEdyqlogshP8l4g#_eWxZgdOEEdyqlogshP8l4g"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://_oZgCsNOEEdyqlogshP8l4g#_oZgCsdOEEdyqlogshP8l4g"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://_RQi0ANONEdyqlogshP8l4g#_RQi0AdONEdyqlogshP8l4g"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://_aUsVENONEdyqlogshP8l4g#_aUsVEdONEdyqlogshP8l4g"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://_h0Gs8NONEdyqlogshP8l4g#_h0Gs8dONEdyqlogshP8l4g"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://_pzQU0NONEdyqlogshP8l4g#_pzQU0dONEdyqlogshP8l4g"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://_4ouDUNOEEdyqlogshP8l4g#_4ouDUdOEEdyqlogshP8l4g"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://_RXGooNOFEdyqlogshP8l4g#_RXGoodOFEdyqlogshP8l4g"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://_KaeNsNOFEdyqlogshP8l4g#_KaeNsdOFEdyqlogshP8l4g"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://_xxcpgNOEEdyqlogshP8l4g#_xxcpgdOEEdyqlogshP8l4g"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://__ZInMNOEEdyqlogshP8l4g#__ZInMdOEEdyqlogshP8l4g"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:CapabilityPattern"
+ href="uma://_buG4sNOFEdyqlogshP8l4g#_buG4sdOFEdyqlogshP8l4g"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_-iiz0NQ8EdyQ89W1tgswSQ"
+ name="delivery_process_list" guid="_-iiz0NQ8EdyQ89W1tgswSQ" variabilityType="contributes">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCIHYsRdEdyD76CYS6Ta7A"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:DeliveryProcess" href="uma://_SuWj4NOPEdyqlogshP8l4g#_SuWj4dOPEdyqlogshP8l4g"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_Z7teDNQ1EdyQ89W1tgswSQ"
+ name="CoreContent" guid="_Z7teDNQ1EdyQ89W1tgswSQ"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_Z7teDdQ1EdyQ89W1tgswSQ"
+ name="CapabilityPatterns" guid="_Z7teDdQ1EdyQ89W1tgswSQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_a0pWkNOEEdyqlogshP8l4g"
+ name="Management" guid="_a0pWkNOEEdyqlogshP8l4g">
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessComponent" xmi:id="_eWxZgNOEEdyqlogshP8l4g"
+ href="uma://_eWxZgNOEEdyqlogshP8l4g#_eWxZgNOEEdyqlogshP8l4g"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessComponent" xmi:id="_oZgCsNOEEdyqlogshP8l4g"
+ href="uma://_oZgCsNOEEdyqlogshP8l4g#_oZgCsNOEEdyqlogshP8l4g"/>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_OKykANONEdyqlogshP8l4g"
+ name="Phase Iteration Templates" guid="_OKykANONEdyqlogshP8l4g">
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessComponent" xmi:id="_RQi0ANONEdyqlogshP8l4g"
+ href="uma://_RQi0ANONEdyqlogshP8l4g#_RQi0ANONEdyqlogshP8l4g"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessComponent" xmi:id="_aUsVENONEdyqlogshP8l4g"
+ href="uma://_aUsVENONEdyqlogshP8l4g#_aUsVENONEdyqlogshP8l4g"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessComponent" xmi:id="_h0Gs8NONEdyqlogshP8l4g"
+ href="uma://_h0Gs8NONEdyqlogshP8l4g#_h0Gs8NONEdyqlogshP8l4g"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessComponent" xmi:id="_pzQU0NONEdyqlogshP8l4g"
+ href="uma://_pzQU0NONEdyqlogshP8l4g#_pzQU0NONEdyqlogshP8l4g"/>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_b_xs8NOEEdyqlogshP8l4g"
+ name="Technical" guid="_b_xs8NOEEdyqlogshP8l4g">
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessComponent" xmi:id="_xxcpgNOEEdyqlogshP8l4g"
+ href="uma://_xxcpgNOEEdyqlogshP8l4g#_xxcpgNOEEdyqlogshP8l4g"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessComponent" xmi:id="_4ouDUNOEEdyqlogshP8l4g"
+ href="uma://_4ouDUNOEEdyqlogshP8l4g#_4ouDUNOEEdyqlogshP8l4g"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessComponent" xmi:id="__ZInMNOEEdyqlogshP8l4g"
+ href="uma://__ZInMNOEEdyqlogshP8l4g#__ZInMNOEEdyqlogshP8l4g"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessComponent" xmi:id="_KaeNsNOFEdyqlogshP8l4g"
+ href="uma://_KaeNsNOFEdyqlogshP8l4g#_KaeNsNOFEdyqlogshP8l4g"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessComponent" xmi:id="_RXGooNOFEdyqlogshP8l4g"
+ href="uma://_RXGooNOFEdyqlogshP8l4g#_RXGooNOFEdyqlogshP8l4g"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessComponent" xmi:id="_buG4sNOFEdyqlogshP8l4g"
+ href="uma://_buG4sNOFEdyqlogshP8l4g#_buG4sNOFEdyqlogshP8l4g"/>
+ </childPackages>
+ </childPackages>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_Z7teDtQ1EdyQ89W1tgswSQ"
+ name="DeliveryProcesses" guid="_Z7teDtQ1EdyQ89W1tgswSQ">
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessComponent" xmi:id="_SuWj4NOPEdyqlogshP8l4g"
+ href="uma://_SuWj4NOPEdyqlogshP8l4g#_SuWj4NOPEdyqlogshP8l4g"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_Z7teD9Q1EdyQ89W1tgswSQ"
+ name="ProcessContributions" guid="_Z7teD9Q1EdyQ89W1tgswSQ"/>
+ <bases href="uma://_iVydgENdEdy245g62lfWcA#_iVydgENdEdy245g62lfWcA"/>
+ <bases href="uma://_A118oMYaEdyXeo04os5BOw#_A118oMYaEdyXeo04os5BOw"/>
+ <bases href="uma://_14Ft0M3pEdyuBO4ZIzcyig#_14Ft0M3pEdyuBO4ZIzcyig"/>
+ <bases href="uma://_ji3-gEMXEdyP_Jn83ylwUQ#_ji3-gEMXEdyP_Jn83ylwUQ"/>
+ <bases href="uma://_CX-9AM3qEdyuBO4ZIzcyig#_CX-9AM3qEdyuBO4ZIzcyig"/>
+ <bases href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0TmecJ-VEdy3Nc4rvuj7bA"/>
+ <bases href="uma://_LdRtkM3qEdyuBO4ZIzcyig#_LdRtkM3qEdyuBO4ZIzcyig"/>
+ <bases href="uma://_OOB2AAouEdyhlpBPrduOMw#_OOB2AAouEdyhlpBPrduOMw"/>
+ <bases href="uma://_iNwFsMhNEdygFZkm1d5NtQ#_iNwFsMhNEdygFZkm1d5NtQ"/>
+ <bases href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzAJ6WEdyQN-zRFaRrCQ"/>
+ <bases href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdoL8BEdyWX5Yd-9QZ1A"/>
+ <bases href="uma://_NBRHwMh3EdygFZkm1d5NtQ#_NBRHwMh3EdygFZkm1d5NtQ"/>
+ <bases href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS10J6YEdyQN-zRFaRrCQ"/>
+ <bases href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_40sbAJ6YEdyQN-zRFaRrCQ"/>
+ <bases href="uma://_IItp4MuXEdyLOriywSJkoQ#_IItp4MuXEdyLOriywSJkoQ"/>
+ <bases href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9OMG5KEdyAHIxjZ9kpqw"/>
+ <bases href="uma://_h_9roM3PEdyKkus0T68H3Q#_h_9roM3PEdyKkus0T68H3Q"/>
+ <bases href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExQMktEdygFZkm1d5NtQ"/>
+ <bases href="uma://_GxBjAM2sEdym_ZFqrJcXUg#_GxBjAM2sEdym_ZFqrJcXUg"/>
+ <bases href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS4LPREduocbW-TPTq7A"/>
+ <bases href="uma://_XPLD8MudEdyRPtFYRAKVDg#_XPLD8MudEdyRPtFYRAKVDg"/>
+ <bases href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK0LPPEduocbW-TPTq7A"/>
+ <bases href="uma://_NjNCEMrmEdyd6uFrFHNXhA#_NjNCEMrmEdyd6uFrFHNXhA"/>
+ <bases href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKMLS9EduDY8LNbMCDBA"/>
+ <bases href="uma://_00zMMMt1EdyRPtFYRAKVDg#_00zMMMt1EdyRPtFYRAKVDg"/>
+ <bases href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rEI7-Edy7q8CKc_B8eg"/>
+ <bases href="uma://_HYAA4MriEdyd6uFrFHNXhA#_HYAA4MriEdyd6uFrFHNXhA"/>
+ <bases href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfULPaEduocbW-TPTq7A"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/publish.openup.base/.project b/praclib/temp/publish.openup.base/.project
new file mode 100644
index 0000000..d22d3d5
--- /dev/null
+++ b/praclib/temp/publish.openup.base/.project
@@ -0,0 +1,12 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<projectDescription>
+ <name>publish.openup.base</name>
+ <comment></comment>
+ <projects>
+ </projects>
+ <buildSpec>
+ </buildSpec>
+ <natures>
+ <nature>com.ibm.rmc.library.persistence.distributed.project.MethodPluginProjectNature</nature>
+ </natures>
+</projectDescription>
diff --git a/praclib/temp/publish.openup.base/customcategories/core_principles_category.xmi b/praclib/temp/publish.openup.base/customcategories/core_principles_category.xmi
new file mode 100644
index 0000000..fb00ba5
--- /dev/null
+++ b/praclib/temp/publish.openup.base/customcategories/core_principles_category.xmi
@@ -0,0 +1,58 @@
+<?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="-2Exr8xUknR1c7fbnPMMrTw"
+ name="core_principles,_HEu9QBOHEduCNqgZdt_OaA" guid="-2Exr8xUknR1c7fbnPMMrTw"
+ changeDate="2008-01-23T17:10:09.392-0800" version="1.0.0">
+ <mainDescription><p>
+ OpenUP is based on four mutually supporting core principles.
+</p>
+<h5 style="MARGIN: 12pt 0in 3pt">
+ Balance competing priorities to maximize stakeholder value
+</h5>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p>
+ Promote practices that allow project participants and stakeholders to develop a solution that maximizes stakeholder
+ benefits, and is compliant with constraints placed on the project.<br />
+ See <a class="elementLinkWithUserText"
+ href="./../../core.mgmt.common.base/guidances/concepts/core_principle_balance_793DD27.html"
+ guid="_ssG6MMvpEdqukPpotm3DYg">Balance</a> core principle for more information.
+ </p>
+</blockquote>
+<h5 style="MARGIN: 12pt 0in 3pt">
+ Collaborate to align interests and share understanding
+</h5>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p>
+ Promote practices that foster a healthy team environment, enable collaboration and develop a shared understanding
+ of the project.<br />
+ See <a class="elementLinkWithUserText"
+ href="./../../core.mgmt.common.base/guidances/concepts/core_principle_collaborate_EC5EB51F.html"
+ guid="_KkTIsMp7EdqC_NfSivunjA">Collaborate</a> core principle for more information.
+ </p>
+</blockquote>
+<h5 style="MARGIN: 12pt 0in 3pt">
+ Focus on the architecture early to minimize risks and organize development
+</h5>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p>
+ Promote practices that allow the team to focus on architecture to minimize risks and organize development.<br />
+ See <a class="elementLinkWithUserText"
+ href="./../../core.mgmt.common.base/guidances/concepts/core_principle_focus_346C6FAF.html"
+ guid="_9gocwMvoEdqukPpotm3DYg">Focus</a> core principle for more information.
+ </p>
+</blockquote>
+<h5>
+ Evolve to continuously obtain feedback and improve
+</h5>
+<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
+ <p>
+ Promote practices that allow the team to get early and continuous feedback from stakeholders, and demonstrate
+ incremental value to them.<br />
+ See <a class="elementLinkWithUserText"
+ href="./../../core.mgmt.common.base/guidances/concepts/core_principle_evolve_BFD9AEB4.html"
+ guid="_GXiogMvoEdqukPpotm3DYg">Evolve</a> core principle for more information.
+ </p>
+</blockquote></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/publish.openup.base/customcategories/discipline_list.openup.xmi b/praclib/temp/publish.openup.base/customcategories/discipline_list.openup.xmi
new file mode 100644
index 0000000..f469604
--- /dev/null
+++ b/praclib/temp/publish.openup.base/customcategories/discipline_list.openup.xmi
@@ -0,0 +1,33 @@
+<?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="-R4YxqKgYJ6BDk0wsjrMZ5Q"
+ name="discipline_list.openup,_3ZvJEMn_EdyuBO4ZIzcyig" guid="-R4YxqKgYJ6BDk0wsjrMZ5Q"
+ changeDate="2008-01-23T17:10:21.812-0500">
+ <mainDescription><p>
+ A <a class="elementLink" href="./../../core.default.uma_concepts/guidances/termdefinitions/discipline_7667F451.html"
+ guid="_yGUuidnmEdmO6L4XMImrsA">discipline</a> is a collection of <a class="elementLinkWithUserText"
+ href="./../../core.default.uma_concepts/guidances/termdefinitions/task_6C1FF051.html"
+ guid="_x459ktnmEdmO6L4XMImrsA">tasks</a> that are related to a major "area of concern" within the overall project.
+ Grouping tasks into disciplines is mainly an aid to understanding the project from a traditional waterfall perspective.
+ Although it is more common to perform tasks concurrently across several disciplines (for example, certain requirements
+ tasks are performed in close coordination with analysis and design tasks), separating these tasks into distinct
+ disciplines is simply an effective way to organize content, which makes comprehension easier.
+</p>
+<p>
+ Another reason that several tasks are all categorized by the same discipline is that they represent a part in achieving
+ a higher goal, or performing work tasks that are all related to each other. Every discipline defines standard ways of
+ doing the work it categorizes. Such standard ways are expressed by so-called <b>reference workflows</b> described with
+ <a class="elementLink" href="./../../core.default.uma_concepts/guidances/termdefinitions/capability_pattern_F5DDC5F.html"
+ guid="_2RUJACO4EdqaNq6Ptg8uyA">capability pattern</a>s, which define how the tasks categorized by the discipline work
+ together (in the most generic way). These reference workflows are often used for educating and teaching practitioners.
+</p>
+<p>
+ Like other workflows, a discipline's reference workflow is a semi-ordered sequence of activities, presented as either a
+ breakdown structure or an activity diagram performed to achieve a particular result. The "semi-ordered" nature of
+ discipline workflows emphasizes that the discipline workflows cannot present the real nuances of scheduling real work,
+ for they cannot depict the optionality of activities, or the iterative nature of real projects. Yet they still have
+ value as a way for us to understand the process, by breaking it into smaller areas of concern.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/publish.openup.base/customcategories/domain_list.openup.xmi b/praclib/temp/publish.openup.base/customcategories/domain_list.openup.xmi
new file mode 100644
index 0000000..3fd985b
--- /dev/null
+++ b/praclib/temp/publish.openup.base/customcategories/domain_list.openup.xmi
@@ -0,0 +1,14 @@
+<?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="-axI6vPcMAQ0mu7CwmZuwgg"
+ name="new_custom_category,_UTepoMoCEdyuBO4ZIzcyig" guid="-axI6vPcMAQ0mu7CwmZuwgg"
+ changeDate="2008-01-24T16:14:46.298-0800" version="7.2.0">
+ <mainDescription>This page allows you to navigate the published configuration from the perspective of <a class="elementLinkWithUserText"
+href="./../../core.default.uma_concepts/guidances/termdefinitions/work_product_826E4C22.html"
+guid="_H4JXwB_SEdq6CKKKq4D7YA">work products</a>, organized by <a class="elementLinkWithUserText"
+href="./../../core.default.uma_concepts/guidances/termdefinitions/domain_D8238B93.html"
+guid="_yHEVYdnmEdmO6L4XMImrsA">domains</a>. You can see the work products that have been included, and visit each work
+product page to see its definition and relationships to other elements.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/publish.openup.base/customcategories/getting_started.xmi b/praclib/temp/publish.openup.base/customcategories/getting_started.xmi
new file mode 100644
index 0000000..50b36a0
--- /dev/null
+++ b/praclib/temp/publish.openup.base/customcategories/getting_started.xmi
@@ -0,0 +1,10 @@
+<?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="-BZL7M9SUWacUmnxTIShrmA"
+ name="new_custom_category,_CjSiUMn-EdyuBO4ZIzcyig" guid="-BZL7M9SUWacUmnxTIShrmA"
+ changeDate="2008-01-23T13:57:38.500-0800" version="7.2.0">
+ <keyConsiderations>OpenUP is a process for small, co-located teams. It can be used as-is but, if your team has significantly different
+characteristics, the process should be modified or extended to address those needs.</keyConsiderations>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/publish.openup.base/customcategories/introduction_to_openup.xmi b/praclib/temp/publish.openup.base/customcategories/introduction_to_openup.xmi
new file mode 100644
index 0000000..934554d
--- /dev/null
+++ b/praclib/temp/publish.openup.base/customcategories/introduction_to_openup.xmi
@@ -0,0 +1,191 @@
+<?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="-ri4DnKtNEQ38B72_KOz06w"
+ name="new_custom_category,_BTJ_YMXwEduywMSzPTUUwA" guid="-ri4DnKtNEQ38B72_KOz06w"
+ changeDate="2008-02-05T18:25:23.296-0500" version="1.0.0">
+ <mainDescription><table width="589" align="center" border="0">
+ <tbody>
+ <tr>
+ <td width="96">
+ <div align="center">
+ <a href="./../../publish.openup/customcategories/getting_started_5684BDA6.html"
+ guid="_CjSiUMn-EdyuBO4ZIzcyig"><img height="48" alt="" src="./resources/GetStarted_48.gif" width="48"
+ usemap="#map" border="0" /></a>
+ </div>
+ </td>
+ <td width="95">
+ <div align="center">
+ <a href="./../../publish.openup/customcategories/core_principles_category_B7B55076.html"
+ guid="_qktUMMn7EdyuBO4ZIzcyig"><img height="48" alt="" src="./resources/CorePrinciples_48.gif"
+ width="48" usemap="#map2" border="0" /></a>
+ </div>
+ </td>
+ <td width="88">
+ <div align="center">
+ <a href="./../../publish.openup/customcategories/role_list.openup_4D587163.html"
+ guid="_Mp2wYMoDEdyuBO4ZIzcyig"><img height="48" alt="" src="./resources/Roles_48.gif" width="48"
+ usemap="#map3" border="0" /></a>
+ </div>
+ </td>
+ <td width="98">
+ <div align="center">
+ <a href="./../../publish.openup/customcategories/domain_list.openup_310E794E.html"
+ guid="_UTepoMoCEdyuBO4ZIzcyig"><img height="48" alt="" src="./resources/WorkProducts_48.gif" width="48"
+ usemap="#map4" border="0" /></a>
+ </div>
+ </td>
+ <td width="88">
+ <div align="center">
+ <a href="./../../publish.openup/customcategories/discipline_list.openup_2BD4D306.html"
+ guid="_3ZvJEMn_EdyuBO4ZIzcyig"><img height="48" alt="" src="./resources/Disciplines_48.gif" width="48"
+ usemap="#map5" border="0" /></a>
+ </div>
+ </td>
+ <td width="98">
+ <div align="center">
+ <a href="./../../process.openup.base/deliveryprocesses/openup_lifecycle_EE511F3A.html"
+ guid="_SuWj4dOPEdyqlogshP8l4g"><img height="48" alt="" src="./resources/LifeCycle_48.gif" width="48"
+ usemap="#map6" border="0" /></a>
+ </div>
+ </td>
+ </tr>
+ <tr valign="top" align="middle">
+ <td width="96">
+ <div align="center">
+ <a class="elementLink" href="./../../publish.openup/customcategories/getting_started_5684BDA6.html"
+ guid="_CjSiUMn-EdyuBO4ZIzcyig">Getting Started</a>
+ </div>
+ </td>
+ <td width="95">
+ <div align="center">
+ <a class="elementLink"
+ href="./../../publish.openup/customcategories/core_principles_category_B7B55076.html"
+ guid="_qktUMMn7EdyuBO4ZIzcyig">Core Principles</a>
+ </div>
+ </td>
+ <td width="88">
+ <div align="center">
+ <a class="elementLinkWithUserText"
+ href="./../../publish.openup/customcategories/role_list.openup_4D587163.html"
+ guid="_Mp2wYMoDEdyuBO4ZIzcyig">Roles</a>
+ </div>
+ </td>
+ <td width="98">
+ <div align="center">
+ <a class="elementLinkWithUserText"
+ href="./../../publish.openup/customcategories/domain_list.openup_310E794E.html"
+ guid="_UTepoMoCEdyuBO4ZIzcyig">Work Products</a>
+ </div>
+ </td>
+ <td width="88">
+ <div align="center">
+ <a class="elementLinkWithUserText"
+ href="./../../publish.openup/customcategories/discipline_list.openup_2BD4D306.html"
+ guid="_3ZvJEMn_EdyuBO4ZIzcyig">Disciplines</a>
+ </div>
+ </td>
+ <td width="98">
+ <div align="center">
+ <a class="elementLinkWithUserText"
+ href="./../../process.openup.base/deliveryprocesses/openup_lifecycle_EE511F3A.html"
+ guid="_SuWj4dOPEdyqlogshP8l4g">Lifecycle</a>
+ </div>
+ </td>
+ </tr>
+ </tbody>
+</table>
+<h3>
+ What is OpenUP?
+</h3>
+<p>
+ OpenUP is a lean Unified Process that applies iterative and incremental approaches within a structured lifecycle.
+ OpenUP embraces a pragmatic, agile philosophy that focuses on the collaborative nature of software development. It is a
+ tools-agnostic, low-ceremony process that can be extended to address a broad variety of project types.
+</p>
+<p>
+ <img height="546" alt="OpenUP layers: micro-increments, iteration lifecycle and project lifecycle"
+ src="./resources/three_layers.jpg" width="700" usemap="#map" border="0" tag="OpenUP" layers:="" iteration=""
+ lifecycle="" and="" project="" /> <map id="Map" name="Map">
+ <area shape="rect" alt="Iteration Lifecycle" coords="11,170,100,219"
+ href="./../../practice.mgmt.iterative_dev.base/guidances/concepts/iteration_lifecycle_B16552E2.html"
+ guid="_DI_tICNaEdyCq8v2ZO4QcA" />
+ <area shape="rect" alt="Project Lifecycle" coords="11,383,100,435"
+ href="./../../practice.mgmt.risk_value_lifecycle.base/guidances/concepts/project_lifecycle_203F87.html"
+ guid="_nSfVwCNYEdyCq8v2ZO4QcA" />
+ <area shape="rect" alt="Work Item" coords="110,55,188,104"
+ href="./../../practice.mgmt.iterative_dev.base/workproducts/work_items_list_39D03CC8.html"
+ guid="_rGNWsCbSEdqh1LYUOGRh2A" />
+ <area shape="rect" alt="Iteration Plan" coords="117,208,179,302"
+ href="./../../practice.mgmt.iterative_dev.base/workproducts/iteration_plan_B46FED39.html"
+ guid="_0aQBEslgEdmt3adZL5Dmdw" />
+ <area shape="rect" alt="Project Plan" coords="118,421,176,514"
+ href="./../../practice.mgmt.two_level_project_planning.base/workproducts/project_plan_1CDBB7E4.html"
+ guid="_0a6vcMlgEdmt3adZL5Dmdw" />
+ <area shape="poly" alt="Increment"
+ coords="332,96,332,97,332,98,332,99,332,100,332,101,333,102,333,103,333,104,333,105,333,106,334,107,334,107,334,108,334,109,335,110,335,111,335,112,336,113,336,114,336,115,337,116,337,117,338,118,338,118,339,119,339,120,340,121,340,122,341,123,342,123,342,124,343,125,343,126,344,126,345,127,346,128,346,129,347,129,348,130,348,131,349,131,350,132,351,132,352,133,352,134,353,134,354,135,355,135,356,136,357,136,358,137,358,137,359,137,360,138,361,138,362,138,363,139,364,139,365,139,366,140,367,140,368,140,369,140,370,141,371,141,372,141,373,141,374,141,375,141,376,141,377,141,378,141,379,141,380,141,381,141,382,141,383,141,384,141,385,141,386,141,387,140,388,140,389,140,389,140,390,139,391,139,392,139,393,138,394,138,395,138,396,137,397,137,398,137,399,136,400,136,400,135,401,135,402,134,403,134,404,133,405,132,405,132,406,131,407,131,408,130,408,129,409,129,410,128,411,127,411,126,412,126,413,125,413,124,414,123,414,123,415,122,416,121,416,120,417,119,417,118,418,118,418,117,418,116,419,115,419,114,420,113,420,112,420,111,421,110,421,109,421,108,422,107,422,107,422,106,422,105,422,104,423,103,423,102,423,101,423,100,423,99,423,98,423,97,423,96,423,95,423,94,423,93,423,92,423,91,423,90,423,89,422,88,422,87,422,86,422,85,422,84,421,83,421,82,421,81,420,80,420,79,420,78,419,77,419,76,418,76,418,75,418,74,417,73,417,72,416,71,416,70,415,70,414,69,414,68,413,67,413,66,412,66,411,65,411,64,410,64,409,63,408,62,408,62,407,61,406,60,405,60,405,59,404,58,403,58,402,57,401,57,400,56,400,56,399,55,398,55,397,54,396,54,395,54,394,53,393,53,392,53,391,52,390,52,389,52,389,52,388,51,387,51,386,51,385,51,384,51,383,50,382,50,381,50,380,50,379,50,378,50,377,50,376,50,375,50,374,50,373,50,372,51,371,51,370,51,369,51,368,51,367,52,366,52,365,52,364,52,363,53,362,53,361,53,360,54,359,54,358,54,358,55,357,55,356,56,355,56,354,57,353,57,352,58,352,58,351,59,350,60,349,60,348,61,348,62,347,62,346,63,346,64,345,64,344,65,343,66,343,66,342,67,342,68,341,69,340,70,340,70,339,71,339,72,338,73,338,74,337,75,337,76,336,76,336,77,336,78,335,79,335,80,335,81,334,82,334,83,334,84,334,85,333,86,333,87,333,88,333,89,333,90,332,91,332,92,332,93,332,94,332,95"
+ href="./../../practice.mgmt.iterative_dev.base/guidances/concepts/micro_increments_C8773066.html"
+ guid="_S80VwCNbEdyCq8v2ZO4QcA" />
+ <area shape="poly" alt="Iteration"
+ coords="346,250,346,252,346,253,346,254,346,255,346,257,346,258,346,259,347,260,347,261,347,263,347,264,347,265,348,266,348,267,348,269,349,270,349,271,349,272,350,273,350,274,351,275,351,277,352,278,352,279,353,280,353,281,354,282,354,283,355,284,355,285,356,286,357,287,357,288,358,289,359,290,359,291,360,292,361,293,362,294,363,295,363,296,364,297,365,298,366,299,367,300,368,300,368,301,369,302,370,303,371,304,372,304,373,305,374,306,375,307,376,307,377,308,378,309,379,309,380,310,381,310,382,311,384,311,385,312,386,313,387,313,388,314,389,314,390,314,391,315,393,315,394,316,395,316,396,316,397,317,398,317,400,317,401,317,402,318,403,318,404,318,406,318,407,318,408,318,409,319,410,319,412,319,413,319,414,319,415,319,417,319,418,319,419,319,420,318,421,318,423,318,424,318,425,318,426,318,427,317,429,317,430,317,431,317,432,316,433,316,434,316,436,315,437,315,438,314,439,314,440,314,441,313,442,313,444,312,445,311,446,311,447,310,448,310,449,309,450,309,451,308,452,307,453,307,454,306,455,305,456,304,457,304,458,303,459,302,460,301,461,300,461,300,462,299,463,298,464,297,465,296,466,295,466,294,467,293,468,292,469,291,469,290,470,289,471,288,471,287,472,286,473,285,473,284,474,283,475,282,475,281,476,280,476,279,477,278,477,277,478,275,478,274,478,273,479,272,479,271,480,270,480,269,480,267,480,266,481,265,481,264,481,263,481,261,482,260,482,259,482,258,482,257,482,255,482,254,482,253,482,252,482,250,482,249,482,248,482,247,482,246,482,244,482,243,482,242,482,241,481,240,481,238,481,237,481,236,480,235,480,234,480,232,480,231,479,230,479,229,478,228,478,227,478,225,477,224,477,223,476,222,476,221,475,220,475,219,474,218,473,217,473,216,472,215,471,214,471,213,470,212,469,211,469,210,468,209,467,208,466,207,466,206,465,205,464,204,463,203,462,202,461,201,461,200,460,200,459,199,458,198,457,197,456,197,455,196,454,195,453,194,452,194,451,193,450,192,449,192,448,191,447,191,446,190,445,189,444,189,442,188,441,188,440,187,439,187,438,186,437,186,436,186,434,185,433,185,432,185,431,184,430,184,429,184,427,183,426,183,425,183,424,183,423,183,421,183,420,182,419,182,418,182,417,182,415,182,414,182,413,182,412,182,410,182,409,182,408,182,407,183,406,183,404,183,403,183,402,183,401,183,400,184,398,184,397,184,396,185,395,185,394,185,393,186,391,186,390,186,389,187,388,187,387,188,386,188,385,189,384,189,382,190,381,191,380,191,379,192,378,192,377,193,376,194,375,194,374,195,373,196,372,197,371,197,370,198,369,199,368,200,368,200,367,201,366,202,365,203,364,204,363,205,363,206,362,207,361,208,360,209,359,210,359,211,358,212,357,213,357,214,356,215,355,216,355,217,354,218,354,219,353,220,353,221,352,222,352,223,351,224,351,225,350,227,350,228,349,229,349,230,349,231,348,232,348,234,348,235,347,236,347,237,347,238,347,240,347,241,346,242,346,243,346,244,346,246,346,247,346,248,346,249"
+ href="./../../core.mgmt.common.base/guidances/concepts/iteration_C20B1904.html" guid="_lam4ADkBEduxovfWMDsntw" />
+ <area shape="rect" alt="Build" coords="581,228,656,330"
+ href="./../../practice.tech.continuous_integration.base/workproducts/build_95D7D8FD.html"
+ guid="_0YuXEMlgEdmt3adZL5Dmdw" />
+ <area shape="rect" alt="Inception Phase" coords="249,387,304,404"
+ href="./../../practice.mgmt.risk_value_lifecycle.base/guidances/concepts/inception_phase_C4456871.html"
+ guid="_0hmKgBOMEduCNqgZdt_OaA" />
+ <area shape="rect" alt="Elaboration Phase" coords="305,386,399,404"
+ href="./../../practice.mgmt.risk_value_lifecycle.base/guidances/concepts/elaboration_phase_BE880435.html"
+ guid="_2plxwBOMEduCNqgZdt_OaA" />
+ <area shape="rect" alt="Construction Phase" coords="400,387,543,404"
+ href="./../../practice.mgmt.risk_value_lifecycle.base/guidances/concepts/construction_phase_873B6559.html"
+ guid="_48EKsBOMEduCNqgZdt_OaA" />
+ <area shape="rect" alt="Transition Phase" coords="545,387,598,404"
+ href="./../../practice.mgmt.risk_value_lifecycle.base/guidances/concepts/transition_phase_DD5986E5.html"
+ guid="__ca5UBOMEduCNqgZdt_OaA" />
+ <area shape="rect" alt="Risk" coords="306,457,344,485"
+ href="./../../core.mgmt.common.base/guidances/concepts/risk_AF5840DA.html" guid="_0bsLgMlgEdmt3adZL5Dmdw" />
+ <area shape="rect" alt="Value" coords="452,427,498,452"
+ href="./../../core.mgmt.common.base/guidances/concepts/core_principle_balance_793DD27.html"
+ guid="_ssG6MMvpEdqukPpotm3DYg" />
+ <area shape="rect" coords="11,11,177,35"
+ href="./../../practice.mgmt.iterative_dev.base/guidances/concepts/micro_increments_C8773066.html"
+ guid="_S80VwCNbEdyCq8v2ZO4QcA" />
+ </map>
+</p>
+<p>
+ <em>OpenUP layers: micro-increments, iteration lifecycle and project lifecycle</em>
+</p>
+<p>
+ Personal effort on an OpenUP project is organized in <strong>micro-increments</strong>. These represent short units of
+ work that produce a steady, measurable pace of project progress (typically measured in hours or a few days). The
+ process applies intensive collaboration as the system is incrementally developed by a committed, self-organized team.
+ These micro-increments provide an extremely short feedback loop that drives adaptive decisions within each iteration.
+</p>
+<p>
+ OpenUP divides the project into iterations: planned, time-boxed intervals typically measured in weeks. Iterations focus
+ the team on delivering incremental value to stakeholders in a predictable manner. The iteration plan defines what
+ should be delivered within the iteration, and the result is a demo-able or shippable build. OpenUP teams self-organize
+ around how to accomplish iteration objectives and commit to delivering the results. They do that by defining and
+ "pulling" fine-grained tasks from a work items list. OpenUP applies an <strong>iteration lifecycle</strong> that
+ structures how micro-increments are applied to deliver stable, cohesive builds of the system that incrementally
+ progresses towards the iteration objectives.
+</p>
+<p>
+ OpenUP structures the <strong>project lifecycle</strong> into four phases: Inception, Elaboration, Construction, and
+ Transition. The project lifecycle provides stakeholders and team members with visibility and decision points throughout
+ the project. This enables effective oversight, and allows you to make "go or no-go" decisions at appropriate times. A
+ project plan defines the lifecycle, and the end result is a released application.
+</p></mainDescription>
+ <keyConsiderations><p>
+ Use OpenUP as-is when you have a small, co-located team.
+</p>
+<p>
+ Modify OpenUP for small teams with different circumstances (for instance, a novel project or geographically distributed
+ team members). See <a class="elementLink"
+ href="./../../publish.openup/guidances/supportingmaterials/resources_for_modifying_methods_7663A1A6.html"
+ guid="_omneEMX4EduywMSzPTUUwA">Resources for Modifying Methods</a> for more information on how to customize OpenUP.
+</p></keyConsiderations>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/publish.openup.base/customcategories/resources/CorePrinciples_48.gif b/praclib/temp/publish.openup.base/customcategories/resources/CorePrinciples_48.gif
new file mode 100644
index 0000000..da5215c
--- /dev/null
+++ b/praclib/temp/publish.openup.base/customcategories/resources/CorePrinciples_48.gif
Binary files differ
diff --git a/praclib/temp/publish.openup.base/customcategories/resources/Disciplines_48.gif b/praclib/temp/publish.openup.base/customcategories/resources/Disciplines_48.gif
new file mode 100644
index 0000000..36f36b4
--- /dev/null
+++ b/praclib/temp/publish.openup.base/customcategories/resources/Disciplines_48.gif
Binary files differ
diff --git a/praclib/temp/publish.openup.base/customcategories/resources/GetStarted_48.gif b/praclib/temp/publish.openup.base/customcategories/resources/GetStarted_48.gif
new file mode 100644
index 0000000..5839c94
--- /dev/null
+++ b/praclib/temp/publish.openup.base/customcategories/resources/GetStarted_48.gif
Binary files differ
diff --git a/praclib/temp/publish.openup.base/customcategories/resources/LifeCycle_48.gif b/praclib/temp/publish.openup.base/customcategories/resources/LifeCycle_48.gif
new file mode 100644
index 0000000..f7f4665
--- /dev/null
+++ b/praclib/temp/publish.openup.base/customcategories/resources/LifeCycle_48.gif
Binary files differ
diff --git a/praclib/temp/publish.openup.base/customcategories/resources/OpenUp1_350.jpg b/praclib/temp/publish.openup.base/customcategories/resources/OpenUp1_350.jpg
new file mode 100644
index 0000000..0bb0b38
--- /dev/null
+++ b/praclib/temp/publish.openup.base/customcategories/resources/OpenUp1_350.jpg
Binary files differ
diff --git a/praclib/temp/publish.openup.base/customcategories/resources/Roles_48.gif b/praclib/temp/publish.openup.base/customcategories/resources/Roles_48.gif
new file mode 100644
index 0000000..3fb662d
--- /dev/null
+++ b/praclib/temp/publish.openup.base/customcategories/resources/Roles_48.gif
Binary files differ
diff --git a/praclib/temp/publish.openup.base/customcategories/resources/WorkProducts_48.gif b/praclib/temp/publish.openup.base/customcategories/resources/WorkProducts_48.gif
new file mode 100644
index 0000000..9554964
--- /dev/null
+++ b/praclib/temp/publish.openup.base/customcategories/resources/WorkProducts_48.gif
Binary files differ
diff --git a/praclib/temp/publish.openup.base/customcategories/resources/about.gif b/praclib/temp/publish.openup.base/customcategories/resources/about.gif
new file mode 100644
index 0000000..1316610
--- /dev/null
+++ b/praclib/temp/publish.openup.base/customcategories/resources/about.gif
Binary files differ
diff --git a/praclib/temp/publish.openup.base/customcategories/resources/back_to_top.gif b/praclib/temp/publish.openup.base/customcategories/resources/back_to_top.gif
new file mode 100644
index 0000000..356d954
--- /dev/null
+++ b/praclib/temp/publish.openup.base/customcategories/resources/back_to_top.gif
Binary files differ
diff --git a/praclib/temp/publish.openup.base/customcategories/resources/concept_dgm32.gif b/praclib/temp/publish.openup.base/customcategories/resources/concept_dgm32.gif
new file mode 100644
index 0000000..fa195bd
--- /dev/null
+++ b/praclib/temp/publish.openup.base/customcategories/resources/concept_dgm32.gif
Binary files differ
diff --git a/praclib/temp/publish.openup.base/customcategories/resources/concept_obj.gif b/praclib/temp/publish.openup.base/customcategories/resources/concept_obj.gif
new file mode 100644
index 0000000..03af38b
--- /dev/null
+++ b/praclib/temp/publish.openup.base/customcategories/resources/concept_obj.gif
Binary files differ
diff --git a/praclib/temp/publish.openup.base/customcategories/resources/delproc_lg_dgm32.gif b/praclib/temp/publish.openup.base/customcategories/resources/delproc_lg_dgm32.gif
new file mode 100644
index 0000000..3b9c93e
--- /dev/null
+++ b/praclib/temp/publish.openup.base/customcategories/resources/delproc_lg_dgm32.gif
Binary files differ
diff --git a/praclib/temp/publish.openup.base/customcategories/resources/delproc_obj.gif b/praclib/temp/publish.openup.base/customcategories/resources/delproc_obj.gif
new file mode 100644
index 0000000..dcc7373
--- /dev/null
+++ b/praclib/temp/publish.openup.base/customcategories/resources/delproc_obj.gif
Binary files differ
diff --git a/praclib/temp/publish.openup.base/customcategories/resources/discipline_dgm32.gif b/praclib/temp/publish.openup.base/customcategories/resources/discipline_dgm32.gif
new file mode 100644
index 0000000..5c3484d
--- /dev/null
+++ b/praclib/temp/publish.openup.base/customcategories/resources/discipline_dgm32.gif
Binary files differ
diff --git a/praclib/temp/publish.openup.base/customcategories/resources/discipline_obj.gif b/praclib/temp/publish.openup.base/customcategories/resources/discipline_obj.gif
new file mode 100644
index 0000000..51d0e44
--- /dev/null
+++ b/praclib/temp/publish.openup.base/customcategories/resources/discipline_obj.gif
Binary files differ
diff --git a/praclib/temp/publish.openup.base/customcategories/resources/icon_introL.gif b/praclib/temp/publish.openup.base/customcategories/resources/icon_introL.gif
new file mode 100644
index 0000000..1826cbd
--- /dev/null
+++ b/praclib/temp/publish.openup.base/customcategories/resources/icon_introL.gif
Binary files differ
diff --git a/praclib/temp/publish.openup.base/customcategories/resources/lib_16.gif b/praclib/temp/publish.openup.base/customcategories/resources/lib_16.gif
new file mode 100644
index 0000000..00a311e
--- /dev/null
+++ b/praclib/temp/publish.openup.base/customcategories/resources/lib_16.gif
Binary files differ
diff --git a/praclib/temp/publish.openup.base/customcategories/resources/lib_32.gif b/praclib/temp/publish.openup.base/customcategories/resources/lib_32.gif
new file mode 100644
index 0000000..cae5c19
--- /dev/null
+++ b/praclib/temp/publish.openup.base/customcategories/resources/lib_32.gif
Binary files differ
diff --git a/praclib/temp/publish.openup.base/customcategories/resources/mic.gif b/praclib/temp/publish.openup.base/customcategories/resources/mic.gif
new file mode 100644
index 0000000..0b316db
--- /dev/null
+++ b/praclib/temp/publish.openup.base/customcategories/resources/mic.gif
Binary files differ
diff --git a/praclib/temp/publish.openup.base/customcategories/resources/micL.gif b/praclib/temp/publish.openup.base/customcategories/resources/micL.gif
new file mode 100644
index 0000000..1826cbd
--- /dev/null
+++ b/praclib/temp/publish.openup.base/customcategories/resources/micL.gif
Binary files differ
diff --git a/praclib/temp/publish.openup.base/customcategories/resources/pract_dgm32.gif b/praclib/temp/publish.openup.base/customcategories/resources/pract_dgm32.gif
new file mode 100644
index 0000000..f597332
--- /dev/null
+++ b/praclib/temp/publish.openup.base/customcategories/resources/pract_dgm32.gif
Binary files differ
diff --git a/praclib/temp/publish.openup.base/customcategories/resources/pract_obj.gif b/praclib/temp/publish.openup.base/customcategories/resources/pract_obj.gif
new file mode 100644
index 0000000..fe8075a
--- /dev/null
+++ b/praclib/temp/publish.openup.base/customcategories/resources/pract_obj.gif
Binary files differ
diff --git a/praclib/temp/publish.openup.base/customcategories/resources/roles_dgm32.gif b/praclib/temp/publish.openup.base/customcategories/resources/roles_dgm32.gif
new file mode 100644
index 0000000..baa3d33
--- /dev/null
+++ b/praclib/temp/publish.openup.base/customcategories/resources/roles_dgm32.gif
Binary files differ
diff --git a/praclib/temp/publish.openup.base/customcategories/resources/roles_obj.gif b/praclib/temp/publish.openup.base/customcategories/resources/roles_obj.gif
new file mode 100644
index 0000000..90b1aae
--- /dev/null
+++ b/praclib/temp/publish.openup.base/customcategories/resources/roles_obj.gif
Binary files differ
diff --git a/praclib/temp/publish.openup.base/customcategories/resources/three_layers.jpg b/praclib/temp/publish.openup.base/customcategories/resources/three_layers.jpg
new file mode 100644
index 0000000..402e55d
--- /dev/null
+++ b/praclib/temp/publish.openup.base/customcategories/resources/three_layers.jpg
Binary files differ
diff --git a/praclib/temp/publish.openup.base/customcategories/resources/workproducts_lg_obj.gif b/praclib/temp/publish.openup.base/customcategories/resources/workproducts_lg_obj.gif
new file mode 100644
index 0000000..deca591
--- /dev/null
+++ b/praclib/temp/publish.openup.base/customcategories/resources/workproducts_lg_obj.gif
Binary files differ
diff --git a/praclib/temp/publish.openup.base/customcategories/resources/workproducts_obj.gif b/praclib/temp/publish.openup.base/customcategories/resources/workproducts_obj.gif
new file mode 100644
index 0000000..2e097ce
--- /dev/null
+++ b/praclib/temp/publish.openup.base/customcategories/resources/workproducts_obj.gif
Binary files differ
diff --git a/praclib/temp/publish.openup.base/customcategories/role_list.openup.xmi b/praclib/temp/publish.openup.base/customcategories/role_list.openup.xmi
new file mode 100644
index 0000000..5ad538c
--- /dev/null
+++ b/praclib/temp/publish.openup.base/customcategories/role_list.openup.xmi
@@ -0,0 +1,60 @@
+<?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="-ycCaKmcEl9VQJtZYXMdW-w"
+ name="new_custom_category,_Mp2wYMoDEdyuBO4ZIzcyig" guid="-ycCaKmcEl9VQJtZYXMdW-w"
+ version="7.2.0">
+ <mainDescription><p>
+ Software is created by people with different interests and skills. A healthy team environment enables effective
+ collaboration and requires a culture engaged in creativity and positive change. Roles are the human face of the
+ software development process but traditional descriptions can be constraining. New points of view on traditional
+ software project roles are needed to leverage collaboration instead of increasing communication channels.
+</p>
+<p>
+ Roles do not represent individual responsibilities over tasks or deliverables but are instead “hats” that people can
+ put on when working together. Each role is not limited to describing the primary performer of some task, instead the
+ roles include a perspective on collaboration by providing additional performers for each task. Playing one or more of
+ these roles can help teams express different points of view when creating a solution. This perspective on roles
+ empowers a new generation of software development processes, more focused on people interaction. Nobody does great
+ software alone but a team working together can do extraordinary things.
+</p>
+<p>
+ This page allows you to navigate the published configuration from the perspective of <a class="elementLinkWithUserText"
+ href="./../../core.default.uma_concepts/guidances/termdefinitions/role_37A0C602.html"
+ guid="_yUefQNnmEdmO6L4XMImrsA">roles</a>. You can see the roles that have been included, and visit each role page to
+ see its definition and relationships to other elements.&nbsp;&nbsp;
+</p>
+<p align="center">
+ <strong>Main roles in OpenUP and their interaction</strong>
+</p>
+<p align="center">
+ <img height="350" alt="Main roles in OpenUP and their interaction" src="./resources/OpenUp1_350.jpg" width="350"
+ usemap="#map7" border="0" /> <map id="Map7" name="Map7">
+ <area shape="rect" alt="Stakeholder" coords="144,5,207,62"
+ href="./../../core.default.role_def.base/roles/stakeholder_9FFD4106.html" guid="_dTa6gMAYEdqX-s4mWhkyqQ" />
+ <area shape="poly" alt="Tester" coords="336,242,310,287,254,256,278,209"
+ href="./../../core.default.role_def.base/roles/tester_9859B590.html" guid="_0ZM4MclgEdmt3adZL5Dmdw" />
+ <area shape="rect" alt="Developer" coords="148,282,201,347"
+ href="./../../core.default.role_def.base/roles/developer_C633AB7.html" guid="_0YDosMlgEdmt3adZL5Dmdw" />
+ <area shape="poly" alt="Architect" coords="66,199,14,232,40,283,96,249"
+ href="./../../core.default.role_def.base/roles/architect_E7A12309.html" guid="_0X9iEMlgEdmt3adZL5Dmdw" />
+ <area shape="poly" alt="Project Manager" coords="11,118,68,146,99,91,50,52"
+ href="./../../core.default.role_def.base/roles/project_manager_E657F936.html" guid="_0a0o0MlgEdmt3adZL5Dmdw" />
+ <area shape="poly" alt="Analyst" coords="258,99,312,66,338,114,284,145"
+ href="./../../core.default.role_def.base/roles/analyst_39D7C49B.html" guid="_0VxJsMlgEdmt3adZL5Dmdw" />
+ <area shape="circle" alt="Communication and Collaboration" coords="176,176,47"
+ href="./../../opn.legacy.openup_basic.KEEP/customcategories/collab_commun_subprocess_A3CDA6EF.html"
+ guid="_r8cVIEmbEdu0xduwSKie-w" />
+ <area shape="poly" alt="Management" coords="85,219,70,163,115,89,169,72,169,117,124,144,120,197"
+ href="./../../opn.legacy.openup_basic.KEEP/customcategories/management_subprocess_DF9A1A7F.html"
+ guid="_Aoz2gEmcEdu0xduwSKie-w" />
+ <area shape="poly" alt="Intent" coords="181,116,223,143,229,196,264,219,283,160,245,94,181,70"
+ href="./../../opn.legacy.openup_basic.KEEP/customcategories/intent_subprocess_33C0EF8F.html"
+ guid="_57_ZMEmbEdu0xduwSKie-w" />
+ <area shape="poly" alt="Solution" coords="129,211,176,235,221,210,257,231,214,271,133,272,94,232"
+ href="./../../opn.legacy.openup_basic.KEEP/customcategories/solution_subprocess_8AA9BF96.html"
+ guid="_HEVvgEmcEdu0xduwSKie-w" />
+ </map>
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/publish.openup.base/disciplinegroupings/openup_disciplines.xmi b/praclib/temp/publish.openup.base/disciplinegroupings/openup_disciplines.xmi
new file mode 100644
index 0000000..e38e086
--- /dev/null
+++ b/praclib/temp/publish.openup.base/disciplinegroupings/openup_disciplines.xmi
@@ -0,0 +1,32 @@
+<?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="-cGfGHqSFsvSqPwBKeoShxA"
+ name="new_discipline_grouping,_UBqBMMn_EdyuBO4ZIzcyig" guid="-cGfGHqSFsvSqPwBKeoShxA">
+ <mainDescription><p>
+ A <a class="elementLink" href="./../../core.default.uma_concepts/guidances/termdefinitions/discipline_7667F451.html"
+ guid="_yGUuidnmEdmO6L4XMImrsA">discipline</a> is a collection of <a class="elementLinkWithUserText"
+ href="./../../core.default.uma_concepts/guidances/termdefinitions/task_6C1FF051.html"
+ guid="_x459ktnmEdmO6L4XMImrsA">tasks</a> that are related to a major "area of concern" within the overall project.
+ Grouping tasks into disciplines is mainly an aid to understanding the project from a traditional waterfall perspective.
+ Although it is more common to perform tasks concurrently across several disciplines (for example, certain requirements
+ tasks are performed in close coordination with analysis and design tasks), separating these tasks into distinct
+ disciplines is simply an effective way to organize content, which makes comprehension easier.
+</p>
+<p>
+ Another reason that several tasks are all categorized by the same discipline is that they represent a part in achieving
+ a higher goal, or performing work tasks that are all related to each other. Every discipline defines standard ways of
+ doing the work it categorizes. Such standard ways are expressed by so-called <b>reference workflows</b> described with
+ <a class="elementLink" href="./../../core.default.uma_concepts/guidances/termdefinitions/capability_pattern_F5DDC5F.html"
+ guid="_2RUJACO4EdqaNq6Ptg8uyA">capability pattern</a>s, which define how the tasks categorized by the discipline work
+ together (in the most generic way). These reference workflows are often used for educating and teaching practitioners.
+</p>
+<p>
+ Like other workflows, a discipline's reference workflow is a semi-ordered sequence of activities, presented as either a
+ breakdown structure or an activity diagram performed to achieve a particular result. The "semi-ordered" nature of
+ discipline workflows emphasizes that the discipline workflows cannot present the real nuances of scheduling real work,
+ for they cannot depict the optionality of activities, or the iterative nature of real projects. Yet they still have
+ value as a way for us to understand the process, by breaking it into smaller areas of concern.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/publish.openup.base/guidances/concepts/core_principle_balance.xmi b/praclib/temp/publish.openup.base/guidances/concepts/core_principle_balance.xmi
new file mode 100644
index 0000000..814efb7
--- /dev/null
+++ b/praclib/temp/publish.openup.base/guidances/concepts/core_principle_balance.xmi
@@ -0,0 +1,170 @@
+<?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="-I4IbR1GW6IFBCdq9SiMUsw"
+ name="core_principle_balance,_ssG6MMvpEdqukPpotm3DYg" guid="-I4IbR1GW6IFBCdq9SiMUsw"
+ changeDate="2008-01-23T17:11:19.330-0800" changeDescription="Removed metaphoric photo Removed open_up from page name."
+ version="0.02">
+ <mainDescription><h3>
+ Introduction
+</h3>
+<p>
+ Systems are rarely all things to all people. Often, attempts to make them so are wasteful, and result in bloated
+ systems.
+</p>
+<p>
+ To be successful, stakeholders and the project participants must converge on a clear understanding and agreement of
+ these three factors:
+</p>
+<ul>
+ <li>
+ Problem to be solved
+ </li>
+ <li>
+ Constraints placed on the development team (cost, schedule, resources, regulations, and so on)
+ </li>
+ <li>
+ Constraints placed on the solution
+ </li>
+</ul>
+<p>
+ The challenge for all project participants is creating a solution that maximizes the value delivered to the
+ stakeholders, subject to the constraints. Balance is about making the critical, cost-benefit trade-offs between desired
+ features and the subsequent design decisions that define the architecture of the system.
+</p>
+<p>
+ Discovering the balance point is challenging, elusive, and ongoing, because the balance point is dynamic. As the system
+ evolves, stakeholder needs change, new opportunities appear, risks are resolved, new risks appear, and the development
+ team discovers new realities about the system. Change happens throughout the development cycle. Stakeholders and team
+ members must be prepared to re-evaluate commitments, reset expectations, and adjust plans accordingly as the system
+ evolves.
+</p>
+<h3>
+ Practices
+</h3>
+<h4>
+ Know your audience
+</h4>
+<blockquote>
+ <p>
+ You cannot know how to make effective trade-offs if you do not know who the stakeholders are and what they really
+ want.
+ </p>
+ <p>
+ Get to know your stakeholders. Better yet, work closely with them to ensure that you know their needs. Start by
+ identifying all stakeholders, and then maintain open and frequent communication and collaboration between them and
+ the development team.
+ </p>
+</blockquote>
+<h4>
+ Separate the problem from the solution
+</h4>
+<blockquote>
+ <p>
+ Too often, we run headlong into a solution without understanding the problem. After all, we are taught how to solve
+ problems, not how to define problems, so that's easier. However, this limits your understanding of the problem,
+ imposes artificial constraints, and makes it difficult to balance trade-offs, or to even know what the trade-offs
+ are.
+ </p>
+ <p>
+ Make sure that you understand the problem before you define the solution. By clearly separating the problem (what
+ the customer needs) from the solution (what the system must do), it is easier to maintain the proper focus, and
+ easier to accommodate alternate ways of solving the problem.
+ </p>
+</blockquote>
+<h4>
+ Create a shared understanding of the domain
+</h4>
+<blockquote>
+ <p>
+ Domain experts often have limited technical expertise; developers, architects, and testers often have limited
+ domain expertise; and reviewers and other stakeholders often have limited time to commit to the project and learn
+ the problem domain. As a result, people often have an inconsistent or poor understanding of the problem domain,
+ which causes communication problems and increases the likelihood of delivering poor value to the stakeholders.
+ </p>
+ <p>
+ Enhance and share all parties’ understandings of the domain. A concise and shared understanding of the problem
+ domain enhances communication and project effectiveness. Start by defining the problem in the Vision document. As
+ your understanding increases, capture key domain concepts and terminology in the Glossary to ensure a consistent,
+ shared use of the language of the domain.
+ </p>
+</blockquote>
+<h4>
+ Use scenarios and use cases to capture requirements
+</h4>
+<blockquote>
+ <p>
+ Many companies still document requirements as a list of declarative statements, which are sometimes called the
+ ”shall statements.” These lists are often difficult for stakeholders to understand, because they require the end
+ user to read through and mentally translate the list into a visualization of how the requirements will interact
+ with the system.
+ </p>
+ <p>
+ Make use of scenarios and use cases to capture functional requirements in a form that is easy for stakeholders to
+ understand. Nonfunctional requirements, such as performance, stability, or usability requirements, are important
+ and can be documented as system-wide requirements, using traditional techniques.
+ </p>
+</blockquote>
+<h4>
+ Establish and maintain agreement on priorities
+</h4>
+<blockquote>
+ <p>
+ Making poor decisions in deciding what to develop next can result in wasted effort, delivering capabilities that
+ are never used, or identifying problems late in the project (resulting in delays and even project failure).
+ </p>
+ <p>
+ Prioritize requirements for implementation by regularly working with the stakeholders during product evolution.
+ Make choices that deliver value and reduce risks, while building a system that can evolve.
+ </p>
+</blockquote>
+<h4>
+ Make trade-offs to maximize value
+</h4>
+<blockquote>
+ <p>
+ Cost-benefit trade-offs cannot be made independent of the architecture. Requirements establish the benefits of the
+ system to the stakeholder, while architecture establishes the cost. The cost of a benefit may influence the
+ stakeholder's perceived value of the benefit.
+ </p>
+ <p>
+ Work with the stakeholders and team members to prioritize requirements and develop candidate architectures to
+ implement those solutions. Use the candidate architectures to evaluate the cost of the benefits. Candidate
+ solutions are considered at a high level when determining architectural feasibility. Different architectural
+ perspectives can result in different assessments of cost versus benefit. The candidate architecture that provides
+ the most coverage at the lowest cost is selected for further development.
+ </p>
+</blockquote>
+<h4>
+ Manage scope
+</h4>
+<blockquote>
+ <p>
+ Change is inevitable. Although change presents opportunities to enhance stakeholder value, unconstrained change
+ will result in a bloated, deficient system and unmet stakeholder needs.
+ </p>
+ <p>
+ Manage change while maintaining agreements with the stakeholders. Modern processes always manage change,
+ continually adapting to changes in the environment and stakeholder needs, assessing the impact of changes, making
+ trade-offs, and re-prioritizing work. Stakeholder and developer expectations must be realistic and aligned
+ throughout the development lifecycle.
+ </p>
+</blockquote>
+<h4>
+ Know when to stop
+</h4>
+<blockquote>
+ <p>
+ Over-engineering a system not only wastes resources, but also leads to an overly complex system.
+ </p>
+ <p>
+ Stop developing the system when the desired quality is achieved. Remember that “Quality is conformance to the
+ requirements” <a
+ href="./../../../core.mgmt.common.base/guidances/supportingmaterials/mgmt_references_D80619F3.html#CRO79"
+ guid="_JlTPUM6aEdyuBO4ZIzcyig">[CRO79]</a>. This is what gives a sense of closure to the practice. Separate the
+ problem from the solution, ensuring that the solution does, indeed, solve the problem. After the critical
+ requirements are implemented and validated, the system is ready for stakeholder acceptance.
+ </p>
+</blockquote></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/publish.openup.base/guidances/concepts/core_principle_collaborate.xmi b/praclib/temp/publish.openup.base/guidances/concepts/core_principle_collaborate.xmi
new file mode 100644
index 0000000..bc01173
--- /dev/null
+++ b/praclib/temp/publish.openup.base/guidances/concepts/core_principle_collaborate.xmi
@@ -0,0 +1,145 @@
+<?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="-IXfkG-XfnoEo0xgux482Kw"
+ name="core_principle_collaborate,_KkTIsMp7EdqC_NfSivunjA" guid="-IXfkG-XfnoEo0xgux482Kw"
+ authors="Steve Adolph" changeDate="2008-01-23T17:13:21.751-0800" changeDescription="Initial Version |Removed metaphoric photo. Removed "Don't go dark" collaborative practice.|Removed metaphoric photo. Removed "Don't go dark" collaborative practice. Removed open_up from page name.|Added "organize around the architecture practice""
+ version="0.03">
+ <mainDescription><h3>
+ Introduction
+</h3>
+<p>
+ Software is created by people with different interests and skills who must work together to create software
+ effectively.
+</p>
+<p>
+ Develop practices that foster a healthy team environment. A healthy team environment enables effective collaboration,
+ which aligns the interests of project participants (development team, quality assurance, product stakeholders, and
+ customers) and helps project participants develop a shared understanding of the project.
+</p>
+<h3>
+ Practices
+</h3>
+<h4>
+ Maintain a common understanding
+</h4>
+<p>
+ Project participants require a common understanding of a project to cooperate effectively. Otherwise, disorder sets in,
+ because the team members cannot align their understanding and interests, and will then work with different purposes.
+</p>
+<p>
+ Be proactive communicating and sharing information with project participants. Do not assume that everyone will just
+ find what they need to know, or that each person has the same understanding of the project as everyone else. Use work
+ products (such as the Vision, Work Items List, and Requirements) to align the understanding between the stakeholders
+ and developers. Use the architecture to focus and align the interests of the developers. At the end of each iteration,
+ get agreement on whether the iteration goals have been reached and, if not, what actions must be taken.
+</p>
+<h4>
+ Foster a high-trust environment
+</h4>
+<p>
+ People who do not feel safe will not communicate their ideas, take initiative, or admit their ignorance. In these
+ low-trust work environments, activities must be laboriously planned in detail, carefully supervised, and extensively
+ audited. A team working in a low-trust environment may not be able to keep up with rapid change.
+</p>
+<p>
+ Take actions that foster a high-trust environment:
+</p>
+<ul>
+ <li>
+ <p>
+ <b>Manage by intent.</b> Create an environment where teams manage themselves, and managers serve as mentors to
+ teams to help them complete their objectives.
+ </p>
+ </li>
+ <li>
+ <p>
+ <b>Tear down the walls.</b> Work to remove both the physical and mental barriers that inhibit development of a
+ common understanding among project participants.
+ </p>
+ </li>
+ <li>
+ <p>
+ <b>Walk a mile (or 1.6 kilometers) in someone else's shoes.</b> Respect and try to understand the perspectives
+ of others before criticizing their ideas or responding to their criticism.
+ </p>
+ </li>
+ <li>
+ <p>
+ <b>Respond to conversations with relevance.</b> People, especially technical workers, often respond with
+ argument or disagreement, which leads to rivalry and establishes a pecking order in which only a few people
+ contribute to the discussion. Develop and encourage behavior that values curiosity and relevance over argument
+ and disagreement.
+ </p>
+ </li>
+ <li>
+ <p>
+ <b>Always look to yourself first for the source of communication problems.</b> Understand that everyone has a
+ perspective that is largely invisible to the individual (although it is often obvious to everyone else).
+ Develop the habit of identifying the assumptions and prejudices within you that lead to argument or lack of
+ communication. Learn to overcome these in the moment of the conversation. This takes practice. There are times
+ when others may be intractable, but often the problem can be addressed by wrestling with your own perspective.
+ </p>
+ </li>
+ <li>
+ <p>
+ <b>Understand the constraints of the workplace culture.</b> Some organizations operate in a way that allows
+ people to admit mistakes, ask questions, and experiment. Some organizations limit these expressions, but they
+ may change, with time and effort. Some organizations have no tolerance for error, and their workers put
+ themselves in danger if they admit mistakes or experiment. Understand your environment and protect yourself
+ accordingly. Understand that low-trust organizations have more problems in achieving their goals, and provide a
+ less satisfying environment.
+ </p>
+ </li>
+</ul>
+<h4>
+ Share responsibility
+</h4>
+<p>
+ There may be disadvantages for individuals when they work alone. Communication with the team can become sporadic, and
+ then stop. People may get into trouble and not ask for help, or not realize that the team is in trouble and needs their
+ help. Their understanding of the project may become misaligned with the rest of the team. In the worse situations,
+ trust breaks down as individuals see the team working at different purposes to their interests.
+</p>
+<p>
+ While individuals have primary responsibility for their work products, responsibility for work products is shared.
+ Nothing is someone else's responsibility. This may mean either taking up slack and working with someone who is lagging
+ for some reason, or asking for help. Experienced staff should be extra-vigilant and watch over less-experienced staff,
+ encouraging them to ask for help if necessary.
+</p>
+<h4>
+ Learn continuously
+</h4>
+<p>
+ Not only is software development a fast-developing field where technical skills rapidly become obsolete, it is also an
+ empirical process, where software is developed in a manner that sometimes resembles trial and error. Furthermore,
+ software is developed by teams of people who must work together to achieve results.
+</p>
+<p>
+ Continuously develop both your technical and interpersonal skills. Learn from the examples of your colleagues. Take the
+ opportunity to be both a student of your colleagues, as well as a teacher to them. Always increase your personal
+ ability to overcome your own antagonism toward other team members.
+</p>
+<h4>
+ Organize around the architecture
+</h4>
+<p>
+ As projects grow in size, communication between team members becomes increasingly complex. While all team members
+ understand the overall system, they can focus primarily on the one or more subsystems that they are responsible for.
+ Organizing around the architecture also helps with communication by providing the team with a common vocabulary and
+ shared mental model of the system. Communication between team members becomes increasingly complex.
+</p>
+<p>
+ Organize the team around the architecture, and the vocabulary and a shared mental model of the system. However, be
+ careful that individuals and teams organized this way do not form a so-called <i>silo mentality</i>, where they focus
+ strictly on their subsystems and become ignorant of the other subsystems.
+</p>
+<p>
+ An architecture that reflects the organization’s structure is not in itself evidence that the team has successfully
+ organized around the architecture. If organizations and teams are not organized around the architecture, then the
+ architecture will naturally conform to the organization, as a result of political and cultural influences. In the end,
+ the architecture and the organization will almost always be a reflection of each other. The goal is to guide team
+ organization from the needs of the architecture as much as possible.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/publish.openup.base/guidances/concepts/core_principle_evolve.xmi b/praclib/temp/publish.openup.base/guidances/concepts/core_principle_evolve.xmi
new file mode 100644
index 0000000..c71b82e
--- /dev/null
+++ b/praclib/temp/publish.openup.base/guidances/concepts/core_principle_evolve.xmi
@@ -0,0 +1,152 @@
+<?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="-aMD1wQVJLzzlMARfHBdOBQ"
+ name="core_principle_evolve,_GXiogMvoEdqukPpotm3DYg" guid="-aMD1wQVJLzzlMARfHBdOBQ"
+ changeDate="2008-01-23T17:15:20.861-0800" changeDescription="removed OpenUP from page name."
+ version="0.02">
+ <mainDescription><h3>
+ Introduction
+</h3>
+<p>
+ It is usually not possible to know all stakeholders' needs, be aware of all project risks, comprehend all project
+ technologies, or know how to work with your colleagues. Even if it were possible to know all of these things, they are
+ likely to change over the life of the project. Promote practices that allow the team to demonstrate incremental value,
+ and to get early and continuous feedback from stakeholders.
+</p>
+<p>
+ The intention behind this principle is to continuously get feedback, and to improve both the product and the process of
+ the project team. When you provide structure and create a mindset for continuous feedback and improvement, changes are
+ accommodated more easily. In addition, feedback is captured early and often, and high-priority risks are confronted
+ early in the project. By constantly identifying and attacking risks, there is more confidence in project progress and
+ quality.
+</p>
+<p>
+ Not only does the product evolve, but the team also finds better ways to work together and get involved with
+ stakeholders. The process followed by the team can be adjusted accordingly to leverage lessons learned and adjust
+ project pace and needs.
+</p>
+<h3>
+ Practices
+</h3>
+<h4>
+ Develop your project in iterations
+</h4>
+<p>
+ Developing a system in a single, linear pass is difficult, because it makes it expensive to incorporate changes and new
+ knowledge. Worse, it can delay the discovery and mitigation of risks, because development efforts are scheduled later
+ in the lifecycle.
+</p>
+<p>
+ Divide your project into a series of time-boxed <a class="elementLinkWithUserText"
+ href="./../../../core.mgmt.common.base/guidances/concepts/iteration_C20B1904.html"
+ guid="_lam4ADkBEduxovfWMDsntw">iterations</a>, and plan your project iteratively. This iterative strategy enables you
+ to incrementally deliver capabilities (such as an executable, usable subset of implemented and tested requirements)
+ that can be assessed by stakeholders at the end of each iteration. This provides rapid and timely feedback loops, so
+ that issues can be addressed and improvements made at a lower cost. Also, this is accomplished while you still have
+ sufficient budget and time left to do so, and you have not gone so far ahead that major rework is required.
+</p>
+<p>
+ Iterative development enables teams to continuously improve software throughout the development <a
+ href="./../../../opn.legacy.openup_basic.KEEP/deliveryprocesses/openup_basic_process_2CB8A7DA.html"
+ guid="_0uyGoMlgEdmt3adZL5Dmdw">lifecycle</a>.
+</p>
+<h4>
+ Focus iterations on meeting the next management milestone
+</h4>
+<p>
+ A project can appear to make progress while risks and unresolved issues pile up. Focus on bringing closure to important
+ project issues (such as stakeholder concurrence regarding scope, and proving the proposed architecture).
+</p>
+<p>
+ Divide the project into phases (such as <a class="elementLinkWithUserText"
+ href="./../../../practice.mgmt.risk_based_milestones.base/guidances/concepts/inception_phase_C4456871.html"
+ guid="_0hmKgBOMEduCNqgZdt_OaA">Inception</a>, <a class="elementLinkWithUserText"
+ href="./../../../practice.mgmt.risk_based_milestones.base/guidances/concepts/elaboration_phase_BE880435.html"
+ guid="_2plxwBOMEduCNqgZdt_OaA">Elaboration</a>, <a class="elementLinkWithUserText"
+ href="./../../../practice.mgmt.risk_based_milestones.base/guidances/concepts/construction_phase_873B6559.html"
+ guid="_48EKsBOMEduCNqgZdt_OaA">Construction</a> and <a class="elementLinkWithUserText"
+ href="./../../../practice.mgmt.risk_based_milestones.base/guidances/concepts/transition_phase_DD5986E5.html"
+ guid="__ca5UBOMEduCNqgZdt_OaA">Transition</a>), with each phase having a clearly visible management <a
+ class="elementLinkWithUserText"
+ href="./../../../practice.mgmt.risk_based_milestones.base/guidances/concepts/phase_milestones_5678231E.html"
+ guid="_HNxbwMBJEdqSgKaj2SZBmg">milestone</a>. The focus of each iteration within a phase is on achieving that
+ milestone.
+</p>
+<h4>
+ Manage risks
+</h4>
+<p>
+ Deferring difficult and risky issues until later in a project significantly increases the risk of project failure. Such
+ procrastination may lead to investing in the wrong technologies, a bad design, or a set of requirements that may not
+ address stakeholder needs.
+</p>
+<p>
+ Attack <a href="./../../../core.mgmt.common.base/guidances/concepts/risk_AF5840DA.html"
+ guid="_0bsLgMlgEdmt3adZL5Dmdw">risks</a> early, or they will attack you. Continuously identify and prioritize risks,
+ and then devise strategies to mitigate them. Determine the focus of iterations based on risks. For example,
+ architecturally significant risks should be addressed early in the project, no later than the end of the Elaboration
+ phase, when the architecture has been proven and baselined.
+</p>
+<p>
+ Fore more information, see <a class="elementLinkWithType"
+ href="./../../../core.mgmt.common.base/guidances/guidelines/managing_risks_B1256EB4.html"
+ guid="_VNxL4ACsEdu8m4dIntu6jA">Guideline: Managing Risks</a>.
+</p>
+<h4>
+ Embrace and manage change
+</h4>
+<p>
+ Change is inevitable, and while change presents opportunities to enhance stakeholder value, unconstrained change will
+ result in a bloated, deficient system and unmet stakeholder needs. Furthermore, the later in the development cycle a
+ change is made, the more the change is likely to cost.
+</p>
+<p>
+ Embrace and manage change. Embracing change helps you to build a system that addresses stakeholder needs, and managing
+ change allows you to reduce costs and improve predictability of those changes. Changes made early in the project can
+ usually be made with limited cost. As you progress in your project, changes can become increasingly costly.
+</p>
+<p>
+ To satisfy customer needs, you typically need to introduce changes to the project, but the customer must be made aware
+ of the impact that those changes have on the project cost and schedule. Understand the impact of a change in the
+ current phase, and isolate team members from disruptive changes during the current iteration. Change requests are
+ reviewed and prioritized during the current iteration, but are not acted upon until assigned to a future iteration.
+</p>
+<p>
+ If necessary, document the changes. For informal projects, a discussion with stakeholders may be enough.
+</p>
+<h4>
+ Measure progress objectively
+</h4>
+<p>
+ If you do not objectively know how your project is progressing, you do not really know if it is failing or succeeding.
+ Uncertainty and change make a software project’s progress difficult to measure objectively, and people are prone to
+ making objective assessments from subjective information.
+</p>
+<p>
+ Get a clear picture of project status by objectively measuring progress. The best measure of progress is the delivery
+ of working software, which is something that you do by taking an evolutionary approach. You can also define a set of
+ objective <a href="./../../../core.mgmt.common.base/guidances/concepts/metrics_37698708.html"
+ guid="_0mYYkMlgEdmt3adZL5Dmdw">metrics</a> to collect during an iteration (for example, requirements that were
+ implemented and validated, number of defects issued compared with number fixed) and review them as part of the <a
+ href="./../../../practice.mgmt.iterative_dev.base/tasks/assess_results_EC34D88D.html"
+ guid="_0l53cMlgEdmt3adZL5Dmdw">iteration assessment</a>.
+</p>
+<h4>
+ Continuously re-evaluate what you do
+</h4>
+<p>
+ On a regular basis, ask questions and verify assumptions about the project. Regularly meet with the team to track
+ status and identify risks and issues. This can be done daily when the team gathers to share the status of individual
+ responsibilities and identify and address issues. At the end of iterations, <a
+ href="./../../../practice.mgmt.iterative_dev.base/tasks/assess_results_EC34D88D.html"
+ guid="_0l53cMlgEdmt3adZL5Dmdw">assess the status</a> of what has been done and look for areas of improvement that can
+ be addressed in the next iteration. Have a retrospective review at the end of the project and capture lessons learned
+ to run future projects in a more efficient way.
+</p>
+<p>
+ If we always challenge what we do and seek new, innovative ways to develop software, we improve how we work. This leads
+ to improved project results.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/publish.openup.base/guidances/concepts/core_principle_focus.xmi b/praclib/temp/publish.openup.base/guidances/concepts/core_principle_focus.xmi
new file mode 100644
index 0000000..a1b573c
--- /dev/null
+++ b/praclib/temp/publish.openup.base/guidances/concepts/core_principle_focus.xmi
@@ -0,0 +1,91 @@
+<?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="-HTMJFV29MTZkKWqnIo01Gg"
+ name="core_principle_focus,_9gocwMvoEdqukPpotm3DYg" guid="-HTMJFV29MTZkKWqnIo01Gg"
+ authors="Steve Adolph" changeDate="2008-01-23T17:14:28.752-0800" changeDescription="Added first draft of content."
+ version="0.02">
+ <mainDescription><h3>
+ Introduction
+</h3>
+<p>
+ The architecture of a software system is the organization or structure of the system's significant components
+ interacting through interfaces, with components composed of successively smaller components and interfaces.
+</p>
+<p>
+ Without an architectural foundation, a system will evolve in an inefficient and haphazard way. Such a system often
+ proves difficult to extend, reuse, or integrate without substantial rework. It is also difficult to organize the team,
+ or to communicate ideas without the <b>common technical focus</b> that the architecture provides.
+</p>
+<p>
+ Focus on the architecture early to minimize risks and organize development.
+</p>
+<h3>
+ Practices
+</h3>
+<h4>
+ Create the architecture for what you know today
+</h4>
+<p>
+ As Albert Einstein said, make everything as simple as possible, but no simpler. Software projects are
+ resource-constrained, and the desire of developers to create elegant solutions may lead to a system of greater
+ complexity than the stakeholder requires. Efforts to future-proof a system in a turbulent or uncertain environment will
+ likely lead to code bloat, which increases overall costs and complexity with few real benefits.
+</p>
+<p>
+ Create architectures that address the stakeholder’s real needs, and provide appropriate flexibility and speed for the
+ requirements as they are known today. Avoid the desire, no matter how well-intentioned, to speculate on future
+ requirements and thereby over-engineer the architecture. There is a distinction between over-architecting and building
+ an architecture that is flexible and extensible. For example, there may not be an apparent reason for creating three
+ architectural layers in a system, but it is probable that the system will grow in ways one can't predict, so we should
+ architect for that.
+</p>
+<h4>
+ Leverage the architecture as a collaborative tool
+</h4>
+<p>
+ Lack of a common understanding by developers about a system leads to indecision and contrary opinions among developers,
+ and can quickly paralyze the project. Developers may have different mental models of the system and work at cross
+ purposes to each other.
+</p>
+<p>
+ Create and evolve the system architecture with the intention of using it to align the developers' competing mental
+ models of the system. A good architecture facilitates collaboration by providing a common vocabulary for all
+ discussions regarding the system under development.
+</p>
+<h4>
+ Cope with complexity by raising the level of abstraction
+</h4>
+<p>
+ Software is complex, and people have a limited capacity for coping with complexity. As a system gets larger, it is
+ difficult for the team to develop a common understanding of the system, because it's hard to see the bigger picture.
+</p>
+<p>
+ Use models to raise the level of abstraction to focus on important high-level decisions, such as relationships and
+ patterns, rather than getting bogged down in details. Modeling raises the level of abstraction, and allows the system
+ to be more easily understood from different perspectives.
+</p>
+<h4>
+ Organize the architecture into loosely coupled, highly cohesive components
+</h4>
+<p>
+ Tight coupling between components makes a system fragile and difficult to understand. Software is expensive to create,
+ so if existing components can be reused, that may reduce effort required to create a system.
+</p>
+<p>
+ Organize the architecture of the system into components to maximize cohesion and minimize coupling. This improves
+ comprehension, and increases flexibility and opportunities for re-use.
+</p>
+<h4>
+ Reuse existing assets
+</h4>
+<p>
+ It is wasteful to build what you can simply reuse, download, or even buy.
+</p>
+<p>
+ Make every effort to reuse existing assets. Developers are often reluctant to reuse assets, because those assets do not
+ exactly meet their needs, or those assets are of poor quality. Be prepared to balance the savings you can realize using
+ an existing asset, even if the asset requires you to make some accommodation in the architecture or relax a constraint.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/publish.openup.base/guidances/concepts/project_lifecycle.additon.xmi b/praclib/temp/publish.openup.base/guidances/concepts/project_lifecycle.additon.xmi
new file mode 100644
index 0000000..7a5f89a
--- /dev/null
+++ b/praclib/temp/publish.openup.base/guidances/concepts/project_lifecycle.additon.xmi
@@ -0,0 +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.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="-zuqK2tneGKchXpqLVRtwlg"
+ name="new_concept,_j0leQOL0EdyM47cGD2jiaQ" guid="-zuqK2tneGKchXpqLVRtwlg" changeDate="2008-02-24T11:23:28.578-0500">
+ <mainDescription>See <a class="elementLink" href="./../../../publish.openup/guidances/concepts/core_principle_balance_793DD27.html"
+guid="_ssG6MMvpEdqukPpotm3DYg">Balance competing priorities to maximize stakeholder value</a>.</mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/publish.openup.base/guidances/roadmaps/openup_roadmap.xmi b/praclib/temp/publish.openup.base/guidances/roadmaps/openup_roadmap.xmi
new file mode 100644
index 0000000..d4b820f
--- /dev/null
+++ b/praclib/temp/publish.openup.base/guidances/roadmaps/openup_roadmap.xmi
@@ -0,0 +1,207 @@
+<?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="-APgHPRv2KxEoFdcbHUli5w"
+ name="new_roadmap,_Q2ErcMn-EdyuBO4ZIzcyig" guid="-APgHPRv2KxEoFdcbHUli5w" changeDate="2008-01-23T17:26:40.941-0800"
+ version="7.2.0">
+ <mainDescription><h3>
+ Overview of OpenUP
+</h3>
+<p>
+ OpenUP is for small teams who work together in the same location. The team needs to engage in plenty of daily
+ face-to-face interaction. Team members include the stakeholders, developers, architects, project manager, and testers.
+ They make their own decisions about what they need to work on, what the priorities are, and how best to address
+ stakeholder needs. The organization must support the team by allowing them these responsibilities.
+</p>
+<p>
+ Team members collaborate extensively. The presence of stakeholders as team members is critical to successfully
+ implementing OpenUP.
+</p>
+<p>
+ Team members participate in daily stand-up meetings to communicate status and issues. Problems are addressed outside of
+ the daily meetings.
+</p>
+<p>
+ OpenUP focuses on significantly&nbsp;reducing risk early in the lifecycle. This requires regular risk review meetings
+ and rigorous implementation of mitigation strategies.
+</p>
+<p>
+ All work is listed, tracked, and assigned through the Work Items List. Team members use this single repository for all
+ tasks that need to be recorded and tracked. This includes all change requests, bugs, and stakeholder requests.
+</p>
+<p>
+ Use cases are used to elicit and describe requirements; therefore, team members need to develop skills in writing good
+ use cases. Stakeholders are responsible for reviewing and certifying that the requirements are correct. Use cases are
+ developed collaboratively.
+</p>
+<p>
+ Architecturally significant requirements must be identified and stabilized in the Elaboration phase so that a robust
+ architecture can be created as the core of the system. An architecturally significant requirement change that must be
+ addressed may arise later in development, but the risk of this happening is significantly reduced in the Elaboration
+ iteration.
+</p>
+<p>
+ Testing is performed multiple times per iteration, every time the solution is incremented with the development of a
+ requirement, change, or bug fix. These tests happen after developers have developed the solution (which should have
+ been unit-tested) and integrate it into the code base. These tests help guarantee that a stable build is created and
+ always available as development progresses.
+</p>
+<p>
+ OpenUP does not include content for deployment, configuration management, or the development environment (such as
+ customizing this process or setting up development environments). OpenUP focuses on a singe team, and these areas are
+ generally addressed at an organizational or enterprise level. Look for extensions to OpenUP that address these wider
+ areas.
+</p>
+<p>
+ OpenUP is an iterative software development process that is minimal, complete, and extensible. It is governed by four
+ <a class="elementLinkWithUserText"
+ href="./../../../opn.legacy.openup_basic.KEEP/customcategories/core_principles_category_8075133D.html"
+ guid="_UCOtoMXwEduywMSzPTUUwA">core principles</a>:
+</p>
+<ul>
+ <li>
+ <a class="elementLinkWithUserText"
+ href="./../../../core.mgmt.common.base/guidances/concepts/core_principle_collaborate_EC5EB51F.html"
+ guid="_KkTIsMp7EdqC_NfSivunjA">Collaborate to align interests and share understanding</a>
+ </li>
+ <li>
+ <a class="elementLinkWithUserText"
+ href="./../../../core.mgmt.common.base/guidances/concepts/core_principle_balance_793DD27.html"
+ guid="_ssG6MMvpEdqukPpotm3DYg">Balance competing priorities to maximize stakeholder value</a>
+ </li>
+ <li>
+ <a class="elementLinkWithUserText"
+ href="./../../../core.mgmt.common.base/guidances/concepts/core_principle_focus_346C6FAF.html"
+ guid="_9gocwMvoEdqukPpotm3DYg">Focus on the architecture early to minimize risks and organize development</a>
+ </li>
+ <li>
+ <a class="elementLinkWithUserText"
+ href="./../../../core.mgmt.common.base/guidances/concepts/core_principle_evolve_BFD9AEB4.html"
+ guid="_GXiogMvoEdqukPpotm3DYg">Evolve to continuously obtain feedback and improve</a>
+ </li>
+</ul>
+<p>
+ People in <a class="elementLinkWithUserText"
+ href="./../../../core.default.uma_concepts/guidances/termdefinitions/role_37A0C602.html"
+ guid="_yUefQNnmEdmO6L4XMImrsA">Roles</a>&nbsp;perform <a class="elementLinkWithUserText"
+ href="./../../../core.default.uma_concepts/guidances/termdefinitions/task_6C1FF051.html"
+ guid="_x459ktnmEdmO6L4XMImrsA">tasks</a> that use and produce <a class="elementLinkWithUserText"
+ href="./../../../core.default.uma_concepts/guidances/termdefinitions/artifact_F635D25.html"
+ guid="_x7cUM9nmEdmO6L4XMImrsA">artifacts</a>. OpenUP describes the minimal set of&nbsp;Roles, Tasks, and
+ Artifacts&nbsp;involved in software development:
+</p>
+<ul>
+ <li>
+ <a class="elementLinkWithUserText"
+ href="./../../../opn.legacy.openup_basic.KEEP/rolesets/openup_basic_roles_5CDDEEDA.html"
+ guid="_TZIJ0O8NEdmKSqa_gSYthg">Roles</a>
+ </li>
+ <li>
+ <a class="elementLinkWithUserText"
+ href="./../../../opn.legacy.openup_basic.KEEP/disciplinegroupings/openup_basic_disciplines_AF6D7A8E.html"
+ guid="__BZycP1UEdmek8CQTQgrOQ">Tasks</a> (organized by disciplines)
+ </li>
+ <li>
+ <a class="elementLinkWithUserText"
+ href="./../../../opn.legacy.openup_basic.KEEP/domains/openup_basic_wp_E9648102.html"
+ guid="_s4Z9AMWXEdqWePvIjHInwg">Artifacts</a> (organized by domains)&nbsp;
+ </li>
+</ul>
+<h4>
+ The OpenUP software development&nbsp;lifecycle
+</h4>
+<p>
+ OpenUP is an iterative process&nbsp;distributed throughout&nbsp;four <a class="elementLinkWithUserText"
+ href="./../../../practice.mgmt.risk_based_milestones.base/guidances/concepts/phase_85B003C3.html"
+ guid="__7xOEC7aEdqHMdmRzC0-2g">phases</a>: Inception, Elaboration, Construction, and Transition. Each phase consists of
+ one or more iterations where stable, working versions of the software are developed and released, with the completion
+ of each iteration representing a minor <a class="elementLinkWithUserText"
+ href="./../../../practice.mgmt.risk_based_milestones.base/guidances/concepts/phase_milestones_5678231E.html"
+ guid="_HNxbwMBJEdqSgKaj2SZBmg">milestone</a>&nbsp;for the project and contributing to the successful achievement of the
+ phase's major milestone, where phase objectives are met.
+</p>
+<p>
+ The following diagram depicts the OpenUP <a class="elementLinkWithUserText"
+ href="./../../../opn.legacy.openup_basic.KEEP/deliveryprocesses/openup_basic_process_2CB8A7DA.html"
+ guid="_0uyGoMlgEdmt3adZL5Dmdw">lifecycle</a>.
+</p>
+<p align="center">
+ <img height="192" alt="Figure 1: Diagram of the OpenUP Lifecycle" src="./resources/openup_lifecycle.jpg" width="667"
+ usemap="#map" border="0" />
+</p><br align="center" />
+<br />
+<h4>
+ How&nbsp;to get started?
+</h4>
+<p>
+ The fourth OpenUP core principle, "Evolve to continuously obtain feedback and improve", suggests an iterative and
+ incremental approach to adopting OpenUP.
+</p>
+<ul>
+ <li>
+ Start with the core principles and understand the intentions behind OpenUP.
+ </li>
+ <li>
+ Then assess your existing process, and select one or two key areas that you would like to improve.
+ </li>
+ <li>
+ Begin using OpenUP to improve these areas first.
+ </li>
+ <li>
+ In later iterations or development cycles, make incremental improvements in other areas.
+ </li>
+ <li>
+ If you have little or no experience with unified processes or other iterative processes, use OpenUP in a small
+ pilot project, perhaps with only three to four people working for only two to three months.
+ </li>
+</ul>
+<p>
+ While OpenUP is a ready to use as-is, you may choose to extend the process or modify the work product templates to suit
+ your specific needs. For example:
+</p>
+<ul>
+ <li>
+ You may require more or less precision in your work products.
+ </li>
+ <li>
+ Your organization may have specific configuration management practices or safety protocols to include in your
+ process.
+ </li>
+ <li>
+ You may simply want to put your own corporate logo on the banner.
+ </li>
+ <li>
+ You may want to incorporate lessons learned from a retrospective review into OpenUP.
+ </li>
+</ul>
+<p>
+ Use EPF Composer to extend and tailor OpenUP. For more information about EPF composer, visit <a
+ href="http://www.eclipse.org/epf" target="_blank">www.eclipse.org/epf</a>.
+</p><map id="Map" name="Map">
+ <area shape="rect" alt="link to inception phase concept" coords="116,7,175,25"
+ href="./../../../practice.mgmt.risk_based_milestones.base/guidances/concepts/inception_phase_C4456871.html"
+ guid="_0hmKgBOMEduCNqgZdt_OaA" />
+ <area shape="rect" alt="link to elaboration phase concept" coords="255,11,327,27"
+ href="./../../../practice.mgmt.risk_based_milestones.base/guidances/concepts/elaboration_phase_BE880435.html"
+ guid="_2plxwBOMEduCNqgZdt_OaA" />
+ <area shape="rect" alt="link to construction phase concept" coords="395,11,476,27"
+ href="./../../../practice.mgmt.risk_based_milestones.base/guidances/concepts/construction_phase_873B6559.html"
+ guid="_48EKsBOMEduCNqgZdt_OaA" />
+ <area shape="rect" alt="link to transition phase concept" coords="554,10,619,27"
+ href="./../../../practice.mgmt.risk_based_milestones.base/guidances/concepts/transition_phase_DD5986E5.html"
+ guid="__ca5UBOMEduCNqgZdt_OaA" />
+ <area shape="rect" alt="link to inception phase iteration delivery process" coords="39,98,100,162"
+ href="./../../../opn.legacy.openup_basic.KEEP/capabilitypatterns/inception_phase_iteration_C2188B46.html"
+ guid="_0o3r4slgEdmt3adZL5Dmdw" />
+ <area shape="rect" alt="link to inception phase iteration delivery process" coords="188,100,250,169"
+ href="./../../../opn.legacy.openup_basic.KEEP/capabilitypatterns/elaboration_phase_iteration_97E7400D.html"
+ guid="_0sTaYMlgEdmt3adZL5Dmdw" />
+ <area shape="rect" alt="link to construction phase iteration delivery process" coords="332,100,397,165"
+ href="./../../../opn.legacy.openup_basic.KEEP/capabilitypatterns/construction_phase_iteration_FB82CA56.html"
+ guid="_y-3IrutQEdqc1LGhiSPqRg" />
+ <area shape="rect" alt="link to transition phase iteration delivery process" coords="480,98,541,167"
+ href="./../../../opn.legacy.openup_basic.KEEP/capabilitypatterns/transition_phase_iteration_87676AD2.html"
+ guid="_0rQRgMlgEdmt3adZL5Dmdw" />
+</map></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/publish.openup.base/guidances/roadmaps/resources/openup_lifecycle.jpg b/praclib/temp/publish.openup.base/guidances/roadmaps/resources/openup_lifecycle.jpg
new file mode 100644
index 0000000..4719cad
--- /dev/null
+++ b/praclib/temp/publish.openup.base/guidances/roadmaps/resources/openup_lifecycle.jpg
Binary files differ
diff --git a/praclib/temp/publish.openup.base/guidances/supportingmaterials/about_openup.xmi b/praclib/temp/publish.openup.base/guidances/supportingmaterials/about_openup.xmi
new file mode 100644
index 0000000..4bd6f6b
--- /dev/null
+++ b/praclib/temp/publish.openup.base/guidances/supportingmaterials/about_openup.xmi
@@ -0,0 +1,31 @@
+<?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="-WFD3nKccpkueaG15cHT-fA"
+ name="about_openup,_8tSNMPGYEdqiDINUyockoA" guid="-WFD3nKccpkueaG15cHT-fA" changeDate="2006-09-27T19:25:47.645-0400"
+ version="1.0.0">
+ <mainDescription><h3>
+ <a id="version" name="version">Version Information</a>
+</h3>
+<p>
+ OpenUP Plug-in Version 1.0.<br />
+ Based on: Base Concepts Plug-in Version:&nbsp;1.0.
+</p>
+<h3>
+ Legal Statement
+</h3>
+<p class="node">
+ See <a href="./resources/copyrite.htm"><u><font color="#0000ff">Intellectual Property Notices</font></u></a>.
+</p>
+<h3>
+ Browser Support
+</h3>
+<p>
+ <b>Note 1:</b>&nbsp;EPF published Web sites&nbsp;do not currently support Netscape Navigator 6.x.
+</p>
+<p>
+ <b>Note 2:</b> Some versions of Microsoft Internet Explorer 4.x and Netscape Navigator 4.x may not be able to display
+ all pages of OpenUP.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/publish.openup.base/guidances/supportingmaterials/minimal_complete_extensible.xmi b/praclib/temp/publish.openup.base/guidances/supportingmaterials/minimal_complete_extensible.xmi
new file mode 100644
index 0000000..1b79d9e
--- /dev/null
+++ b/praclib/temp/publish.openup.base/guidances/supportingmaterials/minimal_complete_extensible.xmi
@@ -0,0 +1,216 @@
+<?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="-AO488Z6M5HCAbxm1c-SjUA"
+ name="new_supporting_material,_xKvXkMn8EdyuBO4ZIzcyig" guid="-AO488Z6M5HCAbxm1c-SjUA"
+ changeDate="2008-01-23T16:48:09.562-0500">
+ <mainDescription><h3>
+ Introduction
+</h3>
+<p>
+ A good way to understand OpenUP is to think of it as targeted to teams that have the following objectives:
+</p>
+<ul>
+ <li>
+ Apply the minimally necessary process that brings value.
+ </li>
+ <li>
+ Avoid being overloaded with unproductive formal work products.
+ </li>
+ <li>
+ Use a process that can be tailored and extended for additional needs that may arise during the software development
+ lifecycle.
+ </li>
+</ul>
+<p>
+ In order to be applied to as many project environments as possible, OpenUP is a process that has the following
+ characteristics:
+</p>
+<ul>
+ <li>
+ Minimal - only fundamental content is included
+ </li>
+ <li>
+ Complete - it can be manifested as an entire process to build a system
+ </li>
+ <li>
+ Extensible - it can be used as a foundation on which process content can be added or tailored as needed
+ </li>
+</ul>
+<h4>
+ Minimal
+</h4>
+<p>
+ OpenUP is considered an agile, lightweight process that promotes software development best practices such as:
+</p>
+<ul>
+ <li>
+ iterative development
+ </li>
+ <li>
+ team collaboration
+ </li>
+ <li>
+ continuous integration and tests
+ </li>
+ <li>
+ frequent deliveries of working software
+ </li>
+ <li>
+ adaptation to changes, and so on.
+ </li>
+</ul>
+<p>
+ Other factors also count when determining the size of process material, such as the number of method elements like
+ roles, tasks, artifacts and guidance.
+</p>
+<p>
+ OpenUP provides descriptions of responsibilities, skills and competencies of the fundamental roles in a team. See the
+ list of <a class="elementLinkWithUserText"
+ href="./../../../opn.legacy.openup_basic.KEEP/rolesets/openup_basic_roles_5CDDEEDA.html"
+ guid="_TZIJ0O8NEdmKSqa_gSYthg">roles</a> for more details.
+</p>
+<p>
+ OpenUP provides the essential artifacts needed to capture and communicate decisions. Ultimately, the process is not
+ governed by artifact creation. For example, thinking about design is more important than documenting the design;
+ assessing and planning an iteration is about promoting team collaboration instead of creating plans that are written in
+ stone. In addition, for each artifact, OpenUP suggests informal representations or provides informal templates as
+ starting points for teams that do not need to create their own. The team decides what the most appropriate form to be
+ applied is. See the list of <a class="elementLinkWithUserText"
+ href="./../../../opn.legacy.openup_basic.KEEP/domains/openup_basic_wp_E9648102.html"
+ guid="_s4Z9AMWXEdqWePvIjHInwg">work products</a> organized by domains.
+</p>
+<p>
+ Tasks in OpenUP are clear and focused on results. Text is usually short and objective, describing how individuals
+ should collaborate to achieve objectives. Steps are short descriptions of what to achieve, and point to external
+ guidance on how to do it. See the list of <a class="elementLinkWithUserText"
+ href="./../../../opn.legacy.openup_basic.KEEP/disciplinegroupings/openup_basic_disciplines_AF6D7A8E.html"
+ guid="__BZycP1UEdmek8CQTQgrOQ">tasks</a> organized by disciplines.
+</p>
+<p>
+ OpenUP recommends the least amount of process guidance a team should use in order to be successful. Teams may have
+ different names or responsibilities for roles, may perform tasks in or have different representations for artifacts,
+ but they still want to follow the principles and practices described in OpenUP to increase the chances of project
+ success.
+</p>
+<h4>
+ Complete
+</h4>
+<p>
+ OpenUP is considered a complete process because it covers the essential <a class="elementLinkWithUserText"
+ href="./../../../opn.legacy.openup_basic.KEEP/disciplinegroupings/openup_basic_disciplines_AF6D7A8E.html"
+ guid="__BZycP1UEdmek8CQTQgrOQ">disciplines</a> in a software development lifecycle by guiding the team in the following
+ high level activities:
+</p>
+<ul>
+ <li>
+ Customer needs and requirements are elicited and captured, with continuous customer involvement.
+ </li>
+ <li>
+ A robust architecture for the system is evolved, addressing technical risks and promoting team organization.
+ </li>
+ <li>
+ For each requirement, a technical solution is designed, implemented and tested, which conforms to the architectural
+ decisions.
+ </li>
+ <li>
+ The system is evaluated by tests that validate customer requirements.
+ </li>
+ <li>
+ Defects and enhancements feed back into development.
+ </li>
+ <li>
+ Work is prioritized, iterations are planned and assessed, and team members take on work to be done.
+ </li>
+</ul>
+<p>
+ However, OpenUP assumes that the project team is not responsible for certain activities and decisions that are assigned
+ to other areas of the organization, such as:
+</p>
+<ul>
+ <li>
+ Creation of the business case is dealt with by management who decides whether or not the project is worth investing
+ in, what is the return on investment, and so on.
+ </li>
+ <li>
+ Environment setup - some organizational issues may not be in the scope of the team, such as: installation,
+ configuration and licensing of development tools and configuration management tools; development process
+ customization and publishing, etc.
+ </li>
+ <li>
+ Deployment and operation - addressed at an organizational rather than a team level.
+ </li>
+</ul>
+<p>
+ Other areas of concern are also not present in OpenUP, because small teams do not need to deal with the formality or
+ overhead of these areas. They include, but are not limited to:
+</p>
+<ul>
+ <li>
+ Advanced configuration management
+ </li>
+ <li>
+ Advanced requirements management
+ </li>
+ <li>
+ Program and portfolio management
+ </li>
+</ul>
+<h4>
+ Extensible
+</h4>
+<p>
+ OpenUP can be adopted by projects as it is, out-of-the-box, because it's minimal and complete.
+</p>
+<p>
+ However, different projects may have different needs. Organizations may be interested in customizing some aspects of
+ OpenUP to adapt it to their projects. These are some examples of possible customization:
+</p>
+<ul>
+ <li>
+ Add new or rename existing roles
+ </li>
+ <li>
+ Add steps to existing tasks
+ </li>
+ <li>
+ Create new guidelines on a given technique
+ </li>
+ <li>
+ Remove a given content area
+ </li>
+ <li>
+ Modify existing or add new templates to artifacts
+ </li>
+ <li>
+ Modify or create a new process lifecycle
+ </li>
+ <li>
+ Add or remove process content
+ </li>
+ <li>
+ Add guidance on how to achieve compliance
+ </li>
+ <li>
+ Add guidance specific to a technology being used
+ </li>
+ <li>
+ Replace or augment&nbsp;one of the layers with new&nbsp;content (e.g. by changing&nbsp;or adding material to how
+ management is performed)
+ </li>
+ <li>
+ Etc.
+ </li>
+</ul>
+<p>
+ OpenUP can be customized and extended by using the EPF Composer tool, which allows you to author, configure and publish
+ methods. With EPF Composer, you can add, remove and change elements according to your team needs, then publish the
+ content to serve as guidance for your team.
+</p>
+<p>
+ See more information about customization in <a class="elementLinkWithType"
+ href="./../../../publish.openup/guidances/supportingmaterials/resources_for_modifying_methods_7663A1A6.html"
+ guid="_omneEMX4EduywMSzPTUUwA">Supporting Material: Resources for Modifying Methods</a>.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/publish.openup.base/guidances/supportingmaterials/openup_family.xmi b/praclib/temp/publish.openup.base/guidances/supportingmaterials/openup_family.xmi
new file mode 100644
index 0000000..94e4945
--- /dev/null
+++ b/praclib/temp/publish.openup.base/guidances/supportingmaterials/openup_family.xmi
@@ -0,0 +1,65 @@
+<?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="-SzBbFkdIbmuzPg7qVDolbA"
+ name="new_supporting_material,_9VLUIMn8EdyuBO4ZIzcyig" guid="-SzBbFkdIbmuzPg7qVDolbA"
+ changeDate="2008-01-23T13:49:26.562-0800" version="7.2.0">
+ <mainDescription><p>
+ The OpenUP family of processes aims at addressing a broad variety of project types while sharing a set of common
+ characteristics. These are the key principles of:
+</p>
+<ul>
+ <li>
+ <a class="elementLink"
+ href="./../../../core.mgmt.common.base/guidances/concepts/core_principle_collaborate_EC5EB51F.html"
+ guid="_KkTIsMp7EdqC_NfSivunjA">Collaborate to align interests and share understanding</a>
+ </li>
+ <li>
+ <a class="elementLink"
+ href="./../../../core.mgmt.common.base/guidances/concepts/core_principle_evolve_BFD9AEB4.html"
+ guid="_GXiogMvoEdqukPpotm3DYg">Evolve to continuously obtain feedback and improve</a>
+ </li>
+ <li>
+ <a class="elementLink"
+ href="./../../../core.mgmt.common.base/guidances/concepts/core_principle_focus_346C6FAF.html"
+ guid="_9gocwMvoEdqukPpotm3DYg">Focus on the architecture early to minimize risks and organize development</a>
+ </li>
+ <li>
+ <a class="elementLink"
+ href="./../../../core.mgmt.common.base/guidances/concepts/core_principle_balance_793DD27.html"
+ guid="_ssG6MMvpEdqukPpotm3DYg">Balance competing priorities to maximize stakeholder value</a>.
+ </li>
+</ul>
+<p>
+ Processes in the OpenUP family are written as extensions to the core OpenUP process, which embraces a pragmatic, agile
+ philosophy focusing on the collaborative nature of software development. This core OpenUP process is a tools-agnostic,
+ low-ceremony process that can be extended to address a broad variety of project types.
+</p>
+<p>
+ By adding process plug-ins, extensions to OpenUP can be&nbsp;created that address a variety of development concerns,
+ such as SOA, geographical distribution, model-driven architecture and embedded systems. Tool and technology specific
+ guidance can be added, such as guidance on J2EE, and a variety of development tools. Some of these extensions can be
+ quite modest, adding&nbsp;for example&nbsp;just tool specific guidance to existing tasks, while others could be quite
+ comprehensive, creating processes that provide a radically expanded scope with new or altered artifacts, new or altered
+ tasks, and new or altered roles.
+</p>
+<p>
+ As stated above, to qualify as members of the OpenUP family, extending processes&nbsp;must comply with the key
+ principles of OpenUP and be written as extensions to the OpenUP core process.
+</p>
+<p>
+ Extensions to OpenUP can be:
+</p>
+<ul>
+ <li>
+ used internally by an organization
+ </li>
+ <li>
+ open source as a part of the EPF project,
+ </li>
+ <li>
+ made freely available outside the open source licenses of Eclipse (EPL)
+ </li>
+</ul></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/publish.openup.base/guidances/supportingmaterials/resources/about.gif b/praclib/temp/publish.openup.base/guidances/supportingmaterials/resources/about.gif
new file mode 100644
index 0000000..1316610
--- /dev/null
+++ b/praclib/temp/publish.openup.base/guidances/supportingmaterials/resources/about.gif
Binary files differ
diff --git a/praclib/temp/publish.openup.base/guidances/supportingmaterials/resources/back_to_top.gif b/praclib/temp/publish.openup.base/guidances/supportingmaterials/resources/back_to_top.gif
new file mode 100644
index 0000000..356d954
--- /dev/null
+++ b/praclib/temp/publish.openup.base/guidances/supportingmaterials/resources/back_to_top.gif
Binary files differ
diff --git a/praclib/temp/publish.openup.base/guidances/supportingmaterials/resources/lib_16.gif b/praclib/temp/publish.openup.base/guidances/supportingmaterials/resources/lib_16.gif
new file mode 100644
index 0000000..00a311e
--- /dev/null
+++ b/praclib/temp/publish.openup.base/guidances/supportingmaterials/resources/lib_16.gif
Binary files differ
diff --git a/praclib/temp/publish.openup.base/guidances/supportingmaterials/resources/lib_32.gif b/praclib/temp/publish.openup.base/guidances/supportingmaterials/resources/lib_32.gif
new file mode 100644
index 0000000..cae5c19
--- /dev/null
+++ b/praclib/temp/publish.openup.base/guidances/supportingmaterials/resources/lib_32.gif
Binary files differ
diff --git a/praclib/temp/publish.openup.base/guidances/supportingmaterials/resources/mic.gif b/praclib/temp/publish.openup.base/guidances/supportingmaterials/resources/mic.gif
new file mode 100644
index 0000000..0b316db
--- /dev/null
+++ b/praclib/temp/publish.openup.base/guidances/supportingmaterials/resources/mic.gif
Binary files differ
diff --git a/praclib/temp/publish.openup.base/guidances/supportingmaterials/resources/micL.gif b/praclib/temp/publish.openup.base/guidances/supportingmaterials/resources/micL.gif
new file mode 100644
index 0000000..1826cbd
--- /dev/null
+++ b/praclib/temp/publish.openup.base/guidances/supportingmaterials/resources/micL.gif
Binary files differ
diff --git a/praclib/temp/publish.openup.base/guidances/supportingmaterials/resources/practices.jpg b/praclib/temp/publish.openup.base/guidances/supportingmaterials/resources/practices.jpg
new file mode 100644
index 0000000..e3e5b57
--- /dev/null
+++ b/praclib/temp/publish.openup.base/guidances/supportingmaterials/resources/practices.jpg
Binary files differ
diff --git a/praclib/temp/publish.openup.base/guidances/supportingmaterials/resources_for_contributing_to_openup.xmi b/praclib/temp/publish.openup.base/guidances/supportingmaterials/resources_for_contributing_to_openup.xmi
new file mode 100644
index 0000000..7c7f8d0
--- /dev/null
+++ b/praclib/temp/publish.openup.base/guidances/supportingmaterials/resources_for_contributing_to_openup.xmi
@@ -0,0 +1,87 @@
+<?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: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="-L1P2_4P5Yqtia4p34Th7FQ"
+ name="resources_for_contributing_to_openup,_t9yXEMX4EduywMSzPTUUwA" guid="-L1P2_4P5Yqtia4p34Th7FQ"
+ changeDate="2008-02-22T10:20:53.171-0500" version="7.2.0">
+ <mainDescription><p>
+ <strong>[*** Consider making this content less OpenUP-specific and more general for any open source process/practice
+ contribution.&nbsp; Once it is more general, it should be moved to a more general place (such as core.default.tool_def
+ or common) ***]</strong>
+</p>
+<h3>
+ Opportunities in the OpenUP community
+</h3>
+<p>
+ OpenUP is developed by the Eclipse Process Framework (EPF) team. EPF is an open source community that depends solely on
+ the active participation of its user community to produce process content and tools. There are a variety of ways to
+ participate in the development and deployment of OpenUP, depending on your interest and skill level.
+</p>
+<p>
+ If all you want to do is ask a few questions to get started, sign up for the EPF Newsgroup. If you want to participate
+ in discussions and decisions about the content and direction of OpenUP, sign up for the epf-dev mailing list. Use
+ Bugzilla to get your hands dirty by reporting bugs and enhancements, verifying the correctness of method content, or
+ submitting method content to address process issues. Participate at the highest levels by joining OpenUP technical and
+ committee meetings. These meetings are where detailed process issues and product strategy are discussed.
+</p>
+<p>
+ Everyone who downloads or uses OpenUP is encouraged to participate at some level. OpenUP is only as good as the quality
+ of the participation of its contributors.
+</p>
+<h4>
+ EPF newsgroup
+</h4>
+<p>
+ The EPF Newsgroup is the place to ask and answer questions about OpenUP, EPF Composer, and other EPF processes. Most of
+ the traffic involves how to use EPF Composer and OpenUP. It’s monitored by the community, and you can access it like
+ you do any newsgroup. Everyone who uses OpenUP will benefit from the support it offers and by receiving announcements
+ about OpenUP. Sign up for the <a href="http://www.eclipse.org/epf/community/community_index.php"
+ target="_blank">newsgroup.</a>
+</p>
+<h4>
+ EPF-Dev mailing list
+</h4>
+<p>
+ The epf-dev mailing list is used by the OpenUP development community to communicate and discuss development issues.
+ Sign up for the <a href="https://dev.eclipse.org/mailman/listinfo/epf-dev" target="_blank">mailing list</a> to
+ participate in technical discussions and receive meeting announcements.
+</p>
+<h4>
+ Bugs, enhancements, and process content
+</h4>
+<p>
+ Bugzilla is the tool used to track changes and tasks for OpenUP. Bugzilla is the Work Items List for the OpenUP project
+ and contains the requirements, enhancements, bugs, to-do items, and so forth for the project. Anyone in the community
+ is invited to report bugs and enhancements, to provide content addressing the bugs and enhancements, and to help
+ validate that the content is correct. You can provide content simply by adding an attachment to any Bugzilla entry.
+</p>
+<p>
+ Learn how to use <a href="http://www.eclipse.org/epf/process/change_request_faq.php" target="_blank">Bugzilla change
+ requests</a> for OpenUP.
+</p>
+<p>
+ Content can be submitted as text files or exported from EPF Composer as plug-ins or XML. Edit the latest version of the
+ libraries by downloading them from the CVS in EPF Composer. Set up EPF Composer to download the OpenUP library by
+ following the instructions on the <a href="http://www.eclipse.org/epf/composer_dev_guide/cvs_setup.php"
+ target="_blank">EPF Composer Development Guide</a>. Note that only committers can commit changes to the CVS. Any
+ changes made by contributors must be attached to a Bugzilla entry.
+</p>
+<h4>
+ Meetings and committees
+</h4>
+<p>
+ There are numerous meetings every week to discuss OpenUP progress and define solutions. The <a title="EPF Calendar"
+ href="http://tech.groups.yahoo.com/group/eclipseprocessframework/cal" target="_blank">EPF Calendar</a> is open to
+ everyone and lists all upcoming meetings (teleconferences and face-to-face). Participate in these meetings to dive
+ deeply into OpenUP issues by collaborating directly with other members of the community. Although everyone is welcome
+ to attend these meetings, it’s generally expected that participants will, at some point, take responsibility for some
+ OpenUP tasks.
+</p>
+<p>
+ The calendar and epf-dev newsgroup also announce the EPF Committer meetings. Currently, these are held quarterly in
+ both the North America and Europe. This is the highest level of participation, where committers and contributors make
+ critical decisions about EPF projects, including OpenUP. Everyone from the OpenUP community is welcome, and attendees
+ are expected to participate in discussions and take on responsibility for addressing aspects of the EPF.
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/publish.openup.base/guidances/supportingmaterials/welcome.xmi b/praclib/temp/publish.openup.base/guidances/supportingmaterials/welcome.xmi
new file mode 100644
index 0000000..5b30de0
--- /dev/null
+++ b/praclib/temp/publish.openup.base/guidances/supportingmaterials/welcome.xmi
@@ -0,0 +1,78 @@
+<?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="-wnTtT1mWib0PnhUQquLy8A"
+ name="new_supporting_material,_yDfxMMN9Edy3nv0ZK8D4GQ" guid="-wnTtT1mWib0PnhUQquLy8A"
+ changeDate="2008-01-21T08:18:22.375-0800" version="7.2.0">
+ <mainDescription><br />
+<table title="" cellspacing="0" cellpadding="2" width="85%" border="0">
+ <tbody>
+ <tr>
+ <td>
+ <img height="165" alt="image of jigsaw pieces" src="./resources/practices.jpg" width="198" />
+ </td>
+ <td>
+ <font size="5"><strong>Welcome to the<br />
+ Open Source Practices for Agile Projects</strong></font>
+ </td>
+ </tr>
+ </tbody>
+</table><br />
+<br />
+<br />
+<h3>
+ Why Practices?
+</h3>
+<p>
+ Practices enable a new approach to building methods - practice composition.
+</p>
+<p>
+ This approach offers the following benefits:
+</p>
+<ul>
+ <li>
+ Adaptability and scalability
+ </li>
+ <li>
+ Incremental adoption
+ </li>
+ <li>
+ Easy to configure and use
+ </li>
+ <li>
+ Community development
+ </li>
+</ul>
+<h3>
+ Adaptability and Scalability
+</h3>
+<p>
+ The set of practices included in the&nbsp;Open Source&nbsp;Practices for Agile Projects supports a range of
+ solutions.&nbsp;In particular, these agile practices can be adapted to suit your organization and supplemented by your
+ own practices.&nbsp;
+</p>
+<h3>
+ Incremental Adoption
+</h3>
+<p>
+ Each practice is described as a standalone capability that can be adopted by an organization or project.&nbsp;Each
+ practice may include enablement materials that explain how to get started.&nbsp;&nbsp;
+</p>
+<h3>
+ Easy to Configure and Use
+</h3>
+<p>
+ Creating a method is as simple as selecting the practices that you wish to adopt, and then publishing the
+ results.&nbsp;Each practice adds itself into the framework so that content can be viewed by practice, or across
+ practices by work product, role, task and so on.
+</p>
+<h3>
+ Community Development
+</h3>
+<p>
+ Since a practice can be easily authored on its own, practices are ideal for community development.&nbsp;The basic agile
+ practices for the&nbsp;Open Source&nbsp;Practice Library are, in fact, developed by the Eclipse Process Framework
+ community.&nbsp;
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/publish.openup.base/guidances/supportingmaterials/who_should_use_openup.xmi b/praclib/temp/publish.openup.base/guidances/supportingmaterials/who_should_use_openup.xmi
new file mode 100644
index 0000000..7600d06
--- /dev/null
+++ b/praclib/temp/publish.openup.base/guidances/supportingmaterials/who_should_use_openup.xmi
@@ -0,0 +1,46 @@
+<?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="-gIuZFV8-iU-9QVhpmPUtWw"
+ name="new_supporting_material,_jd1tQMn9EdyuBO4ZIzcyig" guid="-gIuZFV8-iU-9QVhpmPUtWw"
+ changeDate="2008-01-23T16:53:36.921-0500">
+ <mainDescription><p>
+ OpenUP is most useful for four primary groups of users:
+</p>
+<ul>
+ <li>
+ Software development practitioners (developers, project managers, analysts, and testers) working together as a
+ project team
+ </li>
+ <li>
+ Stakeholders
+ </li>
+ <li>
+ Software process engineers
+ </li>
+ <li>
+ Instructors
+ </li>
+</ul>
+<p>
+ Software development practitioners can find guidance on what is required of them in the roles defined by OpenUP. Each
+ role describes a set of activities and artifacts for which the role is responsible. Guidance is also given on how those
+ roles collaborate.
+</p>
+<p>
+ Stakeholders will find guidance on what they may expect from the software development team, and how the software will
+ be created. OpenUP also describes the stakeholders' responsibilities, and states how they can best work with the
+ development team to obtain software that meets their needs.
+</p>
+<p>
+ Software process engineers can use EPF Composer to extend and modify OpenUP. Modification may be as simple as altering
+ templates for work products, or as sophisticated as adding activities necessary for creating software in your specific
+ environment (such as audits for safety-critical systems). In addition to modifying method content, process engineers
+ can add, change, or remove process flows to add organization-specific capability patterns.
+</p>
+<p>
+ OpenUP is appropriate for academic organizations also. As an open source process, it can serve as the basis for
+ software engineering courses and, when combined with the EPF Composer, courses in software process engineering.<br />
+</p></mainDescription>
+</org.eclipse.epf.uma:ContentDescription>
diff --git a/praclib/temp/publish.openup.base/plugin.xmi b/praclib/temp/publish.openup.base/plugin.xmi
new file mode 100644
index 0000000..fbb34f1
--- /dev/null
+++ b/praclib/temp/publish.openup.base/plugin.xmi
@@ -0,0 +1,312 @@
+<?xml version="1.0" encoding="UTF-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.4/uma.ecore" xmlns:org.eclipse.epf.uma.resourcemanager="http:///org/eclipse/epf/uma/resourcemanager.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">
+ <org.eclipse.epf.uma.resourcemanager:ResourceManager xmi:id="_4ulTkMg7EdyXeo04os5BOw"
+ guid="_4ulTkMg7EdyXeo04os5BOw">
+ <resourceDescriptors xmi:id="__blXAMg7EdyXeo04os5BOw" id="-wnTtT1mWib0PnhUQquLy8A"
+ uri="guidances/supportingmaterials/welcome.xmi"/>
+ <resourceDescriptors xmi:id="_7R-_QMn6EdyuBO4ZIzcyig" id="-ri4DnKtNEQ38B72_KOz06w"
+ uri="customcategories/introduction_to_openup.xmi"/>
+ <resourceDescriptors xmi:id="_qmWS8cn7EdyuBO4ZIzcyig" id="-2Exr8xUknR1c7fbnPMMrTw"
+ uri="customcategories/core_principles_category.xmi"/>
+ <resourceDescriptors xmi:id="_9VUeEcn8EdyuBO4ZIzcyig" id="-AO488Z6M5HCAbxm1c-SjUA"
+ uri="guidances/supportingmaterials/minimal_complete_extensible.xmi"/>
+ <resourceDescriptors xmi:id="_TrFmMcn9EdyuBO4ZIzcyig" id="-SzBbFkdIbmuzPg7qVDolbA"
+ uri="guidances/supportingmaterials/openup_family.xmi"/>
+ <resourceDescriptors xmi:id="_p4zlkcn9EdyuBO4ZIzcyig" id="-gIuZFV8-iU-9QVhpmPUtWw"
+ uri="guidances/supportingmaterials/who_should_use_openup.xmi"/>
+ <resourceDescriptors xmi:id="_PbeVsMn-EdyuBO4ZIzcyig" id="-BZL7M9SUWacUmnxTIShrmA"
+ uri="customcategories/getting_started.xmi"/>
+ <resourceDescriptors xmi:id="_ZrIAkMn-EdyuBO4ZIzcyig" id="-APgHPRv2KxEoFdcbHUli5w"
+ uri="guidances/roadmaps/openup_roadmap.xmi"/>
+ <resourceDescriptors xmi:id="_8n8Iwcn-EdyuBO4ZIzcyig" id="-L1P2_4P5Yqtia4p34Th7FQ"
+ uri="guidances/supportingmaterials/resources_for_contributing_to_openup.xmi"/>
+ <resourceDescriptors xmi:id="_pJyRgMn_EdyuBO4ZIzcyig" id="-cGfGHqSFsvSqPwBKeoShxA"
+ uri="disciplinegroupings/openup_disciplines.xmi"/>
+ <resourceDescriptors xmi:id="_DqSUscoAEdyuBO4ZIzcyig" id="-R4YxqKgYJ6BDk0wsjrMZ5Q"
+ uri="customcategories/discipline_list.openup.xmi"/>
+ <resourceDescriptors xmi:id="_eIdKscoCEdyuBO4ZIzcyig" id="-axI6vPcMAQ0mu7CwmZuwgg"
+ uri="customcategories/domain_list.openup.xmi"/>
+ <resourceDescriptors xmi:id="_jEGI0MoDEdyuBO4ZIzcyig" id="-ycCaKmcEl9VQJtZYXMdW-w"
+ uri="customcategories/role_list.openup.xmi"/>
+ <resourceDescriptors xmi:id="_I6hwsPGaEdqiDINUyockoA" id="-WFD3nKccpkueaG15cHT-fA"
+ uri="guidances/supportingmaterials/about_openup.xmi"/>
+ <resourceDescriptors xmi:id="_VIeQwMvpEdqukPpotm3DYg" id="-HTMJFV29MTZkKWqnIo01Gg"
+ uri="guidances/concepts/core_principle_focus.xmi"/>
+ <resourceDescriptors xmi:id="_PUrQsMvqEdqukPpotm3DYg" id="-I4IbR1GW6IFBCdq9SiMUsw"
+ uri="guidances/concepts/core_principle_balance.xmi"/>
+ <resourceDescriptors xmi:id="_ffK0QMvoEdqukPpotm3DYg" id="-aMD1wQVJLzzlMARfHBdOBQ"
+ uri="guidances/concepts/core_principle_evolve.xmi"/>
+ <resourceDescriptors xmi:id="_aV48scp8EdqC_NfSivunjA" id="-IXfkG-XfnoEo0xgux482Kw"
+ uri="guidances/concepts/core_principle_collaborate.xmi"/>
+ <resourceDescriptors xmi:id="_26exEeL0EdyM47cGD2jiaQ" id="-zuqK2tneGKchXpqLVRtwlg"
+ uri="guidances/concepts/project_lifecycle.additon.xmi"/>
+ </org.eclipse.epf.uma.resourcemanager:ResourceManager>
+ <org.eclipse.epf.uma:MethodPlugin xmi:id="_4ulTgMg7EdyXeo04os5BOw" name="publish.openup.base"
+ guid="_4ulTgMg7EdyXeo04os5BOw" changeDate="2008-02-08T11:33:42.750-0800">
+ <copyrightStatement href="uma://_iVydgENdEdy245g62lfWcA#_cTs20KzREduOqvpk_MDLfQ"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4ulTgcg7EdyXeo04os5BOw"
+ name="Content" guid="_4ulTgcg7EdyXeo04os5BOw">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4ulTgsg7EdyXeo04os5BOw"
+ name="Categories" guid="_4ulTgsg7EdyXeo04os5BOw">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4ulTg8g7EdyXeo04os5BOw"
+ name="Domains" guid="_4ulTg8g7EdyXeo04os5BOw"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4ulThMg7EdyXeo04os5BOw"
+ name="Disciplines" guid="_4ulThMg7EdyXeo04os5BOw">
+ <contentElements xsi:type="org.eclipse.epf.uma:DisciplineGrouping" xmi:id="_UBqBMMn_EdyuBO4ZIzcyig"
+ name="openup_disciplines" guid="_UBqBMMn_EdyuBO4ZIzcyig" briefDescription="This is the list of disciplines in OpenUP, which help organize tasks."
+ presentationName="OpenUP Disciplines">
+ <presentation xmi:id="-cGfGHqSFsvSqPwBKeoShxA" href="uma://-cGfGHqSFsvSqPwBKeoShxA#-cGfGHqSFsvSqPwBKeoShxA"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4ulThcg7EdyXeo04os5BOw"
+ name="RoleSets" guid="_4ulThcg7EdyXeo04os5BOw"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4ulThsg7EdyXeo04os5BOw"
+ name="WP Types" guid="_4ulThsg7EdyXeo04os5BOw"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4ulTh8g7EdyXeo04os5BOw"
+ name="Tools" guid="_4ulTh8g7EdyXeo04os5BOw"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4ulTiMg7EdyXeo04os5BOw"
+ name="StandardCategories" guid="_4ulTiMg7EdyXeo04os5BOw"/>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4ulTicg7EdyXeo04os5BOw"
+ name="CustomCategories" guid="_4ulTicg7EdyXeo04os5BOw">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4ulTisg7EdyXeo04os5BOw"
+ name="Hidden" guid="_4ulTisg7EdyXeo04os5BOw">
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_4ulTi8g7EdyXeo04os5BOw"
+ name="Custom Categories" guid="_4ulTi8g7EdyXeo04os5BOw" categorizedElements="_s-pk0Mg_EdygFZkm1d5NtQ _fzN2YN4ZEdyhmsbt0Xyl8A _UkkXMN4aEdyhmsbt0Xyl8A"/>
+ </childPackages>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_Gc5BIMg9EdyXeo04os5BOw"
+ name="practices" guid="_Gc5BIMg9EdyXeo04os5BOw" presentationName="Practices"
+ shapeicon="customcategories/resources/pract_dgm32.gif" nodeicon="customcategories/resources/pract_obj.gif">
+ <categorizedElements xsi:type="org.eclipse.epf.uma:CustomCategory" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_auUD0NQuEdyM_J8-fv54DA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:CustomCategory" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_lBrxENQuEdyM_J8-fv54DA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_s-pk0Mg_EdygFZkm1d5NtQ"
+ name="view_tabs_for_openup" guid="_s-pk0Mg_EdygFZkm1d5NtQ" presentationName="View Tabs for OpenUP"
+ shapeicon="customcategories/resources/lib_32.gif" nodeicon="customcategories/resources/lib_16.gif"
+ categorizedElements="_Sq2EYMhAEdygFZkm1d5NtQ _pA1jIMn6EdyuBO4ZIzcyig"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_Sq2EYMhAEdygFZkm1d5NtQ"
+ name="epf_practices_library" guid="_Sq2EYMhAEdygFZkm1d5NtQ" presentationName="EPF Practices"
+ shapeicon="customcategories/resources/pract_dgm32.gif" nodeicon="customcategories/resources/pract_obj.gif">
+ <categorizedElements xsi:type="org.eclipse.epf.uma:SupportingMaterial"
+ href="#__ZzOUcg7EdyXeo04os5BOw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:CustomCategory" href="#_Gc5BIMg9EdyXeo04os5BOw"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:CustomCategory" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCIHYcRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_pA1jIMn6EdyuBO4ZIzcyig"
+ name="openup" guid="_pA1jIMn6EdyuBO4ZIzcyig" presentationName="OpenUP"
+ shapeicon="customcategories/resources/delproc_lg_dgm32.gif" nodeicon="customcategories/resources/delproc_obj.gif">
+ <categorizedElements xsi:type="org.eclipse.epf.uma:CustomCategory" href="#_7PTesMn6EdyuBO4ZIzcyig"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:CustomCategory" href="#_CjSiUMn-EdyuBO4ZIzcyig"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:CustomCategory" href="#_3ZvJEMn_EdyuBO4ZIzcyig"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:CustomCategory" href="#_UTepoMoCEdyuBO4ZIzcyig"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:CustomCategory" href="#_Mp2wYMoDEdyuBO4ZIzcyig"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:DeliveryProcess" href="uma://_SuWj4NOPEdyqlogshP8l4g#_SuWj4dOPEdyqlogshP8l4g"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:CustomCategory" href="uma://_vsno4EKmEdyrauqpmnA8jQ#_qdO80MRhEdyD76CYS6Ta7A"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:CustomCategory" href="#_BpvFAMt7EdyuBO4ZIzcyig"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:SupportingMaterial"
+ href="uma://_iVydgENdEdy245g62lfWcA#_UaGfECcTEduSX6N2jUafGA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_7PTesMn6EdyuBO4ZIzcyig"
+ name="introduction_to_openup" guid="_7PTesMn6EdyuBO4ZIzcyig" presentationName="Introduction to OpenUP"
+ shapeicon="customcategories/resources/icon_introL.gif" nodeicon="customcategories/resources/mic.gif">
+ <presentation xmi:id="-ri4DnKtNEQ38B72_KOz06w" href="uma://-ri4DnKtNEQ38B72_KOz06w#-ri4DnKtNEQ38B72_KOz06w"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:CustomCategory" href="#_qktUMMn7EdyuBO4ZIzcyig"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:SupportingMaterial"
+ href="#_xKvXkMn8EdyuBO4ZIzcyig"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_DI_tICNaEdyCq8v2ZO4QcA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_S80VwCNbEdyCq8v2ZO4QcA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Concept" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_nSfVwCNYEdyCq8v2ZO4QcA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:SupportingMaterial"
+ href="#_9VLUIMn8EdyuBO4ZIzcyig"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:SupportingMaterial"
+ href="#_jd1tQMn9EdyuBO4ZIzcyig"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_qktUMMn7EdyuBO4ZIzcyig"
+ name="core_principles_category" guid="_qktUMMn7EdyuBO4ZIzcyig" briefDescription="Four core principles capture the general intentions behind OpenUP. They create the foundation for interpreting roles and work products, and for performing tasks."
+ presentationName="Core Principles" shapeicon="customcategories/resources/concept_dgm32.gif"
+ nodeicon="customcategories/resources/concept_obj.gif" categorizedElements="_ssG6MMvpEdqukPpotm3DYg _KkTIsMp7EdqC_NfSivunjA _9gocwMvoEdqukPpotm3DYg _GXiogMvoEdqukPpotm3DYg">
+ <presentation xmi:id="-2Exr8xUknR1c7fbnPMMrTw" href="uma://-2Exr8xUknR1c7fbnPMMrTw#-2Exr8xUknR1c7fbnPMMrTw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_CjSiUMn-EdyuBO4ZIzcyig"
+ name="getting_started" guid="_CjSiUMn-EdyuBO4ZIzcyig" briefDescription="This area provides information useful for understanding how to deploy and adopt OpenUP."
+ presentationName="Getting Started" shapeicon="customcategories/resources/micL.gif"
+ nodeicon="customcategories/resources/mic.gif">
+ <presentation xmi:id="-BZL7M9SUWacUmnxTIShrmA" href="uma://-BZL7M9SUWacUmnxTIShrmA#-BZL7M9SUWacUmnxTIShrmA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:Roadmap" href="#_Q2ErcMn-EdyuBO4ZIzcyig"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:SupportingMaterial"
+ href="uma://_fRdVEMYbEdyXeo04os5BOw#_omneEMX4EduywMSzPTUUwA"/>
+ <categorizedElements xsi:type="org.eclipse.epf.uma:SupportingMaterial"
+ href="#_t9yXEMX4EduywMSzPTUUwA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_3ZvJEMn_EdyuBO4ZIzcyig"
+ name="discipline_list.openup" guid="_3ZvJEMn_EdyuBO4ZIzcyig" briefDescription="This is the list of disciplines in OpenUP, which help organize tasks."
+ presentationName="OpenUP Disciplines" shapeicon="customcategories/resources/discipline_dgm32.gif"
+ nodeicon="customcategories/resources/discipline_obj.gif" variabilityType="extendsReplaces">
+ <presentation xmi:id="-R4YxqKgYJ6BDk0wsjrMZ5Q" href="uma://-R4YxqKgYJ6BDk0wsjrMZ5Q#-R4YxqKgYJ6BDk0wsjrMZ5Q"/>
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_PxzG4MRfEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_UTepoMoCEdyuBO4ZIzcyig"
+ name="domain_list.openup" guid="_UTepoMoCEdyuBO4ZIzcyig" briefDescription="This is the list of domains in OpenUp providing organization of work products."
+ presentationName="OpenUP Work Products" shapeicon="customcategories/resources/workproducts_lg_obj.gif"
+ nodeicon="customcategories/resources/workproducts_obj.gif" variabilityType="extendsReplaces">
+ <presentation xmi:id="-axI6vPcMAQ0mu7CwmZuwgg" href="uma://-axI6vPcMAQ0mu7CwmZuwgg#-axI6vPcMAQ0mu7CwmZuwgg"/>
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_EfGDkMRfEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_Mp2wYMoDEdyuBO4ZIzcyig"
+ name="role_list.openup" guid="_Mp2wYMoDEdyuBO4ZIzcyig" briefDescription="This is the list of roles in OpenUP."
+ presentationName="OpenUP Roles" shapeicon="customcategories/resources/roles_dgm32.gif"
+ nodeicon="customcategories/resources/roles_obj.gif" variabilityType="extendsReplaces">
+ <presentation xmi:id="-ycCaKmcEl9VQJtZYXMdW-w" href="uma://-ycCaKmcEl9VQJtZYXMdW-w#-ycCaKmcEl9VQJtZYXMdW-w"/>
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCIHZMRdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_BpvFAMt7EdyuBO4ZIzcyig"
+ name="about" guid="_BpvFAMt7EdyuBO4ZIzcyig" presentationName="About"
+ nodeicon="customcategories/resources/about.gif" categorizedElements="_8tSNMPGYEdqiDINUyockoA"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_fzN2YN4ZEdyhmsbt0Xyl8A"
+ name="contributions_to_practices" guid="_fzN2YN4ZEdyhmsbt0Xyl8A" presentationName="Contributions to Custom Cats for Practices"
+ categorizedElements="_mjf3YN4ZEdyhmsbt0Xyl8A"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_mjf3YN4ZEdyhmsbt0Xyl8A"
+ name="risk_value_lifecycle_practice.concepts" guid="_mjf3YN4ZEdyhmsbt0Xyl8A"
+ variabilityType="contributes" categorizedElements="_ssG6MMvpEdqukPpotm3DYg _KkTIsMp7EdqC_NfSivunjA _GXiogMvoEdqukPpotm3DYg _9gocwMvoEdqukPpotm3DYg">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_UfU6wOMQEdyM47cGD2jiaQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_UkkXMN4aEdyhmsbt0Xyl8A"
+ name="contributions_to_nav_building_blocks" guid="_UkkXMN4aEdyhmsbt0Xyl8A"
+ presentationName="Contributions to Navigation Building Blocks" categorizedElements="_ZoqjMN4aEdyhmsbt0Xyl8A"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:CustomCategory" xmi:id="_ZoqjMN4aEdyhmsbt0Xyl8A"
+ name="concept_list.assign" guid="_ZoqjMN4aEdyhmsbt0Xyl8A" variabilityType="contributes"
+ categorizedElements="_ssG6MMvpEdqukPpotm3DYg _KkTIsMp7EdqC_NfSivunjA _GXiogMvoEdqukPpotm3DYg _9gocwMvoEdqukPpotm3DYg">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:CustomCategory"
+ href="uma://_vsno4EKmEdyrauqpmnA8jQ#_WCR4Y8RdEdyD76CYS6Ta7A"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_4ulTjMg7EdyXeo04os5BOw"
+ name="CoreContent" guid="_4ulTjMg7EdyXeo04os5BOw">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="__ZzOUMg7EdyXeo04os5BOw"
+ name="OpenUP Practice Lib" guid="__ZzOUMg7EdyXeo04os5BOw">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_3aT48N4YEdyhmsbt0Xyl8A"
+ name="Contribute Core Principles to Practices" guid="_3aT48N4YEdyhmsbt0Xyl8A">
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_8pcQQN4YEdyhmsbt0Xyl8A"
+ name="inception_phase.principle" guid="_8pcQQN4YEdyhmsbt0Xyl8A" variabilityType="contributes"
+ conceptsAndPapers="_ssG6MMvpEdqukPpotm3DYg _KkTIsMp7EdqC_NfSivunjA">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Concept" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_0hmKgBOMEduCNqgZdt_OaA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_IXkEQN4ZEdyhmsbt0Xyl8A"
+ name="elaboration_phase.principle" guid="_IXkEQN4ZEdyhmsbt0Xyl8A"
+ variabilityType="contributes" conceptsAndPapers="_ssG6MMvpEdqukPpotm3DYg _KkTIsMp7EdqC_NfSivunjA _9gocwMvoEdqukPpotm3DYg">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Concept" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_2plxwBOMEduCNqgZdt_OaA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_PglVYN4ZEdyhmsbt0Xyl8A"
+ name="construction_phase.principle" guid="_PglVYN4ZEdyhmsbt0Xyl8A"
+ variabilityType="contributes" conceptsAndPapers="_GXiogMvoEdqukPpotm3DYg">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Concept" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_48EKsBOMEduCNqgZdt_OaA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_Ug9fAN4ZEdyhmsbt0Xyl8A"
+ name="transition_phase.principle" guid="_Ug9fAN4ZEdyhmsbt0Xyl8A" variabilityType="contributes"
+ conceptsAndPapers="_KkTIsMp7EdqC_NfSivunjA">
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Concept" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#__ca5UBOMEduCNqgZdt_OaA"/>
+ </contentElements>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_bGjA8OFQEdyhmsbt0Xyl8A"
+ name="Contributions to Open Source Practices" guid="_bGjA8OFQEdyhmsbt0Xyl8A">
+ <childPackages xsi:type="org.eclipse.epf.uma:ContentPackage" xmi:id="_cxOwQOL0EdyM47cGD2jiaQ"
+ name="Risk-Value Lifecycle" guid="_cxOwQOL0EdyM47cGD2jiaQ"/>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_j0leQOL0EdyM47cGD2jiaQ"
+ name="project_lifecycle.additon" guid="_j0leQOL0EdyM47cGD2jiaQ" variabilityType="contributes">
+ <presentation xmi:id="-zuqK2tneGKchXpqLVRtwlg" href="uma://-zuqK2tneGKchXpqLVRtwlg#-zuqK2tneGKchXpqLVRtwlg"/>
+ <variabilityBasedOnElement xsi:type="org.eclipse.epf.uma:Concept" href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_nSfVwCNYEdyCq8v2ZO4QcA"/>
+ </contentElements>
+ </childPackages>
+ <contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="__ZzOUcg7EdyXeo04os5BOw"
+ name="welcome" guid="__ZzOUcg7EdyXeo04os5BOw" presentationName="Welcome"
+ shapeicon="guidances/supportingmaterials/resources/lib_32.gif" nodeicon="guidances/supportingmaterials/resources/lib_16.gif">
+ <presentation xmi:id="-wnTtT1mWib0PnhUQquLy8A" href="uma://-wnTtT1mWib0PnhUQquLy8A#-wnTtT1mWib0PnhUQquLy8A"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="_xKvXkMn8EdyuBO4ZIzcyig"
+ name="minimal_complete_extensible" guid="_xKvXkMn8EdyuBO4ZIzcyig" briefDescription="OpenUP is minimal, complete, and extensible. It's the minimum amount of process for a small team. It can be used as-is or extended and customized for specific purposes."
+ presentationName="Minimal, Complete, and Extensible" shapeicon="guidances/supportingmaterials/resources/micL.gif"
+ nodeicon="guidances/supportingmaterials/resources/mic.gif">
+ <presentation xmi:id="-AO488Z6M5HCAbxm1c-SjUA" href="uma://-AO488Z6M5HCAbxm1c-SjUA#-AO488Z6M5HCAbxm1c-SjUA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="_9VLUIMn8EdyuBO4ZIzcyig"
+ name="openup_family" guid="_9VLUIMn8EdyuBO4ZIzcyig" briefDescription="OpenUP is a family of processes based on a common set of principles and a shared core process."
+ presentationName="The OpenUP Family" shapeicon="guidances/supportingmaterials/resources/micL.gif"
+ nodeicon="guidances/supportingmaterials/resources/mic.gif" conceptsAndPapers="_ssG6MMvpEdqukPpotm3DYg _KkTIsMp7EdqC_NfSivunjA _GXiogMvoEdqukPpotm3DYg _9gocwMvoEdqukPpotm3DYg">
+ <presentation xmi:id="-SzBbFkdIbmuzPg7qVDolbA" href="uma://-SzBbFkdIbmuzPg7qVDolbA#-SzBbFkdIbmuzPg7qVDolbA"/>
+ <supportingMaterials href="uma://_fRdVEMYbEdyXeo04os5BOw#_omneEMX4EduywMSzPTUUwA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="_jd1tQMn9EdyuBO4ZIzcyig"
+ name="who_should_use_openup" guid="_jd1tQMn9EdyuBO4ZIzcyig" briefDescription="This supporting material explains who should use OpenUP."
+ presentationName="Who Should Use OpenUP">
+ <presentation xmi:id="-gIuZFV8-iU-9QVhpmPUtWw" href="uma://-gIuZFV8-iU-9QVhpmPUtWw#-gIuZFV8-iU-9QVhpmPUtWw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Roadmap" xmi:id="_Q2ErcMn-EdyuBO4ZIzcyig"
+ name="openup_roadmap" guid="_Q2ErcMn-EdyuBO4ZIzcyig" briefDescription="This roadmap presents an overview of OpenUP, its purpose, and its lifecycle."
+ presentationName="OpenUP Roadmap">
+ <presentation xmi:id="-APgHPRv2KxEoFdcbHUli5w" href="uma://-APgHPRv2KxEoFdcbHUli5w#-APgHPRv2KxEoFdcbHUli5w"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="_t9yXEMX4EduywMSzPTUUwA"
+ name="resources_for_contributing_to_openup" guid="_t9yXEMX4EduywMSzPTUUwA"
+ briefDescription="There are many ways to contribute to OpenUP. Everyone who uses OpenUP is encouraged to participate in its ongoing improvement."
+ presentationName="Resources for Contributing to OpenUP">
+ <presentation xmi:id="-L1P2_4P5Yqtia4p34Th7FQ" href="uma://-L1P2_4P5Yqtia4p34Th7FQ#-L1P2_4P5Yqtia4p34Th7FQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:SupportingMaterial" xmi:id="_8tSNMPGYEdqiDINUyockoA"
+ name="about_openup" guid="_8tSNMPGYEdqiDINUyockoA" presentationName="About OpenUP"
+ nodeicon="guidances/supportingmaterials/resources/about.gif">
+ <presentation xmi:id="-WFD3nKccpkueaG15cHT-fA" href="uma://-WFD3nKccpkueaG15cHT-fA#-WFD3nKccpkueaG15cHT-fA"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_ssG6MMvpEdqukPpotm3DYg"
+ name="core_principle_balance" guid="_ssG6MMvpEdqukPpotm3DYg" briefDescription="Develop a solution that maximizes stakeholder benefits and complies with constraints placed on the project."
+ presentationName="Balance competing priorities to maximize stakeholder value">
+ <presentation xmi:id="-I4IbR1GW6IFBCdq9SiMUsw" href="uma://-I4IbR1GW6IFBCdq9SiMUsw#-I4IbR1GW6IFBCdq9SiMUsw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_KkTIsMp7EdqC_NfSivunjA"
+ name="core_principle_collaborate" guid="_KkTIsMp7EdqC_NfSivunjA" briefDescription="Develop collaborative practices that foster a healthy team environment. Good collaborative practices align the interests of project participants and help them develop a shared understanding of the project."
+ presentationName="Collaborate to align interests and share understanding">
+ <presentation xmi:id="-IXfkG-XfnoEo0xgux482Kw" href="uma://-IXfkG-XfnoEo0xgux482Kw#-IXfkG-XfnoEo0xgux482Kw"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_GXiogMvoEdqukPpotm3DYg"
+ name="core_principle_evolve" guid="_GXiogMvoEdqukPpotm3DYg" briefDescription="Promote practices that allow the team to get early and continuous feedback from stakeholders, and demonstrate incremental value to them."
+ presentationName="Evolve to continuously obtain feedback and improve">
+ <presentation xmi:id="-aMD1wQVJLzzlMARfHBdOBQ" href="uma://-aMD1wQVJLzzlMARfHBdOBQ#-aMD1wQVJLzzlMARfHBdOBQ"/>
+ </contentElements>
+ <contentElements xsi:type="org.eclipse.epf.uma:Concept" xmi:id="_9gocwMvoEdqukPpotm3DYg"
+ name="core_principle_focus" guid="_9gocwMvoEdqukPpotm3DYg" briefDescription="An evolving architecture helps the team to address complexity, drive risk mitigation, and organize development."
+ presentationName="Focus on the architecture early to minimize risks and organize development">
+ <presentation xmi:id="-HTMJFV29MTZkKWqnIo01Gg" href="uma://-HTMJFV29MTZkKWqnIo01Gg#-HTMJFV29MTZkKWqnIo01Gg"/>
+ </contentElements>
+ </childPackages>
+ </childPackages>
+ <childPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_4ulTjcg7EdyXeo04os5BOw"
+ name="CapabilityPatterns" guid="_4ulTjcg7EdyXeo04os5BOw"/>
+ </methodPackages>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_4ulTjsg7EdyXeo04os5BOw"
+ name="DeliveryProcesses" guid="_4ulTjsg7EdyXeo04os5BOw"/>
+ <methodPackages xsi:type="org.eclipse.epf.uma:ProcessPackage" xmi:id="_4ulTj8g7EdyXeo04os5BOw"
+ name="ProcessContributions" guid="_4ulTj8g7EdyXeo04os5BOw"/>
+ <bases href="uma://_vsno4EKmEdyrauqpmnA8jQ#_vsno4EKmEdyrauqpmnA8jQ"/>
+ <bases href="uma://_qqyzAJ6WEdyQN-zRFaRrCQ#_qqyzAJ6WEdyQN-zRFaRrCQ"/>
+ <bases href="uma://_nKS10J6YEdyQN-zRFaRrCQ#_nKS10J6YEdyQN-zRFaRrCQ"/>
+ <bases href="uma://_4gXdoL8BEdyWX5Yd-9QZ1A#_4gXdoL8BEdyWX5Yd-9QZ1A"/>
+ <bases href="uma://_40sbAJ6YEdyQN-zRFaRrCQ#_40sbAJ6YEdyQN-zRFaRrCQ"/>
+ <bases href="uma://_Hz9OMG5KEdyAHIxjZ9kpqw#_Hz9OMG5KEdyAHIxjZ9kpqw"/>
+ <bases href="uma://_Z2cK0LPPEduocbW-TPTq7A#_Z2cK0LPPEduocbW-TPTq7A"/>
+ <bases href="uma://_4gaS4LPREduocbW-TPTq7A#_4gaS4LPREduocbW-TPTq7A"/>
+ <bases href="uma://_Y9TKMLS9EduDY8LNbMCDBA#_Y9TKMLS9EduDY8LNbMCDBA"/>
+ <bases href="uma://_DZ1rEI7-Edy7q8CKc_B8eg#_DZ1rEI7-Edy7q8CKc_B8eg"/>
+ <bases href="uma://_GbYfULPaEduocbW-TPTq7A#_GbYfULPaEduocbW-TPTq7A"/>
+ <bases href="uma://_D-ExQMktEdygFZkm1d5NtQ#_D-ExQMktEdygFZkm1d5NtQ"/>
+ <bases href="uma://_0TmecJ-VEdy3Nc4rvuj7bA#_0TmecJ-VEdy3Nc4rvuj7bA"/>
+ <bases href="uma://_iVydgENdEdy245g62lfWcA#_iVydgENdEdy245g62lfWcA"/>
+ <bases href="uma://_Z7teANQ1EdyQ89W1tgswSQ#_Z7teANQ1EdyQ89W1tgswSQ"/>
+ </org.eclipse.epf.uma:MethodPlugin>
+</xmi:XMI>
diff --git a/praclib/temp/publish.openup.base/resources/about.htm b/praclib/temp/publish.openup.base/resources/about.htm
new file mode 100644
index 0000000..ea50579
--- /dev/null
+++ b/praclib/temp/publish.openup.base/resources/about.htm
@@ -0,0 +1,62 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+
+
+<html>
+<head>
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
+ <title>About</title>
+<script src="scripts/common.js" type="text/javascript" language="JavaScript"></script>
+ <style type="text/css">
+ body {
+ margin: 8px;
+ }
+ </style>
+</head>
+
+<body>
+
+ <img src="./images/icon_about.gif" width="32" height="32" alt="about icon" border="0"/><br /><br />
+<span class="pop">OpenUP<br />
+Version 1.0<br />
+<br />
+(c) Copyright Eclipse contributors and others 2004, 2007.<br />
+All Rights Reserved.</span><br /><br />
+ <table summary="" border="0" cellspacing="0" cellpadding="0">
+ <tr>
+ <td><img src="./images/shim.gif" alt="" width="1" height="1" /></td>
+ <td class="buttonbody" colspan="2"><img src="./images/shim.gif" alt="" width="1" height="1" /></td>
+ <td colspan="2"><img src="./images/shim.gif" alt="" width="1" height="1" /></td>
+ </tr>
+ <tr>
+ <td class="buttonbody" colspan="4" rowspan="2"><img src="./images/shim.gif" alt="" width="1" height="1" /></td>
+ <td><img src="./images/shim.gif" alt="" width="1" height="1" /></td>
+ </tr>
+ <tr>
+ <td class="buttonshadow"><img src="./images/shim.gif" alt="" width="1" height="1" /></td>
+ </tr>
+ <tr>
+ <td class="buttonbody" colspan="2" rowspan="2"><img src="./images/shim.gif" alt="" width="1" height="1" /></td>
+ <td class="buttonbody"><a class="button" href="javascript:self.close();"><span class="buttontxt"> Close </span></a></td>
+ <td class="buttonbody" rowspan="2"><img src="./images/shim.gif" alt="" width="1" height="1" /></td>
+ <td class="buttonshadow" rowspan="2"><img src="./images/shim.gif" alt="" width="1" height="1" /></td>
+ </tr>
+ <tr>
+ <td class="buttonbody"><img src="./images/shim.gif" alt="" width="1" height="1" /></td>
+ </tr>
+ <tr>
+ <td><img src="./images/shim.gif" alt="" width="1" height="1" /></td>
+ <td class="buttonbody"><img src="./images/shim.gif" alt="" width="1" height="1" /></td>
+ <td class="buttonbody"><img src="./images/shim.gif" alt="" width="1" height="1" /></td>
+ <td class="buttonshadow"><img src="./images/shim.gif" alt="" width="1" height="1" /></td>
+ <td><img src="./images/shim.gif" alt="" width="1" height="1" /></td>
+ </tr>
+ <tr>
+ <td colspan="2"><img src="./images/shim.gif" alt="" width="1" height="1" /></td>
+ <td class="buttonshadow"><img src="./images/shim.gif" alt="" width="1" height="1" /></td>
+ <td colspan="2"><img src="./images/shim.gif" alt="" width="1" height="1" /></td>
+ </tr>
+ </table>
+
+</body>
+</html>
diff --git a/praclib/temp/publish.openup.base/resources/openup_banner.jpg b/praclib/temp/publish.openup.base/resources/openup_banner.jpg
new file mode 100644
index 0000000..3d58181
--- /dev/null
+++ b/praclib/temp/publish.openup.base/resources/openup_banner.jpg
Binary files differ
