Différences
Ci-dessous, les différences entre deux révisions de la page.
| Les deux révisions précédentes
Révision précédente
|
|
ctds09 [2009/10/01 10:01]
tigli |
ctds09 [2010/05/04 11:11] (Version actuelle)
tigli |
| === Abstract : === | === Abstract : === |
| |
| Ubiquitous Computing, introduced by Mark Weiser in 1991, raised many challenges across computer science: in systems design and engineering, in systems modeling, and in user interface design. Initially the effective integration and interaction with the physical world sufficed to promote ubiquitous computing interest due to significantly increased real world visibility as well as real world control, towards ambient intelligence. But these first ubiquitous systems were often proofs of concept with a single static configuration with a priori known devices. Today mobility of users and an increasing heterogeneity of devices introduce a new significant challenge for Middleware for ubiquitous computing. We witness to a kind of inversion in the classical software methodology where the software applications levels are much more stable and stationary than the software infrastructure level. The operational environment is then tightly connected with the real world but is also partly unknown at design time and is always changing at runtime in uncountable manner. | Ubiquitous Computing, introduced by Mark Weiser in 1991, raised many challenges across computer science : in systems design and engineering, in systems modeling, and in user interface design. Initially the effective integration and interaction with the physical world sufficed to promote ubiquitous computing interest due to significantly increased real world visibility as well as real world control, towards ambient intelligence. But these first ubiquitous systems were often proofs of concept with a single static configuration with previously known devices. Today the mobility of users and an increasing heterogeneity of devices introduce new significant challenges for Middleware in ubiquitous computing. We witness a kind of inversion in the classical software methodology where the levels of software applications are much more stable and stationary than the software infrastructure level. The operational environment is then tightly connected with the real world but is also partly unknown at design time and is always changing at runtime in uncountable manner. |
| | The first part of this talk will introduce a set of requirements, trends and open issues associated with middleware for ubiquitous computing in a dynamic real world. In the second part of this talk, the speaker will present an example of middleware for ubiquitous computing, called WComp, based on services for devices and three models for local composition (LCA), distributed composition (SLCA) and reactive adaptation (AA) using Aspects. Demonstrations on the platform WComp shall illustrate the various stages of this talk. |
| |
| Building on experience from work on service continuity for mobile workers in the French National research project CONTINUUM (continuum.unice.fr), the speaker will postulate that we are moving towards an era of emergent middleware that is middleware that emerges at run-time to match the current operational environment and application requirements. The first part of this talk will conclude with identifying a set of requirements, trends, open issues associated with middleware for ubiquitous computing in a dynamic real world. | |
| |
| In the second part of this talk, the speaker will present a new middleware for ubiquitous computing, called WComp, based on services for devices and three models for local composition (LCA), distributed composition (SLCA) and reactive adaptation (AA) using Aspects. Demonstrations on the platform WComp shall illustrate the various stages of this talk. | |
| |
| ==== Other Informations ==== | ==== Other Informations ==== |
