ACM Home Page
Please provide us with feedback. Feedback
Mapping concern space to software architecture: a connector-based approach
Full text PdfPdf (80 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 - 5  
Year of Publication: 2005
ISBN:1-59593-119-8
Also published in ...
Authors
Jing (Janet) Liu  Iowa State University, Ames, IA
Robyn R. Lutz  Iowa State University, Ames, IA
Jeffrey M. Thompson  Guidant Corporation, St. Paul, MN
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 5,   Downloads (12 Months): 23,   Citation Count: 2
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/1083125.1083126
What is a DOI?

ABSTRACT

Concern modeling plays an important role in software design, implementation and maintenance. Hyperspace has provided a strong conceptual framework to separate concerns in multi-dimensional levels. The contribution of this work is to create an architectural element, called a concern connector, to support the implementation of hyperspace in the architectural design phase. The paper makes three basic claims for this idea. First, using concern connectors allows the scope of each hyperslice in a certain concern dimension to be defined and stored. Second, the concern interactions within each hypermodule can be specified in the concern connectors. Third, the association of concern modeling with this distinctive architectural element improves the flexibility of concern maintenance and evolution during the development process. To test these claims the paper investigates the use of concern connectors in a real-world architectural model. The results show how concern connectors implement concern modeling in the architectural design.


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
Chitchyan, R., and Sommerville, I. Composing Dynamic Hyperslices. Workshop on Correctness of Model-based Software Composition (ECOOP 2003).
2
 
3
 
4
Ellenbogen, K. A. and Wood M. A. Cardiac Pacing and ICDs: 3rd Edition. Blackwell Science, 2002, 415--424.
 
5
IEEE Architecture Working Group. IEEE Recommended Practice for Architectural Description of Software-Intensive Systems. IEEE Std 1471--2000, IEEE, 2000.
 
6
Kandé, M. M., Kienzle, J., and Strohmeier, A. From AOP to UML: Towards an Aspect-Oriented Architectural Modeling Approach. TR 200258. Swiss Fed. Ins. Tech., 2002.
 
7
Kandé, M. M., and Strohmeier, A. Modeling Crosscutting Concerns using Software Connectors. ASoC3. Tampa Bay, Florida, 2001.
 
8
 
9
Lohmann, D., and Ebert, J., A Generalization of Hyperspace Approach Using Meta-Models. The 2003 AOSD Early Aspects Workshop (AOSD-EAWS'03). Boston, MA.
10
 
11
Ossher, H., Tarr, P. Research Report: Multi-Dimensional Separation of Concerns in Hyperspace. IBM Research Report 21452(96717), 1999.
 
12
Ossher H., Tarr, P. Multi-Dimensional Separation of Concerns and the Hyperspace Approach. Proc. Symp. Sw. Arch. & Component Technology, 2000.
 
13
Pekilis, B. R. Multi-Dimensional Separation of Concerns and IBM Hyper/J. TR., Bell Canada Software Reliability Laboratory, U. of Waterloo, 2002.
 
14
Philippow, I., Riebisch, M., and Boellert, K. The Hyper/UML Approach for Feature Based Software Design. The 4th AOSD Modeling with UML Workshop. SF, CA, 2003.
 
15
16


Collaborative Colleagues:
Jing (Janet) Liu: colleagues
Robyn R. Lutz: colleagues
Jeffrey M. Thompson: colleagues