Experience using MISRA Targetlink Guidelines on a Production Hybrid Program

As the size and complexity of vehicle electronic control systems has increased, embedded software developers have adopted model-based development techniques to help to offset the increased development effort. While these techniques can improve productivity in terms of amount of code generated per day, they need to be used within a structured software development process if they are to deliver an effort reduction over the whole software product lifecycle. Many of the same types of software engineering tools and techniques that are used when developing in an imperative programming language are equally applicable when developing using model-based techniques. One such technique is the use of language subsets, such as MISRA C, in order to avoid language features that are either poorly defined or commonly misunderstood. The MISRA Autocode Guidelines provide similar guidance on the use of some of the more commonly used modeling tools, with particular reference to automatic code generation for production purposes. This paper presents our experience of using the MISRA Autocode Guidelines for TargetLink to automatically generate code for a production mild hybrid control application.