The KIPS Transactions:PartD (정보처리학회논문지D)

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

DOI QR Code

Traceability Enhancement Technique for Dependency Relations of Software Artifacts based on the Integration of Software Configuration Management System and Personal Workspace

소프트웨어 형상관리 시스템과 개인 작업공간 통합 기반 산출물 의존 관계 추적성 개선 기법

  • 김대엽 (충남대학교 컴퓨터공학과 대학원) ;
  • 윤청 (충남대학교 컴퓨터공학과)
  • Received : 2011.04.26
  • Accepted : 2011.06.29
  • Published : 2011.12.31
Download PDF
⟨ Previous Next ⟩

Abstract

The ability to trace change history and dependency relations of software artifacts which are continuously changed has been recognized as an important factor that support quality management activities such as verification, validation, and testing in software system development process. General software configuration management systems provide tracing information for artifacts only within the configuration management system, and it does not go further to changes that occur within personal workspace. This paper provides a solution that helps tracing down not only changes of configuration items but also change history of artifacts existent in personal workspace through the integration of configuration management system and personal workspace. Furthermore, in cases of artifacts which are included in a configuration item, this paper provides a solution that support tracing dependency relations between the artifacts by identifying their version links. For the integration of configuration management system and personal workspace, a revision of configuration item is connected to the artifact's version of the workspace by the tagging mechanism, and traceability for change history and dependency relations of artifacts can be managed more effectively through integrated change process.

지속적으로 변경되는 소프트웨어 산출물들의 변경 이력과 의존 관계를 추적하는 능력은 소프트웨어 시스템 개발 프로세스에서 확인 및 검증, 시험과 같은 품질관리 활동들을 지원하는 중요한 요소로 인식되고 있다. 일반적인 소프트웨어 형상관리 시스템들은 산출물에 대한 추적 정보를 형상관리 시스템 내에서만 제공하고 있으며 개인의 작업공간에서 발생한 개별적인 변경까지 추적하는 기능은 지원하지 못하고 있다. 본 연구를 통해 형상관리 시스템과 개인의 작업공간을 통합함으로써 형상항목에 대한 변경뿐만 아니라 개인의 작업공간에 존재하는 산출물들의 변경 이력까지 추적할 수 있도록 하였다. 더 나아가 소프트웨어 산출물들이 동시에 생성되어 하나의 형상항목에 포함되는 경우 이들 산출물들의 버전 링크를 식별함으로써 산출물들 사이의 의존 관계를 추적할 수 있도록 하였다. 형상관리 시스템과 개인 작업공간의 통합을 위해 형상항목의 수정버전(revision)을 작업공간에 존재하는 산출물들의 버전에 태그로 연결시켰으며, 통합 변경 과정에서 산출물들에 대한 변경 이력 및 의존 관계의 효율적인 추적이 가능하도록 하였다.

Keywords

