PECB CMSA study guide
PECB CMSA · Work through your exam, one topic at a time.
The PECB CMSA is listed in this site's metadata under the name "Certified Management Software Architect," with "CMSA" as its short alias. It sits in the software architecture family of PECB individual certifications, alongside PECB's wider catalogue of cybersecurity, privacy, AI, governance, continuity, and quality credentials. The PECB CMSA study guide has 5 sections and about 1,911 words.
01Software Architecture Fundamentals and Principles
This domain tests whether you can define software architecture precisely and reason about it in the vocabulary of ISO/IEC/IEEE 42010: architecture is the fundamental concepts or properties of a system in its environment, embodied in its elements, relationships and the principles of its design and evolution. The architecture description is a distinct work product that expresses that architecture for identified stakeholders and their concerns.
397 words, about 2 min02Software Architecture Design and Modeling
This domain tests how you move from drivers to structures: identifying architecturally significant requirements, selecting styles, patterns and tactics, and expressing the result in models that belong to defined viewpoints. Design starts from architecturally significant requirements, usually quality attribute scenarios with stimulus, response and measure, not from a preferred pattern.
379 words, about 2 min03Software Architecture Documentation and Communication
This domain tests how to build an architecture description that is fit for its audiences: the required 42010 content, viewpoint selection, decision records, and keeping documentation alive. A usable architecture description contains stakeholders and their concerns, viewpoints and views, correspondence rules, rationale and decisions, a glossary, and known constraints.
371 words, about 2 min04Software Architecture Implementation and Governance
This domain tests how architecture becomes working software while staying conformant: decision rights, reviews, automated enforcement, exceptions and architecture-level technical debt. Implementation proceeds through a walking skeleton, architecture runway and enablers that make later feature work cheap rather than through a big-bang build.
353 words, about 2 min05Software Architecture Evaluation and Maintenance
This domain tests scenario-based evaluation before major commitment, the vocabulary of evaluation outputs, and keeping architecture valid as systems and drivers change. Methods include SAAM for scenario-based modifiability, ATAM for quality attribute and trade-off analysis, CBAM for cost-benefit economics, ARID for intermediate designs, and ALMA for modifiability analysis.
411 words, about 2 min