An Enterprise Data Architects thoughts on…

Lars E Martinssonwww.linkedin.com/in/larsmartinsson

Data Architecture Deliverables for Software Development Orgs

…for proper risk management

Content and opinions in this material are those of the author. Opinions may not represent those of any prior, current or future employer

Content• Presentation Goal• Data Architecture Influencers (Roles)• Data Architecture at 100 000 feet (Disciplines)• Data Architecture at 10 000 feet (Domains)• Data Architecture at Ground Level (Deliverables)• More information (Why, How, Templates)

Presentation Goal• This presentation lists over 200 data architecture

related deliverables – Based on decades of work building large scale software– Consider to complete stated deliverables if you are in

business of developing enterprise class-or-size software – If a deliverable is skipped the tentative risk and cost should

be discussed with relevant stakeholders

• The goal is to remind Enterprise Data Architects– What deliverables should be created, and for each state– What role the architect plays (delivers, approves, consumes)

Data Architecture Influencers (Roles)

Enterprise Data Architect

Enterprise Software Architect

Enterprise Applications Architect

Enterprise Business Architect

Enterprise Security Architect

Product Data Librarian

Product Manager

Development Manager

Architecture Review Board Product Steering Committee

Chief Technology Officer Product Portfolio Manager

Customer CouncilGeneral Manager

Product Data Modeler

Product Architect

IT Architect

Message: Managing The Data Architecture is a collaborative effort“Mainly Defines and Governs” “Mainly Requests and Implements”

IT Security ArchitectAuditor

Vendor

Bleeding Edge Customer

Product Analyst

Data Privacy Officer

Warehouse Architect

Science Data Architect

Database Administrator

Data Architecture at 100 000 Feet (Disciplines)

1. Data Asset Discovery2. Data Strategy3. Data Governance4. Data Modeling5. Data Access6. Data Content Management7. Data Analysis8. Data Life Cycle Management9. Data Management Practice

Data Architecture at 10 000 feet (Domains)

1. Data Asset Discovery– Enterprise Modeling– Functional Modeling– Data Store Inventory

2. Data Strategy– Roadmap– Technology

3. Data Governance– Policies, Processes, QA– Standards– Reviews

4. Data Modeling– Enterprise Data Modeling– Information Architecture Modeling– Information Analysis Modeling– Physical Data Modeling

5. Data Access– Data Security Standard– Product Security

6. Data Content Management– Reference Data– Master Data– Documents

7. Data Analysis– Meta Data– Data Warehouse– Business Intelligence– Analytics Modeling

8. Data Life Cycle Management– Packaging– Deployment– Operation

9. Data Management Practice– Project Sponsorship– Professional Development– Collaboration and Evangelism

Discipline 1: Data Asset Discovery

• This discipline provides info that is crucial to define and ongoing refine the Data Architecture• Priority from a Data Architecture perspective. Full Role Names can be found on the role slide

Discipline 2: Data Strategy

• The Enterprise Data Architect is heavily involved in defining roadmap, setting scope and follow-up on implementations as well as compile lists of data technologies used

• Coordinating data related tool use cross the Enterprise may yield significant synergies• Consider these items even if you want to be “lightweight” on governance (next slide)

Discipline 3: Data Governance

• Many other important Design Patterns exist – those mentioned only representative

Discipline 4: Data Model Management

Discipline 5: Data Access

Discipline 6: Data Content Management

Discipline 7: Data Analysis

Discipline 8: Data Life Cycle Management

Discipline 9: Data Management Practice

Proposed Next Step

This presentation listed over 200 deliverables an Enterprise Data Architect should evangelize and is a light introduction to “frame the scope” to anyone thinking about Enterprise Data ArchitectureTo successfully execute on each deliverable more information must be created (e.g. deliverable descriptions, why/benefits, contributing roles, exit/measure criteria, ready-to-use templates etc.)

www.linkedin.com/in/larsmartinssonFeedback? Contact me through LinkedIn