On the relationships between static and dynamic models in reverse engineering Java software

Systä, Tarja

doi:10.1109/wcre.1999.806969

Cited by 49 publications

(24 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Walker et al map dynamic information to architectural views [167]. Lots of approaches using dynamic information extract design views rather than architecture [58,59,82,132,156]. Huan et al consider runtime events such as method calls, CPU utilization or network bandwidth consumption because it may inform reverse engineers about system security properties or system performance aspects [69].…”

Section: A Non-architectural Inputsmentioning

confidence: 99%

Software Architecture Reconstruction: A Process-Oriented Taxonomy

Ducasse

Pollet

2009

IIEEE Trans. Software Eng.

257

153

View full text Add to dashboard Cite

Abstract-To maintain and understand large applications, it is important to know their architecture. The first problem is that unlike classes and packages, architecture is not explicitly represented in the code. The second problem is that successful applications evolve over time, so their architecture inevitably drifts. Reconstructing the architecture and checking whether it is still valid is therefore an important aid. While there is a plethora of approaches and techniques supporting architecture reconstruction, there is no comprehensive software architecture reconstruction state of the art and it is often difficult to compare the approaches. This article presents a state of the art in software architecture reconstruction approaches.

show abstract

Section: A Non-architectural Inputsmentioning

confidence: 99%

Software Architecture Reconstruction: A Process-Oriented Taxonomy

Ducasse

Pollet

2009

IIEEE Trans. Software Eng.

257

153

View full text Add to dashboard Cite

show abstract

“…Kollmann et al [11] compared the (static) reverse-engineering capabilities of the existing commercial UML tools. T. Systä [16] presented a tool for abstracting scenarios from traces obtained from debugging Java bytecode. Similarly, Richner and Ducasse [15] used dynamic information for recovering collaboration diagrams and roles.…”

Section: Related Workmentioning

confidence: 99%

“…This is already well-known for traditional software: tasks such as the recovery of design patterns [10], scenarios and sequence diagrams [16,3] are just some examples.…”

Section: Introductionmentioning

confidence: 98%

Supporting Web Application Evolution by Dynamic Analysis

Lucca

Penta

Fasolino

et al.

Eighth International Workshop on Principles of Software Evolution (IWPSE'05)

View full text Add to dashboard Cite

show abstract

“…This is already well known for traditional software: tasks such as the recovery of design patterns [2], scenarios and sequence diagrams [3,4] are only some examples.…”

Section: Introductionmentioning

confidence: 99%