View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ARID (Active Reviews for Intermediate Designs)Expectation MappingATAM (Architecture Tradeoff Analysis Method)Alignment Mapping
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Facilitation Expectation Mapping |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | 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 review as a planning range; preparation and evaluation additional | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope | 1-2 h |
Participantsdifferent | Designers, developers as users, and facilitation | 3-12 | Evaluation team, architects, and relevant stakeholders | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Expectation Map, Alignment Notes, Agreements | 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 | ArchitectureEngineeringFeedbackValidationTasks | AlignmentStakeholdersTeam | ArchitectureQualityRiskTradeoffsStakeholders | AlignmentStakeholdersStrategyFacilitation |