In the course of the increasingly agile orientation in software development, our customers ask us again and again whether modelling and agility go well together. Our opinion on this is quite clear and has also been proven in various studies: Only with properly applied modelling can agile processes be implemented at all in the face of increasing complexity, if you also want to document all regulations and requirements in a comprehensible way. As an example, we want to deal in this text with „Continuous Integration“, which has been state of the art in classical software development for some time. The aim is to continuously compile, test and merge the software product to be developed. In addition, the status of the development is published regularly: internally a stable development status, externally an official release of the software.

But how do you bring „Continuous Integration“ into model-based software development? The tool chain around Enterprise Architect (LemonTree, Git, Pro Cloud Server, Prolaborate) currently offers all the prerequisites to realise this scenario. From our experience, these possibilities are currently unique on the market and they open up completely new possibilities for our customers. Therefore, we want to present to you which procedures of classical software development can be adopted for „continuous modelling“ with this tool chain. It will also become clear that working with a central database (Prolaborate) and using LemonTree/Git are not contradictory, but can be used very well in parallel.


You can download the entire whitepaper here for free: