Lecture2a - Design

Embed Size (px)

Citation preview

  • 8/9/2019 Lecture2a - Design

    1/53

    Week 2: Design

    o Introduction to Usability

    o The Design

    o Design: Defining goals and personas

    o CSCW

    o Mobile

  • 8/9/2019 Lecture2a - Design

    2/53

  • 8/9/2019 Lecture2a - Design

    3/53

    Related Questions today???

    o What is usability?

    o Why is usability important?

    o How measuring usability?

  • 8/9/2019 Lecture2a - Design

    4/53

    What is poor usability?

    To end-users..

    I cant findwhat Im

    looking for

    Its very fancy,but its not very

    useful

    I find it a bitfrustrating

    I dont think itseems trustworthy

    Cant it be

    more likeGoogle?

    I really like it,but I dont use it

    much

    It doesnt dowhat I need it

    to do

  • 8/9/2019 Lecture2a - Design

    5/53

    What is poor usability?

  • 8/9/2019 Lecture2a - Design

    6/53

    What is Usability???

    o User Friendly ???

    o Is not a synonym ofusability

    o Avoid this expression!

  • 8/9/2019 Lecture2a - Design

    7/53

    What is Usability???

    o Its not about is this product usable?

    o But its about how usable this product?

  • 8/9/2019 Lecture2a - Design

    8/53

    What is Usability???

  • 8/9/2019 Lecture2a - Design

    9/53

    What is Usability???

    o The effectiveness,efficiency,

    and satisfaction with which

    specified users achieve

    specified goals in particularenvironments.

    o source: ISO 9241-11

    o applies equally to bothhardware and software design

  • 8/9/2019 Lecture2a - Design

    10/53

    What is Usability???

    ISO 9241-11:

    o Effectiveness: The accuracy and completeness with which

    specified users achieve their own goals with the system.

    o Efficiency: The resources expended in relation to the accuracyand completeness of goals achieved.

    o Satisfaction: The comfort and acceptability of the system tothe users and other people affected by its use.

  • 8/9/2019 Lecture2a - Design

    11/53

    What is Usability???

    Jacob Nielson's definition:

    oL

    ear

    nab

    ility:

    How easy is it for users to accomplish basic tasksthe first time they encounter the design?

    o Efficiency: Once users have learned the design, how quicklycan they perform tasks?

    o Memorability: When users return to the design after a periodof not using it, how easily can they reestablish proficiency?

  • 8/9/2019 Lecture2a - Design

    12/53

    What is Usability???

    Jacob Nielson's Definition (cont.):

    o Errors: How many errors do users make, how severe are theseerrors, and how easily can they recover from the errors?

    o Satisfaction: How pleasant is it to use the design?

  • 8/9/2019 Lecture2a - Design

    13/53

    What is Usability???

  • 8/9/2019 Lecture2a - Design

    14/53

    Attributes of usability

  • 8/9/2019 Lecture2a - Design

    15/53

    User as starting point

  • 8/9/2019 Lecture2a - Design

    16/53

    Why usability is important?

    o system development is expensive, and supporting a poorlydesigned user interface is even more expensive;

    o users will reject or work around systems that do not meet theirneeds;

    o design teams need to discover all problems users have in orderto provide remedies;

    o even the best designers are not representative of the users ofthe system, thus teams need to understand users' perspectivesand experiences with other systems;

  • 8/9/2019 Lecture2a - Design

    17/53

    Why usability is important?

    o usability evaluation is an inexpensive way to improve systems

    before they are implemented, to improve existing systems,

    and to choose usable systems;

    o business users do not have a lot of time to spend learning how

    to use a system;

    o businesses cannot train fast enough to keep pace with attrition

    and changing business rules;

  • 8/9/2019 Lecture2a - Design

    18/53

    Why usability is important?

    o people prefer a usable system with fewer features to a system

    with gratuitous "bells and whistles" which they have to work

    hard at figuring out; and

    o people often use systems in ways developers did not expect,

    and if designers find this out, they can build these features

    into a new system

  • 8/9/2019 Lecture2a - Design

    19/53

    Where?

    o Usability testing can be done wherever it is

    o in a real work setting

    o or in a usability lab

  • 8/9/2019 Lecture2a - Design

    20/53

    When???

    o During early design stages to:

    o Predict product usability

    o Check design teams understanding of user requirements

    o Test out ideas

    o Later in design process:

    o Identify user difficulties

    (fine tune product)

    o Improve upgrade a product

  • 8/9/2019 Lecture2a - Design

    21/53

    How conducting usability evaluation?

    Usabilitymethods

    Testing

    Inspection

    Inquiry

    -Laboratory testing-Thinking aloud

    -Heuristic Evaluation-Cognitive Walkthrough

    -Focus Group-Questionnaires

  • 8/9/2019 Lecture2a - Design

    22/53

    Principles in testing

    o Use real users

    o Design real tasks

    o Record and report the test

  • 8/9/2019 Lecture2a - Design

    23/53

    How many subjects?

  • 8/9/2019 Lecture2a - Design

    24/53

    How many subjects?

  • 8/9/2019 Lecture2a - Design

    25/53

    Setting up usability testing

  • 8/9/2019 Lecture2a - Design

    26/53

    Measuring Usability

    o What can be measured?

    o Performance measures: Counts of actions and behaviours

    you can see

    o Subjective measures: Peoples perceptions, opinions and

    judgments

  • 8/9/2019 Lecture2a - Design

    27/53

    Measuring usability

    Effectiveness Efficiency User satisfaction

    1. Percent task complete

    2. Ratio of success tofailures

    3. Number of featuresused

    1. Time to complete task

    2. Time to learn

    3. Time spent on errors

    1. Rating scale for

    usefulness

    2. Rating scale for

    satisfaction3. Number of times user

    express frustration

  • 8/9/2019 Lecture2a - Design

    28/53

    Measuring Usability

    o Timeo The time taken to complete a task on a computer is an

    obvious metric to choose. Whiteside et al (1985) have

    proposed the following empirical relationship:

  • 8/9/2019 Lecture2a - Design

    29/53

    Measuring Usability

    o Error Rateo All users make errors. The number and type of errors made

    during the performance of a particular task by a user is

    clearly an indication of the usability of the system

    o Attitude Measureso attitude of the user of a system usually has to be found by

    using questionnaires or interviews. These measures cancover complete system use, from learnability, to ease of

    use, to functionality.

  • 8/9/2019 Lecture2a - Design

    30/53

    Measuring Usability

  • 8/9/2019 Lecture2a - Design

    31/53

    The Design

    Dr. Nor Azman Ismail

  • 8/9/2019 Lecture2a - Design

    32/53

  • 8/9/2019 Lecture2a - Design

    33/53

  • 8/9/2019 Lecture2a - Design

    34/53

  • 8/9/2019 Lecture2a - Design

    35/53

  • 8/9/2019 Lecture2a - Design

    36/53

  • 8/9/2019 Lecture2a - Design

    37/53

  • 8/9/2019 Lecture2a - Design

    38/53

  • 8/9/2019 Lecture2a - Design

    39/53

  • 8/9/2019 Lecture2a - Design

    40/53

    Video example ofBMW iDrive

  • 8/9/2019 Lecture2a - Design

    41/53

  • 8/9/2019 Lecture2a - Design

    42/53

  • 8/9/2019 Lecture2a - Design

    43/53

  • 8/9/2019 Lecture2a - Design

    44/53

    Design: Defining goals and personas

    Dr. Nor Azman Ismail

  • 8/9/2019 Lecture2a - Design

    45/53

  • 8/9/2019 Lecture2a - Design

    46/53

  • 8/9/2019 Lecture2a - Design

    47/53

  • 8/9/2019 Lecture2a - Design

    48/53

  • 8/9/2019 Lecture2a - Design

    49/53

  • 8/9/2019 Lecture2a - Design

    50/53

  • 8/9/2019 Lecture2a - Design

    51/53

  • 8/9/2019 Lecture2a - Design

    52/53

  • 8/9/2019 Lecture2a - Design

    53/53