10 Prove : Assessment Guidelines
Overview
This document outlines the guidelines for instructors and teaching assistants to use as they assess the assignment. It is intended to give structure and guidance to the grading process to ensure that the most important components of the assignment are highlighted, and to promote consistency across sections.
In all cases, the instructor has the latitude to deviate from this rubric on a case-by-base basis to provide the holistic assessment that, in their judgment, best matches the assignment.
Goal of Milestone Assessments
The goal of this assignment is to help students stay on track toward their future deliverable, and also to give them feedback quickly if they are headed down a bad path. With that in mind, the focus of this assessment is not to account for a few points here or there, but rather to give feedback and guidance.
Fundamental Concepts
This assignment is designed to highlight the following fundamental concepts:
Good object-oriented design
Interaction of several classes (Game, Ship, Bullet)
Polymorphism
This milestone requires the students to get the collisions working. This means they will need to face polymorphism head on.
Major Things to Look For
The number one most important thing to look for is the logic of calling a "split" or "break apart" function. This should be in the game class and it should NOT have any logic in there that attempts to say "if it's a large one, do this, if it's a medium do that." Instead, the code should say "rock.split()" or something similar and let each type of asteroid specify what it does.
Also, please be on the lookout for how they attempt to get the newly created asteroids into the list held by the game. There are different ways to do this, but check to see that they are on track.
In addition, the following should be present for this milestone:
Large asteroids should break into 2 mediums and 1 small
Medium asteroids should break into 2 smalls
Small asteroids should disappear
Bullets should cause collisions
Ships should cause collisions
Medium and small asteroids should spin and move faster than large ones.
Scoring
Given the formative nature of this assessment, the scoring is done in broad strokes as follows:
100% - Functionality is there, class design/hierarchy looks correct
90% - Minor issue with functionality or inheritance
75% - Program compiles/runs, but missing major functionality or not using inheritance
50% - Some attempt was made and general concepts are started
0% - Nothing submitted