Human Computer Interface. HCI and Designing the User Interface The user interface is a critical part of an information system -- it is what the users.

Slides:



Advertisements
Similar presentations
Chapter 11 Designing the User Interface
Advertisements

Human Computer Interface
Using Macros and Visual Basic for Applications (VBA) with Excel
© De Montfort University, Characteristics of Good Dialogues Howell Istance Department of Computer Science De Montfort University.
Requirements Analysis 8. 1 Storyboarding b508.ppt © Copyright De Montfort University 2000 All Rights Reserved INFO2005 Requirements Analysis Human.
7M701 1 User Interface Design Sommerville, Ian (2001) Software Engineering, 6 th edition: Chapter 15
Microsoft Windows Vista Chapter 6 Customizing Your Computer Using the Control Panel.
1 / 31 CS 425/625 Software Engineering User Interface Design Based on Chapter 15 of the textbook [SE-6] Ian Sommerville, Software Engineering, 6 th Ed.,
User Interface Design: Methods of Interaction. Accepted design principles Interface design needs to consider the following issues: 1. Visual clarity 2.
User Interface Design 2 Constructing an Interface for an ATM.
03/12/2001 © Bennett, McRobb and Farmer Human–Computer Interaction Based on Chapter 16 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis.
Today’s class Group Presentation More about principles, guidelines, style guides and standards In-class exercises More about usability Norman’s model of.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 14 Designing.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Interaction Styles Interface Widgets. What are Interaction Styles?  A Collection of interface objects and associated techniques from which an interaction.
Principles and Methods
User interface design Designing effective interfaces for software systems Objectives To suggest some general design principles for user interface design.
COMP1007 Introduction to Requirements Analysis © Copyright De Montfort University 2002 All Rights Reserved COMP1007 Introduction to Requirements Analysis.
© 2005 by Prentice Hall Chapter 3c Designing Interfaces and Dialogues.
1 User Interface Design CIS 375 Bruce R. Maxim UM-Dearborn.
Chapter 13: Designing the User Interface
Chapter 14 Designing the User Interface
Design, goal of design, design process in SE context, Process of design – Quality guidelines and attributes Evolution of software design process – Procedural,
User Interface Design Chapter 11. Objectives  Understand several fundamental user interface (UI) design principles.  Understand the process of UI design.
Chapter 12 Designing Interfaces and Dialogues
User Interface Theory & Design
Systems Analysis and Design in a Changing World, 6th Edition
1 ISE 412 Human-Computer Interaction Design process Task and User Characteristics Guidelines Evaluation.
XP Chapter 4 Succeeding in Business with Microsoft Office Access 2003: A Problem-Solving Approach 1 Collecting Data for Well-Designed Forms Chapter 4 “Making.
Module Designing Computer-based Information Systems
Systems Analysis and Design in a Changing World, 6th Edition
1 BTEC HNC Systems Support Castle College 2007/8 Systems Analysis Lecture 9 Introduction to Design.
14 Chapter 11: Designing the User Interface. 14 Systems Analysis and Design in a Changing World, 3rd Edition 2 Identifying and Classifying Inputs and.
1 Human-Computer Interaction  Design process  Task and User Characteristics  Guidelines  Evaluation.
11.10 Human Computer Interface www. ICT-Teacher.com.
User interface design. Recap OOD is an approach to design so that design components have their own private state and operations Objects should have constructor.
CSC 480 Software Engineering Lecture 19 Nov 11, 2002.
Software Evaluation Catherine McKeveney Medical Informatics 1st March 2000.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.
What about Chapter 7?. What is the usability process? Tyldesley’s 22 possible Measurement Criteria Let’s focus on usability–A usability initiative needs.
Productivity Programs Common Features and Commands.
Copyright © 2010 Wolters Kluwer Health | Lippincott Williams & Wilkins Introduction to Windows Chapter 2.
1 Command Field: Use this field to go to transactions directly by entering the transaction code. The transaction codes can be found either in the SAP Easy.
User Interface Structure Design Chapter 11. Key Definitions The user interface defines how the system will interact with external entities The system.
Software Architecture
Exploring Windows and Essential Computing Concepts 1 Windows Desktop u Windows Basics u Icon u Start Button u My Computer u Network Neighborhood u Recycle.
User Interface Theory & Design Lecture 6a 1.  User interface is everything the end user comes into contact with while using the system  To the user,
1 CP586 © Peter Lo 2003 Multimedia Communication Human Computer Interaction.
Basic Computer and Word Functions, part 1 Read the information and use to answer the questions in the Basic Computer and Word Functions Study Guide.
E.g.: MS-DOS interface. DIR C: /W /A:D will list all the directories in the root directory of drive C in wide list format. Disadvantage is that commands.
14 Chapter 11: Designing the User Interface. 14 Systems Analysis and Design in a Changing World, 3rd Edition 2 Identifying and Classifying Inputs and.
Input Design Lecture 11 1 BTEC HNC Systems Support Castle College 2007/8.
Catholic University College of Ghana Fiapre-Sunyani INFORMATION TECHNOLOGY I Audrey Asante, Faculty of ICST Graphic User Interface Tutorials and Documentation.
Introduction to KE EMu Unit objectives: Introduction to Windows Use the keyboard and mouse Use the desktop Open, move and resize a.
Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 7 - Designing the User and System Interfaces.
Human-Computer Interaction Design process Task and User Characteristics Guidelines Evaluation ISE
1 Lesson 11 Exploring Microsoft Office 2010 Computer Literacy BASICS: A Comprehensive Guide to IC 3, 4 th Edition Morrison / Wells.
 2002 Prentice Hall. All rights reserved. 1 Introduction to the Visual Studio.NET IDE Outline Introduction Visual Studio.NET Integrated Development Environment.
