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

Data Integration Architect Roles and Responsibilities

Improve accountability with David Bowman’s information management guidelines for data integration 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 integration architect roles and responsibilities and tasks and deliverables

Data Integration Architect Responsibilities
  • Should have overall responsibility for the data integration solution and all data integration deliverables including data flow diagrams and source system inventory;
  • Should include designing the extract, transform and load solution, leading system and integration testing and defining standards and architecture toolkits;
  • Should provide technical direction to the data warehouse team to ensure the integrity of the data warehouse; and
  • Should be accountable to the solution architect for the quality of all data integration deliverables.
Data Integration Architect Roles and Responsibilities for Configuration Management

Should specify the following configuration management requirements.

Management Roles

Should define software configuration management responsibilities.

Management Activities
  • Should specify the tools (hardware or software) necessary to perform the assigned activities on each project; and
  • Should define the criteria for updating the configuration management plan.
Configuration Identification
  • Should identify the project work products, how they will be controlled, where they will be stored and what tool will be used;
  • Should identify the naming and identification scheme that will be applied to all project work products;
  • Should describe the process that will be followed to baseline all work products;
  • Should identify how labels will be used to support code migration; and
  • Should identify how labels will be used to support concurrent code development and merging.
Managing Configuration Items
  • Should describe how software work products will be stored;
  • Should describe how code and data model repository access will be controlled; and
  • Should describe the plan to recover development work products in the event of failure.
Configuration Control
  • Should specify how change control for the software configuration management plan will be governed e.g. interface control should describe the process to control change to interface specifications;
  • Should describe the release planning and object migration plan i.e. how objects will be migrated thru each environment to production; and
  • Should describe the approach to control configuration items during the build phase.
Configuration Status Accounting

Should specify the configuration status accounting process.

Configuration Audits
  • Should describe the configuration item audit process;
  • Should describe how configuration audit reports will be distributed; and
  • Should describe any vendor or subcontractor work product audit process.
Metrics

Should define project software configuration management metric requirements.

Postmortem Activities
  • Should define the work product archival and retention process; and
  • Should define what configuration management data should be collected at project close.
Data Integration Architect Roles and Responsibilities for Requirements Specification

Conceptual Data Movement Diagram
  • Should provide definitions of each key system or data source that is required;
  • Should confirm understanding of the data integration scope;
  • Should be a sub-set of the enterprise conceptual data movement diagram;
  • Should involve working sessions with selected stakeholders;
  • Should involve feed-back sessions to introduce the conceptual data movement digram; and
  • Should be approved before commencing logical data movement diagrams.
Logical Data Movement Diagram
  • Should show all existing and new interfaces that will be required to satisfy requirements;
  • Should show the flow of data into, between, and out of all applications impacted by the project;
  • Should assign each system a system id;
  • Should assign each interface (existing and new) an interface id for requirements traceability;
  • Should involve working sessions with selected stakeholders;
  • Should involve feed-back sessions to introduce the conceptual data movement digram;
  • Should be the subject of an internal team review; and
  • Should be approved before commencing logical data movement diagrams.
Source System Definitions
  • Should provide a definition of each source system that will be required by the project;
  • Should provide a definition of each interface that will be required by the project;
  • Should involve a feed-back session with selected stakeholders to introduce the source system documentation;
  • Should be the subject of an internal team review; and
  • Should be approved before finalizing requirements specification.
Data Migration or Conversion
  • Should identify all data migration and or data conversion requirements to help plan the architecture and design;
  • Should involve facilitating working sessions with selected stakeholders to elicit data conversion requirements;
  • Should document data conversion requirements;
  • Should be the subject of an internal team review; and
  • Should be approved before finalizing requirements specification
Data Migration or Conversion Requirements
  • Should identify all data migration and or data conversion requirements to help plan the architecture and design.
  • Should involve facilitating working sessions with selected stakeholders to elicit data conversion requirements
  • Should document data conversion requirements;
  • Should be the subject of an internal team review
  • Should be approved before finalizing requirements specification
Data Quality Analysis
  • Should create a data profile for each data source so as to gain an understanding of the quality of source data to help the architecture an design team finalize detail specifications;
  • Should utilize a data profiling tool to analyze each source system table;
  • Should document data profile results in a project documentation repository;
  • Should be the subject of an internal team review;
  • Should involve feed-back session with selected stakeholders to introduce the data profile results; and
  • Should be approved before finalizing requirements specification.
Change Data Movement
  • Should identify change data movement requirements in terms of how the client wants to report changes;
  • Should involve working sessions with selected stakeholders to elicit change data movement requirements;
  • Should document change data movement requirements;
  • Should be the subject of an internal team review;
  • Should involve feed-back session with selected stakeholders to introduce the requirements; and
  • Should be approved before finalizing requirements specifications.
Data Integration Architect Roles and Responsibilities for Architecture and Design

Data Integration Architecture
  • Should provide diagram showing the key architecture components and environments;
  • Should describe what happens in each stage of the data integration solution;
  • Should define the interface capacity;
  • Should provide a link to each interface specification for each interface specified on the data integration diagram;
  • Should specify the approach that will be used to address data migration requirements;
  • Should define the approach for ensuring change data capture including the use of change data capture software if appropriate;
  • Should define the strategy for file/table control, record control and record accounting; and
  • Should provide high level data integration module specifications for each data integration module including any master data management integration routines.
Design
  • Should create or manage the creation of Interface Specifications; and
  • Should create or manage the creation Data Integration Specifications
Build and Test
  • Should lead data movement development deliverable review/checkpoints;
  • Should deliver operations guide;
  • Should deliver operations training material;
  • Should conduct system testing;
  • Should prepare the integration test environment;
  • Should develop the integration test data acquisition plan;
  • Should create integration test cases;
  • Should create integration test steps;
  • Should coordinating the execution of integration tests;
  • Should identify defects; and
  • Should create release packages to move from the integration test environment to the quality assurance test environment.
Summary…

Data integration architect roles and responsibilities should include overall responsibility for the data integration solution and all data integration deliverables including data flow diagrams and source system inventory.

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