요구사항 추적성 매트릭스에서 유연한 맵핑 변경을 가능하게 하는 스프레드시트 애플리케이션

정세린 ( Serin Jeong ),이선아 ( Seonah Lee ) 한국정보처리학회 2018 정보처리학회논문지. 소프트웨어 및 데이터 공학 Vol.7 No.9

요구사항 추적성은 개발과 유지보수 과정 동안 지속적으로 관리해야 한다. 그러나, 실제에서는 품질 보증을 점검하는 단계에서 갱신한다. 이러한 차이는 개발자가 추적성을 갱신하는 노력에 비해 추적성을 통해 얻는 혜택이 적기 때문이다. 이러한 노력 대비 보상의 관점에서 우리는 일반적으로 사용하는 스프레드시트 형태의 요구사항 추적성 매트릭스에서 맵핑을 유연하게 바꿀 수 있는 방법을 제안한다. 제안의 목적은 개발자가 요구사항 추적성을 갱신하는데 들이는 노력을 줄이는 것이다. 제안 방법은 먼저, 각 시트에 두 산출물 간의 관계만을 기입하여 변경이 발생할 때, 개발자가 변경된 맵핑을 즉시 반영할 수 있도록 한다. 다음, 개발자가 원하는 시점에서 제안 방법은 자동적으로 모든 산출물의 관계를 계산하여 추적성 매트릭스를 생성한다. 또한 누락된 맵핑 관계를 색상으로 표시하고 척도를 계산하여 개발자가 추적성 매트릭스의 완전성을 파악하도록 돕는다. 우리는 제안 방법의 적용가능성을 파악하기 위하여 사례 연구를 수행하였다. 사례 연구는 제안한 요구사항 추적성 매트릭스가 실제 프로젝트에 적용 가능하며 변경된 맵핑 관계를 쉽게 수용함을 보여준다. 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.

Current issues on Requirement Traceability Mechanism for Software Organization of the 4th Industrial Revolution

Janghwan Kim,R. Young Chul Kim 한국인터넷방송통신학회 2020 Journal of Advanced Smart Convergence Vol.9 No.4

In the 4th industrial revolution, there are many projects for diverse software applications of smart city environments. Most of the stakeholders focus on considering software quality for their developed software. Nobody doesn’t guarantee requirement satisfaction after complete development. At this time, we can only work on user acceptance testing for requirement satisfaction on frequently changing requirements. Why keeps the requirement traceability? This traceability is to identify risks related to requirements, to assure correct software development based on customer requirements. To solve this, we are researching how to implement requirement traceability across each artifact's relationship to each activity of a whole development lifecycle.

A Comparative Study between LSI and LDA in Constructing Traceability between Functional and Non-Functional Requirements

Sung-Hoon Byun(변성훈),Seok-Won Lee(이석원) 한국컴퓨터정보학회 2019 韓國컴퓨터情報學會論文誌 Vol.24 No.7

Requirements traceability is regarded as one of the important quality attributes in software requirements engineering field. If requirements traceability is guaranteed then we can trace the requirements’ life throughout all the phases, from the customers’ needs in the early stage of the project to requirements specification, deployment, and maintenance phase. This includes not only tracking the development artifacts that accompany the requirements, but also tracking backwards from the development artifacts to the initial customer requirements associated with them. In this paper, especially, we dealt with the traceability between functional requirements and non-functional requirements. Among many Information Retrieval (IR) techniques, we decided to utilize Latent Semantic Indexing (LSI) and Latent Dirichlet Allocation (LDA) in our research. Ultimately, we conducted an experiment on constructing traceability by using two techniques and analyzed the experiment results. And then we provided a comparative study between two IR techniques in constructing traceability between functional requirements and non-functional requirements.

Current issues on Requirement Traceability Mechanism for Software Organization of the 4th Industrial Revolution

Kim, Janghwan,Kim, R. Young Chul The Institute of Internet 2020 International journal of advanced smart convergenc Vol.9 No.4

