The Modeling Room: (M2) Describe the people & things - (A11) Implement historic values

Series: The Modeling Room, module 2, article 11 of 26. Emma moved, so her city needs dated versions, not a second customer. Test the move-day boundary, map each recorded activity to exactly one version, and group an as-was report that keeps her pre-move city on her pre-move work.

The Modeling Room: (M2) Describe the people & things - (A11) Implement historic values
Implement historic descriptions with dated versions and validate the version selected for a recorded activity.

Who should read it?

Students learning modelstorming, analysts, report builders, data modelers working with business experts

Prerequisite

You told a genuine change from a correction and chose a history policy for Emma's city, as in article 10.

Learning objective

Implement a historic value as dated version rows and validate which version each recorded activity selects

Artifact

A history implementation card with dated version rows, boundary probes, and an activity-to-version mapping

Why this matters

Emma's record now says Riverside. Rerun her earlier work by city and the report must label September work with the city she moved to or the city she lived in then. Choose wrong and every total stays correct while the label misleads. Store the new city as a 2nd customer row and she counts twice.

What you'll learn

  • How to store one member's history as dated version rows and select the row valid at an event's date.
  • How to test the boundary between versions and map each recorded activity to exactly one version.

Your output: a history implementation card with version rows, probes, and an activity-to-version mapping.

New terms: effective dating and as-was reporting

This post is for paying subscribers only

Already have an account? Sign in.