CFP last date
20 May 2024
Reseach Article

Software Safety Analysis of Ball Position Control System using SFMEA

by Kadupukotla Satish Kumar, Panchumarthy Seetha Ramaiah
International Journal of Computer Applications
Foundation of Computer Science (FCS), NY, USA
Volume 143 - Number 5
Year of Publication: 2016
Authors: Kadupukotla Satish Kumar, Panchumarthy Seetha Ramaiah
10.5120/ijca2016910170

Kadupukotla Satish Kumar, Panchumarthy Seetha Ramaiah . Software Safety Analysis of Ball Position Control System using SFMEA. International Journal of Computer Applications. 143, 5 ( Jun 2016), 1-7. DOI=10.5120/ijca2016910170

@article{ 10.5120/ijca2016910170,
author = { Kadupukotla Satish Kumar, Panchumarthy Seetha Ramaiah },
title = { Software Safety Analysis of Ball Position Control System using SFMEA },
journal = { International Journal of Computer Applications },
issue_date = { Jun 2016 },
volume = { 143 },
number = { 5 },
month = { Jun },
year = { 2016 },
issn = { 0975-8887 },
pages = { 1-7 },
numpages = {9},
url = { https://ijcaonline.org/archives/volume143/number5/25070-2016910170/ },
doi = { 10.5120/ijca2016910170 },
publisher = {Foundation of Computer Science (FCS), NY, USA},
address = {New York, USA}
}
%0 Journal Article
%1 2024-02-06T23:45:30.012104+05:30
%A Kadupukotla Satish Kumar
%A Panchumarthy Seetha Ramaiah
%T Software Safety Analysis of Ball Position Control System using SFMEA
%J International Journal of Computer Applications
%@ 0975-8887
%V 143
%N 5
%P 1-7
%D 2016
%I Foundation of Computer Science (FCS), NY, USA
Abstract

Software Failure Modes and Effects Analysis (SFMEA) is a traditional system safety analysis technique which is widely used in the aerospace, automotive and other safety-critical intensive systems. However, traditional FMEA methods are difficult to identify and analyzing the failure modes which caused by the dynamic logical information between interfaces or functions, such as softwarehardware interaction. To intuitively assume the effects of module failures in a system, numerous approaches have been proposed. This work addresses the use of SFMEA by using an experiment for safety-critical embedded control systems. The work presented here provides a general example illustrating how SFMEA can be effectively applied to an 8-bit micro-controller (Chip 89S52) based computer control system having little or no hardware protection. This paper also describes Functional FMEA, interface FMEA, and detailed software FMEAs. The experimental results of SFMEA also found the hardware failures and memory faults. The safety analysis reveals several design deficiencies and physical faults for which modifications are needed. This paper also found that, when properly implemented SFMEA at the right point in the Software Development Life cycle, it makes requirements, design and code reviews more effective. It also identifies single point failures due to software.

References
  1. Isaksen, U., Bowen, J.P. and Nissanke, N. (1997) System and Software Safety in Critical Systems, Technical Report RUCS/97/TR/062/A, University of Reading, UK.
  2. Office of Science and Engineering Laboratories (OSEL) 2011 Annual Report.
  3. Nathaniel Ozarin (2004) Failure Modes and Effects Analysis During Design of Computer Software. Proceedings of The Annual Reliability and maintainability Symposium.
  4. MIL-STD-1543 (1974), Reliability Program Requirements for Space and Missile Systems.
  5. SAMSO-STD 77-2, (1977) Failure Modes and Effects Analysis For Satellite, Launch Vehicle and Re-entry Systems.
  6. R.T. Anderson,(1976) Reliability Design Handbook, IIT Research Institute, Catalog No. RDH-376.
  7. P. L. Goddard (1993)Validating the safety of real time control systems using FMEA, Proc. Ann. Reliability and Maintainability Symp. pp. 227-230.
  8. P.L. Goddard,(2000) Software FMEA Techniques, Proc. Ann. Reliability and Maintainability Symp, pp. 118-123.
  9. Goble, W. (2012). The FMEA method .INTECH, 59(2), 14-16,18,20. Retrieved from http://search.proquest. com.ezproxy.libproxy.db.erau.edu/docview/ 1008351257?accountid=27203
  10. McKinney, B. T. (1991). FMECA, the right way. InReliability and Maintainability Symposium, 1991.Proceedings., Annual (pp. 253-259) IEEE.
  11. De Miguel, M. A., Fernandez, J., Pauly, B., & Person, T. (2005). Model-Based integration of safety analysis and reliable software development. In Object-Oriented Real-Time Dependable Systems, 10th IEEE International Workshop on (pp. 312-319) IEEE.
  12. Franceschini, F., & Galetto, M. (2001). A new approach for evaluation of risk priorities of failure modes in FMEA.International Journal of Production Research, 39(13), 2991-3002.
  13. Jenab, K., & Dhillon, B.S. (2005). Group-based failure effects analysis (GFEA). International Journal of Reliability, Quality and Safety Engineering, 12(4), 291-307.
  14. Illiashenko, O., & Babeshko, E. (2012). Choosing FMECAbased techniques and tools for safety analysis of critical systems. Information & Security, 28(2), 275-285.
  15. Bozzano, M., & Villafiorita, A. (2010). Design and safety assessment of critical systems.CRC Press.
  16. Haider, A. A., & Nadeem, A. (2013). A survey of safety analysis techniques for safety critical systems.International Journal of Future Computer and Communication, 2(2), 134-137. doi:10.7763/IJFCC.2013.V2.137
  17. Chao, L. P., & Ishii, K. (2007). Design process error proofing: failure modes and effects analysis of the design process. Journal of Mechanical Design, 129(5), 491-501.
  18. Dale, C., & Anderson, T. (2009). Safety-Critical Systems: Problems, Process and Practice: Proceedings of the Seventeenth Safety-Critical Systems Symposium Brighton, UK, Springer Science & Business Media.
  19. K. Jenab and J. Pineau / Management Science Letters 5 (2015), Failure mode and effect analysis on safety critical components of space travel.pp. 669678.
Index Terms

Computer Science
Information Sciences

Keywords

BPCS Software Safety SFMEA