Fall 2017 students: This year, we're splitting the course into 2 numbers (you can think of it as two sections with the same lecture). CSCI 130 will have the same lecture, labs, and readings as CSCI 1300 but half of the assignments will be different. CSCI 1300 will have assignments with computer science prerequisites (involving more statistics, logic, programming), so you should have taken the computer science introductory sequence before taking CSCI 1300. You may choose which one you want to take, but you won't be able to take the other one for credit in the future. CSCI 1300 provides 1000-level CS credit, but CSCI 130 does not, so CS concentrators may prefer CSCI 1300. Typically, a number of RISD students also take the course; RISD students should come to the first day of class to get information about enrolling. There is currently no waitlist: if CSCI 1300 is full and you want to take CSCI 1300, then register for CSCI 130 until the semester starts, and we'll shuffle you to CSCI 1300 afterwards.
This course will cover concepts in human-computer interaction that focus on designing user interfaces. Topics include understanding when to use different interfaces, modeling and representing user interaction, principles of user experience design, eliciting requirements and feedback from users, methods for designing and prototyping interfaces, and user interface evaluation. Students interested in learning the process behind building a user interface and gaining hands-on experience designing a user interface should take this course.
Nearly all course information will be available on the course website. The course is expected to require 10 hours / week of work outside class for assignments, readings, labs, and other activities.
Location: To be determined
Time: 6:40-8:00pm on Tuesdays and Thursdays
|Day||Lecture||Reading Due (on day of lecture)||Assignment||Assignment due|
|Sep 10 & 11||UI Camp|
|Sep 13||History||Portfolios||Journal||Sundays until Oct 30|
|Sep 20||Pointing||Buxton - Input||Input||Sep 26|
|Sep 27||Understanding||Adams and Cooper - Personas||Personas||Oct 5 (extended)|
|Oct 4||Models||Cooper - Undo Save||A/B Testing||Oct 12 (extended)|
|Oct 11||Affordances||Norman - Design||Redesign||Oct 17|
|Oct 18||Navigation||Rivers - Navigation||Sitemap||Oct 24|
|Oct 25||Prototyping||Buxton - Sketching||Sketching||Nov 1 (in class) & 7|
|Nov 1||Visual||Vignelli - Canon||Mockups||Nov 7|
|Nov 8||Output||Hery - UI State||Responsive||Nov 14|
|Nov 15||Evaluation||Rogers - Evaluation||Playtesting||Nov 21|
|Nov 22||HCI (optional)||Kramer and followups||Deception OR Development||Nov 28, Nov 30|
|Nov 24||Thanksgiving (holiday)|
|Dec 1||Social||Goffman and Eggers|
|Dec 6||Presentations||Dec 5|
|Sep 13||Ha Phan||Product Designer||GoPro|
|Sep 27||Courtney George||Experience Designer||Adobe|
|Oct 11||Andrew Evans||Product Designer||IDEO|
|Oct 20||Larry Goldberg||Accessibility Director||Yahoo|
|Oct 25||Alex Hadik||UX Designer & Frontend Developer||IBM|
|Nov 8||Jill Woelfer||UX Researcher|
|Nov 10||Behzad Aghaei||UX Designer||Apple|
|Dec 1||Jessica Tran||Design Researcher||Microsoft|
Jeff Huang, 407 CIT, jeff @cs.brown.edu
Office hours: Tuesdays 2:30-4:30pm
Lily George (Head TA) lily_georgebrown.edu
Neilly Tan (Head TA) neille-ann_tan @brown.edu
Jina Yoon (Head TA) jina_yoon @brown.edu
Shaun Wallace (Graduate TA) shaun_wallace @brown.edu
Please do not email any individual TA or Head TA. They have been advised to ignore emails not sent to the TA list. This is to ensure we apply a consistent policy for questions, and so you can get a faster response to your emails.
Assignments are graded by undergraduate TAs and reviewed by Head TAs, using a rubric developed with the instructor. If you feel an assignment was graded unfairly, first reach out to the TA who graded you - if you still disagree, please email the Graduate TA (shaun_wallacecs.brown.edu) and explain why you think your assignment deserved a better grade. The Graduate TA will make a determination about whether your score will be changed within a week.@
Slides will be posted just before class starts but may be available on Canvas beforehand. Readings and assignments will be posted one week in advance with the due date for reading comments or assignment in parentheses (submit everything to Canvas).
TAs will lead multiple labs during the semester outside of the course lecture hours where students can gain experience with a specific interaction design tool or UI development for a specific platform. They will be in a tutorial + exercise format, and take place in List 315. Students should take 4 labs in total (UI Camp counts as 2).
UI Camp will be a bootcamp run by the TAs to have small groups work with 5 different design tools on various small design tasks. It will be an all-day workshop that happens on the weekend following the first day of class, and be considered as a Lab. UI Camp is new this year, and considered optional, but students are strongly encouraged to participate. UI Camp and the UX Visitors Series are generously supported by Adobe and Balsamiq.
|Lab 1: Balsamiq + Invision||Link||Link||Link|
|Lab 2: Sketch + XD||Link||Link||Link|
|Lab 3: Illustrator||Link||Link||Link|
|Lab 4: Photoshop||Link||Link||Link|
|Lab 5: proto.io + Quant UX||Link||Link||Link|
|Lab 6: Principle + Figma||Link||Link||Link|
|Lab 7: Framer||Link||Link||Link|
|Lab 8: React||Link||Link||Link|
No-show policy: if you sign up for a lab and can't attend, please let us know at least 24 hours ahead of time -- otherwise, you'll lose priority for lab signups, and will have to sign up after everyone else. This might make it hard to sign up for four labs, so please try to let us know ahead of time if you need to miss a lab.
Reading comments are due at 11:55pm on the due date listed in the schedule. No late reading comments will be accepted, except by using a late pass (see below). For assignments 20%, of an assignment grade will be deducted for each week it is late. So an assignment turned in 9 days late will have 40% points off.
All student get 3 late passes, each of which can be used to compensate for an assignment or reading comment turned in 3 days (72 hours) late (usable once per assignment or reading comment). These will be automatically applied at the end of the course. Note that each late pass reimburses 1% of the total course grade. There are no benefits to having extra late passes when the semester ends. Any further accomodation requires a note sent to the Head TA contact email from either 1) a Dean of the College or 2) Health Services or a Doctor stating the time period of not being able to do coursework.
The Collaboration Policy explains the policies around working with other students or using outside-class resources for your assignment. It can be viewed in Canvas and is marked as an assignment worth 0 points. Your work will not be graded until you have agreed to the collaboration policy by submitting that assignment.