W2005 A1 Information
Marking and Submission Information
The mark for A1 will be out of 100, with
the assignment is intentionally somewhat vague
for the following reasons:
- 50 for correctness (i.e., program does what is required)
- 10 for design, i.e.,
- at least one subclass
- private instance variables
- using methods rather than repeating code
- good separation of the user interface classes
(e.g., VendingFrame) from the
backend classes (e.g., VendingMachine and Product). That is,
each class should have a well-focussed responsibility).
- 10 for robustness (exception handling)
- 10 for doing the demo
- 20 for documentation
- javadoc-style comments before each class and method. (Try running
javadoc *.java to see if you get a good set of html files
describing your API).
- proper indentation
- all variables and methods start with lower case letters, class starts
with upper case letter, constants all upper case
- include a README file which explains roughly what your program
does and any interesting features or approaches that you took. Also
mention any extra features that you would like to be considered for
for bonus marks (Max. 5 bonus marks).
- to give you room to invent your own solution;
- problem descriptions in the real world are often
initially vague, and part of your job is to find out details
by asking questions;
Therefore, I will accept reasonable variation in your interpretation
of what is required. Also, it goes without saying that your code
should not be too similar to anyone elses (see the CMF re. plagiarism).
If some part of your code is from somewhere other than your head or
the course text, cite your source in a comment.
submit-cps209-0n *.java (where this includes all the files necessary
to compile your program).
submit-cps209-0n README (where this text file explains what works
and what doesn't work in your assignment).