ACM Home Page
Please provide us with feedback. Feedback
Concern modeling in the concern manipulation environment
Full text PdfPdf (184 KB)
Source ACM SIGSOFT Software Engineering Notes archive
Volume 30 ,  Issue 4  (July 2005) table of contents
SESSION: Modeling and Analysis of Concerns in Software (MACS) table of contents
Pages: 1 - 5  
Year of Publication: 2005
ISSN:0163-5948
Also published in ...
Authors
William Harrison  IBM Thomas J. Watson Research Center, Hawthorne, NY
Harold Ossher  IBM Thomas J. Watson Research Center, Hawthorne, NY
Stanley Sutton  IBM Thomas J. Watson Research Center, Hawthorne, NY
Peri Tarr  IBM Thomas J. Watson Research Center, Hawthorne, NY
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 12,   Downloads (12 Months): 45,   Citation Count: 8
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1082983.1083134
What is a DOI?

ABSTRACT

The Concern Manipulation Environment (CME) is an AOSD environment in which software is organized and manipulated in terms of concerns. This paper is about ConMan, the CME concern manager, which supports the identification, definition, encapsulation, extraction and composition of concerns. ConMan models software in terms of concerns, relationships, constraints, units, artifacts, and associated information. The concern model is multidimensional and concerns can be defined extensionally and/or intensionally. ConMan is neutral with respect to artifact types and formalisms, and it can be used with both aspect-oriented and non-aspect oriented software and methods. ConMan is intended to serve both as a tool for directly modeling concerns and as a platform for developing alternative concern-modeling approaches.


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
E. Baniassad and S. Clarke, "Finding aspects in requirements with Theme/Doc", In Early Aspects 2004: Aspect-Oriented Requirements Engineering and Architecture Design Workshop; at 3rd AOSD, 2004.
 
2
L. Bass, M. Klein, and L. Northrop, "Identifying aspects using architectural reasoning". In Early Aspects 2004: Aspect-Oriented Requirements Engineering and Architecture Design Workshop; at 3rd AOSD, 2004.
 
3
I. Brito, and A. Moreira, "Integrating the NFR frame-work in a RE model", In Early Aspects 2004: Aspect-Oriented Requirements Engineering and Architecture Design Workshop; at 3rd AOSD 2004.
4
 
5
A. Colyer, A. Clement, G. Harley and M. Webster. Eclipse AspectJ, Addison-Wesley, 2004.
 
6
Eclipse.org. "Concern Manipulation Environment Project", http://www.eclipse.org/cme
7
 
8
FEAT, http://www.cs.ubc.ca/labs/spl/projects/feat/
 
9
IBM Corp. http://www.research.ibm.com/hyperspace/.
 
10
D. Lohmann, and J. Ebert, "A generalization of the hyperspace approach using meta-models", In Early Aspects 2003: Aspect-Oriented Requirements Engineering and Architecture Design Workshop, at 2nd AOSD, 2003.
11
12
 
13
P. Tarr, H. Ossher, and W. Harrison, "Pervasive Query Support in the Concern Manipulation Environment", IBM Research Report RC23343 (WO409-135) September 21, 2004 (see {6}).
14
 
15
B. Tekinerdogan, "ASAAM: aspectual software architecture analysis method", In Early Aspects 2003: Aspect-Oriented Requirements Engineering and Architecture Design Workshop, at 2nd AOSD., 2003.
 
16
D. Wagelaar, "A concept-based approach for early aspect modeling", In Early Aspects 2003: Aspect-Oriented Requirements Engineering and Architecture Design Workshop, at 2nd AOSD, 2004.

CITED BY  8

Collaborative Colleagues:
William Harrison: colleagues
Harold Ossher: colleagues
Stanley Sutton: colleagues
Peri Tarr: colleagues