• Journal of Platform Technology
• /
• 제11권5호
• /
• pp.3-15
• /
• 2023

Requirements traceability link information is the basis for determining whether requirement change requested throughout the software development life cycle should be reflected in the system. Setting up complete requirements traceability links requires considerable effort. However, the commensurate benefits can be obtained in later development or further maintenance phases. For this reason, setting up and managing requirements traceability links in the software development phase are tasks that cause considerable resistance to developers. This study proposes a method for generating requirement traceability links in business applications. The key feature of the proposed method is that the traceability link from the requirements element, which is the basis of the corresponding element to the analysis element, is automatically established at the same time the elements of the analysis model are identified. This can be a way to reduce developer effort while increasing the efficiency of the traceability model. A case study on a Course Registration System demonstrates the feasibility of applying the proposed requirements traceability management method to actual software development.

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

• 대한안전경영과학회지
• /
• 제9권6호
• /
• pp.89-96
• /
• 2007

It is well known that the test and evaluation plan (TEP) is very crucial in the successful development of safety-critical systems. As such, this paper discusses an approach to the development of the TEP for a system that should meet safety requirements in the systems development process. It is studied how to incorporate the result of preliminary hazard analysis (PHA) in generating the safety requirements. It is also discussed how to deal with them when the system requirements (i.e., functions, performance, constraints, components, etc) and the safety requirements are integrated into one model. While doing so, we have constructed the required traceability among them, which is necessary and very useful when the safety requirements need to be corrected or be changed. The use of the traceability makes it possible to easily check out whether and how the safety requirements are properly incorporated in the system design process. Furthermore, without the verified traceability, the system cannot be changed or upgraded later. In order to implement the model on a computer-aided tool, we have constructed a database (DB) schema. As a result, the implemented model/DB allows to automatically generate TEP which can be used to measure the performance and safety level of the developed system.

• 정보처리학회논문지D
• /
• 제17D권4호
• /
• pp.271-282
• /
• 2010

소프트웨어 프로젝트의 실패요인 중 54%가 요구사항관리 미흡에서 발생하며, 이중 22%는 요구사항 변경관리에서 기인한다. 따라서 실패요인을 줄이기 위해 요구사항 관리활동이 중요하며 이중 요구사항 변경을 위한 핵심활동으로 추적기법을 활용한다. 추적기법에 사용되는 방법인 추적테이블은 단순링크 방식으로 사용이 간편하고 가독성이 있으며 추적의 정확성이 높은 장점이 있다. 그러나 기존 추적테이블 연구는 변경관리 방법 및 추적의 효과를 구체적으로 제시하고 있지 않으며, 또한 변경영향 추정연구는 추정방법이 복잡하여 실용성에 한계가 있다. 이에 본 연구는 기존에 연구된 추적테이블을 이용하여 변경요구사항을 관리하는 방법을 제시하고 이로 인해 변경율 및 변경영향도를 기존 연구에 비해 용이하게 추정할 수 있는 기법을 제안한다. 또한 15개 프로젝트를 대상으로 추적테이블의 효과를 가설 검정하여 추적테이블이 프로젝트 성공에 영향을 미치며, 요구사항 관리미흡으로 인한 실패요인을 감소시킴을 확인한다.

• 시스템엔지니어링학술지
• /
• 제7권2호
• /
• pp.31-37
• /
• 2011

Korean Naval Ship acquisition processes are very complicate. There are 4 phases, Feasibility Study, Concept Design, Basic Design, Detail Design and Construction. A number of organizations and support groups exist to acquire naval war ships. Thus, It is very important how to establish traceability about requirements. This work has investigated how to improve traceability about requirements using Shipboard Work Breakdown Structure.

• 한국철도학회:학술대회논문집
• /
• 한국철도학회 2010년도 춘계학술대회 논문집
• /
• pp.1821-1828
• /
• 2010

