This section provides guidance on how to effectively compare and merge models in a team development environment.
Consider the following example, which shows how multiple team members work in parallel.
Enabling team capabilities for configuration management systems
When you develop models, you can enable team capabilities to work with configuration management systems, which facilitate version control and can assist your development process.Comparing versions of a model to find differences
You can compare two or three models to find the differences between them. When you compare models, the models must have a common ancestor.Merging versions of a model to resolve conflicts
You can merge versions of a model that were developed in parallel to resolve the conflicts between them.Canceling merges between versions of a model
If you do not want to use the result of a merge between versions of a model, you must close the merge editor and not save the merged model.Saving merged models
You can save a merged model after you resolve all its conflicts. You can also save a separate copy of a merged model to any location. If you save a copy, you continue to work on the original merged model in the merge editor.
Related concepts
Model roles in a compare and merge session
Differences and conflicts between versions of a model
External references in models
Related information
Tutorial on comparing and merging versions of a model