Software architecture recovery: Difference between revisions

Revision as of 09:30, 28 May 2014

Revision as of 11:33, 30 October 2016

Line 1:

'''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 system]]s 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 softare retrofits <ref name="ieeesw">{{Cite journal |doi = 10.1109/MS.2016.49 | url = http://ieeexplore.ieee.org/document/7420474/?arnumber=7420474| title = Software Retrofit in High-Availability Systems: When Uptime Matters | journal = IEEE Software |volume = 32 |issue = 3 |year = 2015|last1 = Ronzon| first1 T. = }}</ref>.

== Approaches ==

Line 8 ⟶ 10:

== References ==

{{reflist}}

* http://www.ucb.br/ucbtic/wmswm-04/SoftwareArchitectureRecovery.pdf (link is dead)