From Computing and Software Wiki

Revision as of 04:19, 23 November 2009

User Interface Standards is created by Group 6 for 2009/2010 Software Engineering 4D03 Assignment 5. Group Members: Roshan Jesuratnam, Ashan Khan, Arturo Mata, Jaganvir Sandhu

This document specifically looks at Graphical User Interface (GUI) standards, over other types of interfaces which exist.

Overview

A fundamental reality of application development is that the user interface is the system to the users. What users want is for developers to build applications that meet their needs and that are easy to use. Too many developers think that they are artistic geniuses – they do not bother to follow user interface design standards or invest the effort to make their applications usable, instead they mistakenly believe that the important thing is to make the code clever or to use a really interesting color scheme.

User interface design important for several reasons. First of all the more intuitive the user interface the easier it is to use, and the easier it is to use and the less expensive to use it. The better the user interface the easier it is to train people to use it, reducing your training costs. The better your user interface the less help people will need to use it, reducing your support costs. The better your user interface the more your users will like to use it, increasing their satisfaction with the work that you have done.

A collection of principles for improving the quality of your user interface design. These principles are, structure principle, simplicity principle, visibility principle, feedback principle, tolerance principle, reuse principle.

The most important thing you can possibly do is ensure your user interface works consistently. If you can double-click on items in one list and have something happen, then you should be able to double-click on items in any other list and have the same sort of thing happen. Put your buttons in consistent places on all your windows, use the same wording in labels and messages, and use a consistent color scheme throughout. Consistency in your user interface enables your users to build an accurate mental model of the way it works, and accurate mental models lead to lower training and support costs.

For a user interface standard to increase usability in the resulting products, two conditions have to be met: The standard must specify a usable interface, and the standard must be usable by developers so that they actually build the interface according to the specifications.

Clearly end users benefit from well-designed interface standards. However, organizations benefit as well. Organizations benefit from reduced production costs and more effective use of resources. Production costs are reduced because standards are essentially reusable, template-based building blocks. Developers identify the task a user seeks to execute on a given page, select the template based on that task, and then customize the page to fit the specific context of that task.

Standards

ADD MORE SHIT ON THIS, NEEDS MORE COWBELL

TAKE FROM APPLE AND MICROSOFT AND MORE CRAP
http://en.wikipedia.org/wiki/Aqua_(user_interface)
http://developer.apple.com/mac/library/documentation/UserExperience/Conceptual/AppleHIGuidelines/XHIGIntro/XHIGIntro.html
http://download.microsoft.com/download/e/1/9/e191fd8c-bce8-4dba-a9d5-2d4e3f3ec1d3/ux%20guide.pdf ********************
http://www.usabilitynet.org/tools/r_international.htm
http://www.beta-research.com/standards.html <---GOOD RESOURCE

Windows

  Window Management

Window management is one of the most fundamental user activities. The main purpose is to require less effort from users to move their mouse across greater distances making window placement more predictable and therefore easier to find.

  Dialog Boxes

  Title Bar

All windows should have a title bar even if the window doesn’t have a title (which should be a very rare exception). Use the title bar controls as follows: • Close: All primary and secondary windows with a standard window frame should have a Close button on the title bar. Clicking Close has the effect of canceling or closing the window. • Minimize All primary windows and long-running modeless secondary windows (such as progress dialogs) should have a Minimize button. Clicking Minimize reduces the window to its taskbar button. Consequently, windows that can be minimized require a title bar icon. • Maximize/Restore down All resizable windows should have a Maximize/Restore down button. Clicking Maximize displays the window in its largest size, which for most windows is full screen; whereas clicking Restore down displays the window in its previous size. However, some windows don't benefit from using a full screen, so these windows should maximize to their largest useful size.

  Windows Title:

A document window should display the name of the document being viewed. Application windows display the application name. Panels display a descriptive title appropriate for that window. If the contents of the window can change, it might be appropriate to change the title to reflect the current context.

For example, if you need to display more than one item in the title, separate the items with a dash (—) with space on either side. For example, the main viewer window of Mail displays the currently selected message mailbox and the selected folder, if any. When a message is viewed in its own window, the message title is displayed. Don’t display pathnames in window titles. When displaying document titles, use the display name and show the extension if the user has elected to show extensions.

  The Windows Size

In this example, Windows Media® Player changes its format when the window becomes too small for the standard format.

