Grading
Scoring criteria
- Three HW (programming) assignments: 10% + 10% + 30% = 50%
- Midterm - 15%
- Final - 35%
Look under the 'Lectures' tab for when the homeworks and exams are scheduled. Also, final letter grading will be 'relative', based on an informal ranges will be derived based on the final weighted score distribution.
Ground rules
NOTE THAT THIS COURSE INVOLVES CODING!!! If you are uncomfortable with C/C++ or programming in general, please DROP the class. "Alternate" arrangements to substitute for homeworks CANNOT be made - sorry. By missing out on HWs (where you WILL use C/C++) you'll lose 50% of your final weighted score. NO EXCEPTIONS!
Be advised that there will be a 5% penalty per day in case of late submission for the homework assignments. Please don't ask for extensions! It is up to you to budget your time wisely and get the HWs done on time. Note that almost everyone else in class carries a heavy workload as well - so granting you a penalty-free exception would not be FAIR to others.
Use the 'Assignments' link in Blackboard to submit your work - EMAIL SUBMISSIONS ARE NOT ALLOWED! Using the Blackboard for submissions protects you (and protects us - instructor and TAs) since you will have timestamped, non-repudiable 'proof' that you (hopefully) submitted the files before the deadline. Please make sure that you do submit all files properly! It is your responsibility to do so.
Exams (midterm, Final) will be "closed book". The Final will be cumulative, ie. include pre-midterm material as well, although to a smaller extent compared to post-midterm. The questions will test whether you understand the subject matter, not whether you can memorize things or calculate very quickly. If you show up for all the classes, pay attention and take notes, you should do fine.
Plagiarism: "Just do it" - NOT!
'NO PLAGIARISM' RULE: IN NO CASE IS COPYING/INCORPORATING/'BORROWING/TWEAKING/PORTING' CODE FROM ELSEWHERE ACCEPTABLE - DOING SO WILL GET YOU AN AUTOMATIC 'F' FOR THE COURSE, AND POSSIBLY MORE (EG. EXPULSION FROM YOUR DEGREE PROGRAM OR THE UNIVERSITY). YOU WILL BE RISKING YOUR FUTURE CAREER OR ACADEMIC OPPORTUNITIES BY CHEATING - DON'T DO IT!
The one line summary would be "don't plagiarize, do individual work on HWs unless specified otherwise". Note that HW3 *is* a group project, so you *do* need to collaborate on that one.
Still not convinced this is serious? Read on..
Let me reiterate: while collaboration among students is encouraged, cheating/plagiarism is not tolerated - it will get you an automatic 'F' in the class and will be reported to Student Conduct if it is severe enough. Note - this applies to tests as well! In other words, "no peeking" at others' answers while you are taking your test.
Here's more clarification of the above, as it applies to homework [the foll. text adapted from Sam Buss's class at UCSD, and it fits our requirements pretty well]:
Programming projects are individual projects. One exception to this is that the final projects can be joint if (a) you get approval from the professor ahead of time, and (b) the duties can be split among the member of the project team in such a way that each team member is working on an independent portion of the code. The latter restriction is to establish accountability for grading purposes, and to ensure that each member of the project team has well defined responsibilities..
Basic principles:
- You are expected to do your own work, program your own projects, and understand all aspects of your program.
- You may seek information and help from fellow students, TA, the instructor, outside books, resources on the Internet, etc.
- Fellow students or friends may help you debug your code, suggest fixes, etc. For debugging, you must debug the code yourself while your helper makes suggestions looking over your shoulder. If your helper suggests fixes, you must understand them and you must type them yourself.
- It is acceptable to get this kind of help (as mentioned above) on localized parts of your code. This should not be used for large portions of your code.
- Any kind of help from TAs or the instructor is permitted.
- For resources such as books or web pages - you may not pass off other's work as your own. Significant help from such resources should be acknowledged by inserting comments in your code, AND discussing it with the TA during the grading session. Again, this kind of help from these resources should only provide localized parts of your code; it should not be used for large portions of your code. If the help from these resources is too substantial, it is not allowed.
- Completely disallowed: turning in other's work as your own, copying other student's code, borrowing substantial pieces of code from any source.
Consequences of willful violations of the above guidelines are likely to be as severe as is allowed and reasonable, quite possibly including referral to the appropriate Dean.
Resources at the Student Judicial Affairs (SJACS) site include the following student-oriented publications in both viewable and printable forms (look in Resources -> Academic Resources):
- "Guide to Avoiding Plagiarism" addresses issues of paraphrasing, quotations and citations in written assignments, drawing heavily upon materials used in the university's Writing Program.
- "Understanding and Avoiding Academic Dishonesty" addresses more general issues of academic integrity, including guidelines for adhering to standards concerning examinations and unauthorized collaboration.
Also, the SCampus student handbook contains the university's Student Conduct Code and other student-related policies.
SUMMARY, YET AGAIN: DON'T PLAGIARIZE! IF YOU DO, YOU'LL GET (AND DESERVE) AN 'F' GRADE AND POSSIBLY FACE MORE CONSEQUENCES. NO APPEALS, NO EXCEPTIONS, NO KIDDING.