In this study we suggest a method of optimization of verification hierarchy structure and system requirements management by using a verification matrix with traceability consideration. Verification items were gathered in the process of CDR(Critical Design Review), and analyzed with respect to requirements traceability structure. Missed or overlapped items were adjusted, and cross-correlated items between sub-systems were clustered and rearranged in order to structurize verification requrements (VRs). Those VRs are to be used as a guideline for the test and evaluation planning, development of test items and procedure, and system requirements management throughout the system integration stages.

• 디지털콘텐츠학회 논문지
• /
• 제13권2호
• /
• pp.247-254
• /
• 2012

정보체계 개발 시 사용자 요구사항의 관리는 핵심요소이다. 그동안 요구사항의 관리와 관련하여 추적 테이블을 이용한 추적 모델이나 SOA 등 특정 방법론을 기반으로 한 추적 기법은 연구된 바 있다. 그러나 IT비전문가인 사업담당자를 위한 객관적이며 정량화된 평가 방법과 판정 기준을 제시한 사례는 없었다. 이에, 본 연구자는 선행 사례 연구를 통해 공공분야의 정보시스템을 구축하는 과정에서 요구사항 반영의 적정성을 판단하는데 있어 비전문가도 접근하기 쉽고 객관적이며 정량화된 평가 방법과 판정 기준을 제시한 바 있다. 본 연구에서는 선행 연구의 한계점을 고찰하여 요구사항 반영에 대한 평가 산식을 개선하고 다양한 사업 사례 분석을 통해 사업 특성 별 판정기준을 도출, 제시하였다.

• 한국군사과학기술학회지
• /
• 제3권2호
• /
• pp.149-155
• /
• 2000

This paper presents results from a computer-aided systems engineering application to system development projects. RDD-100 version of ALC Inc. was used in this work. The framework adopted in the study takes a unified approach to the system design and the process management associated with it, thereby coherent and full traceability between them is maintained. Conventional system engineering process supported by the tool is adopted in the system design. On the other hand, the same tool is also used to the systems engineering management to get full traceability between system design data and engineering management data. It is greatly helpful in managing many sub-contractors in the sense that the traceability can help identify the sub-project responsibility as well as the objectives of the project in coordination with interface requirements. We conclude with the advantage and limits of our unified approach.

• 시스템엔지니어링학술지
• /
• 제2권2호
• /
• pp.33-38
• /
• 2006

It is well known that efficient management and thorough implementation of stakeholder requirements is vital for a successful development of a large-scale and complex system. Equally important is to make sure that all the requirements be correctly realized in the developed system. For the purpose, verification requirements are derived with traceability from the system requirements. This paper discusses a step by step process for constructing the requirements verification model which includes : 1) the schema modeling both requirements and their traceability; 2) the template documenting the verification requirements; 3) the verification model constructed from the schema; and 4) the test and evaluation plan that can be printed automatically.

• 대한안전경영과학회지
• /
• 제15권1호
• /
• pp.11-19
• /
• 2013

In modern systems design and development, one of the key issues is considered to be related with how to reflect faithfully the stakeholder requirements including customer requirements therein, thereby successfully implementing the system functions derived from the requirements. On the other hand, the issue of safety management is also becoming greatly important these days, particularly in the operational phase of the systems under development. An approach to safety management can be based on the use of the failure mode effect and analysis (FMEA), which has been a core method adopted in automotive industry to reduce the potential failure. The fact that a successful development of cars needs to consider both the complexity and failure throughout the whole life cycle calls for the necessity of applying the systems engineering (SE) process. To meet such a need, in this paper a method of FMEA is developed based on the SE concept. To do so, a process model is derived first in order to identify the required activities that must be satisfied in automotive design while reducing the possibility of failure. Specifically, the stakeholder requirements were analyzed first to derive a set of functions, which subsequentially leads to the task of identifying necessary HW/SW components. Then the derived functions were allocated to appropriate HW/SW components. During this design process, the traceability between the functions and HW/SW components were generated. The traceability can play a key role when FMEA is performed to predict the potential failure that can be described with the routes from the components through the linked functions. As a case study, the developed process model has been applied in a project carried out in practice. The results turned out to demonstrate the usefulness of the approach.