Docstoc

Introduction to Human-Computer Interaction

Document Sample
Introduction to Human-Computer Interaction Powered By Docstoc
					                IST 413
User Interface Design and Development
   Instructor is John M. Carroll
     307H IST Building, jmcarroll@psu.edu


   TA is Blaine Hoffman
     316 IST Building, bhoffman@ist.psu.edu


   Course info at
    http://courses.ist.psu.edu/SP06/IST413/


                             1
                 Today’s Agenda

   Administration
     Go over Syllabus materials
     Quality Process overview
   Content
     What is this course about (usability engineering)?
     Where did the area of HCI/UE come from?
     How did it develop during the past 30 years?
   Your Questions



                               2
         Key things to bear in mind

   There is a lot of graded work in this class
     We read 1 book cover to cover, and many articles
     There are 10 graded homeworks
     There are 12 in-class activities; 3 involve written group
      work
     There are 10 quizzes
     There is a group project lasting 15 weeks with 3
      document deliverables, 1 case study hypertext, plus an
      implemented Web-site
   It’s not that difficult to do well by keeping up
   If you fall behind, you may not be able to recover
                                3
                     Administrivia
   Enrollment must be carried out today
     The course starts today
     Students not here today are dropped
   Background surveys
       Will be used in forming project teams
       Self-ratings of experience on several dimensions
       Ratings will be confidential, won’t affect grade
       Fill them out right now
   Class roles
     Debaters, homework discussion leaders, example givers
     Get “dibs” on a role+date by sending me email by
      tomorrow (jmcarroll@psu.edu)
                                 4
            Research and Learning
   I do research on how people learn, specifically on
    how they learn through collaborative project-
    based activity
   I was a co-author on the course textbook
   I am a co-developer of a collection of cases at
    http://ucs.ist.psu.edu
   Students in this class participate in the research we
    are doing about the class (and benefit from some
    of the research we did before)
   Informed Consent


                             5
          HCI and Usability:
         History and Concepts
   What is human-computer interaction (HCI)?
     Where did it come from? How has it developed?
   What is usability?
     Origins and development
   Usability engineering
     Scenario-based usability engineering




                              6
                      What is HCI?
 computer science  social, cognitive, behavioral science
 integrate tech dev w/ planning/assessing impacts/utility

                 Technical Support for Users
             Documentation, Training, Help, Education



                            Human-
                           Computer
                          Interaction

                         Collaboration
        Support for System Development Process
Design methods and models; Usability evaluation methods and tools
                                  7
           Where did HCI come from?

   Software Engineering
     software crisis: applications outrunning technology
     formal methods not even formally adequate
   Software Psychology
     experiments and surveys to clarify problems and codify
      principles
   Computer Graphics
     proto-GUIs: technology outrunning applications



                                  8
                  HCI in the 1970s
   work within an assumed process
     tweaking at the end of the “waterfall”
     principal research objective was guidelines
   describe the user
     extreme dichotomies, unrepresentative content
     Newell: playing 20-questions with nature
   verify usability experimentally
     coarse, quantitative, time & errors studies
     too costly & uninformative


                                 9
                    HCI in the 1980s
   Iterative development (vs. waterfalls)
     prototyping, mock-ups
     formative evaluation (thinking aloud)
     usability engineering, usability specifications
   Models and theory (versus guidelines)
     the model human processor: Fitts’ Law, GOMS
     mapping models: syntactic-semantic consistency
     the active user: prior knowledge, problem solving, and error
      as primary resources
   Gradual better integration with UI technology


                                 10
                    HCI in the 1990s
   UE is multifaceted, qualitative, field-oriented
     participatory design, contextual design, ethnographically-
      informed design
     drives/integrates system development lifecycle
   Conceptual frameworks beyond user models
     activity theory, ethnomethodology, distributed cognition,
      grounded theory, design rationale, …
     But diminishing role in mainstream discourse
   User interface technology too well integrated!


                                 11
Context of HCI: Changes in Computer Use
                        Professional programmers,
 1960’s                 “software psychology”

                        Business professionals,
 1970’s                 mainframes, command-line

                        Large, diverse user groups,
 1980’s                 “the computer for the rest of us”

                        World Wide Web and more,
  1990’s                information access & overload

                        Ubiquitous computing,
  2000+                 diversity in task, device, …


                   12
         What is Usability?
              Human performance,
                time and errors




                   Usability

Human cognition,               Collaboration,
  mental models                group
        of plans               dynamics and
    and actions                workplace
                               context




                         13
     The developing concept of usability
   1970s -- human factors engineering
     Taylorism: minimize time and errors
   1980s -- cognitive science and engineering
     internal consistency of displays and interactions
     match interaction to cognitive architecture (sophisticated
      Taylorism)
     match domain-specific knowledge-based expectations:
      metaphoric design
     support and exploit problem-solving, error recognition,
      diagnosis and recovery


                                14
      The developing concept of usability
   1990s -- organizational task analysis
     group interaction, collaborative synergy vs. process losses,
      power and status, conflict and cooperation
     business process/work practices, work flow vs. invisible
      work
     common ground, knowledge management, peer-driven
      professional development
     preference and fun, affective computing
     accessibility, customization (tailorability),
      internationalization (localization)


                                  15
        Why Usability Engineering?

   Waterfall models of development do not work
     too many unknowns (Brooks: No Silver Bullet)
   Need an iterative discovery-oriented process
     but at the same time need to manage it
   Demands well-defined process with metrics
     specifying usability goals as objectives
     assessing and redesigning to meet these objectives
     manage usability as a quality characteristic, much like
      modularity or nonfunctional requirements



                               16
