Data architecture: Difference between revisions

Revision as of 16:00, 13 March 2022

Latest revision as of 23:21, 29 August 2025

(10 intermediate revisions by 8 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/chap09.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 61 ⟶ 62:

* [[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 85 ⟶ 86:

[[Category:Computer data]]

[[Category:Data managementengineering]]

[[Category:Enterprise architecture]]