| <?xml version="1.0" encoding="UTF-8"?> |
| <xmi:XMI 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"> |
| <org.eclipse.epf.uma:BreakdownElementDescription xmi:id="-eF2lt7VydLjXgYjekq1JYA" |
| name="lifecycle_objectives,_mRwHoMA9EdqSgKaj2SZBmg" guid="-eF2lt7VydLjXgYjekq1JYA"> |
| <mainDescription><p>
 |
| The Lifecycle Objectives Milestone is the first major project milestone. During the iteration <a class="elementLinkWithUserText" href="./../../openup_basic/tasks/assess_results.html" guid="_0l53cMlgEdmt3adZL5Dmdw">assessment</a>, the following evaluation criteria should be met <a class="elementlinkwithusertext" href="./../../openup_basic/guidances/supportingmaterials/references.html" guid="_9ToeIB83Edqsvps02rpOOg">[KRO03]</a>:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Stakeholder concurrence on
 |
| </li>
 |
| <li style="LIST-STYLE-TYPE: none">
 |
| <ul>
 |
| <li>
 |
| scope definition
 |
| </li>
 |
| <li>
 |
| initial cost and schedule estimates
 |
| </li>
 |
| <li>
 |
| definitions and priorities for initial set of requirements
 |
| </li>
 |
| <li>
 |
| risks identified and mitigation strategies proposed.
 |
| </li>
 |
| </ul>
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| <br />
 |
| Note:
 |
| </p>
 |
| <p>
 |
| The project may be aborted or reconsidered if it fails to reach this milestone.<br />
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:BreakdownElementDescription> |
| <org.eclipse.epf.uma:BreakdownElementDescription xmi:id="-io5IVl6cfL13mITtSQZ6qw" |
| name="lifecycle_architecture,_RYHw4MA-EdqSgKaj2SZBmg" guid="-io5IVl6cfL13mITtSQZ6qw"> |
| <mainDescription><p>
 |
| The Lifecycle Architecture Milestone is the&nbsp;second major project milestone. During iteration <a class="elementLinkWithUserText" href="./../../openup_basic/tasks/assess_results.html" guid="_0l53cMlgEdmt3adZL5Dmdw">assessments</a>&nbsp;in Elaboration, you should keep these&nbsp;evaluation
 |
| criteria&nbsp;in mind&nbsp;<a class="elementlinkwithusertext" href="./../../openup_basic/guidances/supportingmaterials/references.html" guid="_9ToeIB83Edqsvps02rpOOg">[KRO03]</a>:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Stability of Vision, requirements and Architecture.
 |
| </li>
 |
| <li>
 |
| Major risk elements addressed and resolved by testing and evaluating executable prototypes.
 |
| </li>
 |
| <li>
 |
| Construction iterations planned in sufficient detail and&nbsp;credibly estimated&nbsp;to allow the work to proceed.
 |
| </li>
 |
| <li>
 |
| Agreement of stakeholders that the current vision can be met if plans are executed to develop complete system on
 |
| top of current architecture.
 |
| </li>
 |
| <li>
 |
| Resourse expenditures versus planned expenditures are acceptable.<br />
 |
| </li>
 |
| </ul></mainDescription> |
| </org.eclipse.epf.uma:BreakdownElementDescription> |
| <org.eclipse.epf.uma:BreakdownElementDescription xmi:id="-ekFhym49Ew6H0sL1MJ5yNw" |
| name="initial_operational_capability,_TV_y0MA-EdqSgKaj2SZBmg" guid="-ekFhym49Ew6H0sL1MJ5yNw"> |
| <mainDescription><p>
 |
| The Initial Operational Capability&nbsp;Milestone is the&nbsp;third major project milestone. During iteration <a class="elementLinkWithUserText" href="./../../openup_basic/tasks/assess_results.html" guid="_0l53cMlgEdmt3adZL5Dmdw">assessments</a>&nbsp;in Construction, keep these&nbsp;evaluation criteria&nbsp;in
 |
| mind&nbsp;<a class="elementlinkwithusertext" href="./../../openup_basic/guidances/supportingmaterials/references.html" guid="_9ToeIB83Edqsvps02rpOOg">[KRO03]</a>:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Product release is stable and mature enough to be deployed in the user community.
 |
| </li>
 |
| <li style="LIST-STYLE-TYPE: none">
 |
| <ul>
 |
| <li>
 |
| The beta product is ready to be handed over to&nbsp;the users.
 |
| </li>
 |
| <li>
 |
| All functionality has been developed and all alpha testing (if any) has been completed.
 |
| </li>
 |
| <li>
 |
| In addition to the software, a user manual has been developed, and there is a description of the current
 |
| release.
 |
| </li>
 |
| </ul>
 |
| </li>
 |
| <li>
 |
| Actual resource expenditures compared to planned expenditures are acceptable.
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| Note:
 |
| </p>
 |
| <p>
 |
| In case the project fails to reach this milestone, an iteration can be added to Construction, thus postponing
 |
