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 of Specification by Example with a method-specific labelled workspace.
Agile
Specification by Example
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration of Acceptance Criteria Workshop with a method-specific labelled workspace.
Agile
Acceptance Criteria Workshop
Purposedifferent
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.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.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.When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update.
Complexitydifferent
MediumHighLowLow
Timedifferent
60-90 min pro FeatureSeveral meetings plus preparation and analysis; total effort depends on scope1-2 Tage20-40 min pro Story
Participantsdifferent
3-6Evaluation team, architects, and relevant stakeholders1-43-6
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Example Table, Acceptance TestsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsArchitecture Document, Context View, Runtime View, Deployment ViewAcceptance Criteria, Story Update
Tagsno overlap
AgileRequirementsExamplesBehavior-Driven Development
ArchitectureQualityRiskTradeoffsStakeholders
ArchitectureDocumentationCommunication
AgileRequirementsRefinementBehavior-Driven Development
Add more methods