Convergence 2003 Wellington – Te Papa, 29 April 2003 Easily Making IT Easy to Use Robert Biddle, James Noble Victoria University of Wellington

Slides:



Advertisements
Similar presentations
Chapter 11 Designing the User Interface
Advertisements

User Interfaces 4 BTECH: IT WIKI PAGE:
SECOND MIDTERM REVIEW CS 580 Human Computer Interaction.
1 A Lightweight Case Tool for Learning OO Design Robert Biddle Victoria University of Wellington, New Zealand
The Developer Perspective Michelle Osmond. Design – Requirements Gathering Sales & Research projects –Prototypes/Demos User group meetings Usability workshops.
The Interaction. Overview Interaction Models understand human-computer communication Ergonomics Physical characteristics of interaction Context Social.
An Agile Approach for Web Systems Engineering A Presentation of an Article by V.E.S. Souza and R.A. Falbo.
1 User-Centered Design CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology April 17, 2007.
James Tam What HCI (and this course) all about 1 1 These notes are based roughly upon the optional reading a Taxonomy of HCI optional reading
1 A U Interface Analysis Professor J. Alberto Espinosa Business Requirements Analysis ITEC-455 Spring 2010.
Usability Inspection n Usability inspection is a generic name for a set of methods based on having evaluators inspect or examine usability-related issues.
Part 4: Evaluation Chapter 20: Why evaluate? Chapter 21: Deciding on what to evaluate: the strategy Chapter 22: Planning who, what, where, and when Chapter.
Design and Evaluation of Iterative Systems n For most interactive systems, the ‘design it right first’ approach is not useful. n The 3 basic steps in the.
© Lethbridge/Laganière 2001 Chapter 7: Focusing on Users and Their Tasks1 7.1 User Centred Design (UCD) Software development should focus on the needs.
SwE 313 Introduction to Rational Unified Process (RUP)
© Prentice Hall CHAPTER 3 Computer Software.
INTRODUCTION. Concepts HCI, CHI Usability User-centered Design (UCD) An approach to design (software, Web, other) that involves the user Interaction Design.
Chapter 13: Designing the User Interface
Chapter 3 Software Two major types of software
UNIT-V The MVC architecture and Struts Framework.
Model the User Experience Today:  Detail some Use Cases  Develop a storyboard of the use cases  Sketch mock-ups of the use case's information requirements.
Human Computer Interaction Semester 1, 2013/2013.
People: Usability IS 101Y/CMSC 101Y November 5, 2013 Marie desJardins Amanda Mancuso University of Maryland Baltimore County.
People: Usability COMP 101 November 12, 2014 Carolyn Seaman Amanda Mancuso Susan Martin University of Maryland Baltimore County.
Predictive Evaluation
Dynamic Web Sites Chris North cs3724: HCI. Presentations matt ketner, sam altman, mike gordon Vote: UI Hall of Fame/Shame?
14 Chapter 11: Designing the User Interface. 14 Systems Analysis and Design in a Changing World, 3rd Edition 2 Identifying and Classifying Inputs and.
4 - 1 Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
System Design: Designing the User Interface Dr. Dania Bilal IS582 Spring 2009.
Computer –the machine the program runs on –often split between clients & servers Human-Computer Interaction (HCI) Human –the end-user of a program –the.
Interaction Design Process COMPSCI 345 S1 C and SoftEng 350 S1 C Lecture 5 Chapter 3 (Heim)
Interacting with IT Systems Fundamentals of Information Technology Session 5.
Part 1-Intro; Part 2- Req; Part 3- Design  Chapter 20 Why evaluate the usability of user interface designs?  Chapter 21 Deciding on what you need to.
1 Rilla Khaled, Pippin Barr James Noble Victoria University of Wellington New Zealand Robert Biddle Carleton University Canada Extreme System Programming.
WordFreak A Language Independent, Extensible Annotation Tool.
Chapter 20 Why evaluate the usability of UI designs?
Overview of the rest of the semester Building on Assignment 1 Using iterative prototyping.
Requirement Engineering. Review of Last Lecture Problems with requirement Requirement Engineering –Inception (Set of Questions) –Elicitation (Collaborative.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.
Overview of the rest of the semester Iteratively design interface to help people log their food intake over the long term.
Heuristic evaluation Functionality: Visual Design: Efficiency:
Content The system development life cycle
14 June 2004System-wide Services: User InterfaceRich Moeser 1 EVLA Overall Software Design Final Internal Review System-wide Services: User Interface.
Human-computer interaction: users, tasks & designs User modelling in user-centred system design (UCSD) Use with Human Computer Interaction by Serengul.
Understanding Users Cognition & Cognitive Frameworks
Usability 1 Usability evaluation Without users - analytical techniques With users - survey and observational techniques.
A Semiotic Model of User-Interface Metaphor
14 Chapter 11: Designing the User Interface. 14 Systems Analysis and Design in a Changing World, 3rd Edition 2 Identifying and Classifying Inputs and.
Rational Unified Process Fundamentals Module 7: Process for e-Business Development Rational Unified Process Fundamentals Module 7: Process for e-Business.
Ruby on Rails Evaluation – Cognitive Dimensions Joshua Sunshine
October 2004J. B. Wordsworth J4ISDPAD1 Information Systems Development Processes and documents.
Overview and Revision for INFO3315. The exam
Interaction Design Chapter 1. Good design? Bad design?
User Interfaces 4 BTECH: IT WIKI PAGE:
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.
Modern Programming Language. Web Container & Web Applications Web applications are server side applications The most essential requirement.
CSCI 4800/6800 Human-Computer Interaction Eileen Kraemer 1/11/05.
 Introduction  Methodology  Case Study 1 : Event-B and RODN  Case Study 2 : B-Method and Atelier B  Observations and Analysis  Conclusion.
Fall 2002CS/PSY Predictive Evaluation (Evaluation Without Users) Gathering data about usability of a design by a specified group of users for a particular.
User Interface Evaluation Introduction Lecture #15.
Design Evaluation Overview Introduction Model for Interface Design Evaluation Types of Evaluation –Conceptual Design –Usability –Learning Outcome.
HCC 831 User Interface Design and Evaluation. What is Usability?
Avraham Leff James T. Rayfield IBM T.J. Watson Research Center
Easily Making IT Easy to Use
Kenneth Baclawski et. al. PSB /11/7 Sa-Im Shin
Ada – 1983 History’s largest design effort
Evaluation technique Heuristic Evaluation.
Usability Techniques Lecture 13.
User Interface Design and Evaluation
ITEC 334 Fall 2009 Computer Programming in the Web Era
Presentation transcript:

Convergence 2003 Wellington – Te Papa, 29 April 2003 Easily Making IT Easy to Use Robert Biddle, James Noble Victoria University of Wellington

Convergence 2003 Wellington – Te Papa, 29 April 2003 What is Usability? Usability: the ease with which a user can learn to operate, prepare inputs for, and interpret outputs of a system or component. (IEEE) Aspects: learnability, predictability, … Factors: experience of user, frequency of use

Convergence 2003 Wellington – Te Papa, 29 April 2003 How Can We Determine Usability? Usability Inspection Cognitive Walkthroughs Heuristic Inspection Cognitive Dimensions Framework Usability Testing Usability Lab or In-Situ Think-Aloud or Co-Discovery Action and Reflection

Convergence 2003 Wellington – Te Papa, 29 April 2003 How Can We Design for Usability? Theories Affordance Theory, Activity Theory, … Techniques Task Analysis, Essential Modelling, … Processes User-Centred Design, Goal-Directed Design, Usage-Centred Design, …

Convergence 2003 Wellington – Te Papa, 29 April 2003 How does Usability work in the Wireless World? 1960s: The Lesson of Television McLuhan: Print is Cold, TV is Hot 1990s: The Lesson of the Web Nielsen: TV is Hot, the Web is Cool

Convergence 2003 Wellington – Te Papa, 29 April 2003

How does Usability work in the Wireless World? 2000+: The Lesson of… CellPhones? PDAs? WebPhones? WAP? GPRS? ?

Convergence 2003 Wellington – Te Papa, 29 April 2003

Recent Work at Victoria in Human-Computer Interaction Approach: Usage-Centred, Object-Oriented, Agile Technology Perl, CGI, Tcl/Tk, Java, JSP, WAP, GPRS, Work with Software Engineering Lightweight Collaborative Tools Learn from the Humanities Visual Corpus Analysis Semiotics of User Interface Design

Convergence 2003 Wellington – Te Papa, 29 April 2003 CASE tools on web pages Allow simple collaboration Usable anywhere with web access Browser independent Inspirations: Wiki, Hotmail BrowserForm HTML Web ServerDBMS Servlets Lightweight Collaborative Tools

Convergence 2003 Wellington – Te Papa, 29 April 2003 Lightweight Collaborative Tools: Ukase

Convergence 2003 Wellington – Te Papa, 29 April 2003 Seek: UML Sequence Diagrams (Rilla Khaled)

Convergence 2003 Wellington – Te Papa, 29 April 2003 NutCASE: UML Class Diagrams (Dan MacKay)

Convergence 2003 Wellington – Te Papa, 29 April 2003 Cliki: Custom Graphic Interaction (Donald Gordon)

Convergence 2003 Wellington – Te Papa, 29 April 2003 Lessons from Lightweight Collaborative Web Tools Focus on users and usage Focus on models and constraints Domain specific work is easier to understand Shared state feeds groupware Less is enough Less is more

Convergence 2003 Wellington – Te Papa, 29 April 2003 Excel Spreadsheet Corpus Analysis (Daniel Ballinger)

Convergence 2003 Wellington – Te Papa, 29 April 2003 Semiotics of UI Design (Pippin Barr) Iconic: Resemblance Indexical: Causality Symbolic

Convergence 2003 Wellington – Te Papa, 29 April 2003 Work in Progress Lightweight Wireless Collaboration Wireless Usability Evaluation Visual Interaction Analysis Software Semiotics

Convergence 2003 Wellington – Te Papa, 29 April 2003

Easily Making IT Easy to Use Robert Biddle, James Noble Victoria University of Wellington