DOI QR코드

DOI QR Code

The Video on Demand System Failure Evaluation of Software Development Step

  • 투고 : 2019.01.28
  • 심사 : 2019.03.26
  • 발행 : 2019.04.30

초록

Failure testing is a test that verifies that the system is operating in accordance with failure response requirements. A typical failure test approaches the operating system by identifying and testing system problems caused by unexpected errors during the operational phase. In this paper, we study how to evaluate these Failure at the software development stage. Evaluate the probability of failure due to code changes through the complexity and duplication of the code, and evaluate the probability of failure due to exceptional situations with bugs and test coverage extracted from static analysis. This paper studies the possibility of failure based on the code quality of software development stage.

키워드

CPTSCQ_2019_v24n4_107_f0001.png 이미지

Fig. 1. presumes of Failure evaluation

CPTSCQ_2019_v24n4_107_f0002.png 이미지

Fig. 2. Model of Failure evaluation

CPTSCQ_2019_v24n4_107_f0003.png 이미지

Fig. 3. part of Source Code

CPTSCQ_2019_v24n4_107_f0004.png 이미지

Fig. 4. static analysis

Table 1. Causes of Failure

CPTSCQ_2019_v24n4_107_t0001.png 이미지

Table 2. Criteria

CPTSCQ_2019_v24n4_107_t0002.png 이미지

Table 3. Weight of Failure

CPTSCQ_2019_v24n4_107_t0003.png 이미지

Table 4. Code complexity criteria

CPTSCQ_2019_v24n4_107_t0004.png 이미지

Table 5. Self Standard

CPTSCQ_2019_v24n4_107_t0005.png 이미지

Table 6. Source Analysis Result

CPTSCQ_2019_v24n4_107_t0006.png 이미지

Table 7. Weight of Failure

CPTSCQ_2019_v24n4_107_t0007.png 이미지

Table 8. Suggestion of improvement plan

CPTSCQ_2019_v24n4_107_t0008.png 이미지

참고문헌

  1. 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.
  2. Park Gee-Yong, Kim Dong Hoon, Lee Dong Young, "Software FMEA analysis for safety-related application software", 96p - 102p, Elsevier, 2014.
  3. TTA, "Software Safety Inspection Guide", 2016.
  4. Alan, Johnston, Ken, "how we test software at microsoft", Microsoft 2008.2.
  5. 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
  6. 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.
  7. Alan, Ken, Johnston, "How We Test Software at Microsoft", Microsoft Pr, 2008.
  8. https://quality-one.com/fmea/