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 Competency Questions with its method-specific working model.
Knowledge Modeling
Competency Questions
Paper illustration of Shape-first Modeling with its method-specific working model.
Knowledge Modeling
Shape-First Modeling
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Purposedifferent
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.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.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.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
MediumMediumLowMedium
Timedifferent
2-4 hHalber Tag pro Domain Slice1-2 Tage2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
2-81-41-4Designers, developers as users, and facilitation
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Competency Question Set, Required Concepts, Test Queries, Coverage MatrixSHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape DocumentationArchitecture Document, Context View, Runtime View, Deployment ViewPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
OntologyKnowledge graphScopeRequirementsSemantic
Knowledge graphValidationSemantic
ArchitectureDocumentationCommunication
ArchitectureEngineeringFeedbackValidationTasks
Add more methods