is the concept of continuous integration familiar to you? have you tried, or are you planning, to apply these practices to model-based design? we want to show you how you can succeed at that tough task and present to you our approach to continuous modeling.
the complexity and challenges of any kind of projects, where a piece of code is needed, are getting bigger and bigger. this also applies to model-based design, which is now used in almost every industry. development and maintenance of models is not a single-player problem anymore. in contrast, development teams, usually located at different locations, even in different countries, are connected remotely (especially due to the covid-19 pandemic) and work on different parts of bigger models.
agile methodologies have come to stay and this is an overhead that development teams or companies adopting them from scratch must overcome. the adoption process of some of the most well-known agile methodologies is often underestimated, since the teams that are adopting them must be appropriately coached, new roles must be defined within the organization depending on the methodology, and so on. choosing the right tool, in our case microsoft azure® devops, has been crucial for success. all of that increases the challenges of the efficient model-based development.
do the following points sound familiar to you?
- people sharing parts of models via usb flash drive, emails, or shared network folders
- big bangs when models are put together
- models are developed without any kind of version control system, e.g., git
- unmaintainable and unversioned build scripts
- lack of continuous integration strategy for models
- lack of release and defect management for models
in this case, we want to show you our approach to continuous modeling to solve all these challenges in an elegant way. to this end, we have defined a modeling framework on top of microsoft azure devops. this framework allows us to create, maintain, and extend our existing models faster and more easily than before.
