CS 449/649 Spring 2017
MW 02:30 - 03:50 in MC 4058Announcements:
Final report requirements are posted.
Groups for heuristic evaluation:
Hercules <-> Team 23
UIIBSME <-> Biscuits
Glasses <-> Travellers
Xiphias <-> Piece of Cake
Awesome <-> Omnilingual
WeatherReady <-> Critically Acclaimed
Bridge Brigade <-> Team SE
TovrShare -> JJJ -> SportyBunch -> TovrShare
Course Policies:
For assignments and the final report deliverables: submit a soft copy by 5:59 pm on the due date.
You are not allowed to submit the next assignment if the previous assignment was not submitted.
Failing to submit all the assignments and final report by the end of the term may result in failing the course.
Use the provided LaTex template or Word template to write your assignments and the final report.
Late penalties for deliverables: -1% for each additional day (6:00 pm to 6:00 pm).
If assignment was not submitted before the next assignment due date, you will get 0% for this assignment,
however next assignment will not be considered submitted until you submit all the previous assignments.
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 www.uwaterloo.ca/academicintegrity/ for more information.]
Grievance:
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, www.adm.uwaterloo.ca/infosec/Policies/policy70.htm.
When in doubt please be certain to contact the department's administrative assistant who will provide further assistance.
Discipline:
A student is expected to know what constitutes academic integrity [check www.uwaterloo.ca/academicintegrity/] 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, TA, or the undergraduate Associate Dean.
For information on categories of offences and types of penalties, students should refer to Policy 71,
Student Discipline, www.adm.uwaterloo.ca/infosec/Policies/policy71.htm.
For typical penalties check Guidelines for the Assessment of Penalties, www.adm.uwaterloo.ca/infosec/guidelines/penaltyguidelines.htm.
Appeals:
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) www.adm.uwaterloo.ca/infosec/Policies/policy72.htm.
Note for Students with Disabilities:
The Office for persons with Disabilities (OPD), located in Needles Hall, Room 1132, collaborates with all academic departments
to arrange appropriate accommodations for students with disabilities without compromising the academic integrity of the curriculum.
If you require academic accommodations to lessen the impact of your disability, please register with the OPD at the beginning of each academic term.
Marking Scheme:
| Deliverable | Due Date | Weight | |
|---|---|---|---|
| CS 449 | CS 649 | ||
| In-class quizzes | May 8 - July 17 | 5% | 5% |
| Assignment 1 | May 17 | 6% | 8% |
| Assignment 2 | June 7 | 8% | 10% |
| Presentation 1 | June 14 | 7% | 6% |
| Assignment 3 | June 28 | 10% | 12% |
| Presentation 2 (+ video of demo) | July 19 | 14% | 11% |
| Final Report | July 24 | 20% | 24% |
| Final Exam | August 4, 7:30pm - 10:00pm | 30% | 24% |
Project Topics:
- Apartment renting application
- Managing personal finances
- Notekeeping application / task manager
- Application for language learning / new words translation
- Application for finding participants for studies
- Application to manage personal medications
- Movie/TV shows recommendations
- Cooking / recepies finding/keeping application
- Application for scheduling / coordinating schedules
- Personal fitness managing application/workout suggestions
- Application for roommates
- Managing personal bills
- Learning basics of programming
- Learning random interesting facts
- Choosing appropriate clothing for the weather
- Dealing with procrastination/locking other apps/increasing productivity
- Time management application
- Packing for a travel app
- App for board game enthusiasts
- Keeping track of expiry dates for groceries
- Clothing/accessories/shoes matching
- Keeping lists(catalogs?) of books/movies
- Finding ideas for a date/evening/party/etc.
- Getting/keeping/organising lifehacks
- News by selected topics
Please, use the provided LaTex template or Word template to write the assignment.
CS 449: 2-3 pages + appendix: 6%
CS 649: 3-4 pages + appendix: 8%
Submit to Dropbox on Learn by 5:59 pm, May 17
In this assignment you will make an initial presentation of your project. The assignment should include the following four sections:
1. Description of the project
In this section you are expected to describe the general market segment you are targeting,
and what potential contributions you see as important for the area. Take this as an opportunity to describe what
motivates you to work on this specific project and what potential value you can
bring to the area. What problems / empty niches did you identify and how? How can your project address
those problems? That will naturally lead you to the next section.
Example: In the AirBnB video we watched in class: Joe Gebbia is talking about how they come up with the idea, that it was solving problems of finding place to stay during the conference, and how different they want this experience to be from the regular hotel stay.
2. Goals and Hypotheses
Here we ask you to specifically list the goals of your application and hypotheses you will be testing.
What exactly are you focusing on within your market segment? What problems/obstacles do you want to solve?
What information do you need to have in order to do so? What do you hypothesise regarding this information
(you also need to briefly justify your hypotheses; if you use information from external sources, make sure
you reference it appropriately).
Example: In the AirBnB video we watched in class: They realized that they need to help users to form trust, both for hosts and for guests. But how do you form this trust? Should there be communication prior to arrival? What should be communicated, would providing additional information help? If so, what kind of information and how much should people say?
3. Target user groups & users for the studies
An important part of identifying your market segment is to understand who your target users are.
Does it mean your application can be used only by those user groups? Most likely no.
But at least that is something we can start working with. Depending on your project topic,
you may need to include different types of information here.
Try to picture one or several *illustrative* generalized users of your future application.
What separates them from others? Does it matter what area of the city they live in? Or does their age group,
social status, everyday activities, language, common means of transportation, education, etc., matter?
Once you identify your main target user group(s), think about participants for your studies.
You need to design a group of participants that would be representative for your target user groups.
You will need to work with 3-5 users for each of your user studies. Describe in this section relevant
demographics for your future group of participants.
Example: In the David Kelley's video: Kids (preschoolers, young teenagers, etc.) as users for MRI in the hospital, personas we have created in class.
4. Plan for observation & interviews
Finally, when everything above is identified, we now need to know what exactly we are planning to
do with our user study participants. First step in this course is the exploratory user study,
which should include observations and interviews. Why do we do that? First, through this study you can test some of the hypotheses
you described in the corresponding section above, and shed some light to the information you identified as
required for your project. Second, you will most likely see some new information you did not anticipate,
so make sure when planning your study to avoid leading questions (see lectures) and leave space to any free-form
feedback your participants might have.
In this section, please, describe your observation and interview designs.
For observations - what is the environment you want you observe in, what type of observation are you planning to use,
what action do you ask your participants to take, how long do you want each section to be and why (note that observations
should not be longer than 15 min per session). For interviews - describe what you are planning to achieve
through interviews and how this information can be used for your project, provide a list of questions you are
planning to ask in appendix (note that interviews should not be longer than 15 min per session).
ONLY FOR CS 649 STUDENTS:
Graduate students are required to have an additional section - literature review on the chosen topic. Please review some academic
literature on behavioural, design, and/or social aspects related to the chosen project.
Your assignment then should include 5 sections:
1. Description of the project
2. Related literature
3. Goals and Hypotheses
4. Target user groups & users for the studies
5. Plan for observation and interviews
Marking breakdown:
Description of the project 0.5%
Goals & Hypothesis 1%
Target user groups & users for the studies 2%
Plan for observation & interviews 2%
Quality of the presentation (Structure; Language; Visualisation) 0.5%
ONLY FOR CS 649 STUDENTS: Related literature 2%
Please, use the provided LaTex template or Word template to write the assignment.
CS 449: 2-3 pages + appendix: 8%
CS 649: 3-4 pages + appendix: 10%
Submit to Dropbox on Learn by 5:59 pm, June 7
Please, include the name of your team in a title of your assignment.
Attach copies of all your consent forms to this assignment.
1. Exploratory study results
Now, when you have already conducted your exploratory studies (observations and interviews), you need to report on your findings.
In class we have discussed how to make your qualitative data actionable: first, we use for that purpose affinity diagrams as a tool
to help us identify common themes in our data, second, we use work models - artifact, cultural, physical, flow and sequence models.
In this section of your assignment you need to report on your study results.
- Name and describe themes you have identified using an affinity diagram.
Attach a picture of the affinity diagram you have created with your team in appendix.
- Name and describe what themes and breakdowns you have identified when working on all 5 work models.
Attach a picture of each *consolidated* (combining all your participants)
work model - artifact, cultural, physical, flow and sequence - created with your team in appendix.
- Conclude by discussing all your findings with respect to your original hypotheses:
what did you learn? Did you prove your hypotheses? Was anything unexpected in your result? Which of the identified
problems will you focus on? What could be reasons for these problems? What in your data can provide insight to address
these problems?
2. Design ideas
After formulating the results of your exploratory study and identifying specific problems you want to focus on,
it is time to think about how we can solve these problems with design.
- When creating design solutions, you first need to brainstorm possible high-level ideas of how a challenge can be approached.
Describe here the solutions you have chosen for your design solutions. Describe how they will address the challenge and why.
For example, in class we identified one of the problems with unpacking hoverboards - people would not look through the manual.
Possibly, because they are very excited to start using hoverboard as soon as possible (supported by data).
One possible solution there would be to place important instructions on how to start using the device directly on a hoverboard,
so that users would necessarily see it. Another part of this design solution - to use drawings instead of text,
not to rely on System 2 thinking triggering.
- Now, when design solutions are chosen, you need to visualize them and integrate them into some specific system
(smartphone application in our case). To visualize ideas and the workflow, at the beginning we use sketches which
then help us to create low-fidelity (paper) prototypes. Both sketches and paper prototypes are fast, cheap and easy to create.
Describe your user flow here and support it with examples of user stories. Include sketches that outline your users flow in
the appendix.
Note: At this stage you only need to submit a rough layout (statical) of an application you are designing.
These sketches should not be paper prototypes yet. You will need to submit descriptive pictures of the paper prototype(s)
you have created with your team in the next (!) assignment.
3. Plan for prototype test and evaluation
How do we know that the solution we have designed would actually solve the challenge and suit our users’ needs?
We test and evaluate the ideas and prototypes. Although you do not need to submit your paper prototypes yet, you
should already plan what you want to test and evaluate about your prototypes. In this section you need to:
- Formulate goals for your evaluation studies,
- Formulate and defend hypotheses for your evaluation studies,
- Provide a detailed plan for your paper prototypes evaluation studies
(including verbal script of instructions and description of the environment settings). Note: each study session should not be longer than 15 min.
ONLY FOR CS 649 STUDENTS:
Graduate students are required to have an additional section - literature review,
relevant to the challenges you want to focus on and your design solutions.
Please review some academic literature on behavioural, design, and/or social aspects related to
the challenges and your solutions. Your assignment then should include 4 sections:
1. Exploratory study results
2. Design ideas
3. Related literature
4. Plan for prototype test and evaluation
Marking breakdown (449):
Exploratory study results 33%
Design ideas 33%
Test and Evaluation studies plan 27%
Quality of the presentation (Structure; Language; Visualisation) 7%
Marking breakdown (649):
Exploratory study results 29%
Design ideas 29%
Related literature review 15%
Test and Evaluation studies plan 22%
Quality of the presentation (Structure; Language; Visualisation) 5%
Please, use the provided LaTex template or Word template to write the assignment.
CS 449: 2-3 pages + appendix: 10%
CS 649: 3-4 pages + appendix: 12%
Submit to Dropbox on Learn by 5:59 pm, June 28
Please, include the name of your team in a title of your assignment.
Attach copies of all your consent forms to this assignment.
1. Results of paper prototype evaluation
- First reflect on results in relation to the study goals you have previously identified
for your paper prototype evaluation. Did you meet all your goals? If no, what is your opinion on why that happened?
Did your study design reflect your goals well and why?
- Then report on discovered themes and detailed results of your paper prototype evaluation study.
How do your results correspond to your hypotheses? What trends/themes did you find? What specifically did you learn
about your design in relation to each theme? You need to report both on positive results (what did you find to be good design decisions)
and negative results (identified problem areas in your design). Give your analysis on why identified design problems may occur,
what causes them.
- In this assignment you also need to submit descriptive images of your paper prototypes that have been tested.
Include all tested screens and interactions, support with short notes if required. You can attach your images in
appendix or as a separate file.
2. Design progression
- Use this section to describe and discuss changes that should be made to your initial design
(used in the tested paper prototype) to address prototype evaluation results. Explain in detail why you expect each specific
suggested change to be beneficial compared to the original design.
- Wireframes: Wireframes are important for visualization and documentation purposes. With high level of precision and details,
they should reflect such aspects of your design as structure of content on your screens and intended user flow through screens.
Thus, creating wireframes is a valuable step on your way from ideation to high fidelity product implementation.
In this assignment you need to submit wireframes for your project. You can attach your wireframes composition in
appendix or as a separate file. Note that:
- Wireframes should reflect design changes you have identified as required.
- Wireframes should include all screens you are planning to include in your high fidelity prototype.
- Wireframes organization should reflect the anticipated user flow for major usage scenarios (use arrows and notes)
3. Plan for high fidelity prototype evaluation
First describe your goals for high fidelity prototype evaluation. What type of information do you expect to get and why do you need it?
What questions do you want to answer through this evaluation?
Describe your plan for heuristic evaluation. What set heuristics are you planning to use and why
(in relation to your goals)? Provide a set of scenario based tasks you are planning to use for the evaluation and briefly
discuss your reasoning for chosen scenarios. Note: heuristic evaluation is to be conducted with an assigned group and does not
require consent forms since it includes only the class members.
Describe your plan for cognitive walkthrough evaluation. Include a description of the study environment and verbal script of the
instructions for your participants. Provide set of scenario based tasks you are planning to use for the evaluation. If it is
different from the set for heuristic evaluation, discuss your reasoning. Note: consent forms are required.
If you are planning to use any additional methods, provide a detailed plan, including a description of the study environment
and verbal script of the instructions for your participants.
Marking breakdown (449 and 649):
Results of paper prototype evaluation 35%
Design progression 36%
Plan for high fidelity prototype evaluation 24%
Quality of the presentation (Structure; Language; Visualisation) 5%
Please, use the provided LaTex template or Word template to write the final report.
CS 449: 8-12 pages + appendix: 20%
CS 649: 12-16 pages + appendix: 24%
Submit to Dropbox on Learn by 5:59 pm, July 24
Please, include the name of your team in a title of your final paper.
Attach copies of all not yet submitted consent forms to your final submission as a separate file .
Your final paper should include all work you have done for your project throughout the course.
As you might notice from the marking breakdown, it is important for us to see that you have addressed our
feedback throughout the course.
While split into sections, final paper should still tell one coherent story of your project development.
Description of the project
Describe the general market segment you are targeting,
potential contributions you see as important for the area, what potential value you are bringing to the area,
what problems / empty niches you originally identified and how your project addressed them.
Goals of the project
What specifically you are focusing on within your market segment and what exact purpose(s) do you see for your project.
Only CS 649 student:
General literature review on the chosen topic.
Product anticipated users
In this section describe user groups you have identified for your product and include personas you have created.
Exploratory study
In this section you are expected to have the following:
- description of goals, hypotheses and focus you have formulated for your exploratory studies,
- description of your participants (number, average age, gender distribution, other demographic information important for your study),
- description of methods you have used including brief summary of your study designs: what were you observing and what
themes you covered in your interview question
- report on exploratory study results: describe and discuss identified themes and detailed results, problems (breakdowns) you decided to focus on.
Initial design ideas
- Discuss how you decided to address identified problems and why.
- Describe what specific information from your exploratory results you used in your design.
- Include sketches and images of your paper prototypes (final versions) - you can include some images
in your main text for illustrative purposes, but appendix should contain all images, clear, readable and in good quality.
Only CS 649 student:
Literature review relevant to the challenges you want to focus on and your design solutions.
Paper prototypes and evaluation
In this section you are expected to have the following:
- description of goals and hypotheses you have formulated for your paper prototype evaluation study,
- description of your participants (number, average age, gender distribution, other demographic information important for your study),
- set of scenario/goal based tasks you gave to your participants,
- report on paper prototype evaluation results: describe and discuss identified themes and detailed results,
your analysis of possible reasons for identified problems in design.
Design progress
- Describe design adjustments you have identified as required based on paper prototype evaluation results,
provide corresponding reasoning.
- Include wireframes you have created - you can include some images in your main text for illustrative purposes,
but appendix should contain all images, clear, readable and in good quality.
High fidelity prototypes and evaluation
In this section you are expected to have the following:
- description of goals you have formulated for your high fidelity prototype evaluation study,
- description and results of heuristic evaluation:
--- description of your participants,
--- name used heuristics and reasoning for choosing them,
--- description of used scenarios and goal-based tasks,
--- report on results
- description and results of cognitive walkthrough:
--- description of your participants (number, average age, gender distribution, other demographic
information important for your study),
--- description of used scenarios and goal-based tasks,
--- report on results
- report on consolidated required design changes identified in the studies.
Conclusion
Use this section to provide comparison of the initial project
ideas and the final result, to reflect on design process you went through and to include
you final thoughts on the project.
Marking breakdown (CS 449):
Description and goals of the project - 7%
Product anticipated users - 7%
Exploratory study - 15%
Initial design ideas - 6%
Paper prototypes and evaluation - 15%
Design progress - 7%
High fidelity prototypes and evaluation - 15%
Conclusion - 8%
Feedback integration - 15%
Quality of the presentation (Structure; Language; Visualisation) 5%
Marking breakdown (CS 649):
Description and goals of the project - 5%
Product anticipated users - 5%
General literature review - 7%
Exploratory study - 13%
Initial design ideas - 5%
Design-relevant literature review - 7%
Paper prototypes and evaluation - 13%
Design progress - 6%
High fidelity prototypes and evaluation - 13%
Conclusion - 5%
Feedback integration - 17%
Quality of the presentation (Structure; Language; Visualisation) 4%
Course Description & Objectives:
Human-Computer Interaction teaches the fundamental issues that underlie the creation and evaluation of usable and useful computational artifacts.By the end of course, you will be able to:
- Identify the primary luminaries relevant to Interactive Design and HCI
- Identify major movements in HCI research, and their motivations, philosophies, and goals
- Identify your target users, design studies to understand your users and their needs within a sociocultural context
- Create user data driven designs and prototypes of different levels of fidelity
- Design studies to evaluate design on different stages of development
- Properly gather and analyze qualitative and quantitative data from user studies including data from: in-situ observations, semi-structured interviews, field studies, in-house experiments, heuristic evaluations
- Distinguish bad and good experimental design
- Add a high quality design of your own product to your portfolio
Course mainly consists of four types of students’ activities:
- Lectures
- In-class activities
- Assigned readings
- Individual group project performed throughout the term in groups of 3-4 students
Marking Scheme:
| Deliverable | Due Date | Weight | |
|---|---|---|---|
| CS 449 | CS 649 | ||
| In-class quizzes | May 8 - July 17 | 5% | 5% |
| Assignment 1 | May 17 | 6% | 8% |
| Assignment 2 | June 7 | 8% | 10% |
| Presentation 1 | June 14 | 7% | 6% |
| Assignment 3 | June 28 | 10% | 12% |
| Presentation 2 (+ video of demo) | July 19 | 14% | 11% |
| Final Report | July 24 | 20% | 24% |
| Final Exam | August 4, 7:30pm - 10:00pm | 30% | 24% |
Course Policies:
For assignments and the final report deliverables: submit a soft copy by 5:59 pm on the due date.
You are not allowed to submit the next assignment if the previous assignment was not submitted.
Failing to submit all the assignments and final report by the end of the term may result in failing the course.
Use the provided LaTex template or Word template to write your assignments and the final report.
Late penalties for deliverables: -1% for each additional day (6:00 pm to 6:00 pm).
If assignment was not submitted before the next assignment due date, you will get 0% for this assignment,
however next assignment will not be considered submitted until you submit all the previous assignments.
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 www.uwaterloo.ca/academicintegrity/ for more information.]
Grievance:
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, www.adm.uwaterloo.ca/infosec/Policies/policy70.htm.
When in doubt please be certain to contact the department's administrative assistant who will provide further assistance.
Discipline:
A student is expected to know what constitutes academic integrity [check www.uwaterloo.ca/academicintegrity/] 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, TA, or the undergraduate Associate Dean.
For information on categories of offences and types of penalties, students should refer to Policy 71,
Student Discipline, www.adm.uwaterloo.ca/infosec/Policies/policy71.htm.
For typical penalties check Guidelines for the Assessment of Penalties, www.adm.uwaterloo.ca/infosec/guidelines/penaltyguidelines.htm.
Appeals:
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) www.adm.uwaterloo.ca/infosec/Policies/policy72.htm.
Note for Students with Disabilities:
The Office for persons with Disabilities (OPD), located in Needles Hall, Room 1132, collaborates with all academic departments
to arrange appropriate accommodations for students with disabilities without compromising the academic integrity of the curriculum.
If you require academic accommodations to lessen the impact of your disability, please register with the OPD at the beginning of each academic term.
Group Work:
Students are to work on the course project in groups of 3-4 people.
Project groups need to be formed at the beginning of the term (by Wednesday, May 10)
and are expected to stay the same throughout the term. Assignments, presentations and final
reports are submitted per group and marked accordingly.
Project Description:
Choosing your project topic:
Each project group is required to choose a unique project topic from the list of suggested projects.
Topics are assigned to project groups on first come, first served basis, thus it is recommended to
choose several topics of interest at the beginning. If your group wants to work on a different project,
not listed among the suggested projects, it necessarily requires an instructor’s approval.
Project topics must be finalized by Wednesday, May 10.
Project details and expectations:
Throughout the course each project group is working on the project chosen at the beginning of the term.
At the end of the course each project is expected to result in a high fidelity interactive prototype of
a phone application. Original project topics are outlining the general area and goal of the application.
During the term students are required to identify specific functionalities required for the successful
adoption of a specific application (based on exploratory user studies), create and prototype an initial
design of the application (low fidelity prototyping), further iterate on the design based on the results
of the user studies (high fidelity prototyping) and asses the final design through the user studies.
Project deliverables:
Students are expected to submit 3 assignments throughout the course.
These assignments help the instructor to monitor the intermediate progress of the projects and to provide
forehanded feedback on the next steps to ensure correct and effective work flow. Assignments all
together are building up to a final report. There are also two group presentations during the term: to present
an intermidiate progress and to present final design. In addition to the final presentation and
final report each project group is required to submit a 3 minute video to demonstrate the final high
fidelity interactive prototype of their application. Please note that all videos will be available for
viewing to all students taking the class.
In-class Quizzes:
To monitor class attendance and familiarization with class materials and additionally assigned materials, there are short quizzes occasionally (read “randomly”) given in some classes. Each quiz will have 3 questions and there will be 5 minutes in class to answer them individually, on paper. There are 12 quizzes in total during the course. Quizzes weight 5% of the final mark and are marked as following: 2% for writing 10 out of 12 (0.2% for each). If you have less than 10 quizzes written by the end of the course, you will have a chance to write one of the missed quizzes at the last class. 3% for quality of answers (0.1 for each correct answer).
Presentation:
There are 2 poster sessions happening during the course (June 14 and July 19, class time).
Main goals of the presentations are to practice verbal presentations
of the product design, obtain feedback from HCI specialists, classmates and additional feedback from the
course staff, explore other projects presented by classmates.
Students are required to prepare a 4 min talk to describe their project, pitch and justify their design idea and
describe the design process. The talk should be supported by visual materials presented on a poster format.
CS 649 Additional Requirements:
Graduate students are expected to perform an academic literature review related to each assignment topic and to
the final report content.
For more details see the assignments description.
Note that CS 649 has a separate marking scheme with weights distribution that differs from CS 449.
Team 23: Project DateNight
Team Biscuits: Project CookieJar
Team Critically Acclaimed: Project CineMe
Team Hercules: Project Fitify
Team Omnilingual: Project Omnilingual
Team SE: Project Rumie
Team TovrShare: Project TovrShare
Team UIIBSME: Project Schdulr
Team Xiphias: Project Budg.it
Team Awesome: Project Code.ly
Team BridgeBrigade: Project OSIMple
Team Glasses: Project Chopify
Team JJJ: Project Simpill
Team Piece of Cake: Project Piece of Cake
Team SportyBunch: Project Quick Sports
Team Travellers: Project PacMate
Team WeatherReady: Project WeatherReady
 |
Anastasia Kuzminykh (akuzminy@) | Instructor | DC 3540 |
|---|---|---|---|
 |
Lisa Elkin (laelkin@) | TA | DC 3540 |
 |
Blaine Lewis (b2lewis@) | TA | DC 3540 |
May Office Hours (Week 1-5)
| Week 1 | May 2 | Tuesday | Lisa | 10:00 - 11:00 | DC 3540 |
|---|---|---|---|---|---|
| Anastasia | 02:00 - 03:00 | DC 3540 | |||
| May 4 | Thursday | Anastasia | 12:30 - 01:30 | DC 3540 | |
| Week 2 | May 8 | Monday | Anastasia | 11:00 - 12:00 | DC 3540 |
| May 9 | Tuesday | Anastasia | 02:00 - 03:00 | DC 3540 | |
| May 11 | Thursday | Anastasia | 12:30 - 01:30 | DC 3540 | |
| Week 3 | May 15 | Monday | Blaine | 11:00 - 12:00 | DC 3540 |
| May 16 | Tuesday | Anastasia | 02:00 - 03:00 | DC 3540 | |
| May 18 | Thursday | Anastasia | 12:30 - 01:30 | DC 3540 | |
| Week 4 | May 23 | Tuesday | Lisa | ? | DC 3540 |
| Anastasia | 10:00 - 11:00 | DC 3540 | |||
| May 4 | Thursday | Anastasia | 12:30 - 01:30 | DC 3540 | |
| Week 5 | May 29 | Monday | Blaine | 11:00 - 12:00 | DC 3540 |
| May 30 | Tuesday | Anastasia | 02:00 - 03:00 | DC 3540 | |
| June 1 | Thursday | Anastasia | 12:30 - 01:30 | DC 3540 |
June Office Hours (Week 6-9)
| Week 6 | June 6 | Tuesday | Lisa | 10:00 - 11:00 | DC 3540 |
|---|---|---|---|---|---|
| Anastasia | 02:00 - 03:00 | DC 3540 | |||
| June 8 | Thursday | Anastasia | 12:30 - 01:30 | DC 3540 | |
| Week 7 | June 12 | Monday | Blaine | 11:00 - 12:00 | DC 3540 |
| June 13 | Tuesday | Anastasia | 02:00 - 03:00 | DC 3540 | |
| June 15 | Thursday | Anastasia | 12:30 - 01:30 | DC 3540 | |
| Week 8 | June 20 | Tuesday | Lisa | 10:00 - 11:00 | DC 3540 |
| Anastasia | 02:00 - 03:00 | DC 3540 | |||
| June 22 | Thursday | Anastasia | 12:30 - 01:30 | DC 3540 | |
| Week 9 | June 26 | Monday | Blaine | 11:00 - 12:00 | DC 3540 |
| June 27 | Tuesday | Anastasia | 02:00 - 03:00 | DC 3540 | |
| June 29 | Thursday | Anastasia | 12:30 - 01:30 | DC 3540 |
July Office Hours (Week 10-13)
| Week 10 | July 4 | Tuesday | Lisa | 10:00 - 11:00 | DC 3540 |
|---|---|---|---|---|---|
| Anastasia | 02:00 - 03:00 | DC 3540 | |||
| July 6 | Thursday | Anastasia | 12:30 - 01:30 | DC 3540 | |
| Week 11 | July 10 | Monday | Blaine | 11:00 - 12:00 | DC 3540 |
| July 11 | Tuesday | Anastasia | 02:00 - 03:00 | DC 3540 | |
| July 14 | Friday | Anastasia | 01:00 - 02:00 | DC 3540 | |
| Week 12 | July 18 | Tuesday | Lisa | 10:00 - 11:00 | DC 3540 |
| Anastasia | 01:30 - 02:30 | DC 3540 | |||
| July 20 | Thursday | Anastasia | 12:30 - 01:30 | DC 3540 | |
| Week 13 | July 24 | Monday | Blaine | 11:00 - 12:00 | DC 3540 |
| July 25 | Tuesday | Anastasia | 01:00 - 02:00 | DC 3540 | |
| Exam Week | August 3 | Thursday | Anastasia | 1:00 - 2:00 | DC 3540 |
LaTex Template and Word template to write assignments and the final report
Overleaf - an online LaTeX collaborative writing tool. Check it out
Research with human participants at University of Waterloo
Forms:
User Study Consent Form (Do not change!)
User Study Manager Permission Form (Do not change!)
-
User Study Thank You Letter (Do not change!)