Exploiting Traceability Uncertainty between Architectural Models and Code. (bibtex)
by Achraf Ghabi, Alexander Egyed
Abstract:
Documenting and maintaining the traceability between architectural models and code is one of the foremost challenges of model-based software development. Yet, traceability is rarely captured immediately while models and code co-evolve but usually recovered later. By then key people may have moved on or their recollection of facts may be blurred or inconsistent. In previous work, we proposed a language for capturing traceability that allows for uncertainty and incompleteness. This paper investigates this language on the unique properties that characterize model-to-code traceability. Our approach takes ambiguous, incomplete, and possibly incorrect assumptions about the traceability between model and code as input. It then validates the correctness of these assumptions and completes the input by inserting their logical consequences. This paper demonstrates the correctness and scalability of our approach which has been validated on several third-party software systems. Our approach is automated and fully tool supported.
Reference:
Exploiting Traceability Uncertainty between Architectural Models and Code. (Achraf Ghabi, Alexander Egyed), In Proceedings of the Joint 10th Working Conference on Software Architecture & 6th European Conference on Software Architecture (WICSA/ECSA 2012), Helsinki, Finland, IEEE, 2012.
Bibtex Entry:
@Conference{DBLP:conf/wicsa/GhabiE12,
  author    = {Achraf Ghabi and Alexander Egyed},
  title     = {Exploiting Traceability Uncertainty between Architectural Models and Code.},
  booktitle = {Proceedings of the Joint 10th Working Conference on Software Architecture \& 6th European Conference on Software Architecture (WICSA/ECSA 2012), Helsinki, Finland},
  year      = {2012},
  pages     = {171-180},
  publisher = {IEEE},
  abstract  = {Documenting and maintaining the traceability between architectural
	models and code is one of the foremost challenges of model-based
	software development. Yet, traceability is rarely captured immediately
	while models and code co-evolve but usually recovered later. By then
	key people may have moved on or their recollection of facts may be
	blurred or inconsistent. In previous work, we proposed a language
	for capturing traceability that allows for uncertainty and incompleteness.
	This paper investigates this language on the unique properties that
	characterize model-to-code traceability. Our approach takes ambiguous,
	incomplete, and possibly incorrect assumptions about the traceability
	between model and code as input. It then validates the correctness
	of these assumptions and completes the input by inserting their logical
	consequences. This paper demonstrates the correctness and scalability
	of our approach which has been validated on several third-party software
	systems. Our approach is automated and fully tool supported.},
  doi       = {10.1109/WICSA-ECSA.212.25},
  file      = {:Conferences\\WICSA 2012 - Exploiting Traceability Uncertainty between Architectural Models and Code\\Exploiting Traceability Uncertainty between Architectural Models and Code-preprint.pdf:PDF},
  keywords  = {FWF P23115},
}
Powered by bibtexbrowser