Method guideKnowledge Modeling

Property Graph Schema Design

A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.

ComplexityMedium

Time4-8 h initial, dann iterativ

Participants1-6

FormatWorkshop + async

MaturityEstablished

Plan Property Graph Schema Design

Prerequisite

What needs to be finished first

Complete firstBounded subject

The scope and purpose of Property Graph Schema Design are stated as a concrete question.

Without scope, property graph schema becomes arbitrary.

Complete firstAccess to relevant perspectives

prioritised queries, sample data and identity rules, volume and change assumptions and domain decision makers are available.

Without these perspectives, central claims in property graph schema remain unsupported.

Preparation

What needs to be ready before start

Materials

prioritised queries, sample data and identity rules, volume and change assumptions, shared workspace, source links, and decision log.

People / roles

Domain expert · graph engineer · query consumer · data steward

Pre-read

Collect prioritised queries, sample data and identity rules, volume and change assumptions in advance and mark open assumptions.

Time needed

2 × 90 minutes plus query testing

Setup

Prepare query-driven modelling of nodes, relationships, properties, and constraints visibly and calibrate assessment terms before starting.

Core question

The one question this method answers

Which graph schema answers the key queries correctly, understandably, and efficiently?

Flow

Phases with goal, actions, output and pitfall

Property graph models are designed from domain queries and traversal paths. Identity, direction, cardinality, constraints, and temporal change are tested explicitly.

property graph schema

Fictional worked example

query-driven modelling of nodes, relationships, properties, and constraints as a precise working structure with a fictional example.

Query

Question · expected answer · volume

Open actions + owner org per project.

Graph pattern

Nodes · relationships · direction

Project-HAS_ACTION→Action-OWNED_BY→Person.

Integrity

ID · constraint · cardinality

Action.id UNIQUE; one active owner.

Query plan

Index · traversal · result

Index Project.id; bounded traversal.

The example demonstrates the domain logic of Property Graph Schema Design; worksheets remain blank.

Neo4j Graph Data Modeling Guidelines

1
Prioritise queries
Prioritise queries
Goal
Produce query catalogue so the core question “Which graph schema answers the key queries correctly, understandably, and efficiently?” can be answered with stronger support.
Inputs for this step
- prioritised queries
- sample data and identity rules
- volume and change assumptions
Actions
- Collect top queries with expected answers and volumes.
- Record source, rationale, and open uncertainty directly in query catalogue.
Output
query catalogue
query catalogue · source · uncertainty · next decision
Quality check
Are read and write patterns included?
Pitfall
Tables are copied one-to-one as nodes and domain relationships disappear into ID properties. Start from queries and domain statements, make identity explicit, and profile real Cypher queries.
Timing: 10–20 minutes
2
Model graph
Model graph
Goal
Produce graph schema so the core question “Which graph schema answers the key queries correctly, understandably, and efficiently?” can be answered with stronger support.
Inputs for this step
- query catalogue
- sample data and identity rules
- volume and change assumptions
Actions
- Model nodes, labels, relationships, properties, and direction.
- Record source, rationale, and open uncertainty directly in graph schema.
Output
graph schema
graph schema · source · uncertainty · next decision
Quality check
Do relationships express domain verbs?
Pitfall
Tables are copied one-to-one as nodes and domain relationships disappear into ID properties. Start from queries and domain statements, make identity explicit, and profile real Cypher queries.
Timing: 10–20 minutes
3
Define integrity
Define integrity
Goal
Produce constraint set so the core question “Which graph schema answers the key queries correctly, understandably, and efficiently?” can be answered with stronger support.
Inputs for this step
- graph schema
- sample data and identity rules
- volume and change assumptions
Actions
- Define identity, cardinality, constraints, and temporality.
- Record source, rationale, and open uncertainty directly in constraint set.
Output
constraint set
constraint set · source · uncertainty · next decision
Quality check
Do constraints prevent invalid core data?
Pitfall
Tables are copied one-to-one as nodes and domain relationships disappear into ID properties. Start from queries and domain statements, make identity explicit, and profile real Cypher queries.
Timing: 10–20 minutes
4
Test queries
Test queries
Goal
Produce validated schema so the core question “Which graph schema answers the key queries correctly, understandably, and efficiently?” can be answered with stronger support.
Inputs for this step
- constraint set
- sample data and identity rules
- volume and change assumptions
Actions
- Load sample data, verify queries, and inspect PROFILE.
- Record source, rationale, and open uncertainty directly in validated schema.
Output
validated schema
validated schema · source · uncertainty · next decision
Quality check
Are result and access path correct?
Pitfall
Tables are copied one-to-one as nodes and domain relationships disappear into ID properties. Start from queries and domain statements, make identity explicit, and profile real Cypher queries.
Timing: 10–20 minutes