• Choose a default window size appropriate for its contents. Don't be afraid to use larger initial window sizes if you can use the space effectively.

• Use resizable windows whenever practical to avoid scroll bars and truncated data. Windows with dynamic content and lists benefit the most from resizable windows.

• For text documents, consider a maximum line length of 65 characters to make the text easy to read. (Characters include letters, punctuation, and spaces.)

• Should set a minimum window size if there is a size below which the content is no longer usable. For resizable controls, set minimum resizable element sizes to their smallest functional sizes, such as minimum functional column widths in list views:

• Should change the presentation if doing so makes the content usable at smaller sizes.

• May be optimized for higher resolutions, but sized down as needed at display time to the actual screen resolution.

  The Windows Location

"Centering" means to bias vertical placement slightly towards the top of the monitor.

Show contextual windows near the object that it was launched from.

Cascade top-level application or document windows off the upper-left corner of the monitor.

Center top-level utility windows.

  The Windows Activation

• Respect users' window state selection. If an existing window needs attention, flash the taskbar button three times to draw attention and leave it highlighted, but don't do anything else. Don't restore or activate the window. Don't use any sound effects. Instead, let users activate the window when they are ready.

• Exception: If the window doesn't appear on the taskbar, bring it to the top of all the other windows and flash its title bar instead.

• Restoring a primary window should also restore all its secondary windows, even if those secondary windows have their own taskbar button. When restoring, place secondary windows on top of the primary window.

  Persistence

• When a window is redisplayed, consider displaying it in the same state as last accessed. When closing, save the monitor used, window size, location, and state (maximized vs. restore). When redisplaying, restore the saved window size, location, and state using the appropriate monitor. Also, consider making these attributes persist across program instances on a per-user basis. If the window is larger than the monitor, resize the window as necessary.

• Move the location toward the upper-left corner to fit within the monitor as necessary.

  Scrolling Windows

People use scroll bars to view areas of a document or a list that is larger than can fit in the current window. Only active windows can be scrolled. A window can have a horizontal scroll bar, a vertical scroll bar, both, or neither. A window that has one or more scroll bars also has a resize control in the bottom right corner.

The scroller size reflects how much of the content is visible; the smaller the scroller, the less of the content the user can see at that time. The scroller represents the relative location, in the whole document, of the portion that can be seen in the window.

The user can use scroll bars by doing the following:

• Dragging the scroller. This method is usually the fastest way to move around a document. The window’s contents changes in “real time” as the user drags the scroller.

• Clicking a scroll arrow. This means, “Show me more of the document that’s hidden in this direction.” The scroller moves in the direction of the arrow. Each scroll arrow click moves the content one unit; your application determines what one unit equals. For example, a word processor would move a line of text per click, a spreadsheet could move one row or column. To ensure smooth scrolling effects, specify units of the same size throughout a document.

• Clicking or pressing in the scroll track. Clicking advances the document by a windowful (the default) or to the pointer’s hot spot, depending on the user’s choice in Appearance preferences. A “windowful” is the height or width of the window, minus at least one unit of overlap to maintain the user’s context. This unit of overlap should be the same as one scroll arrow unit (for example, a line of text, a row of icons, or part of a picture). The Page Up and Page Down keys also move the document view by a windowful. Pressing in the scroll track displays consecutive windowfuls of the document until the location of the scroller catches up to the location of the pointer (or until the user releases the mouse button).

It’s best not to add controls to the scroll-bar area of a window. 
If you add more than one control to this area, it’s hard for people to distinguish among controls.
It’s best to place the majority of your features in the menus as commands. 
Only frequently accessed features should be elevated to the primary interface.

  Common Dialogs

Asthetics

  Sizing

  Formatting

  Titles and Icons

  Fonts and Colour

Interaction

  Mouse

The mouse is the primary input device used to interact with objects in most operating systems. The term mouse can also refer to other pointing devices, such as trackballs, touchpads and pointing sticks built into notebook computers, pens used with Tablets and Touch Technology, and, on computers with touchscreens, even a user's finger.

Physically moving the mouse moves the graphic pointer (also referred to as the cursor) on the screen. The pointer has a variety of shapes to indicate its current behavior.

Moving the mouse without pressing the mouse button moves the pointer, or cursor. The onscreen pointer can assume different shapes according to the context of the application and the pointer’s position. For example, in a word processor, the pointer takes the I-beam shape while it’s over the text and changes to an arrow when it’s over a tools palette. Change the pointer’s shape only to provide information to the user about changes in the pointer’s function.

Just moving the mouse changes only the pointer’s location, and possibly its shape. Pressing the mouse button indicates the intention to do something, and releasing the mouse button completes the action.

Clicking

Clicking has two components: pushing down on the mouse button and releasing it without moving the mouse. (If the mouse moves between button down and button up, it’s dragging, not clicking.) The effect of a click should be immediate and obvious. If the function of the click is to cause an action (such as clicking a button), the selection is made when the button is pressed, and the action takes place when the button is released. For example, if a user presses down the mouse button while the pointer is over an onscreen button, thereby putting the button in a selected state, and then moves the pointer off the button before releasing the mouse button, the onscreen button is not clicked. If the user presses an onscreen button and rolls over another button before releasing the mouse, neither button is clicked.

Double-Clicking

Double-clicking involves a second click that follows immediately after the first click. If the two clicks are close enough to each other in terms of time (as set by the user in Keyboard & Mouse preferences) and location (usually within a couple of points), they constitute a double click. Double-clicking is most commonly used as a shortcut for other actions. Because not everyone is physically able to perform a double click, it should never be the only way to perform an action. Some applications support triple-clicking. For example, in a word processor, the first click sets the insertion point, the second click selects the whole word, and the third click selects the whole sentence or paragraph. Supporting more than three clicks is inadvisable.

Pressing and Holding

Pressing means holding down the mouse button while the mouse remains stationary. Pressing by itself should have no more effect than clicking does, except in well-defined areas such as scroll arrows, where it has the same effect as repeated clicking, where it displays a menu. For example, pressing a Finder icon should select the icon but not open it.

Dragging

Dragging means pressing the mouse button, moving the mouse to a new position, and releasing the mouse button. The uses of dragging include selecting blocks of text, choosing a menu item, selecting a range of objects, moving an icon from one place to another, and shrinking or expanding an object. Dragging a graphic object should move the entire object (or a transparent representation of it), not just the object’s outline.

Your application can restrict an object from being moved past certain boundaries, such as the edge of a window. If the user drags an object and releases the mouse button outside the boundary, the object stays in the original location. If the user drags the item out of the boundary and then back in before releasing the mouse button, the object moves to the new location.

  Touch

Touch Screen Simulation.

Touch Screen design for the elderly.

Many touch interactions are performed using gestures and flicks. A gesture is a quick movement of one or more fingers on a screen that the computer interprets as a command, rather than as a mouse movement, writing, or drawing. Some User Interfaces allow multitouch gestures such as pan, zoom, rotate, two-finger tap, and press and tap. One of the quickest and easiest gestures to perform is a flick. A flick is a simple gesture that results in navigation or an editing command. Navigational flicks include drag up, drag down, move back, and move forward, whereas editing flicks include copy, paste, undo, and delete.

A manipulation is a real-time, physical handling of an object. A manipulation differs from a gesture in that the input corresponds directly to how the object would react naturally to the action in the real world. For example, a photo viewing application might allow users to manipulate a photo by moving, zooming, resizing, and rotating the image. Multitouch manipulations use multiple contact points simultaneously.

Design concepts:

Using touch for input has the following characteristics:

• Natural and intuitive. Everyone knows how to point with a finger and touch things. Object interactions are designed to correspond to how users interact with objects in the real world in a consistent manner.

• Less intrusive. Using touch is silent, and consequently much less distracting than typing or clicking, especially in social situations such as meetings. Compared to using a pen, using a finger is particularly convenient because you don't have to locate or pick up a pen.

• Portable. A computer with touch capability can be more compact because most tasks can be completed without a keyboard, mouse, or touchpad. It can be more flexible because it doesn't require a work surface. It enables new places and scenarios for using a computer.

• Direct and engaging. Touch makes you feel like you are directly interacting with the objects on the screen, whereas using a mouse or touchpad always requires you to coordinate hand movements with separate on-screen pointer movements—which feels indirect by comparison.

• Reduced accuracy. Users can't target objects as accurately using touch, compared to a mouse or pen. Consequently, you can't expect users to tap or manipulate small objects.

Touch provides a natural, real-world feel to interaction. Direct manipulation and animation complete this impression, by giving objects a realistic, dynamic motion and feedback. For example, consider a card game. Not only is it convenient and easy to drag cards using a finger, the experience takes on an engaging real-world feel when you can toss the cards and have them glide, spin, and bounce exactly like physical cards. And when you try to move a card that can't be moved, it's a better experience to have the card resist but not prevent movement, and settle back in place when released, to clearly indicate that the action was recognized but can't be done.

Basic touch design principles:

Each input device has its strengths and weaknesses. The keyboard is best for text input and giving commands with minimal hand movement. The mouse is best for efficient, precise pointing. Touch is best for object manipulation and giving simple commands. A pen is best for freeform expression, as with handwriting and drawing.

When thinking about touch support for your program:

• Don't assume that if a UI works well for a mouse, it also works well for touch. While good mouse support is a start, a good touch experience has a few additional requirements.

• You can assume that if a UI works well for a finger, it also works well for a pen. Making your program touchable goes a long way to providing good pen support. The primary difference is that fingers have a blunter tip, so they need larger targets. And again, hover must be optional.

• Don't depend on touch pointer to fix touch UI problems. Because the touch pointer isn't as easy to use as direct input, view the touch pointer as a last resort for programs that haven't been designed for touch.

  Keyboard

The keyboard is the primary input device used for text input in computers. For accessibility and efficiency, most actions can be performed using the keyboard as well. Keyboards can also refer to virtual, on-screen keyboards and writing pads used by computers without a physical keyboard, such as tablet-based computers.

Shortcut keys By contrast, shortcut keys have the following characteristics:

• They primarily use Ctrl and Function key sequences (Windows system shortcut keys also use Alt+non-alphanumeric keys and the Windows logo key).
• They are primarily for efficiency for advanced users.
• They are assigned only to the most commonly used commands.
• They are intended to be memorized, and are documented only in menus, tooltips, and Help.
• They have effect throughout the entire program, but have no effect if they don't apply.
• They must be assigned consistently because they are memorized and not directly documented.
• They aren't localized.

Because shortcut keys are intended to be memorized, the most frequently used shortcut keys ideally use letters from the first or most memorable characters within the command's keywords, such as Ctrl+C for Copy and Ctrl+Q for Request. Inconsistent meanings for well-known shortcut keys are frustrating and cause errors.

Finally, because they are intended to be memorized, application-specific shortcut keys make sense only for programs and features that are run frequently enough for motivated users to memorize. Infrequently used programs and features don't need shortcut keys. For example, setup programs and most wizards don't need any special shortcut key assignments, nor do infrequently used commands in a productivity application.

Messages

  Errors and Warnings

A perfect UI would not need any error messages, but it is accepted that this cannot be achieved so error messages are necessary. Generally standard rules for the presentation of error messages are:

• Error messages should be straight forward for as many users as possible regardless of culture, age and impairment.
• It should be easy to understand that an error has occurred.
• It should be clear what the user has to do to correct the error.
• It should be clear for the user where the error was found in the application.
• Make sure the user can see that an error has occurred. Error messages need to stand out from the rest of the layout.
• Use an error icon if your layout makes it difficult to visually separate errors from the rest of the page.
• Be consistent when you present errors (the user will expect errors to be displayed at the same location and with the same style on all pages).
• Do not use complicated words. (tip: check out Ogdens basic english)
• Describe what the user should do to correct the error, especially if it could be difficult to understand.
• Make it clear if there were more than one error so that the user can correct all errors at once.
• For advanced users, adding in the ID number of the error can help a lot in figuring out the source of the error because it has an identity from which the user can search information about.

  Confirmation and Notifications

Generally the same rules as above for errors are followed but there are a few disparities:

• Notification areas in the application are generally not as eye catching as error messages
• Confirmation messages provide users to control an aspect of the application
• Both types of messages should have a consistant look so the type can be easily recognized

Text

  UI Text

  Style and Tone

Commands

  Menus

  Toolbars

  Ribbons

Controls

Principles

These principles are in nature heuristics of interface design. They are guidelines that "should" be used in the design of interfaces, since there is no one industry standard. These general rules provide a basis to build on for an user interface designer.

The similarities between these two sets of guidelines is indicative of the rules interface designers should follow to offer end users efficient ease of use.

Ten Usability Heuristics

Jakob Nielsen, a user adovacate and principal of the Nielsen Norman Group for enhancing user experience, outlines the following heuristics;^[1]

• Visibility of system status
  System should indicate the state/progress it is in through appropriate feedback.
• Relate system and real world
  System should be 'natural' in order to speak the user's language. Concepts should be similar to real-world conventions.
• User Control and freedom
  Interface should encourage user to explore features and give them a sense on control over the system.
• Consistency and standards
  Interface should have same meanings of words as other applications. Other interfaces in the system should be used as a guideline when designing a new one.
• Error Prevention
  System should be designed to prevent errors from happening. By implementing various error handling mechanisms (autocorrect, messages, etc.), users should be able to fix and continue with workflow.
• Recognition rather than recall
  Controls of the interface should be easily visible in order to reduce short term memory load.
• Flexibility and effciency of use
  Allow shortcuts for frequently used features for experienced users to maximize effciency through flexible alternatives.
• Aesthetic and minimalistic design
  Discard irrelevant information in dialogues to ensure relevant units of information does not lose their relative visibility.
• Help users recognize, diagnose, and recover from errors
  All error messages should be illustrated in clear, simple language (no codes) where users undoubtedly recognize the problem and follow a constructive solution.
• Help and documentation
  Help and documentation should be easy to search focused on the user’s task with a list of clear concrete steps to be carried out. Limit all possible ambiguities.

Eight Golden Rules of Interface Design

From the book Designing the User Interface, Ben Shneiderman outlines eight key rules of good interface design;^[2]

• Strive for consistency
  Consistency must be implemented within itself and other interfaces. This ensures a "global" understanding of where things are and where one would look for it. See Figure 1 for example.
• Enable frequent users to use shortcuts
  Expert users should not be bound by interaction styles that may slow progress. Thus, enabling shortcuts through speed keys, hidden commands, marcos, etc. will optimize pace of interaction while reducing the number of interactions.
• Offer informative feedback
  Major or infrequent actions should make aware the user, with descriptive and clear information of what is occuring.
• Design dialog to yield closure
  Sequences of actions should be grouped with a beginning, middle and end. This gives the user a sense of direction and accomplishment of the task.
• Offer simple error handling
  Design the interface in a manner which the chance of human error is impossible. However, since it is impossible to predict every behaviour, design it in a way such that it offers informative feedback explaining the details of the error and how it could be solved.
• Permit easy reversal of actions
  Allow users to undo their mistakes. This allows users to have a sense of security in case a mistake occurs. It also allows users to explore without consequences.
• Support internal locus of control
  Users should be the initiators of actions rather than responders. Actions should respond quickly with delay and offer response.
• Reduce short-term memory load
  Reducing sequences of events and commands allows the user to be aided in tasks. Keep the display simple so it is intuitive for the user.

Design

A collection of principles for improving the quality of your user interface design. These principles are

1. The structure principle. Your design should organize the user interface purposefully, in meaningful and useful ways based on clear, consistent models that are apparent and recognizable to users, putting related things together and separating unrelated things, differentiating dissimilar things and making similar things resemble one another. The structure principle is concerned with your overall user interface architecture.
2. The simplicity principle. Your design should make simple, common tasks simple to do, communicating clearly and simply in the user’s own language, and providing good shortcuts that are meaningfully related to longer procedures.
3. The visibility principle. Your design should keep all needed options and materials for a given task visible without distracting the user with extraneous or redundant information. Good designs don’t overwhelm users with too many alternatives or confuse them with unneeded information.
4. The feedback principle. Your design should keep users informed of actions or interpretations, changes of state or condition, and errors or exceptions that are relevant and of interest to the user through clear, concise, and unambiguous language familiar to users.
5. The tolerance principle. Your design should be flexible and tolerant, reducing the cost of mistakes and misuse by allowing undoing and redoing, while also preventing errors wherever possible by tolerating varied inputs and sequences and by interpreting all reasonable actions reasonable.
6. The reuse principle. Your design should reuse internal and external components and behaviors, maintaining consistency with purpose rather than merely arbitrary consistency, thus reducing the need for users to rethink and remember

There are ten general principles for user interface design. They are called "heuristics" because they are more in the nature of rules of thumb than specific usability guidelines.

• Visibility of system status

The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.

• Match between system and the real world

The system should speak the users' language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.

• User control and freedom

Users often choose system functions by mistake and will need a clearly marked "emergency exit" to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.

• Consistency and standards

Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.

• Error prevention

Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.

• Recognition rather than recall

Minimize the user's memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate.

• Flexibility and efficiency of use

Accelerators -- unseen by the novice user -- may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.

• Aesthetic and minimalist design

Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.

• Help users recognize, diagnose, and recover from errors

Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.

