| <?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" epf:version="1.0.0" xmi:id="-DG8mYMnTGosWIxjPQFUoTA" name="milestones,_HNxbwMBJEdqSgKaj2SZBmg" guid="-DG8mYMnTGosWIxjPQFUoTA" changeDate="2006-10-31T12:53:11.446-0800"> |
| <mainDescription><p> |
| Milestones are&nbsp;the point at which an iteration or phase formally ends. |
| </p> |
| <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> |
| However, there are four major milestones that provide evaluation criteria at the end of each phase. 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_basic/guidances/supportingmaterials/references,_9ToeIB83Edqsvps02rpOOg.html" guid="_9ToeIB83Edqsvps02rpOOg">BOE95</a>]. |
| </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 essentially a span of time between two major milestones. 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. |
| </p> |
| <p> |
| At the end of the <strong>Inception</strong> phase 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 <strong>Elaboration</strong> phase 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. |
| </p> |
| <p> |
| At the end of the <strong>Construction</strong> phase 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 <strong>Transition</strong> phase 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> |