PA High School Computer Fair
Programming Rubric

 
4
3
2
1
  
Documentation Code is well documented and commented. Clear end-user documentation is provided explaining software functionality and features. Documentation and coding provided, but may be incomplete or not particularly well thought out. Documentation and commenting is confusing and/or missing essential explanations of features and functionality. No documentation or code commenting provided. Documentation
Score is:
Flow chart The flow chart was clear, easy to understand, described the entire program correctly, and correctly used all the generally accepted flow charting symbols. The flow chart was somewhat clear, understandable and described the program correctly. There was misuse of some of the generally accepted flow charting symbols. The flow chart was unclear, hard to understand, did not fully describe the entire program correctly, and misused several of the generally accepted flow charting symbols The flow chart was extremely poor. Flowchart
Score is:
Problem Solving The program solved all the problems. The program solved all of the problems but not in the most clear and logical manner. The program did not solve the problem well and was unclear and illogical. The program did not solve the problem at all and would be entirely unusable. Problem Solving Score is:
Coding Conventions The code is well organized, easy to follow (tabbed, indented, no ambiguous variable names, etc.), and reusable. Code is well thought out and clean, but may not adhere to strict coding standards. The code solves the problem, but not in the most elegant and reusable way. Code is thrown together with little thought given to standards and reusability. The code solves the problem but in a complicated, unclean manner. Code is difficult to follow with little or no thought given to coding standards. Unnecessarily complex control flow; spaghetti code. Coding Conventions Score is:
User Interface Interface is intuitive, well-thought out, organized, clean, provides access to all features of the software, and aesthetically sound. The type of user interface is truly relevant to the program created.  User input is validated. Interface is usable, but may not be as well implemented as possible.  The type of user interface is relevant to the program created. All expected software features are accessible. Interface is non-intuitive, and visually distracting or unappealing. The type of user interface is slightly relevant to the program created. Interface does not provide access to essential features of the software or is unusable.   The type of user interface is irrelevant to the program created. User Interface
Score is: