HEAD: Hierarchical Enterprise Architecture for Data
Fuente:
Zenodo
Gespeichert in:
| 1. Verfasser: | |
|---|---|
| Format: | Recurso digital |
| Sprache: | Englisch |
| Veröffentlicht: |
Zenodo
2025
|
| Schlagworte: | |
| Online-Zugang: | |
| Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
| _version_ | 1866902098315051008 |
|---|---|
| author | Jaddu, Je Je Rama Bhushanam |
| author_facet | Jaddu, Je Je Rama Bhushanam |
| contents | <p><span>The <strong>Hierarchical Enterprise Architecture for Data (HEAD)</strong> is put forward here as a way to address that. It is recursive by design: each layer of the organization — from a small team all the way up to the enterprise — plays two roles. It looks after its own analytics while also consuming what comes from below, passing governed results upward in turn. This approach protects local freedom without letting the whole structure fall apart.</span></p> <p><span>HEAD rests on four ideas. <strong>Meta-Analytics</strong> helps teams build new insights out of what has already been analyzed, avoiding the churn of moving large volumes of raw data. <strong>Analytical Lineage</strong> makes it possible to trace how insights are created and reshaped, which builds trust and supports audits. A <strong>Request and Approval Channel</strong> adds a formal, accountable way for upper layers to ask for access to data from below, with the decision left in the hands of the data owner. Finally, the <strong>Change Notification Layer</strong> spreads word of updates — to schemas, policies, or logic — so that everyone can adjust in time. The <strong>Data Glossary</strong>, part of the governance framework, takes care of dataset discovery without confusing visibility with access.</span></p> |
| format | Recurso digital |
| id | zenodo_https___doi_org_10_5281_zenodo_17165602 |
| institution | Zenodo |
| language | eng |
| publishDate | 2025 |
| publisher | Zenodo |
| record_format | zenodo |
| spellingShingle | HEAD: Hierarchical Enterprise Architecture for Data Jaddu, Je Je Rama Bhushanam Data Architecture Meta-Analytics Change Notification Layer Federated Data Systems Enterprise Data Governance Federated Data Architecture Enterprise Data Lake HEAD Hierarchical Enterprise Architecture for Data Recursive Data Architecture Enterprise Data Architecture <p><span>The <strong>Hierarchical Enterprise Architecture for Data (HEAD)</strong> is put forward here as a way to address that. It is recursive by design: each layer of the organization — from a small team all the way up to the enterprise — plays two roles. It looks after its own analytics while also consuming what comes from below, passing governed results upward in turn. This approach protects local freedom without letting the whole structure fall apart.</span></p> <p><span>HEAD rests on four ideas. <strong>Meta-Analytics</strong> helps teams build new insights out of what has already been analyzed, avoiding the churn of moving large volumes of raw data. <strong>Analytical Lineage</strong> makes it possible to trace how insights are created and reshaped, which builds trust and supports audits. A <strong>Request and Approval Channel</strong> adds a formal, accountable way for upper layers to ask for access to data from below, with the decision left in the hands of the data owner. Finally, the <strong>Change Notification Layer</strong> spreads word of updates — to schemas, policies, or logic — so that everyone can adjust in time. The <strong>Data Glossary</strong>, part of the governance framework, takes care of dataset discovery without confusing visibility with access.</span></p> |
| title | HEAD: Hierarchical Enterprise Architecture for Data |
| topic | Data Architecture Meta-Analytics Change Notification Layer Federated Data Systems Enterprise Data Governance Federated Data Architecture Enterprise Data Lake HEAD Hierarchical Enterprise Architecture for Data Recursive Data Architecture Enterprise Data Architecture |
| url | https://doi.org/10.5281/zenodo.17165602 |