| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ProcessDescription 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="_mtb_DvL5Edm6Nvont3uinw" |
| guid="_mtb_DvL5Edm6Nvont3uinw" version="1.0.0"> |
| <mainDescription><p>
 |
| This activity refines the initial high-level architecture into working software. The objective is to produce
 |
| stable software that adequately addresses the technical risks in scope.
 |
| </p>
 |
| <p>
 |
| The architect and developers work together to:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Refine the initial sketch of the architecture into concrete design elements
 |
| </li>
 |
| <li>
 |
| Ensure that the architecture decisions are adequately captured and communicated
 |
| </li>
 |
| <li>
 |
| Ensure that the team has enough information to enable software to be developed
 |
| </li>
 |
| <li>
 |
| Ensure that the requirements that were prioritized for the current iteration are adequately addressed in the software
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| In an iterative project, the team should not attempt to develop the architecture for the entire project in a
 |
| single pass. Rather, they should focus on meeting the requirements in scope for the current iteration, while making
 |
| decisions in the context of the wider project.
 |
| </p></mainDescription> |
| <howtoStaff><p>
 |
| 
 |
| These activities are best carried out as a collaborative effort by the team, with the architect acting as a focal
 |
| 
 |
| point for coordinating and facilitating the decisions.
 |
| 
 |
| </p></howtoStaff> |
| <usageNotes><p>
 |
| 
 |
| 
 |
| 
 |
| 
 |
| The work is best done in several sessions, perhaps performed over a few days.
 |
| 
 |
| 
 |
| 
 |
| 
 |
| </p></usageNotes> |
| </org.eclipse.epf.uma:ProcessDescription> |
