Number of co-authors:2
Number of publications with 3 favourite co-authors:Jane N. Mosier:4Jeffrey A. Fox:1
Sidney L. Smith's 3 most productive colleagues in number of publications:Jane N. Mosier:9Jeffrey A. Fox:3
Design can be art. Design can be aesthetics. Design is so simple, that's why it is so complicated.
-- Paul Rand, 1997
Read the fascinating history of Wearable Computing, told by its father, Steve Mann
Read Steve's chapter !
Sidney L. Smith
Publications by Sidney L. Smith (bibliography)
Fox, Jeffrey A. and Smith, Sidney L. (1989): Dynamic Rules for User Interface Design (DRUID). In: Proceedings of the Human Factors Society 33rd Annual Meeting 1989. p. 1143.
A well-designed user interface is important for the success and acceptance of any software product. Some experts believe that user interface design can be improved through the application of specific rules translated from general design guidelines. Derivation of design rules from guidelines can be aided by computer tools. But storing guidelines in a computer may offer no advantage over printed text unless the computer also provides aids for selecting and applying design guidelines. DRUID development has been sponsored by The MITRE Corporation as a tool for improving user interface design. DRUID is based on the 944 design guidelines proposed in Smith and Mosier's 1986 Guidelines for Designing User Interface Software. But DRUID's capabilities extend beyond that original text and provide further aids for user interface design. Initial DRUID capabilities demonstrated in 1988 support the review of design guidelines as an "electronic book", enabling a user to navigate through structured hypertext to find specific guidelines, to find functionally related guidelines, and to browse through guidelines at will. DRUID also permits ready retrieval of related guideline material by cross referencing and via a topical index. Newly developed DRUID capabilities extend that electronic book and move toward a computer-based design tool. DRUID users can now specify relevant guidelines for a system design application and rate the relative importance of those selected guidelines. Proposed future DRUID capabilities will provide functions to rate design compliance with those selected guidelines, to aid the translation of guidelines into specific design rules, and to develop rule-based templates to support modular design of user interface software. DRUID is implemented on the Apple Macintosh II computer with HyperCard software. The user interface for DRUID is designed to accommodate both expert and novice users. A DRUID user can accomplish sequence control either by pointing (via mouse) or by keyed command entries. DRUID computer aids promise to help expedite and reduce the cost of the development of user interface software. Those aids should also help improve the quality and consistency of user interface software through rule-based design.
© All rights reserved Fox and Smith and/or Human Factors Society
Smith, Sidney L. (1987): Authenticating Users by Word Association. In: Proceedings of the Human Factors Society 31st Annual Meeting 1987. pp. 135-138.
Testing word associations, as an extension of simple password entry, may be a practical means of verifying the identify of individual computer users. If each user specifies his/her own cue-response associations, then responses will be easy to remember. It should be easy for legitimate users to respond correctly to word association testing, but virtually impossible for potential intruders. Such testing should also prove easy for a computer to process.
© All rights reserved Smith and/or Human Factors Society
Mosier, Jane N. and Smith, Sidney L. (1986): Application of Guidelines for Designing User Interface Software. In Behaviour and Information Technology, 5 (1) pp. 39-46.
A survey was conducted of people who had received a report on guidelines for designing user interface software. Analysis of questionnaire responses indicates that respondents considered guidelines useful, that they have used guidelines in various stages of design, and that they plan to use guidelines again. However, respondents also reported significant problems in the practical application of guidelines. Respondents had difficulty locating relevant guidelines within the report, choosing which guidelines would actually be used, establishing priorities among the selected guidelines, and translating generally worded guidelines into specific design rules.
© All rights reserved Mosier and Smith and/or Taylor and Francis
Smith, Sidney L. (1986): Standards versus Guidelines for Designing User Interface Software. In Behaviour and Information Technology, 5 (1) pp. 47-61.
There are significant differences between designing hardware and software for the user interface to computer-based information systems. Formal standards may improve hardware design but may prove ineffective for aiding software design. Our present knowledge supports development of flexible design guidelines for user interface software, but does not justify imposition of standards. Effective application of guidelines will require a process of translation into system-specific design rules, and/or future incorporation into computer-based design algorithms.
© All rights reserved Smith and/or Taylor and Francis
Smith, Sidney L. and Mosier, Jane N. (1986). GUIDELINES FOR DESIGNING USER INTERFACE SOFTWARE, The MITRE Corporation, Bedford, Massachusetts, USA, Prepared for Deputy Commander for Development Plans, and Support Systems, Electronic Systems Division, AFSC, United States Air Force, Hanscom Air Force B.
This report offers guidelines for design of user interface software in six functional areas: data entry, data display, sequence control, user guidance, data transmission, and data protection. This report revises and extends previous compilations of design guidelines (cf. Smith and Mosier, 1984a).
If you are a teacher, a student, a human factors practitioner or researcher, these guidelines can serve as a starting point for the development and application of expert knowledge. But that is not the primary objective of this compilation. The guidelines are proposed here as a potential tool for designers of user interface software.
If you are a system analyst, you can review these guidelines to establish design requirements. If you are a software designer, you can consult these guidelines to derive the specific design rules appropriate for your particular system application. That translation from general guidelines to specific rules will help focus attention on critical user interface design questions early in the design process.
If you are a manager responsible for user interface software design, you may find in these guidelines a means to make the design process more efficient. Guidelines can help establish rules for coordinating individual design contributions, can help to make design decisions just once rather than leaving them to be made over and over again by individual designers, can help to define detailed design requirements and to evaluate user interface software in comparison with those requirements.
The design of user interface software will often involve a considerable investment of time and effort. Design guidelines can help ensure the value of that investment.
© All rights reserved Smith and Mosier and/or their publisher
Smith, Sidney L. and Mosier, Jane N. (1984): The User Interface to Computer-Based Information Systems: A Survey of Current Software Design Practice. In: Shackel, Brian (ed.) INTERACT 84 - 1st IFIP International Conference on Human-Computer Interaction September 4-7, 1984, London, UK. pp. 637-641.
From a survey of 201 people concerned with information system design, estimates for 83 systems indicate that on average 30-35 percent of operational software is devoted to the user-system interface (USI). In the design of USI software, survey responses indicate that improvements are needed in requirements definition, design documentation, and design guidelines.
© All rights reserved Smith and Mosier and/or North-Holland
Smith, Sidney L. and Mosier, Jane N. (1984): The User Interface to Computer-Based Information Systems: A Survey of Current Software Design Practice. In Behaviour and Information Technology, 3 (3) pp. 195-203.
From a survey of 201 people concerned with information-system design, estimates for 83 systems indicate that on average 30-35 per cent of operational software is devoted to the user-system interface (USI). In the design of USI software, survey responses indicate that improvements are needed in requirements definition, design documentation and design guidelines.
© All rights reserved Smith and Mosier and/or Taylor and Francis
Show this list on your homepage
Join the technology elite and advance:
Changes to this page (author)12 Oct 2011: Added21 Feb 2010: Modified
26 Jun 2007: Added
25 Jun 2007: Added
28 Apr 2003: Added
Page maintainer: The Editorial Team