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
Quality Attribute Workshop workspace showing the question, observations, and next decision.
Architecture
Quality Attribute Workshop
Paper illustration of Shape-first Modeling with its method-specific working model.
Knowledge Modeling
Shape-First Modeling
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)
Paper illustration for Risk Storming.
Architecture
Risk Storming
Purposedifferent
A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties.Shape-First Modeling defines data quality through shapes before implementation or integration frays at the edges. The approach fits when validation and data contracts should be part of the design from the start.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.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
2-4 hHalber Tag pro Domain Slice3–4 h for initial assessment; preparation and deeper analysis additional60-90 min
Participantsdifferent
5-151-41 or a small team; particularly suitable for 3–4 people4-12
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Quality Scenarios, Priority List, Architecture ConcernsSHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape DocumentationLean 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 checksAnnotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap
RequirementsArchitectureWorkshop
Knowledge graphValidationSemantic
ArchitectureQualityRiskAssessmentLean
RiskArchitectureWorkshopValidation
Add more methods