Versioning data models

Versioning is the act of creating a new version of a model with changes. Versioning helps to track and control all changes applied to a model, allowing the recovery of a previous version when needed. When customizing a model, a practitioner creates one or more new versions to capture changes at different stages. A new version of a model can also result from its harvesting from a descendant stream.

About this task

Figure 1. Versioning examples
Versioning examples
  • Versioning models in practitioner streams:
    • Practitioner A creates version 1.2 and version 1.3 when customizing the model in a first iteration of changes.
    • Practitioner A creates version 1.4 and version 1.5 when customizing the model in a second iteration of changes.
    • Practitioner B creates version 1.6 when customizing the model in a first iteration of changes.
  • Versioning models in Project stream. Version 1.7 is created as the result of harvesting changes from version 1.6 of practitioner B.
  • Versioning models in Enterprise stream. Version 1.4 is created as the result of harvesting changes from version 1.3 of project 2.
Practitioner role
  • Data architect
  • Data modeler
Tools
  • Source Control Management (SCM) tool

Procedure

Create a new version of the practitioner model.
Note: in many SCM systems, this is also referred to as the check-in operation.