| <?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="-At_b3UIzbgdmtJsb2Ymfhg" |
| name="new_roadmap,_vEruwN-rEdqiM_wFaqLjNg" guid="-At_b3UIzbgdmtJsb2Ymfhg" changeDate="2007-07-02T14:00:05.357-0700" |
| version="1.0.0"> |
| <mainDescription><h3> Overview of OpenUP</h3>
 |
| <p> OpenUP is for small teams who work together in the same location. The team 
 |
| needs to engage in plenty of daily face-to-face interaction. Team members include 
 |
| the stakeholders, developers, architects, project manager, and testers. They 
 |
| make their own decisions about what they need to work on, what the priorities 
 |
| are, and how best to address stakeholder needs. The organization must support 
 |
| the team by allowing them these responsibilities. </p>
 |
| <p> Team members collaborate extensively. The presence of stakeholders as team 
 |
| members is critical to successfully implementing OpenUP. </p>
 |
| <p>
 |
| 
 |
| Team members participate in daily stand-up meetings to communicate status and issues. Problems are addressed outside of
 |
| the daily meetings.
 |
| </p>
 |
| <p> OpenUP focuses on significantly&nbsp;reducing risk early in the lifecycle. 
 |
| This requires regular risk review meetings and rigorous implementation of mitigation 
 |
| strategies. </p>
 |
| <p> All work is listed, tracked, and assigned through the Work Items List. Team 
 |
| members use this single repository for all tasks that need to be recorded and 
 |
| tracked. This includes all change requests, bugs, and stakeholder requests. 
 |
| </p>
 |
| <p> Use cases are used to elicit and describe requirements; therefore, team members 
 |
| need to develop skills in writing good use cases. Stakeholders are responsible 
 |
| for reviewing and certifying that the requirements are correct. Use cases are 
 |
| developed collaboratively. </p>
 |
| <p> Architecturally significant requirements must be identified and stabilized 
 |
| in the Elaboration phase so that a robust architecture can be created as the 
 |
| core of the system. An architecturally significant requirement change that must 
 |
| be addressed may arise later in development, but the risk of this happening 
 |
| is significantly reduced in the Elaboration iteration. </p>
 |
| <p> Testing is performed multiple times per iteration, every time the solution 
 |
| is incremented with the development of a requirement, change, or bug fix. These 
 |
| tests happen after developers have developed the solution (which should have 
 |
| been unit-tested) and integrate it into the code base. These tests help guarantee 
 |
| that a stable build is created and always available as development progresses. 
 |
| </p>
 |
| <p> OpenUP does not include content for deployment, configuration management, 
 |
| or the development environment (such as customizing this process or setting 
 |
| up development environments). OpenUP focuses on a singe team, and these areas 
 |
| are generally addressed at an organizational or enterprise level. Look for extensions 
 |
| to OpenUP that address these wider areas. </p>
 |
| <p>
 |
| OpenUP is an iterative software development process that is minimal, complete, and extensible. It is governed by four
 |
| <a class="elementLinkWithUserText" href="./../../../openup/customcategories/core_principles_category_8075133D.html" guid="_UCOtoMXwEduywMSzPTUUwA">core principles</a>:
 |
| </p>
 |
| <ul>
 |
| <li> <a class="elementLinkWithUserText" href="./../../../openup/guidances/concepts/core_principle_collaborate_EC5EB51F.html" guid="_KkTIsMp7EdqC_NfSivunjA">Collaborate 
 |
| to align interests and share understanding</a> </li>
 |
| <li> <a class="elementLinkWithUserText" href="./../../../openup/guidances/concepts/core_principle_balance_793DD27.html" guid="_ssG6MMvpEdqukPpotm3DYg">Balance 
 |
| competing priorities to maximize stakeholder value</a> </li>
 |
| <li> <a class="elementLinkWithUserText" 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="elementLinkWithUserText" href="./../../../openup/guidances/concepts/core_principle_evolve_BFD9AEB4.html" guid="_GXiogMvoEdqukPpotm3DYg">Evolve 
 |
| to continuously obtain feedback and improve</a> </li>
 |
| </ul>
 |
| <p>People in <a class="elementLinkWithUserText" href="./../../../base_concepts/guidances/termdefinitions/role_37A0C602.html" guid="_yUefQNnmEdmO6L4XMImrsA">Roles</a>&nbsp;perform 
 |
| <a class="elementLinkWithUserText" href="./../../../base_concepts/guidances/termdefinitions/task_6C1FF051.html" guid="_x459ktnmEdmO6L4XMImrsA">tasks</a> 
 |
| that use and produce <a class="elementLinkWithUserText" href="./../../../base_concepts/guidances/termdefinitions/artifact_F635D25.html" guid="_x7cUM9nmEdmO6L4XMImrsA">artifacts</a>. 
 |
| OpenUP describes the minimal set of&nbsp;Roles, Tasks, and Artifacts&nbsp;involved 
 |
| in software development: </p>
 |
| <ul>
 |
| <li>
 |
| <a class="elementLinkWithUserText" href="./../../../openup/rolesets/openup_roles_5CDDEEDA.html" guid="_TZIJ0O8NEdmKSqa_gSYthg">Roles</a>
 |
| </li>
 |
| <li>
 |
| <a class="elementLinkWithUserText" href="./../../../openup/disciplinegroupings/openup_disciplines_AF6D7A8E.html" guid="__BZycP1UEdmek8CQTQgrOQ">Tasks</a> (organized by disciplines)
 |
| </li>
 |
| <li>
 |
