Exploiting Traceability Uncertainty between Architectural Models and Code.

Ghabi, Achraf; Egyed, Alexander

doi:10.1109/WICSA-ECSA.212.25

Exploiting Traceability Uncertainty between Architectural Models and Code.

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:

Achraf Ghabi, Alexander Egyed, "Exploiting Traceability Uncertainty between Architectural Models and Code.", pp. 171-180, 2012.

Bibtex Entry:

@Conference{DBLP:conf/wicsa/GhabiE12,
  Title                    = {Exploiting Traceability Uncertainty between Architectural Models and Code.},
  Author                   = {Achraf Ghabi and Alexander Egyed},
  Booktitle                = {Joint 10th Working Conference on Software Architecture \& 6th European Conference on Software Architecture (WICSA/ECSA), Helsinki, Finland},
  Year                     = {2012},
  Pages                    = {171-180},

  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                     = {Exploiting Traceability Uncertainty between Architectural Models and Code:Conferences\\WICSA 2012 - Exploiting Traceability Uncertainty between Architectural Models and Code\\Exploiting Traceability Uncertainty between Architectural Models and Code.pdf:PDF},
  Keywords                 = {traceability, FWF P23115-N23}
}