Role: Architect

This role is responsible for defining the software architecture, which includes making the key technical decisions that constrain the overall design and implementation of the project.

Role Sets: OpenUP Roles

Relationships


Primary Performs	Outline the Architecture Outline the Architecture Refine the Architecture
Additionally Performs	Assess Results Define Vision Design the Solution Detail Requirements Find and Outline Requirements Manage Iteration Plan Iteration Plan Project
Modifies	Architecture Notebook Design
Process Usage	Agree on the Technical Approach > Architect Agree the Technical Approach > Architect Construction Phase Iteration > Develop Solution (for requirement) (within context) > Architect Construction Phase Iteration > Identify And Refine Requirements > Architect Construction Phase Iteration > Manage Iteration > Architect Construction Phase Iteration > Develop Solution (for requirement) (within context) > Architect Construction Phase Iteration > Identify and Refine Requirements > Architect Construction Phase Iteration > Plan and Manage Iteration > Architect Construction Phase Iteration > Develop Solution Increment > Architect Develop Solution (for requirement) (within context) > Architect Develop Solution Increment > Architect Develop Solution Increment (no TDD) > Architect Develop the Architecture > Architect Develop the Architecture > Develop the Solution > Architect Develop the Architecture > Architect Develop the Architecture > Develop Solution Increment > Architect Elaboration Phase Iteration > Identify and Refine Requirements > Architect Elaboration Phase Iteration > Manage Iteration > Architect Elaboration Phase Iteration > Develop the Architecture > Architect Elaboration Phase Iteration > Develop Solution (for requirement) (within context) > Architect Elaboration Phase Iteration > Identify and Refine Requirements > Architect Elaboration Phase Iteration > Plan and Manage Iteration > Architect Elaboration Phase Iteration > Develop the Architecture > Architect Elaboration Phase Iteration > Develop Solution Increment > Architect Identify and Refine Requirements > Architect Identify and Refine Requirements > Architect Inception Phase Iteration > Identify And Refine Requirements > Architect Inception Phase Iteration > Initiate Project > Architect Inception Phase Iteration > Plan and Manage Iteration > Architect Inception Phase Iteration > Agree on the Technical Approach > Architect Inception Phase Iteration > Identify and Refine Requirements > Architect Inception Phase Iteration > Identify and Refine Requirements > Architect Inception Phase Iteration > Initiate Project > Architect Inception Phase Iteration > Initiate Project > Architect Inception Phase Iteration > Plan and Manage Iteration > Architect Inception Phase Iteration > Plan and Manage Iteration > Architect Inception Phase Iteration > Agree on the Technical Approach > Architect Inception Phase Iteration > Agree on the Technical Approach > Architect Inception Phase Iteration > Develop Architecture Spike > Architect Initiate Project > Architect Initiate Project > Architect OpenUP lifecycle > Construction Iteration [1..n] > Identify and Refine Requirements > Architect OpenUP Lifecycle with DSDM Stakeholder Plugin > Construction Iteration [1..n] > Develop Solution (for requirement) (within context) > Architect Plan and Manage Iteration > Architect Plan and Manage Iteration > Architect Transition Phase Iteration > Manage Iteration > Architect Transition Phase Iteration > Develop Solution (for requirement) (within context) > Architect Transition Phase Iteration > Plan and Manage Iteration > Architect Transition Phase Iteration > Develop Solution Increment > Architect

Main Description

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.

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.

This role is closely involved in organizing the team around the architecture by working closely with the Project Manager in staffing and planning the project.

Staffing

Skills

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:

Experience in both problem and software engineering domains, 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.
Leadership ability 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.
Excellent communication skills 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 person must earn the respect of the team members, the Project Manager, the customer, and the user community, as well as the management team.
Goal-oriented and proactive orientation with a relentless focus on results. 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.

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:

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
Makes the broader technical decisions, thereby demonstrating broad knowledge and experience, as well as communication and leadership skills

Assignment Approaches

This person in this role should be engaged in the project from start to finish.

For smaller projects, a single person may act as both Architect and Project Manager. 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. The Architect and Project Manager must work together closely.

Key Considerations

This role places emphasis on the core principle Focus on the architecture early to minimize risks and organize development.

More Information

Concepts	Focus on the architecture early to minimize risks and organize development Software Architecture

This program and the accompanying materials are made available under the
Eclipse Public License v1.0 which accompanies this distribution.