High-integrity software
From HandWiki
Short description: 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
- Ada (programming language)
- Safety-critical system
- High availability software
- Formal methods
- Software of unknown pedigree
References
- ↑ 1.0 1.1 1.2 "What Is Software Integrity? Overview + Software Integrity Best Practices". https://www.perforce.com/blog/qac/what-is-software-integrity.
- ↑ Sennett, C.T. (2012). High-Integrity Software. Springer Science & Business Media. p. 1. ISBN 978-1-4684-5777-3. https://books.google.com/books?id=6RDrBwAAQBAJ. Retrieved February 14, 2022.
- ↑ Chapman, Rod (September 4, 2024). "Correctness by Construction: The Case for Constructive Static Verification". https://samate.nist.gov/SSATTM_Content/papers/Correctness%20by%20Construction%20-%20Chapman.pdf.
- ↑ "Developing DO-178B/C Compliant Software for Airborne Systems". https://www.aerospacetechreview.com/wp-content/uploads/2020/10/Developing-DO-178B-C-Compliant-Software-for-Airborne-Systems.pdf.
- ↑ European Committee for Electrotechnical Standardization (CENELEC). "CENELEC – EN 50128". https://standards.globalspec.com/std/14317747/EN%2050128.
- ↑ Qi Van Eikema, Hommes (January 25, 2012). "ASSESSMENT OF THE ISO 26262 STANDARD, "ROAD VEHICLES – FUNCTIONAL SAFETY"". 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.
External links
- Boulanger, Jean-Louis (April 13, 2015). CENELEC 50128 and IEC 62279 Standards. John R. Wiley and Sons. ISBN 978-1-84821-634-1.
- Winter, Victor L.; Bhattacharya, Sourav, eds (2001). High Integrity Software. Springer Science+Business Media, LLC. ISBN 978-1-4613-5530-4. https://books.google.com/books?id=z9HgBwAAQBAJ. Retrieved February 14, 2022.
- Wallace, Dolores R.; Ippolito, Laura M.; Kuhn, D. Richard (1992). High Integrity Software Standards and Guidelines. National Institute of Standards and Technology. https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication500-204.pdf. Retrieved February 15, 2022.
 |  |
