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 Fault Isolation.
Engineering
Fault Isolation
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
Purposedifferent
In technical failures, the visible symptom often gets mixed up with the actual cause. Fault Isolation narrows the fault space and progressively reduces which part of the system is truly affected.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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question.
Complexitydifferent
MediumLowLowMedium
Timedifferent
30-180 min15-45 min30 min Setup, dann laufend1-3 Tage
Participantsdifferent
1-61-31-3 maintaining, briefing for everyone1-4
Formatdifferent
Workshop + asyncAsyncAsyncWorkshop + async
Outputdifferent
Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault AreaADR File, Decision Log, RationaleRAID Log, Status Report SourceArchitecture Views, Cross-view Notes, Rationale
Tagsno overlap
TroubleshootingDiagnosisEngineering
ArchitectureRationaleDocumentationGovernance
RiskTrackingStakeholdersGovernance
DocumentationStakeholdersArchitecture
Add more methods