Just-in-time concern modeling

Subscribe (Full Service)


	Search: The ACM Digital Library The Guide

	Feedback

Just-in-time concern modeling

Full text

Pdf (89 KB)

Source

International Conference on Software Engineering archive
Proceedings of the 2005 workshop on Modeling and analysis of concerns in software table of contents

St. Louis, Missouri

SESSION: Modeling and Analysis of Concerns in Software (MACS) table of contents

Pages: 1 - 3

Year of Publication: 2005

ISBN:1-59593-119-8

Also published in ...

Authors

Martin P. Robillard	McGill University, Montréal, QC, Canada
Gail C. Murphy	University of British Columbia, Vancouver, BC, Canada

Publisher

ACM New York, NY, USA

Bibliometrics

Downloads (6 Weeks): 3, Downloads (12 Months): 23, Citation Count: 0

Additional Information:

abstract references index terms collaborative colleagues

Tools and Actions:	Review this Article Save this Article to a Binder Display Formats: BibTeX EndNote ACM Ref

DOI Bookmark:	Use this link to bookmark this Article: http://doi.acm.org/10.1145/1083125.1083136 What is a DOI?

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.

REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

	1	Stephen G. Eick , Todd L. Graves , Alan F. Karr , J. S. Marron , Audris Mockus, Does Code Decay? Assessing the Evidence from Change Management Data, IEEE Transactions on Software Engineering, v.27 n.1, p.1-12, January 2001 [doi>10.1109/32.895984]
	2	Martin Fowler, Refactoring, Proceedings of the Technology of Object-Oriented Languages and Systems (TOOLS 34'00), p.437, July 30-August 03, 2000
	3	Gregor Kiczales, John Lamping, Anurag Menhdhekar, Chris Maeda, Cristina Lopes, Jean-Marc Loingtier, and John Irwin. Aspect-oriented programming. In Proceedings of the 11th European Conference on Object-oriented Programming, volume 1241 of Lecture Notes in Computer Science, pages 220--242. Springer-Verlag, June 1997.
	4	Object Technology International, Inc. Eclipse platform technical overview. White Paper, July 2001.
	5	William F. Opdyke, Refactoring object-oriented frameworks, University of Illinois at Urbana-Champaign, Champaign, IL, 1992
	6	Martin P. Robillard , Gail C. Murphy, Representing concerns in source code, 2003
	7	Martin P. Robillard , Wesley Coelho , Gail C. Murphy, How Effective Developers Investigate Source Code: An Exploratory Study, IEEE Transactions on Software Engineering, v.30 n.12, p.889-903, December 2004 [doi>10.1109/TSE.2004.101]
	8	Martin P. Robillard , Gail C. Murphy, Concern graphs: finding and describing concerns using structural program dependencies, Proceedings of the 24th International Conference on Software Engineering, May 19-25, 2002, Orlando, Florida [doi>10.1145/581339.581390]
	9	Martin P. Robillard and Gail C. Murphy. Evolving desccriptions of scattered concerns. Technical Report SOCS-TR-2005. 1, School of Computer Science, McGill University, Montréal, QC, Canada, January 2005.
	10	Peri Tarr , Harold Ossher , William Harrison , Stanley M. Sutton, Jr., N degrees of separation: multi-dimensional separation of concerns, Proceedings of the 21st international conference on Software engineering, p.107-119, May 16-22, 1999, Los Angeles, California, United States [doi>10.1145/302405.302457]
	11	Jilles van Gurp , Jan Bosch, Design erosion: problems and causes, Journal of Systems and Software, v.61 n.2, p.105-119, March 2002 [doi>10.1016/S0164-1212(01)00152-2]