Lab 1, Click Counter—Grading Rubric
| Functionality | 45/40 Points Total |
|---|
| Criteria | |
| Is a count of zero shown initially when the app is started? | 2/2 |
| Does the “Add One” button increment the count? | 18/18 |
| Does the “Reset” button set the count back to zero? | 10/10 |
| Are all the required widgets in the UI? | 5/5 |
| Does the UI look reasonably neat and is all text visible? | 5/5 |
| Optional, extra credit. Is the count preserved when you rotate the device? | 5/5 |
| Code Quality | 10/10 Points Total |
|---|
| Criteria | |
| Does the program run without crashing? (No unhandled exceptions) | 3/3 |
| Does the coding style follow the conventions used in this course? | 3/3 |
| Have "best practices" for programming been used? | 4/4 |
Criteria for coding style
- Proper indentation is used.
- UI elements are named according to convention (example: incrementButton).
- Java variables, constants, methods, and classes are named using descriptive names (Example: int count, not int i).
- Unnecessary lines of code or files been removed (no commented out code or left-over boiler-plate).
- Explanatory comments are in the code (Coments that explain why you did what you did).
- Variable names and methods use camel case (Example: camelCase).
- Constants are used where needed and named using ALL_CAPS.
- Classes are named using PascalCase (aka TitleCase).
Programming "best practices"
- Constatnts are useda for repeated literals.
- Variables are properly intialized.
- Variables are declared in the correct scope.
- Code is DRY (blocks of code are not duplicated.)
- Correct parameters are used in method declarations.
- Correct access level is used for instance variables, methods and classes (public, private, protected).