• Journal of the Korea Society of Computer and Information
• /
• v.24 no.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.

• Journal of the Korean Society of Systems Engineering
• /
• v.12 no.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.

• KIPS Transactions on Software and Data Engineering
• /
• v.4 no.11
• /
• pp.487-498
• /
• 2015

Traceability enables software developers to trace up the changes occurring in software artifacts. In software product line, traceability is more complex than traceability in a single product as commonality and variability should be considered. Modeling traceability between features and requirements has been proposed in the past. However, traceability between requirements and architecture has more factors to consider, including many-to-many mappings and hierarchical structure of architectures. This paper proposes a method of systematically constructing platform traceability between platform requirements and platform architecture. This paper also shows the efficacy of the proposed mechanism through case studies.

• Journal of the Korean Society of Systems Engineering
• /
• v.6 no.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.

• Journal of KIISE:Software and Applications
• /
• v.35 no.6
• /
• pp.357-365
• /
• 2008

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.

• Journal of the Korea Safety Management & Science
• /
• v.9 no.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
• /
• v.9 no.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.

• The Journal of Society for e-Business Studies
• /
• v.12 no.4
• /
• pp.1-15
• /
• 2007

Traceability links are logical links between individual requirements and other system elements such as architecture descriptions, source code, and test cases. These are useful for requirements change impact analysis, requirements conflict analysis, and requirements consistency checking. However, establishing and maintaining traceability links places a big burden since complex systems have especially yield an enormous number of various artifacts. We propose a feature-oriented requirements tracing method to manage requirements with cost benefit analysis, including value consideration and intermediate catalysis using features. Our approach offers two contributions to the study of requirements tracing: (1)We introduce feature modeling as intermediate catalysis to generate traceability links between user requirements and implementation artifacts. (2)We provide value consideration with cost and efforts to identify traceability links based on prioritized requirements, thus assigning a granularity level to each feature. In this paper, we especially present the results of a case study which is carried out in Apartment Ubiquitous Platform to integrate and connect home services in an apartment complex in details.

• Journal of the Korean Society of Systems Engineering
• /
• v.7 no.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.

• Journal of the Korean Society of Systems Engineering
• /
• v.2 no.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.