Project Survey
Due at 11:30 PM, Monday, December 7, 2026.
Acknowledgment
The development of the project was supported by a Mozilla Responsible Computer Science award . The support is gratefully acknowledged.
Some Suggestions and Warnings
While the coding portion of the project is somewhat similar to Question 3 on the homework, there are several important differences. We want to highlight a few of them up front:
Form Groups of Size Exactly $3$
This is a group project (unlike Question 3 on the homework that had to be done individually) and you can work in groups of size exactly 3. The coding submissions will be on Autolab, and everyone in the group will receive the same group score for the coding component, subject to the individual-component policy described in the syllabus.
The same group for ALL problems
You are expected to work in the same group for ALL problems in the coding project. Not doing so will be considered to be an academic integrity violation. We will use the groups you register on Autolab as part of your Autolab Project Group Registration submission for your project submissions.
There is ONE exception to the above rule: It is OK if the group becomes smaller (e.g. if a group member resigns) but in that case another student cannot be added to the group. If you need clarification on this, please get in touch with Prof. Carlson or Prof. Luo.
Start early!
There is a reason we are giving you substantial time to complete this project. If your group starts even the week before the project is due, your group will be in trouble especially beyond the first problem. Also for most problems you will have to think of algorithms beyond what we cover in class, so the more time you spend on this, the better.
Use the Notation Table
The project description is a bit notation-heavy. If you start losing track, here is the notation page (opens in a new window) that might be useful.
Background and Problem Statements
See the main project page for details on problem statements.
Survey Details
Each group member will fill in a survey rating their own and the contributions of the other group members to the project under the categories of team role, leadership, participation, professionalism, and quality of work (on a scale from $0$ to $3$ for each category). These scores will then be used to divide the team’s points so that individual students’ survey grades reflect how well they contributed to the overall result. The table below explains what the different numerical values for various categories mean.
| Category | 0 points (Unsatisfactory) | 1 point (Developing) | 2 points (Satisfactory) | 3 points (Exemplary) |
| Teamwork | Does not willingly assume team roles; Rarely completes assigned work |
Usually accepts assigned team roles; Occasionally completes assigned work |
Accepts assigned team roles; Mostly completes assigned work |
Accepts all assigned team roles; Always completes assigned work |
| Leadership | Rarely takes leadership role; Does not collaborate; Sometimes willing to assist teammates |
Occasionally shows leadership; Mostly collaborates; Generally willing to assist teammates |
Shows an ability to lead when necessary; Willing to collaborate; Willing to assist teammates |
Takes leadership role; Is a good collaborator; Always willing to assist teammates |
| Participation | Often misses meetings; Routinely unprepared for meetings; Rarely participates in meetings and does not share ideas |
Occasionally misses or does not participate in meetings; Somewhat prepared for meetings; Offers unclear or unhelpful ideas in meetings |
Attends and participates in most meetings; Comes prepared to meetings; Offers useful ideas in meetings |
Attends and participates in all meetings; Comes prepared to meetings; Clearly expresses well-developed ideas in meetings |
| Professionalism | Often discourteous and/or openly critical of teammates; Does not want to listen to any alternative perspectives |
Not always considerate or courteous towards teammates; Usually appreciates teammates' perspectives, but often unwilling to consider them |
Mostly courteous to teammates; Values teammates' perspectives and often willing to consider them |
Always courteous to teammates; Values teammates' perspectives, knowledge, and experiences, and always willing to consider them |
| Quality | Rarely contributes to the coding and reflection components of the project; Others often required to revise, debug, or fix their work |
Occasionally contributes to the coding and reflection components of the project; Others sometimes needed to revise, debug, or fix their work |
Often contributes to the coding and reflection components of the project; Others occasionally needed to revise, debug, or fix their work |
Frequently contributes to the coding and reflection components of the project; Others rarely needed to revise, debug, or fix their work |
Submitting the Survey
The peer-evaluation survey will be completed on a separate website. The website and access instructions will be posted and announced in class at a later time. You will evaluate yourself and your groupmates in all five categories listed above.
The Workflow
- The survey website and access instructions will be posted and announced in class at a later time.
- Complete the survey by 11:30 PM on Monday, December 7, 2026.
- Evaluate yourself and each of your groupmates in all five categories above.
- Submit the survey through the survey website. Survey responses will be used as part of the individual component of the project grade.