Results 1 -
7 of
7
Towards a Model-Driven Approach to Build Component-based Adaptable Middleware
- 3RD WORKSHOP ON ADAPTIVE AND REFLECTIVE MIDDLEWARE TORONTO, CANADA
, 2004
"... Adaptability is one of the goals that applications and middleware frameworks are trying to achieve. On one hand, the component paradigm is a way of reaching this goal by enforcing the reusability of functionalities involved in a component-based middleware framework. In particular, reflection could b ..."
Abstract
-
Cited by 9 (3 self)
- Add to MetaCart
Adaptability is one of the goals that applications and middleware frameworks are trying to achieve. On one hand, the component paradigm is a way of reaching this goal by enforcing the reusability of functionalities involved in a component-based middleware framework. In particular, reflection could be combined with components to improve the adaptability of the structure of their assemblies. On the other hand, the model driven paradigm provides an efficient way to describe an application with enough abstraction to enable its mapping on various execution platforms. The contribution of this paper is a combination of both model and component paradigms to reach more adaptability in middleware, especially in a component-based framework to build transaction services. The framework presented uses models to describe middleware standards and compiles them to components. These components are coupled with a compliant component-based middleware framework. This approach provides adaptability at various levels with some added values.
Model-Based Automation of Service Deployment in a Constrained Environment
, 2004
"... been issued as a Research Report for early dissemination of its contents. In view of the transfer of copyright to the outside publisher, its distribution outside of IBM prior to publication should be limited to peer communications and specific requests. After outside publication, requests should be ..."
Abstract
-
Cited by 2 (0 self)
- Add to MetaCart
(Show Context)
been issued as a Research Report for early dissemination of its contents. In view of the transfer of copyright to the outside publisher, its distribution outside of IBM prior to publication should be limited to peer communications and specific requests. After outside publication, requests should be filled only by reprints or legally obtained copies of the article (e.g., payment of royalties). Copies may be requested from IBM T. J. Watson Research Center, P.
Model-Driven Software Development Using a Metamodel-Based Extension Mechanism For Uml
, 2005
"... ..."
Using MDE to Build a Schizophrenic Middleware for Home/Building Automation
"... Abstract. In the personal or corporate spheres, the home/office of tomorrow is soon to be the home/office of today, with a plethora of networked devices embedded in appliances, such as mobile phones, televisions, thermostats, and lamps, making it possible to automate and remotely control many basic ..."
Abstract
-
Cited by 1 (0 self)
- Add to MetaCart
(Show Context)
Abstract. In the personal or corporate spheres, the home/office of tomorrow is soon to be the home/office of today, with a plethora of networked devices embedded in appliances, such as mobile phones, televisions, thermostats, and lamps, making it possible to automate and remotely control many basic household functions with a high degree of accuracy. In this domain, technological standardization is still in its infancy, or remains fragmented. The different functionalities of the various appliances, as well as market factors, imply that the devices that control them communicate via a multitude of different protocols (KNX, LonWorks, InOne). Building a high level middleware to support all the appliances seems to be a reasonable approach. However, market factors has shown that the emergence of a unique and universal middleware is a dream. To solve this issue, we have built a new generation of schizophrenic middleware in which service access can be generated from an abstract services description. EnTiMid, our implementation of schizophrenic middleware, supports various services access models (several personalities): SOAP (Simple Object Access Protocol), UPnP and DPWS (Device Profile for WebServices). In this paper, we describe how these personalities are generated using a Model Driven Engineering approach and discuss the benefits of our approach in the context of a deployment of new services at the city level. 1
(2008)" Using MDE to Build a Schizophrenic Middleware for Home/Building Automation
, 2010
"... Abstract. In the personal or corporate spheres, the home/office of tomorrow is soon to be the home/office of today, with a plethora of networked devices embedded in appliances, such as mobile phones, televisions, thermostats, and lamps, making it possible to automate and remotely control many basic ..."
Abstract
- Add to MetaCart
(Show Context)
Abstract. In the personal or corporate spheres, the home/office of tomorrow is soon to be the home/office of today, with a plethora of networked devices embedded in appliances, such as mobile phones, televisions, thermostats, and lamps, making it possible to automate and remotely control many basic household functions with a high degree of accuracy. In this domain, technological standardization is still in its infancy, or remains fragmented. The different functionalities of the various appliances, as well as market factors, imply that the devices that control them communicate via a multitude of different protocols (KNX, LonWorks, InOne). Building a high level middleware to support all the appliances seems to be a reasonable approach. However, market factors has shown that the emergence of a unique and universal middleware is a dream. To solve this issue, we have built a new generation of schizophrenic middleware in which service access can be generated from an abstract services description. EnTiMid, our implementation of schizophrenic middleware, supports various services access models (several personalities): SOAP (Simple Object Access Protocol), UPnP and DPWS (Device Profile for WebServices). In this paper, we describe how these personalities are generated using a Model Driven Engineering approach and discuss the benefits of our approach in the context of a deployment of new services at the city level. 1
Type: Survey Status: FINAL
, 2005
"... have emerged recently. In this report we survey the most significant of these approaches, considering their origins, aims, and contributions. Alongside the AO approaches, we also analyse some of the contemporary non-AO work in order to bring out the differences between two sets of techniques, and to ..."
Abstract
- Add to MetaCart
(Show Context)
have emerged recently. In this report we survey the most significant of these approaches, considering their origins, aims, and contributions. Alongside the AO approaches, we also analyse some of the contemporary non-AO work in order to bring out the differences between two sets of techniques, and to understand the potential contributions of aspect-oriented analysis and design. We also provide some initial insights into processes for AO requirements engineering, analysis and design which may serve as basis for integration of the work of the AOSD-EUROPE project partners. We also outline some issues relevant to such integration.
Abstract Elaborating UML 2.0 Profiles for AO Design ∗
"... An effective adoption of aspect-oriented (AO) principles in industrial and large-scale projects heavily relies on a good support for AO principles throughout the whole software life-cycle. Although, aspect-oriented languages and implementation tools are mature, the current challenge is to incorporat ..."
Abstract
- Add to MetaCart
(Show Context)
An effective adoption of aspect-oriented (AO) principles in industrial and large-scale projects heavily relies on a good support for AO principles throughout the whole software life-cycle. Although, aspect-oriented languages and implementation tools are mature, the current challenge is to incorporate aspect-oriented concepts to earlier development phases, such as software design. UML is the most widely used language for software design. It can be extended to incorporate new modelling concepts by means of Profiles. Constructing Profiles which support aspect-oriented design (AOD) would allow software developers to use a well-known design notation and a wide number of available UML tools. This paper outlines a generic guide on how to construct UML Profiles for AOD. 1
