A Scenario-Driven Approach to Traceability.

Egyed, Alexander

A Scenario-Driven Approach to Traceability.

by Alexander Egyed

Abstract:

Design traceability has been widely recognized as being an integral aspect of software development. In the past years this fact has been amplified due to the increased use of legacy systems and COTS (commercial-off-the-shelf) components mixed with the growing use of elaborate â€œupstreamâ€� software modeling techniques such as the Unified Modeling Language (UML). The more intensive emphasis on upstream (non-programming) software development issues has, however, widened the gap between software components (e.g., subsystems, modules) and software models (e.g., class diagrams, data flow diagrams), creating the need for a better understanding of the intricacies and interrelationships between the two. This paper demonstrates how observable run-time information of software systems can be used to detect traceability information between software systems and their models. We do this by employing a technique that evaluates the â€œfootprintsâ€� that usage scenarios (e.g., test cases) make during the execution of software systems. Those footprints can be compared, resulting in additional traceability information among modeling elements associated with those scenarios. Our approach is tool supported.

View PDF

Reference:

Alexander Egyed, "A Scenario-Driven Approach to Traceability.", pp. 123-132, 2001.

Bibtex Entry:

@Conference{DBLP:conf/icse/Egyed01,
  Title                    = {A Scenario-Driven Approach to Traceability.},
  Author                   = {Alexander Egyed},
  Booktitle                = {23rd International Conference on Software Engineering (ICSE), Toronto, Canada},
  Year                     = {2001},
  Pages                    = {123-132},

  Abstract                 = {Design traceability has been widely recognized as being an integral aspect of software development. In the past years this fact has been amplified due to the increased use of legacy systems and COTS (commercial-off-the-shelf) components mixed with the growing use of elaborate â€œupstreamâ€� software modeling techniques such as the Unified Modeling Language (UML). The more intensive emphasis on upstream (non-programming) software development issues has, however, widened the gap between software components (e.g., subsystems, modules) and software models (e.g., class diagrams, data flow diagrams), creating the need for a better understanding of the intricacies and interrelationships between the two. This paper demonstrates how observable run-time information of software systems can be used to detect traceability information between software systems and their models. We do this by employing a technique that evaluates the â€œfootprintsâ€� that usage scenarios (e.g., test cases) make during the execution of software systems. Those footprints can be compared, resulting in additional traceability information among modeling elements associated with those scenarios. Our approach is tool supported.},
  File                     = {A Scenario-Driven Approach to Traceability:Conferences\\ICSE 2001 - A Scenario-Driven Approach to Traceability\\A Scenario-Driven Approach to Traceability.pdf:PDF},
  Keywords                 = {traceability, testing},
  Url                      = {http://doi.ieeecomputersociety.org/10.1109/ICSE.2001.919087}
}