• 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.

• Proceedings of the KSR Conference
• /
• 2010.06a
• /
• pp.1821-1828
• /
• 2010

In this study we suggest a method of optimization of verification hierarchy structure and system requirements management by using a verification matrix with traceability consideration. Verification items were gathered in the process of CDR(Critical Design Review), and analyzed with respect to requirements traceability structure. Missed or overlapped items were adjusted, and cross-correlated items between sub-systems were clustered and rearranged in order to structurize verification requrements (VRs). Those VRs are to be used as a guideline for the test and evaluation planning, development of test items and procedure, and system requirements management throughout the system integration stages.

• 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 Digital Contents Society
• /
• v.13 no.2
• /
• pp.247-254
• /
• 2012

The management of user requirements for information system development is a key element. The traceability has been studied in a specific method as using a traceability table or SOA related to the requirement management. But there are few case about proposing a objective and quantified evaluation method and judgement criterion for none-technical business managers. This researcher has proposed, easy to access by unprofessional and objective and qualifiable, evaluation methods and criteria of Judging for adequacy of requirements reflection in the development process of information system for the government office through a previous case study. In this study, I will give consideration to study the limitations of previous studies and improve the evaluation formula for measuring the reflection of the requirements and derive, reviewed to provide a variety of criteria for each business, through business case analysis.

• Journal of the Korea Institute of Military Science and Technology
• /
• v.3 no.2
• /
• pp.149-155
• /
• 2000

This paper presents results from a computer-aided systems engineering application to system development projects. RDD-100 version of ALC Inc. was used in this work. The framework adopted in the study takes a unified approach to the system design and the process management associated with it, thereby coherent and full traceability between them is maintained. Conventional system engineering process supported by the tool is adopted in the system design. On the other hand, the same tool is also used to the systems engineering management to get full traceability between system design data and engineering management data. It is greatly helpful in managing many sub-contractors in the sense that the traceability can help identify the sub-project responsibility as well as the objectives of the project in coordination with interface requirements. We conclude with the advantage and limits of our unified approach.

• 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.

• Journal of the Korea Safety Management & Science
• /
• v.15 no.1
• /
• pp.11-19
• /
• 2013

In modern systems design and development, one of the key issues is considered to be related with how to reflect faithfully the stakeholder requirements including customer requirements therein, thereby successfully implementing the system functions derived from the requirements. On the other hand, the issue of safety management is also becoming greatly important these days, particularly in the operational phase of the systems under development. An approach to safety management can be based on the use of the failure mode effect and analysis (FMEA), which has been a core method adopted in automotive industry to reduce the potential failure. The fact that a successful development of cars needs to consider both the complexity and failure throughout the whole life cycle calls for the necessity of applying the systems engineering (SE) process. To meet such a need, in this paper a method of FMEA is developed based on the SE concept. To do so, a process model is derived first in order to identify the required activities that must be satisfied in automotive design while reducing the possibility of failure. Specifically, the stakeholder requirements were analyzed first to derive a set of functions, which subsequentially leads to the task of identifying necessary HW/SW components. Then the derived functions were allocated to appropriate HW/SW components. During this design process, the traceability between the functions and HW/SW components were generated. The traceability can play a key role when FMEA is performed to predict the potential failure that can be described with the routes from the components through the linked functions. As a case study, the developed process model has been applied in a project carried out in practice. The results turned out to demonstrate the usefulness of the approach.

• KIPS Transactions on Software and Data Engineering
• /
• v.9 no.11
• /
• pp.357-366
• /
• 2020

As the proportion and complexity of software embedded in aircraft increase, risk factors such as mission failure, function failure and performance failure due to software errors also increase. In the mission-critical software systems such as aircraft software, managing requirement traceability is essential to maintain the software systems with minimal period and cost. However, the development company is not accurately complying with the guideline for managing requirement traceability due to various reasons such as development cost and schedule. Therefore, it is not easy to systematically establish and maintain requirement traceability. In the paper, we analyze actual test cases of aviation software systems from the viewpoint of requirements traceability in order to learn if there are failure cases of test cases due to the absence of systematic traceability management activities. We also check the risks associated with the failure cases according to the type and severity of the cases. As a result of analyzing a total of 7 aircraft-mounted software, failure cases could be divided into three types: omission of requirements, lack of connection between requirements and test procedures, and omission of test procedures. There were a total of 18 failure cases, 6 for each type. The numbers of high, middle and low risks were 1, 13 and 4, respectively, where the number of middle risks is largest.

• Journal of Internet Computing and Services
• /
• v.10 no.1
• /
• pp.175-182
• /
• 2009

Less efforts has been made in developing specifications and verification techniques for quality requirements. This paper suggests specification and traceability methods supporting quality issues such as usability, performance, and understandability when developing information systems with UML notation. With traceability checking methods that augment quality extension to the use cases and sequence diagrams, developers can confirm the level of implementation for both functional and nonfunctional requirements beforehand.

• 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.