Searching for authors named "Constantinos Constantinides" – sorted by Relevance.
-
Considerations on Component Visibility and Code Reusability in AspectJ
- The AspectJ programming language supports the principle of modularity and abstraction by allowing explicit separation between aspects and system core concerns. However, using AspectJ does not necessarily imply loose coupling as aspect definitions may maintain explicit visibility over components. In
- Cited by 2 (1 self) – Add To MetaCart
-
Reasoning About a Classification of Crosscutting Concerns in Object-Oriented Systems
- and behavior of crosscutting concerns in OO systems. We further argue that aspects must be defined as first-class abstractions in order to be manipulated as such and thus to provide for reusability and dynamic adaptability as well as for the creation of dynamically loadable aspect repositories.
- Cited by 5 (0 self) – Add To MetaCart
-
On the Requirements for Concurrent Software Architectures to Support Advanced Separation of Concerns
- Some of the open issues regarding the design and implementation of a concurrent software architecture that should support advanced separation of concerns lie at the level at which components and aspects integrate. Should the integration be at the source code or maybe at the object code? How do we be
- Cited by 2 (2 self) – Add To MetaCart
-
Composing Concerns with a Framework Approach
- As concurrent software systems become larger, the interaction of their components is becoming more complex. This interaction may limit reuse, making it difficult to validate design and correctness and perhaps forcing reengineering of these systems in order to meet future requirements. In order to re
- Cited by 2 (0 self) – Add To MetaCart
-
An Aspect-Oriented Design Framework for Concurrent Systems
- The goal of AOP is to achieve an improved separation of concerns in both design, and implementation. Our work concentrates on the aspectual decomposition of concurrent object-oriented systems. Following a component hierarchy within the object-oriented programming paradigm we categorized aspects as i
- Add To MetaCart
-
An Aspect-Oriented Design Framework
- With Aspect-Oriented Programming (AOP), we see a problem as a collection of different issues, and try to find all issues relevant to the problem. We can therefore manage to achieve an improved separation of concerns in both design, and implementation. The goal of AOP is to decompose a problem into a
- Cited by 1 (0 self) – Add To MetaCart
-
An Aspect-Oriented Design Framework for Concurrent Systems
- Abstract. In Aspect-Oriented Programming we decompose a problem into a number of functional components as well as a number of aspects and then we compose these components and aspects to obtain system implementations. The goal is to achieve an improved separation of concerns in both design, and imple
- Cited by 4 (0 self) – Add To MetaCart
-
A Framework to Address a Two-Dimensional Composition of Concerns
- Although not bound to Object-Oriented Programming (OOP), Aspect-Oriented Programming (AOP) is a paradigm proposal that retains the advantages of OOP and aims at avoiding the tyranny of dominant decomposition. The goal is to achieve an improved separation of concerns in both design, and implementatio
- Cited by 5 (1 self) – Add To MetaCart
-
The Development of Generic Definitions of
- In this paper we investigate the notion of developing generic aspects in Hyper/J and compare it with other approaches.
- Add To MetaCart

