Next generation middleware: requirements, architecture, and prototypes

Eliassen, Frank; Andersen, Anders; Blair, Gordon S.; Costa, Fábio M.; Coulson, Geoff; Goebel, Vera; Hansen, Olav R.; Kristensen, Tom; Plagemann, Thomas; Rafaelsen, Hans Ole; Saikoski, Katia; Yu, Weihai

doi:10.1109/ftdcs.1999.818785

Cited by 28 publications

(20 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…There is only very little work on the influence of middleware on software architectures, with [11] being a notable exception. Indeed, we believe that research on software architecture description languages has over-emphasized functionality and not sufficiently addressed the specification of how global properties and non-functional requirements are achieved in an architecture.…”

Section: Software Architecturementioning

confidence: 99%

An Approach of Software Engineering through Middleware

Wedpathak¹

2015

IJIRCCE

View full text Add to dashboard Cite

ABSTRACT:The challenge for software engineering research is to devise notations, techniques, methods and tools for distributed system construction that systematically build and exploit the capabilities that middleware deliver.The construction of a large class of distributed systems can be simplified by leveraging middleware, which is layered between network operating systems and application communication and coordination of distributed components. Existing middleware products enable software engineers to build systems that are distributed across a local-area network. State-of-the-art middleware research aims to push this boundary towards Internet-scale distribution, adaptive and reconfigurable middleware and middleware for dependable and wireless systems.

show abstract

Section: Software Architecturementioning

confidence: 99%

An Approach of Software Engineering through Middleware

Wedpathak¹

2015

IJIRCCE

View full text Add to dashboard Cite

show abstract

“…Here is where reflection comes into play. By definition [3], reflection allows a program to access, reason about and alter its own interpretation. The principle of reflection has been mainly adopted in programming languages, in order to allow a program to access its own implementation (see the reflection package of Java or the interface repository in CORBA).…”

Section: Principles Of Reflective Middlewarementioning

confidence: 99%

Reflective Middleware Solutions for Context-Aware Applications

Capra

Emmerich

Mascolo

2001

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. In this paper, we argue that middleware for wired distributed systems cannot be used in a mobile setting, as the principle of transparency that has driven their design runs counter to the new degrees of awareness imposed by mobility. We propose the marriage of reflection and metadata as a means for middleware to give applications dynamic access to information about their execution context. Finally, we describe a conceptual model that provides the basis of our reflective middleware.

show abstract

“…TAO [27,12] is a CORBA (Common Object Request Broker Architecture) [54] compliant middleware built over ACE (Adaptive Communication Environment). It implements entire CORBA functionalities and provides real-time QoS (Quality of Service).…”

Section: Introductionmentioning

confidence: 99%

Applying patterns to build a lightweight middleware for embedded systems

Bellebia

Douin

2006

Proceedings of the 2006 Conference on Pattern Languages of Programs

View full text Add to dashboard Cite

Today, patterns are used in several domains (distributed applications, security, software requirements, architecture…). Our purpose is double: first, to know if existing patterns can be applied in the particular domain of embedded systems middleware, second, to establish the grounding towards a patterns language for that domain.In this paper, we describe how to design and build a lightweight middleware for embedded systems with well known patterns such as Composite, Proxy, Visitor, Observer, Publish/Subscribe, Leasing, Evictor or Configurator. The patterns we selected and implemented allow keeping the memory footprint reduced. Yet, they were relevant to address the need of creating topology views of Networked Embedded Systems (NES), to monitor and to manage them. As a result, the middleware is modular, flexible, extensible, and lightweight (< 128 kb) according to targeted embedded systems requirements.In addition, this paper describes a concrete case study, illustrating how to select appropriate patterns to build a dedicated middleware in order to interconnect numerous small devices.

show abstract

Next generation middleware: requirements, architecture, and prototypes

Cited by 28 publications

References 13 publications

An Approach of Software Engineering through Middleware

An Approach of Software Engineering through Middleware

Reflective Middleware Solutions for Context-Aware Applications

Applying patterns to build a lightweight middleware for embedded systems

Contact Info

Product

Resources

About