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 Bottleneck Analysis.
Operations
Bottleneck Analysis
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Purposedifferent
For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput.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.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.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.
Complexitydifferent
MediumLowLowLow
Timedifferent
1-3 h1-2 h15-45 min1-2 Tage
Participantsdifferent
3-83-101-31-4
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop + async
Outputdifferent
Bottleneck Map, Flow Metrics, Improvement Options, Follow-up MeasuresArchitecture Canvas, Goals, Constraints, Quality AttributesADR File, Decision Log, RationaleArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
FlowMeasurementConstraints
CanvasArchitectureAlignmentWorkshop
ArchitectureRationaleDocumentationGovernance
ArchitectureDocumentationCommunication
Add more methods