Can We /How Should We Measure Usability?

     Bottom line is whether the users got what they
      wanted, i.e., is the client satisfied
     Practically speaking, need to break this down so
      that we can operationalize our objectives
     Our textbook definition:
      the quality of an interactive computer system with respect
        to ease of learning, ease of use, and user satisfaction
       can the users do what they want to do in a comfortable
        and pleasant fashion?



                                 17
    Scenarios in Usability Engineering

   Stories of people and their activities, sometimes
    includes computer use, always includes goals
   Typical elements of the story are:
       a setting
       one or more actors or agents
       an orienting or motivating goal or objective
       mental activity, plans or evaluation of behavior
       a “storyline” sequenced by actions and events
   Emphasis on use, i.e., people’s needs, expectations,
    actions, and reactions

                                18
Scenarios in UE: A Simple Example
A problem scenario describing current situation:
Marissa was not satisfied with her class today on
gravitation and planetary motion. She is not certain
whether smaller planets always move faster or how a larger
or denser sun would alter the possibilities for solar systems.

She stays after class to speak with Ms. Gould, but she isn’t
able to pose these questions clearly, so Ms. Gould suggests
that she re-read the text and promises more discussion
tomorrow.




                              19
 A design scenario describing our initial vision:
Marissa , a 10th-grade physics student, is studying gravity and its role
in planetary motion. She goes to the virtual science lab and navigates
to the gravity room.
In the gravity room, she discovers two other students, Randy and
David, already working with the Alternate Reality Kit, which allows
students to alter various physical parameters (such as the universal
gravitational constant) and then observe effects in a simulation world.
The three students, each of whom is from a different school in the
county, discuss possible experiments by typing messages from their
respective personal computers. Together they build and analyze several
solar systems, eventually focusing on the question of how comets can
disrupt otherwise stable systems.
They capture data from their experiments and display it with several
visualization tools, then write a brief report of their experiments,
sending it for comments to Don, another student in Marissa’s class, and
Mr. Arkins, Randy’s physics teacher.

                                    20
     an artist’s
     rendition of the
     initial design
     scenario




21
The Final ‘Virtual School’ System




                22
Why
Scenarios?
                          scenarios         scenarios
                       are concrete         describe use in
                descriptions but are        detail, but as a
                  also very flexible        tentative, working
                                            representation



             scenarios offer      Scenario-Based        scenarios focus
       a vivid description of      Development          on the usability
          use that provokes                             consequences of
       questions and “what                              specific design
              if” discussions                           proposals
                                  scenarios describe
                                the problem situation
                                     using natural
                                language understood
                                  by all stakeholders


              1.6: Be precise but include everyone on the team
                                       23
   Scenario-based usability engineering

              scenario-based envisionment
               and usability specifications

People                                           New
                        Task-
and                     Artifact                 interactive
their                   Cycle                    computing
activities                                       systems

               Scenario-based analysis and
             evaluation of refinements and new
                        opportunities

                             24
                        ANALYZE
  analysis of                                       claims about
stakeholders,
                    Problem scenarios                  current
 field studies                                         practice


                         DESIGN
     metaphors,          Activity             iterative
     information        scenarios             analysis of
     technology,                              usability
     HCI theory,                              claims and
     guidelines    Information scenarios      re-design

                   Interaction scenarios



                   PROTOTYPE & EVALUATE
 summative                                           formative
 evaluation
                   Usability specifications          evaluation

                             25
          Course Topic Overview
Scenario-Based Development
Requirements Analysis        PROJECT 1

Activity Design
Information Design
                             PROJECT 2
Interaction Design
Prototyping
Usability Evaluation         PROJECT 3

Documentation
Emerging Paradigms
Usability in Practice
                        26
               Tradeoffs and SBD

   Design by definition is invention, creativity
     never just one approach, never one correct answer
     BUT some answers are demonstrably better
   Interactive system design tremendously complex
     many interdependencies, eg schedule, cost, competitive
      advantage, local expertise, ...
     users and their needs are one large set of dependencies
   Tradeoffs are useful in analyzing these relations
     here, we focus on tradeoffs affecting users’ experiences
     guides design thinking, also serves as design rationale


                               27
       Learning SBD — By Example

   Virtual science fair as a case study
     complement to real world physical science fairs
     goal is to extend fair interactions, across time & space
   Cumulative, illustrates activities at each phase
     detailed examples of the methods used in projects
     use as a model for your group’s materials & analyses
   Many details specific to this example
     e.g., collaboration, community network, education
     other case studies under construction on the Web at
      http://ucs.ist.psu.edu


                               28
The scope of human-computer
         interaction
Analyzing,
      designing, and
             evaluating,
activities, which typically involve
      one or more humans
             interacting with
                   computing systems
to accomplish one or more tasks

                    29

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:8
posted:10/15/2012
language:English
pages:29