• Journal of KIISE:Software and Applications
• /
• v.32 no.12
• /
• pp.1164-1177
• /
• 2005

As the software development process becomes complicated, software requirements become complicated, too. Many efforts are needed in requirements management. It is impossible to define all requirements of software at first, and the development environment changes as project is gone. As the cost of requirements change management is much more than development cost, the changes should be controled immediately through systematic change management. In this paper, I suggest a method to manage requirements change systematically based on the change management process in software product lines. The requirements change at the application engineering process is analyzed and managed using the domain engineering process because the application requirements are customized from the domain requirements in software product lines. Such the consistent change management helps to make decisions about changes by change impact analysis and alternative solution design. Through this method, the potential change costs can be saved because same change requests are not repeated by controlling the change requests completely.

• Korean Management Science Review
• /
• v.15 no.2
• /
• pp.59-70
• /
• 1998

According to the Gartner Group, the market for ERP software in Korea is growing rapidly. However, the number of successful ERP implementations is quite few. Standard(unmodified) ERP's are built based on best practices. Improvements expected from successful implementation are based on best practices built into the software. Many improvements are lost through modification to "standard" software. Even minor changes in software can significantly reduce benefits. Both implementation time and risk factors are increased with modifications. We introduce a methodology, called package Enable Re-engineering (PER) and the main components of change management program by Ernst & Young. "To-Be" model could be developed through the software capabilities. And change management processes such as continuous education and self-developments are required. The philosophy of the change management processes is to let the software package drive the re-engineering practices and avoid moving the software toward the "As-IS" process. Extensive top management involvement, major focus on speed, extensive communication program, and "clear" picture of the future are essential components of change management. We are sure that the complied experiences and model have implications for practice and for academicians for their endeavors in their fields.

• Proceedings of the Korean Information Science Society Conference
• /
• 2001.10a
• /
• pp.541-543
• /
• 2001

Embedded System이 고도화, 지능화되어감에 따라 이를 구동하는 Embedded Software의 역할과 크기 그리고 복잡도 역시 증가하고 있어 주어진 개발 기간동안 안정되고 품질이 보장된 Embedded Software 개발을 위해서는 기존의 방법보다 간편하고 유연하며 개발 프로세스를 지원하는 새로운 변경 관리 기법과 병렬 환경구성이 방법이 필요하게 되었다. 이에 따라, 기존의 방법을 추상화하여 사용과 관리가 용이하며 프로세스 지원이 가능한 Unified Change Management(UCM)을 Embedded Software인 Handset Platform 개발에 적용하여 병렬 개발 환경 구축과 Change Control and Problem Tracking 측면에서 기존의 방법과 비교하여 그 효용성을 살펴보고자 한다.

• Journal of Internet Computing and Services
• /
• v.22 no.3
• /
• pp.59-66
• /
• 2021

This study proposes a requirements monitoring method that systematically performs traceability management and change management for requirements in order to improve the quality of software systems in the software development process. To this end, we present the artifact change history management models to systematically perform change management for individual artifacts and the traceability matrixes to define the relationship between artifacts. It also proposes a visual dashboard that makes it easy to grasp the situation in which changes are propagated to related artifacts when specific artifacts change.

• The Journal of the Korea Contents Association
• /
• v.12 no.1
• /
• pp.59-67
• /
• 2012

Software change management is focused on the change of a entity like the change of contents of a system or a document. In change management, interactive relationship among requirements and complex decision making is needed to obtain optimized status. In this paper we design a management model of software change management in distributed environment which mange the change among components by time and situation. In addition, each components are defined and use ANP technique for best decision-making by using the subordinate relationship and feedback considering the mutual dependency referring the change of components in distributed environment. Thus, we analyze the dependency among each components and show 3 types of change relationship. Also through analysis of dependency, we verified the effectiveness of such approach.

• The Journal of Korean Association of Computer Education
• /
• v.5 no.4
• /
• pp.61-69
• /
• 2002

