1. Towards Ubiquitous Government Services through Adaptations with Context and Views in a Three-Tier Architecture Dan Hong, SC Cheung, SMIEEE Department of Computer Science HK University of Science & Technology {csdhong,scc}@cs.ust.hk Dickson K. W. CHIU SMIEEE Dickson Computer Systems Hong Kong dicksonchiu@ieee.org Eleanna Kafeza Department of Marketing and Communications, Athens University of Economics and Business kafeza@aueb.gr

2. Context HICSS40 - 2 Introduction Increasing demand for the extension of enterprise services to anytime and anywhere access Mobile devices have significantly inferior capabilities than those of desktop computers over the wired Internet Context become important User environment of operations Reduce user input Any information that can be used to characterize the situation of entities that are considered relevant to the interaction between a user and an application Big difference in software design Different user requirements under different context  Systematic context-based service adaptation  Three-tier views methodology

3. Context HICSS40 - 3 Extended Notion of Context Computing Contexts User Contexts Physical Contexts Available devices CPU Memory Screen size Energy Bandwidth … Preference Purpose User calendar Personal information Facilities Disability … Location Time Destination Traffic condition Physical limitations Weather …

4. Context HICSS40 - 4 u-Government services as pioneer? Motivated by our study in ubiquitous tourist services Largest number of possible users (citizens and visitors) Better governmental services help increase the productivity of the general public Access to various citizens’ contexts are relatively easy More trusted as compared with other private services. Local authorities (such as the city government) can host these services because they have the most resources or the best knowledge about local contexts After gathering the experiences government coordinate the access of citizens’ context legislation and enforcing legal civil usage.

5. Context HICSS40 - 5 System Architecture

6. Context HICSS40 - 6 A Meta-model for Context-aware Adaptation

7. Context HICSS40 - 7 Requirements elicitation methodology 1. Determine the different target groups of users 2. Estimate the typical contexts of these groups (especially those that possibly affect the system’s interactions) 3. For each of these contexts, enlist the requirements specific for the context. 4. For each service, see how different contexts (from step 2) may impact on its interactions and determine the required adaptation 5. For each context-aware feature, detail the desired context-aware capabilities. 6. Make sure that the context-aware capabilities match and satisfy all the requirements elicited from step 3. Otherwise, it would mean that some required context-aware feature are missing and we should re- iterate from step 5 to handle those unaddressed requirements.

8. Context HICSS40 - 8 View formulation methodology Design process views that capture typical sets of context- aware features for adaptation. Design data views for each of the data sources based on the requirements of the process views and context-aware capabilities. Design user interface views based on platform dependent restrictions. Validate view consistency (process algebra and automata theory) – see TSMC Part A, 33(6):725-741, 2003

9. Context HICSS40 - 9 Appointment service & Views for different adaptations (a) Original service process(b) Process view 1 (typical PDA browser) (c) Process view 2 (typical for WAP)(d) Process view 3 (typical for SMS) Authentication / Refresh Enter Service Request Show Options Select Request Mode Select Options Enter Counter- options Enter Constraints Receive Service Reply Confirm Service Details [ valid service allocation ] [ confirmed ] [ rejected ] [ passive mode ] [ counter-offer mode ] [ constraint mode ] Enter Service Request & Options Receive Service Reply Confirm Service Details [ confirmed ] [ reject ] [service not allocated ] Process view is a structurally correct subset of a process definition

10. Context HICSS40 - 10 User Interface Views for PDA users for WAP users

11. Context HICSS40 - 11 User Interface View Implementation Activity XML Processor XML Document Object Screen / Form Activity Presentation Object XSL Style Sheet XML Schemas User Inputs User Interface ViewWorkflow View

12. Context HICSS40 - 12 Data View vs. Complete Schema - Security and privacy - Exchange efficiency

13. Context HICSS40 - 13 Some notes on the effect of context Concentrate on the difference of the requirements for the ubiquitous users from those under standard browsers Identify similar or identical tasks to maximize reuse customize them with views instead of rewriting them Complete detailed service process is too complicated for a mobile environment Simplification of the process Reordering of work steps Task delegation to other personal / software agent Avoid error and security problems Difficult to tell if a user can tolerate a complex process user’s operating environment (e.g., lighting!) Preferences and mood 

14. Context HICSS40 - 14 Conclusion Even for simple and common services, adapting them toward a ubiquitous one is far more complex than previously expected Notion of extended context General experience in building context-aware services is new A meta-model and methodology Requirements elicitation for ubiquitous service design Three-tier view-based implementation of adaptations Just adapting UI is often inadequate => process view Contexts select the appropriate view for user execution View based approach facilitates systematic planning and deployment of such ubiquitous services in phases

15. Context HICSS40 - 15 Further and Ongoing work Ubiquitous requirement conflicts and implications Ubiquitous collaboration and agent-based computing MAIS architecture implementation Application in ubiquitous tourist assistance system

16. Context HICSS40 - 16 Q&A Thank you! Contact: dicksonchiu@ieee.org