Model quality
Quality dimensions
| Dimension | Verification question |
|---|---|
| Completeness | Are all objects and relationships required for the scope present? |
| Correctness | Does information match confirmed sources? |
| Consistency | Are there duplicates, conflicting values, or invalid relationships? |
| Freshness | Was information reviewed within its required interval? |
| Traceability | Can the statement source and change impact be identified? |
| Accountability | Is an actor assigned to make decisions? |
Minimum automated rules
- unique stable identifier;
- known type and allowed state;
- both relationship endpoints exist;
- relationship type pair is allowed;
- one owning system per component;
- endpoints and direction for every integration;
- a component for every deployment;
- a resource for significant production deployments in the enterprise profile;
- owner and review date for critical objects at governed maturity.
Exceptions
A rule violation may be accepted temporarily when the reason, risk owner, compensating control, and expiration date are recorded. A permanent exception means the rule is incorrect or is not actually enforced.