• 한국컴퓨터정보학회논문지
• /
• 제24권7호
• /
• pp.19-29
• /
• 2019

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.

• 시스템엔지니어링학술지
• /
• 제12권1호
• /
• pp.1-5
• /
• 2016

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.

• 정보처리학회논문지:소프트웨어 및 데이터공학
• /
• 제4권11호
• /
• pp.487-498
• /
• 2015

추적성은 소프트웨어 개발자에게 소프트웨어 산출물에 대한 변경을 추적하게 해 준다. 소프트웨어 제품 라인 개발에 있어서의 추적성은 공통성과 가변성을 고려해야 하기 때문에, 개별 제품에서의 추적성보다 복잡하다. 과거 연구에서 제품 라인 개발에서의 제품 피처와 요구사항 간의 추적성 구축을 제시되었다. 그러나 요구사항과 아키텍처 설계 사이의 추적성 구축은 다 대 다 관계와 아키텍처 계층으로 인해 고려해야 할 요소가 더 많다. 본 논문은 이러한 요소들을 고려하여, 제품 라인 개발에서의 요구사항과 아키텍처 사이의 추적성을 모델링하는 체계적인 방법을 제공한다. 또한 사례연구를 통하여 이 방법이 효과적임을 보인다.

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

• 한국정보과학회논문지:소프트웨어및응용
• /
• 제35권6호
• /
• pp.357-365
• /
• 2008

산출물들의 추적 관계 정의를 이용한 요구사항 추적을 통해, 기존의 컴포넌트 자체의 재사용뿐만 아니라 컴포넌트 개발과정에서 나오는 다양한 산출물들을 요구사항 기반으로 재사용할 수 있다. 이러한 재사용성 증가를 목적으로 하는 요구사항추적을 지원하기 위해서는 산출물들이 요구사항을 기반으로 표현될 수 있어야 하고, 표현된 요구사항을 기반으로 하여 추적관계를 추론하는 메커니즘이 제공되어야 한다. 이를 위해, 본 논문에서는 시맨틱스 기반의 요구사항추적을 지원하기 위해서 요구사항 온톨로지를 하여 기술한다. 그 다음에 산출물들이 요구사항 온톨로지를 통해서 시맨틱 태깅되는 기술을 기술한다. 본 논문은 이와 같이 요구사항 추적을 위한 메커니즘을 제안하고, 요구사항 온톨로지의 구조를 정의하며 프로토타입을 제시한다.

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

• International journal of advanced smart convergence
• /
• 제9권4호
• /
• pp.167-172
• /
• 2020

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.

• 한국전자거래학회지
• /
• 제12권4호
• /
• pp.1-15
• /
• 2007

추적 링크는 요구사항과 아키텍처 설계서, 소스 코드, 테스트 케이스 등과 같은 시스템 산출물들 사이의 논리적인 연결을 의미한다. 이러한 추적 링크는 요구사항 변경 영향 분석, 요구사항 충돌 분석, 요구사항 일관성 점검에 매우 유용하다. 그러나, 복잡한 소프트웨어 개발시 많은 다양한 산출물들이 만들어지므로 추적 링크를 생성하거나 운용하는 것은 많은 부담을 초래한다. 본 논문은 가치분석을 근간으로 하고 휘처를 중간 매개체로 활용하는 휘처 기반의 요구사항 추적 기법을 제안한다. 이는 사용자 요구사항과 산출물간의 추적 링크를 생성하기 위한 중간 매개체로 휘처 개념을 적용하였고, 식별된 휘처들의 상세화 정도를 추정하기 위하여 요구사항의 우선순위에 따른 가치 평가를 포함한다. 또한, 본 논문에서 제안한 휘처 기반의 요구사항 추적 기법을 아파트 단지 내 홈 서비스를 통합하는 유비쿼터스 플랫폼에 적용한 사례의 결과를 기술한다.

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

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