The Ariane 5 software failure

  title={The Ariane 5 software failure},
  author={Mark Dowson},
  journal={ACM Sigsoft Software Engineering Notes},
  • M. Dowson
  • Published 1997
  • Computer Science
  • ACM Sigsoft Software Engineering Notes
On 4 June 1996, the Ariane 501 satellite launch failed catastrophically 40 seconds after initiation of the flight sequence, incurring a direct cost of approximately $370 million. The Inquiry Board Report (IBR), clearly identifies the proximate cause of the disaster as a software failure; but in other respects is one of the more astonishing engineering documents of our time. In summary, the sequence of events was as follows: 
Examining a Beta Test
The design parameters associated with a good beta test were catalogued and the actual behaviors and results produced by the study’s beta testers were examined to determine the degree the publisher could be confident the game met the criteria of targeted audience propriety, playability, model fidelity and algorithmic accuracy. Expand
The Validity and Effectiveness of a Business Game Beta Test
This article first catalogs the design parameters associated with a good beta test, then compares this ideal against the beta test created for a first-generation online business game released by a major online game publisher and examines the actual behaviors and results produced by the study's beta testers. Expand
Compliance-aware engineering process plans: the case of space software engineering processes
This analysis is based on qualitative criteria targeting the effort dictated by task demands required to create a CaEPP for software development with ACCEPT, and finds that such a level is adequate since it responds to the information needs required by the ECSS-E-ST-40C framework. Expand
On Supervisor Synthesis via Active Automata Learning
Our society’s reliance on computer-controlled systems is rapidly growing. Such systems are found in various devices, ranging from simple light switches to safety-critical systems like autonomousExpand
Human-centric verification for software safety and security
The aim of this chapter is to help clarify the role of language in the development of knowledge representation and the role that language plays in the interpretation of knowledge. Expand
S4: Simple, Secure, Survivable Systems Human-first crisis technology design principles
Crisis responders can pre-emptively share information, invest and work with existing technology design and development experts that reflect the S4 principles for efficient, effective solutions that enhance response capabilities both now and in future scenarios. Expand
A time-predictable parallel programing model for real-time systems
This thesis pushes the limits of the use of task-based parallel programming models in general, and OpenMP in particular, in critical real-time embedded domains. Expand