Motivation

CSE 331 is primarily concerned with the technical aspects of algorithms: how to design them and then how to analyze their correctness and runtime. However, algorithms are pervasive in our world and are commonplace in many aspects of society. The main aim of the project is to have you explore some of the social implications of algorithms.

Just to give some examples for such implications:

• Big data is hot these days and there is a (not-uncommon) belief that by running (mainly machine learning) algorithms on big data, we can detect patterns and use those to potentially make policy decisions. Here is a cautionary talk:
• For a longer documentary on the societal impacts of algorithms in general (and specifically machine learning), see Coded Bias :

  You can watch the movie on Netflix .

• Another aspect of the effect on technology in society stems from unequal access to technology. In CSE 331 this fall, we will touch upon the issue of access to high-speed Internet a few times, and the project will be motivated by the topic of high-speed Internet. For a primer on the issues regarding unequal access to high-speed Internet, see the following webinar:
  

  (Click on the image above and then check out the recording (the access code is in the linked webpage). I attended the webinar and found it to be very eye-opening.)

The project has three parts

Your project will have three parts:

1. Do five programming problems that involve making tradeoffs between various choices, some of which have ethical dimensions. This will be a group assignment.
2. Each programming question will be paired with (a series of) reflection questions that involve you writing down and reflecting on some of the design decisions you made in the corresponding programming problem. In particular, these questions will ask you to reflect on the societal and ethical implications of your decisions. This will also be a group assignment.
3. At the end of the project, each group member will fill in a survey rating their own and the other group members' contribution to the project.

Before we give more details on the programming problems, reflection questions and survey aspects of the project, we present details on some logistics: in particular, the deadlines and details on forming a group.

Logistics

We begin by collecting all the relevant deadlines and then giving details on forming groups.

Deadlines

For your convenience, below are all the relevant deadlines (please plan accordingly). The deliverables are due by 11:59pm of the due date.

Deliverable	Due Date
Team Composition	September 20
Team Registration (on Autolab)	September 30
Problem 1 Coding	November 1
Problem 1 Reflection	November 4
Problem 2 Coding	November 1
Problem 2 Reflection	November 4
Problem 3 Coding	November 25
Problem 3 Reflection	December 2
Problem 4 Coding	December 6
Problem 4 Reflection	December 10
Problem 5 Coding	December 6
Problem 5 Reflection	December 10
Survey	December 10

Forming groups

You form groups of size exactly three (3) for the project. Below are the various logistics:

• You have two choices in forming your group:
  1. You can form your group on your own: i.e. you can submit the list of EXACTLY three (3) group members in your group.

     Note

     Note that if you pick this option, your group needs to have exactly THREE (3) members. In particular, if your group has only two members, you cannot submit as a group of size two. If you do not know many people in class, feel free to use Piazza to look for the third group member.

     Also, if you form a group of size three, please make only one submission per group.

  2. You can submit just your name, and you will be assigned a random group among all students who take this second option. However, note that if you pick this option, you could end up in a group of size $2$. There will be at most two groups of size $2$.

     Potential risk

     Note that if you pick the option of being assigned a random group, you take on the risk that a assigned group might not "pull their weight." We unfortunately cannot help with such aspects of group dynamics. (Of course if a group member is being abusive, please do let Atri know.) Please note that a group member who does not do much work will get penalized on the individual component of the project grade.

• Submitting your group composition

  Use this Google form to submit your group composition (the form will allow you to pick one of the two options above).

• You need to fill in the form for group composition by 11:59pm on Friday, September 20.

• Deadline is strict!

  If you do not submit the form for group composition by the deadline, then you get a zero for the entire project.

Registering your group on Autolab

Coding Component

In the coding component of the project, you will be developing and implementing algorithms in a scenario that is heavily influenced by a real-life case study.

Reflection Component

In the reflection component of the project, you will be reflecting on the choices you made in the coding component as well as the implications of your choices.

Survey

Each group member will fill in a survey rating their own and their other group members' 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; 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 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