Software architecture recovery

Software architecture recovery is a set of methods for the extraction of architectural information from lower level representations of a software system, such as source code. The abstraction process to generate architectural elements frequently involves clustering source code entities (such as files, classes, functions etc.) into subsystems according to a set of criteria that can be application dependent or not. Architecture recovery from legacy systems is motivated by the fact that these systems do not often have an architectural documentation, and when they do, this documentation is many times out of synchronization with the implemented system.

Software architecture recovery may be required as part of software retrofits.^[1]

Approaches

Most approaches to software architecture recovery has been exploring the static analysis of systems. When considering object-oriented software, which employs a lot of polymorphism and dynamic binding mechanisms, 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 realizations. ^[2]

See also

• Reverse engineering
• Software archaeology
• Software architecture
• System appreciation

References

1. Ronzon, T. (2015). "Software Retrofit in High-Availability Systems: When Uptime Matters". IEEE Software. 32 (3): 11–17. doi:10.1109/MS.2016.49.
2. Lutellier, T.; Chollak, D.; Garcia, J.; Tan, L.; Rayside, D.; Medvidovic, N.; Kroeger, R. (2015). "Comparing Software Architecture Recovery Techniques Using Accurate Dependencies". 2015 IEEE/ACM 37th IEEE International Conference on Software Engineering, Florence. pp. 69–78. doi:10.1109/ICSE.2015.136. ISBN 978-1-4799-1934-5.