Fig. 1. presumes of Failure evaluation
Fig. 2. Model of Failure evaluation
Fig. 3. part of Source Code
Fig. 4. static analysis
Table 1. Causes of Failure
Table 2. Criteria
Table 3. Weight of Failure
Table 4. Code complexity criteria
Table 5. Self Standard
Table 6. Source Analysis Result
Table 7. Weight of Failure
Table 8. Suggestion of improvement plan
References
- ByungRae Cha, MyeongSoo Choi, Sun Park, JongWon Ki,"Verification Test of Failover Recovery Technique based on Software-Defined RAID", Smart Media Journal, Vol.5, No.1, 2016.
- Park Gee-Yong, Kim Dong Hoon, Lee Dong Young, "Software FMEA analysis for safety-related application software", 96p - 102p, Elsevier, 2014.
- TTA, "Software Safety Inspection Guide", 2016.
- Alan, Johnston, Ken, "how we test software at microsoft", Microsoft 2008.2.
- T. McCabe, "A Complexity Measure," IEEE Trans. Software Eng.,vol. 2, no. 4, pp. 308-320, Dec. 1976. https://doi.org/10.1109/TSE.1976.233837
- Tim Menzies, Member, IEEE, Jeremy Greenwald, and Art Frank, "Data Mining Static Code Attributes to Learn Defect Predictors", IEEE TRANSACTIONS ON SOFTWARE ENGINEERING, VOL. 32, NO. 11, JANUARY 2007.
- Alan, Ken, Johnston, "How We Test Software at Microsoft", Microsoft Pr, 2008.
- https://quality-one.com/fmea/