Aspect-Oriented Space Containers for Efficient Publish/Subscribe Scenarios in Intelligent Transportation Systems

Kühn, Eva; Mordinyi, Richard; Keszthelyi, L.; Schreiber, Christian; Bessler, Sandford; Tomic, Slobodanka

doi:10.1007/978-3-642-05148-7_34

Cited by 8 publications

(10 citation statements)

References 24 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In some mobile environments, such as intelligent transportation systems, peers have only a few seconds of connectivity and very limited bandwidth (Zaera, 2008). To avoid the loss of high priority events, such as safety-critical driver warnings, solutions have been proposed such as using a combination of distributed hash tables (DHTs) with Aspect-oriented space containers (Kuhn et al, 2009). Similarly, a notification service for mobile environments in which producers are able to send events even to subscribers that are in permanent move has been proposed (SchwiderskiGrosche and Moody, 2009).…”

Section: Space-based and Sitcomp Architecturementioning

confidence: 99%

Middleware and architectures for space-based and situated computing

Cristea

Dobre

Costan

et al. 2011

IJSSC

View full text Add to dashboard Cite

Situated computing is an actual research area that gathers the knowledge and investigation in mobile, wearable, ubiquitous and augmented computing. The aim is to sustain systems that collect information about contexts and user actions over a period of time and supply it to applications that dynamically adapt to context changes. Situated computing systems have various architectures, but most of them include a middleware layer that supports equipment with limited computing resources and offers functionalities that simplify applications development, deployment, execution, and maintenance. Middleware and architectures are the focus of this paper, which presents the main concepts, research results, and future trends in middleware for situated computing. Service oriented, event driven, agent-based, and peer-to-peer architectures are discussed. Middleware issues for situated computing, embedded devices, autonomic space management, proactive services, context awareness, and smart spaces are tackled as well.

show abstract

Section: Space-based and Sitcomp Architecturementioning

confidence: 99%

Middleware and architectures for space-based and situated computing

Cristea

Dobre

Costan

et al. 2011

IJSSC

View full text Add to dashboard Cite

show abstract

“…Another important component is the so called coordinator [21] which are programmable parts of the container being responsible for managing their view on the entries in the container. The aim of a coordinator is to represent a coordination model and to structure and organize the entries in the container for efficient access [22]. The difference to Linda is that a container may be bounded to a maximum number of entries, and allows the usage of so called coordinators with each having its specific and optimized view on the stored entries.…”

Section: A the Architectural Framework For Agile Processesmentioning

confidence: 99%

“…The last main component of AFA are the so called aspects [22], which represent additional computational logic and are executed on the peer where the container is located. Aspects are triggered by operations on a specific container, rather on the according impact.…”

Section: A the Architectural Framework For Agile Processesmentioning

confidence: 99%

Towards an Architectural Framework for Agile Software Development

Mordinyi

Kühn

Strobel

2010

2010 17th IEEE International Conference and Workshops on Engineering of Computer Based Systems

Self Cite

View full text Add to dashboard Cite

One of the ideas of agile software development is to respond to changes rather than following a plan. Constantly changing businesses result in changing requirements, to be handled in the development process. Therefore, it is essential that the underlying software architecture is capable of managing agile business processes. However, criticism on agile software development states that it fails to pay attention to architectural and design issues and therefore is bound to engender suboptimal design-decisions.In this paper we propose an architectural framework for agile software development, that by explicitly separating computational, coordinational, and communicational models offers a high degree of flexibility regarding architectural and design changes introduced by agile business processes. The framework strength is facilitated by combining the characteristics and properties of state-of-the-art middleware architectural styles captured in a simple API.The benefit of our approach is a clear architectural design with minimized effects of changes the models have on each other, accompanied by an efficient realization of new business requirements.

show abstract

“…Finally, a container may be surrounded by a set of pre-and post-aspects, representing additional computational logic and deployed at specific interception points according to the interceptor pattern. They are executed on the peer where the container is located and are capable of changing or to extending the operation with further functionalities, e.g., to replicate container entries [18].…”

Section: Architecture Of the Afa Frameworkmentioning

confidence: 99%

“…However, by means of aspects the container can be located and replicated in a P2P environment. In such case, aspects installed at every replica would define the replication technique and the consistency strategy between the replicas [18]. Since aspects may contain any code, for software developers it is not necessary to implement replication issues from the scratch.…”

Section: Architecture Of the Afa Frameworkmentioning

confidence: 99%

Structuring Complexity Issues for Efficient Realization of Agile Business Requirements in Distributed Environments

Mordinyi

Kühn

Strobel

2010

Lecture Notes in Business Information Processing

Self Cite

View full text Add to dashboard Cite

Abstract.One of the ideas of agile software development is to respond to changes rather than following a plan. Constantly changing businesses result in changing requirements, to be handled in the development process. Therefore, it is essential that the underlying software architecture is capable of managing agile business processes. However, criticism on agile software development states that it lacks paying attention to architectural and design issues and therefore is bound to engender suboptimal design-decisions. We propose an architectural framework, that by explicitly distinguishing computational, coordinational, organizational, distributional, and communicational models offers a high degree of flexibility regarding architectural and design changes. The framework strength is facilitated by a) combining the characteristics and properties of architectural styles captured in a simple API, and b) offering a predefined architectural structure to the developer of distributed applications to cope with complexities of distributed environments. The benefit of our approach is a clear architectural design with minimal mutual effects of the models with respect to changes, accompanied by an efficient realization of new business requirements.

show abstract

Aspect-Oriented Space Containers for Efficient Publish/Subscribe Scenarios in Intelligent Transportation Systems

Cited by 8 publications

References 24 publications

Middleware and architectures for space-based and situated computing

Middleware and architectures for space-based and situated computing

Towards an Architectural Framework for Agile Software Development

Structuring Complexity Issues for Efficient Realization of Agile Business Requirements in Distributed Environments

Contact Info

Product

Resources

About