Page 46 - 《软件学报》2025年第5期

1946 软件学报 2025 年第 36 卷第 5 期

[21] Rath M, Lo D, Mäder P. Analyzing requirements and traceability information to improve bug localization. In: Proc. of the 15th Int’l Conf.
on Mining Software Repositories. Gothenburg: ACM, 2018. 442–453. [doi: 10.1145/3196398.3196415]
[22] Parizi RM, Lee SP, Dabbagh M. Achievements and challenges in state-of-the-art software traceability between test and code artifacts.
IEEE Trans. on Reliability, 2014, 63(4): 913–926. [doi: 10.1109/tr.2014.2338254]
[23] Ali NB, Petersen K. A consolidated process for software process simulation: State of the art and industry experience. In: Proc. of the 38th
Euromicro Conf. on Software Engineering and Advanced Applications. Cesme: IEEE, 2012. 327–336. [doi: 10.1109/seaa.2012.69]
[24] Li Y, Zhang H, Dong LM, Liu BH, Ma JY. Constructing a hybrid software process simulation model in practice: An exemplar from
industry. In: Proc. of the 2020 Int’l Conf. on Software and System Processes. Seoul: ACM, 2020. 135–144. [doi: 10.1145/3379177.
3388906]
[25] Chen XF, Grundy J. Improving automated documentation to code traceability by combining retrieval techniques. In: Proc. of the 26th
IEEE/ACM Int’l Conf. on Automated Software Engineering. Lawrence: IEEE, 2011. 223–232. [doi: 10.1109/ase.2011.6100057]
[26] Winkler S, Von Pilgrim J. A survey of traceability in requirements engineering and model-driven development. Software & Systems
Modeling, 2010, 9(4): 529–565. [doi: 10.1007/s10270-009-0145-0]
[27] Rath M, Mäder P. The SEOSS 33 dataset——Requirements, bug reports, code history, and trace links for entire projects. Data in Brief,
2019, 25: 104005. [doi: 10.1016/j.dib.2019.104005]
[28] Egyed A, Graf F, Grünbacher P. Effort and quality of recovering requirements-to-code traces: Two exploratory experiments. In: Proc. of
the 18th IEEE Int’l Requirements Engineering Conf. Sydney: IEEE, 2010. 221–230. [doi: 10.1109/re.2010.34]
[29] Borg M, Runeson P, Ardö A. Recovering from a decade: A systematic mapping of information retrieval approaches to software
traceability. Empirical Software Engineering, 2014, 19(6): 1565–1616. [doi: 10.1007/s10664-013-9255-y]
[30] Corallo A, Latino ME, Menegoli M, Pontrandolfo P. A systematic literature review to explore traceability and lifecycle relationship. Int’l
Journal of Production Research, 2020, 58(15): 4789–4807. [doi: 10.1080/00207543.2020.1771455]
[31] Zogaan W, Sharma P, Mirahkorli M, Arnaoudova V. Datasets from fifteen years of automated requirements traceability research: Current
state, characteristics, and quality. In: Proc. of the 25th IEEE Int’l Requirements Engineering Conf. Lisbon: IEEE, 2017. 110–121. [doi: 10.
1109/re.2017.80]
[32] Aung TWW, Huo H, Sui YL. A literature review of automatic traceability links recovery for software change impact analysis. In: Proc. of
the 28th Int’l Conf. on Program Comprehension. Seoul: ACM, 2020. 14–24. [doi: 10.1145/3387904.3389251]
[33] Antoniol G, Canfora G, De Lucia A, Merlo E. Recovering code to documentation links in OO systems. In: Proc. of the 6th Working Conf.
on Reverse Engineering. Atlanta: IEEE, 1999. 136–144. [doi: 10.1109/wcre.1999.806954]
[34] Zhai YP, Hong M, Yang QH. Research on traceability of functional requirements to test case. Computer Science, 2017, 44(11A):
480–484 (in Chinese with English abstract).
[35] Antoniol G, Canfora G, Casazza G, De Lucia A, Merlo E. Recovering traceability links between code and documentation. IEEE Trans. on
Software Engineering, 2002, 28(10): 970–983. [doi: 10.1109/tse.2002.1041053]
[36] Marcus A, Maletic JI, Sergeyev A. Recovery of traceability links between software documentation and source code. Int’l Journal of
Software Engineering and Knowledge Engineering, 2005, 15(5): 811–836. [doi: 10.1142/S0218194005002543]
[37] Asuncion HU, Asuncion AU, Taylor RN. Software traceability with topic modeling. In: Proc. of the 32nd ACM/IEEE Int’l Conf. on
Software Engineering. Cape Town: ACM, 2010. 95–104. [doi: 10.1145/1806799.1806817]
[38] Abadi A, Nisenson M, Simionovici Y. A traceability technique for specifications. In: Proc. of the 16th IEEE Int’l Conf. on Program
Comprehension. Amsterdam: IEEE, 2008. 103–112. [doi: 10.1109/icpc.2008.30]
[39] Cleland-Huang J, Czauderna A, Gibiec M, Emenecker J. A machine learning approach for tracing regulatory codes to product specific
requirements. In: Proc. of the 32nd ACM/IEEE Int’l Conf. on Software Engineering. Cape Town: ACM, 2010. 155–164. [doi: 10.1145/
1806799.1806825]
[40] Lin JF, Liu YL, Zeng QK, Jiang M, Cleland-Huang J. Traceability transformed: Generating more accurate links with pre-trained BERT
models. In: Proc. of the 43rd IEEE/ACM Int’l Conf. on Software Engineering. Madrid: IEEE, 2021. 324–335. [doi: 10.1109/icse43902.
2021.00040]
[41] Ruan H, Chen BH, Peng X, Zhao WY. DEEPLINK: Recovering issue-commit links based on deep learning. Journal of Systems and
Software, 2019, 158: 110406. [doi: 10.1016/J.JSS.2019.110406]
[42] Hammoudi M, Mayr-Dorn C, Mashkoor A, Egyed A. A traceability dataset for open source systems. In: Proc. of the 18th IEEE/ACM Int’l
Conf. on Mining Software Repositories. Madrid: IEEE, 2021. 555–559. [doi: 10.1109/msr52588.2021.00073]
[43] Maro S, Staron M, Steghöfer JP. Challenges of establishing traceability in the automotive domain. In: Proc. of the 9th Int’l Conf. on
Software Quality. Vienna: Springer, 2017. 153–172. [doi: 10.1007/978-3-319-49421-0_11]