<?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:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-KCSbXYv5TALlL00zMMfgVw" name="openup_family,_v2l6gK_5EduMeuOwJ2MpeQ" guid="-KCSbXYv5TALlL00zMMfgVw" changeDate="2007-07-23T20:59:52.500+0330">
  <mainDescription>&lt;p>&#xD;
    The OpenUP family of processes aims at addressing a broad variety of project types while sharing a set of common&#xD;
    characteristics. These are the key principles of:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        &lt;a class=&quot;elementLink&quot; href=&quot;./../../../openup/guidances/concepts/core_principle_collaborate.html&quot;&#xD;
        guid=&quot;_KkTIsMp7EdqC_NfSivunjA&quot;>Collaborate to align interests and share understanding&lt;/a>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;a class=&quot;elementLink&quot; href=&quot;./../../../openup/guidances/concepts/core_principle_evolve.html&quot;&#xD;
        guid=&quot;_GXiogMvoEdqukPpotm3DYg&quot;>Evolve to continuously obtain feedback and improve&lt;/a>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;a class=&quot;elementLink&quot; href=&quot;./../../../openup/guidances/concepts/core_principle_focus.html&quot;&#xD;
        guid=&quot;_9gocwMvoEdqukPpotm3DYg&quot;>Focus on the architecture early to minimize risks and organize development&lt;/a>&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;a class=&quot;elementLink&quot; href=&quot;./../../../openup/guidances/concepts/core_principle_balance.html&quot;&#xD;
        guid=&quot;_ssG6MMvpEdqukPpotm3DYg&quot;>Balance competing priorities to maximize stakeholder value&lt;/a>.&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    Processes in the OpenUP family are written as extensions to the core OpenUP process, which embraces a pragmatic, agile&#xD;
    philosophy focusing on the collaborative nature of software development. This core OpenUP process is a tools-agnostic,&#xD;
    low-ceremony process that can be extended to address a broad variety of project types.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    By adding process plug-ins, extensions to OpenUP can be&amp;nbsp;created that address a variety of development concerns,&#xD;
    such as SOA, geographical distribution, model-driven architecture and embedded systems. Tool and technology specific&#xD;
    guidance can be added, such as guidance on J2EE, and a variety of development tools. Some of these extensions can be&#xD;
    quite modest, adding&amp;nbsp;for example&amp;nbsp;just tool specific guidance to existing tasks, while others could be quite&#xD;
    comprehensive, creating processes that provide a radically expanded scope with new or altered artifacts, new or altered&#xD;
    tasks, and new or altered roles.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    As stated above, to qualify as members of the OpenUP family, extending processes&amp;nbsp;must comply with the key&#xD;
    principles of OpenUP and be written as extensions to the OpenUP core process.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Extensions to OpenUP can be:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        used internally by an organization&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        open source as a part of the EPF project,&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        made freely available outside the open source licenses of Eclipse (EPL)&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        or sold commercially&#xD;
    &lt;/li>&#xD;
&lt;/ul></mainDescription>
</org.eclipse.epf.uma:ContentDescription>
