“So what is this thing you keep banging on about, this Grading Declaration?” I hear you ask. Well, the hint is in the name, really: the grading declaration is a requirement in each assignment that you declare you should get a particular grade on that assignment.
More than that, it’s an affirmation that you’ve:
This is easier if you can actually get a feeling for the workflow.
Here’s an example for Project 1. You’ll start off with some targets in your assignment like this:
Mechanics: No errors in spelling or grammar. All properly formatted citations.
Timeliness: Submitted prior to due date.
Task 1: Objects: Objects are all task-related (nouns)
Task 1: Attributes: Attributes are all task-focused
Task 1: Operations: Operations listed are all task-focused
Task 2: Goals: Model accounts for all four goals in the brief
Task 2: Detail: Models are complete, accounting for major objects, attributes, and operations of each goal
Task 2: Objects: Objects are all task-related (nouns)
Task 2: Attributes: Attributes are all task-focused
Task 2: Operations: Operations listed are all task-focused
And when you go to submit the assignment, you’ll first look for the Grading Declaration quiz. In this case, Grading Declaration: Project 1. For each of the targets above, you’ll see a corresponding short answer quiz item. Simply explain how you feel you accomplished that target for that category. Easy as that!
Once you’ve submitted your declaration quiz you should see the associated assignment submission folder open up. Submit your assignment as usual and, hey presto, time to move on to the next one.
I reserve the right to overrule if I feel the declaration is not in good faith! Example: you declare user testing was done but the submission does not demonstrate any, I will reverse that point.