Jun 19

... there are no simple 'right' answers for most web design questions (at least not for the important ones). What works is good, integrated design that fills a need--carefully thought out, well executed, and tested.

-- Steve Krug, Don't Make Me Think, p. 136

 
 

Featured chapter

Read the fascinating history of Wearable Computing, told by its father, Steve Mann

Read Steve's chapter !

 
 

Latest books

The Social Design of Technical Systems: Building technologies for communities
by Brian Whitworth and Adnan Ahmad

 
Start reading

The Encyclopedia of Human-Computer Interaction, 2nd Ed.
by Mads Soegaard and Rikke Friis Dam

 
Start reading
 
 

Help us help you!

 
 

Eric Smith

Add description
Add publication

Publications by Eric Smith (bibliography)

 what's this?
2003
 
Edit | Del

Baecker, Ronald M. and Smith, Eric (2003): Modularity and Hierarchical Structure in the Digital Video Lifecycle. In: Graphics Interface 2003 June 11-13, 2003, Halifax, Nova Scotia, Canada. pp. 217-224.

1996
 
Edit | Del

Baecker, Ronald M., Rosenthal, Alan J., Friedlander, Naomi, Smith, Eric and Cohen, Andrew (1996): A Multimedia System for Authoring Motion Pictures. In: ACM Multimedia 1996 1996. pp. 31-42.

1988
 
Edit | Del

Smith, Eric and Siochi, Antonio (1988): Software Usability: Requirements by Evaluation. In: Proceedings of the Human Factors Society 32nd Annual Meeting 1988. pp. 264-266.

Recent research has established the importance of defining usability requirements as part of the total requirements for a system. Instead of deciding in an ad hoc manner whether or not a human-computer interface is usable, measurable usability requirements are established at the outset. It is common to state such requirements in an operational manner: U% of a sample of the intended user population should accomplish T% of the benchmark tasks within M minutes and with no more than E errors. The formal experiments needed to test compliance with the requirements makes this method costly. This paper presents an alternative method of specifying usability requirements currently being developed and testing on a large software project at Virginia Tech. Briefly, usability requirements are specified by having every member of the software design team and the user interface design team specify the ease of use desired for each proposed functional requirement of the system under development. The individual ratings are then compared in order to arrive at a consensus. It is this consensus that leads to the formal usability requirements which the interface must meet or exceed. As the interface is built, it is rated in the same manner as that used originally to specify the requirements. This method thus provides a structured means of specifying measurable usability requirements and a means of determining whether or not the interface satisfies those requirements. Several other benefits of this method are presented as well.

© All rights reserved Smith and Siochi and/or Human Factors Society

 
Add publication
Show list on your website
 
 

Join the technology elite and advance:

 
1.

Your career

 
2.

Your network

 
 3.

Your skills

 
 
 
 
 
 

Changes to this page (author)

17 Jun 2009: Modified
25 Jun 2007: Modified
28 Apr 2003: Added

Page Information

Page maintainer: The Editorial Team
URL: http://www.interaction-design.org/references/authors/eric_smith.html
Jun 19

... there are no simple 'right' answers for most web design questions (at least not for the important ones). What works is good, integrated design that fills a need--carefully thought out, well executed, and tested.

-- Steve Krug, Don't Make Me Think, p. 136

 
 

Featured chapter

Read the fascinating history of Wearable Computing, told by its father, Steve Mann

Read Steve's chapter !

 
 

Latest books

The Social Design of Technical Systems: Building technologies for communities
by Brian Whitworth and Adnan Ahmad

 
Start reading

The Encyclopedia of Human-Computer Interaction, 2nd Ed.
by Mads Soegaard and Rikke Friis Dam

 
Start reading
 
 

Help us help you!