An a methodology for building safer software based critical computing systems

2010 IEEE 2nd International Advance Computing Conference, IACC 2010

Volumn , Issue , 2010, Pages 422-429

  Phani Kumar, S ^a   Seetha Ramaiah, P ^b   Khanaa, V ^a  

^a BHARATH UNIVERSITY   (India)

^b ANDHRA UNIVERSITY   (India)

Author keywords

Railroad Crossing Control System(RCCS); Safer software development; Safety critical systems; Software safety; Software safety metrics

Indexed keywords

CIVILIAN AIRCRAFTS; COMPUTER-BASED SYSTEM; COMPUTING SYSTEM; HAZARD ANALYSIS; MEDICAL DEVICES; MODELING SOFTWARES; NUCLEAR PLANT; PRACTICAL PROBLEMS; RISK FREE; SAFETY ASPECTS; SAFETY CRITICAL SYSTEMS; SAFETY METRICS; SAFETY-CRITICAL; SAFETY-CRITICAL FUNCTIONS; SOFTWARE DEVELOPMENT; SOFTWARE DEVELOPMENT PROCESS; SOFTWARE HAZARD ANALYSIS; SOFTWARE SAFETY; SOFTWARE-BASED;

AIRCRAFT ACCIDENTS; AIRCRAFT PLANTS; BIOMEDICAL ENGINEERING; COMPUTER APPLICATIONS; COMPUTER SOFTWARE SELECTION AND EVALUATION; COMPUTER SYSTEM RECOVERY; FLIGHT CONTROL SYSTEMS; HAZARDS; IGNITION; RAILROAD ACCIDENTS; RAILROAD CROSSINGS; RAILROADS; SAFE HANDLING; SAFETY FACTOR; SAFETY TESTING; SECURITY SYSTEMS; STANDARDS;

SOFTWARE DESIGN;

EID: 77951183326     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/IADCC.2010.5422901     Document Type: Conference Paper

References (20)

1. John C. Knight, "Safety Critical Systems: Challenges and Directions", Proceedings of the 24th International Conference on Software Engineering Orlando, Florida, 2002, pp. 547-550
2. NASA. Software Safety: NASA Technical Standard NASA-STD-8719.13A. September 1987
3. NASA Guidebook for Safety Critical Software NASA -GB-1740.13-96
4. Department of Defense. System Safety Program Requirements MILSTD-882C.1984
5. Software considerations in airborne systems and equipment certification. DO178B 1992
6. D. Alberico, J. Bozarth, M. Brown, et. Al. JSSC Software System Safety Handbook; A Technical and Managerial Team Approach December 1999.
7. IEC, International Standard, Functional Safety of Electrical / Electronic / Programmable Electronic Safety- Related Systems - IEC 61508 -3; Part 3 Software Requirements. 1998
8. MISRA. Development Guidelines for Vehicle Based Software. November 1994.
9. H.D. Kuettner, Jr. and P.R. Owen, "Definition and Verification of Critical Safety Functions in Software", Proceedings of the International System Safety Conference (ISSC) 2001. System Safety Society, Unionville,Virginia 2001, pp.337-346.
10. IEEE STD 1228-1994, IEEE Standard for Software Safety Plans, 1994.
11. P.Seetharamaiah and M.Ben Swarup "Towards a methodology for building safe software based systems", Proceedings of the CONQUEST 2008, 11th International Conference on Quality Engineering in Software Technology, Potsdam 2008
12. IEEE100, "The Authoritative Dictionary of IEEE Standard Terms", IEEE Press, 2000.
13. N.G.Leveson and C.S.Turner.An investigation of the Therac-25 accidents. IEEE Computer, 26(7):18-41, March 1987
14. ] James Gleick. The New York Times Magazine 1st December 1996
15. William R. Dunn, "Practical Design of Safety Critical Computer Systems", Reliability Press, 2002.
16. Firesmith, D.G., 2005. Engineering safety-related requirements for software-intensive systems. Proceeding of the 27th International Conference on Software Engineering, May 15-21, St. Louis, Missouri, USA., pp: 720-721. http://portal.acm.org/citation.cfm?id=1062455.106 2635
17. Anderson, P., 2008. Detecting bugs in safety critical code. Dr. Dobbs J., February. http://www.ddj.com/development-tools/206104422
18. Holzmann, G.J., 2006 The power of ten: Rules for developing safety critical code. IEEE Computer, 39: 95-99. DOI: 10.1109/MC.2006.212
19. B. W. Johnson, Design and Analysis of Fault TolerantDigital Systems: Addison-Wesley Publishing Company, 1989
20. Steven K. Iwohar and Dar-Biau Liu, "A Verification Tool to Measure Software in Critical Systems", Proceedings of the Annual Reliability and Maintainability Symposium, p.315- 320, 1995