• KIPS Transactions on Software and Data Engineering
• /
• v.7 no.9
• /
• pp.325-334
• /
• 2018

Requirement traceability should be continuously maintained in software development and evolution. However, it is usually updated in practice in the quality assurance phase. The gap between "is" and "should" exists due to the fact that developers must invest considerable effort to update requirement traceability while being able to obtain only marginal benefit from the updated traceability. To close this gap, we propose a spreadsheet application that enables developers to flexibly change mappings in a requirement traceability matrix. In this way, developers can reduce their effort in updating the requirement traceability matrix, but still obtain the common form of a requirement traceability matrix on a spreadsheet. The proposed application maintains the mappings between two artifacts on each sheet so that, whenever an artifact item changes, developers can instantly insert the relevant mapping changes. Then, when developers desire the common form of a requirement traceability matrix, the proposed application calculates the mappings among several artifacts and creates the matrix. The application also checks traceability errors and calculates the metrics so that developers can understand the completeness of the matrix. To understand the applicability of the proposed approach, we conducted a case study, which shows that the proposed application can be applied to the real project and easily incorporate the mapping changes.

• Journal of the Korea Society of Computer and Information
• /
• v.17 no.5
• /
• pp.115-126
• /
• 2012

It is very important to trace whether all the requirements has been reflected in the developed system. However, most existing researches apply Requirement Traceability Matrix(RTM) to the whole SDLC according to the development methodology. RTM has no practical value because it has not only too many pursuit items but also its tracking method is very complicated and the practical management in developing the information system is not accomplished nearly. Therefore, in this study, we proposed an enhanced RTM which was composed of only necessary items and allow us to manage the applied area effectively from Request for Proposal(RFP) or the proposal stage to SDLC stage then confirmed the effect through six actual applicable cases of information system development project of "K" company.

• Journal of Advanced Navigation Technology
• /
• v.15 no.3
• /
• pp.419-431
• /
• 2011

Design traceability has been widely recognized as being an integral aspect of software development. Also many projects for software application development have failed because that the projects did not analyze user requirements sufficiently and reflected them in the projects adequately. This thesis proposes a specification and tracing technique for object-oriented analysis and design. The subject of this study is the artifacts of UML development methodology. Therefore, to improve the quality of the software development cycle, in short, the system requirement of customers will be able to respond quickly.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2017.11a
• /
• pp.631-634
• /
• 2017

앞으로의 프로젝트에서는 시장 변화, 신기술, 경쟁업체의 대응, 설계결함, 테스트 실패 등의 다양한 외부적 요인으로 인해, 더욱 빈번한 요구사항 변경이 요청된다. 그 이전에 명료한 요구사항을 정의하기가 매우 어렵고, 소프트웨어 구축 중에도 수시로 요구사항이 변경되고 있는 실정이다. 이런 문제는 요구사항 추적성 및 변경 관리의 미비함에 있다. 이를 해결하기 위해, 소프트웨어 개발 프로세스인 요구사항, 분석, 설계, 구현, 테스트 단계에서의 추적성 관리를 위한 프로세스의 구축과 내재화가 필요하다. 본 논문에서는 클로즈 아키텍처 메커니즘을 기반으로 소프트웨어 각 개발 단계 산출물들 간의 추적성 매트릭스를 제시한다. 이를 통해 프로젝트 과정에서의 잦은 요구사항 변경에 유연하게 대처함으로써 소프트웨어 품질 향상에 기여 할 것으로 본다.

• Proceedings of the KIPE Conference
• /
• 2015.11a
• /
• pp.119-120
• /
• 2015

ITER 한국사업단은 AC/DC Converter 최종설계검토(FDR)를 2014년 4월에 끝내고, 제작에 관련된 준비사항 점검인 MRR (Manufacturing Readiness Review)를 2014년 10월에 수행하였다. 1차 제작공정인 CCU/L 컨버터와 관련 I&C System은 2014년 11월부터 제작에 착수하여 곧 FAT(Factory Acceptance Test)를 앞두고 있다. 이 시점에서 중요한 것은 FAT를 앞둔 제작된 기기가 ITER의 설계요건을 충분히 만족하는지에 대한 검증을 하는 것이다. 본 논문은 초전도자석 및 컨버터의 이상상태 또는 고장 시에 장치를 보호하는 중요한 Plant Interlock System(PIS)이 ITER의 설계요건을 충실히 반영하였는지 확인하기 위한 요건추적매트릭스(RTM) 기법을 소개하고, Interlock System의 중요기능인 사고 시 초전도 코일에 충전된 에너지를 급속 방전하기 위한 장치인 DLIB와의 연계기능에 적용한 예를 보이고자 한다.

• Journal of the Korean Society of Industry Convergence
• /
• v.22 no.6
• /
• pp.785-795
• /
• 2019

This paper is a study on the modeling of the quantity estimation model for offshore plant Material handling equipment in FEED(Front End Engineering Design) verification stage using system engineering approach which is an engineering design methods. The relevant engineering execution procedure is not systemized although the operation method and Material handling equipment selection with weight and space constraints is a key part of the FEED. Using the system engineering process, the stakeholder requirements analysis process, the system requirements analysis, and the final system architecture design were sequentially performed, and the process developed through the functional development diagram and Requirement traceability matrix (RTM) was verified. In addition, based on the established process, we propose a Material handling quantity estimation model and Quantity calculation verification Table that can be applied at the FEED verification stage and we verify the applicability through case studies.