S.L. Smith, J.N. Mosier, "Guidelines for Designing User Interface Software," Technical Report, The MITRE Corporation ESD-TR-86-278, 1986.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....complete system should only use one algorithm for abbreviating long names, whatever that algorithm. However, there are plenty of approved principles to deploy (including algorithms for abbreviations) and there is rarely any need to diverge from conventional principles. The reader is referred to [11] for a substantial collection of principles. Here we give a very brief list, omitting such obvious principles as providing rapid feedback to the user s actions. Notice how principles are not necessarily consistent with each other in the limit: the designer has to seek resolutions dependent on ....

S. L. Smith & J. N. Mosier, Guidelines for Designing User Interface Software, Technical Report NTIS No. A177 198, Hanscom Air Force Base, MA. >A massive compendium of user interface design guidelines. This collection has been repeatedly revised in the light of new studies: more recent editions may be available.

....and specific to Web pages. 3.1 On Line documentation tools Tools for WIMP User Interfaces. A large part of on line tools for working with guidelines are hypermedia version of establish paper documents. Representative examples are HyperSam [10] which presents the Smith and Mosier guidelines [20], Cohen s MIL STK 1472 [2] which integrates a military standard, and Sierra [22] which is an hypermedia tool for managing guidelines. These tools are generally structured like their existing paper counterparts. Their main characteristics are that they provide functionalities that allow easier ....

Smith S.L., Mosier J.N.: Guidelines for designing user interface software. Report EDS-TR86 -278. The MITRE Corporation, Bedford (1986)

....of the user. When the user has to compare things the number 7 plus or minus 2 is a good guideline [6] but for localizing tasks where the user knows what to look for this number can be much higher, assuming the search space is in some way structured and the user knows or understands the structure[23]. The question remains if the concept of having many toolbars is bad per se or that users are just not prevented from abusing them. In a WIMP interface the fact that the button is visible is the only guarantee that the button can be selected so visibility is closely related to enabling or ....

Smith and Mosier (1986), Guidelines for Designing User Interface Software, MITRE, 1986

....influence our physical abilities of communication with the environment. 5.1.2. Guidelines Conventional guidelines are necessary to create a common platform, within as well as between ap HELIOS Supplement to Comput. Methods Programs Biomed. 7 plications. Se for instance [11] 12] 13] 15] [16], 17] for examples. General guidelines, however, often prove to be too general to serve as a solution to a specific design problem. They can provide very detailed rules on low design level, which of course is good and necessary, but they don t provide enough of the information required at the ....

Smith Sidney L., Mosier Jane N., Guidelines for Designing User Interface Software, 1986, U.S. DEPARTMENT OF COMMERCE NTIS, Springfield.

....usability resources through the process shown in Figure 1. A key component of the methodology is a hierarchical structure of usability guidelines delivered in the GUIDE tool shown in Figure 2. We have chosen to seed our repository with a Web enhanced Smith and Mosier 944 guidelines corpus [16], although any set of initial guidelines would work equally well. 1 A rule based system is then used to match project characteristics (user populations, tasks, GUI tools, etc. to specific usability resources that project personnel should apply during development. The result is a set of project ....

S. L. Smith and J. N. Mosier, " Guidelines for Designing User Interface Software ," Technical Report, The MITRE Corporation ESD-TR-86-278, 1986.

....platforms that instruct one to use specific widgets for specific purposes; for example, a push button widget in dialogue screens should be used only for application operations. Application programmers can choose to either follow these guidelines or not. Often the guidelines are so exhaustive [Smith and Mosier, 1986] that there are too many things for average people to recollect. In Figure 9 a conceptual model of application layers is presented. It depends on the application, the operating environment and the user interface toolkit which parts of the model are defined by the application and which are defined ....

Sidney L. Smith and Jane N. Mosier, Guidelines for designing user interface software, Technical Report ESD-TR-86-278. Mitre, August 1986. Available as ftp://archive.cis.ohio-state.edu/pub/hci/Guidelines.

....simply reporting his conclusion and the reason he gave) With only a specification document at hand a think aloud study could not be arranged, and without access to the source code of the Builder he could not use Programmable User Model (Howes Young, 1991) as his evaluation technique. Guidelines (Smith Mosier, 1986) was a viable option, but he found it too difficult, as too much reading would have been necessary to acquire the expertise to apply guidelines to the specification document. Because of these constraints, he thought CW the most appropriate choice. A1 s later notes focused more explicitly on the ....

Smith, S.L., & Mosier, J.N. (1986). Guidelines for Designing User Interface Software. ESD-TR-86-278. Bedford, MA: MITRE Corporation.

....major issues: Graphic user interfaces subject to the guidelines that have been developed over the years. The usual issues of uniformity in style of layout, presentation, vocabulary, use of color, and so on apply, and human factors design may be modeled on existing practice (Shneiderman, 1983; Smith and Mosier, 1986; Shackel and Richardson, 1991) Typography, layout and visualization which have human factors guidelines arising in graphic design and information visualization (Bertin, 1983; Tutte, 1990) Hypermedia navigation where issues such as cognitive overload in hyperspace navigation, and the ....

Smith, S.L. and Mosier, J.N. (1986). Guidelines for Designing User Interface Software. Mitre Corporation. ESD-TR-86-278.

....is presented to the designer is through sets of guidelines, and a wide range of handbooks and text books. Guidelines are based on examination of the extensive research literature available on human computer interaction and, very often, on the experience of the particular authors (for example [23]) They encompass, or at least try to encompass, all the approaches above in presenting to the designer a comprehensive guide to the design of the user interface. Their main advantage is that the designer is freed from having to sift through the extensive literature on user interface design. ....

....tools. 6 3.1 A Guideline Review of a Language Based Editor By comparing the existing or proposed user interface of a software tool with a typical set of guidelines, it is possible to gauge the extent to which the tool conforms to the guidelines. In [29] such an assessment using guidelines from [23] and the language based editor UQ1 [36] was reported. Of the 944 guidelines contained in the guideline set, 437 (46.3 ) were considered applicable to the UQ1 editor. This compared favourably with the survey reported in [22] on the application of guidelines. They found that respondents indicated ....

S.L. Smith and J.N. Mosier. Guidelines for designing user interface software. Technical Report ESD-TR-86-278, The Mitre Corporation, Bedford, MA, 1986. Also published as NTIS AD A177 198.

....model of program structure. 28 4.2 The Cornell Pascal editor interface. 32 4.3 UQ1 Pascal editor showing block oriented program display. 34 5.1 Guideline 1. 0ffl4 Fast Response, from Smith and Mosier [SM86] 40 6.1 Macintosh program simulation of UQ editor windows. 66 6.2 Graphical menu style. 67 7.1 An example program input task. 82 7.2 An example program maintenance task. ....

....of program text. 134 10.2 Detail suppression by structural distance. 135 10.3 Mixed language zones. 140 xiii List of Tables 5. 1 Distribution of guidelines in Smith and Mosier [SM86] 39 5.2 Distribution of applicable and non applicable guidelines. 50 6.1 Analysis of variance table showing sources of variation. 70 6.2 Total number of errors before correct selection of an item. 71 6.3 Analysis of variance table, for ....

[Article contains additional citation context not shown here]

S.L. Smith and J.N. Mosier. Guidelines for designing user interface software. Technical Report ESD-TR-86-278, The Mitre Corporation, Bedford, MA, 1986. Also published as NTIS AD A177 198.

....and the designers agree upon the fact that it is a proven solution. Designers share values and ideas so the pattern must relate to their experience. With guidelines this is often an issue because guidelines are usually not explained together with a rationale. In the Smith and Mosier guidelines [11] some guidelines have a short rationale in the comment field but they are often simply defined without any argumentation whereas some are just style definitions and not generic guidelines. It has often been reported that guideline have a number of problems when used [4,8] Some of the problems ....

Smith, S. and Mosier, J.: Guidelines for Designing User Interface Software. MITRE (1986)

....eliminated from initial consideration in order to keep the testing manageable. Additionally, the display and printouts were capable of supporting the potential conditions of these variables. A number of documents were reviewed to aid in the design of potential display formats. The document by Smith and Mosier (1986) entitled Guidelines for Designing User Interface Software was a primary source. Other documents, as referenced in Smith and Mosier, were reviewed, as well. The language variable was examined in the context of Smith and Mosier guidelines calling for l) minimal use of abbreviations, 2) use of ....

Smith, S.L., and Mosier, J. N., Guidelines for Designing User Interface Software, Electronic Systems Division, AFSC, Hanscom AFB, MA, ESD-TR-86-278.1986.

....function design. In essence, the design of the pre drive interface constitutes nothing more than a human computer interaction (HCI) design. For this process, two guideline documents were heavily utilized. These were Smith and Mosier s HCI guideline document and MIL STD 1472D. These documents (Smith and Mosier, 1986) provided individual guidelines ranging from the use of color to menu design. Some of the most important examples of principles applied from these documents included guidelines dictating high legibility and large character size because of the age range of the drivers and, in the pre drive case, ....

Smith, S.L. and Mosier, J.N. (1986). Guidelines for Designing User Interface Software.

No context found.

D#r...hp#v'##!(3), 203-229. Smith, S.L., & Mosier, J.N. (1986). Guidelines for designing user interface software.: MITRE Corporation.

No context found.

S.L. Smith, J.N. Mosier, "Guidelines for Designing User Interface Software," Technical Report, The MITRE Corporation ESD-TR-86-278, 1986.

No context found.

Smith, S. L., Mosier, J. N. Guidelines for Designing User Interface Software, ESD-TR-86-278, Technical Report, The MITRE Corporation 1986.

No context found.

Smith, S. L., Mosier, J. N. Guidelines for Designing User Interface Software, ESD-TR-86-278, Technical Report, The MITRE Corporation, 1986.

No context found.

S. L. Smith and J. N. Mosier, "Guidelines for Designing User Interface Software," The MITRE Coporation, Bedford ESD-TR-86-278 MTR-10090, 1986.

No context found.

Smith, S. L., Mosier, J. N. Guidelines for Designing User Interface Software, ESD-TR-86-278, Technical Report, The MITRE Corporation 1986.

No context found.

Smith, S. L. and Mosier, J. N. (1986). Guidelines for designing user interface software. Technical Report ESD-TR-86-278, The MITRE Corporation, Bedford, MA. ftp://ftp.cis.ohio-state.edu/pub/hci/ Guidelines/.

No context found.

S. L. Smith and J. L. Mosier, Guidelines for Designing User Interface Software, Electronic Systems Division, MITRE Corporation, Bedford, MA Report ESD-TR-86-278, 1986.

No context found.

S.L. Smith, J.N. Mosier, "Guidelines for Designing User Interface Software," Technical Report, The MITRE Corporation ESD-TR-86-278, 1986.

No context found.

Smith, S. L., Mosier, J. N. Guidelines for Designing User Interface Software, ESD-TR-86-278, Technical Report, The MITRE Corporation, 1986.

No context found.

Smith, S. L. and Mosier, J. N. (1986). Guidelines for designing user interface software. Technical Report ESD-TR-86-278, The MITRE Corporation, Bedford, MA. ftp://ftp.cis.ohio-state. edu/pub/hci/Guidelines/.

No context found.

Smith S.L., and Mosier, J.N. (1986). Guidelines for Designing User Interface Software. (Report ESD-TR-86-278, MTR-10090). Bedford, MA: The MITRE Corporation.

First 50 documents

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC