Contextual prototyping of user interfaces

Contextual development differs from traditional user interface development in several ways: It focuses on the context of usage and the user population rather than on the technical features required for interaction. However, the latter come into play when transforming context specifications into user-interface code. Contextual development also considers design to be a non-linear process based on activities (re)engineering work processes rather than performing traditional software-engineering tasks. Consequently, contextual development requires usage-relevant (re)presentation and execution mechanisms. Although the specification of task- and user-knowledge has been recognized to be crucial for contextual user interface design, seamless development support is still lacking. The reported TADEUS (Task Analysis/Design/End User Systems) project targets toward an environment that allows contextual and seamless design and prototyping based on user and task knowledge. Due to its model-based nature TADEUS is open with respect to diagrammatic notations for specification, and different interaction platforms. As a result, different perspectives on the context, development process and its results can be kept consistent throughout development.

[1]  Peter Johnson,et al.  ADEPT: Advanced Design Environment for Prototyping with Task Models , 1993, INTERCHI.

[2]  Christian Stary,et al.  Workflow-oriented prototyping for the development of interactive software , 1997, Proceedings Twenty-First Annual International Computer Software and Applications Conference (COMPSAC'97).

[3]  David E. Kieras,et al.  Using GOMS for user interface design and evaluation: which technique? , 1996, TCHI.

[4]  Eric Cheng,et al.  MOBILE: user-centered interface building , 1999, CHI '99.

[5]  Larry E. Wood,et al.  User Interface Design: Bridging the Gap from User Requirements to Design , 1997 .

[6]  Mary Beth Rosson,et al.  Integrating task and software development for object-oriented applications , 1995, CHI '95.

[7]  Chris W. Johnson,et al.  Interactors and Haggis: Executable specifications for interactive systems , 1997, DSV-IS.

[8]  Peter Johnson,et al.  Bridging the Generation Gap: From Work Tasks to User Interface Designs , 1996, CADUI.

[9]  Jean-Pierre Jacquot,et al.  Early Specification of User-Interfaces: Toward a Formal Approach , 1997, Proceedings of the (19th) International Conference on Software Engineering.

[10]  Karen Holtzblatt,et al.  Contextual design , 1997, INTR.

[11]  David W. Embley,et al.  A Seamless Model for Object-Oriented Systems Development , 1994, ISOOMS.

[12]  Markus F. Peschl,et al.  Representation still matters: Cognitive engineering and user interface design , 1998, Behav. Inf. Technol..

[13]  Yair Wand,et al.  Using objects for systems analysis , 1997, CACM.

[14]  Fabio Paternò,et al.  Deriving Presentations from Task Models , 1998, EHCI.

[15]  Kendall Scott,et al.  UML distilled - applying the standard object modeling language , 1997 .

[16]  Sidney C. Bailin,et al.  An object-oriented requirements specifications method , 1989, CACM.

[17]  David W. Embley,et al.  Object-oriented systems analysis - a model-driven approach , 1991, Yourdon Press Computing series.

[18]  Kee Yong Lim,et al.  The MUSE Method for Usability Engineering , 1997, INTERACT.

[19]  Dominique L. Scapin,et al.  Editing MAD* task descriptions for specifying user interfaces, at both semantic and presentation levels , 1997, DSV-IS.

[20]  Brad A. Myers,et al.  User interface software tools , 1995, TCHI.

[21]  James D. Foley,et al.  History, Results, and Bibliography of the User Interface Design Environment (UIDE), an Early Model-based System for User Interface Design and Implementation , 1994, DSV-IS.