| <?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="-wH64MmEefS0O2enDXTIv4A" |
| name="minimal_complete_extensible,_Nm5vUK__EduMeuOwJ2MpeQ" guid="-wH64MmEefS0O2enDXTIv4A" |
| changeDate="2007-07-19T15:52:07.570-0700" version="1.0.0"> |
| <mainDescription><h3>
 |
| Introduction
 |
| </h3>
 |
| <p>
 |
| A good way to understand OpenUP is to think of it as targeted to teams that have the following objectives:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Apply the minimally necessary process that brings value.
 |
| </li>
 |
| <li>
 |
| Avoid being overloaded with unproductive formal work products.
 |
| </li>
 |
| <li>
 |
| Use a process that can be tailored and extended for additional needs that may arise during the software development
 |
| lifecycle.
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| In order to be applied to as many project environments as possible, OpenUP is a process that has the following
 |
| characteristics:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Minimal - only fundamental content is included
 |
| </li>
 |
| <li>
 |
| Complete - it can be manifested as an entire process to build a system
 |
| </li>
 |
| <li>
 |
| Extensible - it can be used as a foundation on which process content can be added or tailored as needed
 |
| </li>
 |
| </ul>
 |
| <h4>
 |
| Minimal
 |
| </h4>
 |
| <p>
 |
| OpenUP is considered an agile, lightweight process that promotes software development best practices such as:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| iterative development
 |
| </li>
 |
| <li>
 |
| team collaboration
 |
| </li>
 |
| <li>
 |
| continuous integration and tests
 |
| </li>
 |
| <li>
 |
| frequent deliveries of working software
 |
| </li>
 |
| <li>
 |
| adaptation to changes, and so on.
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| Other factors also count when determining the size of process material, such as the number of method elements like
 |
| roles, tasks, artifacts and guidance.
 |
| </p>
 |
| <p>
 |
| OpenUP provides descriptions of responsibilities, skills and competencies of the fundamental roles in a team. See the
 |
| list of <a class="elementLinkWithUserText" href="./../../../openup/rolesets/openup_roles.html"
 |
| guid="_TZIJ0O8NEdmKSqa_gSYthg">roles</a> for more details.
 |
| </p>
 |
| <p>
 |
| OpenUP provides the essential artifacts needed to capture and communicate decisions. Ultimately, the process is not
 |
| governed by artifact creation. For example, thinking about design is more important than documenting the design;
 |
| assessing and planning an iteration is about promoting team collaboration instead of creating plans that are written in
 |
| stone. In addition, for each artifact, OpenUP suggests informal representations or provides informal templates as
 |
| starting points for teams that do not need to create their own. The team decides what the most appropriate form to be
 |
| applied is. See the list of <a class="elementLinkWithUserText" href="./../../../openup/domains/openup_wp.html"
 |
| guid="_s4Z9AMWXEdqWePvIjHInwg">work products</a> organized by domains.
 |
| </p>
 |
| <p>
 |
| Tasks in OpenUP are clear and focused on results. Text is usually short and objective, describing how individuals
 |
| should collaborate to achieve objectives. Steps are short descriptions of what to achieve, and point to external
 |
| guidance on how to do it. See the list of <a class="elementLinkWithUserText"
 |
| href="./../../../openup/disciplinegroupings/openup_disciplines.html" guid="__BZycP1UEdmek8CQTQgrOQ">tasks</a> organized
 |
| by disciplines.
 |
| </p>
 |
| <p>
 |
| OpenUP recommends the least amount of process guidance a team should use in order to be successful. Teams may have
 |
| different names or responsibilities for roles, may perform tasks in or have different representations for artifacts,
 |
| but they still want to follow the principles and practices described in OpenUP to increase the chances of project
 |
| success.
 |
| </p>
 |
| <h4>
 |
| Complete
 |
| </h4>
 |
| <p>
 |
| OpenUP is considered a complete process because it covers the essential <a class="elementLinkWithUserText"
 |
| href="./../../../openup/disciplinegroupings/openup_disciplines.html" guid="__BZycP1UEdmek8CQTQgrOQ">disciplines</a> in
 |
| a software development lifecycle by guiding the team in the following high level activities:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Customer needs and requirements are elicited and captured, with continuous customer involvement.
 |
| </li>
 |
| <li>
 |
| A robust architecture for the system is evolved, addressing technical risks and promoting team organization.
 |
| </li>
 |
| <li>
 |
| For each requirement, a technical solution is designed, implemented and tested, which conforms to the architectural
 |
| decisions.
 |
| </li>
 |
| <li>
 |
| The system is evaluated by tests that validate customer requirements.
 |
| </li>
 |
| <li>
 |
| Defects and enhancements feed back into development.
 |
| </li>
 |
| <li>
 |
| Work is prioritized, iterations are planned and assessed, and team members take on work to be done.
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| However, OpenUP assumes that the project team is not responsible for certain activities and decisions that are assigned
 |
| to other areas of the organization, such as:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Creation of the business case is dealt with by management who decides whether or not the project is worth investing
 |
| in, what is the return on investment, and so on.
 |
| </li>
 |
| <li>
 |
| Environment setup - some organizational issues may not be in the scope of the team, such as: installation,
 |
| configuration and licensing of development tools and configuration management tools; development process
 |
| customization and publishing, etc.
 |
| </li>
 |
| <li>
 |
| Deployment and operation - addressed at an organizational rather than a team level.
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| Other areas of concern are also not present in OpenUP, because small teams do not need to deal with the formality or
 |
| overhead of these areas. They include, but are not limited to:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Advanced configuration management
 |
| </li>
 |
| <li>
 |
| Advanced requirements management
 |
| </li>
 |
| <li>
 |
| Program and portfolio management
 |
| </li>
 |
| </ul>
 |
| <h4>
 |
| Extensible
 |
| </h4>
 |
| <p>
 |
| OpenUP can be adopted by projects as it is, out-of-the-box, because it's minimal and complete.
 |
| </p>
 |
| <p>
 |
| However, different projects may have different needs. Organizations may be interested in customizing some aspects of
 |
| OpenUP to adapt it to their projects. These are some examples of possible customization:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Add new or rename existing roles
 |
| </li>
 |
| <li>
 |
| Add steps to existing tasks
 |
| </li>
 |
| <li>
 |
| Create new guidelines on a given technique
 |
| </li>
 |
| <li>
 |
| Remove a given content area
 |
| </li>
 |
| <li>
 |
| Modify existing or add new templates to artifacts
 |
| </li>
 |
| <li>
 |
| Modify or create a new process lifecycle
 |
| </li>
 |
| <li>
 |
| Add or remove process content
 |
| </li>
 |
| <li>
 |
| Add guidance on how to achieve compliance
 |
| </li>
 |
| <li>
 |
| Add guidance specific to a technology being used
 |
| </li>
 |
| <li>
 |
| Replace or augment&nbsp;one of the layers with new&nbsp;content (e.g. by changing&nbsp;or adding material to how
 |
| management is performed)
 |
| </li>
 |
| <li>
 |
| Etc.
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| OpenUP can be customized and extended by using the EPF Composer tool, which allows you to author, configure and publish
 |
| methods. With EPF Composer, you can add, remove and change elements according to your team needs, then publish the
 |
| content to serve as guidance for your team.
 |
| </p>
 |
| <p>
 |
| See more information about customization in <a class="elementLinkWithType"
 |
| href="./../../../openup/guidances/supportingmaterials/resources_for_modifying_methods.html"
 |
| guid="_omneEMX4EduywMSzPTUUwA">Supporting Material: Resources for Modifying Methods</a>.
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
