Abstract
An architectural connector, a central notion in Architectural Description Languages (ADL) [9, 5], is an abstraction that captures interactions among software components. Existing approaches for representing architectural connectors in programming environments use object-based [6] and component-based [8, 1, 4] notations. Often architectural abstractions are realized in programming environments to ensure representational benefits provided by ADLs like separating computational and interaction concerns and treating connectors as first-class design elements. However, in such programming environments, complex connectors are represented through components. When connectors are represented through components, components and connectors are indistinguishable in terms of mechanisms used to realize them. One has to look for functionalities that components realize to decide whether it is a component or a connector. At the same time, primitive connectors are discernible elements in such programming environments. This paper explores an alternative mechanism i.e. aspect in aspectoriented programming language[7] to represent a connector. Appropriateness of aspects to represent connectors is demonstrated by implementing few examples of connectors in Java/AspectJ [3, 7] programming environment.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Similar content being viewed by others
References
J. Aldrich. Archjava :connecting software architecture to implementation. Proc. International Conference on Software Engineering, 2002
F. Arbab. Abstract behavior types: a foundation model for components and their composition. Sci. Comput. Program., 55(1-3):3–52, 2005
K. Arnold, J. Gosling, and D. Holmes. The Java Programming Language. Addison-Wesley Reading MA, third edition
N. Bhope and R. K. Joshi. System of purely interconnected component. Technical Report, Department of Computer Science and Engineering, IIT-Bombay, June 2001
D. Garlan. Acme: An architecture description interchange language. Proceedings of CASCON’97, November 1997
D. Garlan, S.-W. Cheng, and A. J. Kompanek. Reconciling the needs of architectural description with object-modelinnotations. Sci. Comput. Program., 44(1):23–49, 2002
G. Kiczales, E. Hilsdale, J. Hugunin, M. Kersten, J. Palm, and W. G. Griswold. An overview of aspectj. In ECOOP ’01: Proceedings of the 15th European Conference on Object-Oriented Programming, pages 327–353, London, UK, 2001. Springer-Verlag
S. Malek, M. M. Rakic, and N. Medvidovic. A styleaware architectural middleware for resource constrained, distributed systems. IEEE Transactions On Software Engineering, 31(3):256–272, March 2005
N. Medvidovic and R. N. Taylor. A classification and comparison framework for software architecture description language. IEEE Transactions on Software Engineering, 26(1):70–93, January 2000
N. Vaidya and R. Joshi. Implementation of filter configurations using method call pointcuts in aspectj. In WAOSD 2004: Proceedings of the International Workshop on Aspect-Oriented Software Development, Bejing, China, September 2004
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2011 Springer India Pvt. Ltd
About this paper
Cite this paper
Kiwelekar, A.W., Joshi, R.K. (2011). Empowering primitive architectural connectors with aspects. In: Pise, S.J. (eds) Thinkquest~2010. Springer, New Delhi. https://doi.org/10.1007/978-81-8489-989-4_33
Download citation
DOI: https://doi.org/10.1007/978-81-8489-989-4_33
Publisher Name: Springer, New Delhi
Print ISBN: 978-81-8489-988-7
Online ISBN: 978-81-8489-989-4
eBook Packages: Computer ScienceComputer Science (R0)