In the context of enterprise data modeling for an organization, which of the following statements describes an activity that is not correctly associated with this high level conceptual modeling phase?

Introduction / Context:
This question examines the scope and purpose of enterprise data modeling, a strategic activity in data management. Enterprise data modeling is about understanding what data the organization needs, not about implementing databases on any particular platform. It is a conceptual and planning activity, and therefore some tasks are appropriate at this stage, while others belong to later implementation phases. The exam asks specifically which statement is incorrect when describing enterprise data modeling activities.

Given Data / Assumptions:

We are working at the enterprise level, not just on a single project.
Enterprise data modeling focuses on conceptual understanding of data needs.
Review of current systems and data sources is commonly done at this stage.
High level description of data and planning of projects are typical enterprise activities.
Actual implementation of a database on a DBMS is normally a later stage task.

Concept / Approach:
Enterprise data modeling is essentially about what data the enterprise needs rather than how it will be technically implemented. It involves identifying major entities, key relationships, and high level constraints that span multiple applications. Activities such as reviewing current systems, describing data at a high level, and planning database projects are all aligned with this conceptual nature. By contrast, implementing a new database on a particular DBMS, creating tables, and writing scripts are physical and implementation tasks and do not belong to the enterprise modeling phase.

Step-by-Step Solution:
Step 1: Identify which of the listed activities clearly belong to conceptual and planning work at the enterprise level.Step 2: Recognize that reviewing current systems helps understand existing data and is therefore consistent with enterprise modeling.Step 3: Note that describing data at a very high level of abstraction is the core purpose of enterprise data modeling.Step 4: Observe that planning future database development projects based on the enterprise model is also a strategic activity.Step 5: Conclude that implementing the new database is not part of enterprise data modeling, making that statement the incorrect one in this context.

Verification / Alternative check:
A quick verification technique is to ask whether the activity deals with what or how. If it deals with what data is required across the enterprise, it is conceptual and suitable for enterprise data modeling. If it focuses on how to implement structures on a specific platform, it is part of physical design or implementation. Implementing a database is clearly a how task, so it must fall outside the enterprise modeling stage. Standard methodologies confirm that enterprise modeling precedes any implementation work and serves as a guide for later technical tasks.

Why Other Options Are Wrong:
Reviewing current systems is correct and essential because it reveals existing data structures and integration needs. Describing data at a high level of abstraction is a core goal of enterprise data modeling. Planning one or more database development projects is a natural follow up activity that uses the enterprise model. Identifying major entities and broad business rules also fits squarely in this conceptual modeling phase. Only the statement about implementing the new database is misplaced.

Common Pitfalls:
Students sometimes think of any activity involving databases as part of modeling, which blurs the line between conceptual modeling and implementation. Another pitfall is to assume that once an enterprise model is completed, the next immediate step must be implementation, ignoring intermediate logical and physical design phases. To avoid confusion, always separate strategic what tasks such as enterprise modeling from tactical how tasks such as implementation and tuning. This distinction improves clarity when answering exam questions and when planning real world projects.

Final Answer:
The incorrect statement about enterprise data modeling is implementing the new operational database on a specific database management system platform.