Grading Checkpoints
How your Design + Capstone checkpoints will be graded
PROJECTS OVERIEW
Projects will be divided into a number of checkpoints and a final release
For example, the AP Java Projects typically are organized into:
Alpha (20 points)
Beta (20 points)
Release (100 points)
During each checkpoint, students are graded based on PROCESS and GOALS
For the final release, students are graded based on EXECUTION, AMBITION, CODE QUALITY, and AUDIENCE SCORE
SUBMISSION RULES
Create a zip file with the exact folder organization as shown below. We'll use the project "AceTD" submitting the Beta as an example:
AceTDBeta
Code
AceTowerDefense <--- this is your project folder, copied without changing the name
libs
src
res
and other files
Jar <--- this folder should not be dependent on any other files
openJdk
res
jar file
launch
Screenshots
title.png
gameplay.png
README <--- this is a txt file containing info for Mal, like known bugs and controls
PROCESS SCORE
50%
Jar File does not work
OR
Late enough that it impacts presentation / testing day
80%
Does not follow submission format rules
OR
Trello isn't up to date
OR
Late, but able to be uploaded for presentation / testing
100%
Project is on time
AND
All submission and process rules followed.
110%
Project is turned in by the early submission deadline
AND
All submission and process rules followed.
GOALS SCORE
S - 105%
"Exceeds Expectations"
Went beyond contact goals, either through substantial progress into future checkpoint goals or exceptional implementation of all current goals.
A - 95%
"On Track"
Met all goals for a project of normal ambition
Project had few (if any) bugs or limiting factors
B - 85%
"A Bit Off"
Project is missing a minor goal or has poor execution / contains bugs that impact a single system.
C - 75%
"Some Real Work To Do"
Project is missing up to 25% of contract goals or is failing to meet the main objective of the current development phase.
D - 65%
"Oh No..."
Project is missing up to 50% of contract goals, or has extremely poor execution. Projects in this level often feel one phase behind (ie, an "Beta" that resembles an "Alpha") in terms of goals
E - 50%
"Shockingly Bad"
Missing up to 75% of your goals, or fail to turn in a program with a running Jar file.