• 대한전기학회논문지:시스템및제어부문D
• /
• 제51권1호
• /
• pp.18-25
• /
• 2002

The software reliability is defined, and not only the relations between testing time and reliability, but also the relation between duration following failure fixing and reliability are studied in this paper. The release time making the testing cost to be minimum is determined through evaluating the cost for each condition. Also, the release time is determined depending on the conditions of the first reliability, considering the specified reliability. the optimum release time is determined by simultaneously studying two optimum release time issues that determine both the cost related time and the specified reliability related time. And, each condition and limitation are studied. The trend of the optimum time is also examined.

• 품질경영학회지
• /
• 제26권3호
• /
• pp.141-149
• /
• 1998

It is of great practical interest to decide when to stop testing a software system in the development phase and transfer it to the user. This decision problemcalled an optimal software release one is discussed to specify the a, pp.opriate release time. In almost all studies, the software reliability models used are nonphomogenous Poisson process(NHPP) model with bounded mean value function. HNPP models with unbounded mean value function are more suitable in practice because of the possibility of introducing new faults when correcting or modifying the software. We discuss optimal software release policies which minimize a total average software cost under the constraint of satisfying a software reliability requirement. A numerical example illustrates the results.

• 한국국방경영분석학회지
• /
• 제16권2호
• /
• pp.135-150
• /
• 1990

This paper classifies faults into three types : simple, degenerated, and regenerated faults. This paper also deals with the characteristics of each type of fault to determine the software reliability based on the assumption; i. e., a system consisting of several subsystems (modules) which may be debugged simultaneously. For each type of fault, several formulas are developed to obtain the failure rate and the expected number of failures found during debugging. A model is developed based on the formulas of the failure rate and the expected number of failures to decide the optimal release time of a new software: minimizing the total cost with constraints restricting to the failure rate of each module in the software. By using this model, optimal release times are found for some cases; the eliminated faults are assumed simple faults only, regenerated faults only, simple and degenerated faults, and so on.

• 한국방재학회 논문집
• /
• 제11권2호
• /
• pp.147-156
• /
• 2011

홍수기 다목적댐 운영의 목적은 홍수조절용량을 최대한 이용하여 하류 주요 지점의 첨두홍수량을 저감시키거나, 계획홍수량을 초과하지 않도록 방류량과 방류시점을 조절함으로써 홍수피해규모를 최소화하는 것이다. 따라서 홍수기 다목적댐 운영에 있어 가장 중요한 것은 최적의 방류시점과 방류량의 결정이며 이를 통해 홍수기말 이수용량을 최대로 확보 하는 점이다. 본 연구에서는 다목적 최적화기법의 하나인 goal programming을 이용하여 홍수기 저수지 최적운영을 실시하였다. goal programming은 선형계획법 또는 비선형계획법을 이용하여 두 개 이상의 목적을 가진 문제의 최적 대안을 구하기 위해, 목표값으로부터의 편차의 합을 최소화하여 최적화하는 기법이다. 홍수기 다목적댐 운영에서 goal programming의 적용성을 검토하기 위해 실제 홍수 사상을 이용하여, 단일저수지 운영과 저수지 연계운영을 실시하였다. 단일저수지 운영을 적용하기 위한 시험유역으로는 충주댐 유역을 선정하였고 저수지 연계운영을 적용하기 위한 시험유역으로는 안동댐과 임하댐 유역을 선정하였다. goal programming의 결과 분석을 위해 저수지 모의운영 모형인 HEC-5 모형의 결과와 비교, 분석하였다. 검토 결과 goal programming을 이용할 경우 홍수기 말에 저수지 수위를 홍수기제한수위로 유지할 수 있었으며 주요 지점의 홍수량을 매 시간 적절히 계획홍수량 아래로 유지할 수 있었다. goal programming을 이용한 최적 운영의 경우 전 구간의 유입량을 알고 있다고 가정한 점에서 실제 저수지 운영과는 차이가 있으나, 적절한 제약조건을 적용하고 홍수예경보를 이용하여 예보된 유입량을 활용하면 최적의 방류량 시점과 방류량을 산정하여 홍수기 다목적댐을 효율적으로 운영할 수 있으며 주요 지점의 홍수량도 저감할 수 있을 것으로 판단된다.