References

  1. http://www.iso.org
  2. Pohl K., "PRO-ART: Enabling Requirements Pre-Traceability", Proceedings of the 2nd IEEE International Conference on Requirements Engineering (ICRE 1996), 1996. https://doi.org/10.1109/ICRE.1996.491432
  3. Cleland-Huang J., Schmelzer D., "Dynamic Tracing Non-Functional Requirements through Design Pattern Invariants", Proceedings of the 2nd International Workshop on Traceability in Emerging Forms of Software Engineering(TEFSE 2003), Canada, Oct., 2003.
  4. Cleland-Huang J., Chang C.K., Sethi G., Javvaji K., Hu H., Xia J., "Automatic Speculative Queries through Event-based Requirement Traceability", Proceedings of the IEEE Joint International Requirements Engineering Conference, Germany, Sept., 2002. https://doi.org/10.1109/ICRE.2002.1048540
  5. Egyed A., Gruenbacher P., "Automatic Requirements Traceability: Beyond the Record and Replay Paradigm", Proceedings of the 17th IEEE International Conference on Automated Software Engineering, Edinburgh, UK, Sept., 2002. https://doi.org/10.1109/ASE.2002.1115010
  6. Song X., Hasling B., Mangla G., Sherman B., "Lessons Learned from Building a Web-Based Requirements Tracing System", Proceedings of 3rd International Conference on Requirements Engineering, pp.41-50, 1998. https://doi.org/10.1109/ICRE.1998.667807
  7. Stout G.A., "Requirements Traceability and the Effect on the System Development Lifecycle(SDLC)", http://www.reveregroup.com/articles/137_005-RevereThoughtLeadership.pdf
  8. Ramesh B., Jarke M., "Toward Reference Models for Requirements Traceability", IEEE Transactions on Software Engineering, 27(1), Jan., 2001. https://doi.org/10.1109/32.895989
  9. Gotel O., Finkelstein A., "An Analysis of the Requirements Traceability Problem", Proceedings of the 1st International Conference in Requirements Engineering, pp.94-101, 1994. https://doi.org/10.1109/ICRE.1994.292398
  10. Spanoudakis G., Zisman A., "Software Traceability: A Roadmap", Handbook of Software Engineering and Knowledge Engineering, Vol.3, pp.395-428, Aug., 2005.
  11. Lindvall M., Sandahl K., "Practical Implications of Traceability", Software Practice and Experience, Vol.26, No.10, pp.1161-1180, 1996. https://doi.org/10.1002/(SICI)1097-024X(199610)26:10<1161::AID-SPE58>3.0.CO;2-X
  12. Maletic J.I., Munson E.V., Marcus A., Nguyen T.N., "Using a Hypertext Model for Traceability Link Conformance Analysis", Proceedings of the 2nd International Workshop on Traceability for Emerging Forms of Software Engineering (TEFSE '03), Canada, Oct., 2003.
  13. Pfleeger S.L., Bohner S.A., "A Framework for Software Maintenance Metrics", Proceedings of 6th Conference on Software Maintenance, pp.320-327, 1990. https://doi.org/10.1109/ICSM.1990.131381
  14. Antoniol G., Canfora G., Casazza G., De Lucia A., "Maintaining Traceability Links during Object-Oriented Software Evolution", Software Practice and Experience, 31(4), pp.331-355, 2001. https://doi.org/10.1002/spe.374
  15. Buckner J., Buchta J., Petrenko M., Rajlich V., "JRipples: A tool for program comprehension during incremental change", Proceedings of 13th International Workshop on Program Comprehension", pp.149-152, 2005. https://doi.org/10.1109/WPC.2005.22
  16. Gallagher K., Lyle J., "Using Program Slicing in Software Maintenance", IEEE TSE, 17(8), pp.751-761, 1991. https://doi.org/10.1109/32.83912
  17. Ren X., Shah F., Tip F., Ryder B.G., Chesley O., "Chianti: a tool for change impact analysis of java programs", ACM SIGPLAN Notices, 39(10), pp.432-448, 2004. https://doi.org/10.1145/1035292.1029012
  18. Antoniol G., Canfora G., Casazza G., De Lucia A., Merlo E., "Recovering Traceability Links between Code and Documentation", IEEE Transactions on Software Engineering, 2003.
  19. Hayes J.H., Dekhtyar A., Osborne J., "Improving Requirements Tracing via Information Retrieval", Proceedings of the 11th IEEE International Requirements Engineering Conference, Monterey Bay, 2003. https://doi.org/10.1109/ICRE.2003.1232745
  20. Cleland-Huang J., Settimi R., Duan C., Zou X., "Utilizing Supporting Evidence to Improve Dynamic Requirements Traceability", 13th IEEE International Conference on Requirements Engineering, Paris, pp.135-144, 29 Aug.-2 Sept., 2005. https://doi.org/10.1109/RE.2005.78
  21. Yeong-Jae, Yoo, "Development of a Traceability Analysis Method based on Case Grammar for NPP Requirement Documents written in Korean Language", M.S. Thesis, Department of Nuclear and Quantum Engineering, KAIST, 2003.
  22. Canfora G., Cerulo L., "Impact Analysis by Mining Software and Change Request Repositories", Proceedings of 11th International Symposium on Software Metrics, pp.20-29, 2005. https://doi.org/10.1109/METRICS.2005.28
  23. Gall H., Hajek K., Jazayeri M., "Detection of Logical Coupling based on Product Release History", Proceedings of 14th ICSM, pp.190-198, 1998. https://doi.org/10.1109/ICSM.1998.738508
  24. Gall H., Jazayeri M., Krajewski J., "CVS Release History Data for Detecting Logical Coupling", Proceedings of 6th International Workshop on Principles of Software Evolution, pp.13-23, 2003 https://doi.org/10.1109/IWPSE.2003.1231205
  25. Ying A.T., Murphy G.C., Ng R., Chu-Carroll M.C., "Predicting Source Code Change by Mining Change History", IEEE TSE, 31(6), pp.429-445, 2005.
  26. Zimmermann T., Weisserber P., Diehl S., Zeller A., "Mining Version Histories to Guide Software Changes", IEEE TSE, 31(6), pp.429-445, 2005. https://doi.org/10.1109/TSE.2005.72
  27. Kagdi H., Maletic J.I., Sharif B., "Mining Software Repositories for Traceability Links", 15th IEEE International Conference on Program Comprehension (ICPC'07), pp.145-154, 2007. https://doi.org/10.1109/ICPC.2007.28
  28. Gotel O., Finkelstein A., "Contribution Structures", Proceedings of 2nd International Symposium on Requirements Engineering, pp.100-107, 1995.
  29. Sherba S.A., Anderson K.M., Faisal M., "A Framework for Mapping Traceability Relationships", Proceedings of the 2nd International Workshop on Traceability for Emerging Forms of Software Engineering (TEFSE 2003), Montreal, Canada, Sept., 2003.
  30. Cleland-Huang J., Chang C., Wise J., "Supporting Event Based Traceability through High-Level Recognition of Change Events", Proceedings of IEEE COMPSAC Conference, Oxford, England, Aug., 2002.
  31. 김대엽, 윤청, "소프트웨어 형상관리와 작업공간의 통합을 통한 산출물의 추적성 향상 기법", 정보처리학회 논문지, 제16-D권, 제6호, 2009. https://doi.org/10.3745/KIPSTD.2009.16D.6.899
  32. Kim D., Youn C., "Traceability Enhancement Technique through the Integration of Software Configuration Management and Individual Working Environment", Proceedings of IEEE International Conference on Secure Software Integration and Reliability Improvement, pp.163-172, Jun., 2010. https://doi.org/10.1109/SSIRI.2010.27
  33. Berczuk S.P., Appleton B., "Software Configuration Management Patterns, Effective Teamwork, Practical Integration", Addison Wesley, 2002.
  34. Marcus A., Xie X., Poshyvanyk D., "When and How to Visualize Traceability Links?", Proceedings of the 3rd International Workshop on Traceability in Emerging Forms of Software Engineering, pp.56-61, 2005.

Cited by

  1. Traceability Management Technique for Software Artifacts which Comprise Software Release vol.2, pp.7, 2013, https://doi.org/10.3745/KTSDE.2013.2.7.461