380 likes | 542 Views
Supporting End-User Tailoring: Component-Based Approaches. Markus Won and Volker Wulf Institut für Angewandte Informationstechnologie der Fraunhofer Gesellschaft (FhG-FIT) and ProSEC, University of Bonn. Institutional Setting (1). GMD-FIT (Since: early 1990s) Adaptivity vs. Adaptability
E N D
Supporting End-User Tailoring: Component-Based Approaches Markus Won and Volker Wulf Institut für Angewandte Informationstechnologie der Fraunhofer Gesellschaft (FhG-FIT) and ProSEC, University of Bonn
Institutional Setting (1) • GMD-FIT (Since: early 1990s) • Adaptivity vs. Adaptability • Researchers: Reinhard Oppermann, Michael Paetau, Helmut Simm, Marcus Specht, Markus Eisenhauer • Publication • Oppermann, R. (ed.): Adaptive User Support – Ergonomic Design of Manually and Automatically Adaptable Software, LEA, Hillsdale, NJ 1994 • New focus on adaptive and situation-aware systems, especially in learning and mobility
Institutional Setting (2) • ProSEC at the University of Bonn (since: 1994) • Tailorability (of groupware) • Researchers: Helge Kahler, Volkmar Pipek, Oliver Stiemerling, Gunnar Stevens, Markus Won, Volker Wulf • Publications • Volker Wulf: Design of Tailorable Groupware: Habilitation Thesis, University of Hamburg 2000 • Helge Kahler: Supporting Collaborative Tailoring, PhD-Thesis at Roskilde University, Denmark, 2001 • Oliver Stiemerling: Component-based Tailorability, PhD-Thesis, University of Bonn 2000 • ... • Organizational Rearrangements • Fraunhofer FIT • University of Siegen • University of Bonn
Tailorability • Fields of application are differentiated and dynamically changing • Current tasks • Individual qualifications • Collaborative context • Tailorability is defined • changing aspects of an application‘s functionality • in a persistent way (by means of tailored artefacts) • during the use of an application (at runtime) • by users or local experts • Technical flexibility beyond • modifications of parameters • (re-)programming
Tailorability: Research Challenges (1) • Flexible Architecture • Rule based architectures • Component based architectures (simple and compound components) • Appropriate Interfaces • Vizualizing and manipulating tailored artefacts: 2D and 3D Interfaces • Describing tailored artefacts: Annotations, attaching examples • Understanding tailored artefacts: Exploration Environments • Providing support for tailoring: Integrity checking • Accessing tailoring functions: Direct Activation
Tailorability: Research Challenges (2) • Collaborative Tailoring • Technical infrastructure: Shared repository • Finding tailored artifacts: Naming and classifying • Localizing tailored artifacts: Access rights and views • Quality insurance of tailored artifacts: Identifying creators, (Collective) histories of use
Tailorability: Flexible Architectures • Rule based architectures • Component based architectures • Different tailoring modes • Architecture • Simple and Compound Components
My App‘ My App‘ My App My App Changing the set of components within a composition Changing the connections between components Adding new components to the existing set Re-programming a component‘s functionality Changing Parameters Component-Based Architectures • Properties of components • Independently developed parts of software • Independently exchangeable • Several components interact as one application or system
Server Client CAT-File Names =Applications InstantiateComponents Run-Time (Server) Run-Time (Client) CAT-File = Plan for Application CAT-Files Component Repository Rdsdkj Sdds Sd gghgh Dsds Dsd Sdhjhjhjk hgh The FREEVOLVE Platform: An architectural overview (1) List of Applications
The FREEVOLVE Platform: An architectural overview (2) Server Client • Tailor one application on the Client‘s or the Server‘s side • Client: Direct impact • Server: Next start • Save changes for next use Run-Time (Server) Run-Time (Client) Client Run-Time (Client)
Tailorability: Appropriate Interfaces • Vizualizing and manipulating tailored artefacts: 2D and 3D Interfaces • Describing tailored artefacts: Annotations, attaching examples • Providing support for tailoring: Integrity checking • Understanding tailored artefacts: Exploration Environments • Accessing tailoring functions: Direct Activation
Manipulating Tailored Artifacts: 2D-Environments • Search Tool for Groupware as an example • Tailoring mode very similar to the run-time mode • Abstract (compound) components prevent form too much complexity run-time Design
Tailorability: Appropriate Interfaces • Vizualizing and manipulating tailored artifacts: 2D and 3D Interfaces • Describing tailored artifacts: Annotations, attaching examples • Providing support for tailoring: Integrity checking • Understanding tailored artifacts: Exploration Environments • Accessing tailoring functions: Direct Activation
Integrity Checking: Ease Learning and prevention of failures • Additional Information (in XML) to • Components • Component Sets • Application templates • Tests on • Event Flows • Is all that is needed produced and bound? • Constraints • Are there dependencies between component‘s parameters? • Possible Results • Warnings • Help Texts and Improving Suggestions • Semi-automatic correction of failures (future work)
FREEVOLVE: The IntegrityTailoringClient • Easily tailoring and support by interactive integrity check • Different tailoring view modes (fully synchronized) • Binding are visualized • Properties of components or compound components • Schematical WYSIWIG view of the client application
Tailorability: Appropriate Interfaces • Vizualizing and manipulating tailored artifacts: 2D and 3D Interfaces • Describing tailored artifacts: Annotations, attaching examples • Providing support for tailoring: Integrity checking • Understanding tailored artifacts: Exploration Environments • Accessing tailoring functions: Direct Activation
Collaborative Tailoring • Technical infrastructure: Shared repository • Finding tailored artifacts: Naming and classifying • Localizing tailored artifacts: Access rights and views • Quality insurance of tailored artifacts: Identifying creators, (Collective) histories of use
Naming and classifyingtailored artifacts • Problems in a field study • names of the elementary components hardly indicated their meaning • appropriate components difficult to identify • Design Approach • more meaningful names for the elementary components • additional icons vizualizing elementary components in the menu • classification schemes for elementary and compound components • Experiences from the field test • hierarchy of the elementary components difficult to understand • lacking naming conventions for compound components • requirements for context specific display of components
Conclusion and Future Work • FreEvolve: Platform for component-based tailorability • Platform: Research prototype • Applications: Search tool, access control, chat tool, ... • Research challenges • Decomposition into „understandable“ components • Handling of complex compositions • Consistency of distributed tailoing activities • ... • Development of new applications with industry (research)
End User Development End User Development Kick off – Network of Excellence Examples for adaptive situation-aware systems CRUMPET SAiMotion
Crumpet CRUMPET CReation of User-friendly Mobile services PErsonalised for Tourism
CRUMPET Consortium: • Queen Mary University of London, UK (CO), • Emorphia Ltd (Nortel Networks), UK • European Media Lab, Germany • Fraunhofer FIT Inst. for Applied Information Technology, Germany • PTIN, Portugal • Sonera Ltd, Finland • University of Helsinki, Finland • CRUMPET is an EU-funded IST 5th framework project • Timeframe 1. Oct 2000 – 30. Sept 2002 + 2 months
Idea: adaptive, nomadic information system for tourism • CRUMPET has two main objectives: • To implement and trial tourism-related value-added services for nomadic usersacross mobile and fixed networks • To evaluate agent technology in terms of user-acceptability, performance and best-practiceas a suitable approach for fast creation of robust, scalable, seamlessly accessible nomadic services
Combined technologies Multi-agenttechnology Location - basedservices Personalized interaction Multi-media access via mobile devices
Vision • Trustworthy and ambient agencies for user's world-wide, wireless access to local services; • Personalised support for mobile users; • Location-aware support; • Exploitation of heterogeneous legacy services, which • cover a wide range of locations, • supply a wide range of supplementary, complementary, or even competitive services, • may differ in service features and qualities.
SAiMotion Situation Awareness in Motion next generation of mobile information guide system
Partners in SAiMotion: • Fraunhofer FIT, Sankt Augustin (Coordination) • Fraunhofer IGD, Rostock • Fraunhofer IAO, Stuttgart • Fraunhofer IZM, Berlin • Fraunhofer IIS, Erlangen • Fraunhofer IPSI, Darmstadt SAiMotion is a BMB+F project Timeframe 1. April 2001 – 31. March 2004
Idea: adaptive, nomadic information system for events (conference, fair...) Fair corporation offers innovative services for exhibitors and visitors Exhibitors have access to valuable tracking data and are within easy reach for the visitors Visitors manage a more efficient and and easy-going fair visit
SAiMotion-system • general support for visitors • quick overview • proactive information presentation • individual tours • references on exhibits/ exhibitors of personal interest
Performance features: situation-adapted services personalised: individualized tips and tours interest-driven: proactive information selection location-sensitive: quick guidance and overview course-support: general process support device-independent: optimal presentation on device
Situation awareness and Context • Context modeling is useful to reduce information overload and to adapt content and interaction • What should be taken into account? • Limitation of the system (boundaries of context (Lieberman & Selker; 2002) / purpose of system) • Metaphor • Location • Task • Social situation • Physical environment • History (of interaction/ of tasks/ knowledge) • User and system adapt to each other to share a common context