Harold Ossher
ABSTRACT
This talks describes a number of principles and key concepts underlying concern manipulation, the use of concerns to aid in a variety of software development tasks. Concern modeling and exploration, query and composition are considered. The principles and concepts guided work on the Concern Manipulation Environment (CME), which provides both prototype tools supporting aspect-oriented software development, and flexible components for use in building such tools.
- CME web site: http://sourceforge.net/projects/cme/.Google Scholar
- William Harrison, Vincent Kruskal, Harold Ossher, Peri Tarr and Frank Tip, "Common Low-Level Support for Composition and Weaving." OOPSLA '02 Workshop on Tools for Aspect-Oriented Software Development.Google Scholar
- William Harrison and Harold Ossher, "Member-Group Relationships Among Objects." AOSD '02 Workshop on Foundations Of Aspect-Oriented Languages (FOAL).Google Scholar
- William Harrison, Harold Ossher, Stanley M. Sutton Jr., and Peri Tarr, "Concern Modeling in the Concern Manipulation Environment," ICSE '05 workshop on Modeling and Analysis of Concerns in Software (MACS '05). Google ScholarDigital Library
- W. Harrison, H. Ossher, S. Sutton, P. Tarr, "The Concern Manipulation Environment -- Supporting Aspect-Oriented Software Development." IBM Systems Journal 44(2): 309--318, 2005, special issue on Open Source Software. Google ScholarDigital Library
- William Harrison, Harold Ossher and Peri Tarr, "Asymmetrically vs. Symmetrically Organized Paradigms for Software Composition." Research Report RC22685, IBM Thomas J. Watson Research Center, Yorktown Heights, NY, December, 2002.Google Scholar
- William Harrison, Harold Ossher and Peri Tarr, "General Composition of Software Artifacts." In Proceedings of the 5th International Symposium on Software Composition (SC '06), March 2006, Springer, LNCS 4089. Google ScholarDigital Library
- Peri Tarr, William Harrison, and Harold Ossher, "Pervasive Query Support in the Concern Manipulation Environment." IBM Research Report RC23343, 2005.Google Scholar
Index Terms
- Fundamentals of concern manipulation
Recommendations
Aspects and/versus modularity the grand debate
OOPSLA '06: Companion to the 21st ACM SIGPLAN symposium on Object-oriented programming systems, languages, and applicationsAspect-Oriented Programming (AOP) and Aspect-Oriented Software Development (AOSD) endeavor to aid programmers in the separation of concerns, specifically crosscutting concerns, as an advance in modularization. AOP does so using primarily language ...
Aspect-Oriented workflow languages
ODBASE'06/OTM'06: Proceedings of the 2006 Confederated international conference on On the Move to Meaningful Internet Systems: CoopIS, DOA, GADA, and ODBASE - Volume Part IMost available aspect-oriented languages today are extensions to programming languages However, aspect-orientation, which is a paradigm for decomposition and modularization, is not only applicable in that context In this paper, we introduce aspect-...
Representing concerns in source code
A software modification task often addresses several concerns. A concern is anything a stakeholder may want to consider as a conceptual unit, including features, nonfunctional requirements, and design idioms. In many cases, the source code implementing ...
Comments