Does an enterprise data model represent a high-level conceptual view (entities and relationships), rather than being a strictly relational (table/column) model?

Introduction / Context:
An enterprise data model (EDM) is a conceptual, business-oriented model describing major entity types and their relationships across the enterprise. It is not the same thing as a physical or fully relational schema. This item distinguishes conceptual modeling from relational implementation.

Given Data / Assumptions:

• EDM is typically expressed using entity–relationship notation or a similar conceptual diagram.
• Relational models translate concepts into tables, columns, keys, and constraints.
• The original statement asserts the EDM “is a relational model,” which is a category error.

Concept / Approach:
Conceptual → Logical → Physical. The enterprise model lives primarily at the conceptual level. The relational model appears at the logical/physical levels when implementing in a DBMS. Thus, equating an EDM with a relational model is incorrect, even though the EDM will eventually be elaborated into relational structures.

Step-by-Step Solution:

Verification / Alternative check:
Methodologies (e.g., top-down data architecture) explicitly separate enterprise conceptual models from DB-specific relational schemas.

Why Other Options Are Wrong:

• Correct/“depends on tool” both ignore the conceptual vs. relational distinction.
• Organization size does not change definitions.

Common Pitfalls:
Jumping to physical design too early; mistaking ERDs at enterprise scope for physical table designs.

Final Answer:
Incorrect