">
logo for information-management-architect.com
leftimage for information-management-architect.com

Data Architect Roles And Responsibilities

Improve accountability with David Bowman’s information management guidelines for data architect roles and responsibilities

This site is designed for Information Technology professionals who need to improve accountability and require guidance and direction to establish information management roles.

It provides information management guidelines for data architect roles and responsibilities and tasks and deliverables

Data Architect Responsibilities
  • Should have overall responsibility for the data architecture solution and all data architecture deliverables including data modeling;
  • Should define data architecture requirements as part of requirements specification;
  • Should define source to target mapping and data transformation rules;
  • Should provide technical direction to assigned data architects and data base administrators; and
  • Should be accountable to the solution architect for the quality of all data architecture deliverables.
Data Architect Roles and Responsibilities for Requirements Specification

Conceptual Data Model
  • Should provide an appreciation for the overall scope of data storage requirements;
  • Should include definitions of each conceptual entity;
  • Should confirm understanding of the project data storage scope;
  • Should be a sub-set of the enterprise conceptual data model;
  • Should involve data modeling sessions with selected stakeholders;
  • Should involve feed-back sessions to introduce the conceptual data model; and
  • Should be approved before commencing logical data modeling.
Logical Data Model
  • Should finalize structure and design requirements;
  • Should involve data modeling sessions with selected stakeholders;
  • Should document entity definitions;
  • Should document entity attributes;
  • Should document storage volumetric requirements;
  • Should list any known issues with the logical data model;
  • Should be the subject of an internal team review; and
  • Should be approved before finalizing requirements specification.
Backup and Recovery
  • Should define backup and recovery requirements to achieve service level agreements in the event of operational, non-catastrophic, failure;
  • Should involve facilitating working sessions with selected stakeholders to discuss backup/recovery requirements;
  • Should be the subject of an internal team review; and
  • Should be approved before finalizing requirements specification.
Disaster Recovery
  • Should define backup and recovery requirements to achieve service level agreements in the event of operational, non-catastrophic, failure;
  • Should involve facilitating working sessions with selected stakeholders to discuss backup/recovery requirements;
  • Should be the subject of an internal team review; and
  • Should be approved before finalizing requirements specification.
Architecture and Design

Specify Physical Data Model
  • Should complete a physical data model for data warehouse storage;
  • Should create the physical data model by translating the logical data model into a physical data model;
  • Should define partitioning strategy;
  • Should include process metadata columns as required;
  • Should include audit columns as required;
  • Should identify and document reference table codes and descriptions;
  • Should provide table definitions;
  • Should provide column definitions;
  • Should include volumetrics;
  • Should document the processes and procedures required to meet data retention requirement including processes to archive all data including landing area, staging area, data warehouse and data marts, access archived data and restore archived data;
  • Should document the processes and procedures required to meet backup and recovery requirements;
  • Should document strategy to recover data in event of a system-wide failure including the approach that will be used including planning, processes and procedures;
  • Should define the approach that will be used to replicate data to meet redundancy requirements;
  • Should define the approach that will be used to provide an alternate method of accessing data accessing data in case of a system failure; and
  • Should specify any partitioning strategies that will be used in the database design to help meet performance requirements and archiving requirements.
Information Delivery Architecture
  • Should complete a dimensional data model for reporting and analytics;
  • Should create facts and dimensions based on the requirements specification;
  • Should add snow-flake dimensions if appropriate;
  • Should add physical attributes such as table-space names and index names;
  • Should define partitioning strategy;
  • Should include process metadata columns as required;
  • Should include audit columns as required;
  • Should identify and document reference table codes and descriptions; and
  • Should be the subject of an internal quality assurance review.
Other physical data modeling tasks
  • Should maintain model repository;
  • Should generate data definition language (DDL) used to create the database schema;
  • Should create a model to correspond to each environment;
  • Should synchronize models to ensure that database structures match models; and
  • Should test all DDL before deployment.
Summary…

A Data Architect should have overall responsibility for the data architecture solution and all data architecture deliverables including data modeling

This site provided information management guidelines for data architect roles and responsibilities and tasks and deliverables.