Calendar

May 20

CTS 2013 - The 2013 Intl. Conf. on Collaboration Techn. and Systems

May 22

Knowing (by) Designing 2013

May 27

13th Intl. Conf. on New Interfaces for Musical Expression

May 19

“ Design can be art. Design can be aesthetics. Design is so simple, that's why it is so complicated. ”

-- Paul Rand, 1997

Share this quote on...
Get more quotes via RSS or by joining our Usability Quote of the Day Facebook Page

Featured chapter

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

Read Steve's chapter !

Help us help you!

Spread the word:
Donate
Other ways to help

Antonio Siochi

Add description

← Button will not work: You have not enabled Javascript. How do I enable it?

Rename / change spelling

Add publication

← Button will not work: You have not enabled Javascript. How do I enable it?

Publications by Antonio Siochi (bibliography)

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.”

Add publication