1 / 16

ON RUN-TIME BEHAVIOURAL ADAPTATION IN CONTEXT-AWARE SYSTEMS

ON RUN-TIME BEHAVIOURAL ADAPTATION IN CONTEXT-AWARE SYSTEMS. Javier Cámara, Gwen Salaün, Carlos Canal GISUM – Deptartamento de Lenguajes y Ciencias de la Computación Universidad de Málaga M-ADAPT'07 1st ECOOP Workshop on Model-Driven Software Adaptation Berlin, Germany, 30th of July 2007.

ina-townsend
Download Presentation

ON RUN-TIME BEHAVIOURAL ADAPTATION IN CONTEXT-AWARE SYSTEMS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ON RUN-TIME BEHAVIOURAL ADAPTATION IN CONTEXT-AWARE SYSTEMS Javier Cámara, Gwen Salaün, Carlos Canal GISUM – Deptartamento de Lenguajes y Ciencias de la Computación Universidad de Málaga M-ADAPT'071st ECOOP Workshop on Model-Driven Software Adaptation Berlin, Germany, 30th of July 2007

  2. Index • Introduction • Case Study: Wireless Medical Information System • Issues in Context-aware, Run-time Adaptation • Proposal • Conclusion and Open Issues

  3. Introduction - COTS • COTS products offer specific functionality needed by larger systems into which they are incorporated. • Promote reusability. • Reduction of development costs and time. But: • COTS products cannot be directly reused (interoperability problems or mismatch among components). • Require customized adaptation.

  4. Introduction - Interoperability Levels • Signature Level: Interface descriptions including methods or services that an entity either offers or requires. • Protocol or Behavioural Level: describes the interactive behaviour that a component follows. • Service Level: groups other sources of mismatch related with non-functional properties (temporal requirements, security, etc.) • Semantic Level: This level describes what the component actually does.

  5. Introduction - Software Adaptation Software Adaptation is characterized by: • Highly dynamic run-time procedures. • Modification or extension of application behaviour. • Extensive use of software adaptors ( special software components with the purpose of solving interoperability problems between other software components). • Adaptors are built from a description of how mismatch between components can be worked out (mapping).

  6. Case Study: Wireless Medical Information System

  7. Issues • Context-Aware computing studies the development of systems which exploit context information (e.g., user location, network resources, time, etc.). • The execution context of the system is likely to change at run-time. • Adaptation policies in most proposals in software adaptation are fixed.

  8. Issues • Need of Run-time modifiable adaptation policies dependent on the current state of the context of the system. • Context is complex: depends on many (potentially interrelated) variables  Complexity in mapping specification. • Interoperability Issues: • Name mismatch. • 1-to-many interaction • … • Context-triggered actions. • Reconfiguration of the system.

  9. Proposal Composition Engine. Acts as an “Interpreter” deciding which messages to issue depending on context state and mapping information.

  10. Proposal – Component Interfaces and Execution Environment

  11. Proposal – Mapping – Synchronisation Vectors

  12. Proposal – Mapping – Vector Selection ACTIVE VECTORS vlid vlin vlo vebl vqry vresp vconn vptr vltr vup GLOBAL vlid vresp vlin vlo vptr vqry vltr vup

  13. Proposal – Composition Algorithm

  14. Proposal – Mapping – Synchronisation Vectors

  15. Conclusions and Open Issues • Approach to the composition of mismatching components in systems where behaviour may be affected by context. • Run-time composition and Separation of Concerns enable and simplify context-aware adaptation. • Implementation using Dynamic AOP (Prose?). • Reconfiguration.

  16. Thanks for your time and attention!

More Related