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 arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration of Porter’s five competitive forces
Business Strategy
Porter Five Forces
Paper illustration of a six-field PESTLE grid
Business Strategy
PESTLE Analysis
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
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.Porter Five Forces analyzes the forces that shape competitive pressure and profitability in a market. The view of market structure goes beyond individual competitors and reveals systemic pressure points.PESTLE Analysis makes political, economic, social, technological, legal, and environmental influences visible. The environment of an initiative is thereby read systematically instead of through isolated trends.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.
Complexitydifferent
LowMediumMediumLow
Timedifferent
1-2 Tage1-3 h1-3 h15-45 min
Participantsdifferent
1-42-82-101-3
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewFive Forces Analysis, Competitive Risks, Strategic OptionsPESTLE Map, External Risks, Strategic QuestionsADR File, Decision Log, Rationale
Tagsno overlap
ArchitectureDocumentationCommunication
StrategyCompetitionMarket
StrategyMarketAnalysis
ArchitectureRationaleDocumentationGovernance
Add more methods