Grading Rubric for Project 1

Project Requirements. Total points 100/100.

1. 122 Information Architecture: 17/17.
   
   Your 122 root directory on shell.uoregon.edu is ~/public_html/122 (I will abbreviate ~/public_html/11/ as /122)
   
   
   • 7/7. /122/ contains subdirectories named p1, p2, ..., and p5.
   • 10/10. All C++ files created for this project are in /122/p1
     
     
2. File-- greet-by-name.cpp: 21/21 .
   
   
   • 3/3. File identifier must be greet-by-name.cpp
   • 7/7. User is prompted for name and then greeted by name. (First, last and/or both is OK).
   • 5/5. Proper formatting: All statements in main indented; program header comment at top of source file, etc. See Supplement E: Guidelines for Programming Style and Documentation at companion website.
   • 3/3. No global variables-- all variables declared at the top of the body of main. Global constants are OK.
   • 3/3. Variable identifiers begin with lower-case letter, not a capital. camelCase (or underscore) used in multi-word identifiers (examples: camelCase, camel_case but not CamelCase or Camel_Case).
     
     


3. File-- tipCalc.cpp: 31/31 .
   
   
   • 3/3. File identifier must be tipCalc.cpp
   • 7/7. Correct results for gratuity and total.
   • 10/10. Meets the I/O spec given on the project page
   • 5/5. Proper formatting: All statements in main indented; program header comment at top of source file, etc. See Supplement E: Guidelines for Programming Style and Documentation at companion website.
   • 3/3. No global variables-- all variables declared at the top of the body of main. Global constants are OK.
   • 3/3. Variable identifiers begin with lower-case letter, not a capital. camelCase (or underscore) used in multi-word identifiers (examples: camelCase, camel_case but not CamelCase or Camel_Case).
   
   
   
4. File-- toUC.cpp: 31/31 .
   
   
   • 3/3. File identifier must be toUC.cpp
   • 7/7. User is prompted for Upper Case letter
   • 5/5. Correct Lower Case letter for the input is displayed
   • 5/5. Input is Echoed
   • 5/5. Proper formatting: All statements in main indented; program header comment at top of source file, etc. See Supplement E: Guidelines for Programming Style and Documentation at companion website.
   • 3/3. No global variables-- all variables declared at the top of the body of main. Global constants are OK.
   • 3/3. Variable identifiers begin with lower-case letter, not a capital. camelCase (or underscore) used in multi-word identifiers (examples: camelCase, camel_case but not CamelCase or Camel_Case).
   
   
5. Extra Credit Option (5 pts added to project score): On Time Delivery.
   
   Extra credit work is not required; there is no penalty to your grade for not doing extra credit.
   
   Students must notify the instructors that extra credit was completed: Use the Comments section when submitting your project in Blackboard, and state which XC options you completed.
   
   
6. How to Submit Project 1 for Grading in Blackboard.
   
   On or before the due-date submit the project using the BB Assigment in Projects > Submit Project 1.
   
   Use the "Attach local file" button in BB to attach each of the .cpp files you created for this project.
   
   When you submit your project using the BB Assigment feature, you will have the option of filling in a Comments textbox. Use it to flag XC options you completed (if any), or to bring anything you'd like to your grader's attention.
   
   If you do not use this BB assignment turn-in feature, you will not have a score entered for this project in the gradebook, so please do not forget to do this on or before the due-date.
   
   
7. Programming Teams. Working as part of a two-member team is an option; groups of three or more are not not an option.
   
   If you work as a team:

   A. You must notify the grader of both programmer names in the Comments section when submitting the project in Blackboard
   
   B. Each partner must maintain copies of all project files, etc., in his or her /122 folder on shell.uroegon.edu

8. Required Reading: Policy on Due-Dates.