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 for DMAIC.
Operations
DMAIC
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
For a process problem with fluctuating performance, the method brings analysis and improvement into a disciplined sequence. It creates a framework in which numbers, causes, and control come together.An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale.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.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.
Complexitydifferent
HighMediumLowHigh
Timedifferent
2-12 Wochen1-3 Wochen vom Draft bis zur Entscheidung1-4 hSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
3-103-20 Reviewer1-5Evaluation team, architects, and relevant stakeholders
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Project Charter, Measurement Plan, Cause Analysis, Control PlanRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsContext Diagram, Container Diagram, Component DiagramPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
Continuous improvementQualityProcess improvement
ArchitectureDecisionAsyncGovernance
ArchitectureCommunicationVisualization
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods