SCM: Status and Future Challenges

{ Q1.1: What product model to apply? Most SCM tools are still based on les. It is highly desirable to support more sophisticated data models for representing typed objects, relationships, and attributes. { Q1.2: What version model to apply? E.g. choose a state-based versioning (variants and revisions) or a change-based versioning (conditional compilation with more liberal delta combinations)? The two authors have proposed a unifying version model [CW97], capable of supporting both stateand change-based versioning { but limited experience exists. { Q1.3: Should the version model and product/object model be orthogonal to each other? In many proposals, version model and product/object model are intermingled. Separating product/object model and version model appears attractive because the same version model can be combined with di erent product/object models. However, the implications on database design have still to be explored more thoroughly.