| <?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="-DG8mYMnTGosWIxjPQFUoTA" |
| name="phase_milestones,_HNxbwMBJEdqSgKaj2SZBmg" guid="-DG8mYMnTGosWIxjPQFUoTA" |
| changeDate="2007-05-22T16:13:10.217-0700" version="1.0.0"> |
| <mainDescription><p>
 |
| From a&nbsp;development perspective, each iteration provides an increment of functionality to the product. Thus, the
 |
| end of each iteration corresponds to a checkpoint where the project team demonstrates to stakeholders that the
 |
| objectives for that iteration have been met.
 |
| </p>
 |
| <p>
 |
| From a management perspective, the software lifecycle&nbsp;is decomposed over time into four sequential phases, each
 |
| concluded by a major milestone [<a class="elementLinkWithUserText" href="./../../../openup/guidances/supportingmaterials/references_6CCF393.html" guid="_9ToeIB83Edqsvps02rpOOg">BOE95</a>].
 |
| There are four major milestones that provide evaluation criteria at the end of each phase.
 |
| </p>
 |
| <p class="banner" align="center">
 |
| <img height="156" alt="Click on text for more information about phases and milestones" src="./resources/co_phas1.gif" width="406" border="0" />
 |
| </p>
 |
| <p class="picturetext" align="center">
 |
| The phases and milestones of a project
 |
| </p>
 |
| <p>
 |
| Each phase is&nbsp;a span of time between two major milestones and has specific focus and objectives. At each phase-end
 |
| an assessment is performed to determine whether the objectives of the phase have been met. A satisfactory assessment
 |
| allows the project to move to the next phase. When a milestone is not met, more iterations in the current phase may be
 |
| performed before the milestone can be considered complete. Achieving a milestone represents an objective criteria with
 |
| which to measure progress.
 |
| </p>
 |
| <p>
 |
| At the end of the <a class="elementLink" href="./../../../openup/guidances/concepts/inception_phase_C4456871.html" guid="_0hmKgBOMEduCNqgZdt_OaA">Inception Phase</a> is the first major project milestone or <strong>Lifecycle Objectives
 |
| Milestone</strong>. At this point, you examine the cost versus benefits of the project, and decide either to proceed
 |
| with the project or to cancel it.
 |
| </p>
 |
| <p>
 |
| At the end of the <a class="elementLink" href="./../../../openup/guidances/concepts/elaboration_phase_BE880435.html" guid="_2plxwBOMEduCNqgZdt_OaA">Elaboration Phase</a>&nbsp;is the second important project milestone, the
 |
| <strong>Lifecycle Architecture Milestone</strong>. At this point, a baseline of requirements is agreed to, you examine
 |
| the detailed system objectives and scope, the choice of architecture, and the resolution of the major risks. The
 |
| milestone is achieved when the architecture has been validated.
 |
| </p>
 |
| <p>
 |
| At the end of the <a class="elementLink" href="./../../../openup/guidances/concepts/construction_phase_873B6559.html" guid="_48EKsBOMEduCNqgZdt_OaA">Construction Phase</a><strong>&nbsp;</strong>is the third important project milestone,
 |
| the <strong>Initial Operational Capability Milestone</strong>. At this point, the product is ready to be handed over to
 |
| the transition team. All functionality has been developed and all alpha testing (if any) has been completed. In
 |
| addition to the software, a user manual has been developed, and there is a description of the current release. The
 |
| product is ready for beta testing.
 |
| </p>
 |
| <p>
 |
| At the end of the <a class="elementLink" href="./../../../openup/guidances/concepts/transition_phase_DD5986E5.html" guid="__ca5UBOMEduCNqgZdt_OaA">Transition Phase</a><strong>&nbsp;</strong>is the fourth important project milestone,
 |
| the <strong>Product Release Milestone</strong>. At this point, you decide if the objectives were met, and if you should
 |
| start another development cycle. The Product Release Milestone is the result of the customer reviewing and accepting
 |
| the project deliverables.
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
