Advanced Data Modeling: Be Happier, Add More Value and Be More Valued


In this advanced workshop, Karen Lopez covers how to make data modeling more relevant in 2012 and removing pain points for modelers and other team members.   It includes how to be successful in an agile/scrum environment, how to make models valuable in a NoSQL project, how to better work with DBAs, Developers, Project Managers and how to sound and be more valuable.


With demonstrations, exercises and peer-discussions its goal is to give attendees the attitude and skills to add value and be more valued on modern project teams.  This course follows a workshop format, with both individual and team exercises. We offer this as a public workshop as well as in an onsite corporate format.

Participant Pre-requisites

As an advanced course, it is expected that attendees will have more than two years of hands-on data modeling and database design skills at the enterprise level.   We offer a basics course for those who do not have this experience or feel they need a refresher before participating in this course.

Interested in Attending?

For information about public courses, watch our blog and events page.

For inquiries about private courses, contact Karen with your desired timeframe and number of participants.


Overview of the Traditional Data Modeling Environment

  • Data Modeling Process
  • Tools
  • Databases
  • People
    • Skills
    • Background
    • Attitude
    • Culture
  • Timing

Being Happier, an Overview

  • Leaving 1985 Behind
  • Focusing on the Moment
  • Adding Value
  • Being Valued

Pain Points for Traditional Data Architects

  • New Development Methods
    • Agile / SCRUM
    • Lean, Fast
    • Code First
    • Refactoring
    • How to be Valuable
  • Big Data
    • How Big is Big?
    • 3 Vs? 6 Vs?
    • What does it mean?
    • How to be Valuable
  • NoSQL, Not Only SQL
    • Graph Databases
    • Key Value
    • Document Databases
    • Others
    • How to be Valuable
  • Being Physical
    • SQL
    • Relational Extensions
    • Being Polyglot
    • How to be Valuable
  • Data Governance
    • Governance
    • Stewardship
    • Dictatorships, Anarchies
    • How to be Valuable

Delivering Value in Today’s Data World

  • Working with DBAs
  • Working with Devs
  • Working with Project Managers (or no Project Managers)
  • Working with End Users

Tools: Where are We, Where do We Need to Be?

  • Data Modeling Tools
  • Project Collaboration Tools
  • Loving Your Data Models

Being Happier, The Details

10 Steps to Happiness, Being Valuable and Providing Value


  • Hey Karen I hope all is well with you…

    Can you tell me what tool to look at for creating the traditional Conceptual, Logical and tying (lineage) to many Physical models for structured and unstructured (No SQL) databases …..big data?

    Is ER/Studio 2016 one I should be looking at?


    • Hi Mark! The official ER/Studio answer is that you do Conceptual in their Business Architect (process) tool then do Logical and Physical in their Data Architect tool. This allows you to do map in ER/Studio Data Architect of Logical to Physical models.

      Unofficially, I see clients doing Conceptual as a separate model in ER/Studio, then doing another model with L/P. That doesn’t get you the tie-ins across all three.

      I know there’s a way to import Concepts in Business Architect to the models in Data Architect, but I’ve not checked to see how that mapping works or if it’s even tracked.

Leave a comment

Subscribe via E-mail

Use the link below to receive posts via e-mail. Unsubscribe at any time. Subscribe to by Email



UA-52726617-1 Secured By miniOrange