Background - Using Event-B for Critical Device Software Systems - page 44

79. Main Commission (1994). Report on the accident to Airbus A320-211 aircraft in Warsaw on
14 September 1993 (Technical report). Warsaw: Aircraft Accident Investigation.
80. Marciniak, J. J. (2002). Encyclopedia of software engineering (2nd ed.). New York: Wiley.
81. McDermid, J. A. (2002). Software hazard and safety analysis. In Proceedings of the 7th
international symposium on formal techniques in real-time and fault-tolerant systems ,
FTRTFT'02 (pp. 23-36). London: Springer. Co-sponsored by IFIP WG 2.2.
82. McDermid, H. C., Forder, J., & Storrs, G. (1993). Sam—a tool to support the construction,
review and evolution of safety arguments. In Directions in safety-critical systems (pp. 195-
216). London: Springer.
83. MIL-STD-882C (1993). System safety program requirements. US DoD. http://www.

system-safety.org/ .
84. Miller, S. P., & Srivas, M. (1995). Formal verification of the AAMP5 microprocessor: A case
study in the industrial use of formal methods. In Proceedings, Workshop on industrial-
strength formal specification techniques (pp. 2-16).
85. Milner, R. (1982). A calculus of communicating systems . Secaucus: Springer.
86. NASA Technical Team (2004). NASA software safety guidebook (Technical report). NASA
Technical Standard.
87. Neumann, P. (1995). Safeware: System safety and computers. Software Engineering Notes ,
20 , 90-91.
88. Overture. Overture: Formal modelling in VDM. http://www.overturetool.org/ .
89. Parnas, D. L. (1972). On the criteria to be used in decomposing systems into modules. Com-
munications of the ACM , 15 , 1053-1058.
90. Paulk, M. C. (1995). The SEI series in software engineering . The capability maturity model:
Guidelines for improving the software process . Reading: Addison-Wesley.
91. Price, D. (1995). Pentium FDIV flaw-lessons learned. IEEE MICRO , 15 (2), 86-88.
92. Redmill, M. C. F., & Catmur, J. (1999). System safety: HAZOP and software HAZOP (1st
ed.). Chichester: Wiley.
93. Register, O. F. (1999). Code of federal regulations . Guidance for industry and FDA: Regu-
lation of medical devices: Background information for international officials .
94. Register, O. F. (2011). Code of federal regulations . Title 21, Food and drugs, Pt. 1-99
(p. 511). Revised as of April 1, 2011. US Independent Agencies and Commissions. ISBN
9780160883941.
95. Rouse, W. B., & Compton, W. D. (2009). Systems engineering and management. Informa-
tion, Knowledge, Systems Management , 8 (1-4), 231-240.
96. RTCA (1992). Do-178B, software considerations in airborne systems and equipment certifi-
cation. Committee: SC-167. http://www.rtca.org/ .
97. Rushby, J. (1995). Formal methods and their role in the certification of critical systems
(Technical report). Safety and reliability of software based systems (twelfth annual CSR
workshop).
98. Schumann, J. M. (2001). Automated theorem proving in software engineering .NewYork:
Springer.
99. Sommerville, I. (1995). Software engineering (5th ed.). Redwood City: Addison-Wesley
Longman.
100. Stepney, S., Cooper, D., & Woodcock, J. (2000). An electronic purse: Specification, refine-
ment, and proof (Technical monograph PRG-126). Oxford University Computing Laboratory
Programming Research Group.
101. Tekinerdogan, B., Sozer, H., & Aksit, M. (2008). Software architecture reliability analysis
using failure scenarios. The Journal of Systems and Software , 81 (4), 558-575.
102. Thomas, M. (1993). The industrial use of formal methods. Microprocessors and Microsys-
tems , 17 , 31-36.
103. Trafford, P. J. (1997). The use of formal methods for safety-critical system . PhD thesis,
Kingston University.