Multi-Phase Architecture Transitions in Diagrams
Model architectural roadmaps using lifecycle tagging on diagram elements. Mark shapes and connections as active, planned, or deprecated to represent current state, interim phases, and target architectures.
Architecture rarely changes in one step. Migrations happen in phases, new systems come online gradually, and legacy components are retired incrementally. NeoArc Studio's lifecycle tagging models these planned states by marking individual diagram elements as active, planned, or deprecated, allowing you to document current state, interim phases, and target architectures within a single diagram.
Lifecycle States
Common Use Cases
Creating a Transition
Succession Tracking
When deprecating a shape, assign its replacement via the replaced-by field. This creates a traceable chain:
File Storage
Lifecycle status is stored as a property on each shape and connection in the diagram JSON file. No additional files or directories are needed.
Example: Cloud Migration Roadmap
The data-architecture examples include a complete cloud migration scenario with lifecycle-tagged elements.
Combining with Version Snapshots
Lifecycle tagging and version snapshots work together. Stamp a version to capture the current lifecycle state of all elements. When you view a historical version, you see lifecycle statuses exactly as they were at that point in time.
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.