1 / 15

agenda

agenda. Inleiding en stand van zaken WP1 Context: definition and specification Building Scenarios WP5: Designing Context-Sensitive User Interfaces WP6: Strong Code Mobility Plannen voor komend jaar Napraten, netwerking, drink … in faculty club. fase 1. fase 2. WP 1. WP1. WP 2 - 6.

monte
Télécharger la présentation

agenda

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. agenda • Inleiding en stand van zaken • WP1 • Context: definition and specification • Building Scenarios • WP5: Designing Context-Sensitive User Interfaces • WP6: Strong Code Mobility • Plannen voor komend jaar • Napraten, netwerking, drink … in faculty club

  2. fase 1 fase 2 WP 1 WP1 WP 2 - 6 WP 2 - 6 WP 7 WP 7 WP 8 WP 8 WP9 0 12 24 24 36 48 mijlpalen M m M m M Projectstructuur

  3. Projectplanning

  4. WP2: Context-Driven Implementation Generation • T2.3a: Implementation Generation Mechanism • Fully specify mechanism for automatically selecting model transformations from a set of alternatives • Also find additional criteria for selecting alternatives • Develop an initial approach for code generation • Research existing code generators • Implement a generic, standards-based code generator based on the researched techniques • Work towards a concrete language model to “glue” the already involved languages together • QVT transformations have to be linked to OWL constraints, etc.

  5. WP2: Context-Driven Implementation Generation • T2.4a: Tool support • Extend current CoCompose2 test-bed to integrate with all involved third-party tools: • JMI repository • QVT transformation engine • OWL models • RACER reasoning engine

  6. WP3: Modelling Java Workloads • From classical compiled binaries to Java • Instrumentation framework inside a virtual machine • Separation of concerns: • VM compilers • VM garbage collection • Gecompileerde Java-code • Acquire statistical profiles for Java applications • Delve further into memory/bandwidth problem • Suggestions are welcome

  7. WP4: Service composition and interaction • Functionality emerges from service interactions • Interaction between services to achieve a goal (user task support) • Creating inter-service cooperation • Requires context-awareness (awareness of other services) • Generic formalism for binding semantic information to services • Service cooperation mechanisms • Driving force behind inter-service cooperation • Ad hoc • Context information (user preferences, location, ...) • User task analysis (what is the current task of the user) • User-driven

  8. WP4: Adaptive services • Context-driven adaptation • Services should adapt to changes in the context they depend on • Resource changes • User-task and user-preference changes • Guaranteeing continuous user-task support = • Guaranteeing service availability • Taking into account: • resource availability • service dependencies (e.g. other services) • Requires middleware support • Resource-awareness • Fine-grained adaptation mechanisms (on software components) • Re-deployment of running services

  9. WP5: Adaptable UI • Model-Based User Interface Design • Static and dynamic contexts • Further implementation tool support • Further work on UML profile • User Profiling • Distributed User Interfaces • Use of different Interaction Resources in the environment • Static (design-time) and dynamic (run-time) • Tool support

  10. WP6: Code mobility • Strong Code Mobility • Finish implementation of AspectPicoo • Experiment with sophisticated remote references • E.g.: “rubberband pointers” • Progressive Mobility a.k.a. Application streaming • Move programs module by module: • Program keeps running while it is moving • Examine how to modularize software: • Partial ordering of code, execution overlap, push/pull, … • Results in high-level model for progressive code mobility

  11. WP6: Code mobility • Smart mobility • Virtual machines are everywhere! • E.g. XSLT interpreters • How can we enhance them to support code mobility? • Send code that extends the VM! • Identify minimal kernel required for code mobility • Define grammar for this abstract VM • Define extensions implementing abstract VM on target VMs • E.g. XSLT to annotate grammars • Result in high-level model for smart mobility

  12. WP7: current and future work • Formation of a workgroup: started today • A joint effort of all partners • Critical considerations of various scenarios • Locating feasible ideas • Implementing prototype(s) • Setting up collaborations between partners for integration of Tasks

  13. WP8: Valorisation • meetings with user commission • workshop January 2005: elaboration of scenarios • workshop April or May 2005: topic TBD • meeting after year 2, October 2005 • publications • ongoing effort • projects with industry

  14. agenda • Inleiding en stand van zaken • WP1 • Context: definition and specification • Building Scenarios • WP5: Designing Context-Sensitive User Interfaces • WP6: Strong Code Mobility • Plannen voor komend jaar • Napraten, netwerking, drink … in faculty club

  15. Vragen ?

More Related