NeoArc for Data Architects
Model-first data architecture with a central data model, interactive data views per model, database profiles for vendor-specific output, search profiles for index configuration, schema lineage to model properties, and project reports for coverage metrics.
Your data models live in spreadsheets, scattered ERD tools, and wiki pages that fall out of date the moment someone changes a column type. You need a single source of truth for entities, properties, and relationships that feeds every downstream artefact, from database projections to API mappings to search index configurations. A model-first workflow in NeoArc Studio defines all data entities in a central data model (model.neoarc), then surfaces them through interactive data views that show structure, lineage, and governance coverage in one place.
Model-First: Single Source of Truth
The central data model holds every entity, property, key role, and relationship for the project. All downstream artefacts derive from this model rather than duplicating definitions across separate diagrams.
Data Views: The Modern Evolution of the ERD
Data views go beyond traditional ERDs. Each view selects entities from the model and renders them with crow's foot notation, but also surfaces database projections, API serialisation mappings, search configurations, and governance coverage alongside the structural relationships.
Graph-DB Mode for Entity Definition
The graph diagram editor supports a schema mode where entities are defined with property types, constraints, and labels directly on graph nodes. This is useful for modelling graph database schemas (Neo4j, Azure Cosmos DB Gremlin) alongside data views of the same model.
Schema Lineage to Model Properties
Schema fields link to their source properties in the data model, creating traceable paths from database column to API field.
Common Use Cases
Example: E-Commerce Data Model
This graph diagram shows a typical e-commerce entity relationship model. Each node represents an entity with its properties, types, and constraints. Colours distinguish entity types: purple for customers, blue for transactions, green for catalogue, and orange for junction tables.