EECS 498 APSD P1

Project 1 Rubrics

Here are the rubrics we’re using for the initial review on project 1. The same rubric items will be used for the final revisions grading as well.

• Minesweeper Rubric
• Spelling Bee Rubric
• Sudoku Rubric

Initial Feedback

You’ll receive feedback and scores for each rubric item via a GitHub issue posted on your original, individual project 1 repository.

Project Revisions

Based on your feedback, make revisions to the current codebase in your group repository. It’s fine if you’re still in the middle of implementing parts of future projects, and the code doesn’t need to be in a runnable state. We’ll reassess the same rubric items as they apply to the current project. Do not go back and update your original P1 repositories.

Your group should work together to address feedback from initial grading. For any rubric items where you didn’t get full points, address the underlying design issues in each rubric item in that context. Some may already have been resolved naturally with changes you’ve made for more recent projects and won’t require additional work. Others may require refactoring individual implementations or wider-ranging design choices. Of course, you’ll also want to double check even those items where you got full points originally to make sure your code still meets the criteria!

Your group will submit your revisions together via a GitHub release. This allows you to tag a specific commit as your final submission.

1. Ensure all your code is committed and pushed to your repository.
2. Go to your repository on GitHub.
3. Click on “Releases” in the right sidebar (or navigate to https://github.com/eecs498-software-design/<your-repo>/releases).
4. Click “Draft a new release”.
5. Create a new tag for the release named p1-final-revisions.
6. Set the release title to “Project 1: Final Revisions”.
7. You don’t need to put anything specific in the release description.
8. Click “Publish release”.

Make sure to create your release before 11:59pm on the deadline.

Grading Details

Copied below are the relevant project grading details from course syllabus.

Initial Review and Final Grading (3% + 3% course grade)

The course faculty and staff will review student codebases (i.e. the state of the codebase represented in your submission pull request) and grade them according to a rubric. The rubric is specific to each project and the relevant programming techniques and design principles covered in the course. Each rubric item is evaluated on a 3 point scale:

• 0 - Missing (Related portions are not complete enough to meaningfully evaluate this item.)
• 1 - Insufficient (Significant issues or shortcomings.)
• 2 - Growth Needed (Adequate, but clear areas for improvement.)
• 3 - Exemplary (Implements relevant techniques and principles with few or no issues.)

Our intent is that the initial review and final grading for each project will use the same rubric and each individual item is generally graded with the same rigor, but the points needed for full credit are different. For example, assume a rubric has 10 items for 30 points total. On the initial review, your score might be computed out of 24 points, whereas on the final grading your score might be computed out of 30 points. (Because this is the first offering of the course, we will need to calibrate the exact numbers as we go.)

Note that your score for a rubric item on the initial review indicates an evaluation at that point in time, but does not necessarily guarantee a commensurate evaluation on the final review - since your codebase is evolving, you might need to pay close attention to a particular area to maintain a high quality of design and implementation. We'll do our best to give helpful feedback on particular areas to watch for.