Abstract
Nancy Leveson has observed that few safety failures are due to coding errors [152]; for this reason, it is claimed that verification, although desirable, is not the most cost effective use of a limited budget. Evidence does show that safety failures tend to arise instead from requirements or design decisions [205]; however, low-level implementation decisions can also have a large impact on higher level decisions. For example, the removal of a defensive conditional clause from the source code of the inertial reference system of Ariane 5 would have been safe, except for the requirement to execute the ground-based function during flight [88]. When assessing the safety impact of requirement and design decisions there are always worries about the accuracy of the documentation and whether some decisions have not been recorded, or left implicit.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsPreview
Unable to display preview. Download preview PDF.
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2006 Springer-Verlag Berlin Heidelberg
About this chapter
Cite this chapter
Clayton, P., O’Halloran, C. (2006). Using the Compliance Notation in Industry. In: Cavalcanti, A., Sampaio, A., Woodcock, J. (eds) Refinement Techniques in Software Engineering. PSSE 2004. Lecture Notes in Computer Science, vol 3167. Springer, Berlin, Heidelberg. https://doi.org/10.1007/11889229_7
Download citation
DOI: https://doi.org/10.1007/11889229_7
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-46253-8
Online ISBN: 978-3-540-46254-5
eBook Packages: Computer ScienceComputer Science (R0)