Identifying information requirements is a well-understood activity, but the practice of converting data into visual form based on these requirements is less defined. The Ecological Interface Design (EID) framework attempts to bridge this design gap by offering a set of visual design principles. While these principles supply high-level goals to be achieved by the display, they do not describe the design process per se. EID case studies tend to report the work domain analysis, the design solution and the relationship between these two artefacts. Unfortunately, the presentation of a final solution does not reveal the rationale for decisions made during the design process. This, coupled with the complexity of the systems involved, can make it difficult to transfer design knowledge to other work domains. Here a methodology is proposed to guide the design of visual interface components that make up an ecological display. A structured approach for matching requirements to visual form based on work domain analysis, task analysis, scale matching, and data transformations is presented. A case study reveals the rationale behind the redesign of a process control health reporting system using this methodology.
Keywords: Visual design; Ecological Interface Design; Decision support
Websites do not become usable just because their content is accessible. For people who are blind, the application of the W3C's Web Content Accessibility Guidelines (WCAG) often might not even make a significant difference in terms of efficiency, errors or satisfaction in website usage. This paper documents the development of nine guidelines to construct an enhanced text user interface (ETI) as an alternative to the graphical user interface (GUI). An experimental design with 39 blind participants executing a search and a navigation task on a website showed that with the ETI, blind users executed the search task significantly faster, committing fewer mistakes, rating it significantly better on subjective scales as well as when compared to the GUIs from other websites they had visited. However, performance did not improve with the ETI on the navigation task, the main reason presumed to be labeling problems. We conclude that the ETI is an improvement over the GUI, but that it cannot help in overcoming one major weakness of most websites: If users do not understand navigation labels, even the best user interface cannot help them navigate.
This paper analyzes the behavior of drivers using Adaptive Cruise Control (ACC) within the theoretical framawork of Human-Machine Cooperation. The study was carried out on a driving simulator. Driving task performance data and responses to a trust questionnaire were analyzed in order to examine the relationship between driver reliance on ACC and such intervening variables such as trust, perceived workload and perceived risk. The participants were divided into two groups according to their use of the ACC device during the experimental run. The results show thar high-use drivers seemed to cooperate more with ACC than low-use drivers, who tenders to perceive more risk and a higher workload. These findings are discussed in the light of Riley's theory of operator reliance on automation.
Give us your opinion! Do you have any comments/additions that you would like other visitors to see?
Yousay:
Mar 20th, 2010
#1
Be the first to add a thoughtful note to this page !
Changes to this page (periodical)
10 Sep 2009: Journal/Periodical was added to the bibliography (approved by an editor) 05 Jun 2009: Journal/Periodical was edited
05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 05 Jun 2009: Journal/Periodical was edited 14 Apr 2009: Journal/Periodical was edited (approved by an editor) 02 Feb 2009: Journal/Periodical was added to the bibliography (approved by an editor) 26 Aug 2008: Journal/Periodical was edited (approved by an editor) 16 Jun 2008: Journal/Periodical was added to the bibliography (approved by an editor) 12 May 2008: Journal/Periodical was edited 12 May 2008: Journal/Periodical was edited 12 May 2008: Journal/Periodical was edited 12 May 2008: Journal/Periodical was edited 12 May 2008: Journal/Periodical was edited 12 May 2008: Journal/Periodical was edited 12 May 2008: Journal/Periodical was edited 12 May 2008: Journal/Periodical was edited 12 May 2008: Journal/Periodical was edited 12 May 2008: Journal/Periodical was edited 12 May 2008: Journal/Periodical was edited 12 May 2008: Journal/Periodical was edited 12 May 2008: Journal/Periodical was edited 12 May 2008: Journal/Periodical was edited 12 May 2008: Journal/Periodical was edited 12 May 2008: Journal/Periodical was edited 12 May 2008: Journal/Periodical was edited 12 May 2008: Journal/Periodical was edited 12 May 2008: Journal/Periodical was edited 12 May 2008: Journal/Periodical was edited 12 May 2008: Journal/Periodical was edited 12 May 2008: Journal/Periodical was edited 12 May 2008: Journal/Periodical was edited 12 May 2008: Journal/Periodical was edited 12 May 2008: Journal/Periodical was edited 12 May 2008: Journal/Periodical was edited 12 May 2008: Journal/Periodical was edited 12 May 2008: Journal/Periodical was edited
Computer programs emerge as the outcome of complex human processes of cognition, communication and negotiation, which serve to establish the meaningful embedding of the computer system in its intended use context.