Dieses Dokuwiki verwendet ein von Anymorphic Webdesign erstelltes Thema.

Différences

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

Lien vers cette vue comparative

Les deux révisions précédentes Révision précédente
ubinet_internship [2009/12/02 15:22]
tigli
ubinet_internship [2009/12/02 17:14] (Version actuelle)
tigli
Ligne 31: Ligne 31:
 == Detailled Description:​ == == Detailled Description:​ ==
  
-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 +Ubiquitous Computing, introduced by Mark Weiser in 1991, raised many 
-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.+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.+Web service technology is a representative means of heterogeneous  
 +system integration and communication. Process language standards, such as  
 +WS-BPEL and WS-CDL, have accelerated the usability of web services in  
 +business area. However, recently emerging web service devices in ubiquitous  
 +environments still have a difficulty in coordinating their processes because of  
 +the limited computing power and storage. This research proposes a framework  
 +of event-based process enactment for ubiquitous web service devices. The  
 +framework adopts P2P architecture where devices communicate with one  
 +another via web services eventing. The schema of ECA rules and messaging  
 +protocol are presented for P2P process enactment so that service devices can  
 +interact each other and accomplish their process execution based on the ECA  
 +rules. Our proposed framework is expected to be useful in ubiquitous service  
 +environments since it enables a scalable and light-weighted process enactment  
 +through event-based web service technology. 
 + 
 + 
 +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.
  
-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 :** **Main objectives of the internship :**
  
-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+ 
-Then student will highlight what features of such techniques are "​common aspect-oriented concepts" ​+After a short survey on reactivity in adaptive middlewares,​ the students 
 +of this internship will study in details the evolution of Aspect-oriented system architecture and more particularyAspect of Assembly ​for Component-based ​architecture
 +Then the student will 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). ​ 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 perspective that is at a more abstract level (i.e., target architecture-independent)+After this first part,he will be able to propose :  
 +meta model of service for device and event-based process 
 +- different jointpoint models and corresponding weaving algorithms to react to appearing and disappearing services in the application. 
 +For examplejointpoint would be able to add contextual informations about the ports of the devices. In this case weaving process will  
 +be able to verify contextual constrains at runtime
  
-After this first part he will able to describe ​generic overall ​+The student ​will also consider the algorithmic costs of each weaving process, identifying ​formal performance model  
 +that will allow to compare various solutions.
  
-algorithms in the different steps +To illustrate these results, some algorithms ​would be tested
-(Pointcut Matching and Weaving Mecanism) of the AA application process.  +
-They will specifically study the algorithmic costs of each of these +
-steps  and will propose a formal performance model that will allow to +
-compare different policies in the application of AA. +
-To illustrate these results, some algorithms ​will  be able to be tested+
 in real experiments on the CONTINUUM platform, in collaboration with the in real experiments on the CONTINUUM platform, in collaboration with the
 research engineer of the project. research engineer of the project.
Ligne 71: Ligne 113:
 == Duration : == == Duration : ==
 4 to 6 months with possible continuation in PhD 4 to 6 months with possible continuation in PhD
 +
 +
 +
  
  
ubinet_internship.txt · Dernière modification: 2009/12/02 17:14 par tigli
Piste:
Dieses Dokuwiki verwendet ein von Anymorphic Webdesign erstelltes Thema.
CC Attribution-Noncommercial-Share Alike 3.0 Unported
www.chimeric.de Valid CSS Driven by DokuWiki do yourself a favour and use a real browser - get firefox!! Recent changes RSS feed Valid XHTML 1.0