Integrity Modeler Installation > Appendix 1: Configuration Management Use Cases > Configuration Management Use Cases
  
Configuration Management Use Cases
The following example use cases show how Modeler's database-based CM features can be used to support various development processes and lifecycle stages. In practice, teams will employ two or more of these use cases during a projects lifecycle and may combine aspects from different use cases at different points in a project.
It is important to note that for a large project there is unlikely to be a single process for all project phases. Often it is desirable to use different features at different times to maintain optimal productivity. The important thing is to have appropriate processes at the right time in your project. In practice, this means looking at the goals of a particular modeling phase and ensuring that the processes are appropriate to supporting these goals.
The following example use cases are provided:
Agile modeling using a multi-user model
Versioning models quickly and compactly
Controlling access using package protection and access rights
Differencing models for review purposes
Change tracking in a multi-user model
Breaking large projects into subsystem and component specific models
Model import and export between repositories and CM
Saving a database for an external CM baseline
Sharing components and packages between teams and CM
Developer isolation in support of code and debug cycles
Parallel development of a model for the current and next release
Team isolation in support of product variants
Working on parts of the model remotely