In large Simulink projects, several engineers work on the same model and they often want to edit subsystems of the same MDL-files at the same time. Conventional version control software products do not support syntactically correct merging of MDL-files together with version control management for single subsystems. ecVERSIM treats each Simulink subsystem as a separate module and so allows for parallel development inside the different subsystems as if they were separate files. The user-friendly interface enables you to maintain control even over large and complex Simulink models. The modular philosophy of ecVERSIM allows for highly parallel development even of large single Simulink models.
Typically, when large Simulink and Stateflow models are built to describe system dynamics, many Simulink users are involved and working on the same model. From a version control perspective, without ecVERSIM, it is very difficult to synchronize and maintain the modeling stages and the various model versions provided by the different developers in different company departments. Within a client-server computer environment, ecVERSIM provides all the means to overcome these difficulties. ecVERSIM allows developers to check-in and check-out specific model parts easily. From a user's perspective, there is no restriction in working on the entire model within Simulink. The user gets feedback on which parts of the model are in use or blocked by which person. Rights for working with a model may be user- and project-dependent. ecVERSIM takes takes care of this as well.