Ensuring the Integrity of Embedded Software with Static Code Analysis

Chelf, Ben; Ebert, Christof

doi:10.1109/ms.2009.65

Cited by 8 publications

(3 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Polyspace analyzeslarge Ada programs and helps to uncover runtime errors falling into the category of overflows and underflows, divide-by-zero and other arithmetic errors, out-of-bounds array access, read access to non-initialized data, indefinite loops, dead codes and dangerous type conversions. [2].…”

Section: Selection Of Polyspace Verifier As a Static Analysis Tool For Onboard Softwarementioning

confidence: 99%

Verification of On-board Software of ISRO Launch Vehicles Using Polyspace-A Case Study

Sherine

Ranjan

Jayalal

et al. 2018

2018 7th International Conference on Reliability, Infocom Technologies and Optimization (Trends and Future Directions) (ICRITO)

View full text Add to dashboard Cite

With advent of novel and complex Launch vehicle missions and increase in frequency of launches, Onboard software development lifecycle demands a faster and error free mode of operations. The increased pace of development calls for the need of more and more automation being built into both development and quality assurance processes. Exhaustive manual testing of complex embedded software poses many challenges involving both time and effort. Moreover, it is highly essential to uncover the errors at earlier stages of software lifecycle rather than allowing the errors to migrate till end which results in increase of cost and effort to correct it. Static Verification of the code has been proven as one of the effective mechanisms in uncovering potential defects that would escape even multiple test strategies. In this paper we will be sharing our experiences of using Polyspace verifier -a static analysis tool which helped us in bringing out several significant pointers to error prone conditions in Onboard software and thereby correcting it before unit testing. Application software involved in the Guidance and control of the Launch vehicle was selected for the analysis purpose

show abstract

Section: Selection Of Polyspace Verifier As a Static Analysis Tool For Onboard Softwarementioning

confidence: 99%

Verification of On-board Software of ISRO Launch Vehicles Using Polyspace-A Case Study

Sherine

Ranjan

Jayalal

et al. 2018

2018 7th International Conference on Reliability, Infocom Technologies and Optimization (Trends and Future Directions) (ICRITO)

View full text Add to dashboard Cite

show abstract

“…• The developers of critical embedded systems can ensure that their software code performs as intended by using static code analysis methods and tools [15]. Some static code analysis tools, such as Prevent 4 , Polyspace 5 or Astrée 6 , can check the correctness and security issues in implementation with languages like C, C++, Java or Ada.…”

Section: • the Attack Described In Attacks Againstmentioning

confidence: 99%

SEcuring Integrated Modular Avionics Computers

Dessiatnikoff

Nicomette

Alata

et al. 2013

2013 IEEE/AIAA 32nd Digital Avionics Systems Conference (DASC)

View full text Add to dashboard Cite

The evolution of aircraft IT infrastructure tends to increasingly share computing resources between different applications, use COTS hardware and software, be open to applications and equipment provided by the airlines, and communicate with the outside world. This trend would give more opportunities for potential attackers to corrupt the onboard computing systems, if adequate security measures were not taken to counter these threats. This paper proposes 1) a classification of the potential attacks that may target avionics embedded systems and 2) a description of attack experiments that have been carried out on an experimental realtime kernel compliant with the ARINC-653 standard. It also proposes several generic countermeasures in order to improve the security of avionic embedded systems.

show abstract

“…In order to achieve such an aim many test approaches have to be performed throughout the different stages of the development life cycle of a specific application. Those Tests intend to assure and offer reliable, high-quality and healthy performing software and thereby a good product for the market, because defects or failures may lead to dramatic consequences in case the software is concerned with performing a safety-critical mission (example of embedded software failure is therac-25 radiation machine [5]). The 3 different basic test disciplines followed to get reliable and robust software products are listed below:…”

Section: Model Based Design -Testing Strategiesmentioning

confidence: 99%

A partially automated HiL test environment for model-based development using Simulink® and OPC technology

Chaaban

Schwarz

Batchuluun

et al. 2011

2011 XXIII International Symposium on Information, Communication and Automation Technologies

View full text Add to dashboard Cite

This paper is concerned with the design procedures of an automated testing tool, developed in Matlab ® /Simulink ® environment, that performs software verification during runtime on a PLC (Programmable Logic Controller) or so called HiL test (Hardware-in-the-Loop) for model-based development of control applications. In addition to checking the "semantic" or "functional" correctness of the automatically generated C++ -Code with RTW (Real Time Workshop ® ) for algorithms designed and developed in Simulink ® on hardware targets, the tool compares results obtained from the HiL test with the results of the MiL test (Model-in-the-Loop) performed in early stage of development for the same developed application. The main purpose behind this work is to develop reliable software that fulfil system requirements and to test its behaviour during realtime hardware simulation, in order to achieve the validation step which represents the terminating -step of almost all projects.

show abstract

Ensuring the Integrity of Embedded Software with Static Code Analysis

Cited by 8 publications

References 4 publications

Verification of On-board Software of ISRO Launch Vehicles Using Polyspace-A Case Study

Verification of On-board Software of ISRO Launch Vehicles Using Polyspace-A Case Study

SEcuring Integrated Modular Avionics Computers

A partially automated HiL test environment for model-based development using Simulink® and OPC technology

Contact Info

Product

Resources

About

Ensuring the Integrity of Embedded Software with Static Code Analysis

Cited by 8 publications

References 4 publications

Verification of On-board Software of ISRO Launch Vehicles Using Polyspace-A Case Study

Verification of On-board Software of ISRO Launch Vehicles Using Polyspace-A Case Study

SEcuring Integrated Modular Avionics Computers

A partially automated HiL test environment for model-based development using Simulink&#x00AE; and OPC technology

Contact Info

Product

Resources

About

A partially automated HiL test environment for model-based development using Simulink® and OPC technology