High-integrity software

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.[2][3]

[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 Certification[4]
  • CENELEC EN 50128, Railway applications – Communication, signalling and processing systems – Software for railway control and protection systems[5]
  • 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

References

  1. ^ a b c "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.
Stub icon

This article related to a type of software is a stub. You can help Wikipedia by adding missing information.

Stub icon

This software-engineering-related article is a stub. You can help Wikipedia by adding missing information.

Content Disclaimer

Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.

  1. The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
  2. There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
  3. It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
  4. Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
  5. Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.