• 대한안전경영과학회:학술대회논문집
• /
• 대한안전경영과학회 2011년도 춘계학술대회
• /
• pp.451-459
• /
• 2011

In this paper, a software release model is presented to determine the optimum testing time with consideration of software error type. The software errors are classified into two types, major and minor errors. The software testing is continued until the Nth major error is discovered and corrected. The total cost needed before and after testing time is modeled under nonhomogeneous Poisson error correction model. Numerical examples are presented to demonstrate the results.

• 한국소프트웨어감정평가학회 논문지
• /
• 제16권2호
• /
• pp.69-76
• /
• 2020

본 논문에서는 오류 수정 난이도를 나타내는 지표인 오류 수정 시간을 사용하여 소프트웨어 최적 출시 시점 결정 문제를 연구하였다. 특히 기존의 오류 수정 시간을 고려한 소프트웨어 신뢰도 성장 모델에서 오류 발견 시간과 수정 시간이 독립적이라는 가정을 수정하고, 오류 발견 시간과 수정 시간의 상관관계를 표현할 수 있는 일반적인 프레임워크 모델을 설정하여 소프트웨어 최적 출시 시점을 결정해 보고자 하였다. 그 결과 테스트 초기에 수정 시간이 걸리는 오류를 발견하는 것이 경제적인 관점에서 중요하다는 것을 알 수 있었다. 최적의 소프트웨어 출시 시점을 결정하는 데에 있어서 오류발견시간과 오류수정시간의 상관관계를 분석하는 것이 매우 중요하다는 결론을 얻을 수 있었다.

• Communications for Statistical Applications and Methods
• /
• 제12권3호
• /
• pp.697-704
• /
• 2005

Computer software has gradually become an indispensable elements in many aspects of our daily lives and an important factor in numerous systems. In recent years, it is not unusual that the software cost is more than the hardware cost in many situations. In addition to the costs of developing software, the repair cost resulting from the software failures are even more significant. In this paper, a cost model with warranty cost, time to remove each fault detected in the software system, and delivery delay cost is developed. We use a software reliability model based on non-homogeneous Poisson process (NHPP). We discuss the optimal release policies to minimize the expected total software cost. Numerical examples are provided to illustrate the results.

• 한국경영과학회:학술대회논문집
• /
• 대한산업공학회/한국경영과학회 1991년도 춘계공동학술대회 발표논문 및 초록집; 전북대학교, 전주; 26-27 Apr. 1991
• /
• pp.405-421
• /
• 1991

In this paper, faults existing in a software system is classified into three types; simple, degenerative and regenerative faults. The reliability functions and failure rates of both a software module and system which have a mixture of such faults are obtained and the expected number of failures in the system after time T is also derived. Using the formulas obtained, a cost-reliability model and an efficient algorithm for optimal software release time are proposed via nonlinear programming formulation ; minimizing the total test cost with constraints on the failure rates of each module. Application of this model to several cases are presented and it appears to be more realistic.

• Journal of Information Technology Applications and Management
• /
• 제11권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.

• 산업경영시스템학회지
• /
• 제9권13호
• /
• pp.29-32
• /
• 1986

A decision procedure to determine when computer software should be released after testing is described. This paper extends optimum release policies minimizing the total expected software cost with a scheduled software delivery time under reliability requirement constraint. Such cost considerations enable us to make a release decision as to when transfer a software system from testing phase to operational phase. The underlying model is software reliability growth model described by a nonhomogeneous poisson process. It is assumed that the penalty cost function due to delay for a scheduled software delivery time is linearly proportional to time. Numerical examples are shown to illustrate the results.