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

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

• Journal of the Korea Safety Management & Science
• /
• v.13 no.4
• /
• pp.71-79
• /
• 2011

The work environment of locomotive cabs has long been an important issue in the design of railload systems since it is quite critical in terms of system's operational safety. It is getting more attention as the running speed of the trains goes up these days. To this end, this paper describes how to systematically construct a DB for the requirements set in the course of the improvement process for the aforementioned cab work environment. As a solution approach, we have adopted the requirement architecture concept to cover the whole activities required to do such as in requirements generation, DB construction, change management, and traceability management. Specifically, based on the requirement architecture framework a requirement process to collect requirements for improvement is discussed, and the guide lines are suggested for verification and validation of the developed requirements. In addition, a base schema and requirements templates are developed, which will be used in generating requirements and constructing a DB. Finally, it is demonstrated how the requirements DB for locomotive cabs can be constructed using a computer-aided tool in an integrated fashion.

• Journal of the Korean Society of Systems Engineering
• /
• v.19 no.1
• /
• pp.56-63
• /
• 2023

For the success of system development, it is necessary to systematically manage the requirements that are the basis of system development and its verification results. In order to follow the principles of SE(Systems Engineering)-based V&V(Verification&Validation) process, requirements can be managed by securing the requirements and their establishments, design compliances, and verification compliances according to the system development lifecycle. Especially, in a large-complex system research and development project, such as a space launch vehicle development project, many participants establish, verify, and validate numerous requirements together during the project. Therefore, logical and systematic requirements management, including guarantee of data integrity, change history, and traceability, is very important for multiple participants to utilize numerous requirements together without errors. This paper introduces the practical requirements and verification management for the requirements-based development process in the space launch vehicle development project.

• Proceedings of the Korean Institute of Building Construction Conference
• /
• 2016.05a
• /
• pp.231-232
• /
• 2016

Configuration Management (CM) is a process of identifying and documenting the characteristics of a Structures, Systems and Components (SSCs), and of ensuring that changes to these characteristics are properly assessed, approved, issued, implemented and verified. There are requirement management, change control, facility configuration information management for CM activities. In order to improve safety of Nuclear Power Plant(NPP), it is necessary to manage change item systematically. Existing CM concept is focused on the NPP in operation. On the other hand, NPP under construction is difficult to efficiently manage the change because of different change process from varoius stake-holders. This research considers method of consolidation change process for NPP to ensure that approved changes are accurately reflected in the design requirements, facility configuration information, and the physical configuration.

• The Journal of the Convergence on Culture Technology
• /
• v.7 no.4
• /
• pp.879-892
• /
• 2021

In a make-to-order manufacturing environment, the manufacturer's quotation information is important information used as basic information for bidding, receiving orders, and producing products in response to various customer demands. This quotation information is changed according to various factors such as customer demands, changes in product production environment, changes in drawing information of technical partners, and technological improvement of products. Due to this change, various changes occur in the quotation information that the manufacturer is preparing to reflect the customer's requirements. The change of quotation information according to these various change factors puts a lot of burden on the quotation management work from the standpoint of a make-to-order manufacturing company. In particular, the change of quotation information due to the change factors of quotation is inevitable and frequently occurs due to the requirements of the customer in the customer-oriented make-to-order production environment. In this paper, we propose a quotation change process based on the quotation creation process and propose a consistent and efficient quotation change processing method. To this end, the factors causing the change of quotation were defined, and the types of changes for each factor were defined. And it shows the procedure of applying the quotation change process to the quotation management system through the cases of each cause of the quotation change. In addition, in order to show the usefulness of the quotation change factors, the type of quotation change, the quotation change process, and the quotation system management, the proposed quotation change process and function was applied in the integrated quotation management system for the ship engine division of a typical make-to-order manufacturing company 'H'. As a result, it was confirmed that the proposed quotation change process and management system according to the quotation change factors were efficiently performed.

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

• International conference on construction engineering and project management
• /
• 2013.01a
• /
• pp.566-569
• /
• 2013

The purpose of this research is to develop the technology to meet the requirements of the design content, and to build a 'Requirement Information Management Model' for the design project. The model that should be used in the early design stage will undergo the following process: First, basic requirements would be defined by extracting the design content in the form of a reusable library of space units. At the next stage, requirement information should be modified after considering unique characteristics for the project and conflict problems between function and performance.

• Proceedings of the Korean Institute of Building Construction Conference
• /
• 2018.11a
• /
• pp.134-135
• /
• 2018

Nuclear Power Plant consists of about 1.4 million facilities. and the design standards and design requirements for the continuos utilization and safety of facilities are complexly connected with the facilities. When a design change for facilities or design requirements is occurred at the time of construction or operation, there are a lot of facilities, design requirements, and design bases that are affected by the facilities or design bases being changed. The above design changes are so complex that the existing document-bases design change process is time-consuming and may also cause human error. In this study, we developed a design requirement taxonomy that can be applied to the data-centric design bases document that can improve it. To do this, we analyze the design elements from the highest level to the lowest level applied to the nuclear power plant, and classify the design elements according to the characteristics of the design elements.