Scribd
Upload
9K views

Programming Project Rubric v2-2013

This document provides a rubric for evaluating a programming project with criteria in 8 categories: requirements, design document, timeliness, bugs, attention to detail, graphical user interface, code comments, and use of programming language. Points are awarded on a scale from 0 to 10 for each category. Students must earn at least 70 total points to pass. Additional points above 70 are awarded for higher quality work in areas like design documentation, code comments, and interface design. The highest possible scores recognize projects that apply class concepts elegantly and include challenging embellishments.

Uploaded by

meynardadu
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
9K views

Programming Project Rubric v2-2013

This document provides a rubric for evaluating a programming project with criteria in 8 categories: requirements, design document, timeliness, bugs, attention to detail, graphical user interface, code comments, and use of programming language. Points are awarded on a scale from 0 to 10 for each category. Students must earn at least 70 total points to pass. Additional points above 70 are awarded for higher quality work in areas like design documentation, code comments, and interface design. The highest possible scores recognize projects that apply class concepts elegantly and include challenging embellishments.

Uploaded by

meynardadu
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Programming Project Rubric

Name_______________________________ Total Score ________________________________

1. Meets all requirements & runs


0 pts (more than 1 requirement missing, program crashes, or will not compile).
5 pts (missing 1 requirement as listed on project requirements sheet)
10 pts (all requirements met and runs with no errors)
2. Design document (must be turned in prior to grading conference)
0 pts (missing one or more of the design document components)
5 pts (Documents turned in, but contain spelling errors, grammar errors, or incomplete responses to program
elements)
10 pts (Documents are error free and word processed, descriptions include extensive detail)
3. Project software is released on time
0 pts Project software not available during grading conference
10 pts Project available during grading conference
4. No fatal runtime errors or runtime bugs
0 pts (contains more than 1 run time bug or error).
5 pts (contains 1 run time bug or error)
10 pts (all requirements met and runs with no errors)
5. Attention to detail
0 pts (contains more than one of the following: spelling errors, grammar errors, object named incorrectly, extra
objects, etc.).
5 pts (contains one of the following: spelling error, grammar error, object named incorrectly, extra object, etc.)
10 pts (program contains no errors attributable to simple mistakes or oversights. Spelling, grammar, object
names, choice of objects, object alignment, etc. all checked)
6. Graphical User Interface
0 pts (GUI suffers from more than one of the following: visually distracting objects, clashing colors, inconsistent
graphical components, poor alignment, sizing or spacing, non-standard software interface conventions)
5 pts (GUI suffers from only one of the following: visually distracting objects, clashing colors, inconsistent
software components, poor alignment, sizing or spacing, non-standard software interface conventions)
10 pts (GUI satisfies all of the following: visually attractive objects, compatible colors, consistent software
components, great alignment, sizing and spacing, standard software interface conventions followed)
7. Code is commented and documented
0 pts (Code contains more than one of the following: undefined variables, procedures or functions without
adequate documentation or description)
5 pts (Code contains one of the following: undefined variables, procedures or functions without adequate
documentation or description)
10 pts (Code contains the following: all variables defined and commented, procedures and functions adequately
documented and described)
8. Best use of visual basic language
0 pts (Concepts from class are not applied to the program)
5 pts (Concepts from class are applied, however, code contains unused VB elements ->variables, procedures etc.
, code has flow which is jumpy, ‘spaghetti’, programmer patches were applied, or code contains
unnecessary statements)
10 pts (Concepts from class are applied, Code is straight forward, consistent, logic uses the most direct approach
available in VB and does not rely on programmer patches)

(More on the other side)


Students must earn at least 70 points from the above section to continue to next sections.
Students who earn less than 70 points will need to resubmit their software with a 10% penalty after they correct the problems outlined
above and can prove they understand the material covered in this unit.

To Earn a B:
+2 pts Design document
(Documents are error free and word processed, descriptions include extensive detail and technology is used
to enhance the Design document)

+2 pts Code is commented (Comments are clear, well thought out and clearly describe the VB component:
variables defined, procedures/functions described fully)

+3 pts Graphical User Interface (GUI meets the following with a high degree of attention to detail: visually
focused, colors compliment, consistent throughout software components, follows standard software
interface conventions)

+3 pts Best use of visual basic language (Concepts from class are applied in an integrated and elegant
fashion, code is efficient and as streamlined as possible)

To Earn an A:
+5 pts Embellishment (Project embellishment shows extra work, challenges the student’s programming ability,
is useful to the program and is well executed)

+5 pts Embellishment (Project embellishment is perfectly executed and requires the integration of more difficult
concepts into the project)

You might also like