| <?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_basic\guidances\roadmaps\openup_basic_roadmap.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_basic_roadmap.xmi<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: presentationName<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:presentationName,_vEruwN-rEdqiM_wFaqLjNg CRC: 561715492 -->OpenUP/Basic Roadmap<!-- END:presentationName,_vEruwN-rEdqiM_wFaqLjNg --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: briefDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:briefDescription,_vEruwN-rEdqiM_wFaqLjNg CRC: 1540090830 -->This roadmap presents an overview of OpenUP/Basic, its purpose and lifecycle.<!-- END:briefDescription,_vEruwN-rEdqiM_wFaqLjNg --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: mainDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:mainDescription,-At_b3UIzbgdmtJsb2Ymfhg CRC: 4143424056 --><h3> |
| Introduction |
| </h3> |
| <p> |
| OpenUP/Basic is for small teams, working 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. |
| Team members engage in significant collaboration, making their own decisions as to what needs to be worked on, what the |
| priorities are, and how best to address stakeholder needs. The organization must support the team by allowing them this |
| responsibility. |
| </p> |
| <p> |
| Team members collaborate extensively. The presence of stakeholders as team members is critical to successfully |
| realizing OpenUP/Basic. |
| </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/Basic focuses on signficantly 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 Item List. Team mebers 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. Team members should develop skills at writing good use cases. |
| Stakeholders are responsbile for reviewing and certifying the requirements are correct. Use cases are developed |
| collaboratively. |
| </p> |
| <p> |
| Architecturally significant requirements must be identified and stabilized in Elaboration so a robust architecture can |
| be created that is the core of the system. An architecturally significant requirement change may arise later in |
| development that must be addressed, but the risk of this happening is significantly reduced in the Elaboration |
| iteration. |
| </p> |
| <p> |
| Testing is performed.... |
| </p> |
| <p> |
| OpenUP/Basic doesn't include content for deployment, change management, or environment (such as customizing this |
| process or setting up development environments). OpenUP/Basic is focused 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.<br /> |
| </p> |
| <p> |
| OpenUP/Basic is an iterative software development process that is minimal, complete, and extensible. It is governed by |
| four core <a class="elementLinkWithUserText" |
| href="./../../../openup_basic/customcategories/core_principles_cat,_HEu9QBOHEduCNqgZdt_OaA.html" |
| guid="_HEu9QBOHEduCNqgZdt_OaA">principles</a>: |
| </p> |
| <ul> |
| <li> |
| Balance competing priorities to maximize stakeholder value. |
| </li> |
| <li> |
| Collaborate to align interests and share understanding |
| </li> |
| <li> |
| Evolve to continuously obtain feedback and improve |
| </li> |
| <li> |
| Focus on articulating the architecture |
| </li> |
| </ul> |
| <p> |
| <a class="elementLinkWithUserText" |
| href="./../../../base_concepts/guidances/termdefinitions/role,_yUefQNnmEdmO6L4XMImrsA.html" |
| guid="_yUefQNnmEdmO6L4XMImrsA">Roles</a> perform <a class="elementLinkWithUserText" |
| href="./../../../base_concepts/guidances/termdefinitions/task,_x459ktnmEdmO6L4XMImrsA.html" |
| guid="_x459ktnmEdmO6L4XMImrsA">tasks</a> that consume and produce <a class="elementLinkWithUserText" |
| href="./../../../base_concepts/guidances/termdefinitions/artifact,_x7cUM9nmEdmO6L4XMImrsA.html" |
| guid="_x7cUM9nmEdmO6L4XMImrsA">artifacts</a>. OpenUP/Basic describes the minimal set of roles, tasks, and |
| artifacts involved in software development: |
| </p> |
| <ul> |
| <li> |
| <a class="elementLinkWithUserText" |
| href="./../../../openup_basic/rolesets/openup_basic_roles,_TZIJ0O8NEdmKSqa_gSYthg.html" |
| guid="_TZIJ0O8NEdmKSqa_gSYthg">Roles</a> |
| </li> |
| <li> |
| <a class="elementLinkWithUserText" |
| href="./../../../openup_basic/disciplinegroupings/openup_basic_disciplines,__BZycP1UEdmek8CQTQgrOQ.html" |
| guid="__BZycP1UEdmek8CQTQgrOQ">Tasks</a> (organized by disciplines) |
| </li> |
| <li> |
| <a class="elementLinkWithUserText" |
| href="./../../../openup_basic/domains/openup_basic_wp,_s4Z9AMWXEdqWePvIjHInwg.html" |
| guid="_s4Z9AMWXEdqWePvIjHInwg">Artifacts</a> (organized by domains) |
| </li> |
| </ul> |
| <h3> |
| Software development lifecycle |
| </h3> |
| <p> |
| OpenUP/Basic is an iterative process distributed throughout four <a class="elementLinkWithUserText" |
| href="./../../../base_concepts/guidances/concepts/phase,__7xOEC7aEdqHMdmRzC0-2g.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_basic/guidances/concepts/milestones,_HNxbwMBJEdqSgKaj2SZBmg.html" |
| guid="_HNxbwMBJEdqSgKaj2SZBmg">milestone</a> 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/Basic <a class="elementLinkWithUserText" |
| href="./../../../openup_basic/deliveryprocesses/openup_basic_process,_0uyGoMlgEdmt3adZL5Dmdw.html" |
| guid="_0uyGoMlgEdmt3adZL5Dmdw">lifecycle</a>. |
| </p> |
| <p align="center"> |
| <img height="192" alt="Figure 1: Diagram of the OpenUP/Basic Lifecycle" src="./resources/openup-basic_lifecycle.jpg" |
| width="667" usemap="#Map" border="0" /> |
| </p> |
| <p align="center"> |
| Figure 1: The OpenUP/Basic lifecycle |
| </p> |
| <map id="Map" name="Map"> |
| <h4> |
| How 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/Basic. |
| </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/Basic 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/Basic in a |
| small pilot project, perhaps with only three to four people working for only two to three months. |
| </li> |
| </ul> |
| <p> |
| While OpenUP/Basic 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/Basic. |
| </li> |
| </ul> |
| <p> |
| Use EPF Composer to extend and tailor OpenUP/Basic. For more information about EPF composer, visit <a |
| href="http://www.eclipse.org/epf" target="_blank">www.eclipse.org/epf</a>. |
| </p> |
| <area shape="RECT" coords="116,7,175,25" alt="link to inception phase concept" |
| href="./../../../openup_basic/guidances/concepts/inception_phase,_0hmKgBOMEduCNqgZdt_OaA.html" |
| guid="_0hmKgBOMEduCNqgZdt_OaA" /> |
| <area shape="RECT" coords="255,11,327,27" alt="link to elaboration phase concept" |
| href="./../../../openup_basic/guidances/concepts/elaboration_phase,_2plxwBOMEduCNqgZdt_OaA.html" |
| guid="_2plxwBOMEduCNqgZdt_OaA" /> |
| <area shape="RECT" coords="395,11,476,27" alt="link to construction phase concept" |
| href="./../../../openup_basic/guidances/concepts/construction_phase,_48EKsBOMEduCNqgZdt_OaA.html" |
| guid="_48EKsBOMEduCNqgZdt_OaA" /> |
| <area shape="RECT" coords="554,10,619,27" alt="link to transition phase concept" |
| href="./../../../openup_basic/guidances/concepts/transition_phase,__ca5UBOMEduCNqgZdt_OaA.html" |
| guid="__ca5UBOMEduCNqgZdt_OaA" /> |
| <area shape="RECT" coords="39,98,100,162" alt="link to inception phase iteration delivery process" |
| href="./../../../openup_basic/deliveryprocesses/inception_phase_iteration,_xupMvxOKEduCNqgZdt_OaA.html" |
| guid="_xupMvxOKEduCNqgZdt_OaA" /> |
| <area shape="RECT" coords="188,99,250,168" alt="link to inception phase iteration delivery process" |
| href="./../../../openup_basic/deliveryprocesses/elaboration_phase_iteration,_0Spa4BOKEduCNqgZdt_OaA.html" |
| guid="_0Spa4BOKEduCNqgZdt_OaA" /> |
| <area shape="RECT" coords="332,100,397,165" alt="link to construction phase iteration delivery process" |
| href="./../../../openup_basic/deliveryprocesses/construction_phase_iteration,_3CqrAROKEduCNqgZdt_OaA.html" |
| guid="_3CqrAROKEduCNqgZdt_OaA" /> |
| <area shape="RECT" coords="480,98,541,167" alt="link to transition phase iteration delivery process" |
| href="./../../../openup_basic/deliveryprocesses/transition_phase_iteration,_467NIhOKEduCNqgZdt_OaA.html" |
| guid="_467NIhOKEduCNqgZdt_OaA" /> |
| </map><!-- END:mainDescription,-At_b3UIzbgdmtJsb2Ymfhg --> |
| </body> |
| </html> |