Browse > Article
http://dx.doi.org/10.3745/KTSDE.2013.2.7.461

Traceability Management Technique for Software Artifacts which Comprise Software Release  

Kim, Dae Yeob (충남대학교 컴퓨터공학과)
Youn, Cheong (충남대학교 컴퓨터공학과)
Publication Information
KIPS Transactions on Software and Data Engineering / v.2, no.7, 2013 , pp. 461-470 More about this Journal
Abstract
The capacity for tracing relationships among various artifacts which are created at each phase of software system development is essential for software quality management. Software release refers to delivering a set of newly created or changed artifacts to customers. The relationships among artifacts which comprise software release must be traced so that the work for customer's requirement of change and functional enhancement is effectively established. And release management can be effectively realized through the integration of configuration management and change management. This paper proposes the technique for supporting change management of artifacts and for tracing relationships of artifacts which comprise software release through the integrated environment of personal workspace and configuration management system. In the proposed environment, the visualized version graph and automated tagging function are used for tracing relationships of artifacts.
Keywords
Release; Traceability; Baselined Document; Configuration Management; Version Control;
Citations & Related Records
Times Cited By KSCI : 1  (Citation Analysis)
연도 인용수 순위
1 K. Pohl, "PRO-ART: Enabling Requirements Pre-Traceability", Proceedings of the 2nd IEEE International Conference on Requirements Engineering, 1996.
2 J. Cleland-Huang, D. Schmelzer, "Dynamic Tracing Non-Functional Requirements through Design Pattern Invariants", Proceedings of the 2nd International Workshop on Traceability in Emerging Forms of Software Engineering, Canada, Oct., 2003.
3 J. Cleland-Huang, C. K. Chang, G. Sethi, K. Javvaji , H. Hu, J. Xia, "Automatic Speculative Queries through Event-based Requirement Traceability", Proceedings of the IEEE Joint International Requirements Engineering Conference, Germany, Sept., 2002.
4 A. Egyed, P. Gruenbacher, "Automatic Requirements Traceability: Beyond the Record and Replay Paradigm", Proceedings of the 17th IEEE International Conference on Automated Software Engineering, Edinburgh, UK, Sept., 2002.
5 X. Song, B. Hasling, G. Mangla, B. Sherman, "Lessons Learned from Building a Web-Based Requirements Tracing System", Proceedings of 3rd International Conference on Requirements Engineering, pp.41-50, 1998.
6 G. A. Stout, "Requirements Traceability and the Effect on the System Development Lifecycle(SDLC)", http://www.reveregroup.com/articles/137_005-RevereThoughtLeadership.pdf
7 B. Ramesh, M. Jarke, "Toward Reference Models for Requirements Traceability", IEEE Transactions on Software Engineering, 27(1), Jan., 2001.
8 O. Gotel, A. Finkelstein, "An Analysis of the Requirements Traceability Problem", Proceedings of the 1st International Conference in Requirements Engineering, pp.94-101, 1994.
9 H. Kagdi, I. M. Jonathan, S. Bonita, "Mining Software Repositories for Traceability Links", 15th IEEE International Conference on Program Comprehension, 2007.
10 H. Kagdi, S. Yusuf, J. I. Maletic, "Mining Sequences of Changed-files from Version Histories", in Proceedings of 3rd International Workshop on Mining Software Repositories, pp. 47-53, Shanghai, China, May, 2006.
11 T. Zimmermann, A. Zeller, Weibgerber P., Diehl S., "Mining Version Histories to Guide Software Changes", IEEE Transactions on Software Engineering, Vol.31, No.6, pp. 429-445, 2005.   DOI   ScienceOn
12 D. Y. Kim, C. Youn, "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.
13 S. Sundaram, J. H. Hayes, A. Dekhtyar, "Baselines in Requirements Tracing", in Proceedings of Workshop on Predictive Models of Software Engineering, pp.12-17, St. Louis, May, 2005.
14 S. Harvey, C. Parvathi, J. R. Daniel, S. Mahadevan, "Discovering Dynamic Developer Relationships from Software Version Histories by Time Series Segmentation", 23rd IEEE International Conference on Software Maintenance, pp.415-424, Paris, Oct., 2007.
15 G. Harald, J. Mehdi, K. Jacek, "CVS Release History Data for Detecting Logical Coupling", in Proceedings of the 6th IEEE International Workshop on Principles of Software Evolution", 2002.
16 D. Y. Kim, C. Youn, "Traceability Enhancement Technique for Dependency Relations of Software Artifacts based on the Integration of Software Configuration Management System and Personal Workspace", The KIPS Transactions, Vol. 18-D, No.6, 2011.   과학기술학회마을   DOI   ScienceOn
17 R. Conradi, B. Westfechtel, "Version Models for Software Configuration Management", ACM Computing Surveys, Vol. 30, No.2, June, 1998.
18 Office of Government Commerce, ITIL Service Operation, The Stationary Office, UK, 2007.
19 ISO/IEC 20000-1, Information technology-Service management-Part 1: Specification
20 TTA.KO-10.0256, "Guideline for Configuration and Change Management of Information Systems", 2007.
21 K. Mohan., P. Xu and B. Ramesh, "Improving the Change Management Process", Communications of the ACM, Vol.51, No.5, pp.59-64, May, 2008.
22 Y. J. 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.
23 G. Antoniol, G. Canfora, G. Casazza, A. De Lucia, E. Merlo, "Recovering Traceability Links between Code and Documentation", IEEE Transactions on Software Engineering, 2003.
24 J. H. Hayes, A. Dekhtyar, J. Osborne, "Improving Requirements Tracing via Information Retrieval", Proceedings of the 11th IEEE International Requirements Engineering Conference, Monterey Bay, 2003.
25 J. Cleland-Huang, R. Settimi, C. Duan, X. Zou, "Utilizing Supporting Evidence to Improve Dynamic Requirements Traceability", 13th IEEE International Conference on Requirements Engineering, Paris, pp.135-144, 29 Aug.-2 Sept., 2005.
26 G. Canfora, L. Cerulo, "Impact Analysis by Mining Software and Change Request Repositories", Proceedings of 11th International Symposium on Software Metrics, pp.20-29, 2005.
27 H. Gall, K. Hajek, M. Jazayeri, "Detection of Logical Coupling based on Product Release History", Proceedings of 14th ICSM, pp.190-198, 1998.
28 H. Gall, M. Jazayeri, J. Krajewski, "CVS Release History Data for Detecting Logical Coupling", Proceedings of 6th International Workshop on Principles of Software Evolution, pp.13-23, 2003
29 A. T. Ying, G. C. Murphy, R. Ng, M. C. Chu-Carroll , "Predicting Source Code Change by Mining Change History", IEEE TSE, 31(6), pp.429-445, 2005.
30 T. Zimmermann, P. Weisserber, S. Diehl, A. Zeller, "Mining Version Histories to Guide Software Changes", IEEE TSE, 31(6), pp.429-445, 2005.
31 H. Kagdi, J. I. Maletic., B. Sharif., "Mining Software Repositories for Traceability Links", 15th IEEE International Conference on Program Comprehension (ICPC'07), pp. 145-154, 2007.
32 T. Fatma, "Evaluating Software Configuration Management Tools for Opticon Sensors Europe B.V.", Masters Thesis Software Engineering, 25 June, 2004.
33 http://www.processdox.com/, "Configuration, Change and Release Management Policies and Procedures Guide"
34 A. Marcus, X. Xie, D. Poshyvanyk, "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.