This content is not included in
your SAE MOBILUS subscription, or you are not logged in.
Requirement Based Safety Monitor Generation and Integration
Technical Paper
2014-01-0214
ISSN: 0148-7191, e-ISSN: 2688-3627
This content contains downloadable datasets
Annotation ability available
Sector:
Language:
English
Abstract
The safety monitor is a high integrity control that monitors the health and performance of safety related computer controlled functions in vehicles. The integrity of the safety monitor code is critical to the overall performance of the control software. Traditionally, once monitor requirements are understood, then the safety monitor is hand coded or created in a modeling environment. New practices such as ISO 26262 prescribe formal or semiformal methods are used against certain classes of foreseeable faults. Recently, a new tool, which is capable of auto-generating C-code based on safety monitor formal functional requirements is available from BTC Company. Ford Motor Company investigated the tool using an application example from a powertrain control feature safety monitor.
The paper describes a pilot project and process assessment, comprising the steps of requirement-based C-code generation, code integration, code analysis and code verification using requirements selected from the powertrain control feature's specification. First, the paper describes the C-code generation process. This includes requirements capture as textual descriptions, the conversion of the requirements to macros, use of these macros in the creation of temporal logic patterns in formal notations, code generation and target code export. Then the paper discusses the code integration process, and after that the paper compares code analysis reports from Polyspace®, one from the pilot requirement based implementation and one from a Simulink® implementation. Afterwards, the paper demonstrates the functional testing of the code at both unit level and vehicle integration level. In conclusion, the paper summarizes the recommendations and lessons-learned with usage of the tools.
Recommended Content
Technical Paper | SOURCES OF CONTAMINATION OF CRANKCASE OIL |
Technical Paper | A Co-Simulation Framework for Full Vehicle Analysis |
Authors
Topic
Citation
Zhao, Y., Rambow, T., Nguyen, C., Boesch, M. et al., "Requirement Based Safety Monitor Generation and Integration," SAE Technical Paper 2014-01-0214, 2014, https://doi.org/10.4271/2014-01-0214.Data Sets - Support Documents
Title | Description | Download |
---|---|---|
Unnamed Dataset 1 |
Also In
References
- Erkkinen , T. and Conrad , M. Safety-Critical Software Development Using Automatic Production Code Generation SAE Technical Paper 2007-01-1493 2007 10.4271/2007-01-1493
- Beine M. Model-Based Software Development for Safety-Critical Systems: TargetLink Reference Workflow dSPACE 2009
- Buttle , D. , Blache , G. , Lefarth , U. , and Wolff , H. Having Your Cake and Eating It: A Model-Based Approach for Satisfying ISO26262 Software Development Requirements SAE Technical Paper 2011-01-1001 2011 10.4271/2011-01-1001
- Aceituna , D. Survey of Concerns in Embedded Systems Requirements Engineering SAE Int. J. Passeng. Cars - Electron. Electr. Syst. 7 1 2013 10.4271/2013-01-2403
- Friedenthal S. , Moore A. , and Steiner R. A Practical Guide to SysML: The Systems Modeling Language 2 nd The MK/OMG Press 2001
- Clarke E. , Grumberg O. , and Peled D. Model Checking The MIT Press 2001
- OMG Systems Modeling Language http://www.omgsysml.org
- Leveson N. Engineering a Safer World The MIT Press 2011
- International Standard ISO 26262 Road Vehicles-Functional Safety, Part 6: Product Development at the Software Level ISO 2011
- BTC Embedded Systems AG BTC Embedded Tester Booklet http://www.btces.de/media/downloads/productinformation/Booklet_BTC_EmbeddedTester.pdf