• The KIPS Transactions:PartD
• /
• v.17D no.4
• /
• pp.271-282
• /
• 2010

Insufficient requirement management accounts for 54% ofunsuccessful software development projects and 22% of insufficient requirement management comes from requirement change management. Hence, requirement management activities are important to reduce failure rates and a tracing method is suggested as the major factor in requirements change management. A traceability table is easy to use because of its legibility accurate tracing. However, traceability tables of existing studies have failed to concretely suggest method of change management and effect of traceability. Also, studies of methods to estimate change impact is complex. Hence, this study suggests how to use a traceability table to manage changes in requirements. Together, in comparison to existing studies, this study suggests easier methods to estimate change rate and change impact. Also Fifteen projects were sampled to test the hypothesis that traceability table influences the success of projects and that it decreases the failure rate that comes from the insufficient requirements management.

• Journal of KIISE:Software and Applications
• /
• v.33 no.7
• /
• pp.615-623
• /
• 2006

A non-functional requirement is a property or quality that the proposed systems have to support the functional requirements. A non-functional requirement is reflected by quality attribute These non-functional requirements playa crucial role during system development, serving as selection criteria for choosing among decisions. It should be continuously considered through the software development process. In spite of the importance of the non-functional requirements, it received little attention because of ambiguousness and invisibility of non-functional requirements. Therefore non-functional model which is a process to analyze the non-functional requirement is proposed for improving the management efficiency of non-functional requirements. Also, this paper presents the trace among the UML diagrams to the conceptual model. According to the non-functional requirement development process, this paper achieved performance-based case study. After then, non-functional requirement should be traced using the UML diagrams.

• Proceedings of the Korean Society of Computer Information Conference
• /
• 2017.07a
• /
• pp.281-284
• /
• 2017

최근 임베디드 시스템 개발이 Model Driven Engineering 방식으로 변화하면서 요구사항과 모델 간의 추적성을 보장하는 것이 매우 중요해졌다. 이 논문에서는 기존의 FDD(Feature Driven Development)와 FOSE(Feature Oriented Software Engineering) 방법론에 적용된 feature 개념을 재정의하여 이를 AUTOSAR platform에 적용하는 방법을 제시하며 요구사항부터 model, code까지 추적성을 검증한다.

• Proceedings of the Korean Information Science Society Conference
• /
• 2004.10b
• /
• pp.352-354
• /
• 2004

비기능적 요구사항은 대상 시스템이 지원해야 할 기능적 요구사항의 속성 또는 품질로써 소프트웨어 품질 속성으로 반영된다. 또한 비기능적 요구사항은 설계를 결정하기 위한 중요한 기준으로 사용되므로 소프트웨어 개발 프로세스 전반에 걸쳐 꾸준히 고려하고, 관리해야 한다. 하지만 비기능적 요구사항은 가시성이 없고, 명확히 명세하기가 어려운 특성으로 인해 간과하기 쉽다 따라서 비기능적 요구사항을 실제 모델링에 반영하고, 이를 추적하여 계속적으로 관리하기 일한 노력이 필요하다. 이에 본 논문에서는 내장형 소프트웨어의 비기능적 요구사항을 모델링 하는 절차를 제안하며, 내장형 소프트웨어의 특성을 가진 지능형 조명 제어 시스템의 사례를 통해 비기능적 요구사항을 반영한 모델링을 수행하고, 다이어그램들 사이' 의 비기능적 요구사항에 대한 추적 과정을 살펴본다

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.20 no.3
• /
• pp.91-99
• /
• 2019

Naval Ships have a number of requirements related to performance. Naval ship acquisition takes a long time from initial planning to delivery, and various products such as drawings and reports are created. In complex systems, such as naval ships, it is difficult to maintain the required traceability through these outputs. The basic design of the ship is an important step to determine the specifications, performance, and equipment of the ship. It is necessary to apply the systematic requirements management process. The basic design manages the requirements in accordance with the systems engineering-based technical review process, but the actual system architecture design process is not presented. The traceability between the requirements and the functional and physical architectures of components is unclear. This paper examined how to design the system architecture required for specification and system design, and the design results were verified using SE-based technical review process for requirements management. A step-by-step process for designing a submarine system architecture is presented and verified using the SE technical review. This facilitates the specification of the requirements and system architecture design, and supports traceability management and verification of the requirements. The proposed process can be applied in various ships including submarines.

• Journal of KIISE:Software and Applications
• /
• v.33 no.8
• /
• pp.655-667
• /
• 2006

This paper proposes a method for counting function point using goal and scenario based requirements. Function Point is a software sizing method and widely used as a basis to estimate software development cost. Requirements elicitation and analysis should be performed before function point analysis but function point analysis method doesn't deal with requirements elicitation and analysis. For that reason, Function point extraction method from existing requirements method is needed and if the requirements method has advantage for traceability and elicitation, it is suitable for managing cost. Goal and scenario method is widely used as requirements elicitation and analysis. It has also good traceability. Therefore, this paper discusses a method for extracting function point from requirements text gathered using the goal and scenario based requirements elicitation technique. The proposed method aims to establish and maintain traceability between function point and requirements text. Text based function point extraction guidance rules have been developed. The proposed methodology has been applied to Order Processing System development.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2004.11a
• /
• pp.425-428
• /
• 2004

고품질의 소프트웨어 시스템을 개발하기 위해서 소프트웨어 테스트는 중요하다. 소프트웨어 개발 시에 발견되는 심각한 결함과 오류들은 소프트웨어 시스템이 사용자의 요구사항을 정확히 충족시키지 못하는데 원인이 있다. 테스트 수행 시에 요구사항을 정확히 반영하지 못한다면 반드시 테스트되어야 할 조건들이 누락될 수 있고 테스트의 성취도는 감소한다. 따라서 모든 소프트웨어 테스트는 사용자의 요구사항을 추적할 수 있어야 한다. 이를 위해 본 논문에서는 객체지향 접근방법을 사용하여 사용자의 요구사항을 테스트에 반영하고 추적하기 위한 일관성 유지 기법을 제안한다. 이를 기반으로 요구사항을 만족하는 일관성 있는 테스트케이스를 생성한다.

• Journal of Internet Computing and Services
• /
• v.22 no.3
• /
• pp.59-66
• /
• 2021

This study proposes a requirements monitoring method that systematically performs traceability management and change management for requirements in order to improve the quality of software systems in the software development process. To this end, we present the artifact change history management models to systematically perform change management for individual artifacts and the traceability matrixes to define the relationship between artifacts. It also proposes a visual dashboard that makes it easy to grasp the situation in which changes are propagated to related artifacts when specific artifacts change.

• The Journal of Society for e-Business Studies
• /
• v.12 no.3
• /
• pp.33-47
• /
• 2007

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: (1) 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.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2011.11a
• /
• pp.1283-1284
• /
• 2011

요구공학에서 추적성은 최상위 설계요건과 하부 컴포넌트 설계도면과의 논리적인 연관성을 극명하게 나타내는 지표이다. 핵연료주기 시설인 파이로 시스템의 신뢰성을 증진시키기 위해 데이터 분석 및 의사결정 방법을 제안한다. 샘플 데이터를 입력하여 실험한 결과 파이로시스템의 최상위 설계요건부터 컴포넌트 설계도면까지 요구사항을 충족시킴으로써 추적성의 논리근거를 마련하였다.