Rubric
Keep in mind that 541 students have already been assessed using this rubric. Changing it will affect their evaluations.
Criteria | Ratings | Pts | ||
---|---|---|---|---|
Uses a Map<String, Drawable> to track scenes
threshold:
pts
|
|
pts
--
|
||
Student can explain what their map is used for within the program
When are entries added to the map? When are entries retrieved from the map?
threshold:
pts
|
|
pts
--
|
||
Uses a List<Drawable> to keep track of Drawables for a given scene
threshold:
pts
|
|
pts
--
|
||
Student can explain the usage of their List<Drawable>
When are items added to this list? How does it interact with the map?
threshold:
pts
|
|
pts
--
|
||
Program starts with an initial scene called "init"
Init should not be blank, it should contain some drawables
threshold:
pts
|
|
pts
--
|
||
Program clears the screen when "clear" is entered
threshold:
pts
|
|
pts
--
|
||
Program ends when "end" is typed in
threshold:
pts
|
|
pts
--
|
||
Program can record new scenes
Must have a way to begin and end recording
threshold:
pts
|
|
pts
--
|
||
Recorded scenes are saved and displayed to the user
threshold:
pts
|
|
pts
--
|
||
Recorded scenes can be recalled and displayed when selected by the user
threshold:
pts
|
|
pts
--
|
||
Recorded scenes properly track the Drawables input by the user
For example, if the same drawable is added multiple times, it should show up darker as shown in the video
threshold:
pts
|
|
pts
--
|
||
Code is clean
threshold:
pts
|
|
pts
--
|
||
Code is committed and pushed
threshold:
pts
|
|
pts
--
|
||
Total Points:
100
out of 100
|