*** empty log message ***
diff --git a/epf_prac_151/practice.gen.doc_trng.base/guidances/roadmaps/how_to_adopt_doc_training.xmi b/epf_prac_151/practice.gen.doc_trng.base/guidances/roadmaps/how_to_adopt_doc_training.xmi
index ff71623..d8cc997 100644
--- a/epf_prac_151/practice.gen.doc_trng.base/guidances/roadmaps/how_to_adopt_doc_training.xmi
+++ b/epf_prac_151/practice.gen.doc_trng.base/guidances/roadmaps/how_to_adopt_doc_training.xmi
@@ -1,7 +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.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="--dByCrR1PiKA-JrdNIjebw" name="how_to_adopt_doc_training,_2OLFEKBGEeCRzIAAKeJxvA" guid="--dByCrR1PiKA-JrdNIjebw" changeDate="2011-07-30T13:25:06.810-0700" version="7.2.0">
+<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="--dByCrR1PiKA-JrdNIjebw" name="how_to_adopt_doc_training,_2OLFEKBGEeCRzIAAKeJxvA" guid="--dByCrR1PiKA-JrdNIjebw" changeDate="2011-07-30T13:25:06.810-0700" version="7.2.0">
<mainDescription><h3>
- Getting started
+ Getting started with this practice
</h3>
<p>
The goal of the Documentation and Training practice is to ensure that end users of a product receive quality
diff --git a/epf_prac_151/practice.gen.doc_trng.base/tasks/develop_product_documentation.xmi b/epf_prac_151/practice.gen.doc_trng.base/tasks/develop_product_documentation.xmi
index 191760a..f1b93f7 100644
--- a/epf_prac_151/practice.gen.doc_trng.base/tasks/develop_product_documentation.xmi
+++ b/epf_prac_151/practice.gen.doc_trng.base/tasks/develop_product_documentation.xmi
@@ -1,5 +1,5 @@
<?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.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-Msu85VH5rLUfl0OEAnZdIQ" name="01_create_update_product_documenation,_t15g4DHMEeC7j_IRiP-WPQ" guid="-Msu85VH5rLUfl0OEAnZdIQ" changeDate="2012-05-30T13:03:23.148-0700" version="7.5.1">
+<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.6/uma.ecore" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-Msu85VH5rLUfl0OEAnZdIQ" name="01_create_update_product_documenation,_t15g4DHMEeC7j_IRiP-WPQ" guid="-Msu85VH5rLUfl0OEAnZdIQ" changeDate="2012-05-30T13:03:23.148-0700" version="7.5.1">
<mainDescription><p>
Development team members sometimes take documentation for granted, or do not give it enough consideration. However,
after a product is delivered, customers who pay for the system and for support often do not have enough information to
@@ -17,7 +17,15 @@
detailed, and comprehensive product documentation.
</p></mainDescription>
<sections xmi:id="_-zf1suB8EeC1y_NExchKwQ" name="Identify features of current release" guid="_-zf1suB8EeC1y_NExchKwQ">
- <sectionDescription><p>%EOL% Every release will contain a set of features that were developed during the preceding feature development sprint or%EOL% iterations. This list should drive the table of contents of the product documentation. It also is possible that some%EOL% nonfunctional requirements should be documented as well.%EOL%</p>%EOL%<p>%EOL% While the product documentation will not be used directly as user documentation, it will become the basis for the user%EOL% documentation. That foundation of information is why this step is important.%EOL%</p></sectionDescription>
+ <sectionDescription><p>
+ %EOL% Every release will contain a set of features that were developed during the preceding feature development sprint
+ or%EOL% iterations. This list should drive the table of contents of the product documentation. It also is possible that
+ some%EOL% nonfunctional requirements should be documented as well.%EOL%
+</p>%EOL%
+<p>
+ %EOL% While the product documentation will not be used directly as user documentation, it will become the basis for the
+ user%EOL% documentation. That foundation of information is why this step is important.%EOL%
+</p></sectionDescription>
</sections>
<sections xmi:id="_-zf1seB8EeC1y_NExchKwQ" name="Document each feature" guid="_-zf1seB8EeC1y_NExchKwQ">
<sectionDescription>Write a comprehensive description of each feature and include appropriate screen shots as well as relevant information
diff --git a/epf_prac_151/practice.gen.doc_trng.base/tasks/develop_support_documentation.xmi b/epf_prac_151/practice.gen.doc_trng.base/tasks/develop_support_documentation.xmi
index f45e511..23035dd 100644
--- a/epf_prac_151/practice.gen.doc_trng.base/tasks/develop_support_documentation.xmi
+++ b/epf_prac_151/practice.gen.doc_trng.base/tasks/develop_support_documentation.xmi
@@ -1,5 +1,5 @@
<?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.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-jWMpCvzhJPOglJcxCiAYjA" name="03_create_update_support_documenation,_nGAhcDHMEeC7j_IRiP-WPQ" guid="-jWMpCvzhJPOglJcxCiAYjA" changeDate="2012-05-30T13:11:48.626-0700" version="7.5.1">
+<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.6/uma.ecore" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-jWMpCvzhJPOglJcxCiAYjA" name="03_create_update_support_documenation,_nGAhcDHMEeC7j_IRiP-WPQ" guid="-jWMpCvzhJPOglJcxCiAYjA" changeDate="2012-05-30T13:11:48.626-0700" version="7.5.1">
<mainDescription><p>
Support documentation often is the most overlooked aspect of a documentation effort. Anyone who has had the opportunity
to provide end user support for a particular application can appreciate how important effective, well-written support
@@ -75,10 +75,14 @@
</ul></sectionDescription>
</sections>
<sections xmi:id="_-zfOqeB8EeC1y_NExchKwQ" name="Write support documentation" guid="_-zfOqeB8EeC1y_NExchKwQ">
- <sectionDescription>Based on the previous steps, write the support documentation. One way to do this is to assign sections of the document%EOL%(determined in the step "Determine Support Documentation Contents" above) to development team members as sprint/iteration%EOL%tasks in the release sprint/iteration.</sectionDescription>
+ <sectionDescription>Based on the previous steps, write the support documentation. One way to do this is to assign sections of the
+document%EOL%(determined in the step "Determine Support Documentation Contents" above) to development team members as
+sprint/iteration%EOL%tasks in the release sprint/iteration.</sectionDescription>
</sections>
<sections xmi:id="_-zfOrOB8EeC1y_NExchKwQ" name="Perform quality review" guid="_-zfOrOB8EeC1y_NExchKwQ">
- <sectionDescription>As the support documentation is integrated, plan and conduct a quality review during the release sprint/iteration to ensure%EOL%that the documentation is of sufficient quantity and quality. Update and improve the support documentation based on the%EOL%results of the quality review.</sectionDescription>
+ <sectionDescription>As the support documentation is integrated, plan and conduct a quality review during the release sprint/iteration to
+ensure%EOL%that the documentation is of sufficient quantity and quality. Update and improve the support documentation based
+on the%EOL%results of the quality review.</sectionDescription>
</sections>
<sections xmi:id="_-zfOqOB8EeC1y_NExchKwQ" name="Deliver support documentation" guid="_-zfOqOB8EeC1y_NExchKwQ">
<sectionDescription>At the end of a release, deliver the completed support documentation to the deployment manager. Ensure that the program has
diff --git a/epf_prac_151/practice.gen.doc_trng.base/tasks/develop_training_materials.xmi b/epf_prac_151/practice.gen.doc_trng.base/tasks/develop_training_materials.xmi
index 84ca0fb..26407d2 100644
--- a/epf_prac_151/practice.gen.doc_trng.base/tasks/develop_training_materials.xmi
+++ b/epf_prac_151/practice.gen.doc_trng.base/tasks/develop_training_materials.xmi
@@ -1,5 +1,5 @@
<?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.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-IfcWgUklth25pRzdNTE8LA" name="create_update_training_materials,_yJRakDHMEeC7j_IRiP-WPQ" guid="-IfcWgUklth25pRzdNTE8LA" changeDate="2012-05-30T14:02:19.664-0700" version="7.5.1">
+<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.6/uma.ecore" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-IfcWgUklth25pRzdNTE8LA" name="create_update_training_materials,_yJRakDHMEeC7j_IRiP-WPQ" guid="-IfcWgUklth25pRzdNTE8LA" changeDate="2012-05-30T14:02:19.664-0700" version="7.5.1">
<mainDescription><p>
Having the correct amount and type of materials available to adequately train end users and supporters of an
application is necessary to promote usability and to achieve the desired business value. If a course ceveloper is
@@ -14,7 +14,59 @@
immediately before a scheduled release.
</p></mainDescription>
<sections xmi:id="_-zennOB8EeC1y_NExchKwQ" name="Determine scope of training materials" guid="_-zennOB8EeC1y_NExchKwQ">
- <sectionDescription><p>%EOL% Consult the program manager and deployment manager to determine the extent of training materials required for this%EOL% release. Depending on the contents of the release, more or fewer training materials might be needed to support both end%EOL% users and IT operations support personnel.%EOL%</p>%EOL%<p>%EOL% Training materials generally consist of a combination of:%EOL%</p>%EOL%<ul>%EOL% <li>%EOL% Presentation slides%EOL% </li>%EOL% <li>%EOL% Handouts%EOL% </li>%EOL% <li>%EOL% Training aids%EOL% </li>%EOL% <li>%EOL% Hands-on labs and/or exercises%EOL% </li>%EOL% <li>%EOL% Quizzes or tests%EOL% </li>%EOL% <li>%EOL% Practical application workshops%EOL% </li>%EOL%</ul>%EOL%<p>%EOL% Training materials often are grouped into modules, each with a set of learning objectives and competency assessments.%EOL%</p></sectionDescription>
+ <sectionDescription><p>
+ %EOL% Consult the program manager and deployment manager to determine the extent of training materials required for
+ this%EOL% release. Depending on the contents of the release, more or fewer training materials might be needed to
+ support both end%EOL% users and IT operations support personnel.%EOL%
+</p>%EOL%
+<p>
+ %EOL% Training materials generally consist of a combination of:%EOL%
+</p>%EOL%
+<ul>
+ <li style="list-style: none">
+ %EOL%
+ </li>
+ <li>
+ %EOL% Presentation slides%EOL%
+ </li>
+ <li style="list-style: none">
+ %EOL%
+ </li>
+ <li>
+ %EOL% Handouts%EOL%
+ </li>
+ <li style="list-style: none">
+ %EOL%
+ </li>
+ <li>
+ %EOL% Training aids%EOL%
+ </li>
+ <li style="list-style: none">
+ %EOL%
+ </li>
+ <li>
+ %EOL% Hands-on labs and/or exercises%EOL%
+ </li>
+ <li style="list-style: none">
+ %EOL%
+ </li>
+ <li>
+ %EOL% Quizzes or tests%EOL%
+ </li>
+ <li style="list-style: none">
+ %EOL%
+ </li>
+ <li>
+ %EOL% Practical application workshops%EOL%
+ </li>
+ <li style="list-style: none">
+ %EOL%
+ </li>
+</ul>%EOL%
+<p>
+ %EOL% Training materials often are grouped into modules, each with a set of learning objectives and competency
+ assessments.%EOL%
+</p></sectionDescription>
</sections>
<sections xmi:id="_-zenm-B8EeC1y_NExchKwQ" name="Develop user training materials" guid="_-zenm-B8EeC1y_NExchKwQ">
<sectionDescription><p>
@@ -29,13 +81,27 @@
</p></sectionDescription>
</sections>
<sections xmi:id="_-zenmuB8EeC1y_NExchKwQ" name="Develop support training materials" guid="_-zenmuB8EeC1y_NExchKwQ">
- <sectionDescription><p>%EOL% In many cases, IT support personnel are experienced enough to require minimal training on a product release. However,%EOL% where the product is new to the support organization, or the support personnel themselves are inexperienced or%EOL% unfamiliar with a particular technology, support training becomes very important to the success of the product rollout.%EOL%</p>%EOL%<p>%EOL% Using the support documentation as a guideline, identify the parts of the product on which IT support personnel will%EOL% need to be trained. Identify training modules and document learning objectives for each module, then leverage as much%EOL% of the support documentation content as you can to create your training materials.%EOL%</p></sectionDescription>
+ <sectionDescription><p>
+ %EOL% In many cases, IT support personnel are experienced enough to require minimal training on a product release.
+ However,%EOL% where the product is new to the support organization, or the support personnel themselves are
+ inexperienced or%EOL% unfamiliar with a particular technology, support training becomes very important to the success
+ of the product rollout.%EOL%
+</p>%EOL%
+<p>
+ %EOL% Using the support documentation as a guideline, identify the parts of the product on which IT support personnel
+ will%EOL% need to be trained. Identify training modules and document learning objectives for each module, then leverage
+ as much%EOL% of the support documentation content as you can to create your training materials.%EOL%
+</p></sectionDescription>
</sections>
<sections xmi:id="_-zenn-B8EeC1y_NExchKwQ" name="Perform quality review" guid="_-zenn-B8EeC1y_NExchKwQ">
- <sectionDescription>As user and support training materials are developed, plan and conduct a quality review during the release sprint/iteration%EOL%to ensure that the materials are of sufficient quantity and quality. Update and improve the training materials based on the%EOL%results of the quality review.</sectionDescription>
+ <sectionDescription>As user and support training materials are developed, plan and conduct a quality review during the release
+sprint/iteration%EOL%to ensure that the materials are of sufficient quantity and quality. Update and improve the training
+materials based on the%EOL%results of the quality review.</sectionDescription>
</sections>
<sections xmi:id="_-zennuB8EeC1y_NExchKwQ" name="Perform dry run" guid="_-zennuB8EeC1y_NExchKwQ">
- <sectionDescription>Before formally delivering the user or support training, plan a sprint/iteration task in which representatives of both the%EOL%user and support communities are invited to participate in a dry run of the training materials. Use the feedback obtained%EOL%from these sessions to improve the training materials during the release sprint/iteration.</sectionDescription>
+ <sectionDescription>Before formally delivering the user or support training, plan a sprint/iteration task in which representatives of both
+the%EOL%user and support communities are invited to participate in a dry run of the training materials. Use the feedback
+obtained%EOL%from these sessions to improve the training materials during the release sprint/iteration.</sectionDescription>
</sections>
<sections xmi:id="_-zenneB8EeC1y_NExchKwQ" name="Deliver training materials" guid="_-zenneB8EeC1y_NExchKwQ">
<sectionDescription>When the final user and support training materials are complete, deliver them to the deployment manager for integration
diff --git a/epf_prac_151/practice.gen.doc_trng.base/tasks/develop_user_documentation.xmi b/epf_prac_151/practice.gen.doc_trng.base/tasks/develop_user_documentation.xmi
index cb170b3..40b2fd0 100644
--- a/epf_prac_151/practice.gen.doc_trng.base/tasks/develop_user_documentation.xmi
+++ b/epf_prac_151/practice.gen.doc_trng.base/tasks/develop_user_documentation.xmi
@@ -1,5 +1,5 @@
<?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.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-bkoNpaQhWX6FBG-iOZkRPg" name="create_update_user_documenation,_gMmZoDHMEeC7j_IRiP-WPQ" guid="-bkoNpaQhWX6FBG-iOZkRPg" changeDate="2011-09-12T08:48:05.139-0700" version="7.5.1">
+<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.6/uma.ecore" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-bkoNpaQhWX6FBG-iOZkRPg" name="create_update_user_documenation,_gMmZoDHMEeC7j_IRiP-WPQ" guid="-bkoNpaQhWX6FBG-iOZkRPg" changeDate="2011-09-12T08:48:05.139-0700" version="7.5.1">
<mainDescription><p>
User documentation might include all or parts of user manuals (electronic or paper-based), tutorials, frequently asked
questions (FAQs), on-line Help Files, installation instructions, operational procedures, etc. User documentation often
@@ -11,7 +11,54 @@
User's expectations because they will not be able operate the application effectively.
</p></mainDescription>
<sections xmi:id="_-zfOo-B8EeC1y_NExchKwQ" name="Determine user documentation contents" guid="_-zfOo-B8EeC1y_NExchKwQ">
- <sectionDescription><p>%EOL% User documentation often consists of a wide variety of content such as:%EOL%</p>%EOL%<ul>%EOL% <li>%EOL% User manuals (electronic or paper-based)%EOL% </li>%EOL% <li>%EOL% Tutorials%EOL% </li>%EOL% <li>%EOL% Frequently asked questions (FAQs)%EOL% </li>%EOL% <li>%EOL% On-line Help Files%EOL% </li>%EOL% <li>%EOL% Installation and configuration instructions%EOL% </li>%EOL% <li>%EOL% Operational procedures (or job aids)%EOL% </li>%EOL%</ul>%EOL%<p>%EOL% For your product and for this release, determine which of these types of user documentation your team will develop and%EOL% deliver.%EOL%</p></sectionDescription>
+ <sectionDescription><p>
+ %EOL% User documentation often consists of a wide variety of content such as:%EOL%
+</p>%EOL%
+<ul>
+ <li style="list-style: none">
+ %EOL%
+ </li>
+ <li>
+ %EOL% User manuals (electronic or paper-based)%EOL%
+ </li>
+ <li style="list-style: none">
+ %EOL%
+ </li>
+ <li>
+ %EOL% Tutorials%EOL%
+ </li>
+ <li style="list-style: none">
+ %EOL%
+ </li>
+ <li>
+ %EOL% Frequently asked questions (FAQs)%EOL%
+ </li>
+ <li style="list-style: none">
+ %EOL%
+ </li>
+ <li>
+ %EOL% On-line Help Files%EOL%
+ </li>
+ <li style="list-style: none">
+ %EOL%
+ </li>
+ <li>
+ %EOL% Installation and configuration instructions%EOL%
+ </li>
+ <li style="list-style: none">
+ %EOL%
+ </li>
+ <li>
+ %EOL% Operational procedures (or job aids)%EOL%
+ </li>
+ <li style="list-style: none">
+ %EOL%
+ </li>
+</ul>%EOL%
+<p>
+ %EOL% For your product and for this release, determine which of these types of user documentation your team will
+ develop and%EOL% deliver.%EOL%
+</p></sectionDescription>
</sections>
<sections xmi:id="_-zfOpeB8EeC1y_NExchKwQ" name="Leverage product documentation" guid="_-zfOpeB8EeC1y_NExchKwQ">
<sectionDescription>Re-use whatever material you can from the product documentation that your team has created. If adequate time and attention
diff --git a/epf_prac_151/practice.gen.doc_trng.base/workproducts/training_materials.xmi b/epf_prac_151/practice.gen.doc_trng.base/workproducts/training_materials.xmi
index 2500324..f8ca85f 100644
--- a/epf_prac_151/practice.gen.doc_trng.base/workproducts/training_materials.xmi
+++ b/epf_prac_151/practice.gen.doc_trng.base/workproducts/training_materials.xmi
@@ -1,7 +1,8 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-U5rK8ue_5v305MPzxKzQUg" name="training_materials,_B2vaMEVvEeC6_c5S_pc9RA" guid="-U5rK8ue_5v305MPzxKzQUg" changeDate="2012-05-30T14:04:32.231-0700" version="7.5.1">
+<org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-U5rK8ue_5v305MPzxKzQUg" name="training_materials,_B2vaMEVvEeC6_c5S_pc9RA" guid="-U5rK8ue_5v305MPzxKzQUg" changeDate="2012-05-30T14:04:32.231-0700" version="7.5.1">
<mainDescription><p>
- Training materials that can be used to train end users and production support personnel might consist of:
+ Training materials that can be used to train end users and production support personnel might be of the following
+ types:
</p>
<ul>
<li>
diff --git a/epf_prac_151/practice.gen.production_release.base/guidances/checklists/deployment_plan.xmi b/epf_prac_151/practice.gen.production_release.base/guidances/checklists/deployment_plan.xmi
index 5d88fca..31475c7 100644
--- a/epf_prac_151/practice.gen.production_release.base/guidances/checklists/deployment_plan.xmi
+++ b/epf_prac_151/practice.gen.production_release.base/guidances/checklists/deployment_plan.xmi
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-x6K6zdVklh4CbhxTeVvYew" name="deployment_plan,_LXE_8LlKEeCciPPzZcIJFA" guid="-x6K6zdVklh4CbhxTeVvYew" changeDate="2011-07-28T11:52:30.549-0700" version="7.5.1">
+<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-x6K6zdVklh4CbhxTeVvYew" name="deployment_plan,_LXE_8LlKEeCciPPzZcIJFA" guid="-x6K6zdVklh4CbhxTeVvYew" changeDate="2011-07-28T11:52:30.549-0700" version="7.5.1">
<mainDescription>By answering a set of generic questions (who, what, when, where, why, and how), deployment planning can go a long way to
make a release a satisfying experience. Some questions to be considered are indicated by the check items below:</mainDescription>
<sections xmi:id="_IAHg0uB-EeC1y_NExchKwQ" name="Who are the end users of the features to be released?" guid="_IAHg0uB-EeC1y_NExchKwQ">
@@ -12,7 +12,7 @@
<sections xmi:id="_IAHg1OB-EeC1y_NExchKwQ" name="When do the features need to be available?" guid="_IAHg1OB-EeC1y_NExchKwQ">
<sectionDescription>When must the deployment be completed and tested?</sectionDescription>
</sections>
- <sections xmi:id="_IAG5wuB-EeC1y_NExchKwQ" name="Where are the end users located? " guid="_IAG5wuB-EeC1y_NExchKwQ">
+ <sections xmi:id="_IAG5wuB-EeC1y_NExchKwQ" name="Where are the end users located?" guid="_IAG5wuB-EeC1y_NExchKwQ">
<sectionDescription>Are end users distributed or in one location, and are their infrastructure configurations the same or different? <br /></sectionDescription>
</sections>
<sections xmi:id="_IAHg0OB-EeC1y_NExchKwQ" name="Why is the release taking place?" guid="_IAHg0OB-EeC1y_NExchKwQ">
diff --git a/epf_prac_151/practice.gen.production_release.base/guidances/roadmaps/how_to_adopt_production_release.xmi b/epf_prac_151/practice.gen.production_release.base/guidances/roadmaps/how_to_adopt_production_release.xmi
index 8e9afaf..0a90288 100644
--- a/epf_prac_151/practice.gen.production_release.base/guidances/roadmaps/how_to_adopt_production_release.xmi
+++ b/epf_prac_151/practice.gen.production_release.base/guidances/roadmaps/how_to_adopt_production_release.xmi
@@ -1,7 +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.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-DKbcEDMwu7S4GWFkH-TTkg" name="how_to_adopt_production_release,_IADPYeB-EeC1y_NExchKwQ" guid="-DKbcEDMwu7S4GWFkH-TTkg" changeDate="2011-10-13T06:52:57.041-0700" version="7.2.0">
+<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-DKbcEDMwu7S4GWFkH-TTkg" name="how_to_adopt_production_release,_IADPYeB-EeC1y_NExchKwQ" guid="-DKbcEDMwu7S4GWFkH-TTkg" changeDate="2011-10-13T06:52:57.041-0700" version="7.2.0">
<mainDescription><h3>
- Getting started
+ Getting started with this practice
</h3>
<p>
The goal of the Production Release practice is to transform the business value developed in Feature Development
@@ -13,9 +13,9 @@
Sprint/Iteration is to consider a past project in which your team spent a week of 16-hour days doing all the things
necessary to prepare for a deployment based on an arbitrary release date. Then realize that you do not have to operate
like that any more, and that a Production Release Sprint/Iteration is your opportunity to calmly deal with all the
- preparatory activities that accompany a well-managed, coordinated release while other development team members are doing the
- same. In short, the Production Release practice represents the way you always wished you could prepare for a release
- but did not have the opportunity.
+ preparatory activities that accompany a well-managed, coordinated release while other development team members are
+ doing the same. In short, the Production Release practice represents the way you always wished you could prepare for a
+ release but did not have the opportunity.
</p>
<h3>
Common pitfalls
@@ -26,10 +26,10 @@
</p>
<ul>
<li>
- <strong>A Release Sprint/Iteration is not a time to rest:</strong> Some development team members think that when they get
- to Production Release they can relax and not work too hard. However, when practicing the Agile value of Sustainable
- Pace, teams should <em>not need to</em> rest, and team members should maintain the tempo that they established
- during previous Feature Development Sprint/Iterations.
+ <strong>A Release Sprint/Iteration is not a time to rest:</strong> Some development team members think that when
+ they get to Production Release they can relax and not work too hard. However, when practicing the Agile value of
+ Sustainable Pace, teams should <em>not need to</em> rest, and team members should maintain the tempo that they
+ established during previous Feature Development Sprint/Iterations.
</li>
<li>
<strong>Testing is not more important than documentation and training:</strong> While the various types of testing
diff --git a/epf_prac_151/practice.gen.production_release.base/tasks/develop_backout_plan.xmi b/epf_prac_151/practice.gen.production_release.base/tasks/develop_backout_plan.xmi
index 18581cb..7f65817 100644
--- a/epf_prac_151/practice.gen.production_release.base/tasks/develop_backout_plan.xmi
+++ b/epf_prac_151/practice.gen.production_release.base/tasks/develop_backout_plan.xmi
@@ -1,14 +1,19 @@
<?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.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-Z_sfrl6NWP_8GKlFeHrrgg" name="04_create_update_backout_plan,_2F7n8DHNEeC7j_IRiP-WPQ" guid="-Z_sfrl6NWP_8GKlFeHrrgg" changeDate="2011-07-28T12:18:22.207-0700" version="7.5.1">
+<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.6/uma.ecore" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-Z_sfrl6NWP_8GKlFeHrrgg" name="04_create_update_backout_plan,_2F7n8DHNEeC7j_IRiP-WPQ" guid="-Z_sfrl6NWP_8GKlFeHrrgg" changeDate="2011-07-28T12:18:22.207-0700" version="7.5.1">
<mainDescription>A rollback might be needed for a variety of reasons, including corruption of the production code base, inoperable
components, an unplanned undesirable effect of the release on other production systems, an unhappy customer, etc.
The&nbsp;Development team should provide the production support organization with a specific plan and decision criteria
made available to them to avoid or minimize service interruptions.</mainDescription>
<sections xmi:id="_IAIu9eB-EeC1y_NExchKwQ" name="Determine if backout plan exists" guid="_IAIu9eB-EeC1y_NExchKwQ">
- <sectionDescription>Determine whether the development team has a backout plan already written for a previous release. If so, part of that plan%EOL%might be reusable. If this release is the development team%sq%s first, another development team with a similar feature set%EOL%might have a plan that can be used as a starting point.</sectionDescription>
+ <sectionDescription>Determine whether the development team has a backout plan already written for a previous release. If so, part of that
+plan%EOL%might be reusable. If this release is the development team%sq%s first, another development team with a similar
+feature set%EOL%might have a plan that can be used as a starting point.</sectionDescription>
</sections>
<sections xmi:id="_IAIu8-B-EeC1y_NExchKwQ" name="Develop the backout plan (if applicable)" guid="_IAIu8-B-EeC1y_NExchKwQ">
- <sectionDescription>If a backout plan does not exist, or one cannot be found to be used as a starting point, answer the questions documented in%EOL%the <a class="elementLinkWithType" href="./../../practice.gen.production_release.base/workproducts/backout_plan_DC0D7247.html" guid="_IAHg2eB-EeC1y_NExchKwQ">Artifact: Backout Plan</a> to start and develop a backout plan.</sectionDescription>
+ <sectionDescription>If a backout plan does not exist, or one cannot be found to be used as a starting point, answer the questions documented
+in%EOL%the <a class="elementLinkWithType"
+href="./../../practice.gen.production_release.base/workproducts/backout_plan_DC0D7247.html"
+guid="_IAHg2eB-EeC1y_NExchKwQ">Artifact: Backout Plan</a> to start and develop a backout plan.</sectionDescription>
</sections>
<sections xmi:id="_IAIu9OB-EeC1y_NExchKwQ" name="Update the backout plan (if applicable)" guid="_IAIu9OB-EeC1y_NExchKwQ">
<sectionDescription>If a backout plan does exist that can be used as a baseline, review that plan and update, add, or delete information as
diff --git a/epf_prac_151/practice.gen.production_release.base/tasks/execute_backout_plan.xmi b/epf_prac_151/practice.gen.production_release.base/tasks/execute_backout_plan.xmi
index 1b1589b..919bafa 100644
--- a/epf_prac_151/practice.gen.production_release.base/tasks/execute_backout_plan.xmi
+++ b/epf_prac_151/practice.gen.production_release.base/tasks/execute_backout_plan.xmi
@@ -1,5 +1,5 @@
<?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.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-mHGd7nm4EywKy0UPe9dZhg" name="02_04_execute_backout_plan,_FCK_gGzvEeCPgecPbK9bdg" guid="-mHGd7nm4EywKy0UPe9dZhg" changeDate="2012-05-30T14:08:13.096-0700" version="7.5.1">
+<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.6/uma.ecore" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-mHGd7nm4EywKy0UPe9dZhg" name="02_04_execute_backout_plan,_FCK_gGzvEeCPgecPbK9bdg" guid="-mHGd7nm4EywKy0UPe9dZhg" changeDate="2012-05-30T14:08:13.096-0700" version="7.5.1">
<mainDescription>Assuming a backout plan is available for this release, the deployment engineer (or development team) will follow the
instructions for reversing the installation of the product into production, if there is a problem. While the plan might
have been written with good intentions, sometimes key procedures are missing or have not been thought out. The team backing
@@ -7,13 +7,27 @@
consider the unique circumstances within which the deployment has failed and rely on common sense and experience when
executing the backout plan.</mainDescription>
<sections xmi:id="_IAD2c-B-EeC1y_NExchKwQ" name="Identify release problem(s)" guid="_IAD2c-B-EeC1y_NExchKwQ">
- <sectionDescription><p>%EOL% In the event that the release to production experiences problems, either during or after deployment, the backout plan%EOL% should be invoked. However, the deployment engineer (or development team) must understand where the release went wrong%EOL% so that the code can be fixed before the next release attempt. This is a critical step, but it should be done quickly%EOL% so that the problematic release can be reversed before significant damage is done to the production environment.%EOL%</p>%EOL%<p>%EOL% Log the issues as critical defects as soon as possible and assign those defects to the appropriate team members for%EOL% resolution.%EOL%</p></sectionDescription>
+ <sectionDescription><p>
+ %EOL% In the event that the release to production experiences problems, either during or after deployment, the backout
+ plan%EOL% should be invoked. However, the deployment engineer (or development team) must understand where the release
+ went wrong%EOL% so that the code can be fixed before the next release attempt. This is a critical step, but it should
+ be done quickly%EOL% so that the problematic release can be reversed before significant damage is done to the
+ production environment.%EOL%
+</p>%EOL%
+<p>
+ %EOL% Log the issues as critical defects as soon as possible and assign those defects to the appropriate team members
+ for%EOL% resolution.%EOL%
+</p></sectionDescription>
</sections>
<sections xmi:id="_IAD2cOB-EeC1y_NExchKwQ" name="Backout the release" guid="_IAD2cOB-EeC1y_NExchKwQ">
- <sectionDescription>Following the instructions in the backout plan, reverse the deployment. However, be aware that the backout plan%EOL%instructions are a guide and should not always be taken literally. This interpretation is due to the fact that not every%EOL%problematic condition can be documented in advance and because each real-world situation might be slightly different.</sectionDescription>
+ <sectionDescription>Following the instructions in the backout plan, reverse the deployment. However, be aware that the backout
+plan%EOL%instructions are a guide and should not always be taken literally. This interpretation is due to the fact that not
+every%EOL%problematic condition can be documented in advance and because each real-world situation might be slightly
+different.</sectionDescription>
</sections>
<sections xmi:id="_IAD2cuB-EeC1y_NExchKwQ" name="Determine if the backout was successful" guid="_IAD2cuB-EeC1y_NExchKwQ">
- <sectionDescription>Ascertain whether the reversal was successful. If not, key members of the release team, development team, or program level%EOL%agile system team might need to be engaged to find and fix the problem(s).</sectionDescription>
+ <sectionDescription>Ascertain whether the reversal was successful. If not, key members of the release team, development team, or program
+level%EOL%agile system team might need to be engaged to find and fix the problem(s).</sectionDescription>
</sections>
<sections xmi:id="_IAD2ceB-EeC1y_NExchKwQ" name="Communicate the backout" guid="_IAD2ceB-EeC1y_NExchKwQ">
<sectionDescription>Ensure that all interested parties are aware of the failed release. Because releases often take place at odd hours to
diff --git a/epf_prac_151/practice.gen.production_release.base/tasks/execute_deployment_plan.xmi b/epf_prac_151/practice.gen.production_release.base/tasks/execute_deployment_plan.xmi
index fec1c8d..1f6479c 100644
--- a/epf_prac_151/practice.gen.production_release.base/tasks/execute_deployment_plan.xmi
+++ b/epf_prac_151/practice.gen.production_release.base/tasks/execute_deployment_plan.xmi
@@ -1,5 +1,5 @@
<?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.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-PPEUOk6Gija0ckrWlDdCxA" name="02_02_execute_deployment_plan,_FCK_gWzvEeCPgecPbK9bdg" guid="-PPEUOk6Gija0ckrWlDdCxA" changeDate="2012-05-30T14:11:35.736-0700" version="7.5.1">
+<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.6/uma.ecore" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-PPEUOk6Gija0ckrWlDdCxA" name="02_02_execute_deployment_plan,_FCK_gWzvEeCPgecPbK9bdg" guid="-PPEUOk6Gija0ckrWlDdCxA" changeDate="2012-05-30T14:11:35.736-0700" version="7.5.1">
<mainDescription><p>
This task is straightforward: follow the procedures in the Deployment Plan for the rollout of a specific product
release. If the deployment plan does not exist or it is poorly constructed, this task might be much more difficult.
@@ -12,7 +12,9 @@
plan's contents.
</p></mainDescription>
<sections xmi:id="_IAD2deB-EeC1y_NExchKwQ" name="Review deployment plan" guid="_IAD2deB-EeC1y_NExchKwQ">
- <sectionDescription>Review the contents of the deployment plan to ensure that the production environment has all the dependent components%EOL%installed and that the system is in the correct state. Also ensure that the release window is ready to be achieved.</sectionDescription>
+ <sectionDescription>Review the contents of the deployment plan to ensure that the production environment has all the dependent
+components%EOL%installed and that the system is in the correct state. Also ensure that the release window is ready to be
+achieved.</sectionDescription>
</sections>
<sections xmi:id="_IAD2duB-EeC1y_NExchKwQ" name="Release code" guid="_IAD2duB-EeC1y_NExchKwQ">
<sectionDescription><p>
diff --git a/epf_prac_151/practice.gen.production_release.base/tasks/package_the_release.xmi b/epf_prac_151/practice.gen.production_release.base/tasks/package_the_release.xmi
index a99aa4e..71564c1 100644
--- a/epf_prac_151/practice.gen.production_release.base/tasks/package_the_release.xmi
+++ b/epf_prac_151/practice.gen.production_release.base/tasks/package_the_release.xmi
@@ -1,5 +1,5 @@
<?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.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-fBwPDexzVTCxcEM5H1ljeQ" name="02_01_package_the_release,_DQowcWzvEeCPgecPbK9bdg" guid="-fBwPDexzVTCxcEM5H1ljeQ" changeDate="2012-05-30T14:12:33.929-0700" version="7.5.1">
+<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.6/uma.ecore" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-fBwPDexzVTCxcEM5H1ljeQ" name="02_01_package_the_release,_DQowcWzvEeCPgecPbK9bdg" guid="-fBwPDexzVTCxcEM5H1ljeQ" changeDate="2012-05-30T14:12:33.929-0700" version="7.5.1">
<mainDescription><p>
The key activities normally used to package a release:
</p>
@@ -38,7 +38,10 @@
</li>
</ul></mainDescription>
<sections xmi:id="_IAEdheB-EeC1y_NExchKwQ" name="Assemble components" guid="_IAEdheB-EeC1y_NExchKwQ">
- <sectionDescription>Question all the developers on the development team to determine which components are ready for packaging. Only package%EOL%those components that were completed and accepted during the previous feature development sprint/iterations. Components%EOL%that were not finished or not accepted should not be bundled, unless the customer has granted an exception or they are%EOL%infrastructure-related components.</sectionDescription>
+ <sectionDescription>Question all the developers on the development team to determine which components are ready for packaging. Only
+package%EOL%those components that were completed and accepted during the previous feature development sprint/iterations.
+Components%EOL%that were not finished or not accepted should not be bundled, unless the customer has granted an exception
+or they are%EOL%infrastructure-related components.</sectionDescription>
</sections>
<sections xmi:id="_IAEdguB-EeC1y_NExchKwQ" name="Test the release" guid="_IAEdguB-EeC1y_NExchKwQ">
<sectionDescription>After the components have been packaged and built, that executable should be installed and run in a test environment that
@@ -50,7 +53,8 @@
package can be reconstructed at a later date, if needed. This tag is known as the release "baseline."</sectionDescription>
</sections>
<sections xmi:id="_IAEdg-B-EeC1y_NExchKwQ" name="Package release documentation" guid="_IAEdg-B-EeC1y_NExchKwQ">
- <sectionDescription>Gather all the product, user, and support documentation developed earlier in the production release sprint/iteration and%EOL%add it to the release package.</sectionDescription>
+ <sectionDescription>Gather all the product, user, and support documentation developed earlier in the production release sprint/iteration
+and%EOL%add it to the release package.</sectionDescription>
</sections>
<sections xmi:id="_IAEdgeB-EeC1y_NExchKwQ" name="Deliver release package" guid="_IAEdgeB-EeC1y_NExchKwQ">
<sectionDescription>When the entire release package, including documentation, is ready, deliver it to the deployment manager and the release
diff --git a/epf_prac_151/practice.gen.production_release.base/tasks/plan_deployment.xmi b/epf_prac_151/practice.gen.production_release.base/tasks/plan_deployment.xmi
index 05b5e6e..611a2ed 100644
--- a/epf_prac_151/practice.gen.production_release.base/tasks/plan_deployment.xmi
+++ b/epf_prac_151/practice.gen.production_release.base/tasks/plan_deployment.xmi
@@ -1,5 +1,5 @@
<?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.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-QqCVewwu8buOCXKRukpf5g" name="03_create_update_deployment_plan,_FR0_0DHNEeC7j_IRiP-WPQ" guid="-QqCVewwu8buOCXKRukpf5g" changeDate="2012-05-30T14:20:09.505-0700" version="7.5.1">
+<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.6/uma.ecore" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-QqCVewwu8buOCXKRukpf5g" name="03_create_update_deployment_plan,_FR0_0DHNEeC7j_IRiP-WPQ" guid="-QqCVewwu8buOCXKRukpf5g" changeDate="2012-05-30T14:20:09.505-0700" version="7.5.1">
<mainDescription><p>
Because a deployment engineer is responsible for accepting the results of one or more development team members and
deploying those integrated releases into the production environment, it is important for all parties to agree on the
@@ -7,10 +7,17 @@
by the deployment engineer before and during the deployment to production of a particular release package.
</p></mainDescription>
<sections xmi:id="_IAJ9E-B-EeC1y_NExchKwQ" name="Determine if deployment plan exists" guid="_IAJ9E-B-EeC1y_NExchKwQ">
- <sectionDescription>Determine whether the development team has a deployment plan already written for a previous release. If so, part of that%EOL%plan might be reusable. If this is the development team%sq%s first release, another development team with a similar feature%EOL%set might have a plan that can be used as a starting point.</sectionDescription>
+ <sectionDescription>Determine whether the development team has a deployment plan already written for a previous release. If so, part of
+that%EOL%plan might be reusable. If this is the development team%sq%s first release, another development team with a
+similar feature%EOL%set might have a plan that can be used as a starting point.</sectionDescription>
</sections>
<sections xmi:id="_IAJ9EuB-EeC1y_NExchKwQ" name="Develop the deployment plan (if applicable)" guid="_IAJ9EuB-EeC1y_NExchKwQ">
- <sectionDescription>If a deployment plan does not exist, or one cannot be found to be used as a starting point, use the recommended format%EOL%documented in the <a class="elementLinkWithType" href="./../../practice.gen.production_release.base/workproducts/deployment_plan_121938C3.html" guid="_IAJ9FeB-EeC1y_NExchKwQ">Artifact: Deployment Plan</a> and refer to the <a class="elementLinkWithType" href="./../../practice.gen.production_release.base/guidances/checklists/deployment_plan_C4767691.html" guid="_IAG5weB-EeC1y_NExchKwQ">Checklist: Deployment Plan</a> to start and develop a deployment plan.</sectionDescription>
+ <sectionDescription>If a deployment plan does not exist, or one cannot be found to be used as a starting point, use the recommended
+format%EOL%documented in the <a class="elementLinkWithType"
+href="./../../practice.gen.production_release.base/workproducts/deployment_plan_121938C3.html"
+guid="_IAJ9FeB-EeC1y_NExchKwQ">Artifact: Deployment Plan</a> and refer to the <a class="elementLinkWithType"
+href="./../../practice.gen.production_release.base/guidances/checklists/deployment_plan_C4767691.html"
+guid="_IAG5weB-EeC1y_NExchKwQ">Checklist: Deployment Plan</a> to start and develop a deployment plan.</sectionDescription>
</sections>
<sections xmi:id="_IAJ9FOB-EeC1y_NExchKwQ" name="Update the deployment plan (if applicable)" guid="_IAJ9FOB-EeC1y_NExchKwQ">
<sectionDescription>If a deployment plan does exist that can be used as a baseline, review that plan and update, add, or delete information as
diff --git a/epf_prac_151/practice.gen.production_release.base/tasks/review_conform_to_release_controls.xmi b/epf_prac_151/practice.gen.production_release.base/tasks/review_conform_to_release_controls.xmi
index f540021..527ec3d 100644
--- a/epf_prac_151/practice.gen.production_release.base/tasks/review_conform_to_release_controls.xmi
+++ b/epf_prac_151/practice.gen.production_release.base/tasks/review_conform_to_release_controls.xmi
@@ -1,5 +1,5 @@
<?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.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-zT8t7LcbcrgIhYd_XUi6DA" name="01_review_conform_to_release_controls,_PwLDcDHMEeC7j_IRiP-WPQ" guid="-zT8t7LcbcrgIhYd_XUi6DA" changeDate="2012-05-30T14:22:34.002-0700" version="7.5.1">
+<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.6/uma.ecore" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-zT8t7LcbcrgIhYd_XUi6DA" name="01_review_conform_to_release_controls,_PwLDcDHMEeC7j_IRiP-WPQ" guid="-zT8t7LcbcrgIhYd_XUi6DA" changeDate="2012-05-30T14:22:34.002-0700" version="7.5.1">
<mainDescription><p>
Release controls describe the minimum number of requirements that a software package must adhere to before being
released into production. This is especially important if a development team is new or emerging, because they might not
@@ -8,7 +8,7 @@
protect the IT organization's ability to successfully deliver IT services to internal and external customers.
</p>
<p>
- Release controls typically consist of:
+ Release controls typically consist of the following:
</p>
<ul>
<li>
@@ -34,10 +34,13 @@
</li>
</ul></mainDescription>
<sections xmi:id="_IAJWAuB-EeC1y_NExchKwQ" name="Locate release controls" guid="_IAJWAuB-EeC1y_NExchKwQ">
- <sectionDescription>If the program%sq%s release controls are not readily available, the development team must engage the deployment manager and/or%EOL%their deployment engineers to know where to find the release controls and be able to comply with them.</sectionDescription>
+ <sectionDescription>If the program%sq%s release controls are not readily available, the development team must engage the deployment manager
+and/or%EOL%their deployment engineers to know where to find the release controls and be able to comply with them.</sectionDescription>
</sections>
<sections xmi:id="_IAJWAeB-EeC1y_NExchKwQ" name="Review release controls" guid="_IAJWAeB-EeC1y_NExchKwQ">
- <sectionDescription>The development team should thoroughly review the release controls so that it understands what is expected before a release%EOL%is accepted into the production environment. If the team has any questions or issues with the controls, team members should%EOL%communicate directly with the deployment manager or the deployment engineer to understand the issues.</sectionDescription>
+ <sectionDescription>The development team should thoroughly review the release controls so that it understands what is expected before a
+release%EOL%is accepted into the production environment. If the team has any questions or issues with the controls, team
+members should%EOL%communicate directly with the deployment manager or the deployment engineer to understand the issues.</sectionDescription>
</sections>
<sections xmi:id="_IAJWAOB-EeC1y_NExchKwQ" name="Ensure the team release conforms to the controls" guid="_IAJWAOB-EeC1y_NExchKwQ">
<sectionDescription><p>
@@ -70,7 +73,7 @@
The results of multiple feature development Sprint/Iterations not being included in the release
</li>
<li>
- Embarrassment on the part of the development team member that did not comply
+ Embarrassment on the part of the development team member that did not comply with the controls
</li>
<li>
Loss of funding for that development team
diff --git a/epf_prac_151/practice.gen.production_release.base/tasks/verify_successful_deployment.xmi b/epf_prac_151/practice.gen.production_release.base/tasks/verify_successful_deployment.xmi
index 8e11f0a..1e2aa9f 100644
--- a/epf_prac_151/practice.gen.production_release.base/tasks/verify_successful_deployment.xmi
+++ b/epf_prac_151/practice.gen.production_release.base/tasks/verify_successful_deployment.xmi
@@ -1,5 +1,5 @@
<?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.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-chKviPT1F1yq5Y_KL9ET9g" name="02_03_verify_successful_deployment,_FCK_gmzvEeCPgecPbK9bdg" guid="-chKviPT1F1yq5Y_KL9ET9g" changeDate="2012-05-30T14:15:13.081-0700" version="7.5.1">
+<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.6/uma.ecore" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-chKviPT1F1yq5Y_KL9ET9g" name="02_03_verify_successful_deployment,_FCK_gmzvEeCPgecPbK9bdg" guid="-chKviPT1F1yq5Y_KL9ET9g" changeDate="2012-05-30T14:15:13.081-0700" version="7.5.1">
<mainDescription><p>
Using the success criteria documented either in the deployment plan or in the backout plan, the deployment engineer, in
collaboration with the development team, will determine whether the rollout can be declared a success or not.
@@ -13,7 +13,8 @@
tests should be brief but revealing enough to quickly determine the validity of the deployment.</sectionDescription>
</sections>
<sections xmi:id="_IAFEk-B-EeC1y_NExchKwQ" name="Run manual tests" guid="_IAFEk-B-EeC1y_NExchKwQ">
- <sectionDescription>If the automated smoke tests are successful, run several complex manual tests to simulate key end user behavior. These%EOL%tests should be executed by development team members or stakeholders recruited specifically for this purpose.</sectionDescription>
+ <sectionDescription>If the automated smoke tests are successful, run several complex manual tests to simulate key end user behavior.
+These%EOL%tests should be executed by development team members or stakeholders recruited specifically for this purpose.</sectionDescription>
</sections>
<sections xmi:id="_IAFElOB-EeC1y_NExchKwQ" name="Determine if release should be reversed" guid="_IAFElOB-EeC1y_NExchKwQ">
<sectionDescription>In some situations, problems with the release might be encountered but are not serious enough to reverse the deployment. If
diff --git a/epf_prac_151/practice.gen.production_release.base/workproducts/release_communications.xmi b/epf_prac_151/practice.gen.production_release.base/workproducts/release_communications.xmi
index 6ebef8c..a058068 100644
--- a/epf_prac_151/practice.gen.production_release.base/workproducts/release_communications.xmi
+++ b/epf_prac_151/practice.gen.production_release.base/workproducts/release_communications.xmi
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-wHkXWtQxFeicCBDHK-f7xg" name="release_communications,_pQGOYGPoEeCXEsUUiTbOuQ" guid="-wHkXWtQxFeicCBDHK-f7xg" changeDate="2012-05-30T14:28:28.971-0700" version="7.5.1">
+<org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-wHkXWtQxFeicCBDHK-f7xg" name="release_communications,_pQGOYGPoEeCXEsUUiTbOuQ" guid="-wHkXWtQxFeicCBDHK-f7xg" changeDate="2012-05-30T14:28:28.971-0700" version="7.5.1">
<mainDescription><p>
Sometimes, depending on the product user base, separate communiques might need to be prepared for each stakeholder
group. In that case, this artifact should specify the different groups to which communications are directed, the method
@@ -14,8 +14,9 @@
</p>
<p>
While there is no prescribed format for the release communications artifact, each communique should indicate the
- preferred delivery mechanisms (e.g., beeper notification, telephone calls, a posting to an internal release website,
- live or pre-recorded presentations by senior management, etc.) and generally answer the following questions:
+ preferred delivery mechanisms (for example: beeper notification, telephone calls, a posting to an internal release
+ website, live or pre-recorded presentations by senior management, etc.). This artifact generally answers the following
+ questions:
</p>
<ul>
<li>
diff --git a/epf_prac_151/process.openup.base/guidances/supportingmaterials/release_info_openup_process.xmi b/epf_prac_151/process.openup.base/guidances/supportingmaterials/release_info_openup_process.xmi
index 6eff7bc..ac611dd 100644
--- a/epf_prac_151/process.openup.base/guidances/supportingmaterials/release_info_openup_process.xmi
+++ b/epf_prac_151/process.openup.base/guidances/supportingmaterials/release_info_openup_process.xmi
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-8kqk1tE8R96b88T_NC7SoQ" name="release_info_openup_process,_o5lO8Wr4Ed24CboUCnKL3A" guid="-8kqk1tE8R96b88T_NC7SoQ" changeDate="2012-05-30T12:07:07.892-0700" version="7.2.0">
+<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-8kqk1tE8R96b88T_NC7SoQ" name="release_info_openup_process,_o5lO8Wr4Ed24CboUCnKL3A" guid="-8kqk1tE8R96b88T_NC7SoQ" changeDate="2012-05-30T12:07:07.892-0700" version="7.2.0">
<mainDescription><h3>
EPF Base
</h3>
@@ -7,16 +7,6 @@
1.5.1.4
</h4>
<p>
- a. Incorporated the new practices (Documentation and Training, and Production Release) into the OpenUP delivery
- process.<br />
- b.&nbsp;Incorporated the practice Project Process Tailoring into the OpenUP delivery process.<br />
- c. Updated "planned flags" in OpenUP delivery process.<br />
-</p>
-<h4>
- 1.5&nbsp;
-</h4>
-<p>
- This is the first version of this process plug-in, included as part of the EPF 1.5 practices library.&nbsp; It is
- derived primarily from OpenUP 1.0 Content.
+ This is the first version of this practice, included as part of the EPF 1.5.1.4 practices library.
</p></mainDescription>
</org.eclipse.epf.uma:ContentDescription>
