Group 1 Issues in CA adaptation J Matevska-Meyer

Group 1. “Issues in CA adaptation” J. Matevska-Meyer D. Ayed M. Sjölund P. Rigole G. Rey O. Virtanen

Main Issues 1. Representing Context • • • 2. Reasoning (from low-level to high-level) • 3. Identifying the relevant context Identifying the components to be adapted • 4. Deciding/choosing adaptation activities Mechanisms for actual adaptation: • • 5. Attributes (i. e. similar to metainformation) XML/database Ontologies Standards (CC/PP, OWL etc. ) Distribution History Static (i. e. design time) Runtime

Identifying the components to be adapted • • Deciding/choosing adaptation activities Who (signal to change) – – – Designer User (depends of the user), presented a list: adapt, don’t adapt The system • • • Environment (e. g. a nearby printer) An application Why – Change: • • • System Requirements (e. g. user) When – – • Asap The system decides its appropriate Where – Not in Norway…

Mechanisms for actual adaptation • Static (i. e. design time) – Context-aware deployment plan – Semantic compatibility (e. g. would the system satisfy its specification after adaptation) • Runtime – Context-aware deployment plan • Runtime information included – – Consistency checks Component replacement, deletion/addition Bindings replacement, deletion/addition Attribute tweaking

Open Issues • Structural change at runtime • Availability, persistency (e. g. keep state) • …