Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 2

Project Name: ________________________________________ Course/Year/Section: ________________

Group Members:
1. ____________________________ 5. ____________________________
2. ____________________________ 6. ____________________________
3. ____________________________ 7. ____________________________
4. ____________________________ 8. ____________________________

Criteria  Code is messy and hard to follow.


1. Functionality (40 Points): __________ No comments or documentation.
o Excellent (35-40 points):
 The project fully meets all specified
requirements. 3. User Interface (15 Points): __________
 All features work correctly without o Excellent (12-15 points):
any major bugs.  Intuitive and visually appealing
 Exception handling is thorough. interface.
o Good (25-34 points):  Proper error messages and user
 Most requirements are met, but feedback.
minor issues exist. o Good (8-11 points):
 Some features may not work as  Functional interface but lacks polish.
expected.  Some usability issues.
 Basic exception handling is o Fair (4-7 points):
implemented.  Basic interface with limited usability.
o Fair (15-24 points):  Error handling needs improvement.
 Several requirements are missing or o Poor (0-3 points):
incomplete.  No user interface or unusable
 Significant issues or bugs affect interface.
functionality.
 Limited or no exception handling.
o Poor (0-14 points):
 The project lacks essential
functionality.
 Major bugs prevent proper
execution.
 No exception handling. 4. Creativity and Extra Features (15 Points): _______
2. Code Quality (30 Points): __________ o Excellent (12-15 points):
o Excellent (25-30 points):  Innovative features or
 Code is well-organized, modular, and enhancements beyond
follows best practices. requirements.
 Meaningful variable/method names.  Demonstrates creativity.
 Proper indentation and comments. o Good (8-11 points):
o Good (18-24 points):  Some additional features or minor
 Code structure is mostly clear. improvements.
 Some areas need improvement (e.g.,  Shows effort beyond the basics.
naming conventions). o Fair (4-7 points):
 Adequate comments.  No significant creativity or extra
o Fair (10-17 points): features.
 Code lacks organization or  Meets minimum requirements only.
readability. o Poor (0-3 points):
 Inconsistent naming or poor  No attempt at creativity or
formatting. additional features.
 Minimal comments.
o Poor (0-9 points):
Total Score: __________________
Information System Project Grading Rubrics
Information System Project Grading Rubrics

You might also like