Calendar

May 27

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

May 28

Graphics Interface 2013

May 29

Intl. Workshop on Design and Spontaneity in Computer-Supported Collaborative Learning (DS-CSCL 2013)

May 22

“ User error: replace user and press any key to continue. ”

-- Popular computer one-liner

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

J. B. Brooke

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 J. B. Brooke (bibliography)

1986

Edit | Del

Brooke, J. B. (1986): Usability Engineering in Office Product Development. In: Harrison, Michael D. and Monk, Andrew (eds.) Proceedings of the Second Conference of the British Computer Society Human Computer Interaction Specialist Group - People and Computers II August 23-26, 1986, University of York, UK. pp. 249-259.

“Applying human factors to the development of computer systems is often left to be something of an afterthought. The application of usability engineering techniques can provide a number of benefits in ensuring the improvement of the human factors of a software product. Firstly, usability is modified from a vague wish to a clear statement of measurable goals in product requirements. This helps both the human factors engineer and the product development team. Secondly, the human factors engineer and the product developers must work closely together to develop the goals, which ensures that as many constraining factors on usability as possible are taken into account -- for example, the feasibility of building certain sort of interfaces, the target user population, requirements for backwards compatibility with other products are all things which might affect what is judged to be "good" human factors in absolute terms. The statement of clear measurable usability goals also implies that the product must itself be subjected to usability testing. This procedure allows the human factors engineer to identify those flaws in the software system which cause the greatest usability problems. Experience in testing a variety of office systems has shown that the problems are usually "trivial" flaws in design or implementation. Nonetheless, these tend to compound with each other and interact to cause major usability problems. Basic conceptual problems seem to be rare.”

1980

Edit | Del

Brooke, J. B., Duncan, K. D. and Cooper, Caroline (1980): Interactive Instruction in Solving Fault-Finding Problems -- An Experimental Study. In International Journal of Man-Machine Studies, 12 (3) pp. 217-227.

“Two experiments are described which investigate the effects of providing information about the diagnostic process during training in fault diagnosis. This process information is presented by an interactive computer program. The experimental results demonstrate that some generalizable strategic learning takes place. This learning is apparently dependent on changes in the problem solving context during training.”

1978

Edit | Del

Brooke, J. B., Duncan, K. D. and Marshall, E. C. (1978): Interactive Instruction in Solving Fault Finding Problems. In International Journal of Man-Machine Studies, 10 (5) pp. 603-611.

“A training program is described which provides, during fault diagnosis, additional information about the relationship between the remaining faults and the available indicators. Since this information changes throughout the process of fault diagnosis, an interactive computer system seems to be the most suitable training implementation. The computer program developed for this purpose and the first results of experimental training are described.”

Add publication