ICS22 - Section A4 - Grading Criteria (course code: 36061 time: Tue/Wed 1:00-1:50/2:00-2:50) For each assignment you are being evaluated according to the following criteria: CRITERIA MAXIMUM GRADE DESCRIPTION Correctness 15 The program has to respond properly, providing a correct output for each expected input. For example, in assignment 1, if I deposit 10 and withdraw 5 from the account, I expect the balance to be 5. If I choose an option from the menu, I expect it to work, and so on. If for some simple syntactic error your program does not compile and I can fix it in less than 5 minutes, I will still grade this part of your assignment but will discount -3 points for the compile error. If after 5 minutes, I cannot make your program run, you get 0 for this criteria. This criteria is independent from the Testing one. Starting from assignment 2, if the testing program does not work, you can also get full credit for this criteria if the program itself works properly, responding as expected to the tests I perform with it. Robustness 2 The program should not crash. It evaluates wether the program is tolerant to wrong inputs and the end-user mistakes. For example, I will check whether the program breaks when I press ENTER or type a character instead of a number. Whether it freezes during the execution or prints exception traces to the output when I run it and so on.  Design Quality 2 The classes you defined correspond to the entities of the problem. The basic OO paradigm design techniques are observed. In other words, you get full credit if you are not writting procedural code using an OO language and your code is properly modelled as a set of interacting objects, as oposed to a set of procedure calls. A BAD example would be to write the whole program in a single .java file, use static methods and attributes in an umproper way , access attributes directly instead of through set/get methods, and so on. Another BAD example would be to have the program engine integrated with the user interface object. There should be no interaction with the end-user in the program engine, such as console reading methods, printing of menus and so on. Style 2 See page Style and Documentation Standards It refers to how close to the standard style is your source code written. Documentation 2 See page Style and Documentation Standards It refers to how well is your source code commented, according to the standards defined for this class. Testing 6 This part evaluates your testing document or program, evaluating how thorough it is. You will get a full credit for that if your test: Is formated according to the test cases template and example described in the Project1 assignment. Which includes: test case name, purpose, steps, expected output and additional comments. If it is complete, describing the main test cases for the possible inputs of the program. It must include: normal cases, error cases and boundary cases. It is clear and not ambiguous. Starting on project 2, it will evaluate how good is your testing program. Turned in correctly? 1 See Page How to submit your project. I give you full credit if you submitted only the .java files and the .doc test case, and if the directory name is correct. If any of those is not correct, the score will be 0. In other words, if you submit .class files, you lose the point. If you do not name the folder exactly right, you also lose the point. TOTAL POINTS 30   Page updated on January 22nd, 2002. E-mail:rsilvafi@ics.uci.edu