Analisis Dampak Perubahan Artefak Kebutuhan Berdasarkan Kedekatan Semantik Pada Pengembangan XP

Arrijal Nagara Yanottama; Siti Rochimah

doi:10.29207/resti.v5i4.3281

Arrijal Nagara Yanottama Universitas Negeri Malang
Siti Rochimah Teknik Informatika, Fakultas Teknologi Elektro dan Informatika Cerdas , Institut Teknologi Sepuluh Nopember

DOI: https://doi.org/10.29207/resti.v5i4.3281

Keywords: XP, traceability link, TF-IDF, semantic proximity, natural language processing

Abstract

The Extreme Programming (XP) development method is popular because of the flexibility of the development process, it can accommodate changes quickly. But this method has a weakness in terms of documentation. It is expected that the speed of discovering which parts of the source code need to be changed will be greatly improved by analyzing the impact of changes on the requirements document. In this study, a method of analyzing the impact of changes is proposed by tracing changes in the artifact of the need to find out the source code that occurs. Early language methods and semantic approaches are used. Based on the proximity of the semantics, it will be analyzed to find out the elements in the source code that use the Spearman Correlation Coefficient. The test dataset in this study consisted of the source code in the PHP programming language as well as the functional requirements of the software. Requirements change list is generated by analysis of the latest 2 (two) expert versions of the source code. The changing needs are described in a user story document. Based on the test results in this study, the average precision was 0.1725 and the average recall value was 0.6041.

Downloads

Download data is not yet available.

References

M. Yasvi, K. Yadav, and Sahendrasingh. S., “Review On Extreme Programming-XP,” Int. Conf. Robot. Smart Technol. Electron. Eng. Delhi, no. April, pp. 1–8, 2019, [Online]. Available: https://www.researchgate.net/publication/332465869.

J. Cleland-Huang, O. C. Z. Gotel, J. H. Hayes, P. Mäder, and A. Zisman, “Software traceability: Trends and future directions,” Futur. Softw. Eng. FOSE 2014 - Proc., pp. 55–69, 2014, doi: 10.1145/2593882.2593891.

B. Ramesh and M. Jarke, “Toward Reference Models for Requirements Traceability,” Softw. Eng. IEEE Trans., vol. 27, pp. 58–93, Feb. 2001, doi: 10.1109/32.895989.

R. S. Arnold, Software Change Impact Analysis. Washington, DC, USA: IEEE Computer Society Press, 1996.

O. Gotel et al., “The quest for Ubiquity: A roadmap for software and systems traceability research,” in 2012 20th IEEE International Requirements Engineering Conference (RE), 2012, pp. 71–80, doi: 10.1109/RE.2012.6345841.

M. A. Javed and U. Zdun, “A systematic literature review of traceability approaches between software architecture and source code,” ACM Int. Conf. Proceeding Ser., 2014, doi: 10.1145/2601248.2601278.

E. Bouillon, P. Mäder, and I. Philippow, “A Survey on Usage Scenarios for Requirements Traceability in Practice BT - Requirements Engineering: Foundation for Software Quality,” 2013, pp. 158–173, doi: 10.1007/978-3-642-37422-7_12

M. Grechanik, K. S. McKinley, and D. E. Perry, “Recovering and using use-case-diagram-to-source-code traceability links,” 6th Jt. Meet. Eur. Softw. Eng. Conf. ACM SIGSOFT Symp. Found. Softw. Eng. ESEC/FSE 2007, pp. 95–104, 2007, doi: 10.1145/1287624.1287640.

M. Shahid and S. Ibrahim, “Change impact analysis with a software traceability approach to support software maintenance,” in 2016 13th International Bhurban Conference on Applied Sciences and Technology (IBCAST), 2016, pp. 391–396, doi: 10.1109/IBCAST.2016.7429908.

A. von Knethen and M. Grund, “QuaTrace: a tool environment for (semi-) automatic impact analysis based on traces,” in International Conference on Software Maintenance, 2003. ICSM 2003. Proceedings., 2003, pp. 246–255, doi: 10.1109/ICSM.2003.1235427.

M. Hammad, M. L. Collard, and J. I. Maletic, “Automatically identifying changes that impact code-to-design traceability during evolution,” Softw. Qual. J., vol. 19, no. 1, pp. 35–64, 2011, doi: 10.1007/s11219-010-9103-x.

A. De Lucia, F. Fasano, R. Oliveto, and G. Tortora, “Recovering traceability links in software artifact management systems using information retrieval methods,” ACM Trans. Softw. Eng. Methodol., vol. 16, no. 4, 2007, doi: 10.1145/1276933.1276934.

H. Schwarz, J. Ebert, and A. Winter, “Graph-based traceability: A comprehensive approach,” Softw. Syst. Model., vol. 9, no. 4, pp. 473–492, 2010, doi: 10.1007/s10270-009-0141-4.

A. Keller and S. Demeyer, “Change impact analysis for UML model maintenance,” Emerg. Technol. Evol. Maint. Softw. Model., pp. 32–56, Jan. 2011, doi: 10.4018/978-1-61350-438-3.ch002.

D. Kchaou, N. Bouassida, M. Mefteh, and H. Ben-Abdallah, “Recovering semantic traceability between requirements and design for change impact analysis,” Innov. Syst. Softw. Eng., vol. 15, no. 2, pp. 101–115, 2019, doi: 10.1007/s11334-019-00330-w.