Revision as of 02:04, 10 June 2008 edit Alaibot (talk \| contribs) 434,501 edits m Robot: tagging uncategorised page ← Previous edit		Revision as of 23:28, 28 June 2008 edit undo Fabrictramp (talk \| contribs) Administrators 123,697 edits Dead-end pages clean up project; you can help! using AWB Next edit →
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 ~~systems~~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. == 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 systembehavior, 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.▼ == ~~'''Approaches'''~~References == 1.* http://www.ucb.br/ucbtic/wmswm-04/SoftwareArchitectureRecovery.pdf▼ ▲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 systembehavior, 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. ~~== Reference ==~~ ▲1. http://www.ucb.br/ucbtic/wmswm-04/SoftwareArchitectureRecovery.pdf {{uncategorized\|date=June 2008}}

Software architecture recovery: Difference between revisions