- From: Jean Vanderdonckt <jean.vanderdonckt@uclouvain.be>
- Date: Tue, 29 Jan 2013 11:38:07 +0100
- To: 'Joëlle Coutaz' <joelle.coutaz@imag.fr>, <public-mbui@w3.org>
Dear Joëlle and Gaëlle, Thank you very much for presenting this clear view. Regarding UC3 "Car rental" case study, it has been decided to use it as a running example through all chapters. It is also our goal to provide several development paths for this example, thus finishing with different AUIs, CUIs, and FUIs. Some FUIs are sketches or mockups, some other are really running (we have screenshots or videos demonstrating their usage). What would be the best way to present this information to our audience in a way that they can clearly see the paths and the different AUIs, CUIs, and FUIs? Should we gather these "instantiations" in one single place or distribute them? Or something else? All the best, Jean -----Original Message----- From: Joëlle Coutaz [mailto:joelle.coutaz@imag.fr] Sent: mardi 29 janvier 2013 11:15 To: public-mbui@w3.org Subject: Selection of use cases for the Introduction Chapter Dear all, As planned at the last Telco meeting (thursday Jan. 24th 2013), - Gaelle and I propose a selection of one use case per cell for the recap table at the top of Section "Use Cases for MBUID. The other use cases will be suppressed from the introduction chapter but combined in an Annex. - We are expecting email exchanges between now and tonight so that we can start modifying the introduction document tomorrow. Below, we have listed four cells for which there are competing use cases. **** Cell Task&Concept-Design Time: actually, there are 2 use cases here : - UC3- "Car rental" provided by UCL. Motivation: it has been decided that it will be used as the running example for every chapter. - UC1- "Digital home" provided by ISTI. Motivation: it is well described, easy to understand, and very timely in the scientific, technical, and industrial communities. - Reasons for not selecting the other UCs: UC5 (Usability engineering) and UC10 (Learning HCI) are presented in generic terms; no screen dump of the FUI has been provided; UC12 (User modeling) is too complex. **** Cell Task&Concept-Run Time - UC4 "Minimalist UI" provided by DFKI. Motivation: it is well described, applies to large scale industrial domain, covers the "environment aspect" of the context of use. - Reasons for not selecting the other UCs: UC7-4(MASP). The concept of meta-UI is probably too complex to be grasped by readers newcomers in the field. In addition the UI is expressed in German, thus not accessible to any one. UC10 (dynamic composition of UI) is quite timely and well described, probably too advanced (academic) for readers newcomers in the field. Can be discussed in comparison with UC4. **** Cell Concrete UI-Design Time The 2 use cases proposed for this cell, UC6 (automotive industry approach) and UC11 (multi-device development tools) are generic descriptions/discussions about methods and tools respectively. They are not specific instances of either an approach used by such and such automative company for UC6, nor the description of a specific multi-device dev. tool. such as PhoneGap for UC11. In short, UC6 and UC11, as currently presented, are not use cases per se. Decisions have to be made by the group and/or by the contributors. **** Cell Final UI-Run Time - UC2 (migratory PACMan) demonstrates automatic total migration between devices. - UC7.2 (Tourism Web Site-TWS) demonstrates partial migration (UI redistribution) under human control by the way of a meta-UI. Both of them are well described. PACMAn is a well-known and very successful game, thus easy to understand by our readers. On the other hand, TWS is a representative of many web sites, and thus may have more interest to advanced readers. Decision has to be made by the group (vote). Best, --joelle and gaelle ************************************************************************* Joelle COUTAZ, Professeur émérite Lab. LIG (laboratoire d'Informatique de Grenoble) 41 rue des Mathématiques, 38400 St-Martin d'Hères, France, http://iihm.imag.fr/coutaz, tel. 33 4 76 51 48 54 *************************************************************************
Received on Tuesday, 29 January 2013 10:39:01 UTC