📄 http:^^www.cs.washington.edu^research^projects^safety^www^book.html
字号:
Date: Tue, 10 Dec 1996 03:34:59 GMTServer: NCSA/1.4.2Content-type: text/html<HEAD><TITLE>Safeware: System Safety and Computers</TITLE></HEAD><BODY><pre> <b>SAFEWARE: SYSTEM SAFETY AND COMPUTERS</b> <b>Nancy G. Leveson</b> <b>University of Washington</b></pre><dl><dl><dl><dd><A HREF="http://www.cs.washington.edu/people/faculty/leveson.html"> (leveson@cs.washington.edu)</A> </dl></dl></dl><pre>Publisher: Addison-WesleyISBN: 0-201-11972-2Price: $49.50Contents: This book examines past accidents and what is currently known about building safe electromechanical systems to see what lessons can be applied to new computer-controlled systems. One lesson is that most accidents are not the result of unknown scientific principles but rather of a failure to apply well-known, standard engineering practices. A second lesson is that accidents will not be prevented by technologicalfixes alone, but will require control of all aspects of the development and operation of the system. The features of a methodology for buildingsafety-critical systems are outlined.<h3>PART 1: <i>The Nature of Risk</i> <tt>(126 pages) </tt></h3><hr> Is there a problem? How safe is safe enough? The role of computers in accidents Software myths Why software engineering is hard Problems in ascribing causality A hierarchical model of causality Root causes of accidents Do humans cause most accidents? The need for and role of humans in automated systems<h3><b>PART 2:</b> <i>Introduction to System Safety</i> <tt> (50 pages)</tt></h3><hr> Foundations of system safety (systems theory and systems engineering) Historical development Basic concepts (hazard analysis, design for safety, management), Software system safety Cost and effectiveness of system safety Other approaches to safety (industrial engineering, reliability engineering).<h3><b>PART 3:</b> <i>Definitions and Models</i> <tt> (75 pages) </tt></h3><hr> Terminology Accident models Human task and error models<h3><b>PART 4:</b> <i>Elements of a Safeware Program</i> <tt> (290 pages) </tt></h3><hr> Managing safety (the role of management, setting policy, communication channels, setting up a system safety organization, place in the organizational structure, documentation) The system and software safety process (general tasks, real examples) Hazard analysis (what it is, how to do it, types of models, types of analysis, current models and techniques, limitations, evaluations) Software hazard analysis and requirements analysis Designing for safety Design of the human--machine interface Verification of safety (testing, software fault tree analysis).<h4><b>APPENDICES:</b> <tt> (132 pages) </tt></h4><hr> Detailed descriptions of well-researched accidents along with brief descriptions of industry-specific approaches to safety <h5>Appendix A</h5> Medical Devices: The Therac-25 story <h5>Appendix B</h5> Aerospace: The civil aviation approach to safety, Apollo 13, DC-10, and Challenger <h5>Appendix C</h5> The Chemical Industry: The chemical process industry approach to safety, Seveso, Flixborough, and Bhopal <h5>Appendix D</h5> Nuclear Power: How a nuclear power plant works, The nuclear power approach to safety, Windscale, Three Mile Island, and ChernobylReferences (20 pages)</pre><p></BODY></html>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -