| <?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="-B6nujkQwc_jcqftjJN3aqg" |
| name="new_concept,_nrrn4GqHEdun45RPFGeYnA" guid="-B6nujkQwc_jcqftjJN3aqg" changeDate="2008-10-12T10:12:46.750-0700" |
| version="1.0.0"> |
| <mainDescription><p>
 |
| The Unified Method Framework (UMF) is an extensible integration framework that defines a “common language” for
 |
| the&nbsp;interoperation of <a class="elementLink"
 |
| href="./../../../core.default.uma_concept.base/guidances/concepts/practice_F5C8EAAB.html"
 |
| guid="_qhCTAFRREd2CWscN8Mx6rg">Practice</a>s .&nbsp;
 |
| </p>
 |
| <p>
 |
| <img alt="umf_graphic" src="./resources/umf.jpg" />&nbsp;
 |
| </p><br />
 |
| <p>
 |
| The UMF provides:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| A common library structure for plug-ins
 |
| </li>
 |
| <li>
 |
| Shared categorization schemes and standardized views
 |
| </li>
 |
| <li>
 |
| Common standards and QA criteria
 |
| </li>
 |
| <li>
 |
| Common development guidance linked to <a class="elementLink"
 |
| href="./../../../core.mdev.common.base/guidances/termdefinitions/licensing_level_746E1470.html"
 |
| guid="_47cn8PU3EdyNMvgj607huw">licensing level</a>s, governance and overall approach to quality
 |
| </li>
 |
| <li>
 |
| Compatible and cooperative authoring processes
 |
| </li>
 |
| <li>
 |
| A shared set of core method elements for building related processes
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| In its broadest sense, the UMF is a virtual library of all methods developed within its constraints.
 |
| </p>
 |
| <p>
 |
| The benefits of the UMF are the same as for any practice framework.&nbsp; Specifically:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Defines a <strong><em>consistent approach</em></strong> for how plug-ins are structured that allows
 |
| <strong><em>true plug-and-play</em></strong> between content authored by different groups and ensures that remotely
 |
| authored content integrates seamlessly into the overall library
 |
| </li>
 |
| <li>
 |
| <strong><em>Reduces complexity</em></strong> and <strong><em>increases understandability</em></strong> of the
 |
| methods&nbsp;as all methods are constructed/structured in a similar way
 |
| </li>
 |
| <li>
 |
| <strong><em>Maximizes reuse</em></strong> as common elements are shared across practices and practices are shared
 |
| across processes.&nbsp; Practices also provide a coarser-grained unit of reuse and customization than just work
 |
| products
 |
| </li>
 |
| <li>
 |
| <em><strong>Increases configurability</strong></em> as practices can be easily configured to produce many different
 |
| types of method assets (i.e., processes) to match specific needs. Practices are <strong><em>loosely
 |
| coupled</em></strong> and <strong><em>interchangeable</em></strong>.&nbsp; Practices are easily “swapped out” and
 |
| can be "mixed and matched" to create the best solution.&nbsp;&nbsp;Specifically, processes can be assembled to best
 |
| suit the end user's needs -- specific practices, role assignments, categorization (domains, work product kinds,
 |
| disciplines, work products, role sets), etc.&nbsp; Processes can be assembled to best suit your needs -- specific
 |
| practices, role assignments, categorization (domains, work product kinds, disciplines, work products, role sets),
 |
| etc.
 |
| </li>
 |
| <li>
 |
| Supports <strong><em>incremental method authoring</em></strong>.&nbsp;Practices are written independently from each
 |
| other.&nbsp; Practices are dependent on a shared core and not on each other.
 |
| </li>
 |
| <li>
 |
| Supports <strong><em>incremental adoption of a process</em></strong>. The process is divided into practices that
 |
| can be adopted individually and incrementally.&nbsp; You can start small with a few practices and then grow/scale,
 |
| adopting one practice at a time
 |
| </li>
 |
| </ul></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
