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.

Selected:Request for CommentsViews and BeyondRisk MatrixLASR (Lightweight Approach for Software Reviews)
Criterion
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
Paper illustration of a calibrated five-by-five risk matrix with response cards.
Decision Making
Risk Matrix
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Purposedifferent
An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale.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.When a project faces many possible disruptions, it quickly becomes unclear which risks deserve attention first. It separates options, evaluation criteria, and open risks. The result is captured as a Risk Matrix and a Top Risk List.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.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung1-3 Tage30-60 min3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
3-20 Reviewer1-43-101 or a small team; particularly suitable for 3–4 people
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsArchitecture Views, Cross-view Notes, RationaleRisk Matrix, Top Risk ListLean 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
Tagsno overlap
ArchitectureDecisionAsyncGovernance
DocumentationStakeholdersArchitecture
RiskDecisionPrioritizationAssessment
ArchitectureQualityRiskAssessmentLean
Add more methods