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 Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Purposedifferent
When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold.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.LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.
Complexitydifferent
MediumMediumMediumHigh
Timedifferent
1-3 h1-3 h3–4 h for initial assessment; preparation and deeper analysis additional2-6 h
Participantsdifferent
3-83-101 or a small team; particularly suitable for 3–4 people3-10
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Context Canvas, Glossary, Integration NotesDomain Context Map, Boundary Notes, Ownership MapLean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checksFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
Domain-Driven DesignBoundariesModeling
Domain-Driven DesignContextBoundaries
ArchitectureQualityRiskAssessmentLean
RiskQualityOperationsRoot cause
Add more methods