Grade breakdown
Grading will be based on 1,000,000 points. The breakdown is as follows.
Component | Description | Quantity | Points | Subtotal |
---|---|---|---|---|
Assignments | Individual programming assignments | 6 | 83,333* | 500,000 |
Extra credit assignment available | 2 | 25,000 | (25,000) | |
Final project | Team-based app development | 1 | 300,000 | 300,000 |
Assessments | Questionnaires | 3 | 50,000 | 150,000 |
Engagement | GitHub commits | 100 | 500 | 50,000 |
Total | 1,000,000 |
* Two assignments are worth 83,334 because of rounding.
Components
Assignments
Each of the individual programming assignments will be worth 71,428 points and will be automatically evaluated.
The autograders will give you feedback so that you can make adjustments to your code to debug it so that it passes the unit tests.
The grade is not the point of any of this. Writing working code is the point of this.
Assignment due dates
The assignment due dates are meant as guideposts, not deadlines.
You can always submit or resubmit the assignments (by pushing them to your GitHub repository) after the due date.
You will not lose points for push or updating your repos after the due date has passed, ever.
Final project points breakdown
Component | Description | Points |
---|---|---|
Group planning | Documentation of your planning process | 50,000 |
API | Back-end API has defined endpoints that you can make queries against. | 75,000 |
Interface | Front-end connects to and interacts with API endpoints and stores/retrieves user or other information. | 75,000 |
Documentation | There is documentation about what you did and how it works. | 50,000 |
Demo | Walkthrough/clickthrough screencap demo of your app and presentation to class. | 50,000 |
Total | 300,000 |
Every member of your team will receive the same number of points for the final project.
The grade breakdown will not be more granular than what is listed above. Your team’s project must have the five components above.
You will check in with a TA assigned to your team throughout the semester as you plan and build. We will give you qualitative feedback on your work throughout and as part of the final presentation.
Assessments
Questionnaires given at the beginning, middle, and end of the semester.
Engagement
Your engagement score is a count of your GitHub commits. I am gathering this directly from your GitHub repositories submitted for your assignments and your team’s final project repos.
I will gather these counts to encourage you to commit small changes meaning that there should be a lot of them.
The number that you are responsible for is actually relatively few. You should easily be able to record over 100 commits over the course of the semester across 10 assignments and the final project. In fact, you should have WAY more than that.