This course teaches the principles of constructing user interfaces. In this course you will learn how to actually implement user interfaces. Some attention is paid to issues of design and usability, but CS 449 provides more complete treatment of these topics.


This course provides an introduction to contemporary user interfaces, including the basics of human-computer interaction, the user interface design/evaluation process, and the architectures within which user interfaces are developed. Students implement and evaluate portions of typical user interfaces in a series of programming assignments.

Recommended Texts

Building Interactive Systems, 2010, by Dan R. Olsen Jr.

A copy is available on 3-hour loan at the DC library under call number UWD1512.

The Design of Everyday Things, 2013, by Don Norman.

A copy is available on 3-hour loan at the DC library under call number TS171.4 .N67 2013.

Designing with the Mind in Mind: Simple Guide to Understanding User Interface Design Guidelines, 2013, by Jeff Johnson

A copy is available on a 3-hour loan at the DC library under call number UWD1568.


We'll be using Piazza for all announcements, as well as questions and answers about the course material and assignments. Please create an account at the start of the term, using your real name and your Waterloo username; this will make it easier for course staff to identify you if required.


MWF 10:30-11:20 MC 4040 (Section 002) - Jeff Avery
MWF 1:30-2:20 MC 4040 (Section 001) - Jeff Avery
MWF 2:30-3:20 MC 4040 (Section 004) - Jeff Avery
MWF 3:30-4:20 MC 4040 (Section 003) - Alex Williams


