Problem set assessment: Difference between revisions

Latest revision as of 13: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?

References[edit]

@@ Line 1: / Line 1: @@
-[[file:square.png|right|frame|Problem sets are designed to really get you thinking!!]]
+[[file:square.png|right|frame|Problem sets are designed to get you really 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 "count" as summative grades.    [[Media:Problem-setrubric.pdf|Please click here to see how you will be graded]]
+== 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.
+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.
+'''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]]?
+== References ==
+<references />
-{| style="width: 95%;" class="wikitable sortable"
-|-
-! Problem Set !! Difficulty Level !! Notes
-|-
-| [[my priorities, my time]] || Average || None
-|-
-| [[chess]] || Expert || None
-|-
-| [[Strings: making HTML tags]] || Average || None
-|-
-| [[simple password rules]] || Average || None
-|-
-| [[date fashion]]  || Average || None
-|-
-| [[mean, median, mode and other statistical functions]]  || Expert || There are three parts to this problem set. 2 are beginner, but 1 is very challenging :-)
-|-
-| [[Email validator]]  || Beginner || None
-|-
-| [[making a small grid]] || Average || None
-|-
-| [[moving around a small grid]] || Average || This is the foundation for many possible games you can make in Python!!
-|-
-| [[Guess a number ]] || Average || There are easy ways to extend this fun little guessing game
-|}
- '''Difficulty Level Key:'''
- * '''Beginner:''' this problem set is good for beginners
- * '''Advanced:''' this problem set should be challenging
- * '''Expert:''' This problem set is very challenging for most students (but it can be solved).
- All problem sets have opportunity to exceed standards.
 [[Category:Problem set]]
+[[Category:Grading]]