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 Team API with its method-specific working model.
Team Design
Team API
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
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.When expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document.The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.
Complexitydifferent
HighLowLowLow
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scopeHalf day initial, dann laufend1-2 h45-90 min
Participantsdifferent
Evaluation team, architects, and relevant stakeholdersEin Team plus Stakeholder3-103-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsTeam API DocumentArchitecture Canvas, Goals, Constraints, Quality AttributesExpectation Map, Alignment Notes, Agreements
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
TeamAlignmentCommunicationService
CanvasArchitectureAlignmentWorkshop
AlignmentStakeholdersTeam
Add more methods