| <?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:rmc="http://www.ibm.com/rmc" rmc:version="7.5.0" xmlns:epf="http://www.eclipse.org/epf" |
| epf:version="1.5.0" xmi:id="-F-eWIBzxEXE1jygbN3nrrQ" |
| name=",_2plxwBOMEduCNqgZdt_OaA" guid="-F-eWIBzxEXE1jygbN3nrrQ" changeDate="2008-02-24T08:14:58.015-0800" |
| 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="./../../../core.mgmt.common.base/guidances/supportingmaterials/references.mgmt_D80619F3.html#KRO03" guid="_JlTPUM6aEdyuBO4ZIzcyig">[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 enables 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<i> an</i><strong> </strong><i>executable architecture</i>. 
 |
| </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>
 |
| <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 compared to maintenance 
 |
| cycle, unprecedented system compared to well-known technology and architecture, 
 |
| and so on. </p>
 |
| <p> Typically, on the first iteration, it is better to 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> During the subsequent 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 that potential risks are identified as early as 
 |
| possible. <a class="elementlinkwithusertext" href="./../../../core.tech.common.base/guidances/supportingmaterials/references.tech_6CCF393.html" guid="_9ToeIB83Edqsvps02rpOOg">[KRO03]</a> 
 |
| </p>
 |
| <p>
 |
| <br />
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
