Lab 7 Grading Guideline Automatic Grades of 0 awarded for the following reasons: [1] If the student's .java files do not appear in the submission. [2] If the code does not compile. [3] If the code does not run. [A] UML Diagram & Attendance (20%) UML diagram submitted and shows overall design. (3 points) [A1] Shows the "behavior" classes. (3 points) [A2] A "double" behavior class is included. (3 points) [A3] Includes a new bacteria class that extends from one of the lab7lib.shapes class. (3 points) [A4] Shows other relevant classes to the project. (8 points) [A5] Student present at Lab 7 session (Week of 3/17). [B] Design/Style (37%) (12 points) [B1] Students have created an interface for the behaviors of the bacteria (4 points). This interface should have one method that is called when the bacteria need to be updated (4 points). This method should take as a parameter the bacteria class that the student's created (4 points). ( 5 points) [B2] There is a Null Object. Students have a class that implements the Behavior interface, but is a "do nothing" behavior. (10 points) [B1] Uses the composite design pattern. i.e. - a class that can perform 2 behaviors is composed to get the multi-behavior. Composites that compose more than two behaviors should receive 0 points. (10 points) [B2] Uses inheritance appropriately to create new bacteria class. [C] Functionality (43%) (5 points) [C1] There is a class that models the Petri Dish and can be run as an application. (12 points) [C2] Each of the behaviors work properly (3 points each) Color Changing Turning Breathing Random Movement (6 points) [C3] Menu appears and allows user to select current behaviors without creating a bacterium. (10 points) [C4] Behaviors work in single(6) or in multiples (10). (10 points) [C5] Clicking any bacterium makes it take on the behavior currently selected in the menu. DEDUCTIONS [D] Null Pointer Exceptions (15 points maximum deduction) BEFORE any other menu items are selected, selecting the "Create" button should not cause any NullPointerExceptions. The exact behavior of the student program at this point does not matter, but an Exception should not be thrown. Also, at no other time while their code is running should a NullPointerException be thrown. If a NullPointer is thrown at either time, 15 points should be deducted from the student's score. [E] Style (20 points maximum deduction) If the submitted code does not meet the given criterion, it should be deducted the appropriate (5 points)[E1] Code uses proper tabbing and whitespace for readability. (5 points)[E2] Naming of classes, methods, and variables are meaningful to the project. (5 points)[E3] Naming conventions for classes, methods, variables, parameters are following according to CSE 115 styles. (5 points)[E4] Every class, instance variable, and method is commented with its purpose in the project. GIVING FEEDBACK You must e-mail a feedback/grade message to each student whose work you grade. You will ONLY e-mail to the student's cse e-mail account, which is username@cse.buffalo.edu. The subject line will be: CSE115 Lab 7 Grade and feedback A copy of this ENTIRE email with the bottom part filled in by you should be sent to the student for their reference. If a student receives less that the maximum number of points, you must give an explanation of why the student lost points. ---------------------------------------------------------------------- [Lab #7: 100 points maximum] Your score ==> [A: 20 points maximum] You earned ==> Breakdown: [A1: 3 max] ==> [A2: 3 max] ==> [A3: 3 max] ==> [A4: 3 max] ==> [A5: 8 max] ==> [B: 37 points maximum] You earned ==> Breakdown: [B1: 12 max] ==> [B2: 5 max] ==> [B3: 10 max] ==> [B4: 10 max] ==> [C: 43 points maximum] You earned ==> Breakdown: [C1: 5 max] ==> [C2: 12 max] ==> [C3: 6 max] ==> [C4: 10 max] ==> [C5: 10 max] ==> DEDUCTIONS [35 points max deduction] [D: 15 points max deduction] ==> [E: 20 points max deduction] Breakdown: [E1: 5 max] ==> [E2: 5 max] ==> [E3: 5 max] ==> [E4: 5 max] ==> AUTOMATIC GRADE ASSIGNED: Reason: