Problem set assessment: Difference between revisions
Mr. MacKenty (talk | contribs) |
Mr. MacKenty (talk | contribs) |
||
| Line 12: | Line 12: | ||
* To what extent is there evidence of effort? | * To what extent is there evidence of effort? | ||
''[[example of poor scope]]'' | ''[[example of poor scope]]'' | ||
''[[example of | ''[[example of better scope]]'' | ||
'''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? | ||
''[[example of poor correctness]]'' | |||
''[[example of better correctness]]'' | |||
'''Design''' | '''Design''' | ||
| Line 23: | 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) | ||
''[[example of poor design]]'' | |||
''[[example of better design]]'' | |||
'''Style''' | '''Style''' | ||
| Line 28: | Line 32: | ||
* 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]]? | ||
''[[example of poor style]]'' | |||
''[[example of better style]]'' | |||
== References == | == References == | ||
Revision as of 08:14, 31 May 2016
Problem sets are designed to really get you thinking!!
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.
Introduction[edit]
4 axes in a good answer[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?
example of poor scope example of better scope
Correctness
- To what extent did your code meet specifications?
- To what extent did your code meet unit tests?
example of poor correctness example of better correctness
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)
example of poor design example of better design
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?
example of poor style example of better style