| Transition.
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:BreakdownElementDescription> |
| <org.eclipse.epf.uma:BreakdownElementDescription xmi:id="-jLx3JjiFCqSKsnGO-5SDKw" |
| name="product_release,_X3F_cMA-EdqSgKaj2SZBmg" guid="-jLx3JjiFCqSKsnGO-5SDKw"> |
| <mainDescription><p>
 |
| The Product Release Milestone is the last major project milestone. During iteration <a class="elementLinkWithUserText" href="./../../openup_basic/tasks/assess_results.html" guid="_0l53cMlgEdmt3adZL5Dmdw">assessment</a>, you decide if the objectives were met, and&nbsp;then close the
 |
| project.&nbsp;These are the evaluation criteria to keep in mind <a class="elementlinkwithusertext" href="./../../openup_basic/guidances/supportingmaterials/references.html" guid="_9ToeIB83Edqsvps02rpOOg">[KRO03]</a>:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Users satisfaction and product acceptance
 |
| </li>
 |
| <li>
 |
| Stakeholder concurrence on acceptable resource expenditures compared to planned expenditures
 |
| </li>
 |
| <li>
 |
| Product is in production; therefore, a new development cycle for enhancements or maintenance may start
 |
| </li>
 |
| </ul></mainDescription> |
| </org.eclipse.epf.uma:BreakdownElementDescription> |
| <org.eclipse.epf.uma:DeliveryProcessDescription xmi:id="-q6sRit33qxBD7OweLhVeQA" |
| guid="-q6sRit33qxBD7OweLhVeQA"> |
| <mainDescription><p>
 |
| OpenUP/Basic is an iterative process with <a class="elementlinkwithusertext" href="./../../openup_basic/guidances/concepts/core_principle_evolve.html" guid="_GXiogMvoEdqukPpotm3DYg">iterations</a>&nbsp;distributed throughout four <a class="elementLinkWithUserText" href="./../../base_concepts/guidances/concepts/phase.html" guid="__7xOEC7aEdqHMdmRzC0-2g">phases</a>: <a class="elementLinkWithUserText" href="./../../openup_basic/guidances/concepts/inception_phase.html" guid="_0hmKgBOMEduCNqgZdt_OaA">Inception</a>, <a class="elementLinkWithUserText" href="./../../openup_basic/guidances/concepts/elaboration_phase.html" guid="_2plxwBOMEduCNqgZdt_OaA">Elaboration</a>, <a class="elementLinkWithUserText" href="./../../openup_basic/guidances/concepts/construction_phase.html" guid="_48EKsBOMEduCNqgZdt_OaA">Construction</a>, and <a class="elementLinkWithUserText" href="./../../openup_basic/guidances/concepts/transition_phase.html" guid="__ca5UBOMEduCNqgZdt_OaA">Transition</a>.
 |
| </p>
 |
| <p>
 |
| Each phase may have as many iterations as needed, depending on degree of novelty of the business domain, technology
 |
| being used, architectural complexity, and project size, to name a few factors.
 |
| </p>
 |
| <p>
 |
| To offer a quick start for teams to plan their iterations,&nbsp;OpenUP/Basic provides&nbsp;work breakdown structure
 |
| (WBS) templates for each iteration and a WBS template for an end-to-end process.
 |
| </p>
 |
| <p>
 |
| Iterations may have variable lengths, depending on project characteristics. One-month iterations are typically
 |
| recommended, because this timeframe provides:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| A reasonable amount of time for projects to deliver meaningful increments in functionality
 |
| </li>
 |
| <li>
 |
| Early and frequent customer feedback
 |
| </li>
 |
| <li>
 |
| Timely management of risks and issues during the course of the project
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| OpenUP/Basic is intended to offer process guidance to small projects:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| <div class="O" style="mso-margin-left-alt: 216; mso-char-wrap: 1; mso-kinsoku-overflow: 1" v:shape="_x0000_s1026">
 |
| 3&nbsp;to&nbsp;6 people on the team
 |
| </div>
 |
| </li>
 |
| <li>
 |
| <div class="O" style="mso-margin-left-alt: 216; mso-char-wrap: 1; mso-kinsoku-overflow: 1" v:shape="_x0000_s1026">
 |
| 3&nbsp;to&nbsp;6 months of work
 |
| </div>
 |
| </li>
 |
| </ul></mainDescription> |
| <purpose><p>
 |
| The purposes of this delivery process are to:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Offer process guidance for small-scale projects
 |
| </li>
 |
| <li>
 |
| Allow project managers to create project plans based on the proposed work breakdown structures
 |
| </li>
 |
| <li>
 |
| Allow project managers to track status based on goals
 |
| </li>
 |
| <li>
 |
| Allow&nbsp;team members&nbsp;to understand how to perform their work to achieve project goals
 |
| </li>
 |
| <li>
 |
| Provide a complete, end-to-end delivery process that serves as an example for defining alternative delivery
 |
| processes
 |
| </li>
 |
| </ul></purpose> |
| </org.eclipse.epf.uma:DeliveryProcessDescription> |
| </xmi:XMI> |