• Help and documentation

Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user's task, list concrete steps to be carried out, and not be too large.

Techniques

In the book, The Object Primer by Scott Ambler. It outlines the following tips and techniques that one should think about when creating a user interface;^[3]

• Consistency
  Ensure interface works in a consistent manner which enables user to build an accurate model of the way it works.
• Set standards and stick to them
  Use a consistent interface design standard throughout. All aspects of software must follow Agile Modeling (AM)’s Apply Modeling Standards.
• Be prepared to hold the line
  Be open to stakeholder’s ideas and suggestions. Inform stakeholders when developing the user interface of your corporate UI standards.
• Explain the rules
  Explain all rules in a clear consistent manner to avoid problems.
• Navigation between major user interface items is important
  Be sure the system is flexible enough to support various approaches to ensure your user will make sense of the application. A user interface-flow diagram is optional to further understand the flow of your user interface.
• Navigation within a screen is important
  Organize navigation between widgets in a consistent manner users will find recognizable.
• Word your messages and labels effectively
  Illustrate text (messages and labels) through clear, effective language. Avoid inconsistency.
• Understand the UI widgets
  Adopt an effective UI widget standard in your application.
• Look at other applications with a grain of salt
  Create authentic application which follows the user interface-standards and guidelines of your organization.
• Use color appropriately
  Colours should be used sparingly for accessibility reasons. If colours are used, they should be used with a secondary indicator which does not discriminate. Colours should also be consistant throughout the application.
• Follow the contrast rule
  Background and foreground should contrast enough for the user to easily read contents of the interface.
• Align fields effectively
  Editable fields (i.e textboxes) should be aligned to be visually appealing and promote efficiency through features such as 'tabbing'.
• Expect your users to make mistakes
  Allow easy reversal of actions. See Principles
• Justify data appropriately
  Left justify string, Right justify numbers, Decimal justify floating point numbers.
• Your design should be intuitable
  Interfaces should be easy to learn and should encourage the user to explore and become familiar with its elements.
• Don’t create busy user interfaces
  Interfaces should be simple at best. Clutter causes confusion and stalls efficient workflow.
• Group things effectively
  Related features should be effectively grouped together, whereas items which are not should be distinctly separated.
• Take an evolutionary approach
  Methods such as rapid prototyping and Agile Model Driven Development are critical approaches in designing user interfaces.

Human Factors

(Use http://www.beta-research.com/standards.html)

References

[1] Nielsen, Jakob. Ten Usuability Heuristics. http://www.useit.com/papers/heuristic/heuristic_list.html
[2] Shneiderman, Ben. Eight Golden Rules of Interface Design. http://faculty.washington.edu/jtenenbg/courses/360/f04/sessions/schneidermanGoldenRules.html
[3] Ambler, Scott. The Object Primer. http://www.ambysoft.com/essays/userInterfaceDesign.html
[4] Scott W. Ambler, Initials. (n.d.). The Object primer 3rd edition agile model driven development with uml 2. Retrieved from http://www.ambysoft.com/essays/userInterfaceDesign.html
[5] Thovtrup , Henrik , & Nielsen, Jakob. (1991). Assessing the usability of a user interface standard. Retrieved from http://www.ambysoft.com/essays/userInterfaceDesign.html
[6] MSDN, Initials. (2009). User interface standards. Retrieved from http://msdn.microsoft.com/en-us/library/aa217660%28office.11%29.aspx
[7] © Copyright Usernomics, Initials. (2008). User interface design. Retrieved from http://www.usernomics.com/user-interface-design.html
[8]Molich, R., and Nielsen, J. (1990). Improving a human-computer dialogue, Communications of the ACM 33. 3 (March), 338-348.
[9]Nielsen, J., and Molich, R. (1990). Heuristic evaluation of user interfaces. Proc. ACM CHI'90 Conf. (Seattle, WA, 1-5 April), 249-256.
[10]Nielsen, J. (1994a). Enhancing the explanatory power of usability heuristics. Proc. ACM CHI'94 Conf. (Boston, MA, April 24-28), 152-158.
[11]Nielsen, J. (1994b). Heuristic evaluation. In Nielsen, J., and Mack, R.L. (Eds.), Usability Inspection Methods, John Wiley & Sons, New York, NY.
[12]Nielsen, Jakob. (2005 ). Ten usability heuristics. Retrieved from http://www.useit.com/papers/heuristic/heuristic_list.html