The Data Model is a diagram type in Elements that allows you to create and analyze data structures using ERD (Entity-Relationship Diagram) notation. It helps you model entities, their attributes, and the relationships between them, supporting schema planning and system configuration.
What is a Data Model?
A Data Model provides a structured view of how data is organized and related across your systems. It is ideal for:
Designing database schemas
Defining relationships between business entities
Supporting integration planning between systems
Documenting data flows for system architecture
Each entity can include detailed attributes and documentation for clarity.
Who is this feature for?
This diagram type is especially useful for:
System Architects: To align system designs with data requirements
Business Analysts: To define data requirements for processes and systems
Developers and Database Designers: To create ERDs for implementation
Prerequisites
A free Elements workspace
Permission to create and edit diagrams in your workspace
How to Create a Data Model
To create a Data Model:
Click the "New" button in diagrams menu, then "Create blank diagram", and then select "Data Model" from the list of diagram types. Then click next.
Give your diagram name and description to capture intended scope.
Supported Card Types
The canvas includes two default card options (but you can add or remove attributes to either of them at will)
Full Card: Includes attributes and a description field.
Simplified Card: A compact version for clean, high-level overviews.
This makes it easy to document entities in detail while keeping the diagram clean.
💡 Tip: Use clear naming conventions for entities and attributes to avoid confusion later.
Drill Down to Related Diagrams
Entities can be linked to other diagrams for deeper context. Supported child diagrams include:
Another Data Model (for hierarchical or modular modeling)
Interaction Flow
System Architecture
This lets you connect data models to wider architectural views.
📘 Example: A “Customer” entity might drill into a System Architecture diagram showing where customer data is stored across applications.
Best Practices for Building Data Models
To get the most out of your diagrams:
Keep entity names consistent with business terminology.
Group attributes logically to make entities easier to understand.
Use relationships sparingly — too many can make the diagram cluttered.
Add documentation so your team can understand the purpose and meaning of each entity.