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 Domain Context Map
Domain Modeling
Domain Context Map
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Purposedifferent
When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole.In dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia.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 several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries.
Complexitydifferent
MediumMediumHighMedium
Timedifferent
1-3 h15-60 min je ZyklusSeveral meetings plus preparation and analysis; total effort depends on scope1-3 h
Participantsdifferent
3-101-8Evaluation team, architects, and relevant stakeholders2-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Domain Context Map, Boundary Notes, Ownership MapSituation Assessment, Decision Loop, Action UpdatesPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
Domain-Driven DesignContextBoundaries
DecisionChangeLearningStrategy
ArchitectureQualityRiskTradeoffsStakeholders
Domain-Driven DesignBoundariesStrategy
Add more methods