| <?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.4/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.2.0" xmi:id="-TfxeHO_AJxYCzXVva0kSzQ" |
| name="new_custom_category,_BTJ_YMXwEduywMSzPTUUwA" guid="-TfxeHO_AJxYCzXVva0kSzQ" |
| changeDate="2007-07-12T15:06:21.889-0700" version="1.0.0"> |
| <mainDescription><table width="589" align="center" border="0">
 |
| <tbody>
 |
| <tr>
 |
| <td width="96">
 |
| <div align="center">
 |
| <a href="./../../openup/customcategories/getting_started_with_openup.html"
 |
| guid="__cft0MXxEduywMSzPTUUwA"><img height="48" alt="getting started"
 |
| src="./resources/GetStarted_48.gif" width="48" usemap="#map" border="0" /></a>
 |
| </div>
 |
| </td>
 |
| <td width="95">
 |
| <div align="center">
 |
| <a href="./../../openup/customcategories/core_principles_category.html"
 |
| guid="_UCOtoMXwEduywMSzPTUUwA"><img height="48" alt="core principles"
 |
| src="./resources/CorePrinciples_48.gif" width="48" usemap="#map2" border="0" /></a>
 |
| </div>
 |
| </td>
 |
| <td width="88">
 |
| <div align="center">
 |
| <a href="./../../openup/rolesets/openup_roles.html" guid="_TZIJ0O8NEdmKSqa_gSYthg"><img height="48"
 |
| alt="roles" src="./resources/Roles_48.gif" width="48" usemap="#map3" border="0" /></a>
 |
| </div>
 |
| </td>
 |
| <td width="98">
 |
| <div align="center">
 |
| <a href="./../../openup/domains/openup_wp.html" guid="_s4Z9AMWXEdqWePvIjHInwg"><img height="48"
 |
| alt="work products" src="./resources/WorkProducts_48.gif" width="48" usemap="#map4" border="0" /></a>
 |
| </div>
 |
| </td>
 |
| <td width="88">
 |
| <div align="center">
 |
| <a href="./../../openup/disciplinegroupings/openup_disciplines.html"
 |
| guid="__BZycP1UEdmek8CQTQgrOQ"><img height="48" alt="disciplines" src="./resources/Disciplines_48.gif"
 |
| width="48" usemap="#map5" border="0" /></a>
 |
| </div>
 |
| </td>
 |
| <td width="98">
 |
| <div align="center">
 |
| <a href="./../../openup/deliveryprocesses/openup_lifecycle.html" guid="_0uyGoMlgEdmt3adZL5Dmdw"><img
 |
| height="48" alt="lifecycle" src="./resources/LifeCycle_48.gif" width="48" usemap="#map6"
 |
| border="0" /></a>
 |
| </div>
 |
| </td>
 |
| </tr>
 |
| <tr valign="top" align="middle">
 |
| <td width="96">
 |
| <div align="center">
 |
| <a class="elementLinkWithUserText"
 |
| href="./../../openup/customcategories/getting_started_with_openup.html"
 |
| guid="__cft0MXxEduywMSzPTUUwA">Getting Started</a>
 |
| </div>
 |
| </td>
 |
| <td width="95">
 |
| <div align="center">
 |
| <a class="elementLinkWithUserText" href="./../../openup/customcategories/core_principles_category.html"
 |
| guid="_UCOtoMXwEduywMSzPTUUwA">Core Principles</a>
 |
| </div>
 |
| </td>
 |
| <td width="88">
 |
| <div align="center">
 |
| <a class="elementLinkWithUserText" href="./../../openup/rolesets/openup_roles.html"
 |
| guid="_TZIJ0O8NEdmKSqa_gSYthg">Roles</a>
 |
| </div>
 |
| </td>
 |
| <td width="98">
 |
| <div align="center">
 |
| <a class="elementLinkWithUserText" href="./../../openup/domains/openup_wp.html"
 |
| guid="_s4Z9AMWXEdqWePvIjHInwg">Work Products</a>
 |
| </div>
 |
| </td>
 |
| <td width="88">
 |
| <div align="center">
 |
| <a class="elementLinkWithUserText" href="./../../openup/disciplinegroupings/openup_disciplines.html"
 |
| guid="__BZycP1UEdmek8CQTQgrOQ">Disciplines</a>
 |
| </div>
 |
| </td>
 |
| <td width="98">
 |
| <div align="center">
 |
| <a class="elementLinkWithUserText" href="./../../openup/deliveryprocesses/openup_lifecycle.html"
 |
| guid="_0uyGoMlgEdmt3adZL5Dmdw">Lifecycle</a>
 |
| </div>
 |
| </td>
 |
| </tr>
 |
| </tbody>
 |
| </table>
 |
| <p>
 |
| <b>What is OpenUP?</b>
 |
| </p>
 |
| <p>
 |
| OpenUP is an open source software development process designed for small, co-located teams who want to take an <a
 |
