blob: 590e7bb9132fd28b24071174698f10f757c2184c [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd">
<!-- VERSION rmc:7.1.0 -->
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<!-- START NON-TRANSLATABLE -->
<title>openup&amp;#92;guidances&amp;#92;supportingmaterials&amp;#92;&amp;#92;openup_family.xmi</title>
</head>
<!-- WARNING: do not modify the generated comments in this file below this line. They are used as markers for the import process. -->
<body>
Element Name: openup_family.xmi<br/><br/>
<!-- END NON-TRANSLATABLE -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: presentationName<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:presentationName,_v2l6gK_5EduMeuOwJ2MpeQ CRC: 3887283197 -->The OpenUP Family<!-- END:presentationName,_v2l6gK_5EduMeuOwJ2MpeQ -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: briefDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:briefDescription,_v2l6gK_5EduMeuOwJ2MpeQ CRC: 173963725 -->OpenUP is a family of processes based on a common set of principles and a shared core process.<!-- END:briefDescription,_v2l6gK_5EduMeuOwJ2MpeQ -->
<br/><br/><br/>
<!-- START NON-TRANSLATABLE -->
Attribute: mainDescription<br/><br/>
<!-- END NON-TRANSLATABLE -->
<!-- START:mainDescription,-KCSbXYv5TALlL00zMMfgVw CRC: 2130337649 --><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>
<li>
or sold commercially
</li>
</ul><!-- END:mainDescription,-KCSbXYv5TALlL00zMMfgVw -->
</body>
</html>