Hazard Analysis Techniques for System Safety

Good reference but I didn’t realize I was renting it. However, it stops a lot of arguments

As an assigned textbook, most potential buyers will have little choice in whether to buy the book or not; the book is required. For instructors, this is likely the best -- only? -- book available appropriate for the subject. Based on the book content, the author is clearly very knowledgeable on the subject.Unfortunately, the author actually adds to the complexity of the material. In many ways, the book reads like a military manual written by a committee whose priority was to include input without regard for readability or comprehension/retention by the reader. Conflicting and arbitrary abstractions only add to the confusion of a subject already full of abstraction layers.First, there is a plethora of acronyms common to military texts. Some acronyms, like PHA, have multiple possible meanings (preliminary hazard analysis or process hazard analysis). Some acronyms are fully justified, like HCF for Hazard Causal Factor, while others seem more like the abbreviation abuse in a text message among teenagers like ET (event tree), SC (safety critical), or CF (configuration management). JBAPIRDMIDAA (Just because a phrase is repeated doesn't mean it deserves an acronym). Likewise, while an abbreviation might be useful when placed in a flow chart or graphic like STP (software test plan), PDR (preliminary design review), or FT (fault tree) does not mean the author should use that in the text. When every sentence contains 2-3 acronyms explained once, 15 pages earlier, the text becomes unreadable. Reading many sentences is like trying to translate from an unknown foreign language using a dictionary.For example, on page 89 we find a typical sentence, "In some respects, the MM approach to developing an SMM is very much like a fault tree analysis (FTA) in visual modeling logical SFPs, except without the rigid methodology requirements of FTA." If you don't have your English-Acronym dictionary handy, that is mind mapping (MM), system mishap model (SMM), and SFP is not in the glossary. Ironically, just a few pages earlier, the author cautioned readers on how to write about hazards, "Do not abbreviate or assume readers understand program-special lingo and acronyms."In the author's defense, the field of hazard analysis depends largely on documents written by the US military. Most of the acronyms and abstraction models were likely developed by the military, and a complete study needs to include the references, however cryptic.Second, the author adds to the complexity. The author describes conceptual definition of a 'hazard' developed by Pat Clemens that breaks a hazard down into the source, mechanism, and outcome. Propane tank, leak, spark, explosion. The definition is simple and easy to understand. Of course, this has to be abbreviated S, M, and O. The author is unsatisfied with this easily understood and remembered breakdown. So, in the name of "increased descriptive comprehension" he adds numerous syllables without any discernible improvement in comprehension. Source becomes HS (hazard source) [given this is hazard analysis, what other source would we be referring to?]. Mechanism becomes IM (initiating mechanism) [ kind of like always requiring any reference to a machine be qualified with whether the machine was running/operating, or not]. Outcome becomes T/TO (Target/Threat Outcome) [ ...because we might be confused by non-target or non-threat outcomes?].Given the nature of the material, perhaps this is unduly harsh criticism. I doubt I could complete a similar textbook. Even if I did, I doubt my work would be as complete or as useful as this book. As a student though, I find the writing style and presentation to be more of an obstacle than an assistance in learning the material.

This book is great reference for system safety engineering. I work as a system safety engineer and I go to the book when ever I need to understand a particular hazard analysis I can look it up in the book. The book also helped me understand mishaps, hazards and causes. This is not the kind of book you should read cover to cover, but it has been very helpful in my job as a system safety . engineer.

Very detailed and descriptive examples - the only confusing part was the addition of the types versus techniques. This to me this just muddied the waters. Would be much easier to state that during this phase use this analysis (example: Design phase - PHL, PHA) and be done with it. Other than that, very good book, great reference to have at all times.Kerry LeMonsSystem Safety Engineer

Very logical presentation of all material.

Didn't care for the way it was written.. Seemed to repeat itself a lot

Decent textbook.

Very germane, best in class

Excellent Book

The first edition of this book has been on my desk since 2006. Both my colleagues have a copy on their desks too (we work at different locations). As far as I know, this is the only book that explains the theory of system safety. I use it at least once per week.Recently I ordered and received the second edition. Mr. Ericson has updated the original chapters and added eight new ones. I'm impressed. The second edition takes MIL-STD 882E into account. I'm very happy with the new edition and have requested copies for my colleagues.Two minor points of criticism:1) There is no reference to IEC 61508 for electric/electronic/programmable electronic equipment (incl. software),2) There is no reference to the "safety cases" that are required by the British (DEF-STAN 00-56) and Australian (DEF(AUST)-5679) authorities as well as by the offshore industry.Having said that, I still hold the opinion that not only does this book deserve five stars, it MUST be on the desk of every system safety professional/practitioner.

Haven't finished it yet but have covered the theory chapters and now into the method chapters. So far this is an excellent book. The only pedantic points I have is the overuse of acronyms and very occasional grammatical mistakes that require interpreting.My background is Systems Engineering in safety critical systems. This is book is a good primer.