Re: Selection of use cases for the Introduction Chapter

Hi,

I won't be able to join you tomorrow as I will be giving a talk in Nice.
and Gaelle will be teaching.

So, please do what the group thinks is useful for the documents.
Best,
--joelle
On 6 Feb 2013, at 17:40, Javier Rodriguez wrote:

> Dear all,
> 
> First of all, sorry for the delay in our response. We have been quite busy this last week and we are having technical difficulties to join the weekly audioconferences. 
> 
> In what regards to what it has been said about the Use Case 11: Multi-device development tools:
> 
> **** 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.
> 
> If you think it is appropriate, we can modify this section in order to provide a similar description, but more focused on MyMobileWeb platform. You can find a brief description about how MyMobileWeb applies MBUI at [1].
> 
> Best regards,
> 
> Javi
> 
> [1] http://www.w3.org/2005/Incubator/model-based-ui/XGR-mbui-20100504/#ideal2
>  
> 
> 2013/1/31 Jaroslav Pullmann <jaroslav.pullmann@fit.fraunhofer.de>
> 
>  Dear Joelle, dear all
> 
> please find my comments below:
> 
> 
> >> **** 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.
> 
> - the example provides an elaborated diagram of different model re-combinations,
>   though examples of corresponding "context information" and resulting adaptation scenarios
>   should be added
> 
> - I support the way to concretely/formally describe the artefacts in question
>   (informal list of) tasks and the domain model. Will the other layers/models be covered as well?
> 
> 
> >> - UC1- "Digital home" provided by ISTI. Motivation: it is well described, easy to understand, and very timely in the scientific, technical, and industrial communities.
> 
> - though this UC references usage of the task model, its "design-time" relevance is not apparent to me, does the
>   mentioned filtering of the underlying "nomadic CTT task model" take place at design or runtime ?
> 
> - the UC has a broad, general coverage of possible/prospective MBUI solutions for digital homes and uses often
>   a conditional langauge ("should/will be expressed..."). Possibly the focus could be narrowed to a single example
>   and have a final wording ?
> 
> 
> >> - 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;
> 
>  UC5 has a strong orientation on (high-level) models and early prototypes (generated out of these models). When
>  re-phrased, this could be a good UC candidate for TM/Design time perspective. It could elaborate on aspect of model
>  acquisition (how does domain/task analysis and usability consideration) map to e.g. task model, and aspect of (static)
>  model transformation and prototype generation ..
> 
> 
> 
> >>
> >> **** 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.
> 
> - I have some doubts whether there is any UC illustrating task model adaptation at runtime ?
>   UC4 describes the generation of an unified UI for a variety of devices and thus implies the usage of
>   different task models, but this aspect should be elaborated further ?
> 
> - proprietary models mentioned here should be mapped onto the MBUI/Cameleon-stack:
>       "dialog model"
>       "adaptation model" (adaptation rules)
>       "presentation model"
> 
> 
> 
> >> **** 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.
> 
>  Maybe UC5 is a candidate: prototype generation at design time (for the purpose of iterative development) ?
> 
> 
> **** Cell Concrete UI-Run Time
> 
>  - UC7.3 remains a strong candidate, though:
>  - the model diagram does not reflect the whole context of use: user (session data, gestures etc.)
>    and environment (interactive room, light conditions etc.)
>  - surprisingly the CUI-model (platform-dependent layer) is not being re-organized (branching only
>    at FUI (implementation language level) ?
> 
> 
> >>
> >> **** Cell Final UI-Run Time
> >> - UC2 (migratory PACMan) demonstrates automatic total migration between devices.
> 
>  - my vote for UC2
> 
>  Many thanks for your effort, best regards
>    Jaroslav
> 
> 
> 
> 
> 
> On 01/30/2013 07:45 PM, Joëlle Coutaz wrote:
> Hi,
> Except from Jean, I have not received any feedback to the email below. I need your input before I can start editing the introduction document.
> Best,
> --joelle
> 
> Begin forwarded message:
> 
> Resent-From: public-mbui@w3.org
> From: Joëlle Coutaz <joelle.coutaz@imag.fr>
> Subject: Selection of use cases for the Introduction Chapter
> Date: 29 January 2013 11:15:29 GMT+01:00
> To: public-mbui@w3.org
> 
> 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
> *************************************************************************
> 
> 
> 
> 
> *************************************************************************
> 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
> *************************************************************************
> 
> 
> 
> 
> -- 
> Jaroslav Pullmann
> Fraunhofer Institute for Applied Information Technology FIT
> Web Compliance Center: http://imergo.com/ · http://imergo.de/
> Schloss Birlinghoven, D-53757 Sankt Augustin, Germany
> Phone: +49-2241-142623 · Fax: +49-2241-142065
> 
> 
> 
> 
> -- 
> Javier Rodríguez Escolar
> 
> CTIC-Centro Tecnológico
> Investigador I+D+i - R&D Researcher
> Unidad de Movilidad e Independencia de Dispositivo
> Parque Científico y Tecnológico de Gijón
> c/ Ada Byron, 39 Edificio Centros Tecnológicos
> 33203 Gijón - Asturias - España
> Tel.: +34 984 29 12 12
> Fax: +34 984 39 06 12
> E-mail: javier.rodriguez@fundacionctic.org
> http://www.fundacionctic.org
> Política de Privacidad: http://www.fundacionctic.org/privacidad

*************************************************************************
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 Wednesday, 6 February 2013 17:01:59 UTC