• Lectures will start on time and finish at least 10 minutes before the official finishing time (e.g., Thu 1200-1350).
• There will be several in-class activities during the lecture; you will submit them at the end of the lecture. We shall return them back to you during the next lecture.
• Lecture slides will be available on IVLE latest by Wed midnight.

Tutorials

• Tutorials start from week 3 Monday.
• Tutorial attendance is marked.
• Submitting tutorial answers will earn you participation marks.

Submitting tutorials

First, we apologize for the strict rules on naming/formatting/submission. The reason for such is because your submissions are processed in a semi-automated manner (the class is too big to do manual processing). Full compliance with the submission procedure is a must.

• All document submissions should be in an MS Word format (*.doc or *.docx, not pdf). 
• If your answers are in handwritten form, you can scan them and insert the scanned images to an MS Word file.
• You may do a tutorial question on your own or with up to 3 other course mates. They need not be from your project team. Different tutorials/activities may be done with different course mates (encouraged).
• Upload your submissions to the corresponding IVLE folder.
  
• Solution to each tutorial question is to be submitted as a separate document. Just enter your answer in the same document (containing the question)  you downloaded from IVLE.  That document contains some formatting info that is important to our automated processing system. 
•  If you did the question together with other course mates, each of you still need to submit a copy under your name. Otherwise, our processing system will not enter that solution under your name. 
• Due to the large size of the class, we cannot promise individual feedback. However,
  
• we publish your submissions after the deadline is over. This way, you can learn from each others' answers.
• you are always welcome to approach the tutor to get feedback about any specific part of your answer.
• Deadlines:
• Tutorial answers are Fri 11am in the week following the week it was released (Tutorial 1, released in week 1, will be due Fri 11am in week 2). The exact date will also appear along with the question.  

What's the point of submitting when no feedback is given?

Submitting tutorials forces you to have your own answer before you come to the tutorial instead of coming with a blank mind and simply copying the model answer.
This enhances the learning as it encourages you to be critical about the model answer and compare it with your own answer.

Publishing your tutorial/project submissions

We publish your submissions because

• it gives you all a chance to learn from each other.  
• it gives you an incentive to do a better job.
  
• it lets you judge for yourself where you stand compared to your peers.
• it discourages plagiarism.
• it increases your accountability (you should take pride in your work).

Mid-term

• 1 hour only.
• MCQ,
  
• open book exam. You may bring any printed or written materials to the exam hall. As with any other open-book exam, you will not have enough time to look up every little thing during the exam. You still have to study the material before coming to the exam.
  
• All materials in lectures for which tutorials completed before the recess are examinable. That is, lectures 1 - 4.
  
• See the schedule page for date/location/timing.
• If you miss it due to a medical reason (MC required) or due to a time-table clash (get approval *before* the mid-term), there will be a make up mid-term at a later date.

Final exam

• Open book.

• All materials covered in lectures and tutorials are examinable (unless told otherwise).
• Some exam questions may use Java code (you are allowed to get help from the invigilator if you cannot make out what such code means). You can answer using C++, Java, pseudocode. Minor syntax errors will be ignored if they are not directly relevant to the question.
  

Acknowledgments

The current teaching team wish to acknowledge the help received from past teaching team members, especially, Dr Bimlesh and Dr Yuen Jien. Some of the current materials have been derived from materials produced by past teaching team members.
We also thank SoC students Huang Yaoquan and Gary Kwong for giving/creating Firefox demos for the benefit of CS2103 students.

Edit this page (if you have permission) |

Google Docs -- Web word processing, presentations and spreadsheets.