Artifact

What comes out at the end

Sketch: what the artifact looks like

Property Graph Schema Design · Queries in Graphschema übersetzenUse Cases und Query-Pattern in Node Labels, gerichtete Relationship Types, Properties, Indexe und Beispielqueries überführen

Form

Versioned property graph schema with date, sources, owners, and next review.

Versioning / ownership

Retain date, source, assumption state, and decision for every version of property graph schema.

Tool alternatives

property graph schema as board or document
Source and evidence register
Decision and action log

property-graph-schema-design-working-template.md

Plan Property Graph Schema Design around its domain steps and the concrete decision question.

Property Graph Schema Design: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Full workshop Time: 2 × 90 minutes plus query testing

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

Materials: prioritised queries, sample data and identity rules, volume and change assumptions, shared workspace, source links, and decision log.
Roles: Domain expert · graph engineer · query consumer · data steward
Advance information: Collect prioritised queries, sample data and identity rules, volume and change assumptions in advance and mark open assumptions.
Overall time needed: 2 × 90 minutes plus query testing
Setup: Prepare query-driven modelling of nodes, relationships, properties, and constraints visibly and calibrate assessment terms before starting.

Prepare for the work steps

Prioritise queries: Prioritise queries

prioritised queries
sample data and identity rules
volume and change assumptions

Model graph: Model graph

query catalogue
sample data and identity rules
volume and change assumptions

Define integrity: Define integrity

graph schema
sample data and identity rules
volume and change assumptions

Test queries: Test queries

constraint set
sample data and identity rules
volume and change assumptions

property graph schema

Query

Question · expected answer · volume

...

Graph pattern

Nodes · relationships · direction

...

Integrity

ID · constraint · cardinality

...

Query plan

Index · traversal · result

...

Enter only real input, sources, and decisions.

Neo4j Graph Data Modeling Guidelines

Prioritise queries: Prioritise queries

Expected artifact: query catalogue

query catalogue · source · uncertainty · next decision

Entry:

...

Are read and write patterns included?

Model graph: Model graph

Expected artifact: graph schema

graph schema · source · uncertainty · next decision

Entry:

...

Do relationships express domain verbs?

Define integrity: Define integrity

Expected artifact: constraint set

constraint set · source · uncertainty · next decision

Entry:

...

Do constraints prevent invalid core data?

Test queries: Test queries

Expected artifact: validated schema

validated schema · source · uncertainty · next decision

Entry:

...

Are result and access path correct?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/property-graph-schema-design/run-sheet

Example output

Concrete filled scenario, fictional example

Fictional example for orientation. Counts and timings describe this case and are not universal requirements.

property-graph-schema-design-beispiel.md

Concrete filled scenario, fictional example

Query: open actions for a project with owner organisation. Nodes: Project, Action, Person, Organization. Relationships: (:Project)-[:HAS_ACTION]->(:Action)-[:OWNED_BY]->(:Person)-[:MEMBER_OF {validFrom,validTo}]->(:Organization). Constraint: Action.id unique. Query profile tests index on Project.id and traversal.

Pitfalls

Recognize symptoms and steer against them

Quick overview, the full text is in the matching phase in the flow

Prioritise queriesTables are copied one-to-one as nodes and domain relationships disappear into ID properties.View in phase
Model graphTables are copied one-to-one as nodes and domain relationships disappear into ID properties.View in phase
Define integrityTables are copied one-to-one as nodes and domain relationships disappear into ID properties.View in phase
Test queriesTables are copied one-to-one as nodes and domain relationships disappear into ID properties.View in phase

Stop criteria

When to pause, resolve prerequisites, or choose another approach

property graph schema answers the core question with traceable evidence or explicitly marked uncertainty.

Owners, next actions, and review dates are named for open points.

Where to go next?

Knowledge Modeling

Shape-First Modeling

Carries the graph schema's constraints into testable validation rules.

Paper illustration of a Concept Map with concepts and labelled links

Knowledge Modeling

Concept Mapping

Additionally documents the schema's relationships as a conceptual map.

View in playbookPrepare Knowledge ModelingMove from a knowledge domain to questions, concept model, schema, and validation rules.

Finished the method guide?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.

Go to profile More methods