DataFlux

I am so excited! I get to work on an integration project that is huge. I mean really, really big — and it affects an entire organization. I hope I have a ton of insightful findings to share with you. Where to start, Where to start? After the project plan is solidified, roles and responsibilities are identified. Now a role is not necessarily a person! For example, there could be a data architect, business architect, technical architect, and a business intelligence architect role. Are you confused? I was, until we dug into the responsibilities of each role. Here you go:

• Data Architect – This role is responsible for the data model design based on business requirements, and the quality of the data. Probably the biggest job here since data profiling, and data quality go hand in hand.
• Business Architect – This role is responsible for the business requirements, scoping, and the conceptual architecture. Conceptual architecture diagrams do start diving into the technological platform.
• Technical Architect – This role designs the ETL architecture based on performance and reuse. Knowing how to index the data to get the best ETL performance is an art.
• Business Intelligence Architect – This role designs the reporting and analytics layer of BI (Business Intelligence). This includes start schemas, cubes, and reports

Now I really do believe that, in most organizations, that the data architect, business architect, and business intelligence architect are all rolled up into one person. Usually the technical architect role may be a combination of a DBA, and ETL programmer. How are roles defined in your organization?