Series "The Modeling Room: Design Out Loud for Collaborative Data Warehouse Modeling"

Goal is to teach BEAM* (Business Event Analysis and Modeling) and dimensional modeling so readers can actually run a modelstorming session and build star schemas. Easy to learn, easy to apply.

Series "The Modeling Room: Design Out Loud for Collaborative Data Warehouse Modeling"

Who should read it?

Students, DW architects, computer scientists, BI users.

Intro

BEAM* means Business Event Analysis & Modeling. The method is attributed to Lawrence Corr and Jim Stagnitto, authors of "Agile Data Warehouse Design". The series teaches dimensional modeling for analytics. It is not a universal prescription for all warehouse architectures.

Purpose is to teach readers to discover reporting requirements together, document them with modelstorming and BEAM* and translate business models into dimensional warehouse models.

No SQL knowledge is assumed until the optional implementation examples.

This is a revised and updated 26-article learning path. The original had 9 articles. Each lesson explains now one main skill with a concrete example. Smaller lessons retain the explanation that beginners need.

How to study

Read in order on the first pass. Each article states the prerequisite, one learning objective, and the artifact you will create. First follow the worked example; then attempt the bike-shop exercise before opening its answer; finally apply the same questions to your own domain. Keep the resulting artifacts in a single workbook.

After each module, reconstruct its main artifact without looking at the article. On a later day, test it with a new example. Correct answers alone are not enough: explain why a plausible wrong answer fails. A practitioner with prior experience may use the checkpoints to skip familiar material.

The 6 core artifacts

6 artifacts carry the method; keep these in your portfolio:

  1. Question card (article 1)
  2. Event table with grain statement (article 4 and 6)
  3. Story-test pack (article 5)
  4. Dimension cards (article 7)
  5. One star schema (article 14)
  6. Measure cards (article 15)

Every other artifact named in a lesson (role map, policy table, event matrix, bridge rules, lifecycle row, packet sheets) is practice or optional support: it sharpens one decision, and you can drop it from your portfolio once that decision is safe.

Series Articles

Module 1: discover one event

  1. Start with a question: A better warehouse starts with a better question
  2. Find the event: Find the action hidden in the report
  3. Ask the 7Ws: 7 questions make a repair story concrete
  4. Build the event table: Give every story a row
  5. Test with story themes: The awkward example improves the model
  6. Declare the grain: Say exactly what one row means

Module 2: describe the people & things

  1. Discover dimensions: Keep the bike's descriptions out of the repair story
  2. Identify members: 2 customers can share a name
  3. Model hierarchies: Add categories without changing the repair count
  4. Decide history: A correction and a change need different treatment
  5. Implement historic values: Keep the old customer without duplicating the person
  6. Reuse a date dimension: 1 calendar can answer several date questions

Module 3: build & connect the warehouse models

  1. Map events and dimensions: Draw the warehouse before adding another table
  2. Translate to a star: Turn the tested story into a star
  3. Define safe measures: A number needs a unit and an aggregation rule
  4. Take a periodic snapshot: A monthly appointment is not a monthyl snapshot
  5. Follow a process: Follow 1 job without losing its milestones
  6. Compare facts safely: Compare labor & parts without multiplying either

Module 4: handle realistic exceptions

  1. Count without money: A service-plan enrollment is still worth recording
  2. Handle customer types: A company does not have a date of birth
  3. Model many-to-many: 2 mechanics must not create 2 copies of the bill
  4. Model reasons and methods: A repair reason is not proof of a cuase
  5. Handle complex hierarchies: A fleet can have branches of different depths
  6. Model changing profiles: Keep changing profiles from rewriting every customer

Module 5: apply the whole method

  1. Run the workshop: Leave the workshop with a model people can test
  2. Build your own model: Build a 2nd model without copying the bike shop