Please enable JavaScript.
Coggle requires JavaScript to display documents.
Software Safety (Example of software failures (Ford Recalls F150 and…
Software Safety
-
-
Fault management options
Avoidance: Prevent faults from entering the system during the design phase
“good practices” in design – e.g. programming standards
-
Tolerance: Find faults in operational system after release, allow system to proceed correctly
Recovery blocks:
-
Run “primary module”, then run an “acceptance test”
If test fails, roll back changes and run an “alternative module”
N-version programming:
several independent implementations of a program
Goal: ensure “design diversity”, avoid common faults
Both approaches are costly, and may not be very effective
For a study on whether N-version programming really achieves “design diversity”, read Knight & Leveson’s article.
What is software safety?
-
thereby preventing accidental injury or death, whether intentional or unintentional. (Herrmann)
Features & procedures
-
Procedures: concern the proper environment for the software, and its proper use
-
Physical, mechanical components of environment
-
-
-
-
-
-