Human Interface Guidelines

Slides:



Advertisements
Similar presentations
Microsoft Office Illustrated Fundamentals Unit C: Getting Started with Unit C: Getting Started with Microsoft Office 2010 Microsoft Office 2010.
Advertisements

1 Official Interface Guidelines by David Catmull User interface documentation published by Apple and Microsoft.
Tutorial 8: Developing an Excel Application
Apple OSX Sami Pohjolainen, Gulshan Kumar.  This is a presentation about Apple OSX guidelines  Sami Pohjolainen,
Tutorial 12: Enhancing Excel with Visual Basic for Applications
1 CS 501 Spring 2002 CS 501: Software Engineering Lecture 11 Designing for Usability I.
User Interface Design: Methods of Interaction. Accepted design principles Interface design needs to consider the following issues: 1. Visual clarity 2.
A Guide to Oracle9i1 Creating an Integrated Database Application Chapter 8.
Help and Documentation CSCI324, IACT403, IACT 931, MCS9324 Human Computer Interfaces.
User Interface Design. Overview The Developer’s Responsibilities Goals and Considerations of UI Design Common UI Methods A UI Design Process Guidelines.
1 Introduction to the Visual Studio.NET IDE Powerpoint slides modified from Deitel & Deitel.
© 2005 by Prentice Hall Chapter 3c Designing Interfaces and Dialogues.
1 User Interface Design CIS 375 Bruce R. Maxim UM-Dearborn.
Performing User Interface Design
Exploring StarOffice 6.0 Tools StarOffice 6.0 Tools.
Chapter 12 Designing Interfaces and Dialogues
Systems Analysis and Design in a Changing World, 6th Edition
Systems Analysis and Design in a Changing World, 6th Edition
Lecture Set 3 Introduction to Visual Basic Concepts Part A – User Interfaces and Windows Forms – The Toolbox.
Human-Computer Interaction
Systems Analysis and Design in a Changing World, 6th Edition
Design. Hard design - increase control. - Displays are more virtual / artificial. Marketplace pressure: - Adding operations cheaper. Adding controls expensive.
1 Lesson 6 Exploring Microsoft Office 2007 Computer Literacy BASICS: A Comprehensive Guide to IC 3, 3 rd Edition Morrison / Wells.
1 SWE 513: Software Engineering Usability II. 2 Usability and Cost Good usability may be expensive in hardware or special software development User interface.
Guidelines and Prototypes CS774 Human Computer Interaction Spring 2004.
Tutorial 111 The Visual Studio.NET Environment The major differences between Visual Basic 6.0 and Visual Basic.NET are the latter’s support for true object-oriented.
Principles of Good Screen Design
Click to edit Master subtitle style USABILITY and USER INTERFACE DESIGN Application.
Designing Interface Components. Components Navigation components - the user uses these components to give instructions. Input – Components that are used.
CS CS 5150 Software Engineering Lecture 11 Usability 1.
CHAPTER TEN AUTHORING.
Computing Fundamentals Module Lesson 3 — Changing Settings and Customizing the Desktop Computer Literacy BASICS.
Copyright © 2010 Wolters Kluwer Health | Lippincott Williams & Wilkins Introduction to Windows Chapter 2.
SEG3120 User Interfaces Design and Implementation
COM148X1 Interactive Programming Lecture 7. Topics Today HCI Event Handling.
Why do we need good user interfaces?. Goals of User Interfaces Usable – how much effort to do a task? – example: often-used buttons easier to find – example:
INFO 355Week #71 Systems Analysis II User and system interface design INFO 355 Glenn Booker.
1 More about Graphical User Interfaces CIS*2450 Advanced Computing Techniques.
Chapter 2 – Introduction to the Visual Studio .NET IDE
Human Interface Guidelines Networking Lab Lee Ho Jae.
Introduction to Interactive Media Interactive Media Tools: Authoring Applications.
Yonglei Tao School of Computing & Info Systems GVSU Ch 7 Design Guidelines.
The Structure of the User Interface Lecture # 8 1 Gabriel Spitz.
Conceptual Model Design Informing the user what to do Lecture # 10 (a) Gabriel Spitz.
McGraw-HillCopyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved. Office Word 2010 Lab 1 Creating and Editing a Document.
Importance of user interface design – Useful, useable, used Three golden rules – Place the user in control – Reduce the user’s memory load – Make the.
Anti-mac Interface Dona Gentner Jakob Nielsen [Sun Microsystems]
Usability Olaa Motwalli CIS764, DR Bill – KSU. Overview Usability factors. Usability guidelines.  Software application.  Website. Common mistakes. Good.
IT323 - Software Engineering 2 1 Tutorial 3.  Suggest ways in which the user interface to an e-commerce system such as an online stores might be adapted.
William H. Bowers – Specification Techniques Torres 17.
 2002 Prentice Hall. All rights reserved. 1 Introduction to the Visual Studio.NET IDE Outline Introduction Visual Studio.NET Integrated Development Environment.
Conceptual Model Design Informing the user what to do Lecture 10a Gabriel Spitz 1.
6. (supplemental) User Interface Design. User Interface Design System users often judge a system by its interface rather than its functionality A poorly.
Dive Into® Visual Basic 2010 Express
Lesson 11 Exploring Microsoft Office 2007
The Desktop Screen image displayed when a PC starts up A metaphor
Chapter 2 Hix & Hartson Guidelines.
User Interface Design The Golden Rules: Place the user in control.
International Computer Driving Licence Syllabus version 5.0
Chapter 2 – Introduction to the Visual Studio .NET IDE
Java Look-and-Feel Design Guidelines
Chapter Lessons Understand the Macromedia Flash workspace
Introduction to Computers
Software Engineering D7025E
Interface Design Easy to learn? Easy to use? Easy to understand?
Official Interface Guidelines
Demystifying Web Content Accessibility Guidelines
Microsoft Office Illustrated Fundamentals
Chapter 4 Enhancing the Graphical User Interface
Adobe Flash CS3 Revealed
Presentation transcript:

Human Interface Guidelines Networking Lab Lee Ho Jae

Introduction Principles to create excellent software Good human interface with design and processes

Design Process – Involving Users Know your Audience - Define, understand, similar product, design for customers Analyze User Tasks - Define & analyze, conceptual model, overall workflow Build Prototypes - Prototype to test and verify design - Storyboard, prototyping software, writing code

Design Process – Involving Users Observe Users - Try out prototype and observe reactions - Verify test scope and instructions - Supplement prototype with results Guidelines for Observing Users - Describe test purpose, duration - Test product, not the participant - Think-aloud protocol - Without any interference or extra help - Use the result as it is (don’t blame users for inexperience) - Review all results with a cross-functional team

Design Process – Making Design Decisions Weigh the cost against the potential benefits Adding a feature to application - Larger, slower, complex, conflict each other, documentation Avoid feature cascade - Appropriate feature to original intent and main workflow Apply the 80 Percent Solution - Meet the needs of at least 80 percent of users

Characteristics of Great Software High Performance - Frequently measure using metrics(not assumptions) - Modern APIs, threads, memory management system - Avoid polling, unnecessary I/O, loading resource before use Ease of Use - Metaphors, feature with real benefit - Intelligent default settings - Present information step by step - Useful error messages, undo, redo - Internationalize and assistive to disabilities

Characteristics of Great Software Attractive Appearance - Use high-quality graphics and icons, 32-bit color - Use system-provide interface builder - Use modern APIs Reliability - Earn user’s trust (integrity of user’s data) - A predictable user interface (same action, same result) - Validate user input (data type, length, …) - Test software under various conditions - Use modern APIs, standard-based APIs

Characteristics of Great Software Adaptability - Keep working even if the current conditions change - If file system or network fails…? - Changes in screen availability and resolution Interoperability - Communicate across environments - Same file format, extensions on all platform - Standard data-exchange protocol - Save configuration data using system preferences

Characteristics of Great Software Mobility - Battery power, movability, configuration changes - Avoid polling, minimize access on movable drive - Be sensitive to screen resolution changes

Human Interface Design - Principles Metaphor - Convey concepts and features - File folders storing documents, iTunes, iPhoto Reflect the User’s Mental Model - Experience from real-world, other software - Familiarity, Simplicity, Availability, Discoverability Explicit and Implied Actions - See, Select, Perform - Menu list, drag-and-drop operation Direct Manipulation - Implied Action - Drag selected text, resizing of a graphic object

Human Interface Design - Principles User Control - User decides everything - Help only with an appropriate warning Feedback and Communication - Inform users of current status of application - MSN is going to tray. Progress indicator Consistency - Consistent terminology, icons - Versions, user’s expectations WYSIWYG - Printing, Publish - Features easily accessible (Don’t hide in menu)

Human Interface Design - Principles Forgiveness - Easily reversible action, warning for irreversible loss Perceived Stability - Use standard graphical elements - Dimmed menu item, user-modifiable settings Aesthetic Integrity - High quality of icons, anti-aliased text - Consistent scale in fonts, controls Modelessness - Exception : short-term mode, alert, installer

Human Interface Design - Principles Managing Complexity - Complex task, simple interface - Progressive disclosure, separated info-window, preferences

Human Interface Design - Users Worldwide Compatibility - Cultural Values (Owl – wisdon/black magic, holiday) - Language differences (standard usage/syntax) - Text Display/Editing (align direction, scanner) - Resource (region dependent data, logical flow of content) Universal Accessibility - Visual Disabilities (high contrast, text sizes, zooming, voice) - Hearing Disabilities (visual cue come with audible cue) - Physical Disabilities (Sequentially instead simultaneously)

Human Interface Design – Extend Interface Build on the Existing Interface - Push button (round shaped with a label) Don’t Assign New Behaviors to Existing Objects Create a New Interface Element Cautiously - Avoid unnecessary complexity - Apply changes to new user interface from system interface

Prioritizing Design Decisions Meet Minimum Requirements - Single menu bar, multilayered window - Files in proper locations, Standard Controls - Avoid system-reserved keyboard shortcuts

Prioritizing Design Decisions Deliver the Feature Users Expect - Communication (error messages, feedback on commands) - High-quality graphics - User assistance (Help), Drag-and-drop

Prioritizing Design Decisions Differentiate Your Application - Modelessness, fast user switching (only login) - Internationalization of interface - Accessibility to users with disabilities - High Performance and reliability - Surprise and delight (keep user’s mental model in mind)