No. 1 model versioning tool for distributed teams
The best teams have full control over their model versions
LemonTree was developed to use versioning systems like Git for models as well. Split your models as you wish and benefit from precise version control of the individual model parts.
Compare (Diff) versions
Analyse model changes precisely and easily
Merge of model parts
Combine different model versions in a controlled manner
Breakdown into individual components
Divide the models into individual components, which remain linked
Lifecycle for model parts
Individual model components are given their own lifecycle
Developed for safety requirements like ISO26262
Safety requirements demand good configuration management for models as well.
Review of models
LemonTree makes it easy to review and release all changes. The changes made are marked accordingly to make them traceable at any time. With LemonTree, users can thus ensure that they meet all requirements even during critical audits.
Controlled changes to the model
LemonTree already shows in a preview how the merged versions will look like. This helps you to recognize the effects of the merging at an early stage and thus to make only really desired changes.
Get you and your team agile
Develop your product lines with distributed teams and involve your suppliers right away. LemonTree allows you flexibility for the entire life cycle.
Different life cycles of model components
Since the models can be divided and individually versioned, each component (sub-model) can have its own lifecycle.
Export of model components
Model parts/components can be cleanly removed from a model and are thus also available to external developers for further processing.
Reuse of components in different projects
Individual model parts/components can be reused in different projects and further developed in parallel.
Developers at suppliers or from another internal department can quickly and easily import ready-made model packages into Enterprise Architect for further development.
LemonTree supports a platform approach to modelling, since the models can be divided into platform components on the one hand and project components on the other hand, and further developed separately.
Import with read-only permission
Model parts can be defined as “read-only” so that an internal or external supplier can use these parts but not modify them.
Versioning with Git
A partial model (or the entire model) can still be managed as EAP(x) in versioning systems such as Git.
Updating of models through intelligent model merging
If a component of the model has developed further during parallel processing, the new version can be easily imported.
Management of dependencies between model components
The integrated dependency analysis serves to define model parts more precisely before export.