• Journal of the Korea Society of Computer and Information
• /
• v.19 no.2
• /
• pp.209-219
• /
• 2014

With rapid convergence of information technology and expending role of software, many organizations have taken interested in We explore the relationship between the level of change awareness and deployment of software process improvement (SPI) approaches using a competing values framework. To measure awareness level of organization's change, DICE framework which provides means for predicting the outcome of change management initiatives is used. The four factors for organizaton's change: duration, integrity, commitment, and effort are evaluated and a score is calculated. In this paper, we apply the DICE(R) score as an independent variable to predict the outcome of a software process improvement. Our results indicated that the Organization have a higher chance of success have the better outcome in software process improvement.

• 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.

• Journal of Korean Society for Quality Management
• /
• v.34 no.4
• /
• pp.133-138
• /
• 2006

In this paper, we propose a software reliability growth model (SRGM) based on the testing domain, which is isolated by the executed test cases. This model assumes an imperfect debugging environment in which new faults are introduced in the fault-correction process. We consider that the fault detection rate of NHPP model is changed in the proposed SRGM. We obtain the maximum likelihood estimate, and compare goodness-of-fit with another existing software reliability growth model.

• Journal of Korea Society of Industrial Information Systems
• /
• v.13 no.3
• /
• pp.63-86
• /
• 2008

Recently implementing enterprise resource planning (ERP) systems with packaged business software is growing rapidly. The purpose of this article is to provide further insights into the business process change and change management in implementation process of ERP systems. This paper examine an survey of some 146 firms' adoption and implementation of packaged ERP software. In this paper, we propose an integrated approach of business process change and change management of the implementation process. This research highlights the importance of change management for implementing ERP. In addition, we empirically reveals that the eventual success of ERP systems depends on effective business process change and change management during the ERP implementation.

• Journal of the Korea Society of Computer and Information
• /
• v.23 no.12
• /
• pp.115-122
• /
• 2018

As the proportion of software in weapon systems increases, the impact of software on the overall system is growing. As a result, software quality management becomes important, and related regulations and work manuals for quality assurance activities at each stage in the R & D process are becoming more sophisticated. However, due to the characteristics of the weapon system software that is developed as a customized form for the purpose of a specific mission, there are limits to specifying and definitizing the detailed requirements (upper and lower level) according to various operational concepts during the development process. Due to this, software modification (patch change, shape change due to upgrade, etc.) occurs on account of many defects and performance improvement in the mass production and operation stage after the development is completed. In this study, we analyze the characteristics of these weapon system softwares and propose quality improvement methods based on ISO / IEC / IEEE 29119 test method.

• International journal of advanced smart convergence
• /
• v.10 no.2
• /
• pp.130-137
• /
• 2021

In the current software project, it is still very difficult to extract and define clear requirements in the requirement engineering. Informal requirements documents based on natural language can be interpreted in different meanings depending on the degree of understanding or maturity level of the requirements analyst. Also, Furthermore, as the project progresses, requirements continue to change from the customer. This change in requirements is a catastrophic failure from a management perspective in software projects. In the situation of frequent requirements changes, a current issue of requirements engineering area is how to make clear requirements with unclear and ambigousrequirements. To solve this problem, we propose to extract and redefine clear requirements by incorporating Design Thinking methodologies into requirements engineering. We expect to have higher possibilities to improve software quality by redefining requirements that are ambiously and unclearly defined.

• The Journal of Society for e-Business Studies
• /
• v.12 no.3
• /
• pp.33-47
• /
• 2007

The requirements have been changed during development progresses, since it is impossible to define all of software requirements. These requirements change leads to mistakes because the developers cannot completely understand the software's structure and behavior, or they cannot discover all parts affected by a change. Requirement changes have to be managed and assessed to ensure that they are feasible, make economic sense and contribute to the business needs of the customer organization. We propose a feature-oriented requirements change management method to manage requirements change with value analysis and feature-oriented traceability links including intermediate catalysis using features. Our approach offers two contributions to the study of requirements change: (1) We define requirements change tree to make user requirements change request generalize by feature level. (2) We provide overall process such as change request normalization, change impact analysis, solution dealing with change request, change request implementation, change request evaluation. In addition, we especially present the results of a case study which is carried out in asset management portal system in details.

• Journal of Information Technology Applications and Management
• /
• v.22 no.3
• /
• pp.143-167
• /
• 2015

This paper addresses the issue how the total life cycle cost may be minimized and how the cost should be allocated to the acquirer and developer. This paper differentiates post life cycle change (PLCC) endeavors from PLCC activities, rigorously classifies PLCC endeavors according to the result of PLCC endeavors, and rigorously defines the life cycle cost of a software product. This paper reviews classical definitions of software 'maintenance' types and proposes a new typology of PLCC activities too. The proposed classification schemes are exhaustive and mutually exclusive, and provide a new paradigm to review existing literatures regarding software cost estimation, software 'maintenance,' software evolution, and software architecture from a new perspective. This paper argues that the long-term interest of the acquirer is not protected properly because warranty period is typically too short and because the main concern of warranty service is given to removing the defects detected easily. Based on the observation that defects are caused solely by errors the developer has committed for software while defects are often induced by using for hardware (so, this paper cautiously proposes not to use the term 'maintenance' at all for software), this paper argues that the cost to remove defects should not be borne by the acquirer for software.

• The KIPS Transactions:PartD
• /
• v.10D no.1
• /
• pp.67-76
• /
• 2003

The reuse of software is to use the components of software to be made beforehand to improve the productivity of it. The development of electronic commerce requires it which can be shown from changing the change of business models Reuse is the necessary solution to cope with a rapid change in the electronic commercial transaction. These reuse business models have the defects that they are not offered from version management. This paper has the purpose that by doing the supplementation of defects not to be offered from the version management and by introducing the quick change management about reuse business models, reusing the components and saving a development and reducing a development af period. The reuse of components by the new reuse business models has the advantages to minimize the danger elements from the design to the finish. We use the version management and try to present the method to make the efficiency of reuse by introducing components and managing the elements about components to the version in the technique to accomplish the reuse of software.

• Journal of the Korean Operations Research and Management Science Society
• /
• v.16 no.1
• /
• pp.113-119
• /
• 1991

The author is currently assistant professor of Management Science at Korea Advanced Institute of Science and Technology, following a few years as assistant professor of Industrial Engineering at Kyung Hee University, Korea. He received his doctorate from the department of Industrial Engineering and Operations Research, University of California, Berkeley. His research interests are time series and forecasting modelling, Bayesian forecasting and the related software development. He is now teaching time series analysis and econometrics at the graduate level.