• 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.7 no.9
• /
• pp.325-334
• /
• 2018

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.

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

• KIPS Transactions on Software and Data Engineering
• /
• v.3 no.1
• /
• pp.1-6
• /
• 2014

Many companies have tried to adopt Software Product Line Engineering for improving the quality and productivity of information systems and software product. There are several models defined in software product line methodology and each model has different abstraction level. Therefor it is important to maintain the traceability and consistency between models. In this paper, consistency checking rules are suggested by traceability matrix of work products.

• Journal of the Korea Society of Computer and Information
• /
• v.17 no.5
• /
• pp.115-126
• /
• 2012

It is very important to trace whether all the requirements has been reflected in the developed system. However, most existing researches apply Requirement Traceability Matrix(RTM) to the whole SDLC according to the development methodology. RTM has no practical value because it has not only too many pursuit items but also its tracking method is very complicated and the practical management in developing the information system is not accomplished nearly. Therefore, in this study, we proposed an enhanced RTM which was composed of only necessary items and allow us to manage the applied area effectively from Request for Proposal(RFP) or the proposal stage to SDLC stage then confirmed the effect through six actual applicable cases of information system development project of "K" company.

• Journal of Advanced Navigation Technology
• /
• v.15 no.3
• /
• pp.419-431
• /
• 2011

Design traceability has been widely recognized as being an integral aspect of software development. Also many projects for software application development have failed because that the projects did not analyze user requirements sufficiently and reflected them in the projects adequately. This thesis proposes a specification and tracing technique for object-oriented analysis and design. The subject of this study is the artifacts of UML development methodology. Therefore, to improve the quality of the software development cycle, in short, the system requirement of customers will be able to respond quickly.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2017.11a
• /
• pp.631-634
• /
• 2017

앞으로의 프로젝트에서는 시장 변화, 신기술, 경쟁업체의 대응, 설계결함, 테스트 실패 등의 다양한 외부적 요인으로 인해, 더욱 빈번한 요구사항 변경이 요청된다. 그 이전에 명료한 요구사항을 정의하기가 매우 어렵고, 소프트웨어 구축 중에도 수시로 요구사항이 변경되고 있는 실정이다. 이런 문제는 요구사항 추적성 및 변경 관리의 미비함에 있다. 이를 해결하기 위해, 소프트웨어 개발 프로세스인 요구사항, 분석, 설계, 구현, 테스트 단계에서의 추적성 관리를 위한 프로세스의 구축과 내재화가 필요하다. 본 논문에서는 클로즈 아키텍처 메커니즘을 기반으로 소프트웨어 각 개발 단계 산출물들 간의 추적성 매트릭스를 제시한다. 이를 통해 프로젝트 과정에서의 잦은 요구사항 변경에 유연하게 대처함으로써 소프트웨어 품질 향상에 기여 할 것으로 본다.

• Proceedings of the KIPE Conference
• /
• 2015.11a
• /
• pp.119-120
• /
• 2015

ITER 한국사업단은 AC/DC Converter 최종설계검토(FDR)를 2014년 4월에 끝내고, 제작에 관련된 준비사항 점검인 MRR (Manufacturing Readiness Review)를 2014년 10월에 수행하였다. 1차 제작공정인 CCU/L 컨버터와 관련 I&C System은 2014년 11월부터 제작에 착수하여 곧 FAT(Factory Acceptance Test)를 앞두고 있다. 이 시점에서 중요한 것은 FAT를 앞둔 제작된 기기가 ITER의 설계요건을 충분히 만족하는지에 대한 검증을 하는 것이다. 본 논문은 초전도자석 및 컨버터의 이상상태 또는 고장 시에 장치를 보호하는 중요한 Plant Interlock System(PIS)이 ITER의 설계요건을 충실히 반영하였는지 확인하기 위한 요건추적매트릭스(RTM) 기법을 소개하고, Interlock System의 중요기능인 사고 시 초전도 코일에 충전된 에너지를 급속 방전하기 위한 장치인 DLIB와의 연계기능에 적용한 예를 보이고자 한다.

• Bulletin of the Korean Chemical Society
• /
• v.35 no.11
• /
• pp.3275-3279
• /
• 2014

A mass balance method for purity assessment of thermolabile organic reference materials was established by combining several techniques, including liquid chromatography with UV/VIS detector (LC-UV), Karl-Fischer (K-F) Coulometry, and thermal gravimetric analysis (TGA). This method was applied to three fluoroquinolones like enrofloxacin, norfloxacin and ciprofloxacin. LC-UV was used to analyze structurally related organic impurities based on UV/VIS absorbance spectra obtained in combination with LC separation. For all three organic reference materials, the UV/VIS spectra of the separated impurities were similar to that of the major component of the corresponding materials. This indicates that the impurities are structurally related to the respective reference material sharing common chromophores. Impurities could be quantified by comparing their absorbances at the wavelength of maximum absorbance (${\lambda}_{max}$). The water contents of the reference materials were measured by K-F Coulometry by an oven-drying method. The total inorganic impurities contents were assayed from ash residues in TGA analysis with using air as a reagent gas. The final purities estimated from results of those analytical techniques were assigned as ($99.91{\pm}0.06$), ($97.09{\pm}0.17$) and ($91.85{\pm}0.17$)% (kg/kg) for enrofloxacin, norfloxacin and ciprofloxacin, respectively. The assigned final purities would be applied to the reference materials which will be used as calibrators for the certification of those compounds in matrix CRMs as starting points for the traceability of their certified values to SI units.

• The KIPS Transactions:PartD
• /
• v.11D no.2
• /
• pp.407-414
• /
• 2004

The US DoD architecture framework defines architecture Products according to three viewpoints : operational view, system view, and technical view. But, its coarse-grained development process causes leakage of the details In transforming among different views. It also uses different methods for architecture products development, so that the levels of those products are not consistent. So. we propose MND AF(Ministry of National Defense Architecture Framework) for military environment to solve those problems. We propose additional architecture products to achieve consistency, including “architecture disciplines definition description,”“organization-to-activity relationships matrix,” “system definition description,” and “technical reference model,” etc. We also propose the architecture development process in more detail through seven steps. In addition, we propose the applicability of those products to the life cycle processes of the acquisition management. MND AF can provide consistency and traceability of architecture products, provide the basis for sl·stem integration and interoperability. Also, architecture developers can construct architecture in a more effective and efficient way through MND AF.