NobleBlocks

Research indexJournal article

Code patterns for automatically validating requirements-to-code traces

Ghabi, Egyed

2012 Proceedings of the 27th IEEE/ACM International Conference on Automated Software Engineering3 Sep 2012

NobleIDark:/48914/w1/20260515/8025A144DOI10.1145/2351676.2351705

Paywalled

The full text is at the publisher

You can read the abstract here, or open it at the publisher.

Read at the publisher

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.

Discussion

Citations

Topics

More

Suggest a correction or report