Ensuring enterprise business processes are effectively documented is not primarily a Data Architecture mechanism for defining project scope boundaries. That responsibility belongs more directly to Business Architecture, process management, and business-analysis disciplines.

DAMA-DMBOK2 explains that Enterprise Data Architecture influences projects by defining enterprise data requirements, reviewing project data designs, determining lineage impacts, controlling unnecessary replication, enforcing Data Architecture standards, and guiding technology and renewal decisions.

Consequently, options A, B, D, and E all represent valid ways architecture can constrain or guide project scope. A design review checks that local solutions remain compatible with enterprise strategy. Standards prevent individual projects from creating incompatible structures. Replication controls limit uncontrolled proliferation of redundant data. Enterprise data requirements ensure that projects account for information needs beyond their immediate application boundaries.

Documenting business processes remains important because processes produce and consume data, but comprehensive process documentation is not itself a primary Enterprise Data Architecture scope-control activity.

From a Data Quality perspective, architectural influence prevents project-level decisions from creating duplicated authoritative sources, inconsistent definitions, undocumented lineage, or uncontrolled transformations.

Reference Topics: DAMA-DMBOK2 Chapter 4 — Manage Enterprise Requirements within Projects; Architecture Governance; Project Scope Boundaries; Data Replication; Chapter 13 — Consistency and Lineage.

===============