Software architecture recovery: Difference between revisions

Revision as of 03:21, 6 August 2024

Latest revision as of 14:24, 24 July 2025

Line 5:

== Approaches ==

Most approaches to software architecture recovery has been exploring the [[static program analysis|static analysis]] of systems. When considering object-oriented software, which employs a lot of polymorphism and dynamic binding mechanisms, [[dynamic program analysis|dynamic analysis]] becomes an essential technique to comprehend the system behavior, object interactions, and hence to reconstruct its architecture.

In this work, the criteria used to determine how source code entities should be clustered in architectural elements are mainly based on the dynamic analysis of the system, taking into account the occurrences of interaction patterns and types (classes and interfaces) in [[Use-case analysis|use-case realizations]]. <ref>{{cite book |first=T. |last=Lutellier |first2=D. |last2=Chollak |first3=J. |last3=Garcia |first4=L. |last4=Tan |first5=D. |last5=Rayside |first6=N. |last6=Medvidovic |first7=R. |last7=Kroeger |chapter=Comparing Software Architecture Recovery Techniques Using Accurate Dependencies |title=2015 IEEE/ACM 37th IEEE International Conference on Software Engineering, Florence |year=2015 |isbn=978-1-4799-1934-5 |pages=69–78 |doi=10.1109/ICSE.2015.136}}</ref>

== See also ==