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
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of Specification by Example with a method-specific labelled workspace.
Agile
Specification by Example
Paper illustration of a yellow story card, blue rule cards, green example cards and a red question card on a light workspace.
Agile
Example Mapping
Purposedifferent
arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.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.When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests.When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound.
Complexitydifferent
LowHighMediumLow
Timedifferent
1-2 TageSeveral meetings plus preparation and analysis; total effort depends on scope60-90 min pro Feature30-60 min
Participantsdifferent
1-4Evaluation team, architects, and relevant stakeholders3-63-7
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsExample Table, Acceptance TestsExample Map, Acceptance Criteria, Open Questions
Tagsno overlap
ArchitectureDocumentationCommunication
ArchitectureQualityRiskTradeoffsStakeholders
AgileRequirementsExamplesBehavior-Driven Development
Behavior-Driven DevelopmentRequirementsExamplesRefinement
Add more methods