• Journal of Korea Society of Digital Industry and Information Management
• /
• v.9 no.4
• /
• pp.239-249
• /
• 2013

The role of software process is getting more important to make good quality softwares. One of the measures to improve the software process is Defect Removal Efficiency(DRE). DRE gives a measure of the development team ability to remove defects prior to release. It is calculated as a ratio of defects resolved to total number of defects found. Software Engineering Levels are usually decided by CMMI Model. The model is designed to help organizations improve their software product and service development, acquisition, and maintenance processes. The score of software engineering levels can be calculated by CMMI model. The levels are composed of the three groups(absent, average, and advanced). This study is to find if there is any difference among the three categories in term of the result of software engineering levels on DRE. We propose One way ANOVA to analyze influence of software engineering levels on DRE. Bootstrap method is also used to estimate the sampling distribution of the original sample because the data are not sampled randomly. The method is a statistical method for estimating the sampling distribution of an estimator by sampling with replacement from the original sample. The data were collected in 106 software development projects by the survey. The result of this study tells that there is some difference of DRE among the groups. The higher the software engineering level of a specific company becomes, the better its DRE gets, which means that the companies trying to improve software process can increase their good management performance.

• The Journal of Korea Institute of Information, Electronics, and Communication Technology
• /
• v.11 no.6
• /
• pp.645-650
• /
• 2018

Software stability is the possibility of operating without any malfunction in the operating environment over time. In a finite failure NHPP for software failure analysis, the failure occurrence rate may be constant, monotonically increasing, or monotonically decreasing. In this study, based on the NHPP model and based on the software failure time data, we compared and analyzed the attributes of the software development cost model using the exponential distribution Rayleigh distribution and inverse exponential distribution considering the shape parameter of the Weibull distribution as the life distribution. The results of this study show that the Rayleigh model is the fastest release time and has the economic cost compared to the inverse-exponential model and the Goel-Okumoto model. Using the results of this study, it can be expected that software developers and operators will be able to predict the optimal release time and economic development cost.

• Journal of Information Technology Applications and Management
• /
• v.13 no.4
• /
• pp.1-12
• /
• 2006

Many software reliability growth models(SRGM) have been proposed since the software reliability issue was raised in 1972. The technology to estimate and grow the reliability of developing S/W to target value during testing phase were developed using them. Most of these propositions assumed the S/W debugging testing efforts be constant or even did not consider them. A few papers were presented as the software reliability evaluation considering the testing effort was important afterwards. The testing effort forms which have been presented by this kind of papers were exponential, Rayleigh, Weibull, or logistic functions, and one of these 4 types was used as a testing effort function depending on the S/W developing circumstances. I propose the methology to evaluate the SRGM using least square estimator and maximum likelihood estimator for those 4 functions, and then examine parameters applying actual data adopted from real field test of developing S/W.

• The Transactions of the Korea Information Processing Society
• /
• v.4 no.2
• /
• pp.409-429
• /
• 1997

Problems encountered during software development or pteration nay result from defects in the software,ghrdware,or their oterations.Because of their diversity,the determination of the sources of a problem and its corrective adtion requires a centrally controlled system for monitoring provlems and detemining systematiccauses. In the paper,the SPR/SCR management system was developed and applied for the collection and analysis of the error data,process data and product data delected by each phasd in SDLC.There are four objectibes in the SPR/SCR management system.The first is to assure that software errors are documented,corrected,and vot forgottem. The second is to assure that SPR.are assessed for their validity.The third is to provide feedback on SPR status to the developer and the user.The fourth is ot prvide data for measuring and prediciting sofware quality and reliability.These goals could be satisfied by the application of the SPR/SCR mangement system.Also,the accomplishment rate of software reliability,criterion of test completion,estimation of release time, efficient development and management can be reflected by applying the SPR/SCR management system.

• Proceedings of the Korean Operations and Management Science Society Conference
• /
• 2002.05a
• /
• pp.585-589
• /
• 2002

본 연구에서는 소프트웨어의 출시 이후 주기적인 보수(periodic maintenance)를 고려한 출시 시기 결정 방법을 제시하였다. 출시시기 결정방법에 관한 연구는 소프트웨어의 신뢰성 확보, 사용자 편의성 등에 관한 연구와 더불어 중요한 연구 분야로 여겨지는 분야이다. 일반 적으로 소프트웨어는 출시 이후에도 패치(patch), 서비스팩(service pack)등을 통해 지속적인 보수가 이루어지기 때문에, 출시 이후의 보수를 고려하여 출시시기를 결정하는 방법론이 필요하다. 이를 위해, 출시 이후의 보수정책을 반영한 소프트웨어 신뢰성 성장 모형(software reliability growth model)을 도출하였다. 위 모형을 기반으로 하여 비용과 신뢰성에 근거한 소프트웨어 출시 시점을 결정해 보았다. 제시된 모형의 타당성을 검증하기 위해 예제를 통해 기존의 논문에서 제시되었던 결과들과 비교분석을 해 보았다. 본 연구의 결과는 기존 연구에서 고려되지 않았던 보수 정책을 고려함으로써, 보다 현실에 가까운 모형을 제시하였다는 점에서 의의를 찾을 수 있고, 출시 후 보수 시점, 보수 정책 등의 결정에도 기여할 수 있을 것이다.