(all email addresses are


The instructors are responsible for the course as a whole: lectures, setting assignments and exams, developing marking schemes and resolving issues related to the course.

Jeff Avery (jeffery.avery@)
Office Hours: Tues 11:00-12:00 or by appointment, DC 3107

Alex Williams (alex.williams@)
Office Hours: Thurs 11:00-12:00 or by appointment, DC 3540

Instructional Apprentices

Instructional apprentices are responsible for helping the instructor develop assignments and marking schemes, helping maintain marking consistency, resolving mark appeals, etc.

PhotoName (email)Office Hours
Shaishav Siddhpuria (spsiddhp@)By appointment
Terence Dickson(tpdickso@)Wed 10:00-11:00, DC 3540

Teaching Assistants

Teaching assistants are responsible for marking assignments, marking exams, and holding office hours.

PhotoName (email)Office Hours
Bahareh Sarrafzadeh (bsarrafz@)Thurs 3:30-4:30, DC 3540
Dallas Fraser(d6fraser@)Mon 3:00-4:00, DC 3139
Jeremy Hartmann (jeremy.hartmann@)Fri 1:00-2:00, DC 3540
Lisa Elkin(laelkin@)Fri 10:00-11:00, DC 3540
Qi Feng (Edmund) Liu (qfliu@)Tues 3:00-4:00, DC 3540
Will Callaghan(wrcallag@)Thurs 1:30-2:30, DC 3540

Instructional Support Coordinator

The ISC is responsible for long-term support for the course, maintaining the marks spreadsheet, coordinating accomodations (illness, alternate exams, etc), screening for cheating and dealing with the results.

Caroline Kierstead (ctkierst@)
MC 4009


There are four major assignments, each worth 10%, a midterm worth 20% (see schedule for date and location), and a final exam worth 40%. Final course grades will be calculated as follows:

                assignments = (A00*.01 + A01*.10 + A02*.10 + A03*.10 +  A04*.10)/.40
                exams = (.20*Midterm + .40*Final)/.60
                normal = .60 * exams + .40 * assignments
                if assignments < .50 or exams < .50
                    grade = min(.47, exams, normal) * 100 
                    grade = normal * 100 

Note: to pass the course you must pass the weighted average of the assignments and the weighted average of the exams.


Assignments are meant to provide meaningful, engaging experiences in constructing interfaces while giving you the opportunity to create applications you will want to share with others. There's lots of room for creativity in assignments and each will have a component for going above and beyond the basic assignment specification.

The assignments in this course require a significant amount of time. Do not underestimate the time it takes to code interactive applications.

Plagiarism detection software is used to screen assignments in this course to verify that students aren't sharing code in their assignments. We will report suspicious activity, and penalties for plagiarism/cheating are severe. Please read the available information about academic integrity very carefully.

Detailed assignment descriptions and due dates are posted in the course schedule when available.

There are four assignments plus a bonus:

Assignment Policies

  1. Assignments consist of writing complete, working programs that satisfy a specification. You are expected to submit working source code, and a makefile that can build it, unless otherwise directed.
  2. Assignments will be done in C++ and Java, as specified on the assignment. Code should be "platform-neutral", and can be developed the desktop platform of your choice (Windows, OS X, Linux). Exact details will be provided in the assignment specifications.
  3. Due dates are typically Fridays at 5:00 PM. Details will be on the assignment specification. Late assignments are not accepted.
  4. Submission must be via your Git repository.
  5. Assignments are your individual work:
    • You must design and implement the assignments by yourself. There are no group assignments.
    • You can use code examples provided in-class. You are allowed to directly use or include portions of in-class samples in your assignments. Some assignments may also, at the instructor's discretion, include starter code that you can use.
    • You cannot use anyone else's code in your assignments (this includes current or past students of this course), and you are prohibited from sharing your code with anyone else in the course. You can discuss how you accomplished something in general terms with other students, but sharing code in any way is prohibited.
    • No other third-party code or libraries are allowed in your assignments. You should not be searching for, and using, code that you find on the Internet (this includes GitHub, Stack Overflow and similar sites). It is perfectly acceptable to search for a general technique (e.g. how does this class work?) but you cannot use any third-party code in your assignments.
    • You should not make your code publicly available on any hosting sites (e.g. GitHub), even after the end of the term. If you wish to show your code to potential employers, you should post in a private/restricted repository instead.
  6. Grades are returned via a mark sheet added to your Git repository.
  7. Recognizing that you put in significant work on these assignments, you'll never get a zero for an honest mistake when submitting your assignments. However, marks will be deducted if TAs need to modify makefiles or add missing files, or submissions are emailed to the instructor, etc. The number of marks deducted will be determined by factors such as the amount of extra effort required by staff to rectify your mistake, the amount of time past the deadline and so on.

Java Development

For assignments, we use either C++/XLib, or Java SE 8 SDK (8u101 or later). A Java IDE is also recommended; either IntelliJ Community or Eclipse.

Git Setup

We will be using Git, a distributed version control system, for assignment submissions. You are expected to setup your account on the UW Git installation, and "push" your assignments to a private repository on that server to submit them. As per assignment policies described above, you are not allowed to publically post your assignments online in any other location.

To access your private repository for this course, you need to git-clone the repo to your local machine.

The command looks like this (replace username with your Quest login name, e.g. jdoe.git):
git clone

To submit assignments, you need to 'git add' new files, 'git commit' changes and 'git push' to the server (push sends it to the server to be graded!). See Git slides for more information.


Intellectual Property

Students should be aware that this course contains the intellectual property of their instructor, TA, and/or the University of Waterloo.  Intellectual property includes items such as:

Course materials and the intellectual property contained therein, are used to enhance a student’s educational experience.  However, sharing this intellectual property without the intellectual property owner’s permission is a violation of intellectual property rights.  For this reason, it is necessary to ask the instructor, TA and/or the University of Waterloo for permission before uploading and sharing the intellectual property of others online (e.g., to an online repository). Permission from an instructor, TA or the University is also necessary before sharing the intellectual property of others from completed courses with students taking the same/similar courses in subsequent terms/years. In many cases, instructors might be happy to allow distribution of certain materials.  However, doing so without expressed permission is considered a violation of intellectual property rights.

Academic Integrity

In order to maintain a culture of academic integrity, members of the University of Waterloo community are expected to promote honesty, trust, fairness, respect and responsibility. [Check for more information.]


A student who believes that a decision affecting some aspect of his/her university life has been unfair or unreasonable may have grounds for initiating a grievance. Read Policy 70, Student Petitions and Grievances, Section 4, When in doubt please be certain to contact the department's administrative assistant who will provide further assistance.


A student is expected to know what constitutes academic integrity [check] to avoid committing an academic offence, and to take responsibility for his/her actions. A student who is unsure whether an action constitutes an offence, or who needs help in learning how to avoid offences (e.g., plagiarism, cheating) or about 'rules' for group work/collaboration should seek guidance from the course instructor, academic advisor, or the undergraduate Associate Dean. For information on categories of offences and types of penalties, students should refer to Policy 71, Student Discipline, For typical penalties check Guidelines for the Assessment of Penalties,


A decision made or penalty imposed under Policy 70 (Student Petitions and Grievances) (other than a petition) or Policy 71 (Student Discipline) may be appealed if there is a ground. A student who believes he/she has a ground for an appeal should refer to Policy 72 (Student Appeals)

Students with Disabilities

AccessAbility Services collaborates with all academic departments to arrange appropriate accommodations for students with temporary or permanent disabilities without compromising the academic integrity of the curriculum. If you require academic accommodations, please register with the AccessAbility Services at the beginning of each academic term.