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 of Competency Questions with its method-specific working model.
Knowledge Modeling
Competency Questions
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
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.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.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.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.
Complexitysame
MediumMediumMediumMedium
Timedifferent
Halber Tag pro Domain Slice2-4 h60-120 min2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
1-42-82-8Designers, developers as users, and facilitation
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape DocumentationCompetency Question Set, Required Concepts, Test Queries, Coverage MatrixCommunication Canvas, Stakeholder Messages, Architecture Communication PlanPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
Knowledge graphValidationSemantic
OntologyKnowledge graphScopeRequirementsSemantic
ArchitectureCommunicationStakeholdersCanvas
ArchitectureEngineeringFeedbackValidationTasks
Add more methods