Separating architectural concerns to ease program understanding

Authors:
Vladimir Jakobac;Nenad Medvidovic;Alexander Egyed
Affiliations:
Univ. of Southern California, Los Angeles, CA;Univ. of Southern California, Los Angeles, CA;Teknowledge Corporation, Marina Del Rey, CA
Venue:
MACS '05 Proceedings of the 2005 workshop on Modeling and analysis of concerns in software
Year:
2005

Citing 9
Cited 1

Foundations for the study of software architecture

ACM SIGSOFT Software Engineering Notes
Extracting architectural features from source code

Reverse engineering
N degrees of separation: multi-dimensional separation of concerns

Proceedings of the 21st international conference on Software engineering
A fast algorithm for finding dominators in a flowgraph

ACM Transactions on Programming Languages and Systems (TOPLAS)
An Approach for Recovering Distributed System Architectures

Automated Software Engineering
Structural Redocumentation: A Case Study

IEEE Software
Architecture-Aware Adaptive Clustering of OO Systems

CSMR '04 Proceedings of the Eighth Euromicro Working Conference on Software Maintenance and Reengineering (CSMR'04)
Using software evolution to focus architectural recovery

Automated Software Engineering
Improving system understanding via interactive, tailorable, source code analysis

FASE'05 Proceedings of the 8th international conference, held as part of the joint European Conference on Theory and Practice of Software conference on Fundamental Approaches to Software Engineering

Enhancing architectural recovery using concerns

ASE '11 Proceedings of the 2011 26th IEEE/ACM International Conference on Automated Software Engineering

Quantified Score

Hi-index	0.00

Visualization

Abstract

This paper presents an iterative, user-guided approach to program understanding based on a framework for analyzing and visualizing software systems. The framework is built around a pluggable and extensible set of clues about a given problem domain, execution environment, and/or programming language. The approach leverages two orthogonal architectural views of a system and describes how a proper identification of boundaries for separate concerns helps in reasoning about the system.