In real life programming there is always a debugging phase after the testing phase. It is only in school that you never get a chance to fix your mistakes. In this assignment you will be “debugging” your Fundamentals Exam stack.
When I graded your exams I went through them thoroughly and scored each part according to a scoring rubric. In the chart below you will see each part broken down according to the requirements given in the exam. Each requirement has a certain number of possible points. Next to the possible points I list the points I gave you on each requirement. Your task will be to discover why you lost points and to attempt to correct your errors.
This assignment is separate from the exam—you can’t change your exam score. Here is how I score this assignment: The total number of possible points for this assignment is 15. Whatever percentage of your errors you correct, will determine how many of the 15 point you get. For example, if you got an 88 on the exam and you correct all 12 points, you get all 15 points for this assignment; if you only correct 8 out of 12, you get 67% of 15, or 10 points, and so forth. Each error that you fail to correct will lower your score for this assignment commensurately. (Note: If you got 100% on the exam you don't have to do anything—you automatically receive the 15 points.)
You may take as much time as you like for this assignment, but it must be returned one week from the date given for full credit.
To avoid a "double jeopardy" situation in which you are penalized twice for the same error, I am providing a safety valve in case you just can't find the errors. In the Keys folder on the server there is a stack called FundExamKey2010.rev. It contains my solutions to all of the problems on the exam. If you just cannot figure out what you did wrong, you may consult the key. (Remember, however, that my solutions may differ from yours in some cases. That does not mean yours is wrong. In programming there may often be more than one correct solution to a problem.)
You may consult any source in making your corrections, including the instructor, TA, other students, and the exam key. But please try to find and correct your errors by yourself before you resort to these sources, since this will provide the very best learning experience.
If you find an error that I missed in the grading and point it out you will not lose points.
If you find something in your exam that I marked incorrect, but you think is correct, please ask me about it. If you can convince me you're right, I will adjust your exam score.
This is what you should turn in:
Turn this in to the Assignment Drop folder one week from the date given.
Fundamentals Exam Scoring Rubrik
Section | Possible Points |
Beginnings: Set up the stack and cards | 16 |
stackfile name | 1 |
stack name | 1 |
stack title | 1 |
"stack BG color, font" | 2 |
name cards | 3 |
title txt color & size | 2 |
name fld group | 3 |
date & cd num grp | 3 |
Cd 1: Free Responses | 15 |
What is Message box? |
3 |
target vs. me |
4 |
What unique abt groups? |
2 |
Difference between remove & del. group |
3 |
What is cond statement? |
3 |
Cd 2: Scripting Terminology | 6 |
|
6 |
Cd 3: Scripting | 26 |
#1. Warning blinker
|
6 |
#2. Showing the date
|
6 |
#3. Help button icons
|
8 |
#4. Go and Return button
| 6 |
Cd 4: Pseudocode | 12 |
Code is Thorough |
6 |
Code is Efficient | 6 |
Cd 5: Imgs & Grcs | 14 |
"Import main image, resize & lock; best quality" |
3 |
"Import image 2, resize& lock; best quality" |
3 |
"Proper layering: frame, lens, detail, handle, main img" |
2 |
"Glass graphic: change gradient color, set blending" |
2 |
"frame graphic - thick line, perfect circle" |
2 |
resize & reposition handle |
2 |
Finishing touches | 6 |
|
|
Observe best practices throughout | 5 |
TOTAL | 100 |