Version: 1.0.0
Purpose
The Data Dictionary defines every business entity, attribute, relationship, and data element used throughout the product.
Its purpose is to establish a consistent understanding of the information managed by the system while providing the foundation for database design, application development, reporting, integrations, and future enhancements.
The Data Dictionary describes the business meaning of data rather than its physical implementation.
When This Artifact Is Created
The Data Dictionary is created during the Governance phase following approval of the Product Requirements.
It is maintained throughout the lifecycle of the project and updated whenever new data elements are introduced or existing definitions change.
Dependencies
Requires:
- Discovery Summary
- Source of Truth
- Product Bible
- Product Requirements
- Product Vocabulary
- Decision Log
Referenced By:
- Database Architecture
- Information Architecture
- UI/UX Bible
- Build Master Plan
- Architecture
- Planning
- Implementation
- Validation
- Evolution
AI Generation Instructions
The Data Dictionary should identify every business entity used by the product.
Each entity should be described using business terminology that is understandable by both business and technical stakeholders.
The Data Dictionary should focus on what the data represents rather than how it is physically stored.
Avoid implementation-specific database details unless required for clarity.
Every entity should support one or more approved business requirements.
Required Sections
Executive Summary
Provide a high-level overview of the information managed by the product.
Business Entities
Identify every major business entity within the product.
Each entity should include:
Entity Name
Description
Business Purpose
Owner (if applicable)
Lifecycle
Attributes
For each business entity identify:
Attribute Name
Description
Business Purpose
Data Type
Required / Optional
Default Value (if applicable)
Validation Rules
Allowed Values (if applicable)
Relationships
Describe relationships between business entities.
Include:
Relationship Type
Cardinality
Business Rules
Ownership
Unique Identifiers
Identify the primary business identifier for each entity.
Document any alternate identifiers.
Status Values
Document valid status values used by each entity together with their business meaning.
Validation Rules
Document business validation rules that apply to each entity or attribute.
Data Ownership
Identify the business owner responsible for each entity when applicable.
Data Retention
Document retention expectations for each entity where applicable.
Privacy and Security Considerations
Identify any special handling requirements for sensitive or regulated information.
Validation Criteria
The Data Dictionary is complete when:
Every business entity has been documented.
Every significant attribute has been defined.
Relationships between entities are documented.
Business terminology is consistent with the Product Vocabulary.
Validation rules are documented.
Sensitive information has been identified.
The human approves the completed artifact.
Maintenance
The Data Dictionary should be reviewed whenever:
New business entities are introduced.
Existing entities change.
Business rules change.
Database Architecture changes.
New integrations are added.
Validation identifies inconsistencies.
The Data Dictionary should remain synchronized with all governance artifacts throughout the lifecycle of the project.