Invoices and Service Invoices Training Presentation for Raytheon Supply Chain Platform (RSCP) April 2016.
1 Unit E-Guidelines (c) elsaddik SEG 3210 User Interface Design & Implementation Prof. Dr.-Ing. Abdulmotaleb.
DOCUMENTATION REF: Essentials of IT (Hamilton et al) Chapter 1.
6. (supplemental) User Interface Design. User Interface Design System users often judge a system by its interface rather than its functionality A poorly.
Computer Literacy BASICS: A Comprehensive Guide to IC 3, 5 th Edition Lesson 11 Exploring Microsoft Office Morrison / Wells / Ruffolo.
AUTHOR PRADEEP KUMAR B.tech 1 st year CSE branch Gnyana saraswati college of eng. & technology Dharmaram(b)
Chapter 6 : User interface design
11.10 Human Computer Interface
Chapter 14 Designing Interfaces and Dialogues
MBI 630: Week 11 Interface Design
GRAPHICAL USER INTERFACE
Human and Computer Interaction (H.C.I.) &Communication Skills
Presentation transcript:

Human Computer Interface

HCI and Designing the User Interface The user interface is a critical part of an information system -- it is what the users see A user's attitude towards a system can be coloured by their experience of the user interface HCI combines techniques from psychology, ergonomics and computer science HCI is about designing the inputs and outputs of a system taking into account human factors

What is the User Interface Users of an information system need to interact with it by - reading and interpreting information - issuing commands to the system - entering words and numbers - reading and interpreting the results or output produced - responding to and correcting errors These are secondary tasks as opposed to the user's primary objectives - a well-designed system means the secondary tasks will be easy to carry out

Two Metaphors: The dialogue metaphor

Example: order entry screen

Use case Diagrams Use cases may be used to document the dialogue between a user and the system - e.g. Enter Customer code or look up customer in an index. For each line of the order, enter the product number and quantity. calculate the Line Price, Tax and totals automatically.

Use Case Documenting Dialogue

Two metaphors: The Direct Manipulation Metaphor The interface gives the impression that you are manipulating objects on the screen through the use of the mouse - drag and drop an icon - shrink or expand a window - push a button - pull down a menu Such interfaces are event-driven - the window manager responds to events and changes the state of the objects in the window

Interface for the Use Case Check Campaign Budget

Characteristics of Good Dialogues (1) Consistency - a consistent user interface design helps users to learn an application and to apply what they know in different parts of the application Appropriate user support - when the user does not know what action to take or has made an error - help messages -- should be context sensitive -- may be general or specific -- provide links between different levels of help -- separate screens, status line or tooltips

Characteristics of Good Dialogues (2) Appropriate user support - error messages -- should be informative (i.e. explain what has gone wrong and how the user can recover) - warning messages -- can prevent the user from making serious errors Adequate feedback from the system - users expect the system to respond once they have carried out some action - the system's response time should be appropriate to the type of user action - the user should be able to cancel commands

Error and Warning Messages

Characteristics of Good Dialogues (3) Minimal user input - reduce unnecessary input from the user - use codes and abbreviations - select from a list - edit incorrect values or commands - prevent information from being re-entered if it can be derived - use default values - provide shortcuts, key combinations for advanced users

Style Guides Some organisations provide standard guidelines or style guides for the design of user interfaces - The Windows Interface Guidelines for Software Design (1997) - Macintosh Human Interface Guidelines (1996) - large organisations produce their own style guides A consistent style enables users to quickly become familiar with new applications

Approaches to Interface Design There are many different ways of designing and implementing a user interface Design is influenced by - the nature of the task the user is carrying out - the type of user - the amount of training undertaken by the user - the frequency of use - the hardware and software architecture of the system

Steps and Objectives in HCI Design

Scenario-based Approach A scenario is a step-by-step description of a user's actions - used as tool in requirements gathering, interface design and evaluation - can be a textual narrative describing a user's actions - storyboards (series of pictures that depict actions) - video mock-ups - prototypes Use cases are similar to scenarios

Examples of Scenario Pete starts up the word-processor. He types in a title for the note and changes its style to Title. He types in two paragraphs describing his idea for an advertisement for the Yellow Partridge campaign to be used in fashion magazines in Europe during the summer of He types his initials and the date and time. He uses the short-cut keys to save the file. The save-as dialogue box appears and, using the mouse, he changes to the Summer 1999 Campaign folder in the Yellow Partridge folder on the server. He scrolls to the bottom of the list of files already in the folder and reads the title of the last note to be added, Note 17, he calls the new note Note 18 and clicks on Save. He exits from the word-processor.

Roles for Scenario-based Approaches Gather requirements - describe what the user does now Envision solutions - describe possible ways of working Evaluate systems - write test cases that follow scenarios Document the system - write manual sections that follow scenarios

Scenario-based Design Can result in large volumes of textual information - requires document management - may delay implementation Solution - use computer-based tools to develop and document scenarios and to develop working models of scenarios - software implementation decisions may be documented at the same time

Achieving Usability Learnability - how much time and effort is required Throughput - speed with which a task can be accomplished and the number of errors Flexibility - the ability of the system to handle changes to the tasks that users carry out Attitude

Summary System designers must take account of the requirements of the people who use their software - to reduce errors, and maximise user-satisfaction The dialogue and direct manipulation metaphors The scenario approach to interface design References: Bennett et al, Chapter 16, Maciaszek, Chapter 6