Project Details
This page contains all the details related to the CSE 410 project.
A Request
I know I am biased in favor of references that appear in the computer science literature. If you think I am missing a relevant reference (outside or even within CS), please email it to me.
Background and Motivation
In this course we will cover various aspects of how algorithms and society interact. In class, we will do this via lectures, activities and discussion. However, you do not really get the material unless you get "your hands dirty." The project in this course is meant as an opportunity for you to make to a deep-dive into a specific (somewhat narrow) topic related to the broad topic of the course. The hope if that y'all will be able to connected your chosen project to the material we cover in class and indeed, take advantage of the latter to improve your project!
Details galore!
There are quite a few details on the project. So please read the rest of the document very carefully. If you have any questions, please ask me!
Project Topics
Here are the four proposed projects (each link leads you to the page for the specific project, which has more details on what each project will entail):
- Human acceptance of algorithmically controlled systems
- Incorporating multiple notions of fairness
- Algorithmic Auditing
- Creating more teaching tools for CSE 410
Highly recommended
We very strongly encourage y'all to pick from the project topics listed above since we have put some thought into creating projects that are (1) fun! but (2) also feasible within the timeframe of a semester.
However, see the point below.
If you want to propose your own project
While we hope that y'all will pick from one of the topics listed above, we do want to give y'all a chance to propose your own project if you have a strong reason to do so (e.g. such a project will be very closely related to your major and/or you took this course because you had a specific project in mind.
If you go down this path, you need to let Atri know by 5pm on THURSDAY January 30, 2020. If you miss this deadline, then you will have to choose from one of the above topics.
Choosing your project topic
To choose your project topic please fill in this Google form .
Group Formation
The groups will be formed by me. Unless there is a strong reason (e.g. there being a mathematical impossibility), all groups will be of size three (3). However, you will be able to have some say in the process. In particular,
Submitting your group formation preferences
To add in your group preferences, please fill in the Google form that you use to input project preferences .
I will honor requests for not having specific student(s) in your group. I will not ask for any explanation for any such choice (unless you would like to tell me) but I do ask that you use your best judgment for this part.
For the rest of your choices (project preferences or preferred groupmates), I will try and honor them as much as possible. My goal is to form diverse groups that are well suited for specific projects (and I will use your form responses in this regard, so please do answer as many questions as you can!.
Section A1 vs. A2
The expectation are slightly different for students in Section A1 vs those in Section A2.
Expectations from Section A1 and A2
While everyone in the group should try and contribute to all aspects of the group project, we have slightly different expectations from students in different sections.
In particular, students in Section A2 (non-CSE majors)) are not expected to contribute to the programming or proving theorems (based on what the project entails). The CSE majors (i.e. those in Section A1) are the ones who are supposed to do the programming or theorem proving tasks. All group members are expected to contribute equally for the rest of the tasks in the project. However, if the entire group agrees, then the students in Section A2 can take a (somewhat) larger role for the non-programming and non theorem-proving aspects of the project.
Translating the above guidelines to your actual project tasks might not be as obvious-- in such a case, please do come talk to me and I'll be happy to help!
Logistics
Contribution of your project score to final grade
The project in total is worth $60\%$ of your final grade.
Here is how the $60\%$ weightage for the project will be further divided down:
Here is the split of grades:
Project Component | $\%$ of FINAL course grade |
Presentations | $30\%$ |
In-class meetings | $15\%$ |
Written report | $10\%$ |
Survey | $5\%$ |
Deadlines
For your convenience, below are all the relevant deadlines. The relevant documents are due by 5pm of the writeup due date. The in-class parts will be held during normal class hours.
Deliverable | Documents Due Date | In-class activity |
Project choice | Google form by February 6 | -- |
First in-class meeting | Progress summary by February 12 | February 13 |
Initial project presentation | Slides by February 26 | February 27 |
Second in-class meeting | Progress summary by March 23 | March 24 |
Mid project presentation | Slides by April 1 | April 2 |
Third in-class meeting | Progress summary by April 22 | April 23 |
Written project report | Report by May 7 | -- |
Final project presentation | Slides by May 13 | May 14 |
Survey | Fill in form by May 13 | -- |
The above deadlines are also on the schedule page.
Presentations
There will be three presentations
There will be three presentations (for the dates see above). All of these will be in the usual classroom (Talbert 112). The first two are during normal class dates while the final presentation is at the same time as the scheduled "final exam" for this course.
Each group will present for 30 minutes.
Each group member will present once
Each of the three presentations will made by different group members. (This is assuming all groups end up being of size $3$-- if not, I'll revisit this.)
Slides are due by 5pm the day BEFORE the presentation
Please upload a PDF of your slides on Autolab. (Yes, this means y'all need to prepare slides for your presentations!) Only one person per group need to upload the file.
You can modify the slides a bit (e.g. fixing typos etc.) but the slides used in your actual presentation should basically be the same as the one uploaded on Autolab.
Presentation components
Each of your presentations should address all the following:
- Motivate your project: why is the project interesting to your group? Why should someone else care?
- State the problem you are trying to solve. If appropriate you can state a mathematical description of the problem if it is absolutely necessary (but make sure you have a high level description of the problem itself).
- What is your proposed solution? This could be different based on your project (e.g. it could be a mathematical model, or an experiment, or a theorem you would like to prove).
- How are you planning to manage your project? This should at least have the following three sub-components:
- Breakup for various tasks for the rest of semester.
- Which group member is responsible for which task?
- What if your deadline for various tasks? For simplicity, just use the in-class meetings and presentation dates as potential deadline dates.
- Give a quick recap of what results you had at the last presentation.
- What new results have y'all obtained since your last presentation. If there is no (or very little) progress, what were the roadblocks that prevented progress?
- What results do you hope you obtain by the next presentation?
Presentation rubric
Here is the split of grades for the various parts of the presentation based on which presentation it is (for a total of 100 points
for each presentation):
Component | Initial presentation | Mid presentation | Final presentation |
Motivation | 10 points | 10 points | 5 points |
Problem | 30 points | 10 points | 5 points |
Solution | 10 points | 40 points | 30 points |
Project management | 40 points | 10 points | 0 points |
Previous results | 0 points | 5 points | 5 points |
Current results | 5 points | 15 points | 55 points |
Future results | 5 points | 10 points | 0 points |
Feel free to use the point distribution to decide on how much time you should spend on each component in your presentation.
Everyone in the group will get the same grade.
Proper citation is a must!
You should properly cite any source you use in your presentation. This should include both the reference material that you use to create the main content of the presentation as well as any use of figures/videos from another source. Not giving proper credit for someone else's material is considered cheating and WILL LEAD TO ACADEMIC INTEGRITY VIOLATION PROCEDURE AGAINST YOUR GROUP.
Coronavirus Change
Starting March 24, 2020 all group presentations will be done during the online class meeting on Zoom (with WebEx as backup). Each group will pick one presenter who will do the presentation and screen-share the slides so that everyone can follow along. Of course other group members can chime in when needed.
Zoom backup
While the hope is that the move to Zoom will work smoothly, in case that the meeting on Zoom does not work smoothly (e.g. if the Zoom servers are overloaded or if you have any technical issues at your end), we will try WebEx next. In case neither works, your group will have 2 days (48 hours) after the end of the lecture to email me a link to a video recording of the group's presentation. A Youtube link (unlisted video is fine) is preferred but uploading the video to UB Box and sending me a link will also work.
In-class group meetings
There will be three meetings
Your group will meet with Atri three times during the semester (for the dates see above). All of these will be in the usual classroom (Talbert 112).
The main idea behind these meetings is that I can keep track of progress that each group is making.
All group members should be present
All group members are expected to stay for the entire 20 minute meeting. If for some reason you cannot make a specific meeting, please let Atri know in advance (but no later than a week before the meeting).
Progress summaries are due by 5pm the day BEFORE the meeting
Please upload PDF (at most two pages (excluding references)) of your Progress summary on Autolab. (The details on the contents is given below but this is so that I can prepare for the meeting) Only one person per group need to upload the file.
We can of course discuss more material over what you mention in your progress summary.
Meeting components
Each of your project summaries (as well as our discussions during the meeting) should address all the following:
- What is your proposed solution? This could be different based on your project (e.g. it could be a mathematical model, or an experiment, or a theorem you would like to prove).
- How are you planning to manage your project? This should at least have the following three sub-components:
- Breakup for various tasks for the rest of semester.
- Which group member is responsible for which task?
- What if your deadline for various tasks? For simplicity, just use the in-class meetings and presentation dates as potential deadline dates.
- Give a quick recap of what results you had at the last meeting.
- What new results have y'all obtained since your last meeting. If there is no (or very little) progress, what were the roadblocks that prevented progress?
- What results do you hope you obtain by the next meeting?
- Do you have any questions for me?
Couple of sentences per each item is enough (except perhaps the project management part)! You can expand on the summary during the actual meeting. You can use whatever medium you want during the meeting-- you can use slides if you wish, or you can give a "demo" on a laptop etc. Basically no restriction on the medium of delivery as long as I can understand what y'all are doing for each component.
Meeting rubric
Here is the split of grades for the various parts of the meetings based on which meeting it is (for a total of 100 points
for each progress summary AND the meeting itself):
Component | First meeting | Second meeting | Third meeting |
Solution | 35 points | 35 points | 30 points |
Project management | 40 points | 20 points | 0 points |
Previous results | 0 points | 10 points | 10 points |
Current results | 10 points | 20 points | 55 points |
Future results | 10 points | 10 points | 0 points |
Questions for Atri | 5 points | 5 points | 5 points |
Feel free to use the point distribution to decide on how much time you should spend on each component in your preparation for the meeting.
Everyone in the group will get the same grade.
Coronavirus Change
Starting March 24, 2020 all group meetings will be done (and graded-- I will be able to keep track of participation online) via the online class meeting on Zoom (with WebEx as backup).
Zoom has the capability to create breakout rooms, which is what we plan to use for the group meetings. If we need to use WebEx instead, we will use specially created "WebEx training" meetings to create breakout rooms and use those instead.
Zoom backup
While the hope is that the move to Zoom will work smoothly, in case that the meeting on Zoom does not work smoothly (e.g. if the Zoom servers are overloaded or if you have any technical issues at your end), we will try WebEx next. In case neither works, then the score for your progress summary will carry over to the meeting itself.
Written report
There is only one report
Each group will submit a written report summarizing their work over the semester (see the deadline above). Your group can include more stuff in its final presentation if y'all want to do so.
The report should be at most ten (10) pages (without references).
Report is due by 5pm Thursday, May 7
Please upload a PDF of your slides on Autolab. Only one person per group need to upload the file.
Report components
Your report should address all the following:
- Motivate your project: why is the project interesting to your group? Why should someone else care?
- State the problem you are trying to solve. If appropriate you can state a mathematical description of the problem if it is absolutely necessary (but make sure you have a high level description of the problem itself).
- What is your proposed solution? This could be different based on your project (e.g. it could be a mathematical model, or an experiment, or a theorem you would like to prove).
- What results did you obtain? If there is no (or very little) progress, what were the roadblocks that prevented progress?
- Future work. What followup work can be done now that your project done?
Presentation rubric
Here is the split of grades for the various parts of the report (for a total of 100 points
):
- Motivation:
10 points
- Problem:
10 points
- Solution:
40 points
Results: 35 points
- Future work:
5 points
Feel free to use the point distribution to decide on how much time you should spend on each component in your report.
Everyone in the group will get the same grade.
Proper citation is a must!
You should properly cite any source you use in your report. This should include both the reference material that you use to create the main content of the report as well as any use of figures from another source. Not giving proper credit for someone else's material is considered cheating and WILL LEAD TO ACADEMIC INTEGRITY VIOLATION PROCEDURE AGAINST YOUR GROUP.
NO Coronavirus Change
Since the report writing and submission is done outside of class, this part of the course will not change.
Survey
Each group member will fill in a survey rating their own and their other group member's contribution to the mini 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)Role Does not willingly assume team roles;
Rarely completes assigned workUsually accepts assigned team roles;
Occasionally completes assigned workAccepts assigned team roles;
Mostly completes assigned workAccepts all assigned team roles;
Always completes assigned workLeadership Rarely takes leadership role;
Does not collaborate;
Sometime willing to assist teammatesOccasionally shows leadership;
Mostly collaborates;
Generally willing to assist teammatesShows an ability to lead when necessary;
Willing to collaborate;
Willing to assist teammatesTakes leadership role;
Is a good collaborator;
Always willing to assist teammatesParticipation Often misses meetings;
Routinely unprepared for meetings;
Rarely participates in meetings and does not share ideasOccasionally misses or does not participate in meetings;
Somewhat prepared for meetings;
Offers unclear or unhelpful ideas in meetingsAttends and participates in most meetings;
Comes prepared to meetings;
Offers useful ideas in meetingsAttends and participates in all meetings;
Comes prepared to meetings;
Clearly expresses well-developed ideas in meetingsProfessionalism Often discourteous and/or openly critical of teammates;
Does not want to listen to any alternate perspectivesNot always considerate or courteous towards teammates;
Usually appreciates teammates' perspectives, but often unwilling to consider themMostly courteous to teammates;
Values teammates' perspectives and often willing to consider themAlways courteous to teammates;
Values teammates' perspectives, knowledge, and experiences, and always willing to consider themQuality Rarely contributes to the project;
Others often required to revise, debug, or fix their workOccasionally contributes to the project;
Others sometimes needed to revise, debug, or fix their workOften contributes to the project;
Others occasionally needed to revise, debug, or fix their workFrequently contributes to the project;
Others rarely needed to revise, debug, or fix their workSubmitting 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
- At 5:01pm on Thursday, May 7 the website above will be ready for you. You will need to complete the survey by 5pm on Wednesday, May 13.
- You will need to enter your UB email and click on a button to generate a verification code.
- You will have limited time (~10 mins) to enter the verification code into the webpage.
- 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 project score to post your survey scores on Autolab (the scores will be posted on your final presentation submission).
- If you have not used this system before, please do a dry run of the system WELL before the final deadline. Your can re-submit and only your final submission will count (so you can iron out any issues in your trial submissions).
NO Coronavirus Change
Since the survey will be filled and submitted outside of class, this part of the course will not change.
- Future work: