| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ContentDescription 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="-6-EbAPOwgLNOseKXLyfu0A" |
| name="defining_practice_configurations,_FnCOMAz8Ed2135n7CJzRCQ" guid="-6-EbAPOwgLNOseKXLyfu0A" |
| changeDate="2008-11-01T04:51:17.343-0700" version="7.2.0"> |
| <mainDescription><p>
 |
| <a class="elementLink" href="./../../../core.mdev.common.base/guidances/concepts/practice_configuration_CC7754F2.html"
 |
| guid="_0H9aAO7EEdy9EOwDlaw7Kw">Practice Configuration</a>s are an important artifact in a <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/concepts/practice_fw_6DA4D54D.html"
 |
| guid="__LjaEFQsEd2uvIuuFjd1Fg">Practice Framework</a>&nbsp;as they assemble a specific set of <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/concepts/practice_F5C8EAAB.html"
 |
| guid="_qhCTAFRREd2CWscN8Mx6rg">Practice</a>s into something a practitioner can use.&nbsp;When defining the practice
 |
| configuration, you must adhere to the architecture of the framework in which the configuration is to exist.
 |
| </p>
 |
| <p>
 |
| Thus, when trying to decide what practice configurations to produce, it is important to take the time to understand the
 |
| nature of the business problem the practice configuration is intended to solve (the configuration's purpose) and who
 |
| will be the primary consumers of the configuration (the configuration's intended audience). Understand what the scope
 |
| of the problem is and the approach to solving it. This understanding forms the basic information that will guide many
 |
| decisions that will affect the ultimate usefulness of the process configuration. It will also guide you in choosing an
 |
| applicable name for the practice configuration.&nbsp;
 |
| </p>
 |
| <p>
 |
| At this point, its even a good idea to identify practices that will be included in the practice configuration, as well
 |
| as any <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/cross_practice_process_5F83B112.html"
 |
| guid="_9NcfoFJgEd2SzrMjC_svdw">cross-practice process</a>es that may be included and what practices they will be
 |
| assembled from.&nbsp;These are not defined in detail at this stage, but identifying them can help clarify the scope of
 |
| the practice configuration.
 |
| </p>
 |
| <p>
 |
| In summary, the following are some key pieces of information that you should capture for a practice configuration and
 |
| some examples for that information:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Name: MAM for Organization X
 |
| </li>
 |
| <li>
 |
| Purpose: Describe the best practices for authoring practice frameworks at Organization X.
 |
| </li>
 |
| <li>
 |
| Scope: All MAM practice framework practices plus Organization X customizations.
 |
| </li>
 |
| <li>
 |
| Intended Audience: Process Engineers at Organization X<br />
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| Practice configurations are physically represented by publishable configurations. Thus, defining a practice
 |
| configuration involves identifying, naming and briefly describing that publishable configuration, and including the
 |
| above information in the definition of the publishable configuration.&nbsp;For more information on publishable
 |
| configurations, 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>.
 |
| </p>
 |
| <p>
 |
| Note: A practice configuration can be defined by mimicking an existing practice configuration. In that case, you can
 |
| define the new practice configuration by copying components of the original practice configuration, including the
 |
| existing practice configuration's method configuration and practice configuration-specific Publish plug-in.
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
