Software engineering: reliability, development, and management.
Software engineering: reliability, development, and management.
Requirements Specification for Process-Control Systems
IEEE Transactions on Software Engineering
Software reliability and dependability: a roadmap
Proceedings of the Conference on The Future of Software Engineering
Modeling software design diversity: a review
ACM Computing Surveys (CSUR)
Software safety: where's the evidence?
SCS '01 Proceedings of the Sixth Australian workshop on Safety critical systems and software - Volume 3
Safety and Software Intensive Systems: Challenges Old and New
FOSE '07 2007 Future of Software Engineering
Software safety: relating software assurance and software integrity
International Journal of Critical Computer-Based Systems
Challenges in the regulatory approval of medical cyber-physical systems
EMSOFT '11 Proceedings of the ninth ACM international conference on Embedded software
Safety demonstration and software development
SAFECOMP'07 Proceedings of the 26th international conference on Computer Safety, Reliability, and Security
| Hi-index | 0.00 |
This paper discusses a feasibility study which developed estimates of the occurrence rate for significant avionics software problems. Two FAA databases, airworthiness directives (ADs) and service difficulty reports (SDRs) were used. A study of the AD database for large aircraft (1984-1994) revealed 33 avionics ADs, 13 of which were software related. Estimates were made of the operational hours for the fleet of commercial aircraft with computer avionics and the number of problem occurrences. Minimum, maximum and average occurrence rates were established. The average occurrence rate for the 6 resulting data sets was 0.15 per million operating hours. The nonoccurrence of ADs for the remaining avionics was "bounded on the average"; yielding less than 0.02 occurrences/per million hrs. The significant problem occurrence rate for the TCAS system (collision avoidance) software has motivated others to apply proof of correctness techniques to the specification and design of this software (Craigen et al., 1994).