Alignment Use Case
In teamworking, it can be difficult to work on a single repository, projects and diagrams not all having the same production cycles. Certain diagrams are in course of creation, while others can be already validated or requiring update.
Implementing a Production Repository
It may be necessary to install a production repository so as to have permanently available models ready for dispatch.
This production repository is supplied by work carried out in the work repository when it is ready for dispatch.
Transfering Objects Between Repositories
It can sometimes be necessary to transfer objects between repositories in a context other than that of the production repository.
In these contexts, it can be necessary to define strict modeling rules to avoid conflicts.Some examples:
• Distinct projects and integration repository
Modeling projects are initiated in distinct repositories. They are then transferred to an integration repository.
Modeling projects are initiated in distinct repositories. They are then transferred to an integration repository.
• Shared models
Models are created in a single repository. They are then used in projects, each of which results in creation of a repository.
Models are created in a single repository. They are then used in projects, each of which results in creation of a repository.
