Software certification - coding, code, and coders

@article{Havelund2011SoftwareC,
  title={Software certification - coding, code, and coders},
  author={Klaus Havelund and Gerard J. Holzmann},
  journal={2011 Proceedings of the Ninth ACM International Conference on Embedded Software (EMSOFT)},
  year={2011},
  pages={205-210}
}
  • K. Havelund, G. Holzmann
  • Published 9 October 2011
  • Computer Science
  • 2011 Proceedings of the Ninth ACM International Conference on Embedded Software (EMSOFT)
We describe a certification approach for software development that has been adopted at our organization. JPL develops robotic spacecraft for the exploration of the solar system. The flight software that controls these spacecraft is considered to be mission critical. We argue that the goal of a software certification process cannot be the development of “perfect” software, i.e., software that can be formally proven to be correct under all imaginable and unimaginable circumstances. More… 

Evidential and Continuous Integration of Software Verification Tools

TLDR
Unless mission-critical embedded software can be developed and verified with less cost and effort, while still satisfying the highest dependability requirements, new mission- critical capabilities such as autonomous control may never reach the market.

Utilizing multicore architectures to enhance software verification in real-time embedded systems

TLDR
The author proposes a novel target-level verification approach which addresses some of the verification challenges posed by modern highly-integrated devices and provides some unique capabilities, but also has some limitations.

Using auxiliary artifacts during code inspection activity: findings from an exploratory study

TLDR
It is suggested that when inspectors use Auxiliary artifacts, their effectiveness in identifying defects is improved and their decision making is more homogeneous than that of inspectors who do not use auxiliary artifacts.

Casos de Garantia de Segurança aplicados a Sistemas Robóticos: Revisão Sistemática da Literatura

Resumo: Contexto: A segurança dos sistemas robóticos é de extrema importância, pois falhas ou acidentes relacionados a eles podem resultar em perdas irreparáveis. Estes sistemas precisam ser

References

SHOWING 1-10 OF 24 REFERENCES

SOFTWARE CONSIDERATIONS IN AIRBORNE SYSTEMS AND EQUIPMENT CERTIFICATION

TLDR
In this article, reuse is defined simply as using previously existing software artifacts as part of the process of creating software systems from predefined software components.

The SPIN Model Checker - primer and reference manual

TLDR
This is the most comprehensive reference guide to SPIN, written by the principal designer of the tool, and gives detailed advice on methods for tackling the most complex software verification problems.

SCRUB: a tool for code reviews

  • G. Holzmann
  • Computer Science
    Innovations in Systems and Software Engineering
  • 2010
TLDR
The tool was designed to support a large team-based software development effort of mission critical software at JPL, but can also be used for individual software development on small projects.

Classes and Interfaces

TLDR
This chapter shows how you can use interfaces in order to create polymorphic classes, and a typical scenario in which one would want to re-factor behaviors into a separate class object.

They write the right stuff

As the 120-ton space shuttle sits surrounded by almost 4 million pounds of rocket fuel, exhaling noxious fumes, visibly impatient to defy gravity, its on-board computers take command. The right stuff

Power of ten

This article deals with the Japanese electronics manufacturer Sharp that is building the world's most ambitious plant for making a new generation of liquid-crystal displays. With the plant, Sharp

Verified Software Systems – the Certification Perspective

  • Verified Software Systems – the Certification Perspective

All rules are 'shall' rules (must be followed), except those marked withwith`*' which are 'should' rules (justified deviations allowed)

  • All rules are 'shall' rules (must be followed), except those marked withwith`*' which are 'should' rules (justified deviations allowed)

JPL Draft Coding Standard for the Java Programming Language

  • JPL Draft Coding Standard for the Java Programming Language

19 Do not use expressions with side effects

  • 19 Do not use expressions with side effects