Actions

Difference between revisions of "Data Architecture"

m
Line 1: Line 1:
'''Data Architecture''' is a set of rules, policies, standards and models that govern and define the type of [[Data|data]] collected and how it is used, stored, managed and integrated within an [[Organization|organization]] and its database systems. It provides a formal approach to creating and managing the flow of data and how it is processed across an organization’s IT systems and applications.<ref>Defining Data Architecture [https://www.techopedia.com/definition/6730/data-architecture Techopedia]</ref>
+
'''Data Architecture''' is a set of rules, policies, standards, and models that govern and define the type of data collected and how it is used, stored, managed, and integrated within an organization and its database systems. It provides a formal approach to creating and managing the flow of data and how it is processed across an organization’s IT systems and applications.<ref>[https://www.techopedia.com/definition/6730/data-architecture Defining Data Architecture]</ref>
  
  
 
'''Overview of Data Architecture<ref>An Overview of Data Architecture [https://en.wikipedia.org/wiki/Data_architecture Wikipedia]</ref>'''<br />
 
'''Overview of Data Architecture<ref>An Overview of Data Architecture [https://en.wikipedia.org/wiki/Data_architecture Wikipedia]</ref>'''<br />
A data architecture should set data standards for all its data systems as a [[vision]] or a [[model]] of the eventual interactions between those data systems. [[Data Integration|Data integration]], for example, should be dependent upon data architecture standards since data integration requires data interactions between two or more data systems. A data architecture, in part, describes the [[Data Structure|data structures]] used by a [[business]] and its [[computer]] applications [[software]]. Data architectures address data in storage, data in use and data in motion; descriptions of data stores, data groups and data items; and mappings of those data artifacts to data qualities, applications, locations etc.
+
A data architecture should set data standards for all its data systems as a vision or a model of the eventual interactions between those data systems. [[Data Integration|Data integration]], for example, should be dependent upon data architecture standards since data integration requires data interactions between two or more data systems. A data architecture, in part, describes the [[Data Structure|data structures]] used by a business and its computer applications software. Data architectures address data in storage, data in use, and data in motion; descriptions of data stores, data groups, and data items; and mappings of those data artifacts to data qualities, applications, locations, etc.
  
Essential to realizing the [[target]] state, Data Architecture describes how data is processed, stored, and utilized in an information [[system]]. It provides criteria for data processing operations so as to make it possible to [[design]] data flows and also [[control]] the flow of data in the system.
+
Essential to realizing the target state, Data Architecture describes how data is processed, stored, and utilized in an information system. It provides criteria for data processing operations so as to make it possible to design data flows and also control the flow of data in the system.
  
The data architect is typically responsible for defining the target state, aligning during development and then following up to ensure enhancements are done in the spirit of the original [[blueprint]].
+
The data architect is typically responsible for defining the target state, aligning during development, and then following up to ensure enhancements are done in the spirit of the original blueprint.
  
 
During the definition of the target state, the Data Architecture breaks a subject down to the atomic level and then builds it back up to the desired form. The data architect breaks the subject down by going through 3 traditional architectural processes:
 
During the definition of the target state, the Data Architecture breaks a subject down to the atomic level and then builds it back up to the desired form. The data architect breaks the subject down by going through 3 traditional architectural processes:
Line 14: Line 14:
 
*Physical - the realization of the data mechanisms for a specific type of functionality.
 
*Physical - the realization of the data mechanisms for a specific type of functionality.
  
Data architecture should be defined in the planning phase of the design of a new data processing and storage system. The major types and sources of data necessary to support an enterprise should be identified in a manner that is complete, consistent, and understandable. The primary [[requirement]] at this stage is to define all of the relevant data entities, not to specify computer [[hardware]] items. A data entity is any real or abstracted thing about which an [[organization]] or individual wishes to store data.
+
Data architecture should be defined in the planning phase of the design of a new data processing and storage system. The major types and sources of data necessary to support an enterprise should be identified in a manner that is complete, consistent, and understandable. The primary requirement at this stage is to define all of the relevant data entities, not to specify computer hardware items. A data entity is any real or abstracted thing about which an organization or individual wishes to store data.
  
  
Line 31: Line 31:
 
*[[Data Compatibility]]
 
*[[Data Compatibility]]
 
*[[Data Governance]]
 
*[[Data Governance]]
*[[Data Integration]]
 
 
*[[Data Management]]
 
*[[Data Management]]
 
*[[Data Mining]]
 
*[[Data Mining]]

Revision as of 14:13, 21 November 2022

Data Architecture is a set of rules, policies, standards, and models that govern and define the type of data collected and how it is used, stored, managed, and integrated within an organization and its database systems. It provides a formal approach to creating and managing the flow of data and how it is processed across an organization’s IT systems and applications.[1]


Overview of Data Architecture[2]
A data architecture should set data standards for all its data systems as a vision or a model of the eventual interactions between those data systems. Data integration, for example, should be dependent upon data architecture standards since data integration requires data interactions between two or more data systems. A data architecture, in part, describes the data structures used by a business and its computer applications software. Data architectures address data in storage, data in use, and data in motion; descriptions of data stores, data groups, and data items; and mappings of those data artifacts to data qualities, applications, locations, etc.

Essential to realizing the target state, Data Architecture describes how data is processed, stored, and utilized in an information system. It provides criteria for data processing operations so as to make it possible to design data flows and also control the flow of data in the system.

The data architect is typically responsible for defining the target state, aligning during development, and then following up to ensure enhancements are done in the spirit of the original blueprint.

During the definition of the target state, the Data Architecture breaks a subject down to the atomic level and then builds it back up to the desired form. The data architect breaks the subject down by going through 3 traditional architectural processes:

  • Conceptual - represents all business entities.
  • Logical - represents the logic of how entities are related.
  • Physical - the realization of the data mechanisms for a specific type of functionality.

Data architecture should be defined in the planning phase of the design of a new data processing and storage system. The major types and sources of data necessary to support an enterprise should be identified in a manner that is complete, consistent, and understandable. The primary requirement at this stage is to define all of the relevant data entities, not to specify computer hardware items. A data entity is any real or abstracted thing about which an organization or individual wishes to store data.


See Also


References

  1. Defining Data Architecture
  2. An Overview of Data Architecture Wikipedia