The #1 model versioning tool for
distributed teams

LemonTree Lieber
LemonTree Lieber

LemonTree 3.3

The versioning tool for distributed teams!
Simultaneously with the release of Enterprise Architect 16, LieberLieber is now presenting LemonTree 3.3 to ensure full compatibility with the widely used modeling platform. In addition, LemonTree.Automation is now a separate solution for use in a tool chain.

LemonTree

LemonTree 3.0

The most important information at a
glance. The versioning tool for distributed teams!

The best teams have full control over their model versions

LemonTree Lieber was developed to use versioning systems like Git for models. Divide your models as you wish and benefit from precise version control of the individual model parts.

LemonTree RN Embedded

Compare (Diff) versions

Analyze model changes precisely and easily

Merging of model parts

Merge different model versions in a controlled manner

Division into individual components

Split the models into individual components that still remain linked

Life cycle for model parts

Individual model components have their own life cycle

Lieber Lieber RN Embedded

Choose your preferred workflow, and

make your team agile

Each team has its own workflows for collaboration, even across companies. Rely on proven workflows like
Gitflow and take advantage of feature branches.

LieberLieber RN Embedded
LemonTree

Versioning systems

Benefit from the countless features of your favorite versioning system for your models.

LemonTree Lieber ieber


Lifecycle tools

Expand your modeling workflows with lifecycle tools like Bitbucket, Gitlab, and many others

RN Embedded

Continuous integration

Use our LemonTree Automation Edition for servers like Jenkins to also integrate modeling automatically.

Designed for safety requirements such as ISO26262

Safety requirements require good configuration management for models too.

LemonTree

Review of models

LemonTree makes it easy to review and approve all changes. The changes made are marked accordingly so that they can be traced at any time. With LemonTree, users ensure that they meet all requirements even during critical audits.

LemonTree Models

Controlled changes to the model

LemonTree already provides a detailed preview of what the merged versions will look like. This helps you to recognize the effects of the merger early on and only make changes that are really desired.

Simple pricing structure

To make your decision for LemonTree Lieber as easy as possible, we have deliberately designed our pricing structure to be simple. We offer you annual licenses including maintenance (all LemonTree versions) and help desk support. You can choose between a single license and a floating license (for your entire team).

LieberLieber

Single license

RN Embedded Solutions

Floating license

You and your team become agile

Develop your product lines with distributed teams and involve your suppliers right away. LemonTree gives you
 flexibility throughout the entire life cycle. Benefit from THE versioning tool for distributed teams!

Different life cycles of model components

Since the models can be divided and versioned individually, each component (submodel) can have its own life cycle

Reuse components in different projects

Individual model parts/components can be reused in different projects and further developed in parallel.

Continuous integration

LemonTree supports a platform approach to modeling as the models can be divided into platform components on the one hand and project components on the other and further developed separately.

Export of model components

Model parts/components can be easily removed from a model and are therefore also available to external developers for further processing.

Prefabricated components

Developers at suppliers or from another internal department can quickly and easily import pre-built model packages into Enterprise Architect and further develop them there. Lemontree Lieber

Import with read permission only

Model parts can be defined as “read-only” so that an internal or external supplier can use these parts but cannot change 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 the models through intelligent model merging

If a component of the model has developed further during parallel processing, the new version can easily be imported.

Managing dependencies between model components

The integrated dependency analysis serves to define model parts more precisely before export.

Contact Us