High integrity software

{{Short description|Software}}

{{Cleanup|reason=Niche term with unclear widespread usage; insufficient connections to other related pages; more references needed|date=October 2023}}

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."{{cite web |title=What Is Software Integrity? Overview + Software Integrity Best Practices |url=https://www.perforce.com/blog/qac/what-is-software-integrity |website=perforce.com |access-date=Feb 15, 2022}} Examples of high-integrity software are nuclear reactor control, avionics software, automotive safety-critical software and process control software.{{cite book |last1=Sennett |first1=C.T. |title=High-Integrity Software |date=2012 |publisher=Springer Science & Business Media |isbn=978-1-4684-5777-3 |page=1 |url=https://books.google.com/books?id=6RDrBwAAQBAJ |access-date=Feb 14, 2022}}{{Cite web |last=Chapman |first=Rod |date=September 4, 2024 |title=Correctness by Construction: The Case for Constructive Static Verification |url=https://samate.nist.gov/SSATTM_Content/papers/Correctness%20by%20Construction%20-%20Chapman.pdf |url-status=live |archive-url=https://web.archive.org/web/20060930110232/https://samate.nist.gov/SSATTM_Content/papers/Correctness%20by%20Construction%20-%20Chapman.pdf |archive-date=September 30, 2006 |access-date=September 4, 2024 |website=National Institute of Standards and Technology}}

{{quote| [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.}}

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

  • DO-178C, Software Considerations in Airborne Systems and Equipment Certification{{cite web |title=Developing DO-178B/C Compliant Software for Airborne Systems |url=https://www.aerospacetechreview.com/wp-content/uploads/2020/10/Developing-DO-178B-C-Compliant-Software-for-Airborne-Systems.pdf |website=Parasoft |access-date=Feb 14, 2022}}
  • CENELEC EN 50128, Railway applications – Communication, signalling and processing systems - Software for railway control and protection systems{{cite web |last1=European Committee for Electrotechnical Standardization (CENELEC) |title=CENELEC - EN 50128 |url=https://standards.globalspec.com/std/14317747/EN%2050128 |website=Engineering360 |access-date=Feb 14, 2022}}
  • 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"{{Cite web |last=Qi Van Eikema |first=Hommes |date=January 25, 2012 |title=ASSESSMENT OF THE ISO 26262 STANDARD, "ROAD VEHICLES – FUNCTIONAL SAFETY" |url=https://www.volpe.dot.gov/sites/volpe.dot.gov/files/docs/Assessment%20of%20the%20ISO%2026262%20Standard%2C%20%E2%80%9CRoad%20Vehicles%20%E2%80%93%20Functional%20Safety%E2%80%9D.pdf |url-status=live |archive-url=https://web.archive.org/web/20150714231041/https://www.volpe.dot.gov/sites/volpe.dot.gov/files/docs/Assessment%20of%20the%20ISO%2026262%20Standard%2C%20%E2%80%9CRoad%20Vehicles%20%E2%80%93%20Functional%20Safety%E2%80%9D.pdf |archive-date=July 14, 2015 |access-date=September 4, 2024 |website=U.S. Department of Transportation Volpe Center}}

See also

References

{{reflist}}