[1]
C. Hobbs, Embedded Software Development for Safety-Critical Systems.
[2]
Mission-critical and safety-critical systems handbook. Amsterdam: Newnes, 2010. [Online]. Available: http://victoria.alma.exlibrisgroup.com/view/action/uresolver.do?operation=resolveService&package_service_id=6325573540002386&institutionId=2386&customerId=2385
[3]
Leanna Rierson, Developing Safety-Critical Software: A Practical Guide for Aviation Software and DO-178C Compliance. CRC Press; 1 edition. [Online]. Available: https://www.amazon.com/Developing-Safety-Critical-Software-Practical-Compliance/dp/143981368X
[4]
Ian Sommerville, Software Engineering (10th Edition). Pearson; 10 edition. [Online]. Available: https://www.amazon.com/Software-Engineering-10th-Ian-Sommerville/dp/0133943038/ref=sr_1_1?s=books&ie=UTF8&qid=1521069366&sr=1-1&keywords=sommerville+software+engineering
[5]
E. M. Clarke, O. Grumberg, and D. A. Peled, Model checking. Cambridge, Mass: MIT Press, 1999.
[6]
F. Nielson, H. R. Nielson, and C. Hankin, Principles of program analysis. Berlin: Springer, 1999.
[7]
Hovemeyer, David ; Pugh, William, ‘Finding bugs is easy’, ACM SIGPLAN Notices, vol. 39, no. 12, pp. 92–106, 2004, doi: 10.1145/1052883.1052895.
[8]
G. Holzmann, ‘The Power of 10: Rules for Developing Safety-Critical Code’, Computer, vol. 39, no. 6, pp. 95–97, June 2006, doi: 10.1109/MC.2006.212.
[9]
G. J. Holzmann, ‘Mars code’, Communications of the ACM, vol. 57, no. 2, pp. 64–73, Feb. 2014, doi: 10.1145/2560217.2560218.
