You are required to read and agree to the below before accessing a full-text version of an article in the IDE article repository.

The full-text document you are about to access is subject to national and international copyright laws. In most cases (but not necessarily all) the consequence is that personal use is allowed given that the copyright owner is duly acknowledged and respected. All other use (typically) require an explicit permission (often in writing) by the copyright owner.

For the reports in this repository we specifically note that

  • the use of articles under IEEE copyright is governed by the IEEE copyright policy (available at http://www.ieee.org/web/publications/rights/copyrightpolicy.html)
  • the use of articles under ACM copyright is governed by the ACM copyright policy (available at http://www.acm.org/pubs/copyright_policy/)
  • technical reports and other articles issued by M‰lardalen University is free for personal use. For other use, the explicit consent of the authors is required
  • in other cases, please contact the copyright owner for detailed information

By accepting I agree to acknowledge and respect the rights of the copyright owner of the document I am about to access.

If you are in doubt, feel free to contact webmaster@ide.mdh.se

Is Requirements Similarity a Good Proxy for Software Similarity? An Empirical Investigation in Industry


Fulltext:


Publication Type:

Conference/Workshop Paper

Venue:

Requirements Engineering: Foundation for Software Quality

Publisher:

Springer International Publishing

DOI:

10.1007/978-3-030-73128-1_1


Abstract

[Context and Motivation] Content-based recommender systems for requirements are typically built on the assumption that similar requirements can be used as proxies to retrieve similar software. When a new requirement is proposed by a stakeholder, natural language processing (NLP)-based similarity metrics can be exploited to retrieve existing requirements, and in turn, identify previously developed code. [Question/problem] Several NLP approaches for similarity computation are available, and there is little empirical evidence on the adoption of an effective technique in recommender systems specifically oriented to requirements-based code reuse. [Principal ideas/results] This study compares different state-of-the-art NLP approaches and correlates the similarity among requirements with the similarity of their source code. The evaluation is conducted on real-world requirements from two industrial projects in the railway domain. Results show that requirements similarity computed with the traditional tf-idf approach has the highest correlation with the actual software similarity in the considered context. Furthermore, results indicate a moderate positive correlation with Spearman's rank correlation coefficient of more than 0.5. [Contribution] Our work is among the first ones to explore the relationship between requirements similarity and software similarity. In addition, we also identify a suitable approach for computing requirements similarity that reflects software similarity well in an industrial context. This can be useful not only in recommender systems but also in other requirements engineering tasks in which similarity computation is relevant, such as tracing and categorization.

Bibtex

@inproceedings{Abbas6142,
author = {Muhammad Abbas and Alessio Ferrari and Anas Shatnawi and Eduard Paul Enoiu and Mehrdad Saadatmand},
title = {Is Requirements Similarity a Good Proxy for Software Similarity? An Empirical Investigation in Industry},
isbn = {978-3-030-73128-1},
editor = {Dalpiaz, Fabiano and Spoletini, Paola},
pages = {3--18},
month = {April},
year = {2021},
booktitle = {Requirements Engineering: Foundation for Software Quality},
publisher = {Springer International Publishing},
url = {http://www.es.mdu.se/publications/6142-}
}