Database & Technology 2 _ Damien Bootsma _ best Practices for capturing meta data for prodctive database development.pdf

The most comprehensive Oracle applications & technology content under one roof The most comprehensive Oracle applications & technology content under one roof

Metadata Best Prac,ces Modelling best prac1ces for Database Developers

Damien Bootsma

So-ware Consultant

The most comprehensive Oracle applications & technology content under one roof

Overview

•  Why? •  Metadata to consider capturing •  Pushing the boat out… •  Q & A


Model beyond this…


Why?

•  Lack of documentaGon for our DBs •  Common data lives in a variety of systems •  Lineage and impact across systems is crucial •  DB funcGonality is not trivial


Why?

•  Who are your customers?

Data Architects

App / DB Dev

DBAs

ETL

Business Analysts

Network / Ops

Process Analysts


What’s Metadata?

•  Describes the characterisGc of a resource

– More than NAME & DATA TYPE •  Data security •  Compliance metadata •  Stewardship •  Governance • Workflow •  Reference Values


Why?

•  Good metadata comes from a true understanding of your data!

•  Data à InformaGon •  InformaGon à Knowledge •  Knowledge à Power


Capturing important Metadata

•  Domains •  Security & Compliance •  Reference Values •  Business Rules


Domains •  What are they?

– Define the characterisGc for a type of aVribute –  Eg: Name: DESCRIPTION

Data Type: VARCHAR(150) DescripGon: Describe the behavior of the current EnGty

•  Benefit> –  Consistency: Same domain is applied to all instances of aVribute type


Domains

•  Varchar(30) •  Null

•  Varchar(20) •  Not Null

• Varchar(max) •  Null

• Varchar(100) •  Not Null


Domains

Impact Analysis / Inheritance / Where Used


Security & Compliance •  What is it?

– Describing authorisaGon and permissions for specific data

– Describe any compliance mandates applicable to data elements

•  Benefit> –  Configure DB to enable certain security mechanisms – Develop correct funcGonality based on compliance and security


Security & Compliance Industries

Financial Services

Healthcare/Pharma

Federal Government

Retail

Energy

Mandates Sarbanes-Oxley

GLBA

Basel II

HIPAA

21 CFR Part 11

PCI DSS

State Data Breach Disclosure Laws

FISMA

Int’l. Data Privacy Laws

FERC/NERC

Guidance

PCAOB

COSO

CobiT

FFIEC

ISO 17799

NIST 800-66

NIST 800-53

DoD STIG

ITIL


Reference Values

•  What is it? – Data such as codes & values that represent correct & possible values for a given aVribute

•  Benefit>

– Consistency of data –  IdenGfy such data & ensure it is correctly in the DB & not in the logic layer


Business Rules

•  What is it? – Statement that defines or constrains some aspect of the business

•  Benefit> – Drives database design and implementaGon – Adds addiGonal context for database development


Business Rules

•  Simple Bank Example: •  Create a Stored Procedure that lists all customers eligible for further discounts on their current mortgage

•  Business Rule: Employees that hold a mortgage with the bank that have worked for the bank for less than 3 years are not eligible for further discounts


Storing Metadata

•  Where is your metadata? – Other modeling tools – Metadata repository – Source code control – Business apps –  Issue tracking systems

•  How can you monitor and integrate the sources together


Where can I find my Metadata?

Modeling & Metadata tools • ER Tools, UML modeling, “Big R” repositories, BPM diagramming, Visio, etc

Social Media Tools • Facebook, twiVer, etc Online CollaboraGon

Tools • Google Wave, Google Sites, EtherPad, Sharepoint, other wiki technology

Issue Tracking • Remedy, Tivoli, JIRA, etc

TradiGonal Business Apps • MS Office, e-‐mail, Lotus, Open Office, Google Docs, etc


Find the centre…

Modeling & Metadata tools • ER Tools, UML modeling, “Big R” repositories, BPM diagramming, Visio, etc

Social Media Tools • Facebook, twiVer, etc Online CollaboraGon

Tools • Google Wave, Google Sites, EtherPad, Sharepoint, other wiki technology

Issue Tracking • Remedy, Tivoli, JIRA, etc

TradiGonal Business Apps • MS Office, e-‐mail, Lotus, Open Office, Google Docs, etc

???


Capture “Everything”

•  “Everything” that is necessary and nothing more – DefiniGon of “everything” will be based on your audience(s)

– How “everything” is stored will be based on how it is accessed


Pushing the Boat out… UML

•  Sequence Diagrams – Flow of a complex Stored Procedure/FuncGon/Trigger

– Contains appropriate constructs •  Tables/Views •  Statements (Insert, Select, Delete, Update) •  Flow control (branching & Looping)

– Picture is worth a thousand words


Pushing the boat out… UML


Summary

•  AddiGonal metadata gives us a more thorough view for development

•  ‘Everything’: Use Metadata that will help you and fellow developers

•  Consider UML as a vehicle for complex funcGonality

•  Get Involved! Model unto others…


Thank you

[email protected]

Database & Technology 2 _ Damien Bootsma _ best Practices for capturing meta data for prodctive database development.pdf

Documents

specic data

good metadata

whats metadata

description data type

google modeling

state data breachnist

metadata best prac

data elements benet