| class="elementLinkWithUserText" href="./../../openup/guidances/supportingmaterials/agile_and_unified.html"
 |
| guid="_qg1IAK__EduMeuOwJ2MpeQ">agile approach</a> to development. OpenUP is an iterative process that is <a
 |
| class="elementLink" href="./../../openup/guidances/supportingmaterials/minimal_complete_extensible.html"
 |
| guid="_Nm5vUK__EduMeuOwJ2MpeQ">Minimal, Complete, and Extensible</a>. It values collaboration and stakeholder benefit
 |
| over unnecessary deliverables and formality. OpenUP is an agile process that is extensible to cover a broad variety of
 |
| contexts, borrowing heavily from Scrum, XP, Eclipse Way, and IBM&reg; Rational Unified Process&reg; (RUP&reg;) methods (see <a
 |
| class="elementLink" href="./../../openup/guidances/concepts/origin_of_content.html"
 |
| guid="_63H5cCd-EdymavVWiFnAjw">Origin of Content</a> for more information).
 |
| </p>
 |
| <p>
 |
| OpenUP is divided into three key areas, shown in Figure 1. Iterations focus the team on delivering value every month.
 |
| Micro-increments focus the team on the continuous progress of well-defined tasks, and the governance lifecycle ensures
 |
| appropriate stakeholder visibility and oversight.
 |
| </p>
 |
| <p>
 |
| <strong>Figure 1: OpenUP Layers: Iterations, Micro-increments, and the governence lifecycle</strong>
 |
| </p>
 |
| <p>
 |
| <img alt="Three key areas that are part of OpenUP"
 |
| src="./../../openup/guidances/concepts/resources/three_layers.jpg" />&nbsp;&nbsp;
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| <b>Iteration Lifecycle.</b> The iteration lifecycle provides a set of team-based practices describing how to
 |
| leverage iterations to focus the team on delivering incremental value to stakeholders in a predictable manner. The
 |
| iteration plan defines what should be delivered within the iteration, and the result is a demoable or shippable
 |
| build.
 |
| </li>
 |
| <li>
 |
| <b>Micro-increments.</b> The micro-increments describe how to carry out day-to-day tasks, including test-driven
 |
| development, defining stakeholders and their needs, and early development of executable architectures. A work item
 |
| defines what should be delivered, tested code is integrated into the build, and validated artifacts are added to
 |
| the project library.
 |
| </li>
 |
| <li>
 |
| <b>Governance lifecycle.</b> The governance lifecycle provide stakeholders and team members with visibility and
 |
| decision points throughout the project. This enables effective oversight, and allows you to make "go or no-go"
 |
| decisions at appropriate times. A project plan defines the lifecycle, and the end result is a released application.
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| <b>Who should use OpenUP?</b>
 |
| </p>
 |
| <p>
 |
| OpenUP is most useful for four primary groups of users:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Software development practitioners (developers, project managers, analysts, and testers) working together as a
 |
| project team
 |
| </li>
 |
| <li>
 |
| Stakeholders
 |
| </li>
 |
| <li>
 |
| Software process engineers
 |
| </li>
 |
| <li>
 |
| Instructors
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| Software development practitioners can find guidance on what is required of them in the roles defined by OpenUP. Each
 |
| role describes a set of activities and artifacts for which the role is responsible. Guidance is also given on how those
 |
| roles collaborate.
 |
| </p>
 |
| <p>
 |
| Stakeholders will find guidance on what they may expect from the software development team, and how the software will
 |
| be created. OpenUP also describes the stakeholders' responsibilities, and states how they can best work with the
 |
| development team to obtain software that meets their needs.
 |
| </p>
 |
| <p>
 |
| Software process engineers can use EPF Composer to extend and modify OpenUP. Modification may be as simple as altering
 |
| templates for work products, or as sophisticated as adding activities necessary for creating software in your specific
 |
| environment (such as audits for safety-critical systems). In addition to modifying method content, process engineers
 |
| can add, change, or remove process flows to add organization-specific capability patterns.
 |
| </p>
 |
| <p>
 |
| OpenUP is appropriate for academic organizations also. As an open source process, it can serve as the basis for
 |
| software engineering courses and, when combined with the EPF Composer, courses in software process engineering.<br />
 |
| </p><br /></mainDescription> |
| <keyConsiderations><p>
 |
| Use OpenUP as-is when you have a small, co-located team.
 |
| </p>
 |
| <p>
 |
| Modify OpenUP for small teams with different circumstances (for instance, a novel project or geographically distributed
 |
| team members). See <a class="elementLinkWithType" href="./../../openup/guidances/supportingmaterials/resources_for_modifying_methods_7663A1A6.html" guid="_omneEMX4EduywMSzPTUUwA">Supporting Material: Resources for Modifying Methods</a> for more information on
 |
| how to customize OpenUP.
 |
| </p></keyConsiderations> |
| </org.eclipse.epf.uma:ContentDescription> |
