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 for Risk Storming.
Architecture
Risk Storming
Paper illustration of Property Graph Schema Design with its method-specific working model.
Knowledge Modeling
Property Graph Schema Design
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of Shape-first Modeling with its method-specific working model.
Knowledge Modeling
Shape-First Modeling
Purposedifferent
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.Property Graph Schema Design turns business and technical requirements into a robust graph schema. It fits when query patterns, constraints, and migrations need to be thought about together.ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation.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.
Complexitydifferent
LowMediumHighMedium
Timedifferent
60-90 min4-8 h initial, dann iterativSeveral meetings plus preparation and analysis; total effort depends on scopeHalber Tag pro Domain Slice
Participantsdifferent
4-121-6Evaluation team, architects, and relevant stakeholders1-4
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Annotated Diagram, Prioritized Risk List, Action BacklogSchema Diagram, Node and Relationship Catalog, Index Plan, Migration Scripts, Sample QueriesPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsSHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation
Tagsno overlap
RiskArchitectureWorkshopValidation
Knowledge graphModelingSemantic
ArchitectureQualityRiskTradeoffsStakeholders
Knowledge graphValidationSemantic
Add more methods