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
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
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 Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.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.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
MediumMediumLowLow
Timedifferent
1-3 h60-120 min1-2 h1-2 Tage
Participantsdifferent
3-82-83-101-4
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Bottleneck Map, Flow Metrics, Improvement Options, Follow-up MeasuresCommunication Canvas, Stakeholder Messages, Architecture Communication PlanArchitecture Canvas, Goals, Constraints, Quality AttributesArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
FlowMeasurementConstraints
ArchitectureCommunicationStakeholdersCanvas
CanvasArchitectureAlignmentWorkshop
ArchitectureDocumentationCommunication
Add more methods