DOI QR코드

DOI QR Code

Failure Analysis of Aircraft Software Test Cases from a Perspective of Requirements Traceability

요구사항 추적성 관점에서 항공기 탑재 소프트웨어 시험 사례 실패 분석

  • 김성섭 (한국항공우주산업(주) KFX임무SW팀) ;
  • 조희태 (경상대학교 AI융합공학과) ;
  • 이선아 (경상대학교 항공우주 및 소프트웨어공학전공/AI융합공학과)
  • Received : 2020.08.26
  • Accepted : 2020.09.20
  • Published : 2020.11.30

Abstract

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.

항공기 탑재 소프트웨어의 비중 및 복잡성 증가에 따라, 소프트웨어 고장으로 인한 임무수행이나 기능 실패 및 성능 미달 등의 위험요인 또한 증가하고 있다. 항공기 탑재 소프트웨어처럼 미션 크리티컬 도메인의 대규모 소프트웨어에서 최소한의 기간과 비용으로 유지보수를 진행하기 위해서는 요구사항 추적관리가 필수적이다. 하지만, 개발업체에서는 개발비용이나 개발일정 등의 여러 사유로 인해 요구사항 추적관리 지침을 정확히 준수하지 못하고 있으며, 체계적으로 추적성 수립 활동을 수행하기란 쉽지 않다. 논문에서는 체계적인 추적성 수립 활동의 부재에 따른 요구사항 추적성 실패사례가 실제로 존재하는지 항공분야 소프트웨어의 실제 시험사례를 요구사항 추적성 관점에서 분석하고, 추적성 실패사례의 유형과 사안 경중에 따른 위험을 확인한다. 총 7개의 항공기 탑재 소프트웨어를 대상으로 분석을 진행한 결과, 실패사례는 총 3가지 유형인 요구사항 누락, 요구사항-시험절차 연계부족, 시험절차 누락으로 나눌 수 있었다. 실패사례는 총 18건으로 각 유형별 6건씩 있었으며, 각 사안에 따른 Risk는 High, Middle, Low 순으로 각각 1건, 13건, 4건으로 중간 수준의 위험이 가장 많았다.

Keywords

References

  1. S. N. Lee, "A Proposal for Creating Blue Ocean on Weapon System Software," Defense & Technology, Vol.433, pp.76-87, 2015.
  2. F. A. C. Pinheiro, "Requirements Traceability. In: do Prado Leite J.C.S., Doorn J.H. (eds) Perspectives on Software Requirements," The Springer International Series in Engineering and Computer Science, Vol.753, Springer, Boston, MA, 213004.
  3. M. Elizabeth and C. Hull, "Introduction to SW Verification and Validation, Requirements Engineering" 2005.
  4. J. K. Lee, H. K. Cho, and I. Y. Ko. "A Method for Requirements Traceability for Reuse of Artifacts using Requirements- Ontology-based Semantic Tagging," Journal of KISS: Software and Applications, Vol.35, No.6, pp.357-365, 2008.
  5. G. Antoniol, G. Canfora, G. Casazza, De Lucia, A. and E. Merlo, "Recovering Traceability Links Between Code and Documentation," Software Engineering, IEEE Transactions on, Vol.28, No.10, pp.970-983, 2002. https://doi.org/10.1109/TSE.2002.1041053
  6. B. G. Lee, M. S. Hwang, Y. B. Lee, H. J. Lee, J. M. Baik, and C. K. Lee, "Design and Development of a Standard Guidance for Software Requirement Specification," Journal of KISS : Software and Applications, Vol.36, No.7, pp.531-538, 2009.
  7. D. S. Kim, "A Suggestion on a Better Template for Requirements Traceability Matrix of a Requirements Specification," Journal of the Korea Society of Systems Engineering, Vol.12, No.1, pp.1-5, 2016. https://doi.org/10.14248/JKOSSE.2016.12.1.001
  8. J. Y. Kim, S. Y. Rhew, and M. S. Hwang. "A Study of Requirement Change Management and Traceability Effect Using Traceability Table," Journal of KIPS D, Vol.17, No.4, pp.271-282, 2010.
  9. M. H. Yim and H. S. Kim, "Case of Requirement Traceability Management Using Computer-Aided Systems Engineering Tool In Light Rail Transit Project," Proc. of the KSR Conference, pp.768-773, 2016.
  10. L. Murray, A. Griths, P. Lindsay, and P. Strooper, "Requirements Traceability for Embedded Software - an Industry Experience Report," Proceedings of the 6th IASTED International Conference on Software Engineering and Applications, pp.374-068, SEA 2002.
  11. A. Qusef, "Test-to-code traceability: Why and how?," IEEE Jordan Conference on Applied Electrical Engineering and Computing Technologies (AEECT), Amman, pp.1-8, doi:10.1109/AEECT.2013.6716450, 2013.
  12. J. H. Jang, J. S. Jang, Y. S. Kang, and B. D. Shin. "The Case Study on Software Dynamic Testing Process Using Static Analysis in Compliance with DO-178C(Airborne Software Certification)," Proc. of the KSASS Spring Conference, pp.842-844, 2016.
  13. J. H. Jang, J. S. Jang, and Y. S. Kang, "The Case Study on Requirement-based Software Testing Process and achievement of Test Coverage in compliance with DO-178C(Airborne Software Certification)," Proc. of the KSASS Fall Conference, pp.1184-1185, 2016.
  14. Weapon System Software Development and Management Manual No.2017-8: Appendix 7, 5-7.