Continuous integration

In the course of the increasingly agile orientation in software development, our customers ask us again and again whether modeling and agility go well together. Our opinion on this is quite clear and has also been proven in various studies: Only with properly applied modeling 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 classic software development for some time. The aim here 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?
In the tool chain around Enterprise Architect (LemonTree, Git, Pro Cloud Server, Prolaborate), you can currently find all the prerequisites to realize 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 would like to present which procedures of the classical software development can be adopted for a “Continuous Modeling” 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.