• Journal of Korea Society of Digital Industry and Information Management
• /
• v.9 no.2
• /
• pp.1-10
• /
• 2013

In this paper, make a study decision problem called an optimal release policies after testing a software system in development phase and transfer it to the user. In the course of correcting or modifying the software, finite failure non-homogeneous Poisson process model, presented and was proposed release policies of the life distribution, half-logistic and log-logistic distributions model which used to an area of reliability because of various shape and scale parameter. In this paper, discuss optimal software release policies which minimize a total average software cost of development and maintenance under the constraint of satisfying a software reliability requirement. In a numerical example, the parameter estimation using maximum likelihood estimation of failure time data make out, and software optimal release time was estimated.

• Journal of Korean Society for Quality Management
• /
• v.23 no.3
• /
• pp.57-68
• /
• 1995

In this paper, we consider possibility that the multiple errors occur in each testing stage. At present, software reliability modeling is considered as a part of software reliability quality assurance in software engineering. However they dealt with the software growth model for the single error debugging at each testing stage until now. Hence it is necessary to study software reliability with multiple errors debugging. Therefore we propose software reliability growth modeling and estimate the parameters in the proposed software reliability growth model for the multiple errors debugging at each testing stage.

• Journal of Korea Society of Digital Industry and Information Management
• /
• v.6 no.2
• /
• pp.183-191
• /
• 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 mixture which has various intensity, if the system is complicated. 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.

• International Journal of Quality Innovation
• /
• v.7 no.1
• /
• pp.90-97
• /
• 2006

The process of producing software differs in many aspects from that of traditional manufacturing. Software is not manufactured in the classical sense. Development of software more closely resembles the development effort that goes into design new product [1-3]. In this article, we first describe the foundations of process improvement, which all processes can share. The process improvement differences between software and manufacturing process are then discussed, and a defect driven process inspection and improvement is introduced. Based on the discussion, two experiments were designed and the results of the results were collected. Through the comparison, we found that some efficient quality improvement approaches can be easily adapted in the software improvement and that the inspection efficiency is also significant.

• The KIPS Transactions:PartD
• /
• v.18D no.6
• /
• pp.451-460
• /
• 2011

The ability to trace change history and dependency relations of software artifacts which are continuously changed has been recognized as an important factor that support quality management activities such as verification, validation, and testing in software system development process. General software configuration management systems provide tracing information for artifacts only within the configuration management system, and it does not go further to changes that occur within personal workspace. This paper provides a solution that helps tracing down not only changes of configuration items but also change history of artifacts existent in personal workspace through the integration of configuration management system and personal workspace. Furthermore, in cases of artifacts which are included in a configuration item, this paper provides a solution that support tracing dependency relations between the artifacts by identifying their version links. For the integration of configuration management system and personal workspace, a revision of configuration item is connected to the artifact's version of the workspace by the tagging mechanism, and traceability for change history and dependency relations of artifacts can be managed more effectively through integrated change process.

• Tunnel and Underground Space
• /
• v.25 no.3
• /
• pp.221-230
• /
• 2015

This study examined and analyzed several mine management software programs developed in domestic and oversea countries. In the oversea countries, many companies have developed and commercialized mine management softwares such as Dispatch, $Cat^{(R)}$ $MineStar^{TM}$ and FARA. These softwares provide many functionalities including real-time machine tracking, machine assignment optimization, productivity management, equipment health monitoring and remote control. For the domestic cases, this study reviewed two software programs (i.e., GEMISIMS, Truck-Shovel fleet optimization) developed by several researchers because there is no mine management software currently commercialized in Korea. In addition, this paper reports the two cases at the Jwaneng mine in Botswana and at the Robinson mine in United States where mine management software programs are used to support mine operations.

• Journal of KIISE
• /
• v.45 no.3
• /
• pp.242-250
• /
• 2018

For high-quality software development, it is necessary to detect and fix the defects inserted. If defect management activities are not properly performed, it will lead to the project delay and project failure due to rework. Therefore, organizations need to establish defect management process and institutionalize it. Process standard models handle defect management in the area of project monitoring and control. However, small organizations experience difficulties in implementing and applying defect management process in a real situation. In this paper, we propose a defect management process for small organization which is designed in accordance with the characteristics of a small projects such as few participants and short development period. The proposed defect management process will be based on a tool chain with open source software such as Redmine, Subversion, Maven, Jenkins that support a defect management process and SW Visualization in systematic way. We also proposed a way of constructing defect database and various methods of analyzing and controlling defect data based on it. In an effort to prove the effectiveness of the proposed process, we applied the process and tool chain to a small organization.

• The KIPS Transactions:PartD
• /
• v.16D no.6
• /
• pp.899-910
• /
• 2009

Software productivity and quality improvement through software configuration management is based on organized and consistent change management. In change management, artifact identified as configuration item should be able to provide its changed history to the members in group and the members should be able to track down the changes made for the corresponding artifact. General software configuration management systems provide tracking information for artifacts only within the configuration management system, and it does not go further to changes that occur within personal working space. This paper provides a solution that helps tracking down changes that occur not only in configuration management, but also personal artifact's changes through the integration of configuration management system and personal working space. A revised version in configuration management system is connected to the artifact version of the working space by the tagging technique, and traceability can be managed more effectively by sharing the tracking information.

• Transactions of the Korean Society of Automotive Engineers
• /
• v.20 no.6
• /
• pp.117-125
• /
• 2012

This paper describes a model-based software development methodology for AUTOSAR-ready light software architecture(AUTOSAR-Lite). The proposed methodology briefly represents an application software modeling technique using Matlab/Simulink. Using the proposed technique, application software architecture elements (e.g. software components, runnables, and interfaces) and functional behaviors can be designed in a single modeling environment. From the designed model, the codes of application software is automatically generated using Real-Time Workshop Embedded Coder. The generated application software is easily integrated with hand-coded basic software using the proposed method. In order to evaluate the proposed methodology, a diesel engine management system for a passenger car was employed as a case study. Based on the methodology, 8 atomic software components and 52 runnables are successfully developed, and they are evaluated by engine experiments. From this case study, AUTOSAR compatible model-based application software was successfully developed, and the effectiveness of the proposed methodology was evaluated.

• Journal of Information Technology Applications and Management
• /
• v.24 no.2
• /
• pp.71-80
• /
• 2017

Software reliability is one of the most elementary and important problems in software development In order to find the software failure occurrence, the instantaneous failure rate function in the Poisson process can have a constant, incremental or decreasing tendency independently of the failure time. In this study, we compared the reliability performance of the software reliability model using the parameters of Pareto life distribution with the intensity decreasing pattern and the shape parameter of Erlang life distribution with the intensity increasing and decreasing pattern in the software product testing. In order to identify the software failure environment, the parametric estimation was applied to the maximum likelihood estimation method. Therefore, in this paper, we compare and evaluate software reliability by applying software failure time data. The reliability of the Erlang and Pareto life models is shown to be higher than that of the Pareto lifetime distribution model when the shape parameter is higher and the Erlang model is more reliable when the shape parameter is higher. Through this study, the software design department will be able to help the software design by applying various life distribution and shape parameters, and providing basic knowledge using software failure analysis.