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 Linked Open Terms with its method-specific working model.
Knowledge Modeling
Linked Open Terms
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration for Risk Storming.
Architecture
Risk Storming
Purposedifferent
Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently.When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List.The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.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.
Complexitydifferent
MediumLowLowLow
Timedifferent
Wochen bis Monate20-40 min initial, dann laufend1-2 h60-90 min
Participantsdifferent
2-83-153-104-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance PlanROAM Board, Owner ListArchitecture Canvas, Goals, Constraints, Quality AttributesAnnotated Diagram, Prioritized Risk List, Action Backlog
Tagsno overlap
OntologyMethodologyAgileSemantic
RiskAgileTrackingAlignment
CanvasArchitectureAlignmentWorkshop
RiskArchitectureWorkshopValidation
Add more methods