<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ContentDescription 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="-IMDeKIiADfZMg8gyWT_JYw" name="new_concept,_wtFW8J8wEd-dppiOhprtkA" guid="-IMDeKIiADfZMg8gyWT_JYw" changeDate="2011-10-13T15:32:52.921-0700" version="7.5.0">
  <mainDescription>&lt;p>&#xD;
    The Unified Method Framework (UMF) is an extensible integration framework that defines a &quot;common language&quot; for&#xD;
    the&amp;nbsp;inter-operation of &lt;a class=&quot;elementLinkWithUserText&quot;&#xD;
    href=&quot;./../../../practice.bus.mdev.base/guidances/concepts/practice_ACB683BB.html&quot;&#xD;
    guid=&quot;_WBtggJ8wEd-dppiOhprtkA&quot;>practices&lt;/a>.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    The UMF provides:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        A common library structure for plug-ins&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Shared categorization schemes and standardized views&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Common standards&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        A&amp;nbsp;shared set of core method elements for building related processes&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    In its broadest sense, the UMF is a virtual library of all methods developed within its constraints.&lt;br />&#xD;
    &lt;br />&#xD;
    The benefits of the UMF are the same as for any practice framework. Specifically:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        Defines a consistent approach for how plug-ins are structured that allows true plug-and-play between content&#xD;
        authored by different groups and ensures that remotely authored content integrates seamlessly into the overall&#xD;
        library&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Reduces complexity and increases understandability of the methods as all methods are constructed/structured in a&#xD;
        similar way&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Maximizes reuse as common elements are shared across practices and practices are shared across processes. Practices&#xD;
        also provide a coarser-grained unit of reuse and customization than just work products.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Increases configurability as practices can be easily configured to produce many different types of method assets&#xD;
        (i.e., processes) to match specific needs. Practices are loosely coupled and interchangeable. Practices are easily&#xD;
        &quot;swapped out&quot; and can be &quot;mixed and matched&quot; to create the best solution.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Supports incremental method authoring. Practices are written independently from each other. Practices are dependent&#xD;
        on a shared core and not on each other.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Supports incremental adoption of a process. The process is divided into practices that can be adopted individually&#xD;
        and incrementally. You can start small with a few practices and then grow/scale, adopting one practice at a time&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    IBM uses the Unified Method Framework (UMF) as the underlying framework for all of its methods.&#xD;
&lt;/p></mainDescription>
</org.eclipse.epf.uma:ContentDescription>
