CSE-321 Programming Languages - Assignments

[ Home | Schedule | Assignments | Software | Resources | Pictures ] gla@postech Sungwoo Park

Words on academic integrity

• You may discuss assignments with other students, but what you hand in must be entirely your own work. This means that you may freely discuss your idea with your classmates (which we encourage indeed), but when it comes to writing your code or written solution, it must be entirely your own work. Hence you should never look at your classmates' code or written solution, not to mention showing yours to them, even if you have discussed assignments with them.
• You should never post code relevant to assignments to the discussion board.
• If we judge that you have copied any part of other students' code or written solution, you will be punished for cheating.
• Cheating also includes plagiarism in the sense of stealing someone else's idea.
• Your code will be compared with other students' code by a code-checking program (to be disclosed at the end of the semester).
• Do not try to outsmart the teaching staff with some, perhaps ingenious, tricks. Instead invest your time in the assignment!
• Policy on cheating:
  1. For cheating, you will receive no credit for the assignment involved.
  2. Both copier and copyee will be equally punished.
  3. For cheating once, the highest grade you can obtain in the course is C0.
  4. For cheating twice, you will be expelled from class.
  5. No exception to the above policy.

Programming assignments

• Your code should strictly follow the Standard ML style guide for this course.
• You should hand in your assignment electronically before the due date. After the due date, the hand-in directory will be closed and you will NOT be able to access it. No late submissions will be accepted.
• Grading criteria:
  • Correctness: Your program should satisfy the given specification.
  • Clarity: Your program should be easy to read, with enough documentation to help readers understand the implmentation. (But beware of unnecessarily long and useless comments!) If we fail to understand your code, you may not receive full credit for your assignment even if it works correctly.
• Grading criteria NOT applied to programming assignments:
  • Efficiency: You should strive only for the elegance, but never for the efficiency of your code (unless otherwise instructed). In particular, try to avoid using mutuable references or arrays whenever possible so that your code remains pure. You will often be tempted to exploit them in your code, but none of our assignments are designed so as to encourage their use. It is even safe to assume that if your code is not pure, you have not thought enough about the assignment!
• Your hand-in directory is /afs/postech.ac.kr/class/cse/cs321/handin/.
• Advice:
  1. Start your assignment early. Keep in mind that the hand-in directory will be closed after the due date.
  2. Spend enough time designing your code before you jump into coding. In other words, think about the problem before typing anything on your screen. It is not uncommon to see that a well-designed specification automatically writes code for you.
  3. Take advantage of the office hours of the teaching staff - they are more than willing to help you.
  4. Again, start your assignment early! Remember that no late submissions will be accepted.

Written assignments

(To be completed later.)

[ Home | Schedule | Assignments | Software | Resources | Pictures ] gla@postech Sungwoo Park