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 Expectation Mapping.
Facilitation
Expectation Mapping
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 Team API with its method-specific working model.
Team Design
Team API
Purposedifferent
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.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 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.
Complexitydifferent
LowLowHighLow
Timedifferent
45-90 min1-2 TageSeveral meetings plus preparation and analysis; total effort depends on scopeHalf day initial, dann laufend
Participantsdifferent
3-121-4Evaluation team, architects, and relevant stakeholdersEin Team plus Stakeholder
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Expectation Map, Alignment Notes, AgreementsArchitecture 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 investigationsTeam API Document
Tagsno overlap
AlignmentStakeholdersTeam
ArchitectureDocumentationCommunication
ArchitectureQualityRiskTradeoffsStakeholders
TeamAlignmentCommunicationService
Add more methods