| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ContentDescription xmi:version="2.0" |
| xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.5/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmlns:rmc="http://www.ibm.com/rmc" |
| rmc:version="7.5.0" xmi:id="-MEGYsPST7NvK6reYOTZiZA" |
| name="defining_practice_config_cross_practice_process,_URR4AMbSEdy9YushbOcFQA" |
| guid="-MEGYsPST7NvK6reYOTZiZA" changeDate="2008-11-17T22:49:53.125-0800" version="7.2.0"> |
| <mainDescription><p>
 |
| Defining a <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/cross_practice_process_5F83B112.html"
 |
| guid="_9NcfoFJgEd2SzrMjC_svdw">cross-practice process</a> is where you turn your attention to the process/lifecycle
 |
| side of things. How should the <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html"
 |
| guid="_x459ktnmEdmO6L4XMImrsA">task</a>s and/or <a class="elementLinkWithUserText"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/activity_1D028230.html"
 |
| guid="_yoVhMB_IEdq6CKKKq4D7YA">activities</a> (i.e., <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/capability_pattern_F5DDC5F.html"
 |
| guid="_2RUJACO4EdqaNq6Ptg8uyA">capability pattern</a>s) from the individual <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/concepts/practice_F5C8EAAB.html"
 |
| guid="_qhCTAFRREd2CWscN8Mx6rg">Practice</a>s "flow" together? Are there any activities that always appear together and
 |
| in what order do they appear? Are there specific sets of activities that can be reused together in more course-grained
 |
| flows?&nbsp;What does an overall lifecycle look like? Define cross-practice processes to&nbsp;reflect these
 |
| decisions.&nbsp;Specifically, define&nbsp;capability patterns for sets of capability patterns that always appear
 |
| together and can be reused in other capability patterns, and define <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/delivery_process_BCDF50B7.html"
 |
| guid="_ZufeMCO3EdqaNq6Ptg8uyA">delivery process</a>es for overall lifecycles. Defining cross-practice
 |
| processes&nbsp;defines an overall flow through the practices and validates that you have the right practice content
 |
| with the right separation of concerns.
 |
| </p>
 |
| <p>
 |
| Perform the following steps to create a cross-practice process:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| If one does not exist, create a Publish Base plug-in to contain the new process.&nbsp;<a
 |
| class="elementLinkWithType"
 |
| href="./../../../practice.mdev.auth.practice_config_auth.base/guidances/roadmaps/customize_existing_practice_config_2642DD24.html"
 |
| guid="_u5j3MFcqEd2N4vZAlUIPvw">Roadmap: Customize an Existing Practice Configuration</a> information on Publish
 |
| Base plug-ins, see <a class="elementLinkWithType"
 |
| href="./../../../core.mdev.common.base/guidances/concepts/practice_lib_plugin_types_3EA8002F.html"
 |
| guid="__428YO6cEdygKbJMUVNEtg">Concept: Practice Library Plug-In Types</a>.<br />
 |
| &nbsp;&nbsp;
 |
| </li>
 |
| <li>
 |
| Create a Publishable&nbsp;<a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/method_configuration_C2B8FA8A.html"
 |
| guid="__V7pAMaEEduMlb2cQZNTYw">method configuration</a>&nbsp;that includes the the necessary core plug-ins (include
 |
| role and standard category definitions), the&nbsp;new Publish plug-in, the practices (including the desired
 |
| practice role assignments),&nbsp;and any cross-practice processes you are interested in including in your
 |
| cross-practice process (remember all processes must have a default configuration). For more information on the
 |
| practice library configuration types, see <a class="elementLinkWithType"
 |
| href="./../../../core.mdev.common.base/guidances/concepts/practice_lib_config_types_B96A959A.html"
 |
| guid="_1gchoO6dEdygKbJMUVNEtg">Concept: Practice Library Configuration Types</a>. For more information on defining
 |
| configurations, see <a class="elementLinkWithType"
 |
| href="./../../../core.mdev.common.base/guidances/guidelines/defining_method_configurations_2B25CEA5.html"
 |
| guid="_l77zcIB-EduaS6LQ8n6xUQ">Guideline: Defining Method Configurations</a>.<br />
 |
| </li>
 |
| <li>
 |
| Create the cross-practice process, specifying the new configuration as the default configuration. Assemble the
 |
| cross-practice process using the method elements (<a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/task_6C1FF051.html"
 |
| guid="_x459ktnmEdmO6L4XMImrsA">task</a>s, <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/termdefinitions/capability_pattern_F5DDC5F.html"
 |
| guid="_2RUJACO4EdqaNq6Ptg8uyA">capability pattern</a>s) from the Process Construction configuration, defining as
 |
| many levels (i.e., nested activities) as are needed. In some cases, there may even be reference workflows from the
 |
| individual practices that you can use for ideas for the process you are building. When assembling cross-practice
 |
| processes, the processes that are used (i.e., the capability patterns that are applied) from the practices must be
 |
| <u><em>copied</em></u> instead of <u><em>extended</em></u> so that the process descriptors are built using the
 |
| default configuration for the cross-practice process. For information on assembling processes, see <a
 |
| class="elementLinkWithType"
 |
| href="./../../../core.mdev.common.base/guidances/guidelines/defining_processes_756EDFA.html"
 |
| guid="_Y_JroEyDEdu4NY1n_hCY0w">Guideline: Defining Processes</a>.
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| In summary, practices provide the pieces parts (tasks and capability patterns) and may even provide some good process
 |
| patterns e.g., reference workflows), but in the end, it is the person creating the a process that must decide the order
 |
| and levels (the level of nesting of the activities) of the process, using any and all available method content elements
 |
| and/or process patterns.
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
