Computer Science 121

Weekly Code/Prototypes

Each week through the remainder of the project you'll typically develop code; this code can be in the form of a prototype that is intended to be thrown away or an extension to your code base for your Alpha. In the case of a prototype, you should follow the prototype instructions from phase I. In the case that you are extending your Alpha code base you should clarify your goal and how you will assess your result before you begin.

If you are adding new functionality, you should describe your goal in terms of its external behavior in a Use Case. You should validate your results by walking through the Use Case in your game.
Whether or not the new code exhibits external behavior, you should describe your goals using a test-first methodology. Ideally, you will write the tests your code is expected to pass before writing the code. Then implement the tests in order to assess your code.
Finally, you should write a brief rationalization for your choices and assessment of the results.

Your discussion, decisions, and rationale should be documented (and labeled "Code/Prototype goals" and "Code/Prototype results") in your planning/assessment notes. Your efforts will be evaluated using this rubric.

Mike Erlinger

Last Modified Tuesday, 02-Oct-2012 13:12:31 PDT