• 응용통계연구
• /
• 제23권3호
• /
• pp.573-584
• /
• 2010

This paper considers the differences in the software execution environments in the testing phase and the operational phase to determine the optimal release time and warranty period of software systems. We formulate equations for the total expected software cost until the end of the software life cycle based on the NHPP. In addition, we derive the optimal release time that minimizes the total expected software cost for an imperfect debugging software reliability model. Finally, we analyze the sensitivity of the optimal testing and maintenance design related to variation of the cost model parameters based on the fault data observed in the actual testing process, and discuss the quantitative properties of the proposed model.

• 품질경영학회지
• /
• 제39권2호
• /
• pp.170-178
• /
• 2011

In general, a software fault detection phenonenon is described by a software reliability model based on a nonhomogeneous Poisson process(NHPP). In this paper, we propose a software reliability growth model considering the differences of the software environments in both the testing phase and the operational phase. Also, we consider the problem of determining the optimal release time and the optimal warranty period that minimize the total expected software cost which takes account of periodic software maintenance(e.g. patch, update, etc). Finally, we analyze the sensitivity of the optimal release time and warranty period based on the fault data observed in the actual testing process.

• 디지털산업정보학회논문지
• /
• 제6권1호
• /
• pp.55-67
• /
• 2010

Decision problem called an optimal release policies, after testing a software system in development phase and transfer it to the user, is studied. The applied model of release time exploited infinite non-homogeneous Poisson process. This infinite non-homogeneous Poisson process is a model which reflects the possibility of introducing new faults when correcting or modifying the software. The failure life-cycle distribution used generalized gamma type distribution which has the efficient various property because of various shape and scale parameter. Thus, software release policies which minimize a total average software cost of development and maintenance under the constraint of satisfying a software reliability requirement becomes an optimal release policies. In a numerical example, after trend test applied and estimated the parameters using maximum likelihood estimation of inter-failure time data, estimated software optimal release time.

• 천문학회보
• /
• 제42권2호
• /
• pp.85.1-85.1
• /
• 2017

We develop a coronagraph to measure the coronal electron density, temperature, and speed by observing the linearly polarized brightness of solar corona with 4 different wavelengths. Through the total solar eclipse on 21 August 2017, we test an operating software of a prototype coronagraph working with two sub-systems of two motorized filter wheels and a CCD camera that are controlled by a portable embedded computer. A Core Flight System (CFS) is a reusable software framework and set of reusable software applications which take advantage of a rich heritage of successful space mission of NASA. We use the CFS software framework to develop the operating software that can control the two sub-systems asynchronously in an observation scenario and communicate with a remote computer about commands, housekeeping data through Ethernet. The software works successfully and obtains about 160 images of 12 filter sets (4 bandpass filters and 3 polarization angles) during the total phase of the total solar eclipse. For the future, we can improve the software reliability by testing the software with a sufficient number of test cases using a testing framework COSMOS. The software will be integrated into the coronagraph for balloon-borne experiments in 2019.

• Journal of Information Processing Systems
• /
• 제16권4호
• /
• pp.915-934
• /
• 2020

Software refactoring is a process to restructure an existing software code while keeping its external behavior the same. Currently, various refactoring techniques are being used to develop more readable and less complex codes by improving the non-functional attributes of software. Refactoring can further improve code maintainability by applying various techniques to the source code, which in turn preserves the behavior of code. Refactoring facilitates bug removal and extends the capabilities of the program. In this paper, an exhaustive review is conducted regarding bad smells present in source code, applications of specific refactoring methods to remove that bad smell and its effect on software quality. A total of 68 studies belonging to 32 journals, 31 conferences, and 5 other sources that were published between the years 2001 and 2019 were shortlisted. The studies were analyzed based on of bad smells identified, refactoring techniques used, and their effects on software metrics. We found that "long method", "feature envy", and "data class" bad smells were identified or corrected in the majority of studies. "Feature envy" smell was detected in 36.66% of the total shortlisted studies. Extract class refactoring approach was used in 38.77% of the total studies, followed by the move method and extract method techniques that were used in 34.69% and 30.61% of the total studies, respectively. The effects of refactoring on complexity and coupling metrics of software were also analyzed in the majority of studies, i.e., 29 studies each. Interestingly, the majority of selected studies (41%) used large open source datasets written in Java language instead of proprietary software. At the end, this study provides future guidelines for conducting research in the field of code refactoring.

• 산업경영시스템학회지
• /
• 제13권22호
• /
• pp.1-6
• /
• 1990

This paper deals with software Release policy having a Fixed Operational period after a Software System is released. The underlying Software Reliability Growth is described by J-M Model Optimal of Software Release Time minimizing Total Expected Cost is Obtained.

• 융합보안논문지
• /
• 제8권4호
• /
• pp.121-126
• /
• 2008

소프트웨어 제품을 개발하여 테스팅을 거친 후 사용자에게 인도하는 시기를 결정하는 일은 아주 실제적이고 흥미 있는 일이 된다. 이러한 문제를 소프트웨어 최적 방출시기라고 한다. 본 연구에서는 이러한 방출문제에 대하여 연구되었다. 수명분포는 감마족 분포에서 대표적인 어랑 문포 모형을 이용한 최적 방출시기에 관한 문제를 다루었다. 소프트웨어 요구 신뢰도를 만족시키고 소프트웨어 개발 및 유지 총비용을 최소화 시키는 최적 소프트웨어 방출 정책에 대하여 논의 되었고 민감도 분석을 이용하여 효율적 최적 방출시기가 논의되었다.

• 한국정밀공학회지
• /
• 제9권1호
• /
• pp.34-43
• /
• 1992

Computer Intergrated Manufacturing (CIM) is an emerging technology which aims at the total automation of a manufacturing system. Despite the extensive research on CIM in this decade, total automation seems to be far from reality for many reasons. In this study, the problems of implementing a CIM system are analyzed and a solution method is suggested. A set of software has been developed and tested for a workstation cotroller which controls closely integrated equipment in the low level of a flexible manufacturing system. The functions of the programs are communications between machines and computers and control of workstation scheduling. The software group is developed on IBM OS/2 operating system with 'c' language to enhance the portability. The usage of the software is presented to users through the Presentation Manager which is menu handler of OS/2 system. Although the software is developed for limited machine equipment, the scheme can be adopted to various machines due to the generality.

• Journal of Information Technology Applications and Management
• /
• 제19권2호
• /
• pp.181-196
• /
• 2012

The cost of software maintenance occupies about two thirds in the software lifecycle. However, it is not easy to estimate the cost of software maintenance because of various viewpoints about software maintenance, unclear estimation methods, and complex procedures. Until now, the cost estimation model has used compensation factors for software characteristic and environment on the basis of program size. Especially, most of existing models use maintenance rate of total software cost as a main variable. This paper suggests the software maintenance cost estimation model that uses the result of calculating real maintenance efforts. In this paper, we classify functional maintenance and non-functional maintenance as software maintenance activity type. For functional maintenance, present function point of target software is needed to evaluate. The suggested maintenance cost evaluation model is applied to a software case in public sector. This paper discusses some differences between our model and other modes.

• 대한안전경영과학회:학술대회논문집
• /
• 대한안전경영과학회 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.