methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of a Polarity Map with two poles and four quadrants
Systems Thinking
Polarity Mapping
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
Paper illustration for CATWOE Analysis.
Systems Thinking
CATWOE Analysis
Purposedifferent
ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation.Polarity Mapping makes tensions between two opposing poles tangible, such as standardization and adaptation or control and autonomy. The method guards against making apparent either-or decisions prematurely.The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes.CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way.
Complexitydifferent
HighMediumLowMedium
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scope1-2 h1-4 h45-90 min
Participantsdifferent
Evaluation team, architects, and relevant stakeholders3-121-53-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsPolarity Map, Warning Signs, Balance ActionsContext Diagram, Container Diagram, Component DiagramCATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
Systems thinkingTradeoffsLeadership
ArchitectureCommunicationVisualization
Systems thinkingFramingStakeholders
Add more methods