Problem set assessment: Difference between revisions
Mr. MacKenty (talk | contribs) No edit summary |
Mr. MacKenty (talk | contribs) |
||
| (7 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
[[file:square.png|right|frame|Problem sets are designed to | [[file:square.png|right|frame|Problem sets are designed to get you really thinking!!]] | ||
== Introduction == | == Introduction == | ||
Problem sets are designed to challenge you to '''apply''' your knowledge of computer science. Problem sets can be completed in many different programming languages. All problem sets are counted as summative grades. This page describes how problem sets are graded. | |||
== 4 | I took this, 100% from CS50. I'm pretty sure I have their implicit permission for this stuff. | ||
== 4 axis in good code == | |||
Each axis is graded independently. | Each axis is graded independently. | ||
| Line 11: | Line 13: | ||
* To what extent does your code implement the features required by our specification? | * To what extent does your code implement the features required by our specification? | ||
* To what extent is there evidence of effort? | * To what extent is there evidence of effort? | ||
'''Correctness''' | '''Correctness''' | ||
* To what extent did your code meet specifications? | * To what extent did your code meet specifications? | ||
* To what extent did your code meet unit tests? | * To what extent did your code meet unit tests? | ||
'''Design''' | '''Design''' | ||
| Line 25: | Line 25: | ||
* To what extent is your code using functions appropriately? | * To what extent is your code using functions appropriately? | ||
* Hint: code that is short is often a proxy for good design (but not always) | * Hint: code that is short is often a proxy for good design (but not always) | ||
'''Style''' | '''Style''' | ||
| Line 32: | Line 31: | ||
* To what extent are your variables well named? | * To what extent are your variables well named? | ||
* To what extent do you adhere to [[style guide]]? | * To what extent do you adhere to [[style guide]]? | ||
== References == | == References == | ||
Latest revision as of 12:43, 30 March 2023
Problem sets are designed to get you really thinking!!
Introduction[edit]
Problem sets are designed to challenge you to apply your knowledge of computer science. Problem sets can be completed in many different programming languages. All problem sets are counted as summative grades. This page describes how problem sets are graded.
I took this, 100% from CS50. I'm pretty sure I have their implicit permission for this stuff.
4 axis in good code[edit]
Each axis is graded independently.
Scope
- To what extent does your code implement the features required by our specification?
- To what extent is there evidence of effort?
Correctness
- To what extent did your code meet specifications?
- To what extent did your code meet unit tests?
Design
- To what extent is this code efficient?
- To what extent is your code eliminating repetition?
- To what extent is your code using functions appropriately?
- Hint: code that is short is often a proxy for good design (but not always)
Style
- To what extent is your code formatted?
- To what extent are your variables well named?
- To what extent do you adhere to style guide?