Role: System Architect
This role is responsible for specifying a system architecture that will satisfy the system requirements and meet project objectives by providing technical leadership and acting as a source of creative vision for system development
Role Sets: Architecture
Relationships

Define the Services Functionality Behavior/Description (SvcV-4)Define the Systems Functionality Behavior/Description (SV-4) WBDevelop Capability to Services Mapping (CV-7)Develop Operational Activity to Services Traceability Matrix (SvcV-5)Develop Service Event Trace Descriptions (SvcV-10c)Develop Service Interfaces on SvcV-1Develop Service Measures Matrix (SvcV-7)Develop Service Rules Model (SvcV-10a)Develop Service State Transition Descriptions (SvcV-10b)Develop Service to Service and Systems Matrixes (SvcV-3a,b)Develop Services Resource Flow Description (SvcV-2)Develop Standards Profile (StdV-1)Develop System Resource Flow Description (SV-2)Develop Systems Event Trace Descriptions (SV-10c)Develop Systems Funtionality Description (SV-4) BBDevelop Systems Measures Matrix (SV-7)Develop Systems Rules Model (SV-10a)Develop Systems State Transition Descriptions (SV-10b)Develop the Organizational Relationships Chart (OV-4)Develop the Services Interface Description (SvcV-1)Develop the Systems Interface Description with Structure Elements (SV-1)Develop the Systems Resource Flow Matrix (SV-6)Develop the Systems Resource Flow Matrix (SvcV-6)Develop the Systems-Systems Matrix (SV-3)Update Systems Resource Flow Description (SV-2)Update the Systems Interface Description with Personnel Services and Information relationships (SV-1)CV-7: Capability to Services MappingOV-4: Organizational Relationships ChartStdV-1: Standards ProfileSV-1: Systems Interface DescriptionSV-10a: Systems Rules ModelSV-10b: Systems State Transition DescriptionSV-10c: Systems Event-Trace DescriptionSV-2: Systems Resource Flow DescriptionSV-3: Systems-Systems MatrixSV-4: Systems Functionality DescriptionSV-6: Systems Resource Flow MatrixSV-7: Systems Measures MatrixSvcV-1: Services Context DescriptionSvcV-10a: Systems Rules ModelSvcV-10b: Service State Transition DescriptionSvcV-2: Services Resource Flow DescriptionSvcV-3a: Systems-Services MatrixSvcV-3b: Systems-Services MatrixSvcV-4: Services Functionality DescriptionSvcV-5: Operational Activity to services Traceability MatrixSvcV-6: Services Resource Flow MatrixSvcV-7: Service Measures MatrixSystem_Architect

Additionally Performs
Modifies
    Main Description

    This role defines a system architecture that will satisfy the system requirements and meet the project objectives to minimize cost and risk.  The role analyzes possible solution architectures to determine the preferred high-level design for the system.  Models of the architecture are created to verify that the design will meet the requirements.

    The focus is on establishing and refinement of the system's structural aspects and is concerned with the optimization of these structures in terms of major system elements and their interfaces, and making trade-offs in competing factors and constraints (for example, performance, cost, environmental impact), in evaluating potential solutions that produce the required behavior. Its view spans the entire system and all factors, external and internal, that might affect its development. Given the need to maintain this broad view, this role rarely engages in depth in the detailed engineering of a system, preferring to leave that to other practitioners in the various engineering specialties.

    Staffing
    Skills

    A person performing this role needs:

    • Technical competence and strong communication skills (both written and verbal)
    • Sound knowledge systems architecture and design methodologies 
    • Critical reasoning skills and decision making skills
    • Creativity in figuring out solutions to complex problems
    • Skill in expressing him or herself in the language in which the architecture is captured (e.g. UML)
    • Leadership qualities, in order to drive the technical effort across the various teams, make critical decisions under pressure and make those decisions stick
    Assignment ApproachesIf the project is large enough to warrant a system architecture team, the goal is to have a good mix of talents, covering a wide spectrum of experience and sharing a common understanding of the systems engineering process. Ideally in such a team there is an individual, almost certainly the lead, who owns the overall vision for the project. The system architecture team should not be a committee of representatives from various teams, domains, or contractors. System architecture is a full-time function, with staff permanently dedicated to it.