Difference between revisions of "Class Policies"

From CSE231 Wiki
Jump to navigation Jump to search
Line 1: Line 1:
 
=Academic Integrity and Citations=
 
=Academic Integrity and Citations=
 +
This is not a group project course.  You are expected to complete all assignments independently.
  
You are expected to complete all assignments, studios, and warmups independently. However, we understand that you and your fellow classmates could discuss implementations together and choose to tackle problems the same way. If this is the case, you should cite the person you talked to with comments on your code. This should take no more than two seconds and will ensure you are not accused of an academic integrity violation. Although it may seem tedious, we recommend doing this to avoid any possible issues later.
+
Any act of dishonesty (e.g. cheating, lying) will be referred to the Dean's office in Engineering Student Services.
 +
If found in violation, the student will receive an F in the course and a permanent mark on their record.
  
===Example of an Honor Pledge===
+
See the [https://wustl.edu/about/compliance-policies/academic-policies/undergraduate-student-academic-integrity-policy/ Undergraduate Student Academic Integrity Policy] for an non-exhaustive list.  If in doubt ask the Professor for clarification.
On my honor as a student, the work I am submitting is mine own.  It was created within the acceptable bounds of this course.
+
 
 +
NOTE: ''Withdrawing from the course will not prevent the academic integrity officer or hearing panel from adjudicating the case, imposing sanctions, or recommending grade penalties, including a failing grade in the course.''
 +
 
 +
CSE 131 has some [http://www.cse.wustl.edu/~cytron/cse131/Info/collaboration.shtml|good general advice on academic integrity].
 +
 
 +
==Honor Pledge==
 +
You will be required to fill out a pledge, acknowledgements, and citations file for each assignment.  To be clear: failure to fill out this pledge will not save you from an academic integrity violation.
 +
 
 +
===Example Pledge===
 +
 
 +
''On my honor as a student, the work I am submitting is mine own.  It was created within the acceptable bounds of this course.''
  
 
(You are free to use this as a pledge.)
 
(You are free to use this as a pledge.)

Revision as of 07:58, 16 January 2018

Academic Integrity and Citations

This is not a group project course. You are expected to complete all assignments independently.

Any act of dishonesty (e.g. cheating, lying) will be referred to the Dean's office in Engineering Student Services. If found in violation, the student will receive an F in the course and a permanent mark on their record.

See the Undergraduate Student Academic Integrity Policy for an non-exhaustive list. If in doubt ask the Professor for clarification.

NOTE: Withdrawing from the course will not prevent the academic integrity officer or hearing panel from adjudicating the case, imposing sanctions, or recommending grade penalties, including a failing grade in the course.

CSE 131 has some general advice on academic integrity.

Honor Pledge

You will be required to fill out a pledge, acknowledgements, and citations file for each assignment. To be clear: failure to fill out this pledge will not save you from an academic integrity violation.

Example Pledge

On my honor as a student, the work I am submitting is mine own. It was created within the acceptable bounds of this course.

(You are free to use this as a pledge.)

Attendance

You are expected to attend class (on both Mondays and Wednesdays) and you will lose points if you fail to show up more than three times. We take attendance using either clicker questions or in-class quizzes. If you are caught trying to sign in for an absent friend, we will consider this an academic integrity violation and treat it as such. If your friends ask you to do this for them, tell them you do not want an academic integrity violation on your record. If you need to be absent for more than three classes for any reason, reach out to the instructors.

Q&S Forms

There will usually be a Q&S form due before every class. We expect you to complete these before class begins. Like attendance, you will only be penalized after missing more than three Q&S forms.

Weekly Updates

Every week, you will be sent an email updating you about your progress for that week. The update will include how much credit you received on the Q&S forms, your progress on the current assignment, and any comments that TAs might have for you based on the state of your assignment. These weekly updates are only meant to help you and do not represent your final grades. For example, even if you do not get full credit on the Q&S forms because you got quiz questions wrong, as long as we see that the majority of your Q&S forms received full credit, wrong answers from genuine attempts will not be docked.

Good Faith Efforts

When assignments are first due, the instructors will review your code and send any relevant feedback to you in your weekly update. After you get your feedback, you will have one week to submit your assignment again. The second submission is the only one that is formally graded, but you are expected to put in a good faith effort into your first submission. An example of a good faith submission might be a mostly completed assignment with a couple bugs and comments for graders that detail what went wrong in your implementation. A non-good faith effort would be adding a few spaces and new lines into your code for submission.

Late Submissions

If you submit an assignment after its due date, we will accept it up to a week after the original due date. However, you will only be able to earn a maximum of 70% of the original amount of points if you choose to submit something late.

Office Hours

Click here for updated office hours.