• Proceedings of the Korea Database Society Conference
• /
• 1999.10a
• /
• pp.165-171
• /
• 1999

형상관리는 프로젝트를 추진함에 있어 현실적으로 필수적인 관리 항목으로 인식할 필요성이 대두되고 있다. 그 이유는 프로젝트를 성공적으로 완료하기 위해서는 전체 프로젝트 공정을 통해 사전에 계획된 절차에 준하여 단계별로 어떻게 추진되고 있는지 추진과정을 추적, 확인되어야 하며, 또한 추진 결과에 있어 단계별로 어떤 결과물이 양산되고 있는지를 검증 및 확인하여야 하기 때문이다. 본 논문에서는 이러한 형상관리를 위해서는 프로젝트 수행 초기에 형상관리 계획을 입안하기 위한 형상관리 조직형태를 제안하며 작성된 계획서에 수록된 형상관리 조직을 운영함에 있어 필요한 형상관리활동의 주요 내용들에 대해 국내외 표준 및 지침에 대해 조사하였으며, 현실적으로 공공 프로젝트를 추진함에 있어 형상관리를 위한 필수관리 항목과 문서화 기준 및 이들 문서들간의 연관성에 대해 연구, 제안한다.

• Proceedings of the KAIS Fall Conference
• /
• 2011.05a
• /
• pp.176-178
• /
• 2011

본 연구에서는 소프트웨어 제품을 개발하여 테스팅을 거친 후 사용자에게 인도하는 시기를 결정하는 방출문제에 대하여 연구되었다. 인도시기에 관한 모형은 무한 고장수에 의존하는 비동질적인 포아송 과정을 적용하였다. 이러한 포아송 과정은 소프트웨어의 결함을 제거하거나 수정 작업 중에도 새로운 결함이 발생될 가능성을 반영하는 모형이다. 강도함수는 로그-로지스틱 패턴을 이용하였다. 따라서 소프트웨어 요구 신뢰도를 만족시키고 소프트웨어 개발 및 유지 총비용을 최소화 시키는 방출시간이 최적 소프트웨어 방출 정책이 된다.

• Proceedings of the KAIS Fall Conference
• /
• 2011.05a
• /
• pp.179-181
• /
• 2011

본 연구에서는 소프트웨어 제품을 개발하여 테스팅을 거친 후 사용자에게 인도하는 시기를 결정하는 방출문제에 대하여 연구되었다. 인도시기에 관한 모형은 무한 고장수에 의존하는 비동질적인 포아송 과정을 적용하였다. 이러한 포아송 과정은 소프트웨어의 결함을 제거하거나 수정 작업 중에도 새로운 결함이 발생될 가능성을 반영하는 모형이다. 강도함수는 중첩 패턴을 이용하였다. 따라서 소프트웨어 요구 신뢰도를 만족시키고 소프트웨어 개발 및 유지 총비용을 최소화 시키는 방출시간이 최적 소프트웨어 방출 정책이 된다.

• The Transactions of the Korea Information Processing Society
• /
• v.4 no.9
• /
• pp.2391-2402
• /
• 1997

TINA is the Open Networking Architecture which as newly introduced software architecture shares the network managements and the service managements on the Distributed Processing Environment. In this paper, based on the concepts and principles defined up to now, we implement and test the CM(Connection Management) Package included in CM which is one of the six functional areas into which TINA Management Architecture is devided. Before the implementation we learn the basic concepts accepted by the four architectures in TINA, and medelling concept of the CM. The interfaces of eaxh information objects explain the functions of computational objects implemented, and the message flows among the computational objects show the connection setup and release procedures.

• Journal of Korean Society for Quality Management
• /
• v.31 no.3
• /
• pp.136-159
• /
• 2003

The purpose of this paper is to propose the effective guidance of Quality Circle(QC) activities. Since 1975, variety of organizations in Korea have widely implemented QC activities for their management systems. The industries have enthusiastically used QC activities and were influenced from them. However, the academics were less interested in this subject, as a result, there were no systematic guidances for QC activities. Thus, in this paper, the effective guidance for QC activities were suggested which were based on the survey from QC proceedings presented in the companies, in the local areas and the national wide contests. As a result, the first main issue is to pick repeated mistakes up during the process period such as unmatched the causes and effects relations in characteristics diagrams, improper selection of important control items in Pareto diagram and so on. Secondly, how to overcome statistics and use them for QC activities. Thirdly, to remind team members about Quality Control 7 tools. Finally, Minitab(Release-13) software has been found that it is not matched with using Korean Standards(KS).