1 / 18

CS 3724 Usability Engine e ring

CS 3724 Usability Engine e ring. Section 2 CRN 11500 MW 2:30-3:45 126 McB. W e lcome !. Today’s Agenda. The team Forms Goals of class Course overview Project Readings, lectures and in-class activities Grading Policies Before you leave…. The Team. Steve Harrison Chris North

williamfields
Download Presentation

CS 3724 Usability Engine e ring

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CS 3724Usability Engineering Section 2 CRN 11500 MW 2:30-3:45 126 McB

  2. Welcome!

  3. Today’s Agenda • The team • Forms • Goals of class • Course overview • Project • Readings, lectures and in-class activities • Grading • Policies • Before you leave…

  4. The Team • Steve Harrison • Chris North • Kibum Kim (GTASection 1 CRN 11499 TuTh 5:00-6:15 ) • Jacob Somervell (GTASection 2 CRN 11500 MW 2:30-3:45)

  5. Contact Info • Email is the best way to contact the teaching team: • me (sharrison@cs.vt.edu) • Dr. North (chnorth1@vt.edu) • Jacob (jsomerve@cs.vt.edu) Section 2 CRN 11500 MW 2:30-3:45 • Web page (courses.cs.vt.edu/~cs3724) contains lecture outlines, assignments, and related materials

  6. Adminstrivia • Force-adds and prerequisite forms • CRN is 11499 • Prerequisite is CS 2604 • Everyone must complete one of the forms • Must attend today • Add decisions by next meeting • Background surveys • Used to place people on teams • Confidential • Does not affect grade

  7. Goals of Course (official version) • Survey of human-computer interaction concepts, theory, and practice. • Interdisciplinary underpinnings. • Informed and critical evaluation of computer-based technology. • User-oriented perspective, rather than system-oriented, with two thrusts: human (cognitive, social) and technological (input/output, interactions styles, devices). • Design guidelines, evaluation methods, participatory design, communication between users and system developers.

  8. Goals of Course (Steve Harrison’s version) • Learn that HCI topic is both wide and deep. • HCI is essentially about design and design involves asking good questions • Convince some of you that HCI is phat / cool • Convince the rest of you that HCI expertise is needed in most computer projects

  9. HCI and UE Analyzing, designing, and evaluatingactivities which typically involve one or more humansinteracting with (or through) computing systems to accomplish one or more tasks.

  10. A Method: Scenario-Based Usability Engineering • Stories of people and their activities • 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

  11. ANALYZE analysis of stakeholders, field studies claims about current practice Problem scenarios DESIGN Activity scenarios metaphors, information technology, HCI theory, guidelines iterative analysis of usability claims and re-design Information scenarios Interaction scenarios PROTOTYPE & EVALUATE summative evaluation formative evaluation Usability specifications

  12. Course Overview • Lectures, videos and activities • Individual homework assignments • Readings • Tests • Hall of Fame / Hall of Shame • Design project

  13. The Project • Team-based (but you already heard that) • Choose from two themes • Information vizualization • College of Engineering community information • Problem seeking / problem solving • Find users & problem, prototype, interim review presentation, evaluate, revise, final presentation • C# language

  14. Textbook • Mary Beth Rosson and John M. Carroll, Usability Engineering: Scenario-Based Development of HCI

  15. Grading Breakdown • Presentation 5% • homework (6 x 5%) 30% • Mid term 15% • Design project 40% • Team formation 0% • Requirements 10% • Formative analysis & design 20% • Interim presentation 5% • Prototype implementation 10% • Summative Evaluation 15% • Final presentation 10% • Final implementation 30% • Final 15%

  16. Key Dates Friday 1/30 10:00 am Homework 1 Friday 2/6 10:00 am Homework 2 Friday 2/13 10:00 am Team report: requirements Friday 2/20 10:00 am Homework 3 Thursday 2/26 Mid Term Friday 3/5 10:00 am Team report: Evaluation & concept Week of 4/15-4/18 Team interim presentations Friday 3/19 10:00 am Homework 4 Friday 3/26 10:00 am Homework 5 Friday 4/9 10:00 am Team project: working prototype Friday 4/16 10:00 am Homework 6 Friday 4/23 10:00 am Team report: eval. of prototype Week of 4/26-5/5 Team final presentations Thursday 5/6 10:00 am Team project turned in Monday 5/10 2:05 pm FINAL EXAM

  17. Policies • Homework due Fridays @ 10:00. Late = 0 • No early exams, make up by advance arrangement • Signed request with rationale • Reminder of VT Honor Code • Specifically, tests and homework are individual • Students with special needs see me ASAP

  18. Before you Leave… • Prerequisites form • Background information form

More Related