Overview of existing safeguarding techniques for automatically generated code

Through the introduction of model-based development, paradigm models became first class citizens in the development of invehicle 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 procedure for a combined model and autocode review and provides examples, lessons learned, as well as significant experimental results drawn from a typical automotive embedded software development project.

show abstract

“…Therefore, autocode reviews are a valuable and necessary safeguarding technique for automatically generated code cf. [20].…”

Section: Discussionmentioning

confidence: 99%

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

Stürmer

Conrad

Fey

et al. 2006

Proceedings of the 2006 International Workshop on Software Engineering for Automotive Systems

Self Cite

View full text Add to dashboard Cite

show abstract

“…Earlier work on verification and validation of code generation from models includes [4,5,11,28]. Typically, a combination of translation validation and translator validation approaches were discussed.…”

Section: Related Workmentioning

confidence: 99%

Testing-based translation validation of generated code in the context of IEC 61508

Conrad

2009

Form Methods Syst Des

Self Cite

View full text Add to dashboard Cite

Production code generation with Model-Based Design has successfully replaced manual coding across various industries and application domains. Furthermore, code generated from executable graphical models is increasingly being deployed in high-integrity embedded applications.To validate the model-to-code translation process, generated software components and its precursory stages (i.e. models) should be subjected to an appropriate combination of quality assurance measures. For high-integrity applications, compliance with safety standards such as IEC 61508 needs to be demonstrated as well.On principle, translation validation of generated code could be carried out in the same manner as for manually written code. However, this would not leverage the advantages of Model-Based Design and w.r.t. process efficiency this would leave something to be desired. Therefore, engineering methods and tools for effective and efficient translation validation of generated code are highly desirable. As a step towards this goal, a workflow for verification and validation of models and generated code will be proposed and as far as possible mapped onto the objectives of IEC 61508-3. A cornerstone of this workflow is testing for numerical equivalence between models and generated code.

show abstract

“…Ideally, the code generator, itself, should be qualified or even formally verified, but this is rarely done: the direct V&V of code generators is generally too laborious and complicated due to their complex nature, while testing the generator itself can require detailed knowledge of the (often proprietary) transformations it applies [5], [6]. Moreover, the qualification is only specific to the use of the generator within a given project, and needs to be repeated for every project and for every version of the tool.…”

Section: Autocode Assurancementioning

confidence: 99%

Generating Code Review Documentation for Auto-Generated Mission-Critical Software

Denney

Fischer

2009

2009 Third IEEE International Conference on Space Mission Challenges for Information Technology

View full text Add to dashboard Cite

Model-based design and automated code generation are increasingly used at NASA to produce actual flight code, particularly in the Guidance, Navigation, and Control domain. However, since code generators are typically not qualified, there is no guarantee that their output is correct, and consequently auto-generated code still needs to be fully tested and certified. We have thus developed AUTOCERT, a generator-independent plug-in that supports the certification of auto-generated code. AUTOCERT takes a set of mission safety requirements, and formally verifies that the autogenerated code satisfies these requirements. It generates a natural language report that explains why and how the code complies with the specified requirements. The report is hyper-linked to both the program and the verification conditions and thus provides a high-level structured argument containing tracing information for use in code reviews.

show abstract

Overview of existing safeguarding techniques for automatically generated code

Cited by 18 publications

References 0 publications

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

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

Testing-based translation validation of generated code in the context of IEC 61508

Generating Code Review Documentation for Auto-Generated Mission-Critical Software

Contact Info

Product

Resources

About