Alexander Egyed

 (Research, Teaching, Tools, and Publications)

 
   
   
         
  Software Model Traceability

   Johannes Kepler University

   Altenbergerstr. 69, 4040 Linz, Austria

   http://www.sea.uni-linz.ac.at

  

XXXXXXXXXXXXXXXXXXXXXXX  
 
 
 

 

     
 

related research: Incremental Transformation and Analysis
related research:
Model Consistency Checking
related research:
Product Families and Product Lines
related research:
Refinement from Software Requirements to Architecture
related research:
Architecture and Design Recovery (reverse engineering)


Software traceability

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 both of them. Recently, we developed a new approach towards design and architecture traceability by observing run-time information of software systems that 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.

Relevant Publications

·         Tailoring Software Traceability to Value-Based Needs

·         A Scenario-Driven Approach to Trace Dependency Analysis

·         Resolving Uncertainties during Trace Analysis

·         Automated Requirements Traceability - Beyond the Record and Replay Paradigm

·         Identifying Requirements Conflicts and Cooperation

·         Towards Understanding Implications of Trace Dependencies among Quality Requirements

·         Reasoning about Trace Dependencies in a Multi-Dimensional Space

·         A Scenario-Driven Approach to Traceability

·         Supporting Software Understanding with Automated Requirements Traceability

Relevant Tools

·         Trace/Analyzer Tool

Relevant Related Events

·         TEFSE

 
     

Copyright © 1999-2008 Alexander Egyed

 

 

pages have been viewed since January 2006

 

   

This page was last updated 01/12/2006