Recovering behavioral design models from execution traces is not an easy task due to the sheer size of typical traces. In this paper, we describe a novel technique for achieving this. Our approach is based on filtering traces by distinguishing the utility components from the ones that implement high-level concepts. In the paper, we first define the concept of utilities; then we present an algorithm based on fan-in analysis that can be used for the detection of utilities. To represent the high-level behavioral models, we explore the Use Case Map (UCM) notation, which is a language used to describe and understand emergent behavior of complex and dynamic systems. Finally, we test the validity of our approach on an object-oriented system called TConfig.

-- DanielAmyot - 11 Oct 2005


  • Please feel free to discuss this article directly on this page. Constructive comments are welcomed! Please sign your TWiki name.

FormForVirtualLibrary edit

Title Recovering Behavioral Design Models from Execution Traces
Authors A. Hamou-Lhadj, E. Braun, D. Amyot, and T. Lethbridge
Type Conference
Conference/Journal Title 9th European Conference on Software Maintenance and Reengineering (CSMR)
Publisher IEEE Computer Society
Month March
Year 2005
Pages 112-121
DOI 10.1109/CSMR.2005.46
Keywords Reverse-engineering, Trace filtering, Use Case Maps, Visualization
Topic attachments
I Attachment Action Size Date Who Comment
CSMR05.pdfpdf CSMR05.pdf manage 170 K 11 Oct 2005 - 13:38 DanielAmyot Pre-publication version, CSMR05
Topic revision: r2 - 12 Nov 2009, SaeedBehnam
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback