OpenUP/OpenUP_baseline_EN/library/base_concepts/guidances/concepts/configuration.xmi

<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" xmi:id="_d7QQABUFEdqrUt4zetC1gg" name="configuration,_d698IBUFEdqrUt4zetC1gg" guid="_d7QQABUFEdqrUt4zetC1gg" changeDate="2005-11-04T18:15:35.245-0800">
  <mainDescription>&lt;p&gt;
    A Method Configuration is a collection of selected &lt;a class=&quot;elementLinkWithUserText&quot;
    href=&quot;./../../../base_concepts/guidances/concepts/method_plugin,_0KeEMBUFEdqrUt4zetC1gg.html&quot;
    guid=&quot;_0KeEMBUFEdqrUt4zetC1gg&quot;&gt;Method Plugins&lt;/a&gt;, &lt;a class=&quot;elementLinkWithUserText&quot;
    href=&quot;./../../../base_concepts/customcategories/method_package,_R5Vk4BtpEdqSLrJ4Ij2LVA.html&quot;
    guid=&quot;_R5Vk4BtpEdqSLrJ4Ij2LVA&quot;&gt;Method Packages&lt;/a&gt; and Processes (see &lt;a class=&quot;elementLinkWithType&quot;
    href=&quot;./../../../base_concepts/guidances/concepts/capability_pattern,1.7072348895114264E-305.html&quot;
    guid=&quot;1.7072348895114264E-305&quot;&gt;Concept: Capability Pattern&lt;/a&gt;, &lt;a class=&quot;elementLinkWithType&quot;
    href=&quot;./../../../base_concepts/guidances/concepts/delivery_process,_EhgqwO8MEdmKSqa_gSYthg.html&quot;
    guid=&quot;_EhgqwO8MEdmKSqa_gSYthg&quot;&gt;Concept: Delivery Process&lt;/a&gt;). A Configuration can be exported into its own stand-alone
    library when it includes the full transitive closure of all elements it depends on. A Method Configuration defines a
    logical subset of a &lt;a class=&quot;elementLink&quot;
    href=&quot;./../../../base_concepts/guidances/concepts/method_library,_m8lGkBUFEdqrUt4zetC1gg.html&quot;
    guid=&quot;_m8lGkBUFEdqrUt4zetC1gg&quot;&gt;Method Library&lt;/a&gt;.
&lt;/p&gt;
&lt;h3&gt;
    Applications
&lt;/h3&gt;
&lt;p&gt;
    A Configuration is often built around one or more Delivery Processes. A Delivery Process can be valid for different
    Method Configurations, but each Configuration may include or exclude particular content for specific situations. For
    example, a Delivery Process can be defined to include content for developing schemas for different types of database
    management systems, such as content for RDBMS and OODBMS. When using such a Delivery Process, users may want to select
    just the type of DBMS used within their project, and hence exclude all content pertaining to other types of DBMS. They
    achieve this by selecting a Configuration which excludes the respective content or by creating a new one if none such
    already exists.&lt;br /&gt;
&lt;/p&gt;</mainDescription>
</org.eclipse.epf.uma:ContentDescription>