The Modeling Room: (M2) Describe the people & things - (A10) Decide history
Series: The Modeling Room, module 2, article 10 of 26. Decide whether a description should correct the past or preserve a genuine change. Build an attribute history policy with the bike-shop team, test Emma's city against recorded work, and leave uncertain update reasons visible.
Who should read it?
Students learning modelstorming, analysts, report builders, data modelers working with business experts
Prerequsite
Separate a member's identity from its descriptions and test a grouping path, as in article 9.
Learning objective
Choose an attribute history policy and justify its effect on a past report with a change story.
Artifact
An attribute history policy table, report comparison, and named evidence checks.
Why this matters
A mistyped phone number and a real move both replace a field on screen. Keep the wrong digit as history and the contact report lies. Send earlier work to the new city and the location report lies. Both totals still add up. This lesson gives you the decision that prevents both.
What you'll learn
- How to tell a correction from a genuine change by its evidence.
- How to choose a history policy per attribute and test it against past work.
Your output: an attribute history policy table with change stories, an as-was trace of past work, and named evidence checks.
New terms: change story; the policies fixed value (FV), current value (CV), historic value (HV), previous value (PV).