School of Electrical Engineering and Computer Science
Oregon State University
Tue & Thu at 4:00 - 5:50pm
Prof. Minsuk Kahng
Assistant Professor, School of Electrical Engineering and Computer Science
E-mail: [email protected]
In this class, you will learn basic principles of Human-Computer Interaction (HCI), including how to design and prototype user interfaces and interactive systems, based on the needs of users, and how to evaluate such interfaces and systems rigorously.
At the completion of this course, students will be able to:
CS 565 is a hands-on course. You'll be expected to actively participate in projects, activities, and discussion. A significant portion of the class will be devoted to a team project (~4-person groups). Each team will design, prototype, and evaluate user interfaces.
Because of this highly interactive nature, we will use a "flipped classroom" model for this term. We will still meet at our scheduled class time via Zoom, but you will do readings and watch videos before the class, and during the class time, we will be doing in-class activities and project working sessions with your teammates.
It is mandatory to attend classes. The in-class activities will be counted towards your final grade, and the project working sessions will be crucial for working on your project deliverables.
Your performance will be evaluated via group projects, individual assignments, quizzes, and active participation. There will be no final exams. Instead, we will consider:
Note: The team receives one grade for the group project. However, allocation of the grade among team members will in some cases not be equal, if team members do not contribute relatively equally to the effort.
We use Canvas for all announcements and submission of projects and assignments, but not for questions.
We use Piazza for questions and discussion. The fastest way to get help with homework assignments is to post your questions on Piazza. That way, our TAs and instructor can help, and your peers can too.
If you prefer that your question addresses to only our TAs and the instructor, you can use the private post feature (i.e., check the "Individual Students(s) / Instructors(s)" radio box). For special cases such as failed submissions due to system errors, missing grades, failed file uploads, emergencies that prevent you from submitting, personal issues, you can contact the staff using a private Piazza post. Emails will not be the fastest way to get response from the staff. Please use Piazza first.
Office Hours TBA
|1||Mon, Mar 30||Introduction 1: Course Introduction||* Pre-quarter Survey|
|Wed, Apr 1||Introduction 2: Design Process||* HW 1: Project Ideas|
|2||Mon, Apr 6||Evaluation 1: Heuristic Evaluation||* HW 2: Heuristic Evaluation|
|Wed, Apr 8||Human Capabilities 1: Perception||* Project Team Assignment|
|3||Mon, Apr 13||Human Capabilities 2: Memory||* Project 1: Proposal|
|Wed, Apr 15||Knowing Your Users 1: Observation||* HW 3: IRB|
|4||Mon, Apr 20||Knowing Your Users 2: Interviews||* Project 2: User Research|
|Wed, Apr 22||User Research into Ideas 1: Data Analysis|
|5||Mon, Apr 27||User Research into Ideas 2: Ideation||* Project 3: Ideation|
|Wed, Apr 29||Poster Presentations (1)||* Poster Feedback|
|6||Mon, May 4||Prototyping 1: Storyboarding and Paper Prototyping||* Project 4: Low-fi Prototyping|
|Wed, May 6||Prototyping 2: Visual Design||* HW 4a: Prototyping - Digital Mockups|
|7||Mon, May 11||CHI Conference||* Project 5: Iteration & Mid-fi|
|Wed, May 13||Poster Presentations (2)||
* HW 4b: Prototyping - Static HTML page
* Poster Feedback
|8||Mon, May 18||Evaluation 2: Usability Testing||* Project 6: User Evaluation|
|9||Mon, May 25||HCI Research: Accessiblity, Designing for AI||* HW 5: Paper Critique|
|Wed, May 27||Evaluation 3: Controlled Experiments|
|10||Mon, June 1||Project Final Presentation|
|Wed, June 3||Project Final Presentation||* Project 7: Final Report|
|11||No Final Exam|
Your mission is to critique the design of the existing user interfaces and redesign it that involves substantial improvements, carefully and thoroughly following the methods and principles from CS 565. Guide your efforts by following the design process we will cover in the class. Details will be provided in the first meeting of the class.
This class is our community. Every student should feel safe and welcome to contribute in this course, and it is all of our jobs to make sure this is the case. I will try to establish this tone whenever possible, but ultimately the responsibility for cultivating a safe and welcoming community belongs to the students---that means you! Fortunately, forming a safe and welcoming community is not too hard. A good place to start is to recognize (and continually remind yourself) of the following facts:
In addition, the OSU Expectations for Student Conduct apply.
In short, treat your classmates as respected colleagues, support each other when needed, have fun without spoiling it for anyone else, and everybody wins.
Academic dishonesty will not be tolerated in this course. This includes plagiarism, cheating, and knowingly assisting others in either of these. (Please see the OSU Code of Student Conduct Section 4.2 "Academic Misconduct" for official guidelines.) If you are found to be guilty of academic dishonesty, you will receive a penalty grade (0 on the assignment and additional deduction on other assignments within the same category) and be reported to the Office of Student Conduct and Community Standards. You will also face the possibility of further disciplinary action (such as suspension from class, your program, or the university). Academic misconduct, or violations of academic integrity, can fall into seven broad areas, including but not limited to: cheating; plagiarism; falsification; assisting; tampering; multiple submissions of work; and unauthorized recording and use. It is important that you understand what student actions are defined as academic misconduct at Oregon State University. The OSU Libraries offer a tutorial on academic misconduct, and you can also refer to the OSU Student Code of Conduct and the Office of Student Conduct and Community Standard’s website for more.
Plagiarism: Remember that ANY sources you use in your assignment must be cited, including any electronic sources. Plagiarism is preventable. If you have any questions about how to use outside resources properly, what counts as plagiarism, etc., please ask me. The following are some general examples of plagiarism: copying without quotation marks, copying someone else's code or scripts, copying someone else's design, using someone else's facts or ideas without citing your source, paraphrasing someone else's writing without acknowledgment, taking passages from another author, with slight changes to grammar or to the arrangement of the sentences, which make little or no difference to the meaning: This is plagiarism!
Accommodations for students with disabilities are determined and approved by Disability Access Services (DAS). If you, as a student, believe you are eligible for accommodations but have not obtained approval please contact DAS immediately at 541-737-4098 or at http://ds.oregonstate.edu. DAS notifies students and faculty members of approved academic accommodations and coordinates implementation of those accommodations. While not required, students and faculty members are encouraged to discuss details of the implementation of individual accommodations.
CS 565 was offered by Prof. Kahng in Spring 2020 and had been taught by Prof. Margaret Burnett, and this year's course is largely adapted from her design.