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 Property Graph Schema Design with its method-specific working model.
Knowledge Modeling
Property Graph Schema Design
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration of Competency Questions with its method-specific working model.
Knowledge Modeling
Competency Questions
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.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.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.
Complexitydifferent
MediumLowMediumHigh
Timedifferent
4-8 h initial, dann iterativ30 min Setup, dann laufend2-4 hSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
1-61-3 maintaining, briefing for everyone2-8Evaluation team, architects, and relevant stakeholders
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Schema Diagram, Node and Relationship Catalog, Index Plan, Migration Scripts, Sample QueriesRAID Log, Status Report SourceCompetency Question Set, Required Concepts, Test Queries, Coverage MatrixPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
Knowledge graphModelingSemantic
RiskTrackingStakeholdersGovernance
OntologyKnowledge graphScopeRequirementsSemantic
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods