View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Business Strategy VMGS |  Architecture arc42 |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | VMGS arranges vision, mission, goals, and strategies into a clear guiding logic. Direction, purpose, and priorities are connected so teams can decide more coherently. | 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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitydifferent | Medium | Low | High | Medium |
Timedifferent | 2-4 h | 1-2 Tage | Several meetings plus preparation and analysis; total effort depends on scope | 1-2 h |
Participantsdifferent | 3-12 | 1-4 | Evaluation team, architects, and relevant stakeholders | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Vision Statement, Mission Statement, Goals, Strategies | Architecture Document, Context View, Runtime View, Deployment View | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | VisionGoalsStrategy | ArchitectureDocumentationCommunication | ArchitectureQualityRiskTradeoffsStakeholders | AlignmentStakeholdersStrategyFacilitation |