Conference on Software Maintenance and Reengineering (CSMR'06) 2006
DOI: 10.1109/csmr.2006.45
|View full text |Cite
|
Sign up to set email alerts
|

Regaining lost knowledge through dynamic analysis and aspect orientation $an industrial experience report

Abstract: This paper describes our experiences of applying dynamic analysis solutions on an industrial legacy application written in C, with the help of Aspect Orientation (AO).We use a number of dynamic analysis techniques that can help in alleviating the problem of (1)

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
17
0

Year Published

2006
2006
2012
2012

Publication Types

Select...
4
2

Relationship

1
5

Authors

Journals

citations
Cited by 16 publications
(17 citation statements)
references
References 20 publications
0
17
0
Order By: Relevance
“…3 Aspicere, an AOP language and tool for legacy C systems This section presents our aspect language for C, Aspicere 11 [87]. We consider its rationale, the language itself and the weaver we have developed for it.…”
Section: Discussionmentioning
confidence: 99%
“…3 Aspicere, an AOP language and tool for legacy C systems This section presents our aspect language for C, Aspicere 11 [87]. We consider its rationale, the language itself and the weaver we have developed for it.…”
Section: Discussionmentioning
confidence: 99%
“…• box (a) is cohesive as ≥ 50% of the contained procedures originate from one module • box (b) is fully cohesive as all contained procedures originate from the same module • box (c) is non-cohesive as < 50% of the contained procedures originate from one module This schema allowed us to not only quickly audit the system's structure, but also gain insight in wrapper-like solutions and procedures implementing low-level functionality [11]. …”
Section: Frequency Of Execution Basedmentioning
confidence: 99%
“…In [11] we applied this approach on an industrial legacy C system. In contrast to the open source case studies where we had to rely on documentation available on the internet, we were now able to validate the results we obtained with the original developers and current maintainers of the application.…”
Section: Coupling Basedmentioning
confidence: 99%
See 1 more Smart Citation
“…Since traces may quickly grow to massive proportions (Zaidman et al 2006b(Zaidman et al , 2005(Zaidman et al , 2006a, we need ways to deal with their size (Cornelissen et al 2009a). We consider two common ways to do so: trace reduction and trace visualization, which are often combined.…”
Section: Trace Analysismentioning
confidence: 99%