Data architect
From Wikipedia, the free encyclopedia
A data architect is a person responsible for making sure an organization's strategic goals are optimized through the use of enterprise data standards. This frequently involves creating and maintaining a centralized registry of metadata.
Data architecture includes topics such as metadata management, business semantics, data modeling and metadata workflow management.
A Data Architect's job frequently includes the set up a metadata registry and allows domain-specific stakeholders to maintain their own data elements. Data Architects also strictly and meticulously enforce standards and integrity within an Enterprise Data Model. Such rigor is necessary because in large enterprises the data model usually outlives all other IT/IS work products:
- Data and Data Model - 25 years+
- Systems - 10-20 years
- Applications - 3-10 years
- Code/Classes - 1-5 years
A side-effect of the methodical and precise nature of the work done by Data Architects is the type of personalities the role attracts, for example (this is very funny among DAs) Q: What is the difference between a Data Architect and a terrorist? A: You can negotiate with a terrorist.
A Data Architect has experience in the following technologies:
- Data dictionaries
- Data warehousing
- Enterprise application integration
- Metadata registry
- Relational Databases
- Semantics
- Structured Query Language (SQL)
- XML, including schema definitions and transformations.
