Seamless Versioning and Collaboration for Agile Modeling with EA

By Daniel Siegl LieberLieber Software GmbH | Nizam Mohamed Prolaborate Product Owner

The need to go agile is obvious � but how can this work using models? We will take a closer look at how Sparx EA teams can achieve the best of both worlds, granular versioning using Lemon Tree and enterprise collaboration and stakeholder reviews using Prolaborate.

Session Recording

Lemontree 3.0 - Fresh Model Versioning

Questions and Answers

If a Git LFS implementation is not desirable/practicable, and our team's codebase is arranged in a monorepo, what alternatives are available for managing the repo size?
Do you have any metrics on expected repo sizes for a large number of commits on a complicated project?

We here this very often before people start to use Git with LemonTree - but once the started this is not a real issue - but every situation is different so feel free to reach out to us to discuss this in detail welcome@lieberlieber.com

On the gitflow best practice slide, why do they still use the "master" terminology. I thought they changed this to "Main"

Very good question it is an old slide - in our public github it is called "main"

Can you elaborate a bit about the difference on doing a 150% model and using a component library

pls tag "Rolf" this is a question that will be a bit longer to discuss wink
The short Answer would be at LieberLieber we think managed clones with exchangable components are they way forward with the compexity of todays systems and therfor models

So I understand for this that I can manage an Enterprise Architecture documentation and a project architecture documentation. The project architecture documentation feeds the enterprise architecture documentation. Understood. Thank you.Edited

not sure I understand your question or remark - feel free to reach out to me

What's PLE?

Product Line Engineering

Speakers Bio

Daniel Sieg

LieberLieber Software GmbH

Business Development at LieberLieber Software GmbH