• Journal of KIISE:Software and Applications
• /
• v.30 no.5_6
• /
• pp.503-514
• /
• 2003

In conventional development methodologies, requirements are considered to be not changing after analysis phase, and requirements specifications are used for the next step system design purpose. But in the real world, requirements can be changed and modified throughout the development life cycle according to end-user's more understanding about the target system, new IT technologies, changes of customer environment and market situation, and so on. So there needs a requirements change management process that can extend requirements management over the entire development life cycle and can support managing changes to the requirements after design phase. In this paper, a requirements change management process that can be integrated into conventional development methodologies is proposed to support the extension of requirements life cycle and managing changes to the requirements after design phase. This process was evaluated through an verification test with a widely used development methodology‘MaRMI’.

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

• 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.17D no.4
• /
• pp.271-282
• /
• 2010

Insufficient requirement management accounts for 54% ofunsuccessful software development projects and 22% of insufficient requirement management comes from requirement change management. Hence, requirement management activities are important to reduce failure rates and a tracing method is suggested as the major factor in requirements change management. A traceability table is easy to use because of its legibility accurate tracing. However, traceability tables of existing studies have failed to concretely suggest method of change management and effect of traceability. Also, studies of methods to estimate change impact is complex. Hence, this study suggests how to use a traceability table to manage changes in requirements. Together, in comparison to existing studies, this study suggests easier methods to estimate change rate and change impact. Also Fifteen projects were sampled to test the hypothesis that traceability table influences the success of projects and that it decreases the failure rate that comes from the insufficient requirements management.

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

• Proceedings of the Korean Information Science Society Conference
• /
• 1998.10b
• /
• pp.623-625
• /
• 1998

시스템의 변경은 개발 주기의 전 과정 가운데 지속적으로 발생하게 되고, 변경이 발생하면 연관된 다른 요소에 영향을 미칠 뿐 아니라 다음 주기에까지 그 영향이 전달되기 때문에, 개발 초기의 요구공학 주기의 산출물인 요구사항명세서로부터 추적과 관리가 시작되어야 한다. 본 논문에서는 요구사항의 관리를 위해 요구사항 관리 모델을 제안하고, 요구사항 관리 계층을 중심으로 요구사항의 저장, 변경사항의 관리 및 추적을 처리하며, 이를 기반으로 이후 프로젝트 관리와 관련된 작업들을 어플리케이션 계층에서 처리하도록 지원하였다. 또한 이 모델이 효율적으로 컴퓨터를 이용한 공동작업(Computer Supported Cooperative Work: CSW)에 활용 가능하도록 웹을 통해 구현한다.

• 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 Institute Of Construction Engineering and Management
• /
• autumn
• /
• pp.119-126
• /
• 2001

This paper analyzes problems related to total cost changes in private investment projects, and then proposes an improvement measure for the control of cost changes within the framework of the project management, contract, human resource, project communication, cost, and time management. From the viewpoint of contract management, the basis of cost change ought to be cleared up with standardization of related provisions in the concession agreement, and potentiality of change ought to be excluded with prescription of the private investor's leading role from the design phase. Regarding human resource management, this paper proposes a standard work flow granting much sovereign rights to private parts by putting restriction on work scopes of the entrusted authority of government, and transferring the rights of assignment, contract, and control about the responsible supervisor to the concessionaire. With regard to project communication management the notification of changes on drawings and technical documents ought to be automated and the realtime database ought to be established with DMIS (Drawings & Documents Management Information System). From the cost management point of view, this thesis integrates the control of cost-change-approved items and disapproved items to one cost breakdown system, and then harmonizes the actual progress with EVMS in time management.

• The KIPS Transactions:PartD
• /
• v.11D no.7 s.96
• /
• pp.1349-1356
• /
• 2004

The interest of version management is increasing in electronic commerce requiring data mining and documents processing system related to digital governmentapplications. In this paper, we define a change set that is to manage historicalinformation and to maintain XML documents during a long period of time and propose several storage policies of XML documents using a change set. A change set includes a change oper-ation set and temporal dimensions and a change operation set is composed with schema change operations and data change operations. We pro-pose three storage policies using a change set. Three storage policies are (1) storing all the change sets, (2) storing the change sets and the versions periodically. (3) storing the aggregation of change sets and the versions at a point of proper time. Also, we compare the performance between the existing storage policy and the proposed storage policies. Though the performance evaluation, we show that the method to store the aggregation of change sets and the versions at a point of proper time outperforms others.