Logo
NeoArc Studio

Graph Diagram Lifecycle Transitions

Model entity lifecycle evolution in graph diagrams using active, planned, and deprecated states. Track succession with replaced-by and evolved-from edges, and visualise architectural change over time.

Graph diagrams support lifecycle tagging on individual nodes and edges, allowing you to model how entity structures evolve over time. Mark nodes as active, planned, or deprecated to show current state, intended additions, and elements being retired. Succession edges track the lineage between old and new entities.

What Lifecycle Tagging Shows

Lifecycle tags on graph elements communicate architectural intent at a glance:

Active Entities
Nodes displayed with default styling. These are live in production and represent the current state of the data model.
Planned Entities
Nodes displayed with dashed borders or muted styling. These are approved additions coming in a future phase.
Deprecated Entities
Nodes displayed with faded styling. These are being phased out and should not be used for new work.
Succession Edges
Replaced-by and evolved-from edges trace the lineage between deprecated and replacement entities.

Use Cases

Setting Lifecycle Status

Succession Tracking

Two edge types track the lineage between deprecated and replacement entities:

Edge TypeDirectionPurpose
Replaced-byDeprecated to ReplacementForward pointer showing what takes over
Evolved-fromReplacement to PredecessorReverse pointer showing origin and lineage

Bulk Deprecation

Multiple entities can be deprecated in a single operation:

Animated Presentations with Lifecycle States

Combine lifecycle tagging with animated presentations to walk stakeholders through the evolution story:

Step 1: Current State
Show all active entities
Step 2: Planned Additions
Reveal planned entities with fade-in animation
Step 3: Deprecations
Highlight deprecated entities and succession edges

Governance Reports

Two reports support lifecycle management in graph diagrams:

Storage

Lifecycle status is stored as a property on each node in the graph diagram JSON file. Succession edges (replaced-by, evolved-from) are stored in the edges array. No additional files or directories are required.