Upload
brittney-miles
View
218
Download
0
Tags:
Embed Size (px)
Citation preview
Housekeeping Register from the waitlist Facebook page: 2015 version please! Course website under construction Need to form MP1 groups by January 16th
12 UG’s + 29 G’s = ~41 students (anyone auditing?)
Want 8-9 groups => ~4-5 students Can be a mix of grad/UG
CSCI 4163 / CSCI 6610, Winter 2014Human-Computer Interactionweb.cs.dal.ca/~hawkey/4163
Dr. Kirstie Hawkey, [email protected]
Basic Info Instructor: Kirstie Hawkey TA: Hasmeet Singh Chandok Office: Room 225, Goldberg building KH Office hours: 2-4 pm, Wednesdays
Course is offered as both an undergrad course (4163) and a graduate course (6610)
NOTE: Tutorial/Lab in LINC room 2600, Killam Library on Fridays, 12:05-1:25 - initial project brainstorming this Friday!
Website: web.cs.dal.ca/~hawkey/4163 Facebook:
www.facebook.com/groups/901037349916233/
Class style Pre-assigned readings Additional resources Some lecture content Interactive exercises HCI topic seminars (breadth!) Group work:
2 mini-projects Understanding the user’s needs Controlled laboratory evaluation of a technique
Individual work: Topic seminars Research paper (grad) Reading responses Participation/peer evaluation/quizzes 3 assignments
Human Computer Interaction Human
The user of a computer program, computerized device, or other information technology artifact
Computer The physical device, artifact, or hardware that
runs the program
Interaction The communication between the human and the
computer
Why Care about the human?
Moore’s Law
transistorsspeeddiscscost
1950 1990 2030Slide idea by Bill Buxton
Computerabilities
Slide: Saul Greenberg
Psychology
1950 1990 20302000BC
human
abilities
Slide idea by Bill Buxton
Where is the bottleneck?
Slide idea by Bill Buxton
system performance
Slide: Saul Greenberg
Human Computer Interaction A discipline concerned with the
of interactive computing systems for human users
design implementation
evaluation
Slide: Saul Greenberg
User Centered Design
process figure: http://www.yucentrik.ca/en/expertise-2/tools/
Our focus:1. Methods for
understanding user needs
2. Methods for evaluating interfaces and techniques with users
3. Theories/models of human performance
NOT DESIGN(3160 in the Fall for user
interface design, prototyping, discount usability evaluation)
User Interface Design HCI
CSCI 3160: UI DesignIterative Design
Design architecture of system Draw UI sketches/task scenarios Prototyping Evaluate with users (primarily
formative) Redesign Implement Prototypes and evaluate
(heuristics, cognitive walkthroughs) Design Considerations
Graphic output/input Errors Design and layout Task
Software E.g., GUI toolkits,
CSCI 4163 – HCIUnderstand users
Learn about their needs, tasks, etc. Understand how users do something
to help inform design decisions Understand relevant theories
Critically understand different experimental approaches to understand and evaluate systems
When to use which approach (advantages and disadvantages)
Analyze results and use these to develop guidelines
Quantitative and qualitative data
Evaluate high fidelity prototypes, interaction techniques, etc. (often summative, comparative)
Course goals
To understand strengths and weaknesses of different experimental methods in HCI To learn about how theories/human models of human performance impact interactionTo develop an appreciation for experimental HCI research and how it can refine the theories/modelsTo be able to apply these techniques to do basic HCI research To learn about User Experience as a career path
Fostering a good learning environment More details at https://www.hackerschool.com/manual#sec-
environment
Don’t let fear, bravado, or the imposter syndrome stand in your way of understanding/learning
Social rules: No feigning surprise at a lack of knowledge
Yes: I was also wondering about that! No well-actually’s
Instead: “Yes, and ….!” No back-seat driving
Yes: give constructive feedback through peer evaluation No subtle –isms
racism, sexism, homophobia, transphobia, and other kinds of bias (technofile-ism?, Windows-ism?) Any others?
Embrace the diversity of perspectives in this room
Keys for success in this class Show up to class and tutorials!
Experiential learning, discussions, activities Read the readings
Be rigorous and reflective Document your efforts Do things for a reason (hopefully a good one!) Examine tradeoffs Justify your approach
Be a good group member BUT… you have problems within your group – address
them (with me) early! Marks will not be evenly distributed among group
members if there is documented evidence of unequal effort
Homework for Thursday’s class Read Chapter 2 of The Encyclopedia of Human
Computer Interaction http://www.interaction-design.org/encyclopedia/
human_computer_interaction_hci.html
Submit (Email? Moodle?) to Hasmeet 2 questions/comments about the reading BEFORE class on Thursday Excellent (2 pts): thought provoking, insightful,
original, good discussion points Good (1 pt): relevant Bad (0 pt): completely irrelevant, comments not
sent or sent late
Plagiarism - Don’t Do It
Kirstie Hawkey originally written in 2003 when I was a PhD Student, Teaching Assistant, & Lecturer
Basic defs
Plagiarism “the submission or presentation of the work of
another as if it were one's own.” http://www.dal.ca/dept/university_secretariat/academic-
integrity/plagiarism-cheating.html
Other cheating Other violations of academic integrity
http://www.dal.ca/dept/university_secretariat/academic-integrity/plagiarism-cheating/other-cheating.html
Academic Integrity Quiz Individually & then we’ll discuss
Don’t Do It
In order not to “do it”, you need to know what it is. Go to Dalhousie’s Academic Integrity website
(http://www.dal.ca/dept/university_secretariat/academic-integrity.html)
Talk to our CS Librarian Gwendolyn McNairn if you have questions or talk to the Writing Center
For each class, find out what level of collaboration is allowed
Exercise to do at home: You Quote It, You Note It tutorial
http://libcasts.library.dal.ca/Tutorials/QuoteNoteA/
Do you REALLY understand?
Don’t sign anything that says that you understand what plagiarism or academic integrity is unless you really do understand it
Make it your first priority to really understand it Dal tutorials in academic integrity and citing
http://libraries.dal.ca/using_the_library/online_tutorials.html
Another Good Tutorial https://www.indiana.edu/~istd/sitemap.html
Don’t Do It We can catch you… we have the technology
Google – a great way to find information, a great way to find where plagiarizers found information
Your TA’s and professors are computer scientists with brains used to seeing patterns. Changing a few words or rearranging something rarely fools us.
Don’t Do It Dalhousie has subscribed to SafeAssign
Compares submissions with online databases
It’s not just writing We can analyze your code and detect
similarities
Compiled code can be compared to the submissions of previous years. Rearranging functions and renaming variables and
changing indentation doesn’t change the underlying structure – and that is what is compared.
Learn how to express yourself Demonstrate to your professor that you know
the material Your ability to cut and paste is not what you will
be marked on. A paper full of quotations says that you don’t
understand it well enough to use your own words
Protect yourself Don’t let others see your written words. Keep collaboration with others at the concept
level. Lock your computer when you leave it, even if
just for a minute. Make sure you are aware what is being
submitted on your behalf for group work.
Don’t Do It
The faculty is making a strong effort to curb plagiarism.
Don’t become the next person with an F in a course and a notation on their transcript of academic dishonesty for the sake of a better mark on a 4% assignment What seems like the easy way out at the time
carries some heavy consequences
Faculty AIOs
Computer Science Dr. Denis Riordan, Associate Dean
Email: [email protected] Dr. Christian Blouin
Email: [email protected]
Graduate Studies Dr. Eileen Denovan-Wright, Associate Dean
Email: [email protected]
Don’t Do It Just don’t
History of HCI Slides from Saul Greenberg FYI if curious
History of Human Computer Interaction Where did HCI innovations and philosophy come
from? Who were the major personalities? What were the important systems? How did ideas move from the laboratory to the
market?
History of HCI
Input/output devices (2005) Input Output
Early daysconnecting wires lights on displaypaper tape & punch cards paperkeyboard teletype
Today (2005) keyboard scrolling glass teletype
+ cursor keys character terminal + mouse bit-mapped screen + microphone audio
Soon? data gloves + suits head-mounted displays
computer jewelry ubiquitous computing
natural language autonomous agentscameras multimedia
The lesson keyboards & terminals are just artifacts of today’s technologies new input/output devices will change the way we interact with computers
History of HCI
RAND’s vision of the future (1954)
From ImageShack web site //www.imageshack.us ; original source unknown
History of HCI
Eniac (1943)
A general view of the ENIAC, the world's first all electronic numerical integrator and computer.
From IBM Archives.
History of HCI
Mark I (1944)
The Mark I paper tape readers.
From Harvard University Cruft Photo Laboratory.
History of HCI
Stretch (1961)
A close-up of the Stretch technical control panel.
From IBM Archives.
History of HCI
Intellectual foundations
Vannevar Bush (1945)
“As we may think” article in Atlantic Monthly http://www.theatlantic.com/magazine/archive/1945/07/
as-we-may-think/3881/
Identified the information storage and retrieval problem:new knowledge does not reach the people who could benefit from it
“publication has been extended far beyond our present ability to make real use of the record”
History of HCI
Bush’s Memex
Conceiving Hypertext and the World Wide Web a device where individuals stores all personal
books, records, communications etc items retrieved rapidly through indexing, keywords,
cross references,... can annotate text with margin notes, comments... can construct and save a trail (chain of links)
through the material acts as an external memory!
Bush’s Memex based on microfilm records! but not implemented
mmmm mmmmmmm mmmmmm mmm
mmmm mmmmmmm mmmmmm mmm
mmmm mmmmmmm mmmmmm mmm
mmmm mmmmmmm mm
mmmm mmm
History of HCI
J.C.R. Licklider (1960)
Outlined “man-computer symbiosis”
“The hope is that, in not too many years, human brains and computing machines will be coupled together very tightly and that the resulting partnership will think as no human brain has ever thought and process data in a way not approached by the information-handling machines we know today.”
History of HCI
J.C.R. Licklider (continued)
Produced goals that are pre-requisite to “man-computer symbiosis”
Immediate goals: time sharing of computers among many users electronic i/o for the display and communication of
symbolic and pictorial information interactive real time system for information
processing and programming large scale information storage and retrieval
History of HCI
J.C.R. Licklider (continued)
intermediate goals: facilitation of human cooperation in the design &
programming of large systems combined speech recognition, hand-printed
character recognition & light-pen editing
long term visions: natural language understanding (syntax,
semantics, pragmatics) speech recognition of arbitrary computer users heuristic programming
History of HCI
Significant Advances 1960 - 1980
Mid ‘60s computers too expensive for a single person
Time-sharing the illusion that each user was on their own
personal machine led to immediate need to support human-computer
interaction dramatically increased accessibility of machines afforded interactive systems and languages vs batch “jobs” community as a whole communicated through computers
(and eventually through networks) via email, shared files, etc.
History of HCI
Ivan Sutherland’s SketchPad-1963 PhD
Sophisticated drawing package introduced many ideas/concepts now found in today’s
interfaces
hierarchical structures defined pictures and sub-pictures object-oriented programming: master picture with
instances constraints: specify details which the system maintains
through changes icons: small pictures that represented more complex items copying: both pictures and constraints input techniques: efficient use of
light pen world coordinates: separation of
screen from drawing coordinates recursive operations: applied to
children of hierarchical objects
From http://accad.osu.edu/~waynec/history/images/ivan-sutherland.jpg
History of HCI
Ivan Sutherland’s SketchPad-1963 PhD Parallel developments in hardware: “low-cost” graphics terminals input devices such as data tablets (1964) display processors capable of real-time
manipulation of images (1968)
Videos: http://www.youtube.com/watch?v=USyoT_Ha_bA http://www.youtube.com/watch?
v=BKM3CmRqK2o&feature=related
History of HCI
Douglas Engelbart
The Problem (early ‘50s)“...The world is getting more complex, and problems are getting more urgent. These must be dealt with collectively. However, human abilities to deal collectively with complex / urgent problems are not increasing as fast as these problems.
If you could do something to improve human capability to deal with these problems, then you'd really contribute something basic.”
...Doug Engelbart
History of HCI
Douglas Engelbart
The Vision (Early 50’s) …I had the image of sitting at a big CRT screen with all kinds of symbols, new and different symbols, not restricted to our old ones. The computer could be manipulated, and you could be operating all kinds of things to drive the computer
... I also had a clear picture that one's colleagues could be sitting in other rooms with similar work stations, tied to the same computer complex, and could be sharing and working and collaborating very closely. And also the assumption that there'd be a lot of new skills, new ways of thinking that would evolve "
...Doug Engelbart
History of HCI
Douglas Engelbart
A Conceptual Framework for Augmenting Human Intellect (SRI Report, 1962)
"By augmenting man's intellect we mean increasing the capability of a man to approach a complex problem situation, gain comprehension to suit his particular needs, and to derive solutions to problems.
One objective is to develop new techniques, procedures, and systems that will better adapt people's basic information-handling capabilities to the needs, problems, and progress of society."
...Doug Engelbart
History of HCI
The First Mouse (1964)The First Mouse (1964)
History of HCI
AFIP Fall Joint ConferAFIP Fall Joint Conference, 1968ence, 1968
Document ProcessingDocument Processing– modern word processingmodern word processing– outline processingoutline processing– hypermediahypermedia
Input / OutputInput / Output– the mouse and one-handed corded the mouse and one-handed corded
keyboardkeyboard– high resolution displayshigh resolution displays– multiple windowsmultiple windows– specially designed furniturespecially designed furniture
Shared workShared work– shared files and personal annotationsshared files and personal annotations– electronic messagingelectronic messaging– shared displays with multiple pointersshared displays with multiple pointers– audio/video conferencingaudio/video conferencing– ideas of an Internetideas of an Internet
User testing, trainingUser testing, traininghttp://vimeo.com/1408300
History of HCI
The Personal Computer Alan Kay (1969)
Dynabook vision (and cardboard prototype) of a notebook computer:
“Imagine having your own self-contained knowledge manipulator in a portable package the size and shape of an ordinary notebook. Suppose it had enough power to out-race your senses of sight and hearing, enough capacity to store for later retrieval thousands of page-equivalents of reference materials, poems, letters, recipes, records, drawings, animations, musical scores...”http://www.youtube.com/watch?v=r36NNGzNvjo
Ted Nelson 1974: “Computer Lib/Dream Machines” popular book describing what computers can do for
people (instead of business!)
History of HCI
The Personal Computer
Xerox PARC, mid-’70s Alto computer, a personal workstation
local processor, bit-mapped display, mouse modern graphical interfaces
text and drawing editing, electronic mail windows, menus, scroll bars, mouse selection, etc
local area networks (Ethernet) for personal workstations could make use of shared resources
ALTAIR 8800 (1975) Popular electronics article that showed people
how to build a computer for under $400
History of HCI
Commercial machines: Xerox Star-1981 First commercial personal computer designed for
“business professionals”
First comprehensive GUI used many ideas developed at Xerox PARC familiar user’s conceptual model (simulated desktop) promoted recognizing/pointing rather than
remembering/typing property sheets to specify appearance/behaviour of
objects what you see is what you get (WYSIWYG) small set of generic commands that could be used
throughout the system high degree of consistency and simplicity modeless interaction limited amount of user tailorability
History of HCI
Commercial Machines: Apple Lisa (1983)
based upon many ideas in the Star predecessor of Macintosh, somewhat cheaper ($10,000) commercial failure as well
http://fp3.antelecom.net/gcifu/applemuseum/lisa2.html
History of HCI
Other events: MIT Architecture Machine Group
Nicholas Negroponte (1969-1980+) many innovative inventions, including
wall sized displays use of video disks use of artificial intelligence in interfaces (idea of agents) speech recognition merged with pointing speech production multimedia hypertext ....
ACM SIGCHI (1982) special interest group on computer-human interaction conferences draw between 2000-3000 people www.chi2011.org http://chi2011.org/program/videos.html
HCI Journals Int J Man Machine Studies (1969) many others since 1982
History of HCI
You know now:
HCI importance result of:
cheaper/available computers/workstations meant people more important than machines
excellent interface ideas modeled after human needs instead of system needs (user centered design)
evolution of ideas into products through several generations pioneer systems developed innovative designs, but often
commercially unviable settler systems incorporated (many years later) well-researched
designs
people no longer willing to accept products with poor interfaces