View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Strategic, Tactical and Operational PlanningArchitecture Decision RecordLASR (Lightweight Approach for Software Reviews)ATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Business Strategy Strategic, Tactical and Operational Planning |  Architecture Architecture Decision Record |  Architecture LASR (Lightweight Approach for Software Reviews) |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | It places decisions and artifacts at the right level. Strategic planning clarifies direction, tactical planning translates it into programs, and operational planning steers concrete processes. | 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. | LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail. | 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. |
Complexitydifferent | Medium | Low | Medium | High |
Timedifferent | 90-180 min | 15-45 min | 3–4 h for initial assessment; preparation and deeper analysis additional | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 4-12 | 1-3 | 1 or a small team; particularly suitable for 3–4 people | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop | Async | Workshop + async | Workshop + async |
Outputdifferent | Planning Levels Map, Cadence Model, Planning Artifact Inventory | ADR File, Decision Log, Rationale | Lean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | CadenceGovernanceExecution | ArchitectureRationaleDocumentationGovernance | ArchitectureQualityRiskAssessmentLean | ArchitectureQualityRiskTradeoffsStakeholders |