User-interface modelling--adding usability to use cases

User interface modelling (UIM) is basically a method for gathering user requirements that are applicable when designing the user interface to an information system. UIM is to be used as a complement to use case modelling (Jacobson, Christerson, Jonsson & Overgaard, 1992) in the system development process. An actor model, a goal model and a work model are specified during sessions where the end-users cooperate with software engineers and user-interface designers. The actor model is a description of characteristics for each category of users. The goal model is a list of high-level goals the users want to achieve. The work model is a specification of work situations, information objects and actions, and properties of attributes and operations, suitable for the design. UIM does not describe a step-by-step procedure on how to create usable interfaces. Interface design is partially a creative process than cannot be completely described with a method. However, the design process can be facilitated if the design decisions are based on a substantial model defining the users' requirements for the user interface. This model is created during UIM sessions.The method has been tested in different development projects at the Swedish National Tax Board. It has been shown to provide useful input to the user-interface design process.

[1]  Larry L. Constantine,et al.  Essential modeling: use cases for user interfaces , 1995, INTR.

[2]  Jean Scholtz,et al.  Systematic creativity: a methodology for integrating user, market and engineering requirements for product definition, design and usability testing , 1995, EHCI.

[3]  W. Buxton.  Human-Computer Interaction , 1988, Springer Berlin Heidelberg.

[4]  Magnus Lif.  User Interface Modeling for the Design of Administrative Information Systems , 1997, HCI.

[5]  Allen Newell,et al.  The psychology of human-computer interaction , 1983 .

[6]  Mats Lind,et al.  Analysis of Information Utilization (AIU) , 1997, Int. J. Hum. Comput. Interact..

[7]  Richard M. Young,et al.  Options and Criteria: Elements of design space analysis , 1991 .

[8]  Ivar Jacobson,et al.  Object-oriented software engineering - a use case driven approach , 1993, TOOLS.

[9]  Morten Kyng,et al.  Design at Work , 1992 .

[10]  Ben Shneiderman,et al.  Designing the User Interface: Strategies for Effective Human-Computer Interaction , 1998 .

[11]  Christiane Floyd,et al.  A Comparative Evaluation of System Development Methods , 1986, Information Systems Design Methodologies: Improving the Practice.

[12]  Christiane Floyd,et al.  Outline of a Paradigm Change in Software Engineering , 1993 .

[13]  Ergonomic requirements for office work with visual display terminals ( VDTs ) — Part 11 : Guidance on usability , 1998 .

[14]  Alistair G. Sutcliffe,et al.  Integrating Human Computer Interaction with Jackson System Development , 1991, Comput. J..

[15]  Mats Lind,et al.  Efficient development of organisations and information technology - a design approach , 1995 .

[16]  Ivar Jacobson,et al.  Object-Oriented Software Engineering , 1991, TOOLS.

[17]  Tom Dayton,et al.  Participatory Practices in the Software Lifecycle , 1997 .

[18]  R. Rapoport.  Three Dilemmas in Action Research , 1970 .

[19]  Clayton Lewis,et al.  Making usable, useful, productivity-enhancing computer applications , 1991, CACM.

[20]  David Benyon,et al.  The Role of Task Analysis in Systems Design , 1992, Interact. Comput..

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

[22]  Jonathan Grudin,et al.  Interactive systems: bridging the gaps between developers and users , 1991, Computer.