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