Code patterns for automatically validating requirements-to-code traces.

Ghabi, Achraf; Egyed, Alexander

doi:10.1145/2351676.2351705

Code patterns for automatically validating requirements-to-code traces.

by Achraf Ghabi, Alexander Egyed

Abstract:

Traces between requirements and code reveal where requirements are implemented. Such traces are essential for code understanding and change management. Unfortunately, traces are known to be error prone. This paper introduces a novel approach for validating requirements-to-code traces through calling relationships within the code. As input, the approach requires an executable system, the corresponding requirements, and the requirements-to-code traces that need validating. As output, the approach identifies likely incorrect or missing traces by investigating patterns of traces with calling relationships. The empirical evaluation of four case study systems covering 150 KLOC and 59 requirements demonstrates that the approach detects most errors with 85-95% precision and 82-96% recall and is able to handle traces of varying levels of correctness and completeness. The approach is fully automated, tool supported, and scalable.

Reference:

Achraf Ghabi, Alexander Egyed, "Code patterns for automatically validating requirements-to-code traces.", pp. 200-209, 2012.

Bibtex Entry:

@Conference{DBLP:conf/kbse/GhabiE12,
  Title                    = {Code patterns for automatically validating requirements-to-code traces.},
  Author                   = {Achraf Ghabi and Alexander Egyed},
  Booktitle                = {27th International Conference on Automated Software Engineering (ASE), Essen, Germany},
  Year                     = {2012},
  Pages                    = {200-209},

  Abstract                 = {Traces between requirements and code reveal where requirements are implemented. Such traces are essential for code understanding and change management. Unfortunately, traces are known to be error prone. This paper introduces a novel approach for validating requirements-to-code traces through calling relationships within the code. As input, the approach requires an executable system, the corresponding requirements, and the requirements-to-code traces that need validating. As output, the approach identifies likely incorrect or missing traces by investigating patterns of traces with calling relationships. The empirical evaluation of four case study systems covering 150 KLOC and 59 requirements demonstrates that the approach detects most errors with 85-95% precision and 82-96% recall and is able to handle traces of varying levels of correctness and completeness. The approach is fully automated, tool supported, and scalable.},
  Doi                      = {10.1145/2351676.2351705},
  File                     = {Code Patterns for Automatically Validating Requirements-to-Code Traces:Conferences\\ASE 2012 - Code Patterns for Automatically Validating Requirements-to-Code Traces\\Code Patterns for Automatically Validating Requirements-to-Code Traces.pdf:PDF},
  Keywords                 = {requirements, traceability, FWF P23115-N23}
}