1 / 14

Interface Standards International User Interfaces

This document discusses the importance of consistency in user interfaces to reduce training time by 25-50%, leading to easier learning and increased user satisfaction. It highlights the benefits of adhering to interface standards, such as improved usability and support for international markets. The challenges of cultural differences in graphical interfaces, icon recognition, character sets, and data formatting are examined. Guidelines for developing user-friendly interfaces in a global context are provided, emphasizing the necessity of separating interface design from functionality for better adaptability.

arnie
Télécharger la présentation

Interface Standards International User Interfaces

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Interface StandardsInternational User Interfaces Chapters 8 & 9

  2. Consistency • Between 25 – 50% of training can be reduced if interfaces are consistent

  3. Consistency • Benefits • Ease of learning • Ease of use • Lower training time • Fewer errors because users can predict what a system will do • All these items mean: fewer user frustrations and  increased user satisfaction

  4. Interface Standards • Benefits: • Reduced requirements • Supporting software will be easier • And, if standards are used by developers, there should be an increase in usability • But just using standards do not mean that interfaces will be more usability

  5. Dangers --- oh no! • There “may” be a conflict between taking the time required to develop a good common user interface versus the pressure to get the first product out the door. • Solution: make sure a formal written document states the standards at the start of a new program.

  6. Usable In-House Standards • Most developers will have to accept the in-house GUI standards

  7. International User Interfaces • These interfaces are to be used in several countries. • Language translation and other cultures influences will present problems • Soon the majority of software produced in the US will be for the international market.

  8. International Graphical Interfaces • Icons and color are not universal • E.g., mailboxes look different in different countries • Icons can be classifies into three categories • Resemblance icons -- physical objects • Reference icons -- represent the concept • Arbitrary icons -- by convention

  9. International Graphical Interfaces • Only 13% recognized the Red Cross logo in Japan • Checkboxes -- see Figure 22 in book • Italic typefaces may not be appropriate in kanji. Should use shaded boxes.

  10. Gestural Interfaces • Gestures are used in virtual reality systems. They need to be examined for international usability. • Okay???

  11. Guidelines • Characters • Many countries have character sets beyond A-Z. Therefore, GUIs should allow for extended character sets. • Sorting – sorting special characters may be a problem. In Kanji sorting names are phonetically sorted in Goju-on order.

  12. Guidelines • Numbers & Currency • The decimal point is a period in some countries and a comma with others. • Time • D/M/Y or D/M-Y or M/D/Y • Write out the name of the month with letters instead of giving numbers

  13. Separate the GUI • Separate the interface from the rest of the system • Store the interface definition in a GUI (configuration) file. Or a separate part of the program.

  14. Multilocale Interfaces • If data moves between two counties, a good multilocale interface would allow a new locale and have the interface and data change appropriately. • Sending prices $$$ • the system should not compromise (or translate) the measurement units. E.g., US dollars into the local currency

More Related