Appropriateness of user interfaces to tasks

ABSTRACT

In this paper we define the complex relation between task models and user interfaces in a declarative manner. We do this by describing how a task model can be transformed to other functionally equivalent task models, how it can be mapped to a user interface prototype, and how a user interface can be transformed to other functionally equivalent user interfaces. We use this relation in order to tackle the question whether a user interface is appropriate for a task, which leads us to a conceptual notion of usability. The user interfaces are modeled with form-oriented analysis.

REFERENCES

• 1: S. Balbo, N. Ozkan, and C. Paris. Choosing the right task modelling notation: A Taxonomy. In D. Diaper and N. Stanton, editors, The Handbook of Task Analysis for Human-Computer Interaction. Lawrence Erlbaum Associates, 2004.
• 2: H. Balzert. From OOA to GUIs: The JANUS System. JOOP, 8(9):43--47, 1996.
• 3: Tim Clerckx , Kris Luyten , Karin Coninx, The mapping problem back and forth: customizing dynamic models while preserving consistency, Proceedings of the 3rd annual conference on Task models and diagrams, November 15-16, 2004, Prague, Czech Republic [doi>10.1145/1045446.1045455]
• 4: Dirk Draheim , Gerald Weber, Form-Oriented Analysis, SpringerVerlag, 2004
• 5: David Frankel, Model Driven Architecture: Applying MDA to Enterprise Computing, John Wiley & Sons, Inc., New York, NY, 2002
• 6: D. Hollingsworth. The Workflow Reference Model. Technical Report Document Number TC00-1003, Workflow Management Coalition, January 1995.
• 7: International Organization for Standardization Ergonomic Requirements for Office Work with Visual Display Terminals (VDT) - Part 10: Dialogue Principles. ISO 9241--10, 1996.
• 8: Ivar Jacobson , Grady Booch , James Rumbaugh, The unified software development process, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1999
• 9: Ivar Jacobson, Object-Oriented Software Engineering: A Use Case Driven Approach, Addison Wesley Longman Publishing Co., Inc., Redwood City, CA, 2004
• 10: J. Miller and J. Mukerji. MDA Guide Version 1.0.1. Technical Report omg/2003-06-01, Object Management Group, 2003.
• 11: Fabio Paternò , Carmen Santoro, Preventing user errors by systematic analysis of deviations from the system task model, International Journal of Human-Computer Studies, v.56 n.2, p.225-245, February 2002 [doi>10.1006/ijhc.2001.0523]
• 12: P. Pinheiro da Silva. User Interface Declarative Models and Development Environments: A Survey. Lecture Notes in Computer Science, 1946:207--226.
• 13: Daniel Reichart , Peter Forbrig , Anke Dittmar, Task models as basis for requirements engineering and software execution, Proceedings of the 3rd annual conference on Task models and diagrams, November 15-16, 2004, Prague, Czech Republic [doi>10.1145/1045446.1045457]
• 14: D. Scapin and C. Pierret-Golbreich. Toward a Method for Task Description: MAD. Work with Display Units, (89), 1990.
• 15: August-Wilhelm Scheer, Aris-Business Process Modeling, Springer-Verlag New York, Inc., Secaucus, NJ, 2000
• 16: S. Wilson and P. Johnson. Bridging the generation gap: From work tasks to user interface designs. In J. Vanderdonckt, editor, Proceedings of CADUI'96 - Computer-Aided Design of User Interfaces, pages 77--94. Presses Universitaires de Namur, 1996.
• 17: S. Wilson, P. Johnson, C. Kelly, J. Cunningham, and P. Markopoulos. Beyond hacking: a model based approach to user interface design. In J. L. Alty, D. Diaper, and S. Guest, editors, People and Computers VIII, British Computer Society Conference Series, pages 217--231. Cambridge University Press, 1993.

INDEX TERMS

Keywords:
form-oriented analysis, model-based user interface development (MB-UID), task models, usability, use cases