Article · Wikipedia archive · Last revised Jun 17, 2026

High-integrity software

High-integrity software is software whose failure may cause serious damage with possible "life-threatening consequences". "Integrity is important as it demonstrates the safety, security, and maintainability of code." Examples of high-integrity software are nuclear reactor control, avionics software, automotive safety-critical software and process control software. [H]igh integrity means that the code: Does what it should. Can be tested. Has security features. Lacks security vulnerabilities. Is easy to understand and follow logically. Is easy to edit and upgrade without introducing new errors.

Last revised
Jun 17, 2026
Read time
≈ 2 min
Length
371 w
Citations
8
Source
Wikipedia ↗

High-integrity software is software whose failure may cause serious damage with possible "life-threatening consequences".1 "Integrity is important as it demonstrates the safety, security, and maintainability of code."1 Examples of high-integrity software are nuclear reactor control, avionics software, automotive safety-critical software and process control software.23

[H]igh integrity means that the code:

  • Does what it should.
  • Can be tested.
  • Has security features.
  • Lacks security vulnerabilities.
  • Is easy to understand and follow logically.
  • Is easy to edit and upgrade without introducing new errors.1

A number of standards are applicable to high-integrity software, including:

  • DO-178C, Software Considerations in Airborne Systems and Equipment Certification4
  • CENELEC EN 50128, Railway applications – Communication, signalling and processing systems – Software for railway control and protection systems5
  • IEC 61508, Functional Safety of Electrical/Electronic/Programmable Electronic Safety-related Systems (E/E/PE, or E/E/PES)
  • ISO 26262, Road Vehicles – Functional Safety (especially 'part 6' of the standard, which is titled "Product development at the software level"6
See also

See also

References

References

  1. "What Is Software Integrity? Overview + Software Integrity Best Practices". perforce.com. Retrieved February 15, 2022.
  2. Sennett, C.T. (2012). High-Integrity Software. Springer Science & Business Media. p. 1. ISBN 978-1-4684-5777-3. Retrieved February 14, 2022.
  3. Chapman, Rod (September 4, 2024). "Correctness by Construction: The Case for Constructive Static Verification" (PDF). National Institute of Standards and Technology. Archived (PDF) from the original on September 30, 2006. Retrieved September 4, 2024.
  4. "Developing DO-178B/C Compliant Software for Airborne Systems" (PDF). Parasoft. Retrieved February 14, 2022.
  5. European Committee for Electrotechnical Standardization (CENELEC). "CENELEC – EN 50128". Engineering360. Retrieved February 14, 2022.
  6. Qi Van Eikema, Hommes (January 25, 2012). "ASSESSMENT OF THE ISO 26262 STANDARD, "ROAD VEHICLES – FUNCTIONAL SAFETY"" (PDF). U.S. Department of Transportation Volpe Center. Archived (PDF) from the original on July 14, 2015. Retrieved September 4, 2024.
External links