A Scenario-Driven Approach to Trace Dependency Analysis.

Egyed, Alexander

A Scenario-Driven Approach to Trace Dependency Analysis.

by Alexander Egyed

Abstract:

Software development artifactsâ€”such as model descriptions, diagrammatic languages, abstract (formal) specifications, and source codeâ€”are highly interrelated where changes in some of them affect others. Trace dependencies characterize such relationships abstractly. This paper presents an automated approach to generating and validating trace dependencies. It addresses the severe problem that the absence of trace information or the uncertainty of its correctness limits the usefulness of software models during software development. It also automates what is normally a time consuming and costly activity due to the quadratic explosion of potential trace dependencies between development artifacts.

View PDF

Reference:

Alexander Egyed, "A Scenario-Driven Approach to Trace Dependency Analysis.", In IEEE Transactions on Software Engineering, vol. 29, no. 2, pp. 116-132, 2003.

Bibtex Entry:

@Article{dblp:journals/tse/Egyed03,
  Title                    = {A Scenario-Driven Approach to Trace Dependency Analysis.},
  Author                   = {Alexander Egyed},
  Journal                  = {IEEE Transactions on Software Engineering},
  Year                     = {2003},
  Number                   = {2},
  Pages                    = {116-132},
  Volume                   = {29},

  Abstract                 = {Software development artifactsâ€”such as model descriptions, diagrammatic languages, abstract (formal) specifications, and source codeâ€”are highly interrelated where changes in some of them affect others. Trace dependencies characterize such relationships abstractly. This paper presents an automated approach to generating and validating trace dependencies. It addresses the severe problem that the absence of trace information or the uncertainty of its correctness limits the usefulness of software models during software development. It also automates what is normally a time consuming and costly activity due to the quadratic explosion of potential trace dependencies between development artifacts.},
  File                     = {A Scenario-Driven Approach to Trace Dependency Analysis:Journals\\TSE 2003 - A Scenario-Driven Approach to Trace Dependency Analysis\\A Scenario-Driven Approach to Trace Dependency Analysis.pdf:PDF},
  Keywords                 = {traceability},
  Url                      = {http://doi.ieeecomputersociety.org/10.1109/TSE.2003.1178051}
}