Architecture Evaluation
Compare candidate system architectures against stakeholder priorities, quality attributes, interface complexity, resilience, evolvability and technical risk. Explore how weighting assumptions and architecture evidence influence the preferred option.
Evaluate architecture quality against stakeholder outcomes and system-level risks—not just local technical preference.
Architecture evaluation considers how candidate structures support quality attributes, interfaces, resilience, evolvability, verification, support and technical risk. Weighted scoring can support comparison, but it should not replace engineering judgement, scenario analysis or explicit handling of non-negotiable constraints.
This tool compares three fictional architectures for a distributed mission-control platform. It is deliberately different from a generic trade study: the emphasis is on architecture qualities, interactions, lifecycle consequences and robustness to changing priorities.
Architecture Evaluation — Step by Step
Eight stages establish the mission context, define criteria, set weights, evaluate candidate architectures, review risk and evidence, test sensitivity, apply a changed-priority challenge and conclude with a management architecture view.
Quality Attributes, Candidate Architectures, Risk and Sensitivity
Reveal the evaluation context to begin.
Review criteria, weights, architecture scores, evidence confidence and decision implications.
Explore Priority Sensitivity Without Changing the Guided Evaluation
Adjust stakeholder priority weights and evidence confidence. Experiment Mode is isolated from the guided evaluation.
Test your architecture-evaluation judgement.
Architecture evaluation cues
Quality Attribute
A system property such as performance, resilience, security, maintainability or evolvability used to judge architecture fitness.
Architecture Scenario
A concrete operating or change scenario used to test how an architecture responds under relevant conditions.
Weight
Relative importance assigned to an evaluation criterion. Weights should reflect stakeholder priorities and be tested for sensitivity.
Constraint
A mandatory condition that cannot be compensated away by a high weighted score elsewhere.
Evidence Confidence
Confidence in the models, prototypes, tests, analyses and assumptions supporting each architecture score.
Sensitivity
How much the preferred architecture changes when weights, scores or assumptions change. High sensitivity implies lower decision robustness.
The preferred architecture should be robust to stakeholder priorities, mandatory constraints and evidence uncertainty—not just win one weighted calculation.
Use weighted comparison as one part of architecture evaluation, then test scenarios, constraints, technical risks and sensitivity before committing to the structure.