At the beginning of a data modeling course, I find it very useful to learn more about the participants. Most people begin by mentioning their job title followed by their job responsibilities, such as “I’m a developer and I code the mappings which load the warehouse.” A title implies certain responsibilities. The data analyst captures requirements, the data modeler represents the requirements, the DBA and developer implement the requirements, and so on. However, I have noticed a trend lately where the title ‘data architect’ is often tied with similar responsibilities to those of the analyst and modeler.
This challenge is to clarify the role of the data architect. In your organization, does the title ‘data architect’ encompass both data analysis and data modeling activities, or does the title ‘data architect’ come with an entirely different set of responsibilities?