Data Model
Define logical data ownership, structure, usage, constraints, and relationships
The Data Model connects logical information to the architecture elements that own and use it. Open Model → Data Model.
Version And Mode
The Data Model belongs to the selected architecture version. Select a version before opening it, and switch from Read to Edit mode before making changes. Historical, imported, or permission-restricted versions remain read-only.
Workbench
The workbench combines three views of the same model:
- Scope rail — filter by an architecture element, entity kind, or relationship to the selected scope
- Catalog — search, sort, page through, and select logical entities
- Relationship graph — inspect how entities relate without losing the catalog context
The inspector is where you create or edit an entity and its supporting evidence.
Logical Entities
For each entity, capture:
- A human-readable name and logical kind
- Its canonical architecture owner
- Attributes and logical data types
- Constraints such as identity, uniqueness, validation, or reference rules
- Architecture elements that read, write, produce, consume, or otherwise use the entity
- Relationships and cardinality to other entities
Ownership answers “where is this information authoritative?” Usage answers “which parts of the architecture depend on it?” Keep those two concepts distinct.
Scope And Architecture Context
Selecting a System, Container, Component, or Block scopes the catalog to data owned or used by that element and its relevant descendants. Data Model context also appears on architecture element and relationship detail pages, helping reviewers connect structural dependencies to information flow.
Review Questions
- Does every important entity have one clear canonical owner?
- Are readers and writers represented as usages rather than duplicate owners?
- Do relationship cardinalities match the intended domain rules?
- Are sensitive or business-critical constraints explicit?
- Would a proposed system change affect ownership, usage, or integrity?
Documentation, Decisions, And History
The Data Model can be included in published documentation and embedded as a live resource in Architecture Documents. What-if decisions can cite verified Data Model evidence. Version comparison and merge workflows include Data Model changes.
Archie and MCP can inspect the model and propose or apply supported changes according to their approval and access mode. Review the exact owner, stable IDs, and current version before accepting automated edits.