• Industrial Engineering and Management Systems
• /
• 제11권1호
• /
• pp.39-47
• /
• 2012

Requirements definition, which determines a project baseline, has a strong impact on the success of a project. However, since in-depth requirements are gradually revealed through the requirements definition process, the requirements definition is not a straight forward process and often falls into disorder. Thus project management standpoints are critical for the success of the requirements definition. In this paper, we present a framework and mechanisms of communication-centered project management, which controls the requirements definition process based on the situation of communication-oriented activities among stakeholders. In addition, we present a communication-centered project plan with a planning method. The project plan, which represents a time schedule of requirements definition activities, is made by a simulation-optimization algorithm using a stakeholder matrix showing the relations of requirements domains and relevant stakeholders. The effectiveness and the significance of communication-centered project management at the requirements definition phase are demonstrated by numerical examples.

• 정보처리학회논문지D
• /
• 제9D권1호
• /
• pp.81-90
• /
• 2002

More than 50% of defects and errors in the software development projects are related to the requirements[14]. But the development methodologies can not provide enough supports to the requirements management and changes. In the real world, the requirements keep changing as the requirements at the early development phase are usually incomplete, the developer′s understanding of the problem will be constantly changed during the software process, and new requirements may emerge with the organizational and environmental changes. In this paper, a requirements management process that can be integrated into the development methodologies is proposed to extend the requirements management over the whole development life-cycle and to support the requirements changes at the design/implementation/test phases. To evaluate the proposed process, it was compared to the existing requirements managements processes and models, and examined through a integration test with a widely used development methodology "MaRMI" to show the expected improvements at each development phase.

• 시스템엔지니어링학술지
• /
• 제6권2호
• /
• pp.7-14
• /
• 2010

Systematic and efficient Management of Development requirements will lead to success of project such as aircraft system development consisting of complex subsystem. For such reason, Requirements management tools have been used in most of project. In the case of FA-50 development project, requirements management tools have been used for systematic and efficient management of FA-50 Requirements. Especially FA-50 system was designed on the basis of the TA-50 configuration. Therefore, it needs traceability of requirements about functions, which have been already developed and will be newly developed. This paper was described about the implementation method of FA-50 development requirements traceability management.

• 한국건설관리학회논문집
• /
• 제21권6호
• /
• pp.3-15
• /
• 2020

성공적 건설 프로젝트의 수행을 위해 발주자의 요구사항을 명확히 정의하고, 전 생애주기를 포괄하여 각 사업 참여자의 전문기술을 통해 이를 프로젝트에 반영해야 한다. 이에 프로젝트 요건을 정보관리 차원에서 체계화 관리하기 위한 요건관리(Requirements Management)의 개념 정립이 요구된다. 본 연구에서는 건축분야 요건관리의 개념을 포괄적으로 정의하고, 요건정보 유형과 정보 분석기준을 제시하여 설계 요건정보를 효율적으로 관리하기 위한 방법론적 기반을 마련하고자 하였다. 또한 이를 사례연구에 적용하여 요건정보를 도출 및 분석하였으며, 발주자 설계관리 및 지식관리 관점에서 요건관리 시스템화 방향을 제안하였다.

• Industrial Engineering and Management Systems
• /
• 제11권1호
• /
• pp.70-81
• /
• 2012

The subject of "Design Requirements" (DR) is central to the design of software and engineering systems. The main reason for this is that quality aspects are usually closely tied to requirements, among other things. In this review paper, we consider how the subject of requirements is being managed in these two seemingly different design disciplines. Two important aspects are covered, namely: (a) requirements development, describing various activities leading to requirements documentation, and (b) requirements change management, describing various activities needed for the proper treatment of the inevitable changes in requirements. Similarities and differences on how these two aspects are handled in software and engineering systems are highlighted. It is concluded from this literature survey that the management of software requirements is quite coherent and well established as a science. On the other hand, management of engineering systems requirements suffer from being unstructured, in particular when requirements changes are involved. Important gaps and future important research areas are identified.

• 한국정보과학회논문지:소프트웨어및응용
• /
• 제32권12호
• /
• pp.1164-1177
• /
• 2005

