Software FMEA: A missing link in design for robustness

SAE Technical Papers

Volumn , Issue , 2005, Pages

  Raheja, Dev ^a  

^a Design for Competitiveness Inc   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

PRODUCT DESIGN;

DESIGN PROGRESS; IN-CONTROL; PRODUCT RECALLS; ROBUST DESIGNS; ROBUST SOFTWARE; SOFTWARE FAILURE; SOFTWARE FMEA;

SOFTWARE DESIGN;

EID: 85072461470     PISSN: 01487191     EISSN: 26883627     Source Type: Journal    
DOI: 10.4271/2005-01-0817     Document Type: Conference Paper

References (7)

1. NIST (National Institute of Standards and Technology), Planning Report 02-3, "The Economic Impact of Inadequate Infrastructure for Software Testing" May 2003.
2. SAE JA 1002, "Software Reliability Program Standard" January 2004
3. Raheja, Dev, "Assurance Technologies: Principles and Practices" McGraw-Hill, 1991
4. Goddard, P.L., "Software FMEA Techniques" Proceedings of the Annual Reliability and Maintainability Symposium, January 2000.
5. Hecht Herbert, An Xuegao, Hecht Myron, "Computer Aided Software FMEA for Unified Modeling Language Based Software" Proceedings of the Annual Reliability and Maintainability Symposium, January 2004.
6. Ozarin, Nathaniel, "Developing Rules for Failure Modes and Effects Analysis of Computer Software" SAE Congress Paper 2003-01-2987.
7. Bowles John B., Wan Chi, "Software Failure Modes and Effects Analysis for a Small Embedded Control System" Proceedings of the Annual Reliability and Maintainability Symposium, January 2001. NIST (National Institute of Standards and Technology), Planning Report 02-3, "The Economic Impact of Inadequate Infrastructure for Software Testing" May 2003.