Program 3 Grading Guide
** Print out this document, fill in the top section and include this with your homework submission. **

Name

____________________________

ID __________________

Partner 

____________________________

ID __________________

Grader 

____________________________

 

Grade (correctness / style)  _______ / _______

Section Number

___________

 

Section Day:     Mon       Tues
Section Time:     10:10       1:25       2:30       3:35
Section Instructor:  ______________________

The following lists items necessary for a correct assignment. Items you missed have been crossed out on this sheet, and the item code has been written in your program at the appropriate place.

Correctness
c11  Printouts of both Classes are included.
c12  Textual printout
demonstrates program functionality.

Class Person
c21  toString() properly modified to display friend information.
c22  newFriend(Person p) correctly makes Person p a friend and has appropriate return codes.
c23  removeFriend(Person p) correctly removes p as a friend and has appropriate return codes.
c24  Access methods name() and male() correctly implemented.
c25  Person class does not allow states disallowed in the constraints.
c26  Other (specify):

Class Program3
c31  showPeople() correctly displays every person in the database
c32  stringToPerson(String name) correctly returns the Person with the corresponding name
c33  personExists(String name) correctly returns true if a Person exists with the corresponding name
c34  main() correctly obtains and processes input from user
c35  the correct error messages are displayed when constraints are violated.
c36  Other (specify):

Organization and Style
s11  Assignment included with name(s), ID(s), and section info
s12  Program and output stapled together, pages separated, perforated edges removed from printout.
s13  Printouts are legible (e.g. nothing relevant cut off)
s14  Printouts of textual output and screen snapshot
s15  Appearance of program is easy to read (e.g. not cluttered or confusing, code indented well)
s16  Other (specify):

Class Person
s21  Specifications of Class Person followed (i.e. no extra public classes)
s22  All new fields and helper methods are private
s23  Generally good  OOP style followed (i.e. no methods irrelevant to Class Person, no unnecessary fields)
s24  Comments added/modified appropriately
s25  Other (specify):

Class Program3
s31  Helper methods are used where appropriate to avoid redundancy
s32  Does not include components of Class Person that should be properly encapsulated
s33  Comments added/modified appropriately
s34  Other (specify):