Using Program Slicing in Software Maintenance
IEEE Transactions on Software Engineering
Foundations for the study of software architecture
ACM SIGSOFT Software Engineering Notes
Abstractions for Software Architecture and Tools to Support Them
IEEE Transactions on Software Engineering - Special issue on software architecture
Specification and Analysis of System Architecture Using Rapide
IEEE Transactions on Software Engineering - Special issue on software architecture
Extracting architectural features from source code
Reverse engineering
Recognizing a Program's Design: A Graph-Parsing Approach
IEEE Software
Structural Redocumentation: A Case Study
IEEE Software
Slicing Concurrent Programs - A Graph-Theoretical Approach
AADEBUG '93 Proceedings of the First International Workshop on Automated and Algorithmic Debugging
Interactive explanation of software systems
KBSE '95 Proceedings of The 10th Knowledge-Based Software Engineering Conference
Augmenting Pattern-Based Architectural Recovery with Flow Analysis: Mosaic - a Case Study
WCRE '96 Proceedings of the 3rd Working Conference on Reverse Engineering (WCRE '96)
Software Engineering
Combating architectural degeneration: a survey
Information and Software Technology
A framework for architecture-driven migration of legacy systems to cloud-enabled software
Proceedings of the WICSA 2014 Companion Volume
Hi-index | 0.00 |
We describe the experiences we have had in using ManSART - a software architecture recovery tool that we developed and are employing in the analysis of large scale legacy software systems. ManSART uses a battery of standard data flow, control flow, and program slicing capabilities to automatically recover architectural features from source code. This source code analysis is enabled by representations called analysis. Analysis modules describe the interfaces of each component in a multiple component system. ManSART uses these modules to focus source code analysis and to store the results.