| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:RoleDescription 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="_Y6tLEKbXEdm9d-ircVOUCA" |
| name="architect,_0X9iEMlgEdmt3adZL5Dmdw" guid="_Y6tLEKbXEdm9d-ircVOUCA" changeDate="2007-03-02T10:46:47.447-0800" |
| version="1.0.0"> |
| <mainDescription><p>
 |
| This role leads or coordinates the technical design of the system and has overall responsibility for facilitating the
 |
| major technical decisions expressed as software architecture. This typically includes identifying and documenting the
 |
| architecturally significant aspects of the system as views that describe requirements, design, implementation, and
 |
| deployment.
 |
| </p>
 |
| <p>
 |
| This role is also responsible for providing the rationale for these decisions, balancing the concerns of the various
 |
| stakeholders, reducing technical risks, and ensuring that decisions are effectively communicated, validated, and
 |
| followed.
 |
| </p>
 |
| <p>
 |
| This role is closely involved in organizing the team around the architecture by working closely with the&nbsp;<a class="elementLink" href="./../../openup/roles/project_manager_E657F936.html" guid="_0a0o0MlgEdmt3adZL5Dmdw">Project Manager</a>&nbsp;in staffing and planning the project.
 |
| </p></mainDescription> |
| <keyConsiderations>This role&nbsp;places emphasis on the core principle <a class="elementLink" href="./../../openup/guidances/concepts/core_principle_focus_346C6FAF.html" guid="_9gocwMvoEdqukPpotm3DYg">Focus on the architecture early to minimize risks and organize development</a>.</keyConsiderations> |
| <skills><p>
 |
| Architects must be well-rounded people with maturity, vision, and a depth of experience that allows for grasping issues
 |
| quickly and making educated, critical judgments in the absence of complete information. Specifically, the person must
 |
| possess this combination of qualifications:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| <b>Experience</b> <strong>in both problem and software engineering domains</strong>, with evidence of a thorough
 |
| understanding of the requirements to solve the problem and active participation in software development. If there
 |
| is a team, this experience can be represented by different team members, but at least one person must be able to
 |
| provide the overall vision for the project.
 |
| </li>
 |
| <li>
 |
| <b>Leadership ability</b> to motivate and maintain momentum for the technical effort across the various teams and
 |
| to make critical decisions under pressure, plus make those decisions stick. To be effective, this role must have
 |
| the authority to make technical decisions.
 |
| </li>
 |
| <li>
 |
| <b>Excellent communication</b> <strong>skills</strong> to earn trust, persuade, motivate, and mentor. This role
 |
| cannot lead by decree, but only by the consent of the rest of the project team. To be effective, this&nbsp;person
 |
| must earn the respect of the team members, the <a class="elementLink" href="./../../openup/roles/project_manager_E657F936.html" guid="_0a0o0MlgEdmt3adZL5Dmdw">Project Manager</a>, the customer, and the user community, as well as the management
 |
| team.
 |
| </li>
 |
| <li>
 |
| <b>Goal-oriented and proactive</b> <strong>orientation</strong> with a relentless focus on results.&nbsp;This
 |
| person is the technical driving force behind the project, not a visionary or dreamer. The career of a successful
 |
| architect is a long series of sub-optimal decisions made in uncertainty and under pressure. Only those who can
 |
| focus on doing what needs to be done will be successful.
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| From an expertise standpoint, this role also needs to show both design and implementation abilities. However, from the
 |
| design perspective, the effective architect typically exhibits these traits:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Tends to be a generalist, rather than a specialist, who knows many technologies at a high level rather than a few
 |
| technologies at the detail level
 |
| </li>
 |
| <li>
 |
| Makes the broader technical decisions, thereby demonstrating broad knowledge and experience, as well as
 |
| communication and leadership skills
 |
| </li>
 |
| </ul></skills> |
| <assignmentApproaches><p>
 |
| This person in this role should be engaged in the project from start to finish.
 |
| </p>
 |
| <p>
 |
| For smaller projects, a single person may act as both Architect and <a class="elementLink" href="./../../openup/roles/project_manager_E657F936.html" guid="_0a0o0MlgEdmt3adZL5Dmdw">Project Manager</a>. However, it is better to have these roles performed by different people to ensure that the pressures one
 |
| role doesn't cause neglect of the other role.&nbsp;The Architect and Project Manager&nbsp;must work together closely.
 |
| </p></assignmentApproaches> |
| </org.eclipse.epf.uma:RoleDescription> |
