Concurrency control and recovery in database systems
Concurrency control and recovery in database systems
High-Availability Computer Systems
Computer
The Byzantine Generals Problem
ACM Transactions on Programming Languages and Systems (TOPLAS)
Distributed Algorithms
Requirements engineering as a key to holistic software quality
ISCIS'06 Proceedings of the 21st international conference on Computer and Information Sciences
Proof-based system engineering using a virtual system model
ISAS'05 Proceedings of the Second international conference on Service Availability
Empirical study of root cause analysis of software failure
ACM SIGSOFT Software Engineering Notes
| Hi-index | 0.00 |
The report issued by the Inquiry Board in charge of inspecting the Ariane 5 flight 501 failure concludes that causes of the failure are rooted into poor S/W Engineering practice. From the failure scenario described in the Inquiry Board report, it is possible to infer what, in our view, are the real causes of the 501 failure. We develop arguments to demonstrate that the real causes of the 501 failure are neither S/W specification errors nor S/W design errors. Real causes of the failure are faults in the capture of the overall Ariane 5 application/ environment requirements, and faults in the design and the dimensioning of the Ariane 5 on-board computing system. These faults result from not following a rigorous System Engineering approach, such as applying a proof-based System Engineering method. What is proof-based System Engineering for Computing Systems is also presented.