Embedded automotive vehicle software is characterized by specific execution environment constraints and corresponding implementation strategies. These characteristics seem to run counter to the object-oriented and implementation-independent world of UML software analysis modeling. In order to effectively use UML for embedded automotive vehicle software, a set of mappings is required to translate UML models into an implementation that meets the unique needs of the automotive world.

This paper outlines a specific strategy for translating UML models into a C implementation targeting common embedded automotive requirements: minimum execution time and space overhead, no use of dynamic memory, and pre-allocated and statically initialized structures.