| <?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="-F-eWIBzxEXE1jygbN3nrrQ" name=",_2plxwBOMEduCNqgZdt_OaA" guid="-F-eWIBzxEXE1jygbN3nrrQ" changeDate="2006-09-27T16:28:27.954-0700" version="1.0.0"> |
| <mainDescription><p> |
| The purpose of this phase is to establish the baseline of the architecture of the system and provide a stable basis for |
| the bulk of the&nbsp;development effort in the next phase. |
| </p> |
| <p> |
| There are objectives for the Elaboration phase that help you address risks associated with requirements, architecture, |
| costs, and schedule <a class="elementlinkwithusertext" href="./../../../openup_basic/guidances/supportingmaterials/references,_9ToeIB83Edqsvps02rpOOg.html" guid="_9ToeIB83Edqsvps02rpOOg">[KRO03]</a>: |
| </p> |
| <ul> |
| <li> |
| <p> |
| <strong>Get a more detailed understanding of the requirements.</strong> Having a good understanding of the |
| majority of requirements allows you to create a more detailed plan and to get buy-in from stakeholders. Be sure |
| to gain an in-depth understanding of the most critical requirements to be validated by&nbsp;the architecture. |
| </p> |
| </li> |
| <li> |
| <p> |
| <strong>Design, implement, validate, and establish the baseline for the architecture.</strong> Design, |
| implement, and test a skeleton structure of the system. Although the functionality is not complete yet, most of |
| the interfaces between the building blocks are implemented and tested. This is referred to <strong>an |
| executable architecture</strong>. |
| </p> |
| </li> |
| <li> |
| <p> |
| <strong>Mitigate essential risks, and produce accurate schedule and cost estimates.</strong> Many technical |
| risks are addressed as a result of detailing the requirements and of designing, implementing, and testing the |
| architecture. Refine and detail the high-level project plan. |
| </p> |
| </li> |
| </ul> |
| <p> |
| The following table summarizes the&nbsp;Elaboration phase objectives and&nbsp;what activities address each objective: |
| </p> |
| <p align="center"> |
| <strong>Elaboration 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"> |
| Get a more detailed understanding of the requirements |
| </td> |
| <td class="Normal" valign="top" width="348"> |
| <a class="elementLinkWithUserText" href="./../../../manage_requirements,_0ruyoclgEdmt3adZL5Dmdw.html" guid="_0ruyoclgEdmt3adZL5Dmdw">Manage Requirements</a> <br /> |
| </td> |
| </tr> |
| <tr> |
| <td class="Normal" valign="top" width="300"> |
| Design, implement, validate, and baseline an architecture |
| </td> |
| <td class="Normal" valign="top" width="348"> |
| <p style="TEXT-ALIGN: justify"> |
| <a class="elementLinkWithUserText" href="./../../../define_architecture,_0rcewclgEdmt3adZL5Dmdw.html" guid="_0rcewclgEdmt3adZL5Dmdw">Define the Architecture</a><br /> |
| <a class="elementLinkWithUserText" href="./../../../develop_requirement_within_context,_WrXvwPinEdmugcVr9AdHjQ.html" guid="_WrXvwPinEdmugcVr9AdHjQ">Develop Solution (for requirement)(within context)</a><br /> |
| <a class="elementLinkWithUserText" href="./../../../validate_build,_0rilYclgEdmt3adZL5Dmdw.html" guid="_0rilYclgEdmt3adZL5Dmdw">Validate Build</a> |
| </p> |
| </td> |
| </tr> |
| <tr> |
| <td class="Normal" valign="top" width="300"> |
| Mitigate essential risks, and produce accurate schedule and cost estimates |
| </td> |
| <td class="Normal" valign="top" width="348"> |
| <a class="elementLinkWithUserText" href="./../../../manage_iteration,_0rWYIslgEdmt3adZL5Dmdw.html" guid="_0rWYIslgEdmt3adZL5Dmdw">Manage Iteration</a> <br /> |
| </td> |
| </tr> |
| </tbody> |
| </table> |
| <br /> |
| <h4> |
| Key considerations |
| </h4> |
| <p> |
| The number of iterations in the Elaboration phase is dependent on, but not limited to, factors such as green-field |
| development versus maintenance cycle, unprecedented system versus well-known technology and architecture, and so on. |
| </p> |
| <p> |
| Typically, on the first iteration, you should design, implement, and test a small number of critical scenarios to |
| identify what type of architecture and architectural mechanisms you need, so you can mitigate the most crucial risks. |
| You also detail high-risk requirements that have to be addressed early in the project. You test enough to validate that |
| the architectural risks are mitigated. |
| </p> |
| <p> |
| On the following iterations, you fix whatever was not right from the previous iteration. You design, implement, and |
| test the remaining architecturally significant scenarios, ensuring that you check all major areas of the system |
| (architectural coverage), so potential hidden risks arise as early as possible. <a class="elementlinkwithusertext" href="./../../../openup_basic/guidances/supportingmaterials/references,_9ToeIB83Edqsvps02rpOOg.html" guid="_9ToeIB83Edqsvps02rpOOg">[KRO03]</a> |
| </p> |
| <p> |
| <br /> |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |