Page History

Error reporting and error handling play a central role in the engineering and operation of survivable systems.  Survivability is an emergent property of a system as a whole \[[Fisher 99|AA. C References#Fisher 99]\] and depends on the behavior of all of the system's components and the interactions among them.  From the viewpoint of error handling, every system component, down to the smallest routine, can be considered to be a sensor capable of reporting on some aspect of the health of the system.  Any error (i.e., anomaly) ignored, or improperly handled, could threaten delivery of essential system services and thusas a result put at risk the organizational or business mission that the system supports.

\[[Fisher 99|AA. C References#Fisher 99]\]
\[[Horton 90|AA. C References#Horton 90]\] Section 11, p. 168, and Section 14, p. 254
\[[ISO/IEC 9899-:1999|AA. C References#ISO/IEC 9899-1999]\] Sections 7.1.4, 7.9.10.4, and 7.11.6.2
\[[ISO/IEC PDTR 24772|AA. C References#ISO/IEC PDTR 24772]\] "REU Termination strategy" and "NZN Returning error status"
\[[Koenig 89|AA. C References#Koenig 89]\] Section 5.4, p. 73
\[[Lipson 00|AA. C References#Lipson 00]\]
\[[Lipson 06|AA. C References#Lipson 06]\]
\[[MISRA 04|AA. C References#MISRA 04]\] Rule 16.1
\[[Summit 05|AA. C References#Summit 05]\] C-FAQ Question 20.4