Engineer Architecture study guide
Engineer Architecture · Work through your exam, one topic at a time.
Engineer Architecture is a professional certification exam for engineers who design software-intensive systems and are ready to be judged on the decisions behind those designs rather than on coding speed. It suits senior developers moving into architecture roles, technical leads owning a system end to end, and consultants who must justify structural choices to clients and review boards. The Engineer Architecture study guide has 9 sections and about 3,027 words.
01Architecture Fundamentals and Design Principles
This domain checks whether you can define architecture precisely and justify structural decisions. Expect questions on the ISO/IEC/IEEE 42010 definition (fundamental concepts or properties of a system in its environment, embodied in its elements, relationships, and principles of its design and evolution), on the boundary between architecture and detailed design, and on classic principles: separation of concerns, modularity, information hiding, abstraction, cohesion, and coupling.
363 words, about 2 min02Requirements Engineering and Stakeholder Analysis
This domain tests whether you can find, classify, negotiate, and verify requirements, and whether you know who genuinely holds a stake. Expect functional versus non-functional requirements, constraints and assumptions, elicitation technique selection, prioritisation methods, and traceability.
363 words, about 2 min03System and Solution Architecture Modeling
This domain tests whether you can select and produce views that answer specific stakeholder concerns, using recognised notations at a consistent level of abstraction. ISO/IEC/IEEE 42010 separates viewpoint (the conventions for constructing a view) from view (the actual description).
358 words, about 2 min04Quality Attributes and Non-Functional Requirements
This domain tests whether you can turn "-ilities" into measurable, testable scenarios and select tactics whose trade-offs you can state explicitly. Use the six-part scenario: source, stimulus, environment, artefact, response, response measure.
301 words, about 2 min05Integration, Interfaces, and Interoperability
This domain tests how systems exchange meaning, not just bytes: integration styles, contract design, message semantics, versioning, and the organisational side of interoperability. Choose the integration style by coupling: file transfer (lowest coupling, highest latency), shared database (tightest coupling, avoid across domains), remote procedure call (simple, temporally coupled), messaging (decoupled, asynchronous, eventual consistency).
327 words, about 2 min06Architecture Evaluation and Trade-off Analysis
This domain tests whether you can run a structured, scenario-driven evaluation and name risks precisely rather than vaguely. ATAM sequence: present the method and the architecture, build a utility tree from prioritised quality attribute scenarios, map scenarios to architectural approaches, then identify sensitivity points, trade-off points, risks, non-risks, and the resulting decisions.
313 words, about 2 min07Architecture Governance and Documentation
This domain tests decision rights, standards and exceptions, and documentation that stays true after the project moves on. Governance is about who decides, how conformance is checked, and how exceptions are granted - not about approval meetings.
340 words, about 2 min08Implementation, Deployment, and Operations Support
This domain tests whether the architecture can be built, released, and run - and whether you supply what operations needs to keep it running. Architecture runway: identify enablers (platform, pipelines, observability) that must exist before features can land, and schedule them explicitly.
326 words, about 2 min09Professional Practice, Ethics, and Communication
This domain tests judgement: obligations to the public, client, and profession; handling conflicts; and explaining architecture to different audiences. The ACM/IEEE-CS Software Engineering Code of Ethics orders obligations: public, client and employer, product, judgement, management, profession, colleagues, self.
336 words, about 2 min