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