Data architecture: Difference between revisions

Revision as of 14:50, 27 December 2021

Latest revision as of 23:21, 29 August 2025

(14 intermediate revisions by 12 users not shown)

Line 1:

{{Short description|Standards on data collection and storage}}

{{Refimprove|date=November 2008}}

'''Data architecture''' isconsist theof models, policies, rules, and standards that govern which [[data]] is collected and how it is stored, arranged, integrated, and put to use in data systems and in organizations.<ref>[http://www.businessdictionary.com/definition/data-architecture.html Business Dictionary - Data Architecture] {{Webarchive|url=https://web.archive.org/web/20130330185324/http://www.businessdictionary.com/definition/data-architecture.html |date=2013-03-30 }}; [http://pubs.opengroup.org/architecture/togaf9-doc/arch/chap10chap09.html TOGAF 9.1 - Phase C: Information Systems Architectures - Data Architecture]</ref> Data is usually one of several [[architecture ___domain]]s that form the pillars of an [[enterprise architecture]] or [[solution architecture]].<ref>[http://www.learn.geekinterview.com/data-warehouse/data-architecture/what-is-data-architecture.html What is data architecture] GeekInterview, 2008-01-28, accessed 2011-04-28</ref>

== Overview ==

Line 10 ⟶ 11:

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 three traditional architectural stages:

* Conceptual - represents all [[Business_objectBusiness object|business entities]].

* Logical - represents the logic of how entities are related.

* Physical - the realization of the data mechanisms for a specific type of functionality.

Line 16 ⟶ 17:

The "data" column of the [[Zachman Framework]] for enterprise architecture &ndash;

{| class="wikitable"

{| border=1

|'''! Layer''' ||!! '''View''' ||!! '''Data (Whatwhat)''' ||!! '''Stakeholder'''

|-

|1 || '''Scope/Contextualcontextual''' || List of things and architectural standards<ref>[https://web.archive.org/web/20160305023946/http://www.strins.com/data-architecture-standards.html Data Architecture Standards]</ref> important to the business || Planner

|-

|2||'''Business Modelmodel/Conceptualconceptual''' || Semantic model or [[Entity-relationshipConceptual modelschema|Conceptualconceptual]]/[[Enterpriseenterprise data model]] || Owner

|-

|3||'''System Modelmodel/Logicallogical''' || Enterprise/[[Logicallogical data model]] || Designer

|-

|4||'''Technology Modelmodel/Physicalphysical''' || [[Physical data model]] || Builder

|-

|5||'''Detailed Representationsrepresentations''' || Actual [[database]]s || Developer

|}

Line 47 ⟶ 48:

Various constraints and influences will have an effect on data architecture design. These include enterprise requirements, technology drivers, economics, business policies and data processing needs.

; Enterprise requirements: These generally include such elements as economical and effective system expansion, acceptable performance levels (especially system access speed), [[Financial transaction|transaction]] reliability, and transparent [[data management]]. In addition, the [[Data conversion|conversion]] of raw data such as transaction [[Record (computer science)|records]] and [[image]] [[Computer file|files]]s into more useful [[information]] forms through such features as [[data warehouse]]s is also a common organizational [[requirement]], since this enables managerial decision making and other organizational processes. One of the architecture techniques is the split between managing [[transaction data]] and (master) [[reference data]]. Another is splitting [[Automatic identification and data capture|data capture systems]] from data retrieval systems (as done in a data warehouse).

; Technology drivers: These are usually suggested by the completed data architecture and database architecture designs. In addition, some technology drivers will derive from existing organizational integration frameworks and standards, organizational economics, and existing site resources (e.g. previously purchased [[software licensing]]). In many cases, the integration of multiple legacy systems requires the use of [[data virtualization]] technologies.

Line 59 ⟶ 60:

== See also ==

* [[Controlled vocabulary]]

* [[Data mesh]], a ___domain-oriented data architecture

* [[Disparate system]]

* [[Enterprise Informationinformation Securitysecurity Architecturearchitecture]] - (EISA) – positions data security in the enterprise information framework.

* [[FDIC Enterprise Architecture Framework]]

* [[Information silo]]

Line 84 ⟶ 86:

[[Category:Computer data]]

[[Category:Data managementengineering]]

[[Category:Enterprise architecture]]