Programming Assignments
We will do five programming assignments. Each programming assignment takes up 10% of your total grade.
- Assignment 1: Directory listing (due: 9/29)
- Assignment 2: Memory management (due: 10/20)
- Assignment 3: Buffer overflow (due: 11/07 11:59am)
- Assignment 4: Web server (due: 11/24)
- Assignment 5: Security (due: 12/15)
Assignment Submission (Important)
Use the KLMS to submit your assignments. (Link will be announced at KLMS.) Your submission should be one gzipped tar file whose name is YourStudentID_assign#.tar.gz. For example, if your student ID is 20231234, and it is for assignment #1, please name the file as 20231234_assign1.tar.gz.
To create the .tar.gz, first move all your files to the directory (20231234_assign1).
Then, move to your directory 20231234
Create a .tar.gz file by the 'tar' command like
Then, you'll see 20231234_assign1.tar.gz. If you want to decompress and release the files in it (in a different directory),
Ethics Document (Important)
For every assignment submission, please fill out and submit the pdf version of this document that pledges your honor that you did not violate any ethics rules required by this course and KAIST. You can either scan a printed version into a pdf file or make the Word document into a pdf file after filling it out.
Please sign on the document and submit it along with your other assignment files, or we won't grade your assignment.
Late Submission
You can submit your assignment late with the following penalty.
- 95% of the full credit up to 1 hour late,
- 80% of the full credit up to 24 hours late,
- 0% of the full credit beyond 24 hours late.
Important:
- Note that we do not accept late submission for the last assignment (assignment 5).
Collaboration Policy
Please refer to the course policy page.
Coding Style
Good coding style will be one criterion for grading each assignment. Please make sure your code has proper indentation and descriptive comments. At the start of each file, please add your name, student ID, and the description of the file. Make sure not to leak any memory and check/handle every return value of function calls.
Assignment Grading
Your submission will be graded on one of the Lab machines (eelabg12) for the course. You are free to use other machines for coding and debugging, but please make sure to compile and test your final version on the Lab machines (eelabg12). In a rare case, library mismatch or O/S stack difference (Solaris vs. Linux) can bypass some of your bugs, but they can actually show up on the Lab machines while grading. In order to avoid this last-minute surprise, please test on Lab machines before submitting your work.
We will use an automated program for scoring. And it works similar below practice in assignments. So you can check your functionality using diff command.
Fix a small mistake
Because we used an automatic grading system, trivial mistake in your submission may cause huge amount of deduction in your assignment score. For such exceptional circumstances, you can request changes and get modified grading at the TA's discretion. You will get 5% amount of deduction from your total score. Note that once submitted no algorithm change to the code is allowed and you cannot propose any changes to the submitted code.