정보과학회 논문지 (Journal of KIISE)

  • 제42권3호
  • /
  • Pages.328-340
  • /
  • 2015
  • /
  • 2383-630X(pISSN)
  • /
  • 2383-6296(eISSN)
한국정보과학회 (Korean Institute of Information Scientists and Engineers)
권호 표지
DOI QR코드

DOI QR Code

객체지향 개발에서의 효율적인 변경 관리를 위한 추적성 관리 및 영향 분석 방법

Methodology for Traceability Management and Impact Analysis for Efficient Change Management in Object-Oriented Development

  • 김대엽 (충남대학교 컴퓨터공학과) ;
  • 윤청 (충남대학교 컴퓨터공학과)
  • 투고 : 2014.09.15
  • 심사 : 2015.01.21
  • 발행 : 2015.03.15
⟨ 이전 논문 다음 논문 ⟩

초록

소프트웨어에 대한 고객의 요구사항은 다양한 이유로 인해 지속적으로 변화하며, 그로 인해 소프트웨어 개발 시 변경은 불가피한 작업이다. 요구사항에 대한 변경 요청이 발생하는 경우, 변경의 파급 효과를 정확하게 예측하는 것은 효율적인 변경 관리를 위해 매우 중요하다. 본 논문은 객체지향 개발 시 적용할 수 있는 추적성 정보의 관리 방법과 시스템을 구성하는 각 산출물들의 추적성 정보를 바탕으로 변경의 파급효과를 예측하기 위한 영향 분석 지침을 제시한다. 객체지향 시스템을 구성하는 주요 산출물들에 대해서 추적의 대상이 되는 추적 항목들을 식별하고, 그것들의 연관 관계를 정의한다. 추적 항목들의 연관 관계를 기반으로 변경의 파급 효과를 순방향 및 역방향으로 추적하고, 분석할 수 있는 가이드라인을 제시함으로써, 정확한 변경의 범위를 식별하는 것이 본 논문이 제안하는 방법의 목적이다.

Software requirements are continuously changed for various reasons, consequently changes of software are inevitable. In the case of changes necessitated by changes in requirements, it is necessary to precisely predict the ripple effects of the changes for efficient management of the changes. This paper proposes the management method of traceability information, which can be applied in object-oriented development. Furthermore, we introduce the guidelines for prediction of the ripple effects of changes based on traceability information among artifacts composing a system. We identify traceability items for the essential artifacts which were composed of the object-oriented system, and define relationships among them. The purpose of the method proposed in this paper is to identify the scope of change precisely through the guidelines. These can then be used for tracing and analyzing the impact of the changes both the forward and backward looking, based on the relationships of traceability items.

키워드

참고문헌

  1. Standish Group, "Chaos Reports," 2009.
  2. Standish Group, "Chaos Reports," 2013.
  3. Gotel O. and Finkestein A., "An Analysis of the Requirements Traceability Problem," Proc. of the 1st International Conference on Requirements Engineering, pp. 94-101, 1994.
  4. Antoniol G., et al., "Information Retrieval Models for Recovering Traceability Links between Code and Documentation," Proc. of the International Conference on Software Maintenance, pp. 40-49, 2000.
  5. Antoniol G., et al., "Recovering Traceability Links between Code and Documentation," IEEE Transactions on Software Engineering, Vol. 28, No. 10, pp. 970-983, 2002. https://doi.org/10.1109/TSE.2002.1041053
  6. Canfora G. and Cerulo L., "Impact Analysis by Mining Software and Change Request Repositories," Proc. of 11th International Symposium on Software Metrics, pp. 20-29, 2005.
  7. Gall H., et al., "CVS Release History Data for Detecting Logical Coupling," Proc. of 6th International Workshop on Principles of Software Evolution, pp. 13-23, 2003.
  8. Ying A.T., et al., "Predicting Source Code Change by Mining Change History," IEEE TSE, 31(6), pp. 429-445, 2005.
  9. Kagdi H., et al., "Mining Software Repositories for Traceability Links," 15th IEEE International Conference on Program Comprehension, pp. 145-154, 2007.
  10. CMMI Product Team, Capability Maturity Model Integration(CMMI), SEI, 2002.
  11. IEEE Computer Society SWEBOK Team, Guide to the Software Engineering Body of Knowledge (SWEBOK), IEEE, 2004.
  12. B.J.M. Abma, "Evaluation of requirements management tools with support for traceability-based change impact analysis," Mater's thesis, University of Twente, 2009.
  13. Weigers K., Software Requirements, Redmond: Microsoft Press, 2003.
  14. Cleland-Huang J., et al., "Event-Based Traceability for Managing Evolutionary Change," IEEE Transactions on Software Engineering, Vol. 29, No. 9, pp. 796-810, 2003. https://doi.org/10.1109/TSE.2003.1232285
  15. Egyed A., "A Scenario-Driven Approach to Traceability," 23rd International Conference on Software Engineering, pp. 123-132, 2000.
  16. IEEE Std 610.12-1990, IEEE Standard Glossary of Software Engineering Terminology, 1990.
  17. Filho A.O., "Change Impact Analysis from Business Rules," ICSE'10, 2010.
  18. Bohner S.A., "Software change impacts: An evolving perspective," Proc. 18th ICSM, pp. 263-272, 2002.
  19. Biggerstaff T.J., et al., "Program understanding and the concept assignment problem," Communication of ACM, 37(5), pp. 72-82, 1994. https://doi.org/10.1145/175290.175300
  20. Briand L.C. et al., "Impact Analysis and Change Management of UML Models," Proc. of the International Conference on Software Maintenance, 2003.
  21. Jeong C. S. and Kim S. R., "A Study on Effective Requirement Traceability Management Method in Implementation Project of Information System," Journal of the Korea Society of Computer and Information, Vol. 17, No. 5, 2012.
  22. Bohner S. A. and Arnold R. S., "Software Change Impact Analysis," IEEE Computer Society Press, 1996.
  23. Pirklbauer G., et al., "Improving Change Impact Analysis with a Tight Integrated Process and Tool," 7th International Conference on Information Technology, 2010.

피인용 문헌

  1. Dynamic Impact Analysis Method using Use-case and UML Models on Object-oriented Analysis vol.43, pp.10, 2016, https://doi.org/10.5626/JOK.2016.43.10.1104