Observations on the connectedness between requirements-to-code traces and calling relationships for trace validation. (bibtex)
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, the handling of traces is highly error prone, in part due to the informal nature of requirements. This paper discusses observations on the connectedness between requirements-to-code traces and calling relationships within the source code. These observations are based on the empirical evaluation of four case study systems covering 150 KLOC and 59 sample requirements. We found that certain patterns of connectedness have high or low likelihoods of occurring. These patterns can thus be used to confirm or reject existing traceability - hence they are useful for validating requirements-to-code traces.
Reference:
Observations on the connectedness between requirements-to-code traces and calling relationships for trace validation. (Achraf Ghabi, Alexander Egyed), In Proceedings of the 26th International Conference on Automated Software Engineering (ASE 2011), Lawrence, USA (Perry Alexander, Corina S. Pasareanu, John G. Hosking, eds.), IEEE Computer Society, 2011.
Bibtex Entry:
@Conference{DBLP:conf/kbse/GhabiE11,
  author    = {Achraf Ghabi and Alexander Egyed},
  title     = {Observations on the connectedness between requirements-to-code traces and calling relationships for trace validation.},
  booktitle = {Proceedings of the 26th International Conference on Automated Software Engineering (ASE 2011), Lawrence, USA},
  year      = {2011},
  editor    = {Perry Alexander and Corina S. Pasareanu and John G. Hosking},
  pages     = {416-419},
  publisher = {IEEE Computer Society},
  abstract  = {Traces between requirements and code reveal where requirements are
	implemented. Such traces are essential for code understanding and
	change management. Unfortunately, the handling of traces is highly
	error prone, in part due to the informal nature of requirements.
	This paper discusses observations on the connectedness between requirements-to-code
	traces and calling relationships within the source code. These observations
	are based on the empirical evaluation of four case study systems
	covering 150 KLOC and 59 sample requirements. We found that certain
	patterns of connectedness have high or low likelihoods of occurring.
	These patterns can thus be used to confirm or reject existing traceability
	- hence they are useful for validating requirements-to-code traces.},
  doi       = {10.1109/ASE.2011.6100087},
  file      = {:Conferences\\ASE 2011 - Observations on the Connectedness between Requirements-to-Code Traces and Calling Relationships\\Observations on the Connectedness between Traces and Calling Relationships-preprint.pdf:PDF},
  keywords  = {FWF P23115},
}
Powered by bibtexbrowser