A configuration is defined as being built up from a system model and version selection rules.
The long transactions model takes a broader approach by assuming that a system is built up out of logical changes.
New configurations of the product are then created by applying sets of the independently stored changes on the baseline version.
This entry covers the check-out/check-in synchronization model, including a meta-model (a process-data diagram).
Issues that are not discussed in detail are the three remaining synchronization models and the actual editing of CIs together with the methods related to this.
The process-data diagram above describes the different concepts that are applicable in the check-out/check-in synchronization model and their relation to the activities that take place.
Central to the meta-data model (right side of the figure) is the Configuration Item.
The meta-process model (left side of the figure) describes the process of the check-out and check-in activities.
When someone requests to open the CI, it is first copied to the local machine of the developer (note: there are systems where editing occurs directly in the repository.