In enterprise data modeling (high-level, organization-wide data planning), which activity listed below is INCORRECT?

Introduction / Context:
Enterprise data modeling is a strategic planning activity that creates an organization-wide view of data. It precedes project-level design and physical implementation.

Given Data / Assumptions:

• Enterprise data modeling focuses on scoping, goals, and high-level entities/relationships.
• It informs later project-specific logical and physical design.
• Implementation is operational, not strategic.

Concept / Approach:
The enterprise model identifies subject areas, major entities, and integration points across departments. Activities include assessing current systems, defining high-level requirements, and planning downstream projects. Physical build and deployment occur after detailed design, not during enterprise modeling.

Step-by-Step Solution:

Verification / Alternative check:
Methodologies place enterprise data modeling before logical/physical design and build phases.

Why Other Options Are Wrong:
They are genuine activities of strategic analysis and planning.

Common Pitfalls:
Blurring strategic and project execution phases; trying to implement before aligning enterprise semantics.

Final Answer:
You implement the new database.