Heiko Dörr

Experiences with model and autocode reviews in model-based software development

Through the introduction of the model-based development, paradigm models became first class citizens in the development of in-vehicle software and are thus also object to strict quality assurance. Just as code reviews are widespread in classical software development, models also have to undergo a stringent review procedure - particularly if they serve as a basis for automatic software implementation by means of model-based code generators. In addition to model reviews, the generated production code (autocode) must be reviewed by performing so-called autocode reviews. This paper presents our procedures for a combined model and autocode reviews and provides examples, lessons learned, as well as significant experimental results drawn from a typical automotive embedded software development project.

Model-Based Development of In-Vehicle Software

Mathematical modeling, which already is established for a long time in many engineering domains, now also gains strongly in importance in the development of embedded software. In the automotive sector (Schauffele and Zurawka, 2003), modeling is used on the one hand for the conceptual anticipation of the functionality to be realized (open/closed loop control, monitoring) and, on the other, for the simulation of the behavior of real physical systems (plant, environment)

Using Model and Code Reviews in Model-based Development of ECU Software

In the automotive industry, the model-based approach is increasingly establishing itself as a standard paradigm for developing control unit software. Just as code reviews are widespread in classical software development as a quality assurance measure, models also have to undergo a stringent review procedure – particularly if they serve as a starting point for automatic implementation by code generators. In addition to these model reviews, the generated production code is reviewed later in the development process by performing auto code reviews. This article will present procedures for and give an account of experiences with model and code reviews which have been adapted to the model-based development process.