• The Journal of Korean Institute of Communications and Information Sciences
• /
• v.29 no.6A
• /
• pp.589-599
• /
• 2004

Most models assume the complete debugging environments by requiring a complete software correction in quantitative evaluation of software reliability. But, in many case, new faults are involved in debugging works, for complete software correction is impossible. In this paper, software growth model is proposed about incomplete debugging environments by considering the possibility of new faults involvements, and software faults occurrence status are also mentioned about NHPP by considering software faults under software operation environments and native faults owing to the randomly involved faults in operation before test. While, effective quantitative measurements are derived in software reliability evaluation, applied results are suggested by using actual data, and fitnesswith existing models are also compared and analyzed.

• The KIPS Transactions:PartD
• /
• v.9D no.4
• /
• pp.659-666
• /
• 2002

Park, Seo and Kim (12) developed the input domain-based SRGM, which was able to quantitatively assess the reliability of a software system during the testing and operational phases. They assumed perfect debugging during testing and debugging phase. To make this input domain-based SRGM more realistic, this assumption should be relaxed. In this paper we generalize the input domain-based SRGM under imperfect debugging. Then its statistical characteristics are investigated.

• The Transactions of the Korea Information Processing Society
• /
• v.5 no.5
• /
• pp.1225-1233
• /
• 1998

An important issue for software developers is to determine when to stop testing the software system and release it to users. Generally the release time is specified by the number of detected faults or the testing time needed to meet the reliability requirement. Software reliability directly depends on the number of remaining or corrected faults. All the detected faults are not always corrected under imperfect debugging environment. We therefore need a new approach to software release policy for imperfect debugging. This paper suggests a software release policy, which guarantees that the reliability requirement has been achieved. The suggested policy is then implemented and illustrated for specific SRGMs.

• Electronics and Telecommunications Trends
• /
• v.18 no.5 s.83
• /
• pp.63-72
• /
• 2003

소프트웨어의 신뢰성을 정량적으로 평가하는 데 있어서 소프트웨어 개발 프로세스의 시험단계나 사용자의 운용단계에 처한 동적 환경상태에서 소프트웨어 고장발생기능 현상을 기술한 소프트웨어 신뢰도성장모델을 많이 제안하고 있다. 대다수의 모델이 발생된 소프트웨어 고장의 발생원인에 대한 완전한 수정을 요구하는 완전 디버깅 환경을 가정하고 있다. 그러나 실제 개발자가 디버깅 작업을 수행할 때 완전한 수정이 불가능하기 때문이다. 다시 말해서 여러 소프트웨어 개발자가 경험한 이러한 디버깅 작업을 행하는 경우에는 결함을 제거하는 데 한계가 있기 때문에 수정 작업시 새로운 결함이 삽입되는 경우가 많다. 즉, 결함 수정은 불완전 환경에 처한다. 본 논문에서는 결함 수정시 신규 결함의 삽입 가능성을 고려하고 불완전 디버깅 환경에 대한 소프트웨어 신뢰도 성장모델을 제안한다. 소프트웨어 동작 환경 하에서 발생된 소프트웨어 고장과 시험 전 소프트웨어 내의 고유 결함에 의한 고장과 동작중에 랜덤하게 삽입된 결함에 의해 발생되는 고장 등 2종류의 결함을 고려하여 비동차 포아송과정(NHPP)에 의한 소프트웨어 고장발생 현상을 기술한다. 또한 소프트웨어 신뢰성 평가에 유용한 정량적인 척도를 도출하고 실측 데이터를 이용하여 적용한 결과를 제시하고 기존의 모델과의 적합성을 비교, 분석한다.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2005.05a
• /
• pp.345-348
• /
• 2005

