Skip to main content
Log in

Software Safety Architecture that can be Formally Verified

  • Electronics
  • Published:
AutoTechnology

Abstract

In modern vehicles, safety-related functions often depend on electronic components and it is increasingly important to ensure, by means of an appropriate development process, that the software that controls these components is correct. In order to handle the increasing complexity of future control systems, efficient verification methods are needed to cut down the time and costs spent on testing.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Similar content being viewed by others

References

  1. Chonlawit Banphawatthanarak: Verification of Stateflow Diagrams Using SMV. Technical Report Department of Electrical and Computer Engineering, Carnegie Mellon University, Pittsburgh, May 2000.

    Google Scholar 

  2. K. L. McMillan: Symbolic Model Checking. Kluwer Academic Publishers, 1993

    Book  MATH  Google Scholar 

  3. Friedemann Bitsch: Classification of Safety Requirements for Formal Verification of Software Models of Industrial Automation Systems. In Proceedings of 13th International Conference on Software and Systems Engineering and their Applications (ICSSEA) 2000, CNAM — Paris, France.

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

About this article

Cite this article

Cossy, M. Software Safety Architecture that can be Formally Verified. AutoTechnol 4, 66–68 (2004). https://doi.org/10.1007/BF03246810

Download citation

  • Issue Date:

  • DOI: https://doi.org/10.1007/BF03246810

Keywords

Navigation