Just-in-time concern modeling

Authors:
Martin P. Robillard;Gail C. Murphy
Affiliations:
McGill University, Montréal, QC, Canada;University of British Columbia, Vancouver, BC, Canada
Venue:
MACS '05 Proceedings of the 2005 workshop on Modeling and analysis of concerns in software
Year:
2005

Citing 8
Cited 0

Refactoring object-oriented frameworks

Refactoring object-oriented frameworks
N degrees of separation: multi-dimensional separation of concerns

Proceedings of the 21st international conference on Software engineering
Does Code Decay? Assessing the Evidence from Change Management Data

IEEE Transactions on Software Engineering
Concern graphs: finding and describing concerns using structural program dependencies

Proceedings of the 24th International Conference on Software Engineering
Design erosion: problems and causes

Journal of Systems and Software
Refactoring

TOOLS '00 Proceedings of the Technology of Object-Oriented Languages and Systems (TOOLS 34'00)
Representing concerns in source code

Representing concerns in source code
How Effective Developers Investigate Source Code: An Exploratory Study

IEEE Transactions on Software Engineering

Quantified Score

Hi-index	0.00

Visualization

Abstract

In this position paper, we propose the notion of just-in-time concern modeling. As some concerns emerge late in the software life cycle and can be ephemeral, we argue that mechanisms should be available to capture descriptions of concerns as they emerge or become relevant. Based on our experience with the FEAT concern modeling and analysis tool, we highlight the essential characteristics, benefits, and pitfalls of just-in-time concern modeling at the source code level.