| <a class="elementLinkWithUserText" href="./../../../openup/domains/openup_wp_E9648102.html" guid="_s4Z9AMWXEdqWePvIjHInwg">Artifacts</a> (organized by domains)&nbsp;
 |
| </li>
 |
| </ul>
 |
| <h4> The OpenUP software development&nbsp;lifecycle </h4>
 |
| <p> OpenUP is an iterative process&nbsp;distributed throughout&nbsp;four <a class="elementLinkWithUserText" href="./../../../base_concepts/guidances/concepts/phase_85B003C3.html" guid="__7xOEC7aEdqHMdmRzC0-2g">phases</a>: 
 |
| Inception, Elaboration, Construction, and Transition. Each phase consists of 
 |
| one or more iterations where stable, working versions of the software are developed 
 |
| and released, with the completion of each iteration representing a minor <a class="elementLinkWithUserText" href="./../../../openup/guidances/concepts/phase_milestones_5678231E.html" guid="_HNxbwMBJEdqSgKaj2SZBmg">milestone</a>&nbsp;for 
 |
| the project and contributing to the successful achievement of the phase's major 
 |
| milestone, where phase objectives are met. </p>
 |
| <p>
 |
| The following diagram depicts the OpenUP <a class="elementLinkWithUserText" href="./../../../openup/deliveryprocesses/openup_lifecycle_2CB8A7DA.html" guid="_0uyGoMlgEdmt3adZL5Dmdw">lifecycle</a>.
 |
| </p>
 |
| <p align="center"> <img height="192" alt="Figure 1: Diagram of the OpenUP Lifecycle" src="./resources/openup_lifecycle.jpg" width="667" usemap="#map" border="0" /> 
 |
| </p>
 |
| <p align="center">&nbsp; </p>
 |
| <h4>
 |
| How&nbsp;to get started?
 |
| </h4>
 |
| <p>
 |
| The fourth OpenUP core principle, "Evolve to continuously obtain feedback and improve", suggests an iterative and
 |
| incremental approach to adopting OpenUP.
 |
| </p> <ul> <li>
 |
| Start with the core principles and understand the intentions behind OpenUP.
 |
| </li> <li>
 |
| Then assess your existing process, and select one or two key areas that you would like to improve.
 |
| </li> <li>
 |
| Begin using OpenUP to improve these areas first.
 |
| </li> <li>
 |
| In later iterations or development cycles, make incremental improvements in other areas.
 |
| </li> <li>
 |
| If you have little or no experience with unified processes or other iterative processes, use OpenUP in a small
 |
| pilot project, perhaps with only three to four people working for only two to three months.
 |
| </li> </ul> <p>
 |
| While OpenUP is a ready to use as-is, you may choose to extend the process or modify the work product templates to
 |
| suit your specific needs. For example:
 |
| </p> <ul> <li>
 |
| You may require more or less precision in your work products.
 |
| </li> <li>
 |
| Your organization may have specific configuration management practices or safety protocols to include in your
 |
| process.
 |
| </li> <li>
 |
| You may simply want to put your own corporate logo on the banner.
 |
| </li> <li>
 |
| You may want to incorporate lessons learned from a retrospective review into OpenUP.
 |
| </li> </ul> <p>
 |
| Use EPF Composer to extend and tailor OpenUP. For more information about EPF composer, visit <a href="http://www.eclipse.org/epf" target="_blank">www.eclipse.org/epf</a>.
 |
| </p> 
 |
| <map id="Map" name="Map">
 |
| <area shape="rect" alt="link to inception phase concept" coords="116,7,175,25" href="./../../../openup/guidances/concepts/inception_phase_C4456871.html" guid="_0hmKgBOMEduCNqgZdt_OaA"></area></area>
 |
| <area shape="rect" alt="link to elaboration phase concept" coords="255,11,327,27" href="./../../../openup/guidances/concepts/elaboration_phase_BE880435.html" guid="_2plxwBOMEduCNqgZdt_OaA"></area></area>
 |
| <area shape="rect" alt="link to construction phase concept" coords="395,11,476,27" href="./../../../openup/guidances/concepts/construction_phase_873B6559.html" guid="_48EKsBOMEduCNqgZdt_OaA"></area></area>
 |
| <area shape="rect" alt="link to transition phase concept" coords="554,10,619,27" href="./../../../openup/guidances/concepts/transition_phase_DD5986E5.html" guid="__ca5UBOMEduCNqgZdt_OaA"></area></area>
 |
| <area shape="rect" alt="link to inception phase iteration delivery process" coords="39,98,100,162" href="./../../../openup/capabilitypatterns/inception_phase_iteration_C2188B46.html" guid="_0o3r4slgEdmt3adZL5Dmdw"></area></area>
 |
| 
 |
| <area shape="rect" alt="link to inception phase iteration delivery process" coords="188,100,250,169" href="./../../../openup/capabilitypatterns/elaboration_phase_iteration_97E7400D.html" guid="_0sTaYMlgEdmt3adZL5Dmdw">
 |
| </area></area>
 |
| <area shape="rect" alt="link to construction phase iteration delivery process" coords="332,100,397,165" href="./../../../openup/capabilitypatterns/construction_phase_iteration_FB82CA56.html" guid="_y-3IrutQEdqc1LGhiSPqRg"></area></area>
 |
| <area shape="rect" alt="link to transition phase iteration delivery process" coords="480,98,541,167" href="./../../../openup/capabilitypatterns/transition_phase_iteration_87676AD2.html" guid="_0rQRgMlgEdmt3adZL5Dmdw"></area></area>
 |
| </map></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
