Scribd
Upload
43 views

Data Architecture Theory

The document outlines principles for data architecture theory including that data should be defined centrally, shared across the enterprise, and have a single source. It discusses principles for data architecture including assigning data custodians, protecting data from unauthorized access, and minimizing data duplication. Design principles for the enterprise data model focus on data integrity, independence, and stability.

Uploaded by

Ebtsam Rashed
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
43 views

Data Architecture Theory

The document outlines principles for data architecture theory including that data should be defined centrally, shared across the enterprise, and have a single source. It discusses principles for data architecture including assigning data custodians, protecting data from unauthorized access, and minimizing data duplication. Design principles for the enterprise data model focus on data integrity, independence, and stability.

Uploaded by

Ebtsam Rashed
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 8

Data Architecture Theory

Data Theory
• Data is an independent resource
• Data is application independent
• Data is stable
• Data has a single source
• Data is shared across the Enterprise/Industry “No business operates in a vacuum”
• Data is defined centrally
• Data is flexible
Data Architecture Principles
 Every data source must have a defined custodian (a business role) responsible for the accuracy,
integrity, and security of that data.

 Data must be protected from unauthorized access and modification.

 Data should not be duplicated, except where essential for practical reasons. If data must be
duplicated, one source must be clearly identified as the master, there must be a robust process to
keep the copies in step, and copies must NOT be modified.

 Data structures must be under strict change control, so that the various business and system
implications of any change can be properly managed.

 Where possible, adopt international, national, or industry standards for common data models.
Where this is not possible, develop organizational standards instead.
Data Architecture Principles
 Processes for data capture, validation, and processing should be automated wherever possible.

 Data should only be entered once.

 Processes which update a given data item should be standard across the enterprise.

 Data should be recorded as accurately and completely as possible, by the most informed source,
as close as possible to its point of creation, in an electronic form at the earliest opportunity, and in
an auditable and traceable manner.

 The cost of data collection and sharing should be minimized.

 The enterprise, rather than any individual or business unit, owns the data.
Data Design Principles

• Data Integrity
• Data Independence
• Data Design Stability
Enterprise Model Definitions
• Business process Model
• Define the Process Scope
• Set the Level of Detail
• Present the Processes in Graphical Format
Enterprise Data Model
•. An Enterprise Data Model (EDM) represents a single integrated definition of data, unbiased of any
system or application. It is independent of “how” the data is physically sources, stored, processed, or
accessed. The model unites, formalizes, and represents the things important to an organization, as
well as the rules governing them.

• The enterprise Data Model consists of three levels of data modeling.


a- conceptual
b- Logical
c- Physical
Enterprise Data Planning

• Initiate Enterprise Data Planning

You might also like