KIPS Transactions on Software and Data Engineering (정보처리학회논문지:소프트웨어 및 데이터공학)

Korea Information Processing Society (한국정보처리학회)
권호 표지
DOI QR코드

DOI QR Code

A Spreadsheet Application that Enables to Flexibly Change Mappings in Requirement Traceability Matrix

요구사항 추적성 매트릭스에서 유연한 맵핑 변경을 가능하게 하는 스프레드시트 애플리케이션

  • 정세린 (경상대학교 정보과학과) ;
  • 이선아 (경상대학교 기계항공정보공학부 항공우주및소프트웨어전공)
  • Received : 2018.03.07
  • Accepted : 2018.03.27
  • Published : 2018.09.30
Download PDF
⟨ Previous Next ⟩

Abstract

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.

요구사항 추적성은 개발과 유지보수 과정 동안 지속적으로 관리해야 한다. 그러나, 실제에서는 품질 보증을 점검하는 단계에서 갱신한다. 이러한 차이는 개발자가 추적성을 갱신하는 노력에 비해 추적성을 통해 얻는 혜택이 적기 때문이다. 이러한 노력 대비 보상의 관점에서 우리는 일반적으로 사용하는 스프레드시트 형태의 요구사항 추적성 매트릭스에서 맵핑을 유연하게 바꿀 수 있는 방법을 제안한다. 제안의 목적은 개발자가 요구사항 추적성을 갱신하는데 들이는 노력을 줄이는 것이다. 제안 방법은 먼저, 각 시트에 두 산출물 간의 관계만을 기입하여 변경이 발생할 때, 개발자가 변경된 맵핑을 즉시 반영할 수 있도록 한다. 다음, 개발자가 원하는 시점에서 제안 방법은 자동적으로 모든 산출물의 관계를 계산하여 추적성 매트릭스를 생성한다. 또한 누락된 맵핑 관계를 색상으로 표시하고 척도를 계산하여 개발자가 추적성 매트릭스의 완전성을 파악하도록 돕는다. 우리는 제안 방법의 적용가능성을 파악하기 위하여 사례 연구를 수행하였다. 사례 연구는 제안한 요구사항 추적성 매트릭스가 실제 프로젝트에 적용 가능하며 변경된 맵핑 관계를 쉽게 수용함을 보여준다.

Keywords

References

  1. J. E. Garcia and A. C. Paiva, "A Requirements-to- Implementation Mapping Tool for Requirements Traceability," J. of Software, Vol.11, No.2, pp.193-200. 2016. https://doi.org/10.17706/jsw.11.2.193-200
  2. Jongyeol Park, Seunghui Ryu, Serin Jung, Seonah Lee, "Investigation on the difficulties of managing traceability in the evolution of software requirements," 19th Korea Conference on Software Engineering, KCSE, 2017.
  3. J. Cleland-Huang, C. K. Chang, and M. Christensen, "Event-based traceability for managing evolutionary change," IEEE Trans. on Software Eng., Vol.29, No.9, pp.796-810, 2003. https://doi.org/10.1109/TSE.2003.1232285
  4. S. Saito, Y. Iimura, H. Tashiro, A. K. Massey, and A. I. Anton, "Visualizing the effects of requirements evolution," Proc. 38th Int. Conf. on Software Eng. Companion (ICSE '16), ACM, pp.152-161, 2016.
  5. S. A. Sherba, K. M. Anderson, and M. Faisal, "A framework for mapping traceability relationships," Proceedings of the 2nd International Workshop on Traceability in Emerging Forms of Software Engineering. 2003.
  6. N. Ali, Y. G. Gueheneuc, and G. Antoniol, "Trustrace: Mining software repositories to improve the accuracy of require- ment traceability links," IEEE Transactions on Software Engineering, Vol.39, No.5, pp.725-741, 2013. https://doi.org/10.1109/TSE.2012.71
  7. S. Palihawadana, et al., "Tool support for traceability management of software artefacts with DevOps practices," Engineering Research Conference (MERCon), 2017 Moratuwa. IEEE, 2017.
  8. S. Maro and J. P. Steghofer, "Capra: A Configurable and Extendable Traceability Management Tool," Requirements Engineering Conference (RE), 2016 IEEE 24th International. IEEE, 2016.
  9. W. Hussain and T. Clear, "Spreadsheets as collaborative technologies in global requirements change management," Global Software Engineering (ICGSE), 2014.
  10. J. Marshall et al., "Transitioning model based systems engineering to onboard spacecraft electronics," Aerospace Conference, 2017 IEEE. IEEE, 2017.
  11. R. Wohlrab et al., "Collaborative traceability management: Challenges and opportunities," Requirements Engineering Conference (RE), 2016 IEEE 24th International. IEEE, 2016.
  12. Juyoung Kim, Sungyul Rhew, Mansu Hwang, "A Study of Requirement Change Management and Traceability Effect Using Traceability Table," The KIPS Transactions: Part D, Vol.17, No.4, pp.271-282. 2010.
  13. S. C. Jayaraman and M. Anand, "The Impact of Visualizing Traceability Links for Evolving Requirements in Software Maintenance-A Controlled Experiment."