현재 소프트웨어 개발 공정이 복잡해짐에 따라 개발하는 소프트웨어의 요구사항 역시 복잡해지고 있으며 요구사항 관리에 많은 노력이 소요되고 있다. 그러나 소프트웨어의 요구사항을 처음부터 모두 정의하는 것은 사실상 불가능하며, 개발이 진행되면서 환경은 변하기 마련이다. 또한 요구사항 변경은 개발보다 많은 비용이 소요되므로 체계적인 변경 관리를 통해 변경에 민첩하게 대응하고 관리되어야 한다. 본 논문에서는 소프트웨어 프로덕트 라인에서 요구사항 변경 관리 프로세스를 기반으로 체계적인 요구사항 변경 관리 방법을 제시한다. 소프트웨어 프로덕트 라인(software product lines)에서 어플리케이션의 요구사항은 도메인 요구사항과 밀접하게 관련되어 있으므로 어플리케이션 공학(application engineering) 단계에서 요구사항 변경이 발생했을 경우 도메인 공학(domain engineering) 단계를 이용하여 변경을 분석하고 관리하는 방법을 제시한다. 이러한 일관된 변경 관리를 통해 변경 범위를 분석하고, 변경 대처방안을 제시함으로써 변경 처리 결정을 내리는데 도움을 주며 한번 요청된 변경이 완벽하게 처리되도록 도와주어 같은 변경의 반복 요청을 막을 수 있기 때문에 잠재된 변경 비용을 절약할 수 있다.

• 대한안전경영과학회지
• /
• 제13권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.

• 시스템엔지니어링학술지
• /
• 제19권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.

• 한국정보과학회논문지:소프트웨어및응용
• /
• 제30권5_6호
• /
• pp.503-514
• /
• 2003

폭포수 모형을 기반으로 하는 구조적 개발 방법론에서는 요구 분석 단계에서 요구 사항들이 일단 명세화되고 나면, 이들은 단지 후속의 개발 단계를 위한 중간 산출물로만 사용되고 더 이상 요구 사항 자체를 관리 대상으로 취급하지 않기 때문에 설계 단계 이후에 발생하는 요구 사항의 변경을 관리할 수 있는 절차가 미흡하다. 그러나 현실적으로는 정보 기술의 발전, 시장 환경이나 적용 환경의 변화 등으로 인하여 개발 기간 중 요구 사항은 끊임없이 변화하게 된다. 따라서 이러한 요구 사항의 지속적인 변경을 지원하기 위해서는 전체 개발 생명 주기에 걸쳐 요구 사항을 관리하고 특히 설계 단계 이후의 요구 사항 변경을 지원할 수 있는 요구 사항 변경 관리 프로세스가 필요하다. 이 논문에서는 하향식(top-down)의 구조적 개발 방법론에 적용할 수 있는 요구 사항 변경 관리 프로세스 모델을 제안하여 설계 단계 이후에 발생하는 요구 사항의 변경을 체계적으로 관리하고 요구 사항 자체를 모든 개발 생명 주기에서 활용하기 위한 방안을 제시한다. 제안 프로세스는 마르미 방법론의 개발 프로세스와 산출물 측면의 적용 검토를 통하여 개발 방법론의 요구 사항 변경 및 관리에 대한 개선 효과를 평가한다.

• 시스템엔지니어링학술지
• /
• 제14권1호
• /
• pp.63-71
• /
• 2018

This paper discusses decommissioning procedure requirements management using requirement engineering to systematically manage the technical requirements and criteria that are required in decontamination and decommissioning activities, and the regulatory requirements that should be complied with in a decommissioning strategy for research reactors and nuclear power plants. A schema was designed to establish the traceability and change management related to the linkage between the regulatory requirements and technical criteria after classifying the procedures into four groups during the full life-cycle of the decommissioning. The results confirmed that the designed schema was successfully traced in accordance with the regulatory requirements and technical criteria required by various fields in terms of decontamination and decommissioning activities. In addition, the changes before and after the revision of the Nuclear Safety Act were also determined. The dismantling procedure requirement management system secured through this study is expected to be a useful tool in the integrated management of radioactive waste, as well as in the dismantling of research reactor and nuclear facilities.