| <?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_DfL5Edm6Nvont3uinw" |
| guid="_mtb_DfL5Edm6Nvont3uinw" version="1.0.0"> |
| <mainDescription><p>
 |
| The goal of this activity is to define a technical approach to the system that supports the project
 |
| requirements, within the constraints placed on the system and the development team. The architect should do the
 |
| following: 
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Work with the team to create an initial sketch of the technical approach to the proposed system
 |
| </li>
 |
| <li>
 |
| Ensure that the technical decisions are adequately captured and communicated
 |
| </li>
 |
| <li>
 |
| Ensure that the team has enough information to understand the approach that your are taking
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| The work done here does not seek to produce a detailed and comprehensive technical specification for the system.
 |
| Rather, the approach should be to decide the overall technical approach at a high level.
 |
| </p>
 |
| <p>
 |
| You should focus on proving the architecture with working software. If the solution is similar to a previously
 |
| produced solution (or is a well-known solution domain), then it will probably be good enough to
 |
| reference that example as evidence of the feasibility of the approach. In some cases, it may be necessary to develop
 |
| one or more prototypes to validate some of the decisions or clarify some of the requirements.
 |
| </p>
 |
| <p>
 |
| The conclusion of this work should produce just enough information to communicate the architecture to the team, and
 |
| to demonstrate its viability to the customer. This allows the project to move forward, enabling you to
 |
| refine and baseline the architecture.
 |
| </p></mainDescription> |
| <howtoStaff><p>
 |
| This activity is best carried out collaboratively by the team, with the architect acting as a focal point
 |
| for coordinating and facilitating the decisions.
 |
| </p></howtoStaff> |
| <usageNotes><p>
 |
| 
 |
| 
 |
| 
 |
| 
 |
| 
 |
| The major effort occurs early in the project; thereafter, you should assess the system regularly to ensure that the
 |
| 
 |
| 
 |
| 
 |
| 
 |
| 
 |
| design is still on track with the architecture.
 |
| 
 |
| 
 |
| 
 |
| 
 |
| 
 |
| </p></usageNotes> |
| </org.eclipse.epf.uma:ProcessDescription> |
