Graph Diagrams

Graph diagrams visualise relationships between concepts using nodes and edges. Unlike traditional diagrams where you manually position every element, graph diagrams use force-directed physics to arrange nodes automatically. Related nodes cluster together naturally, revealing structure without manual layout work.

Dual Purpose: Standalone Diagrams and Project Model

Graph diagrams serve two purposes. As standalone files (.graph-diagram.json), they model graph databases, domain relationships, and dependencies. In graph-db mode, the same editor also serves as the editing canvas for the project model (model.neoarc), which is the single source of truth for your project's data architecture.

Three Authoring Modes

Graph diagrams support three authoring modes, each with different spacing, validation, and property behaviour. Choose the mode that matches your modelling intent.

Graph-DB Mode

Graph-db mode turns graph diagrams into functional data models with typed properties, constraints, and export capabilities.

Validation

Graph-db mode enforces 18 validation rules (10 core rules plus 8 search-specific rules) to maintain model quality. Conceptual mode runs a subset of the core rules. Mindmap mode runs none.

Use Cases

Example: E-Commerce Data Model

Example: Microservices Dependencies

Example: Insurance Domain Model

Version History and Transitions

Graph diagrams support the same versioning and transition system as standard diagrams.

Search, Group, and Tag Filtering

Links Mode

Graph links are a variant of graph diagrams where each node links to a page or external URL. Nodes become navigation targets rather than data model entities.

Force-Directed Layout

Graph diagrams use physics simulation to position nodes. Each authoring mode applies different simulation parameters.

Creating Graph Diagrams

Colour Coding

Use consistent colours to distinguish node types.

Additional Features