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
Paper illustration of Shape-first Modeling with its method-specific working model.
Knowledge Modeling
Shape-First Modeling
Paper illustration for Risk Storming.
Architecture
Risk Storming
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 of Competency Questions with its method-specific working model.
Knowledge Modeling
Competency Questions
Purposedifferent
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.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.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.Competency Questions translate a domain model into concrete questions that it must be able to answer. The method keeps the model's scope clean and prevents pretty but useless structures.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
Halber Tag pro Domain Slice60-90 min3–4 h for initial assessment; preparation and deeper analysis additional2-4 h
Participantsdifferent
1-44-121 or a small team; particularly suitable for 3–4 people2-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape DocumentationAnnotated Diagram, Prioritized Risk List, Action BacklogLean 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 checksCompetency Question Set, Required Concepts, Test Queries, Coverage Matrix
Tagsno overlap
Knowledge graphValidationSemantic
RiskArchitectureWorkshopValidation
ArchitectureQualityRiskAssessmentLean
OntologyKnowledge graphScopeRequirementsSemantic
Add more methods