HCI/ECT 441 Dr. Craig Barnes Office Hours: Tues 5:00pm-5:45pm Tues 9:00pm-9:45pm Office: ?
ECT/HCI Course Info Course Web Site: Check it often.
Course Grading zHomeworks:40% zUser Testing: 15% zFinal:35% zIndividual Contribution: 10%*
Disciplines contributing to HCI
Web Usability Problems
User Centered Development Differs from traditional software development: zUser Centric zInterdisciplinary zHighly iterative
User Centered Development Initial Stages: zNeeds Analysis zUser and Task Analysis zFunctional Analysis zRequirements Analysis
Needs Analysis Simple Description of zType of System zAudience
User Analysis Characterizes potential user of site: zGeneral Demographics zContext of Use
User Analysis Benefits: zCost reduction in: ydevelopment & maintenance ySupport yTraining zIncreased sales
User Analysis zKey: Know your user zAdvice: Site developers are NOT users
User Analysis General Characteristics: zLearning Style zTool Preference zPhysical Differences zCultural Differences
Learning Style How do users learn? zRead then Do zDo then Read
Tool Preference Set of tools users are familiar with: zDrop Down menus zComplex Searches Find the Least Common Denominator
Physical Differences Accessibility issues: Physical Disabilities Color Perception Perception of small objects Smaller buttons require finer motor control
Cultural Differences zGeographical or Not: zEducation zProfession zCorporate Culture
Specific User Characteristics Type of users actively visiting site zWhy they use it zWhat they are doing zHow they are doing it
Knowledge of Jobs If site is part of work environment: zHow do users do their job? zUnderstand fit in workflow? zSpecialized vocabulary
Application Familiarity Determine users’ technical proficiency: zNovice zAdvanced Beginner zCompetent Performer zExpert
Gathering Information Who do you ask? zManagers? zDevelopers? zPrimary Users zSecondary Users
Gathering Information Places to find information: zUsers zCustomer Service zTechnical Support zMarketing
Task Analysis Know what users do: zGoals zTasks zActions
Task Analysis Build description of users’ duties: zWhat tasks are performed zWhy perform them zHow tasks are performed
Goals zStarting point for task analysis zWhat user want to accomplish zIndependent of technology
Tasks Mechanism for accomplishing goals zCan be technology dependent zComposed of sub-components called Actions
Granularity zLevel or amount of detail in a task zBreak task into successively finer steps zDepends on nature and scope of site
Granularity zWorkflow Analysis zJob Analysis zTask List z Task Sequences z Task Hierarchies z Procedural Analysis Successively finer levels of granularity: