Todd is astounding, a citizen of the world he is an amalgam of the best of the best in Data Architecture. Todd views the world through a different set of lenses than most of his stripe. He is head and shoulders above the others with an almost Zen like quality of connecting all things together.
A former “whiz kid” now an Adult “Genius” he is very talented and successful at seeing the Big Picture and Blueprinting I.T. for the rest of us. Interestingly, Todd enjoys Music and finds the parallels in harmonies and orchestrations a soothing respite without leaving his comfort zone of structure and definition in all things. Todd is an extremely talented yet humble person who is always cool as a cucumber, never anxious, but relaxed and level headed.
Data Architecture is the design of data for use in defining the target state and the subsequent planning needed to hit the target state. Data Architecture is one of the pillars of Enterprise Architecture and handshakes with its peer pillars of Business Architecture, Application Architecture and Integration Architecture.
Essential to realizing the target state, Data Architecture describes how data is processed, stored, and utilized in a given system. It provides criteria for data processing operations that make it possible to design data flows and also control the flow of data in the system.
The Data Architect is responsible for defining the target state, alignment during development and then minor follow up to ensure enhancements are done in the spirit of the original blueprint.
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 3 traditional architectural processes:
Conceptual - represents all business entities.
Logical - represents the logic of how entities are related.
Physical - the realization of the data mechanisms for a specific type of functionality