September 1, 2011: The first lecture for 344/544 will be Thu Sept 8, 9:30.
Tutorials/Labs begin on Wednesday September 14.

cs344 and its graduate version cs544 are the entry points to the CS HCI curriculum for both undergraduate and graduate students. Full listing of our HCI offerings

• general information
• course overview
• course policies
• deliverables and marking scheme

Human Computer Interaction design is "design for human use". CPSC 344/544 is a fast-paced, hands-on, project based course that will challenge many of your ideas of what computer science is and can be, if you have not been previously exposed to these concepts.

Computers are a ubiquitous part of many interactions in our lives, from the mundane every-dayness of light switches and "smart" vending machines to entertainment and education to sophisticated instruments and complex energy and defense systems. In this course, we will challenge you to broaden your grasp of what a user interface can and should be, and try your hand at doing better yourself.

CPSC 344 and 444 form a two-course sequence.
CPSC 544 is crosslisted with 344. Intended for graduate students without introductory HCI background, it meets the Computer Science breadth requirement.

Upon completion of this course, students will have:

• an awareness of HCI as a field, both historically and in its future direction
• the ability to critique and analyze interfaces in the real world, both good and bad, in terms of their complementing (or failing to do so) human abilities and limitations
• a healthy skepticism for the relevance of their own design judgment, and appreciation of the value of user-centered design
• an ability to apply basic techniques and the iterative process to create and analyze user interfaces, as well as a basic understanding of the process’s drivers
• detailed knowledge and experience with the standard basic techniques for interface prototyping and informal evaluation
• some preparation for how to make HCI practices work effectively in the face of real-world constraints.

This course is designed around Problem Based Sessions (tutorials) carried out in the CS Department's HCI Learning Studio. We will used team-based learning techinques in small groups lead by our crack TA team to practice and explore the concepts introduced in lecture, and go well beyond them to learn and apply HCI techniques in the group project.

In addition to all university rules, regulations, and academic guidelines, the following policies will hold in CS344:

• Attendance and prompt arrival is expected at all lectures, tutorials and labs. Quiz, assignment and team project marks will suffer from absences. A doctor's note is required to substantiate any illness.

• There will be no makeup for the midterm. Should the midterm be missed, the final exam will absorb the midterm's component of the grade.
• A student must pass the final exam in order to pass the course. If you fail the final exam (score <50%), your final course grade will equal your final exam grade.
• To request that a deliverable be fully or partially re-graded:  the request must be submitted in writing (not via email and not verbally) and the full copy of the deliverable must be resubmitted together with the written request. We reserve the right to re-grade the entire deliverable.
• Late assignment or project components will receive no credit. You are free to submit them, and we may review them during marking. However, your mark for the late work will be a 0.
  --> Contact the instructor or your TA promptly (i.e., as soon as you are aware of the problem) if a medical or family reason prevents you or your team from handing a project component in on time. In other extraordinary circumstances, we may allow late turn-in if you contact cs344@ugrad with a clear explanation of the problem well in advance of the deadline (i.e., at least 48 hours). Poor planning or procrastination do not constitute extraordinary circumstances!

Your team's performance in the course project plays a large part in your individual mark. In addition, in your individual mark there are significant peer and TA / instructor evaluation components which relate to your contributions and participation in your team and in the lecture component in the class.

* The "overall" component of the project mark:

Ambitiousness, ingenuity and resourcefulness; general excellence and quality of improvement as assessed at conclusion of project. Also known as "redemption is possible". Assessed by the entire course staff with input from the final project presentation design jury, assembled from HCI professionals in industry and academia.

** The instructor/TA component:

This mark component is to capture individual contributions to your team's success, and your overall class participation, using input provided by your TA as well as the instructor's direct observation and iteraction.

The baseline (default) will be AT LEAST the value noted in table above; and will be raised if this is felt appropriate. To get 100/100 in this component requires exceptional contributions to your team and in class participation. "Just doing the work" doesn't get the top mark.

You will be assessed in 3 categories: 1. individual contribution to project (i.e. below or above the baseline expectation); 2. tutorial and lecture participation; and generally 3. making good use of instructor and TA, and showing courtesy and good teamwork throughout.

• Factors that improve it: Participating in tutorials through meaningful comment and discussion. Asking thoughtful questions and generally making good use of the staff's time and expertise. Active involvement in lecture sessions. Competently and diplomatically taking a leadership role in the project (this is not limited to the "project leader" which is an administrative designation). Demonstrating creativity, agility and progress in any aspect of project learning. Generally making good use of the instructor and class; proactively engaging the instructor when there's an issue about project or any other aspects of learning (through office hours etc) rather than letting it fester. Giving constructive feedback about suggested improvements for the class.
• Factors that that drive it down: Missing tutorials or failing to attend the the whole time. Don't seem to be working with the group. Regularly missing project-time labs. Consistently arrriving late at tutorials and lectures (disruptive) without travel-hardship exemption and other failures of courtesy. Seriously failing to engage in the class. Showing discourtesy or disrespect to your classmates or the course staff. Letting down your team.