소프트웨어 결함은 그것을 찾아내는 것도 힘들지만 정확한 해법을 찾는 것도 쉽지 않을 뿐더러, 또 테스트자의 능력 여하에 따라 수정중에 새로운 결함이 도입될 수도 있기 때문에 검출된 결함이 완벽하게 제거되기는 쉽지 않다. 따라서, 결함 제거 효율은 개발중인 소프트웨어의 신뢰도 성장이나 테스트 및 수정비용에 영향을 크게 미친다. 이는 소프트웨어 개발의 모든 과정에서 매우 유용한 척도로서 개발자가 디버깅 효율을 평가하는데 크게 도움이 될 뿐더러, 추가로 소요되는 작업량을 예측할 수 있게 해준다. 그러므로 개발 소프트웨어의 신뢰도와 비용면에서 불완전 디버깅의 영향을 연구하는 것은 매우 중요하다고 할 수 있으며, 이는 최적 인도 시각이나 운영 예산에도 영향을 줄 수 있다. 본 논문에서는 개발중인 소프트웨어를 대상으로 하여 디버깅이 완전하지 않으며, 이 때문에 디버깅 중 새로운 결함이 도입될 수도 있다는 제안하에 보편적으로 사용되는 신뢰도 모델을 대상으로 불완전 디버깅 범위로까지 소프트웨어의 신뢰도와 비용 문제를 확장하여 연구한다.

• Journal of the Korea Institute of Information and Communication Engineering
• /
• v.12 no.4
• /
• pp.737-743
• /
• 2008

I compare my parameter estimation methodoloay with existing method, considering both of testing effort and fault detecting rate simultaneously in software reliability modeling. Generally speaking, fault detection/removal mechanism depends on how apply previous fault detection/removal and testing effort of S/W. The fault removal efficiency makes large influence to the reliability growth, testing and removal cost in developing stage S/W. This is very useful measure during all the developing stages and much helpful for the developer to estimate debugging efficiency, and furthermore, to anticipate additional working amount.

• The Journal of Korean Institute of Communications and Information Sciences
• /
• v.30 no.11A
• /
• pp.987-994
• /
• 2005

Most of the proposed SRGMs are required to perfect debugging based on removal of defect as soon as the detection of defects in system tests. But the detected defects are corrected after few days as a fixed time or induced new fault in software under the imperfect debugging environments. Solving these problems, we discussed that the formal software reliability model considered testing-effort for the fault detection and correction of software defects, and then using this model we have estimated of the software reliability closed to practical conditions.

• Journal of Information Technology Applications and Management
• /
• v.11 no.4
• /
• pp.87-94
• /
• 2004

The software reliability growth model(SRGM) has been developed in order to estimate such reliability measures as remaining fault number, failure rate and reliability for the developing stage software. Almost of them assumed that the faults detected during testing were evetually removed. Namely, they have studied SRGM based on the assumption that the faults detected during testing were perfectly removed. The fault removing efficiency. however. IS imperfect and it is widely known as so in general. It is very difficult to remove detected fault perfectly because the fault detecting is not easy and new error may be introduced during debugging and correcting. Therefore, the fault detecting efficiency may influence the SRGM or cost of developing software. It is a very useful measure for the developing software. much helpful for the developer to evaluate the debugging efficiency, and, moreover, help to additional workloads necessary. Therefore. it is very important to evaluate the effect of imperfect dubugging in point of SRGM and cost. and may influence the optimal release time and operational budget. I extent and study the generally used reliability and cost models to the imperfect debugging range in this paper.

• The Transactions of the Korea Information Processing Society
• /
• v.7 no.4
• /
• pp.1103-1111
• /
• 2000

The hyper-geometric distribution software reliability growth model (HGDM) usually assumes that all the software faults detected are perfectly removed without introducing new faults. However, since new faults can be introduced during the test-and-debug phase, the perfect debugging assumption should be relaxed. In this context, Hou, Kuo and Chang [7] developed a modified HGDM for imperfect debugging environment, assuming tat the learning factor is constant. In this paper we extend the existing imperfect debugging HGDM for tow respects: introduction of random sensitivity factor and allowance of variable learning factor. Then the statistical characteristics of he suggested model are studied and its applications to two real data sets are demonstrated.

• Journal of Advanced Navigation Technology
• /
• v.14 no.1
• /
• pp.119-126
• /
• 2010

The software reliability growth model(SRGM) has been developed in order to estimate such reliability measures as remaining fault number, failure rate and reliability for the developing stage software. Almost of them assumed that the faults detected during testing were eventually removed. Namely, they have studied SRGM based on the assumption that the faults detected during testing were perfectly removed. The fault removing efficiency, however, is imperfect and it is widely known as so in general. It is very difficult to remove detected fault perfectly because the fault detecting is not easy and new error may be introduced during debugging and correcting. Therefore, We want to study imperfect software testing effort for the logistic testing effort which is thought to be the most adequate in this paper.