文档下载 文档下载导航
设为首页 | 加入收藏
搜索 请输入内容:  
 导航当前位置: 文档下载 > 所有分类 > The nature of user interface design -- The role of domain knowledge
侵权投诉

The nature of user interface design -- The role of domain knowledge

The importance and growing awareness of domain knowledge acquisition in information systems development and, especially, in the process of design of human-computer interfaces, are becoming more evident. In several in-house development projects, methods for

Methods and tools for HCI development

The extension and limitation of what we call a domain is particularly interesting.The shifting foci on interface design from machine-ware, through single-user human-computer interfaces to the socio-technical environment [Grudin, 1990], suggests that thedomain should never be limited in a way that factors that could influence the perfor-mance of work with computer support risk being left out. Design guidelines, such asthe striving for consistency have, in various situations, been shown to attract attentionaway from the proper focus of user interface design, namely the user, the work task andthe understanding of the work domain [Grudin, 1989].

It is important to sense the differences in various development contexts such as in-house development, commercial products development and competitively bid contractprojects [Grudin, 1991]. In contract development, users are known from the outset, butthe development team is identified only after a contract has been awarded. In productdevelopment, developers are known from the outset but users can merely be identifiedafter the product has reached the market. In in-house development both users and deve-lopers are known from the outset. This implies that one of the prerequisites for an effi-cient development team – good representation from the domain – is fulfilled.

An early focus on users, through the use of interactive design, empirical measure-ment and iterative design to capture the domain knowledge is essential [Gould &Lewis, 1985]. By introducing a ”spiral” model of system development more efficientuser interfaces can be designed [Boehm, 1988]. Essential in this model are succeedingiterations to capture, interpret and refine the representations of domain knowledge,using prototyping techniques and user involvement. One framework for this view onsystem development is the task-artefact cycle [Carroll, 1991]. The purpose is to betterunderstand the tasks people are undertaking, and to apply this understanding in thedesign process. An important part of this understanding concerns the psychology of taskbehaviour. The task-artefact cycle approach also includes the fact that the use of an arte-fact in a work environment will redefine the tasks for which the artefact was originallydesigned.

1.1Domain Modelling and Domain-specific Design

Recent research within cognitive ergonomics stresses the importance of extending ouruser interface horizon beyond the visible user interface to designing users’ interactionswith domains [Fischer, 1993]. Knowledge about the importance of domain modellingdate back as far as Gibson [1977] who, among others, stressed that psychology should bethe study of the interaction between human beings and their environment. We are, ashuman beings, able to directly perceive the environment’s constraints and affordances(possibilities), which are necessary in order to be able to achieve our goals. Within thecognitive engineering approach, it is noted that the human is not a passive user of a com-puter program, but an active problem solver in some world [Woods & Roth, 1988]. InRasmussen & Vicente [1990], the importance of the work task as a fundamental unit inthe human-machine system is emphasised. Relating it to ecological psychology, domainanalysis could be described in terms of its affordances and constraints and the goals ofthe user as states of the domain [Vicente, 1990]. Information that the perceivers actuallyare using in their work is important to attain a valid domain model [Neisser, 1987].Domain modelling can also be useful for software engineering and should have itsgreatest impacts on software reuse [Arango & Prieto-Diaz, 1991].

In Gulliksen [1996], case handling models have been discussed in terms of a generalframework for capturing domain knowledge. These work activity specific domainmodels have proven to be not only essential, but a necessary prerequisite for, in order to40

上一页第2页

你可能喜欢

热门文档

相关文档

站点地图 | 文档上传 | 侵权投诉 | 手机版
本站所有资源均来自互联网,本站只负责收集和整理,均不承担任何法律责任,如有侵权等其它行为请联系我们.
文档下载 Copyright 2013 doc.guandang.net All Rights Reserved.  -  email