Survey for Project

Due at 11:59pm, April 30, 2025.

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 this coding part of the project is somewhat similar to Question 3s on the homework, there are some crucial differences and we wanted to highlight few things for y'all upfront:

Form groups of size EXACTLY $3$

This is a group project (unlike Q3s on the HWs that had to be done individually) and you can work in groups of size exactly 3. The submissions will be on Autolab and everyone in the group will get the same grade.

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 y'all 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 group. If you need clarification on this, please get in touch with Atri.

Start early!

There is a reason we are giving y'all about two months to do 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 your 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 their other group member's contribution to the project under the categories of team role, leadership, participation, professionalism and quality of work (on scale of $0-3$ on each). 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 points (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; Sometime 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 alternate 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 reflections components of the project; Others often required to revise, debug, or fix their work	Occasionally contributes to the coding and reflections components of the project; Others sometimes needed to revise, debug, or fix their work	Often contributes to the coding and reflections components of the project; Others occasionally needed to revise, debug, or fix their work	Frequently contributes to the coding and reflections components of the project; Others rarely needed to revise, debug, or fix their work

Submitting the survey

The peer evaluation survey will have to be filled on https://cse.buffalo.edu/teamwork . You will evaluate yourself and your groupmates in all the five categories.

The workflow

Between 12:00pm, April 18, 2025 and 11:59pm on April 30, 2025 the website above will be ready for you.
Log in with your UB login credentials.
You will then fill in the survey: the website will ask you to evaluate yourself and your groupmates in all the five categories above.
Your part is done. Atri will use your survey responses and your (coding and reflection) project submission to post your survey project scores on Autolab.