Différences

Ci-dessous, les différences entre deux révisions de la page.

--- ubinet_internship [2009/12/02 15:03]
tigli
+++ ubinet_internship [2009/12/02 15:22]
tigli
@@ Ligne 31: / Ligne 31: @@
 == Detailled Description: ==
-Ubiquitous Computing, introduced by Mark Weiser in 1991, raised many
+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
-challenges across computer science: in systems design and engineering,
+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.
-in systems modeling, and in user interface design. Initially the
-effective integration and interaction with the physical world sufficed
+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.
-to promote ubiquitous computing interest due to significantly increased
-real world visibility as well as real world control, towards ambient
+In order to to adress ubiquitous services continuity (Cf. French national research project CONTINUUM, http://continuum.unice.fr) in spite of such constraints, recent researches are moving towards an era of
-intelligence. But these first ubiquitous systems were often proofs of
+emergent middleware that is middleware that emerges at run-time to match the current operational environment and application requirements. The research group Rainbow focus on adaptive service oriented middleware
-concept with a single static configuration with a priori known devices.
+for ubiquitous computing (Cf. main recent publications). Contrary to most of the researches in this domain, Rainbow studies, proposes and validates contributions for a reactive adaptation, i.e. when the time for adaptation remain compatible with the continuous evolution of the ubiquitous environment. Its main contribution bases on the theory of the aspects of assembly (AA) to adapt reactively and independently assemblies of components in Service Component Architecture (SCA) for example.
-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.
-In order to to adress ubiquitous services continuity (Cf. French
-national research project CONTINUUM, http://continuum.unice.fr) in spite
-of such constraints, recent researches 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 research group Rainbow focus on adaptive service oriented middleware
-for ubiquitous computing (Cf. main recent publications).
-Contrary to most of the researches in this domain, Rainbow studies,
-proposes and validates contributions for a reactive adaptation, i.e.
-when the time for adaptation remain compatible with the continuous
-evolution of the ubiquitous environment.
-Its main contribution bases on the theory of the aspects of assembly
-(AA) to adapt reactively and independently assemblies of
-components in Service Component Architecture (SCA) for example.
 **Main objectives of the internship :**
-After a short survey on reactivity in adaptive middlewares, the students
+After a short survey on reactivity in adaptive middlewares, the students of this internship will study in details the evolution of the Aspects-oriented approaches to Aspect-oriented system architecture and more particulary to Aspect of assembly for component-based architectures.
-of this internship will study in details the evolution of the aspects oriented approaches
+Then student will highlight what features of such techniques are "common aspect-oriented concepts"
-to Aspect-oriented system architecture and more particulary to Aspect of Assembly for Component-based architecture.
-Student highlight what features of such techniques are "common aspect-oriented concepts"
 and what features are rather target architecture-specific (for example specific to component-based architecture for AA concept).
-Through Aspect-Oriented Modeling (AOM) he will extract such common characteristics from a perspective
+Through Aspect-Oriented Modeling (AOM) he will extract such common characteristics from a perspective that is at a more abstract level (i.e., target architecture-independent).
-that is at a more abstract level (i.e., target architecture-independent).
-After this first part
+After this first part he will able to describe a generic overall
 algorithms in the different steps

JY Tigli Homepages

Outils pour utilisateurs

Outils du site

Différences

Outils de la page