- Paperback: 704 pages
- Publisher: Addison-Wesley Professional; 1 edition (April 17, 1995)
- Language: English
- ISBN-10: 0201119722
- ISBN-13: 978-0201119725
- Product Dimensions: 6.1 x 1.5 x 9.1 inches
- Shipping Weight: 2.2 pounds (View shipping rates and policies)
- Average Customer Review: 13 customer reviews
Amazon Best Sellers Rank:
#677,188 in Books (See Top 100 in Books)
- #18 in Books > Computers & Technology > Programming > Software Design, Testing & Engineering > Performance Optimization
- #18 in Books > Computers & Technology > Programming > Software Design, Testing & Engineering > Quality Control
- #313 in Books > Computers & Technology > Computer Science > Systems Analysis & Design
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Safeware: System Safety and Computers 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
See the Best Books of 2017
Looking for something great to read? Browse our editors' picks for the best books of the year in fiction, nonfiction, mysteries, children's books, and much more.
Frequently bought together
Customers who bought this item also bought
From the Back Cover
We are building systems today--and using computers to control them--that have the potential for large-scale destruction of life and environment. More than ever, software engineers and system developers, as well as their managers, must understand the issues and develop the skills needed to anticipate and prevent accidents before they occur. Professionals should not require a catastrophe to happen before taking action.
Addressing this need in her long-awaited book, Nancy Levenson examines what is currently known about building safe electromagnetic systems and looks at past accidents to see what practical lessons can be applied to new computer-controlled systems.Software
- Demonstrates the importance of integrating software safety efforts with system safety engineering
- Describes models of accidents and human error that underlie particular approaches to safety problems
- Presents the elements of a software program, including management, hazard analysis, requirements analysis, design for safety, design of the human-machine interface, and verification
About the Author
Nancy G. Leveson is Boeing Professor of Computer Science and Engineering at the University of Washington (and Adjunct Professor at the University of British Columbia). Dr. Leveson recently was awarded the Information System Award from the American Institute of Aeronautics and Astronautics, " . . . for developing the field of software safety and for promoting responsible software and system engineering practices where life and liberty are at stake." She is the Editor-in-Chief of IEEE Transactions on Software Engineering and a meember of the Board of Directors of the Computing Research Association, the National Research Council Commission on Engineering and Technical Systems, and the ACM Committee on Computers and Public Policy. She recently chaired a National Academy of Science study for NASA of the Space Shuttle software development process.
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
This provide over all view of system safety not software safety.
The case studies in appendix are very important for safety engineers.
Appendix A is the therac-25 story on Medical devices.
Appendix B is Apollo 13, the DC-10 and Challenger, Aerospace.
Appendix D is windscale, Three mile island and Chernobyl, Nuclear power.
These are very bad accidents, so we should study more deep.
The naming "safeware" is very good wording, this is not safe software nor safe hardware.
Go ahead, after this book. There are many resources about sytem safety and software safety.
We have already many experiences about HAZOP.
2011/1/18, we have a Workshop on Critical Software(WOCS2011) with Nancy.
The book is a good "bed time reading" that gives an overview of the field, major problems and introduction to some major approaches. It is however not a handbook per se - you will not understand any particular method sufficiently to apply it.
Overall, very good introductory text with a good coverage and a very easy and clear language!
This book won't describe when to use a sequence number or what size CRC is appropriate for your safety-related communication, or what level of code coverage is appropriate or what level of requirement coverage is appropriate for your identified hazard etc. It won't describe the actual versus perceived issues with OOA/OOD, what aspects of a hard real-time design require attention or how to meet the expectations of an independent assessor or certification agency.
The principles of software design assurance/software integrity can be garnered from the standards such as DO-178B, and DO-248-style discussion papers or from CENELEC 50128 and good old MIL-STD-882B to name but a few. Alternatively a free start can be achieved by downloading the Joint Software system Safety Handbook from the US DoD.
Save your money for the works of Moriarty (executive-level), Ericson (introduction/supervised practitioner), or Dunn (software controlled system safety intro) if you must buy something.
But if you're looking for some stories to put into your slick safety presentation or seminar then it might be just the right book.