🏛 Data Modeling

ERWIN Data Modeler

The industry-standard data modeling tool — taught from zero to interview-ready in nine focused lessons.

What is ERWIN?

ERWIN Data Modeler (often written "erwin DM" — the brand uses lowercase) is one of the most widely used commercial data modeling tools in enterprise data teams. Banks, insurance companies, telcos, healthcare providers, and most Fortune 500 companies use it to design databases before they get built.

If you're interviewing for a data engineer, data architect, ETL developer, or database analyst role at a mid-to-large enterprise, you'll almost certainly be asked about ERWIN. Even if your current shop uses a different tool, the concepts transfer directly to dbdiagram, DbSchema, SqlDBM, and Oracle SQL Developer Data Modeler.

Quick note on the name ERWIN stands for Entity-Relationship for Windows. It was originally built by Logic Works in the 1990s, later acquired by CA Technologies, and is now owned by Quest Software. You'll see it referred to as "erwin DM", "ERwin", or just "ERWIN" — they're all the same product.

Why this track exists

Most ERWIN tutorials online are either (a) outdated screenshots from version 7 with grey Windows XP chrome, or (b) the official documentation, which is exhaustive but assumes you already know what you're doing. This track is different:

The three-model methodology

ERWIN is built around the classical three-level data modeling approach. Every serious data architect uses some version of this — interviews love to ask you to compare and contrast.

1. Conceptual Data Model (CDM)

High-level business view. Just entities and relationships. No attributes, no keys, no data types. Drawn on a whiteboard with business stakeholders.

Audience: business + analysts

2. Logical Data Model (LDM)

Detailed structure. Entities, attributes, primary/foreign keys, relationships, cardinality. Normalized. Still database-agnostic.

Audience: data architects + designers

3. Physical Data Model (PDM)

Database-specific implementation. Tables, columns with exact data types (VARCHAR(50), DECIMAL(10,2)), indexes, partitioning, tablespaces. This is what generates the actual SQL DDL.

Audience: DBAs + database engineers

What you'll learn

  1. Install & Setup — Download ERWIN, get a trial license, first launch
  2. The Workspace — Model Explorer, diagram area, toolbox, property editor
  3. Build a Conceptual Model — Library example, drawing entities and relationships
  4. Build a Logical Model — Add attributes, set primary/foreign keys, cardinality
  5. Build a Physical Model — Pick a target database, set data types, generate indexes
  6. Forward / Reverse Engineering — Generate SQL DDL, import an existing database
  7. Best Practices — Naming conventions, common patterns, what NOT to do
  8. Interview Questions — Hand-picked questions with model answers

Prerequisites

Before starting this track, you should be comfortable with:

If any of these feel shaky, work through the Data Modeling section first — it pairs naturally with this track.

How to study this for interviews Don't just read — open ERWIN and follow along. Every step in this guide has been written so you can do it as you read. By the end of the Physical Model lesson, you'll have a working e-commerce database design you can talk through in any interview.

A note on alternatives

If you can't get an ERWIN trial license, the workflow we teach transfers to several alternatives at no cost:

The concepts — conceptual vs logical vs physical, forward/reverse engineering, entity-relationship diagrams — are universal. Interviews test the concepts, not the keystrokes.