Project report
- Due Dec 5, 2024 by 9:30am
- Points 2
- Submitting a file upload
- File Types pdf
See the Semester Project page for details on what to submit.
Grading
2 = Pass—you satisfy all of the specifications to a sufficient degree—it's perfectly met or very nearly met (e.g., if a specification says your code must include a comment above every function, but your code includes comments above only about 80% of functions, then that is deemed "sufficient")
1 = Reasonable attempt—it is clear that you made a good faith effort to meet the majority of the specifications even if they are not all met
0 = Unassessable—no or little attempt was made.
Rubric
Find RubricKeep in mind that 9 students have already been assessed using this rubric. Changing it will affect their evaluations.
| Criteria | Ratings | ||
|---|---|---|---|
|
Your report includes a header at the top with your name, date, and a title
|
|
||
|
Your report answers questions with a smooth flow and easy to read transitions, not in a Q&A format
|
|
||
|
Your report addresses: What is your application and how is it different from related applications? What is special or unique about your application?
|
|
||
|
Your report addresses: In choosing this application or specific features, what risks, if any, did you take? (Did you go beyond the assignment specs? Did you use a technology we hadn't covered in class? Something else risky?)
|
|
||
|
Your report addresses: In designing and implementing your application, what choices did you make? What were the alternatives and why did you settle on the one you did? Identify and discuss three such choices.
|
|
||
|
Your report addresses: What are the components that make up your application and its implementation? Reference your updated component diagram when answering this question.
|
|
||
|
Your report addresses: Thinking ahead, what things would you change about or add to your implementation to make it better?
|
|
||
|
Your report is written with your classmates as the audience
|
|
||
|
|
|||
