So, what is Enterprise Data Architecture?
There are many different definitions of EDA out there; however, the most important is to understand EDA as a part of Enterprise Architecture (EA), that focuses, as its name says, on data. Similar as EA, EDA is a collection of various blueprints (mostly master blueprints) or an integrated set of specific artifacts that defines strategic data requirements. EDA purpose is to align data or information with software resources, and with business strategy. EDA is used to enable and to guide optimal integration of the data with relevant applications and objects, to secure and to improve data quality; and to enable the most optimal and most effective data use and delivery.
Some important advantages of EDA are (or why do we need it):
- it helps to understand the Enterprise Data and their structure;
- it provides high-level overview of the Data and their position in the Enterprise;
- it supports complex inter-systems Implementations, such as Business Intelligence solutions, Enterprise Application Integration or Master Data initiatives;
- it supports organized development and implementation of Data Governance;
- is crucial factor in executing successfull Data Strategy;
- and it delivers understandable and sufficient documentation for legal purposes;
According to my opinion, the biggest benefit of EDA, mostly overseen because of its high-level nature, is bringing all relevant enterprise data together in organized and functional way to enable or to support faster and better decision making.
If this text motivated you to think about the career in this field, it makes me very happy 🙂