US12C - Design Document Draft -
Grading Rubric
| Letter Grades | Overview |
Game Specs |
Technical Specs | Schedule & Personnel | Language & Structure |
| A (+100 points) |
game concept is original and insightful; gives an articulate and vivid understanding of game; clear description of background story; detailed description of game play and important rules; exceptional description of art. | exceptional "rule book" for game; clear
description of interactions, rules, mechanics, artwork, UI, gameplay,
sound, characters, levels, scripts; excellent use of screenshots / artwork |
all rules from game specs translated into an exceptionally clear, specific, unambiguous, and implementable format;. superb consideration of implications, exceptions, and exact limits; excellent use of screenshots / artwork | each team member has a clear set of responsibilities, deliverables; logical sequence for deliverables; statement from each team member about what he/she needs to learn in the remainder of the course | uses sophisticated sentences effectively;
chooses words aptly; observes conventions of written English
and manuscript format; excellent document structure; posted online |
| B (+85 points) |
game concept is good; gives good understanding of game; good description of background story; better-than-average description of game play, important rules, and art. | a good "rule book" for the
game; describes the types of interactions the player can have; would be
fairly easy to turn into a manual; good use of screenshots / artwork |
most rules from game specs
translated into a
specific, unambiguous, and implementable format; good use of screenshots / artwork |
team members have
responsibilities and deliverables; deliverables could be
better-defined; fairly logical sequence for deliverables |
some mechanical difficulties or stylistic
problems; may make occasional problematic word choices or awkward
syntax errors; good document structure; posted online with minor
problems |
| C (+75 points) |
game concept could use
improvement; game description somewhat
confusing or inconsistent; components of background story, game play,
rules or art are lacking |
only partially develops the "rule book"; some components need work: interactions, rules, mechanics, artwork, UI, gameplay, sound, characters, levels, scripts | game specs for the most part are translated into tech specs in an unclear, unspecific, or non-implementable manner; moderate consideration of implications, exceptions, and exact limits | responsibilities and tasks unclear;
deliverables not made explicit enough; unclear deadlines; needs more
foresight |
several unclear or
awkward sections; includes a number of misspelled
words, awkward
grammar repetitions, unstated assumptions or
vague assertions; document structure lacking; posted online with
problems |
| D (+65 points) |
game concept is weak; description does not
respond directly to
the demands of the assignment; overview needs considerable work |
significant oversight of a number of key issues: interactions, rules, mechanics, artwork, UI, gameplay, sound, characters, levels, scripts | written in a format that is difficult to implement; unclear; no significant consideration of implications, exceptions, and exact limits | confusing deliverables and deadlines; unclear
how some members are contributing; little foresight |
some major grammatical or proofreading errors;
misspelled words, awkward
grammar, needless repetitions, unstated assumptions,
vague assertions and omissions
of important features; poor format; not online |
| F (+55 points) |
game concept shows no originality; overview
does not give a description of the
game |
little or no development of game specification |
little or no development of technical
specification, very unclear |
project management completely lacking |
numerous grammatical errors and stylistic
problems that seriously distract from the document; confusing format;
not online |
| Category grade/score |