| <?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" epf:version="1.0.0" xmi:id="_uDU1oQSEEdq61bDkWg1SXw" guid="_uDU1oQSEEdq61bDkWg1SXw" changeDate="2005-10-30T16:58:11.631-0800"> |
| <mainDescription><h3> |
| What is UMA? |
| </h3> |
| <p> |
| The Unified Method Architecture (UMA) is a process engineering meta-model that defines schema and terminology for |
| representing methods consisting of method content and processes. Also see <a class="elementLinkWithType" href="./../../base_concepts/guidances/concepts/introduction_to_uma,_94_eoO8LEdmKSqa_gSYthg.html" guid="_94_eoO8LEdmKSqa_gSYthg">Concept: Key Capabilities of the Unified Method Architecture (UMA)</a>&nbsp;for more |
| details. |
| </p> |
| <h3> |
| Fundamental principle within UMA |
| </h3> |
| <p> |
| UMA is based&nbsp;on the following fundamental&nbsp;separations of concern: |
| </p> |
| <ul> |
| <li> |
| The separation of core method content versus the application of method content in processes |
| </li> |
| <li> |
| The definition of an optional extensibility mechanism in the method for large scale management of method and |
| process repositories |
| </li> |
| <li> |
| Packaging and configuration of method content, processes, and plugins in method libraries |
| </li> |
| <li> |
| A separation of recommended method and guidance description fields |
| </li> |
| <li> |
| A separation of semantic elements from their notation in process diagrams |
| </li> |
| </ul> |
| <h3> |
| The Basic Elements of UMA |
| </h3> |
| <p> |
| The most fundamental principle of the Unified Method Architecture (UMA) is the separation of&nbsp;reusable core method |
| content from its application in processes and almost all of UMA's elements are categorized along this separations. |
| </p> |
| <p> |
| The Unified Method Architecture separates reusable core method content from its application in processes.&nbsp; Method |
| content describes what is to be produced, the necessary skills required and the step-by-step explanation describing how |
| specific development goals are achieved, independently of the placement of these items within a development |
| lifecycle.&nbsp; Processes take these method elements and relate them into semi-ordered sequences that are customized |
| to specific types of projects. For example, a software development project that develops an application from scratch |
| performs development tasks such as "Develop Vision" or "Use Case Design" similar to a project that extends an existing |
| software system.&nbsp; However, the two projects will perform the Tasks at different points in time with a different |
| emphasis, i.e. they will perform the steps of these tasks at different point of time and perhaps apply individual |
| variations and additions. |
| </p> |
| <p> |
| The figure below shows the difference between method content and process by representing them as two different |
| dimensions: |
| </p> |
| <ul> |
| <li> |
| Method content describing how development work is being performed is categorized by disciplines.&nbsp; Each |
| discipline is comprised of tasks (not visible in the figure) that provide step-by-step descriptions of how specific |
| development goals are achieved.&nbsp; |
| </li> |
| <li> |
| For a process, tasks have been referenced by the process from the method content and placed into breakdown |
| structures and workflows ready for instantiation by allocating resources to perform the work and having real work |
| products as the inputs and outputs of the tasks.<br /> |
| </li> |
| </ul> |
| <p align="center"> |
| <img alt="Diagram illustrating the separation of Method and Process content within the UMA Meta-Model" src="../guidances/concepts/resources/uma_hump.jpg" border="0" /> |
| </p> |
| <p class="picturetext" align="center"> |
| Method Content definition versus<br /> |
| the application of Method Content in a Process. |
| </p> |
| <p> |
| UMA's key concepts reflect this separation of method content from process as shown in the figure below.&nbsp; It show |
| that a Method (also refered to as a Method Framework) comprises on method content described with concepts such Work |
| Products, Roles, Task and Categories as well as Processes described with Activities, Capability Patterns, or Delivery |
| Processes. |
| </p> |
| <p align="center"> |
| <img alt="Diagram illustrating that the intersection between Method and Process content is guidance" src="../guidances/concepts/resources/uma_m_vs_p.gif" /> |
| </p> |
| <p align="center"> |
| Overview of how the key UMA concepts are positioned based on whether they represent method content or process |
| </p> |
| <p class="picturetext" align="left"> |
| Key <a class="elementLinkWithUserText" href="./../../base_concepts/customcategories/method_concepts,_WfL28BTMEdqrUt4zetC1gg.html" guid="_WfL28BTMEdqrUt4zetC1gg">Method Content Elements</a> &nbsp;are: |
| </p> |
| <div style="MARGIN-LEFT: 2em"> |
| <ul> |
| <li> |
| <div class="picturetext" align="left"> |
| <a class="elementLink" href="./../../base_concepts/guidances/concepts/work_product,4.804531471620803E-306.html" guid="4.804531471620803E-306">Work Product</a> |
| </div> |
| </li> |
| <li> |
| <div class="picturetext" align="left"> |
| <a class="elementLink" href="./../../base_concepts/guidances/concepts/role,1.1609745730665898E-304.html" guid="1.1609745730665898E-304">Role</a> |
| </div> |
| </li> |
| <li> |
| <div class="picturetext" align="left"> |
| <a class="elementLink" href="./../../base_concepts/guidances/concepts/task,7.624729048911575E-305.html" guid="7.624729048911575E-305">Task</a> |
| </div> |
| </li> |
| </ul> |
| </div> |
| <p class="picturetext" align="left"> |
| Key <a class="elementLinkWithUserText" href="./../../base_concepts/customcategories/process_concepts,_AtM0gBTQEdqrUt4zetC1gg.html" guid="_AtM0gBTQEdqrUt4zetC1gg">Process Elements</a> &nbsp;are: |
| </p> |
| <div style="MARGIN-LEFT: 2em"> |
| <ul> |
| <li> |
| <div class="picturetext" align="left"> |
| <a class="elementLink" href="./../../base_concepts/guidances/concepts/activity,3.132140065969088E-305.html" guid="3.132140065969088E-305">Activity</a> |
| </div> |
| </li> |
| <li> |
| <div class="picturetext" align="left"> |
| <a class="elementLink" href="./../../base_concepts/guidances/concepts/capability_pattern,1.7072348895114264E-305.html" guid="1.7072348895114264E-305">Capability Pattern</a> |
| </div> |
| </li> |
| <li> |
| <div class="picturetext" align="left"> |
| <a class="elementLink" href="./../../base_concepts/guidances/concepts/delivery_process,_EhgqwO8MEdmKSqa_gSYthg.html" guid="_EhgqwO8MEdmKSqa_gSYthg">Delivery Process</a> |
| </div> |
| </li> |
| </ul> |
| </div> |
| <p class="picturetext" align="left"> |
| <a class="elementLinkWithUserText" href="./../../base_concepts/customcategories/guidance,_xy2SAAIsEdqEutyfYo0quQ.html" guid="_xy2SAAIsEdqEutyfYo0quQ">Guidance</a> &nbsp;comes in many types: |
| </p> |
| <div style="MARGIN-LEFT: 2em"> |
| <ul> |
| <li> |
| <div class="picturetext" align="left"> |
| <a class="elementLink" href="./../../base_concepts/guidances/concepts/checklist,_2vVuUBT9EdqrUt4zetC1gg.html" guid="_2vVuUBT9EdqrUt4zetC1gg">Checklist</a> |
| </div> |
| </li> |
| <li> |
| <div class="picturetext" align="left"> |
| <a class="elementLink" href="./../../base_concepts/guidances/concepts/concept,_8wobABUAEdqrUt4zetC1gg.html" guid="_8wobABUAEdqrUt4zetC1gg">Concept</a> |
| </div> |
| </li> |
| <li> |
| <div class="picturetext" align="left"> |
| <a class="elementLink" href="./../../base_concepts/guidances/concepts/example,_dCG-UBUBEdqrUt4zetC1gg.html" guid="_dCG-UBUBEdqrUt4zetC1gg">Example</a> |
| </div> |
| </li> |
| <li> |
| <div class="picturetext" align="left"> |
| <a class="elementLink" href="./../../base_concepts/guidances/concepts/guideline,_IAwkEBUEEdqrUt4zetC1gg.html" guid="_IAwkEBUEEdqrUt4zetC1gg">Guideline</a> |
| </div> |
| </li> |
| <li> |
| <div class="picturetext" align="left"> |
| <a class="elementLink" href="./../../base_concepts/guidances/concepts/practice,_szl6EBUBEdqrUt4zetC1gg.html" guid="_szl6EBUBEdqrUt4zetC1gg">Practice</a> |
| </div> |
| </li> |
| <li> |
| <div class="picturetext" align="left"> |
| <a class="elementLink" href="./../../base_concepts/guidances/concepts/report,_x2sAgBUBEdqrUt4zetC1gg.html" guid="_x2sAgBUBEdqrUt4zetC1gg">Report</a> |
| </div> |
| </li> |
| <li> |
| <div class="picturetext" align="left"> |
| <a class="elementLink" href="./../../base_concepts/guidances/concepts/reusable_asset,_20bs4BUBEdqrUt4zetC1gg.html" guid="_20bs4BUBEdqrUt4zetC1gg">Reusable Asset</a> |
| </div> |
| </li> |
| <li> |
| <div class="picturetext" align="left"> |
| <a class="elementLink" href="./../../base_concepts/guidances/concepts/roadmap,_JCQbIBnXEdqYreeU3jqaDQ.html" guid="_JCQbIBnXEdqYreeU3jqaDQ">Roadmap</a> |
| </div> |
| </li> |
| <li> |
| <div class="picturetext" align="left"> |
| <a class="elementLink" href="./../../base_concepts/guidances/concepts/supporting_material,_80XPABUBEdqrUt4zetC1gg.html" guid="_80XPABUBEdqrUt4zetC1gg">Supporting Material</a> |
| </div> |
| </li> |
| <li> |
| <div class="picturetext" align="left"> |
| <a class="elementLink" href="./../../base_concepts/guidances/concepts/template,_G_UnIBUCEdqrUt4zetC1gg.html" guid="_G_UnIBUCEdqrUt4zetC1gg">Template</a> |
| </div> |
| </li> |
| <li> |
| <div class="picturetext" align="left"> |
| <a class="elementLink" href="./../../base_concepts/guidances/concepts/term_definition,_Z45fwBUDEdqrUt4zetC1gg.html" guid="_Z45fwBUDEdqrUt4zetC1gg">Term Definition</a> |
| </div> |
| </li> |
| <li> |
| <div class="picturetext" align="left"> |
| <a class="elementLink" href="./../../base_concepts/guidances/concepts/tool_mentor,1.0762105093945226E-304.html" guid="1.0762105093945226E-304">Tool Mentor</a> |
| </div> |
| </li> |
| </ul> |
| </div></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |