Presentation is loading. Please wait.

Presentation is loading. Please wait.

Overview of Standards and Guidelines

Similar presentations


Presentation on theme: "Overview of Standards and Guidelines"— Presentation transcript:

1 Overview of Standards and Guidelines
References: Hix & Hartson Shneiderman Need: Smith & Mosier checklist example BruitSAM From appendix Hix and Hartson examples of principles

2 Human Factors Information Influences the UI Product
UI standards UI guidelines Commercial style guides Customized style guide

3 Standards Official document Enforceable by control or law
Publicly available Give requirements Enforceable by control or law General wording General wording therefore hard to decide whether the product is in compliance Standards are simple in wording. They require interpretation and tailoring to be useful.

4 Example Standards ISO 9241 In US: HFES 200
17 parts covering the physical design of computers and terminals and design of UI to software In US: HFES 200 Similar to ISO 9241, under ANSI purview ISO - international Organization for Standardization already has two design standards in use ISO ergonomics of VDT workstations ISO Human centred design processes for interactive systems. This is directed toward project managers. Elaborates the steps in the UI engineering process.

5 Example Standard MIL-STD-1472C Mostly vague and difficult to enforce:
‘Display contents shall be presented in a consistent, standardized way’ ‘Flash coding used only to draw the user's attention to mission critical events…’

6 Guidelines Publicly available wisdom or suggestions
Based on research and practice Requires skill and training to apply Based on research and practice (not just common sense) Requires skill and training to apply Often contradictory when UI designers try to apply the guidelines Example: G1 – make all options available to use G2 – limit number of categories in a menu

7 Guideline Example Smith & Mosier are best known
Oriented toward non-windowed, alphanumeric terminals Available on Macs or PCs (See overhead of checklist for design evaluation) • Smith & Mosier guidelines are the most well-known • oriented toward non-windowed, alphanumeric terminals • available on Macs or pc's. Called BruitSAM initially and now called HyperSam. (show demo) • show overhead of checklist for design evaluation.

8 More Examples General guidelines Very general guidelines
Hix & Hartson’s Developing User Interfaces Nielsen’s Usability Engineering Very general guidelines Shneiderman’s Designing the User Interface Go through slides that illustrate H+H guidelines

9 Commercial Style Guides
Vendors, e.g. Apple, defines the guidelines and makes them commercially available. Applications can then advertise that the adhere to the _____ standard for UI. More concrete and useful framework for design than standards. What do they define? • One organization or vendor like Apple, defines the guidelines and made commercially available. • Applications can then advertise that the adhere to the standard for UI for applications that run on the platform, like the Macintosh.. • More concrete and useful framework for design than standards because they provide specific descriptions of the makeup of interface objects (such as windows...). Usually lead to greater consistency across applications. • Commercial guidelines describe the look and feel of interface objects • look = appearance of an interface object • feel = behavior of an interface object

10 Issues — Commercial S.G. Style guides often have a commercial toolkit
Style guides alone do not insure interface usability Style guides promote consistency and standardization across applications • Style guides often have a commercial toolkit • Style guides alone do not insure interface usability • guidelines developed without evaluation or input from a UI expert. • Appearance and behavior of an object is specified, but neglect to say when to use object E.g.. radio buttons vs.. check boxes

11 Customized Style Guides
UI development teams should always produce a customized style guide Guidelines should be evaluated and validated Customized to the project or projects Used to mediate decision-making and maintain a record of decisions Customized Style Guidelines • UI Development teams should always produce a customized style guide, whether for 1 or more projects, early in the development of the user interface. • As much as possible, guidelines should be evaluated and validated. • Can base on commercial style guides, but customized to the project or projects • Used to mediate decision-making and maintain a record of why decisions were made. • Consists of: • I/O devices supported by the project • Representation screen template - annotated • Section for each interaction object and interaction style • Standard format for messages

12 Reading in Preece et al. Chapter 24 (guidelines)
Chapter 25 (standards)

13 Guidelines Assignment
Find some guidelines Find some applications/websites Some that follow guidelines Some that violate guidelines Evaluate the applications/sites using guidelines Give impression of the suitability of guidelines


Download ppt "Overview of Standards and Guidelines"

Similar presentations


Ads by Google