cust experience a practical guide 09152010

A Practical Guide to Enterprise Data Modeling and Model Management Using ERwin

Tuesday, September 15, 2010 at 2pm ET

abstract

Are you getting the most out of your data models? Are your data models spread out all over the place? Do you reuse or reinvent when you build your data models?

If these are troublesome questions for you and your organization then you may need a practical solution to address them.

During this session. See how WorkSafe BC, adopted a simple straight forward approach to building and managing Enterprise Data Models using CA ERwin Data Modeler and CA ERwin Model Manager, that turned potential chaos, into value for the organization.

biography

• Garry Gramm Enterprise Information Architect, WorkSafe BC

• ERwin Data Modeler user since Version 1.2. Was part of the beta team for ERwin AOS - as ModelMart/ Model Manager was called in the beginning under Logic Works, and have been on most CA ERwin Data Modeler beta programs ever since.

• Currently a member of the CA ERwin Data Modeler Global User Community board and a contributor to ERwin and InfoAdvisors discussion forums.

Topics

• Why CA ERwin Data Modeler

• Challenges

• Building infrastructure

• Building enterprise models

• Model management

Why CA ERwin Data Modeler

• Wanted to replace legacy DM tool

• ERwin 3.x Provided Increased Functionality

– Logical data modeling

– Physical data base design

– Implementation of standards

• Needed to support future needs & objectives

Challenges

• Standards & retro fitting

• New Tool = Learning curve

• Management commitment

• Architecture or not

• “Attitudes” - How to manage them

– People Issues

– Methodology requirements

– New approaches challenge validity

– Upgrade resistance

http://www.istockphoto.com/file_thumbview_approve/9310016/2/istockphoto_9310016-mountain-climber.jpg

Where are we?

Background


Challenges

• Building infrastructure

• Building enterprise models


Building the Infrastructure

• Published Standards

– Naming, Classwords

– Data Definition, Diagramming

• Templates

– Standards, Patterns, Translation

• Procedures

– Modeling, check out/in, MM Maintenance

Building the EDM

• Locate and gather all existing ERwin data models

• Merged by DBMS Type

• Reconciled conflicts

• DBMS specific Enterprise Data Models (EDM)

Are we there yet?

Background


Challenges

Building infrastructure

Building enterprise models


Model Management

• Check out

• Check in

• CA ERwin Model Manager

Check Out Process

• Project team - checkout request

• Model Management - processes request

Checkout Process Activities

• Project team

– Required entities

– New entities

– Validate new entity / table names

• Model management team

– Process checkout request

– Challenge new entities

– Create project model

Checkout Tips

• Subject Area (SA) as small as possible

• Sync custom SA

• Specify minimal info on derive type selection

• Keep same named SAs

Modeling Hints & Tips

Project Team– Review before you build.

• Requirements

• Modeling semantics

• Standards compliance

Model Management Team– Snoop around while project is ongoing

• Look at naming and metadata

• Gentle reminders

Are we There Yet?

Nope - Not Yet!

Check in Process

• Monitor WIP libraries

• Change Management Notification

• Verify updated project model

• Check in the model

• Close WIP library

• Update Spreadsheets

Check In Activities

Project Team– Model compliance

– Sync project model

Model Management Team– Sync project model

– Merge project model

– Visually verify merged model

– Sync merged model

Check-in Tips

• Sync project model

• Use same named SAs

• Use Complete Compare (CC) for the check in

• Use saved ‘type selection’ option sets

• Determine reconciliation strategy

• Have printed diagram handy

Managing Model Manager

Steps to tune and increase MM performance

– Add MM server to SAN

– Partition data file groups

– Transaction logs on separate drives

– Re-index mart regularly

– Remove CA ERwin Data Modeler history

– Keep the mart lean

Our Environment

DB2 SQLS

Copy

Read only

User Updatable

Public Mart

ProductionLibraries

ProjectLibraries(WIP)

Admin Mart

Archive

Example of the ADMIN MART

Summary

Background


Challenges

Building infrastructure

Building enterprise models

Model management

Benefits

• Faster development cycles– Unified disparate models

– Re-use

– Rapid impact analysis

– What if scenarios

• Data consistency

• Single central source for metadata

• Metadata is easily shared

• Secure managed environment

Are We There yet?

Yup – we’re done!

Thank you all for sharing your valuable time for this session.

I hope you found it useful and worthwhile.

If you have any other questions later on you can contact me personally at :

[email protected]

You can also find me on:

LinkedIn, ERwin.com, & InfoAdvisors.com discussion groups.

Questions?

cust experience a practical guide 09152010

Technology