OpenUP/OpenUP_SP/library/openup_basic/guidances/roadmaps/openup_basic_roadmap.xmi - epf/org.eclipse.epf.nl-libraries - Git at Google

 <?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.3/uma.ecore" rmc:version="7.1.0" epf:version="1.0.0" xmi:id="-At_b3UIzbgdmtJsb2Ymfhg" name="new_roadmap,_vEruwN-rEdqiM_wFaqLjNg" guid="-At_b3UIzbgdmtJsb2Ymfhg" changeDate="2007-03-01T10:29:08.857-0800" version="1.0.0">
   <mainDescription>&lt;h3&gt;
     Introduction
 &lt;/h3&gt;
 &lt;p&gt;
     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.
 &lt;/p&gt;
 &lt;p&gt;
     Team members collaborate extensively. The presence of stakeholders as team members is critical to successfully
     realizing OpenUP/Basic.
 &lt;/p&gt;
 &lt;p&gt;
     Team members participate in daily stand-up meetings to communicate status and issues. Problems are addressed outside of
     the daily meetings.
 &lt;/p&gt;
 &lt;p&gt;
     OpenUP/Basic focuses on signficantly&amp;nbsp;reducing risk early in the lifecycle. This requires regular risk review
     meetings and rigorous implementation of mitigation strategies.
 &lt;/p&gt;
 &lt;p&gt;
     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.
 &lt;/p&gt;
 &lt;p&gt;
     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.
 &lt;/p&gt;
 &lt;p&gt;
     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.
 &lt;/p&gt;
 &lt;p&gt;
     Testing is performed....
 &lt;/p&gt;
 &lt;p&gt;
     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.&lt;br /&gt;
 &lt;/p&gt;
 &lt;p&gt;
     OpenUP/Basic is an iterative software development process that is minimal, complete, and extensible. It is governed by
     four core &lt;a class=&quot;elementLinkWithUserText&quot;
     href=&quot;./../../../openup_basic/customcategories/core_principles_cat,_HEu9QBOHEduCNqgZdt_OaA.html&quot;
     guid=&quot;_HEu9QBOHEduCNqgZdt_OaA&quot;&gt;principles&lt;/a&gt;:
 &lt;/p&gt;
 &lt;ul&gt;
     &lt;li&gt;
         Balance competing priorities to maximize stakeholder value.
     &lt;/li&gt;
     &lt;li&gt;
         Collaborate to align interests and share understanding
     &lt;/li&gt;
     &lt;li&gt;
         Evolve to continuously obtain feedback and improve
     &lt;/li&gt;
     &lt;li&gt;
         Focus on articulating the architecture
     &lt;/li&gt;
 &lt;/ul&gt;
 &lt;p&gt;
     &lt;a class=&quot;elementLinkWithUserText&quot;
     href=&quot;./../../../base_concepts/guidances/termdefinitions/role,_yUefQNnmEdmO6L4XMImrsA.html&quot;
     guid=&quot;_yUefQNnmEdmO6L4XMImrsA&quot;&gt;Roles&lt;/a&gt;&amp;nbsp;perform &lt;a class=&quot;elementLinkWithUserText&quot;
     href=&quot;./../../../base_concepts/guidances/termdefinitions/task,_x459ktnmEdmO6L4XMImrsA.html&quot;
     guid=&quot;_x459ktnmEdmO6L4XMImrsA&quot;&gt;tasks&lt;/a&gt; that consume and produce &lt;a class=&quot;elementLinkWithUserText&quot;
     href=&quot;./../../../base_concepts/guidances/termdefinitions/artifact,_x7cUM9nmEdmO6L4XMImrsA.html&quot;
     guid=&quot;_x7cUM9nmEdmO6L4XMImrsA&quot;&gt;artifacts&lt;/a&gt;. OpenUP/Basic describes the minimal set of&amp;nbsp;roles, tasks, and
     artifacts&amp;nbsp;involved in software development:
 &lt;/p&gt;
 &lt;ul&gt;
     &lt;li&gt;
         &lt;a class=&quot;elementLinkWithUserText&quot;
         href=&quot;./../../../openup_basic/rolesets/openup_basic_roles,_TZIJ0O8NEdmKSqa_gSYthg.html&quot;
         guid=&quot;_TZIJ0O8NEdmKSqa_gSYthg&quot;&gt;Roles&lt;/a&gt;
     &lt;/li&gt;
     &lt;li&gt;
         &lt;a class=&quot;elementLinkWithUserText&quot;
         href=&quot;./../../../openup_basic/disciplinegroupings/openup_basic_disciplines,__BZycP1UEdmek8CQTQgrOQ.html&quot;
         guid=&quot;__BZycP1UEdmek8CQTQgrOQ&quot;&gt;Tasks&lt;/a&gt; (organized by disciplines)
     &lt;/li&gt;
     &lt;li&gt;
         &lt;a class=&quot;elementLinkWithUserText&quot;
         href=&quot;./../../../openup_basic/domains/openup_basic_wp,_s4Z9AMWXEdqWePvIjHInwg.html&quot;
         guid=&quot;_s4Z9AMWXEdqWePvIjHInwg&quot;&gt;Artifacts&lt;/a&gt; (organized by domains)&amp;nbsp;
     &lt;/li&gt;
 &lt;/ul&gt;
 &lt;h3&gt;
     Software development&amp;nbsp;lifecycle
 &lt;/h3&gt;
 &lt;p&gt;
     OpenUP/Basic is an iterative process&amp;nbsp;distributed throughout&amp;nbsp;four &lt;a class=&quot;elementLinkWithUserText&quot;
     href=&quot;./../../../base_concepts/guidances/concepts/phase,__7xOEC7aEdqHMdmRzC0-2g.html&quot;
     guid=&quot;__7xOEC7aEdqHMdmRzC0-2g&quot;&gt;phases&lt;/a&gt;: 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 &lt;a class=&quot;elementLinkWithUserText&quot;
     href=&quot;./../../../openup_basic/guidances/concepts/milestones,_HNxbwMBJEdqSgKaj2SZBmg.html&quot;
     guid=&quot;_HNxbwMBJEdqSgKaj2SZBmg&quot;&gt;milestone&lt;/a&gt;&amp;nbsp;for the project and contributing to the successful achievement of the
     Phase's major milestone where phase objectives are met.
 &lt;/p&gt;
 &lt;p&gt;
     The following diagram depicts the OpenUP/Basic &lt;a class=&quot;elementLinkWithUserText&quot;
     href=&quot;./../../../openup_basic/deliveryprocesses/openup_basic_process,_0uyGoMlgEdmt3adZL5Dmdw.html&quot;
     guid=&quot;_0uyGoMlgEdmt3adZL5Dmdw&quot;&gt;lifecycle&lt;/a&gt;.
 &lt;/p&gt;
 &lt;p align=&quot;center&quot;&gt;
     &lt;img height=&quot;192&quot; alt=&quot;Figure 1: Diagram of the OpenUP/Basic Lifecycle&quot; src=&quot;./resources/openup-basic_lifecycle.jpg&quot;
     width=&quot;667&quot; usemap=&quot;#Map&quot; border=&quot;0&quot; /&gt;
 &lt;/p&gt;
 &lt;p align=&quot;center&quot;&gt;
     Figure 1: The OpenUP/Basic lifecycle
 &lt;/p&gt;
 &lt;map id=&quot;Map&quot; name=&quot;Map&quot;&gt;
     &lt;h4&gt;
         How&amp;nbsp;to get started?
     &lt;/h4&gt;
     &lt;p&gt;
         The fourth OpenUP core principle, &quot;Evolve to continuously obtain feedback and improve&quot;, suggests an iterative and
         incremental approach to adopting OpenUP/Basic.
     &lt;/p&gt;
     &lt;ul&gt;
         &lt;li&gt;
             Start with the core principles and understand the intentions behind OpenUP.
         &lt;/li&gt;
         &lt;li&gt;
             Then assess your existing process, and select one or two key areas that you would like to improve.
         &lt;/li&gt;
         &lt;li&gt;
             Begin using OpenUP/Basic to improve these areas first.
         &lt;/li&gt;
         &lt;li&gt;
             In later iterations or development cycles, make incremental improvements in other areas.
         &lt;/li&gt;
         &lt;li&gt;
             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.
         &lt;/li&gt;
     &lt;/ul&gt;
     &lt;p&gt;
         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:
     &lt;/p&gt;
     &lt;ul&gt;
         &lt;li&gt;
             You may require more or less precision in your work products.
         &lt;/li&gt;
         &lt;li&gt;
             Your organization may have specific configuration management practices or safety protocols to include in your
             process.
         &lt;/li&gt;
         &lt;li&gt;
             You may simply want to put your own corporate logo on the banner.
         &lt;/li&gt;
         &lt;li&gt;
             You may want to incorporate lessons learned from a retrospective review into OpenUP/Basic.
         &lt;/li&gt;
     &lt;/ul&gt;
     &lt;p&gt;
         Use EPF Composer to extend and tailor OpenUP/Basic. For more information about EPF composer, visit &lt;a
         href=&quot;http://www.eclipse.org/epf&quot; target=&quot;_blank&quot;&gt;www.eclipse.org/epf&lt;/a&gt;.
     &lt;/p&gt;
     &lt;area shape=&quot;RECT&quot; coords=&quot;116,7,175,25&quot; alt=&quot;link to inception phase concept&quot;
     href=&quot;./../../../openup_basic/guidances/concepts/inception_phase,_0hmKgBOMEduCNqgZdt_OaA.html&quot;
     guid=&quot;_0hmKgBOMEduCNqgZdt_OaA&quot; /&gt;
     &lt;area shape=&quot;RECT&quot; coords=&quot;255,11,327,27&quot; alt=&quot;link to elaboration phase concept&quot;
     href=&quot;./../../../openup_basic/guidances/concepts/elaboration_phase,_2plxwBOMEduCNqgZdt_OaA.html&quot;
     guid=&quot;_2plxwBOMEduCNqgZdt_OaA&quot; /&gt;
     &lt;area shape=&quot;RECT&quot; coords=&quot;395,11,476,27&quot; alt=&quot;link to construction phase concept&quot;
     href=&quot;./../../../openup_basic/guidances/concepts/construction_phase,_48EKsBOMEduCNqgZdt_OaA.html&quot;
     guid=&quot;_48EKsBOMEduCNqgZdt_OaA&quot; /&gt;
     &lt;area shape=&quot;RECT&quot; coords=&quot;554,10,619,27&quot; alt=&quot;link to transition phase concept&quot;
     href=&quot;./../../../openup_basic/guidances/concepts/transition_phase,__ca5UBOMEduCNqgZdt_OaA.html&quot;
     guid=&quot;__ca5UBOMEduCNqgZdt_OaA&quot; /&gt;
     &lt;area shape=&quot;RECT&quot; coords=&quot;39,98,100,162&quot; alt=&quot;link to inception phase iteration delivery process&quot;
     href=&quot;./../../../openup_basic/deliveryprocesses/inception_phase_iteration,_xupMvxOKEduCNqgZdt_OaA.html&quot;
     guid=&quot;_xupMvxOKEduCNqgZdt_OaA&quot; /&gt;
     &lt;area shape=&quot;RECT&quot; coords=&quot;188,99,250,168&quot; alt=&quot;link to inception phase iteration delivery process&quot;
     href=&quot;./../../../openup_basic/deliveryprocesses/elaboration_phase_iteration,_0Spa4BOKEduCNqgZdt_OaA.html&quot;
     guid=&quot;_0Spa4BOKEduCNqgZdt_OaA&quot; /&gt;
     &lt;area shape=&quot;RECT&quot; coords=&quot;332,100,397,165&quot; alt=&quot;link to construction phase iteration delivery process&quot;
     href=&quot;./../../../openup_basic/deliveryprocesses/construction_phase_iteration,_3CqrAROKEduCNqgZdt_OaA.html&quot;
     guid=&quot;_3CqrAROKEduCNqgZdt_OaA&quot; /&gt;
     &lt;area shape=&quot;RECT&quot; coords=&quot;480,98,541,167&quot; alt=&quot;link to transition phase iteration delivery process&quot;
     href=&quot;./../../../openup_basic/deliveryprocesses/transition_phase_iteration,_467NIhOKEduCNqgZdt_OaA.html&quot;
     guid=&quot;_467NIhOKEduCNqgZdt_OaA&quot; /&gt;
 &lt;/map&gt;</mainDescription>
 </org.eclipse.epf.uma:ContentDescription>
	<?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.3/uma.ecore" rmc:version="7.1.0" epf:version="1.0.0" xmi:id="-At_b3UIzbgdmtJsb2Ymfhg" name="new_roadmap,_vEruwN-rEdqiM_wFaqLjNg" guid="-At_b3UIzbgdmtJsb2Ymfhg" changeDate="2007-03-01T10:29:08.857-0800" version="1.0.0">
	<mainDescription><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&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 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>&nbsp;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&nbsp;roles, tasks, and
	artifacts&nbsp;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)&nbsp;
	</li>
	</ul>
	<h3>
	Software development&nbsp;lifecycle
	</h3>
	<p>
	OpenUP/Basic is an iterative process&nbsp;distributed throughout&nbsp;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>&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/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&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/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></mainDescription>
	</org.eclipse.epf.uma:ContentDescription>