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
Paper illustration of Competency Questions with its method-specific working model.
Knowledge Modeling
Competency Questions
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
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.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.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.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
Halber Tag pro Domain Slice60-90 min2-4 h2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
1-44-122-8Designers, developers as users, and facilitation
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape DocumentationAnnotated Diagram, Prioritized Risk List, Action BacklogCompetency Question Set, Required Concepts, Test Queries, Coverage MatrixPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
Knowledge graphValidationSemantic
RiskArchitectureWorkshopValidation
OntologyKnowledge graphScopeRequirementsSemantic
ArchitectureEngineeringFeedbackValidationTasks
Add more methods