Show description

Partitioning or protection, to provide isolation from or containment of faults. Partitioning or protection might also be used to reduce validation and verification effort, since less critical functions require less validation and verification rigor. Partitioning and protection are discussed in Chapter 21. 13. Diversity, which may be used to avoid common faults in two or more items. , compilers), or technologies [5]. 21 22 Developing Safety-Critical Software 14. Redundancy, which may be used to achieve fault tolerance or to avoid a single point of failure.

Org • This book is written so that you can read it from beginning to end, or you can read selected chapters as needed. You will find occasional repetition between some chapters. This is intentional, since some readers may choose to use this book as a reference rather than read it straight through. References to related chapters are included throughout to help those who may not read the text cover to cover. 4 Book Overview This book is divided into five parts. Part I (this part) provides the ­introduction and sets the foundation.

26 Developing Safety-Critical Software Recommendation 10: Develop an integrated lab with accurate models for simulated inputs. The more complete the integration facility, the less the team relies on the aircraft or customer’s facility. The more realistic the simulated input the better. The goal is to sort out as many problems in the lab as possible to avoid the need to troubleshoot in the aircraft or customer’s facility. Recommendation 11: Use validation and verification matrices. Matrices are a simple way to ensure that all requirements are validated and verified and to track the completion of the validation and verification effort.