Extra Credit - Build a STABLE Case

Discuss extra credit here

Up to six extra points are available for students as extra credit for building a case to be added to the STABLE case base. These are six points that could really make a difference -- they will be added to your final score in the class! As a contrast, six points on a given assignment is six points that will be added amongst all the other programming assignments then multiplied by the weighting factor for assignments. These six points get added in to your final grade, so it's literally a half a grade jump -- If you get them...

Instructions for how to build a case are available. Also, to serve as an example, the source code for a previous version of STABLE (in Python) including all the existing cases is posted in ~mg65/stable (on Acme) and ~guzdial/stable (on CoC).

You may only submit ONE case for extra credit. You must build a case on a problem that you've done in this class. It is due NO LATER THAN DECEMBER 18! There are two different ways to get extra credit.

Path One: Build a Case!

Build a case on an assignment in this class, where you correct everything that you lost points on. YOU MUST CORRECT EVERYTHING THAT YOU GOT POINTS OFF FOR!. If you correct everything, you get two points. If your case is good (e.g., good descriptions, good decomposition into steps, and good concepts and generic steps), you get an a total four points. If you create an amazing case (e.g., you create GIF representations and imagemaps, you fill out the four levels of a step, you create new concepts and generic steps), you get all six points. Yes, you may work in teams.

Path Two: Act as a Reviewer for a Case

If you got less than 10 points off on a given assignment, you are eligible to be a reviewer for that assignment. You can get up to two extra points (again, added to your final grade) if you review someone's case and guarantee its correctness -- AND I agree that the quality is good.

Rules:

You may submit only one case! Building a case is hard. I want good ones.
You may not be both a reviewer and a builder! If you have little time but want to get some extra credit, be a reviewer. If you want more extra credit, be a builder. But I don't want anyone sinking so much time into this that they try to be both.

What to Hand In

You must submit to me:

Softcopy (diskette, email, or files available via Acme or CoC filesystem) of the case file(s) itself. (List in the Author field of the Project both the case-writer and the reviewer, if there was one.)
GIF files of the representations for your case, if you did them.
Imagemap files for the representations of your case, if you did them..
The original hand-in (design doc and code) for me to compare and check that the points-off was right. (Reviewer's should be included, too!) Xerox copies are acceptable.

Criteria for Grading

Things I'll be looking for when evaluating your cases:

Does your hierarchy of steps make sense? (Does it have multiple levels?)
Is the repair information good?
Do you reference existing concepts and generic steps? Do you add new ones?
Are you communicating the PROCESS -- what were the issues that you considered when designing and building this assignment?