In the 4th industrial revolution, there are many projects for diverse software applications of smart city environments. Most of the stakeholders focus on considering software quality for their developed software. Nobody doesn't guarantee requirement satisfaction after complete development. At this time, we can only work on user acceptance testing for requirement satisfaction on frequently changing requirements. Why keeps the requirement traceability? This traceability is to identify risks related to requirements, to assure correct software development based on customer requirements. To solve this, we are researching how to implement requirement traceability across each artifact's relationship to each activity of a whole development lifecycle.

요구사항 명세서에 첨부하는 요구사항 추적표 작성 양식 제안

김대승,Kim, DaeSeung 한국시스템엔지니어링학회 2016 시스템엔지니어링학술지 Vol.12 No.1

Most of systems engineers make a traceability matrix and attach it to their technical documents as a result of systems engineering activities. I have been working in the field of systems engineering for many years and have been watching traceability matrices created by systems engineers or developers from various companies. I have been thinking that some of them are not suitable in terms of purposes of traceability matrix. In this paper, I would like to suggest a right template for the traceability matrix in conformance to traceability purposes. The key is that traceability matrix should be created from higher level of requirements to current level of requirements.

요구사항 온톨로지 기반의 시맨틱 태깅을 활용한 산출물의 재사용성 지원을 위한 요구사항추적 방법

이준기(Junki Lee),조혜경(Hae-Kyung Cho),고인영(In-Young Ko) 한국정보과학회 2008 정보과학회논문지 : 소프트웨어 및 응용 Vol.35 No.6

산출물들의 추적 관계 정의를 이용한 요구사항 추적을 통해, 기존의 컴포넌트 자체의 재사용뿐만 아니라 컴포넌트 개발과정에서 나오는 다양한 산출물들을 요구사항 기반으로 재사용할 수 있다. 이러한 재사용성 증가를 목적으로 하는 요구사항추적을 지원하기 위해서는 산출물들이 요구사항을 기반으로 표현될 수 있어야 하고, 표현된 요구사항을 기반으로 하여 추적관계를 추론하는 메커니즘이 제공되어야 한다. 이를 위해, 본 논문에서는 시맨틱스 기반의 요구사항추적을 지원하기 위해서 요구사항 온톨로지를 하여 기술한다. 그 다음에 산출물들이 요구사항 온톨로지를 통해서 시맨틱 태깅되는 기술을 기술한다. 본 논문은 이와 같이 요구사항 추적을 위한 메커니즘을 제안하고, 요구사항 온톨로지의 구조를 정의하며 프로토타입을 제시한다. Requirements traceability enables to reuse various kinds of software artifacts, which are the results from software development life cycle, rather than reuse source code only. To support requirements traceability for reuse of software artifacts, 1) artifacts should be described based on requirements and 2) a requirements tracing method should be supported. In this paper, we provide a description model for annotating requirements information to software artifacts by using requirements ontology. We also provide semantic tagging method users to efficiently annotate artifacts with the requirements ontology. And we finally present how requirements traceability is supported based on requirements ontology and also suggest the system architecture for requirements traceability support.

자동차 전자제어 시스템 개발을 위한 요구공학

조선영(SunYoung Cho),이원택(Wonteak Lee) 한국자동차공학회 2009 한국자동차공학회 학술대회 및 전시회 Vol.2009 No.11

Nowadays environments, safety and comfort are the most important requirements and innovation factors for automotive OEMs and suppliers. Therefore, Requirements engineering has become an important process in automotive system development to handle the complexity of today’s electronic components. This paper describes the process of requirements engineering for development of automotive electric & electronics components in a standardized manner by defining the basic practices like requirements elicitation, requirements analysis, requirements specification and requirements validation. To apply requirements engineering to develop of automotive electronics components, this paper describes the requirements pattern that is mandatory requirements-set of system. Requirements pattern will be the criterion of reuse and the checklist for checking of missing requirements.

산출물의 일관성과 완전성 검증을 위한 추적테이블의 경험적 연구

김주영(Kim Ju Young),류성열(Rhew Sung Yul) 한국정보과학회 2007 정보과학회논문지 : 소프트웨어 및 응용 Vol.34 No.5

