Differences

This shows you the differences between two versions of the page.

--- an_architectural_revere_engineering_environment [2013/09/06 01:47] – yann
+++ an_architectural_revere_engineering_environment [2025/01/15 21:40] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
-====== Abstract ======
+====== Fiutem, R.; Antoniol, G.; Tonella, P. & Merlo, E. ART: An Architectural Revere Engineering Environment. Journal of Software Maintenance: Research and Practice, Wiley, 1999, 11, 339-364 ======
+===== Abstract =====
 When programmers perform maintenance tasks, program understanding is often required. One of the first activities in understanding a software system is identifying its subsystems and their relations, i.e., its software architecture. Since a large part of the effort is spent in creating a mental model of the system under study, tools can help maintainers in managing the evolution of legacy systems by showing them architectural information.
@@ Line 9: / Line 11: @@
 The results obtained show that cliché-based architectural recovery is feasible and the recovered information can be valuable support in reengineering and maintenance activities.
-====== Comments ======
+===== Comments =====
-//Yann-Gaël Guéhéneuc, 2013/09/06//
+//Yann-Gaël Guéhéneuc, 2013/08/30//
 In this paper, the authors introduce the problem of architecture recovery. They also recall the problem of identifying the connections among components. To recover components and their connections, they devise a hierarchical component model and adapt the taxonomy of inter-process connectors (IPC) first proposed by [[A Syntactic Theory of Software Architecture|Dean and Cordy]] to describe the possible connections among components. The considered types of connections are: