| <?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="-FrUmsKsGW4bnNmb9uaNOkg" name=",__ca5UBOMEduCNqgZdt_OaA" guid="-FrUmsKsGW4bnNmb9uaNOkg" changeDate="2006-09-27T16:29:45.049-0700" version="1.0.0"> |
| <mainDescription><p> |
| The purpose in this phase is to ensure that the software is ready for delivery to users. |
| </p> |
| <p> |
| There are objectives for the Transition phase that help you to&nbsp;fine-tune functionality, performance, and overall |
| quality of the beta product from the end of&nbsp;the previous phase <a class="elementlinkwithusertext" href="./../../../openup_basic/guidances/supportingmaterials/references,_9ToeIB83Edqsvps02rpOOg.html" guid="_9ToeIB83Edqsvps02rpOOg">[KRO03]</a>: |
| </p> |
| <ol> |
| <li> |
| <p> |
| <strong>Beta test to validate that user expectations are met.</strong> This typically requires some fine-tuning |
| activities, such as bug-fixing and making enhancements for performance and usability. |
| </p> |
| </li> |
| <li> |
| <p> |
| <strong>Achieve stakeholder concurrence that deployment is complete.</strong> This may involve various levels |
| of tests for product acceptance, including formal and informal tests and beta tests. |
| </p> |
| </li> |
| <li> |
| <p> |
| <strong>Improve future project performance through lessons learned.</strong> Document lessons learned and |
| improve the process and tool environment for the project. |
| </p> |
| </li> |
| </ol> |
| <p> |
| The following table summarizes the&nbsp;Transition phase objectives and&nbsp;what activities address each objective: |
| </p> |
| <p align="center"> |
| <strong>Transition phase objectives and activities</strong> |
| </p> |
| <table cellspacing="0" cellpadding="0" width="648" align="center" border="1"> |
| <tbody> |
| <tr> |
| <td class="Normal" valign="top" width="300"> |
| <p style="TEXT-ALIGN: justify"> |
| <b>Phase objectives</b> |
| </p> |
| </td> |
| <td class="Normal" valign="top" width="348"> |
| <p style="TEXT-ALIGN: justify"> |
| <b>Activities that address objectives</b> |
| </p> |
| </td> |
| </tr> |
| <tr> |
| <td class="Normal" valign="top" width="300" height="62"> |
| Beta test to validate that user expectations are met |
| </td> |
| <td class="Normal" valign="top" width="348"> |
| <a class="elementLinkWithUserText" href="./../../../ongoing_tasks,_0qxwYclgEdmt3adZL5Dmdw.html" guid="_0qxwYclgEdmt3adZL5Dmdw">Ongoing Tasks</a><br /> |
| <a class="elementLinkWithUserText" href="./../../../develop_requirement_within_context,_0DMlYPinEdmugcVr9AdHjQ.html" guid="_0DMlYPinEdmugcVr9AdHjQ">Develop Solution (for requirement)(within context)</a><br /> |
| <a class="elementLinkWithUserText" href="./../../../validate_build,_0qrpwslgEdmt3adZL5Dmdw.html" guid="_0qrpwslgEdmt3adZL5Dmdw">Validate Build</a> |
| </td> |
| </tr> |
| <tr> |
| <td class="Normal" valign="top" width="300"> |
| Achieve stakeholder concurrence that deployment is complete |
| </td> |
| <td class="Normal" valign="top" width="348"> |
| <a class="elementLinkWithUserText" href="./../../../manage_iteration,_0rWYIslgEdmt3adZL5Dmdw.html" guid="_0rWYIslgEdmt3adZL5Dmdw">Manage Iteration</a><br /> |
| <a class="elementLinkWithUserText" href="./../../../validate_build,_0qrpwslgEdmt3adZL5Dmdw.html" guid="_0qrpwslgEdmt3adZL5Dmdw">Validate Build</a> |
| </td> |
| </tr> |
| <tr> |
| <td class="Normal" valign="top" width="300"> |
| Improve future project performance through lessons learned |
| </td> |
| <td class="Normal" valign="top" width="348"> |
| <a class="elementLinkWithUserText" href="./../../../manage_iteration,_0rWYIslgEdmt3adZL5Dmdw.html" guid="_0rWYIslgEdmt3adZL5Dmdw">Manage Iteration</a> |
| </td> |
| </tr> |
| </tbody> |
| </table> |
| <h4> |
| <br /> |
| Key considerations<br /> |
| </h4> |
| <p> |
| The Transition phase can include running old and new systems in parallel, migrating data, training users, and adjusting |
| business processes. |
| </p> |
| <p> |
| The number of iterations in the Transition phase varies from one iteration for a simple system requiring primarily |
| minor bug fixing, to many iterations for a complex system, involving addition of features and performing activities to |
| make the business transition from using the old system to using the new system. |
| </p> |
| <p> |
| When the Transition phase objectives are met, the project is in position to be closed.&nbsp;For some products, the end |
| of the current project lifecycle may coincide with the beginning of the next lifecycle, leading to the next generation |
| of the same product. |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |