Computer-Aided Design of User Interfaces II: Proceedings of the Third International Conference on Computer-Aided Design of User Interfaces, 21–23 October, 1999, Louvain-la-Neuve, Belgium

356 Pages·1999·6.96 MB·English

by  Jean Vanderdonckt

Computer-Aided Design of User Interfaces II
Sponsors
BDE DeIRnECT.
Banque Bruxelles
Lambert
http://www.bbl.be Dell Computer Corp.
http://www.dell.be
Ü The British Council
The Bristish Council Fonds National de la
http://www.britcoun.org/belgium/ Recherche Scientifique
http://www.fnrs.be
Communaute Fran§aise ACM Chapter
de Belgique BelCHI
http://www.cfwb.be http ://belchi. qant. ucl. ac .be
Universite catholique
School of management a! UCL UCL de Louvain
Institut d'Administration et de Gestion http://www.ucl.ac.be
http://www.iag.ucl.ac.be/iag/ University
catholique
deLouvain
Official CADUI WWW site: http://belchi.qant.ucl.ac.be/cadui
COMPUTER-AIDED DESIGN
OF USER INTERFACES II
Proceedings of the Third International Conference on
Computer-Aided Design of User Interfaces,
21-23 October, 1999, Louvain-la-Neuve, Belgium
edited by
Jean Vanderdonckt
Universite catholique de Louvain,
Louvain-la-Neuve, Belgium
and
Angel Puerta
Stanford University,
Stanford, California, U.S.A.
SPRINGER-SCIENCE+BUSINESS MEDIA, B.V.
A CLP. Catalogue record for this book is availabel from the Library of Congress.
ISBN 978-94-010-5861-2 ISBN 978-94-011-4295-3 (eBook)
DOI 10.1007/978-94-011-4295-3
Printed on acid-free paper
All Rights Reserved
© 1999 Springer Science+Business Media Dordrecht
Originally published by Kluwer Academci Publishers in 1999
Softcover reprint of the hardcover 1st edition 1999
No part of the material protected by this copyright notice may be reproduced or
utilized in any form or by any means, electronic or mechanical,
including photocopying, recording or by any information storage and
retrieval system, without written permission from the copyright owner.
TABLE OF CONTENTS
Preface-Introductionto Computer-AidedDesign ofUserInterfuces 1
J VanderdoncktandA. Puerta
Program CommitteeMembers 6
Invited speakers
1. Modeling for ComponentBasedDevelopmentin UMLlCatalysis 7
A.C. Wills
2. TheoryBased Design: From Individual Users and
Tasksto Collaborative Systems 21
P. Johnson
3. EvaluatingAccessibilityand Usability ofWeb Pages 33
M. Cooper
Model-Based User Interface Development Environments
4. Model-Based Design ofUser Interfaces Using Object-Z 43
A. Hussey andD. Carrington
5. A Method Engineering Frameworkfor Modelingand
Generating Interactive Applications 57
Ch. Martin
6. GIPSE, A Model-Based System for CAD Software 61
G. PatryandP. Girard
7. Visto: A More DeclarativeGill Framework 73
K. Aerts
8. Beyond Automatic Generation-ExploratoryApproachto ill Design.....79
S. Kovacevic
9. Using Application Domain Specific Run-Time Systems and
Lightweight UserInterface Models -A Novel Approach for CADill....97
E. Nilsson
lO.XXL: A Visual+Textual Environmentfor Building
Graphical UserInterfaces 115
E. Lecolinet
Linking and Deriving Models
II.Semi-Automated LinkingofUser Interface DesignArtifacts 127
S.S. ElnaffarandN Graham
12.TheTeallachTool: Using Models for Flexible UserInterfaceDesign. 139
P.J Barclay, T. Griffiths. J McKirdy, N W Paton, R. Cooper, and
J Kennedy
vi
13.MDL: ALanguagefor Binding User-Interface Models 159
R.E.K. Stirewalt
Windows management
14.VanishingWindows: An Empirical Study ofAdaptiveWindow
Management 171
T. Miah andJL. Alty
15.AdaptiveLayoutCalculationinGraphical UserInterfaces:
ARetrospective onthe A2DL-Project 185
S. Stil/eandR. Ernst
16.SemanticDifferences Between UserInterfacePlatforms
Relevanceto Designand Re-DesignofUserInterface 199
MB. Harning
Design Frameworks and Objects
17. A Framework for Management of Sophisticated User Interface's
Variants in Design Process:
ACase Study 205
P. Savolainen andH Konttinen
18.GRASYLA: Modelling CaseTool GUIs in MetaCases 217
V EnglebertandJ -L. Hainaut
19.User DefinedObjects are FirstClass Citizen 231
G. Texier andL. Guittet
Supporting Task-Based Design
20.The Visual TaskModel Builder.. 245
M Biere, B. Bomsdorf, andG. Szwillus
21.Computer-Aided Analysis ofCooperative Applications 257
G. Bal/ardin, C. Mancini andF Paterno
22.Methodological andTool SupportforaTask-Oriented 271
DevelopmentofInteractive Systems
A. DittmarandP. Forbrig
23.ModellingWork: Workflowand Task Modelling 275
H Trretteberg
vii
Computer-Aided Design ofUserInterfaces
24.AGeneric Frameworkbasedon Ergonomics Rules for
ComputerAided DesignofUserInterface 281
Ch. Farenc andPh. Palanque
25.CMF: A CoherentModelling Framework for
Task-Based UserInterfaceDesign 293
B. BomsdorfandG. Szwillus,
26.Towel: Real World Mobility onthe Web 305
S. Harper, R. Stevens, andC. Goble
27.Tool-Based Supportfor User-Designer Collaboration
in Distributed User Interface Design and Evaluation 313
J Sarkkinen
Computer-Aided Evaluation ofUser Interfaces
28.An Approach ofComputer-Aided ChoiceofUI
Evaluation Criteriaand Methods 319
A. Nendjo Ella, Ch. Kolski, F Wawak, C. Jacques, andP. Yim
29.Considerating Subjectivity in Software Evaluation-
Application for Teachware Evaluations 331
0. Hfi, Ph. Trigano, andS. Crozat
30.KALDI: AComputer-Aided Usability EngineeringTool for
SupportingTestingand Analysis ofHuman-ComputerInteraction 337
G. Al-Qaimari andD. McRostie
Preface
INTRODUCTION TO COMPUTER-AIDED
DESIGN OF USER INTERFACES
Jean Vanderdoncktl and Angel Puerta2
,3
Jlnstitutd'AdministrationetdeGestion-UniversitecatholiquedeLouvain
PlacedesDoyens, 1-B-1348Louvain-la-Neuve(Belgium)
vanderdonckt@gant,ucl.ac,be,vanderdoncktj@acm,org
Web: http://www.arpuerta.com
JKnowledgeSystemsLaboratory, StanfordUniversity, MSOBx215
Stanford, CA 94305-5479, USA
[email protected]
3RedWhaieCorp., 277Town &Country Village
PaloAlto, CA 94303, USA
[email protected]
Web: http://www.redwhale.com
Computer-Aided Design of Vser Interfaces (CADUI) is hereby referred
to as the particular area of Human-Computer Interaction (HCI) intended to
provide software support for any activity involved in the development life
cycle of an interactive application, Such activities namely include task
analysis, contextual inquiry [l], requirements definition, user-centreddesign,
application modelling, conceptual design, prototyping, programming, in
stallation, test, evaluation, maintenance, Although very recently addressed
(e.g., [3]), the activity ofre-designing an existing user interface (VI) for an
interactive application and the activity of re-engineering a VI to rebuild its
underlying models are alsoconsidered inCADVI.
A fundamental aim ofCADVI is not only to provide some software sup
port to the above activities, but also to incorporate strong and solid meth
odological aspects into the development, thus fostering abstraction reflection
and leaving ad hoc development aside [5,7]. Incorporating such methodo
logical aspects inevitably coversthree related, sometimes intertwined, facets:
models, method and tools. Today, any sound methodology should propose
some method founded on models and supportedby appropriatetools [2].
1
2 VanderdoncktandPuerta
Models are intended to capture, to characterise and to abstract real-world
informationthat will leadtoa future VI. As every model is builton some ab
straction mechanisms, it usually consists in a partial view of the real world
with respect to the design problems. Consequently, one or several models
may be required. Information is primarily stored into models according to an
appropriate format allowing a computer-based system or an automata to so
manipulate them, to access them, to retrieve them, to update them, to man
age them. Several types ofmodelscanbe imagined [6,7] (Fig. 1).
.=J ••u.na,...."..
hJ. ..., I
~
Generated UI n01
Figure1. Philosophyofamodel-basedapproach.
A Task model is used to describe the tasks the end-user has to perform.
Goals in a task model specify when a desired state is met, methods describe
procedures to achieve a goal, where atomic methods achieve a goal in one
stepandcomposite methodsdecomposeagoal into sub-goals.
A Data model is used to abstract the data semantics to be manipulated
throughout the VI input/output. It usually consists in aconceptual schema of
entities, relationships ofa particular design problem or ofobjects and meth
ods in an object-orienteddefinition.
A Control model is to specify the services an application provides. It is
mostly object-oriented; objects capture the state of entities and the opera
tions change the state of objects. It is important that the operations corre
spondto theatomic methods specified in thetask model.
A Presentation model specifies the object and operation appearance, the
hierarchical decomposition of displays into components, the attributes and
layout ofeach component.
A Conversation model is used to describe the human-computer conver
sation. It describes when the end-usercan invoke commands, select or spec
ify inputs and when the computer can query the end-user and presents in
formation.
Introduction to Computer-AidedDesignofUserInteifaces 3
A Behaviour model is sometimes used to specify the input behaviour.
The use of a presentation model and a behaviour model allows specifying
the layoutand thedynamic behaviouroftheuser interfaceindependently.
A Platform model can be used to describe platform characteristics, e.g.,
input devices, output devices. This type of model is particularly appropriate
for CADVIsystems intendedto producemulti-platformVIs.
An Environment model can describe workplace characteristics, e.g., cul
tural characteristics, environment factors. These models are used in different
ways.
A User model specifies the end-usercharacteristics. A user model can be
used in order to generate individual user interfaces (adapted to stereotypes),
to reconfigure the interface to the end-user, to provide adaptive user inter
faces, to provide an appropriate level ofhelp, to actively guide the user dur
inginteraction.
Development activities areorganised into a structured way called Method
(the second facet of a methodology) so that they can share common defini
tions and languages, they can share the same kind of information, they can
be reproduced equally and communicated in the same way. A method is
generally founded on one orseveral models. This foundation is referred to in
the literature as a Model-Based Approach to produce a final VI [5,9]. A
model can underlie one particular development activity or be shared among
several ofthem.
Among all these models, the task model has today gained much attention
and many acceptances in the scientific community to be the model from
which a development should be initiated. In the model-based approach (Fig.
1), one or several models, possibly including a task model, are exploited to
reach a final VI, sometimes with variants obtained by varying the considered
models parameters (e.g., user profiles, user preferences, design options).
Rather, in the Task-Based Approach, at least one model, the task model, is
exploited to feed in the other models in a particular way that is taskdepend
ent orcontext-dependent (Fig. 2).
""3~
GeneratedVI
Figure2. Philosophyofatask-basedapproach.