Software documents consist of a number of logical objects and relationships between them, and a lot of versions are generated during software development. When an object is changed, it is desirable to easily identify the change and the range of change propagation for efficient software development and maintenance. However, it is difficult to identify it in a coarse-grained object management model. To solve this problem, fine-grained object management is required. In this paper, I propose a consistency management model for fine-grained software objects based on operation history applied to edit software objects. This paper presents a formal model for consistency management at the fine-grained level. Consistency between documents is managed using dependency between objects and kinds of the operations applied to the objects so that unnecessary change propagation can be avoided.

• Asia pacific journal of information systems
• /
• v.30 no.3
• /
• pp.457-496
• /
• 2020

This study aims to extensively analyze the performance of various Machine Learning (ML) techniques for predicting version to version change-proneness of source code Java files. 17 object-oriented metrics have been utilized in this work for predicting change-prone files using 31 ML techniques and the framework proposed has been implemented on various consecutive releases of two Java-based software projects available as plug-ins. 10-fold and inter-release validation methods have been employed to validate the models and statistical tests provide supplementary information regarding the reliability and significance of the results. The results of experiments conducted in this article indicate that the ML techniques perform differently under the different validation settings. The results also confirm the proficiency of the selected ML techniques in lieu of developing change-proneness prediction models which could aid the software engineers in the initial stages of software development for classifying change-prone Java files of a software, in turn aiding in the trend estimation of change-proneness over future versions.

• Journal of Information Processing Systems
• /
• v.17 no.5
• /
• pp.972-988
• /
• 2021

At present, DevOps environments are getting popular in software organizations due to better collaboration and software productivity over traditional software process models. Software artefacts in DevOps environments are vulnerable to frequent changes at any phase of the software development life cycle that create a continuous integration continuous delivery pipeline. Therefore, software artefact traceability management is challenging in DevOps environments due to the continual artefact changes; often it makes the artefacts to be inconsistent. The existing software traceability related research shows limitations such as being limited to few types of artefacts, lack of automation and inability to cope with continuous integrations. This paper attempts to overcome those challenges by providing traceability support for heterogeneous artefacts in DevOps environments using a prototype named SAT-Analyser. The novel contribution of this work is the proposed traceability process model consists of artefact change detection, change impact analysis, and change propagation. Moreover, this tool provides multi-user accessibility and is integrated with a prominent DevOps tool stack to enable collaborations. The case study analysis has shown high accuracy in SAT-Analyser generated results and have obtained positive feedback from industry DevOps practitioners for its efficacy.

• Journal of the Korea Society of Computer and Information
• /
• v.16 no.12
• /
• pp.273-283
• /
• 2011

The purpose of this study is to examine the factors influencing performance of change control, management review and flexibility in the software company with innovativeness. This model tests various theoretical research hypotheses relating to performance of software company, change control, management review, flexibility and innovativeness. Valid 100 questionnaires have been collected within two months of 2010. EXCEL, Smart PLS(Partial Least Square) 2.0 and SPSS 15.0 have been utilized for deriving the study results. The results of hypothesis testing are as follows. First, change control and management review positively influences flexibility. Second, flexibility positively influence performance of software company. Finally, change control to flexibility for low group of innovativeness is significantly larger than those for high group of innovativeness. But management review to flexibility for high group of innovativeness is significantly larger than those for low group of innovativeness. The results of this study will provide various implications on performance of software company.

• KIPS Transactions on Software and Data Engineering
• /
• v.2 no.7
• /
• pp.461-470
• /
• 2013

The capacity for tracing relationships among various artifacts which are created at each phase of software system development is essential for software quality management. Software release refers to delivering a set of newly created or changed artifacts to customers. The relationships among artifacts which comprise software release must be traced so that the work for customer's requirement of change and functional enhancement is effectively established. And release management can be effectively realized through the integration of configuration management and change management. This paper proposes the technique for supporting change management of artifacts and for tracing relationships of artifacts which comprise software release through the integrated environment of personal workspace and configuration management system. In the proposed environment, the visualized version graph and automated tagging function are used for tracing relationships of artifacts.