JamesFlare/CSCI-1200
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

adjusting rubrics

Browse Source
This commit is contained in:
Jidong Xiao
2023-10-05 00:16:00 -04:00
parent 6fdb239551
commit 0ca8059034
1 changed files with 3 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
hws/05_online_dating/README.md
View File

@@ -155,8 +155,7 @@ In this assignment, you are required to create linked lists, **but you are not a
Use good coding style when you design and implement your program. Organize your program into functions: Use good coding style when you design and implement your program. Organize your program into functions:
don’t put all the code in main! Be sure to read the [Homework Policies](https://www.cs.rpi.edu/academics/courses/fall23/csci1200/homework_policies.php) as you put the finishing touches on your solution. Be sure to make up new test cases to fully debug your program and don’t forget don’t put all the code in main! Be sure to read the [Homework Policies](https://www.cs.rpi.edu/academics/courses/fall23/csci1200/homework_policies.php) as you put the finishing touches on your solution. Be sure to make up new test cases to fully debug your program and don’t forget
to comment your code! Use the provided template [README.txt](./README.txt) file for notes you want the grader to read. to comment your code! Use the provided template [README.txt](./README.txt) file for notes you want the grader to read.
You must do this assignment on your own, as described in the [Collaboration Policy & Academic Integrity](https://www.cs.rpi.edu/academics/courses/fall23/csci1200/academic_integrity.php) page. If you did discuss the problem or error messages, etc. with anyone, please list their names in your You must do this assignment on your own, as described in the [Collaboration Policy & Academic Integrity](https://www.cs.rpi.edu/academics/courses/fall23/csci1200/academic_integrity.php) page. If you did discuss the problem or error messages, etc. with anyone, please list their names in your README.txt file.
README.txt file.
**Due Date**: 10/12/2023, Thursday, 23:59pm. **Due Date**: 10/12/2023, Thursday, 23:59pm.
@@ -166,8 +165,8 @@ README.txt file.
- README.txt Completed (2 pts) - README.txt Completed (2 pts)
- One of name, collaborators, or hours not filled in. (-1) - One of name, collaborators, or hours not filled in. (-1)
- Two or more of name, collaborators, or hours not filled in. (-2) - Two or more of name, collaborators, or hours not filled in. (-2)
- OVERALL CLASS DECLARATION & IMPLEMENTATION AND CODING STYLE (Good class design, split into a .h and .cpp file. Functions > 1 line are in .cpp file. Organized class implementation and reasonable comments throughout. Correct use of const/const& and of class method const. ) (7 pts) - OVERALL CLASS DECLARATION & IMPLEMENTATION AND CODING STYLE (Good class design, split into a .h and .cpp file. Functions > 1 line are in .cpp file. Organized class implementation and reasonable comments throughout. Correct use of const/const& and of class method const. ) (6 pts)
- No credit (significantly incomplete implementation) (-7) - No credit (significantly incomplete implementation) (-6)
- Function bodies containing more than one statement are placed in the .h file. (-2) - Function bodies containing more than one statement are placed in the .h file. (-2)
- Missing include guards in the .h file. (Or does not declare them correctly) (-1) - Missing include guards in the .h file. (Or does not declare them correctly) (-1)
- Functions are not well documented or are poorly commented, in either the .h or the .cpp file. (-1) - Functions are not well documented or are poorly commented, in either the .h or the .cpp file. (-1)