English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Tools annual

Global: Zendy Free Plan

Global: Zendy Tools monthly

Global: Zendy Plus monthly

The book’s final chapter provides advice on how to persuade management that fault injection is worth including in their development process. My difficulty is that I’m still not convinced myself. I must admit that I only have experience of mutation testing and have not yet tried any other fault injection techniques. The book comes with a CD-ROM that includes demonstration tools for software mutation of Fortran and EPA of C/C11, although you need a Unix machine to run them. My main problem lies in the apparent cost. The authors admit that a fault injection tool ‘costs in the tens of thousands of U.S. dollars’ and then there are the additional training and operational costs. Knowing that both authors work for the major supplier of these tools does not help and I believe most readers will want to consult a second, more objective view before spending the necessary time and money seriously investigating fault injection. The authors suggest that the ‘most convincing case for fault injection involves % liability’, which presents a rather depressing view of the software industry. If this is the case, then based on their legal system, U.S. developers will be years (if not decades) ahead of most of their counterparts in this field. The preface states that it is intended for both practitioners and advanced students of software engineering, and this book provides an ideal text to support a module covering software fault injection. A minor failing of the book is the lack of diagrams. There are thirty pages of text, albeit excellently written, before the first diagram appears. Even when fault injection tool architectures are explained, few visual models are provided. It makes you wonder how they were designed. The book does have one major flaw. This is the lack of empirical data, which seems strange given the authors’ unique position. For instance, it would be useful to know how much it costs to apply a given fault injection technique to a system of a given size. An explanation of why simulated faults, despite being poor representations of real faults, still provide sensible results would have been a useful inclusion. This is, after all, the basis of fault injection. Overall I strongly recommend this book to anyone with an interest in high integrity software. I predict it will remain the standard text on fault injection for years to come.

Correct Systems: Building a Business Process Solution, by Mike Holcombe and Florentin Ipate, Springer-Verlag, 1998 (Book Review)