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

• Electronics and Telecommunications Trends
• /
• v.15 no.6 s.66
• /
• pp.74-83
• /
• 2000

소프트웨어는 개발과정에서 빈번한 변경이 발생한다. 특히, 대형 시스템 개발에 있어서 소프트웨어의 변경요구는 다양하고 복잡하게 된다. 이러한 변경요구에 따른 소프트웨어의 품질관리 또한 중요한 이슈가 되며 변경요구는 개발조직과 연계하여 자연스럽게 제어되어야 한다. 효과적으로 형상관리를 완벽하게 처리하면서 최종 시스템 소프트웨어로 수용함으로써 적시에 배포할 수 있는 기법은 프로젝트 관리 측면에서도 매우 중요하다. 본 고에서는 개발중인 시스템의 소프트웨어의 변경요구를 개발조직의 관리 특성에 맞추어 시스템의 형상관리에 완벽을 가하고 요구사항에 대한 수용기간을 단축시키며 체계적으로 관리, 제어하는 기법과 이에 따른 품질관리 방안 등을 소개하고 이를 지원하는 S/W 종합 도구 및 운용사례 등을 밝힌다.

• The KIPS Transactions:PartA
• /
• v.16A no.2
• /
• pp.125-134
• /
• 2009

This paper proposes a change management system of sensor network applications based on version synchronization that supports to effectively manage defect correction of applications, change of functions for applications or improvement of applications without suspending the sensor network. The proposed change management system consists of the NADE which is an application development environment, the Node Management Server, and the Node Agent. NADE is an Eclipse-based development environment for developing applications which are installed into nodes. NADE is also connected with CVSNT which is a version management tool and performs application version management using the CVSNT. Node Management Server manages nodes to maintain latest versions of applications by synchronizing versions of applications which are performed on the nodes with the versions of applications which are developed in the NADE. Node Agent which is loaded into the node periodically sends the version information of the application to the server, and stores and updates the version information of the application. Through the proposed change management system, applications of nodes are automatically updated when versions of applications are changed by correcting defects, changing functions or improving applications. Therefore, the user can effectively manage the execution of sensor network system without suspending or delaying the sensor network. Also, visibility of change management for sensor network applications will be improved.

• Proceedings of the Korean Information Science Society Conference
• /
• 2003.04c
• /
• pp.82-84
• /
• 2003

소프트웨어는 개발단계에서부터 유지/보수단계에 이르기까지 끊임없이 변경되며 하드웨어와 달리“변하기 쉬운 특성”과“눈에 보이지 않는 특성”을 가지고 있어 소프트웨어의 형상관리를 어렵게 한다. 소프트웨어 형상 관리를 용이하게 하고 이를 통해 개발 생산성을 높이기 위해 많은 소프트웨어 하우스에서는 형상 관리 도구를 도입하여 소프트웨어 개발에 이용하고 있다. 그러나 도입된 형상 관리 도구의 활용 형태를 보면 대부분 버전 관리 부분인데 이는 개발자들이 변경 정보를 충실히 작성하지 않으면 형상 아이템의 버전만 관리될 뿐 실질적인 변경 정보는 각 버전의 비교를 통해서만 알 수 있다. 따라서 본 논문은 형상 관리 아이템 중 코딩 표준에 따라 작성되는 소스 코드를 대상으로 새로운 버전이 생성될 때마다, 변경 정보를 소스 코드로부터 추출하여 자동으로 형상 관리 도구의 버전 관리 정보로 등록하여 관리함으로써 소스 코드와 형상 관리 도구의 버전 정보를 통합하여 관리하는 방안을 제시하고자한다.

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

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

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

• Proceedings of the Korean Information Science Society Conference
• /
• 2010.06b
• /
• pp.64-68
• /
• 2010

소프트웨어 산출물들은 지속적으로 변경되며, 변경 이력을 관리하기 위해 버전관리 기법이 사용된다. 산출물의 버전 정보는 과거의 변경에 대한 추적성을 제공함으로써 효율적인 변경 관리를 돕는다. 여러 산출물들이 함께 변경된 경우 각 산출물들의 버전정보를 링크시킴으로써 변경에 대한 추적성을 향상시킬 수 있다. 버전 링크의 식별은 미리 정해진 산출물들의 집합을 대상으로 하며, 동일한 변경 요청에 대해서 이루어진다. 본 논문은 산출물들의 집합을 한 형상항목 내에 포함된 것으로 정하고, 형상항목에 대한 변경 요청으로부터 산출물들간의 버전 링크를 식별하기 위한 기법을 제시한다. 형상항목과 산출물의 관계로부터 버전 링크를 식별하기 위해 형상관리 환경과 산출물의 버전관리 환경을 통합하였다.