소프트웨어 개발시 요구사항이 시스템에 제대로 반영되어 개발되고 있는지를 추적하는 일은 아주 중요하다. 이에, 본 연구에서는 추적테이블을 이용하여 요구사항을 추적하는 방법을 연구하였다. 본 연구에서 제시한 추적테이블에서는 제안요청서, 제안서 등의 내용을 명확히 명세하게 함으로써 요구사항의 발생근거를 명확히 하고, 산출물마다 요구사항 식별코드를 매핑하게 하여 산출물간의 일관성 및 완전성 검증하는데 용이하게 하였다. 아울러, 본 연구를 진행하면서 마르미-Ⅲ v.4.0 방법론의 요구획득단계 산출물중에 추가하거나 보완이 필요한 요소를 발견하게 되었기에 개선된 추적테이블과 함께 부가적인 연구결과로 제시하고자 한다. 본 연구에서 제시한 개선된 추적테이블을 이용하여 산출물을 검증함으로써 소프트웨어 개발시 요구사항 관리 부족으로 일어나는 각종 위험 및 문제요소를 줄일 수 있을 것이다. 또한 마르미-Ⅲ v.4.0 방법론의 요구획득 단계 산출물을 본 연구의 추적테이블 작성방법에 따라 추가 · 보완하게 함으로써 마르미-Ⅲ 방법론의 활용을 높이고자 한다. It is very important to track whether software is properly developed according to requirements. This study suggests a method to track requirements by using a tracking table. In this study, the tracking table indicates why such requirements are included by detailing the content of requests for proposals and proposals. The table also facilitates verification of the consistency between outputs and the integrity by having ID codes of each requirement mapped to each output. Furthermore, as this study was conducted, it was found that some factors were required to be added or supplemented to the outputs at the requirement gathering stage of MaRMI-Ⅲ v.4.0 methodology. Thus, this study seeks to present this additional result along with the enhanced tracking table. By verifying outputs, the tracking table presented in this study will help to reduce all kinds of risks and problems that may occur in software development due to the lack of management of requirements. In addition, the output of the requirement-gathering stage of MaRMI-Ⅲ v.4.0 methodology will be improved/supplemented according to the creation of tracking tables; this will increment the applicability of the MaRMI-Ⅲ methodology.

가치분석을 통한 휘처 기반의 요구사항 변경 관리

안상임(Sangim Ahn),정기원(Kiwon Chong) 한국전자거래학회 2007 한국전자거래학회지 Vol.12 No.3

소프트웨어 개발 초기에 모든 요구사항을 정의하는 것은 불가능 하기 때문에 요구사항은 소프트웨어 개발이 진행되는 동안에 지속적으로 변경된다. 이러한 요구사항 변경은 개발자가 소프트웨어 구조나 행위를 완벽하게 이해하지 못하거나 변경에 따라 영향을 받는 모든 부분을 식별할 수 없을 경우 많은 오류를 야기시킨다. 그러므로, 조직의 비즈니스에 공헌하면서 비용ㆍ효과적으로 적절히 처리되기 위하여 요구사항은 관리되고 평가되어야 한다. 본 논문은 가치분석을 통하여 생성된 휘처 기반의 요구사항 추적 링크를 근간으로 하는 요구사항 변경 관리 기법을 제안한다. 이는 사용자 요구사항과 산출물간의 연결을 분석하기 위하여 휘처를 중간 매개체로 활용한 추적 링크를 이용한다. 그리고 요구사항 변경 요청을 휘처 단위로 상세화하기 위한 변경 트리 모델을 정의하고 변경 관리가 수행되는 전체적인 프로세스를 제시한다. 또한, 요구사항 변경 관리 기법을 자산관리포탈시스템에 적용한 사례의 결과를 기술한다. 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: (l)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.

An Automatic Generation Method of Traceability Links from Requirement to Design in Business Applications

박수진 아이씨티플랫폼학회 2023 JOURNAL OF PLATFORM TECHNOLOGY Vol.11 No.5

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.