Cust experience a practical guide 09152010

459 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
459
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
18
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Cust experience a practical guide 09152010

  1. 1. A Practical Guide to Enterprise DataModeling and Model ManagementUsing ERwinTuesday, September 15, 2010 at 2pm ET
  2. 2. 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. PAGE 2
  3. 3. 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. PAGE 3
  4. 4. Topics• Why CA ERwin Data Modeler• Challenges• Building infrastructure• Building enterprise models• Model management PAGE 4
  5. 5. 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 PAGE 5
  6. 6. 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 resistancePAGE 6
  7. 7. Where are we?BackgroundWhy CA ERwin Data ModelerChallenges• Building infrastructure• Building enterprise models• Model management PAGE 7
  8. 8. Building the Infrastructure• Published Standards – Naming, Classwords – Data Definition, Diagramming• Templates – Standards, Patterns, Translation• Procedures – Modeling, check out/in, MM MaintenancePAGE 8
  9. 9. Building the EDM• Locate and gather all existing ERwin data models• Merged by DBMS Type• Reconciled conflicts• DBMS specific Enterprise Data Models (EDM) PAGE 9
  10. 10. Are we there yet?BackgroundWhy CA ERwin Data ModelerChallengesBuilding infrastructureBuilding enterprise models• Model management PAGE 10
  11. 11. Model Management• Check out• Check in• CA ERwin Model Manager PAGE 11
  12. 12. Check Out Process• Project team - checkout request• Model Management - processes request PAGE 12
  13. 13. 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 PAGE 13
  14. 14. Checkout Tips• Subject Area (SA) as small as possible• Sync custom SA• Specify minimal info on derive type selection• Keep same named SAs PAGE 14
  15. 15. 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 PAGE 15
  16. 16. Are we There Yet? Nope - Not Yet! PAGE 16
  17. 17. Check in Process• Monitor WIP libraries• Change Management Notification• Verify updated project model• Check in the model• Close WIP library• Update Spreadsheets PAGE 17
  18. 18. 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 PAGE 18
  19. 19. 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 PAGE 19
  20. 20. Managing Model ManagerSteps 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 PAGE 20
  21. 21. Our Environment Public Mart Production Read only Libraries Admin Mart DB2 SQLS Project Libraries (WIP) User Updatable Copy ArchivePAGE 21
  22. 22. Example of the ADMIN MART PAGE 22
  23. 23. SummaryBackgroundWhy CA ERwin Data ModelerChallengesBuilding infrastructureBuilding enterprise modelsModel management PAGE 23
  24. 24. 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 PAGE 24
  25. 25. 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 : Garry.Gramm@worksafebc.comYou can also find me on:LinkedIn, ERwin.com, & InfoAdvisors.com discussion groups. PAGE 25
  26. 26. Questions? PAGE 26

×