The Ariane 5 software failure

  title={The Ariane 5 software failure},
  author={Mark Dowson},
  journal={ACM SIGSOFT Softw. Eng. Notes},
  • M. Dowson
  • Published 1 March 1997
  • Computer Science
  • ACM SIGSOFT Softw. Eng. 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: 

Reliability of safety‐critical systems: A state‐of‐the‐art review

Safety‐critical systems are designed to prevent catastrophic consequences from failure, such as injury or death to humans and environmental damage. These must be carefully designed to ensure

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.

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.

On Supervisor Synthesis via Active Automata Learning

Two algorithms are presented, SupL∗ and MSL, that directly learn supervisors when provided with a simulator of the SUL and its corresponding specifications, and two algorithms that learn a modular supervisor for the system under learning, that is, several smaller supervisors, one for each specification.

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.

Teaching software engineering: an active learning experience

Teaching has changed; students, too. Software engineering is always evolving. In this paper, the authors present their experience teaching an introductory course to software engineering applying

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.

Model Integrated Decomposition and Assisted Specification (MIDAS)

The goal of MIDAS is to address the many challenges observed in applying the current model‐based certification guidance, and the principal issue with interpreting the current guidance is a misplaced focus on the separation of graphical vs. textual specification rather than a clean and clear separation of design from intent.

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.