- Preliminaries
- Lectures
- Tutorials
- Text Books
- Programming Language
- Project
- Tools
- Forming Teams
- Peer Evaluations
- Exams
- Grade Breakdown
- Participation Marks
- Appendix A: Module Principles
- Appendix B: Module Policies
- Policy on following instructions
- Policy on grading smaller/larger teams
- Policy on project work distribution
- Policy on absence due to valid reasons (e.g. MC, LOA, University events)
- Policy on email response time
- Policy on tech help
- Policy on publishing submissions
- Policy on plagiarism
- Policy on reuse
- Policy on help from outsiders
- Policy on suggested length for submissions
- Appendix C: Frequently Asked Questions
- Why the workload is so high?
- Why so much bean counting?
- Why you force me to visit a separate website instead of using IVLE?
- Why slides are not detailed enough, handouts are wordy?
- Why so much self-study?
- Why do I have to come to tutorials on time?
- What if I don’t carry around a laptop?
- Why very narrow project scope?
- Why project requirements are so vague?
- Why I’m not allowed to use my favorite OS/IDE/etc?
- Why so many submissions?
- Why not enough marks for intermediate submissions?
- Why submission requirements differ between CS2103T and CS2101?
- Appendix D: How to get help in CS2103/T
- Appendix E: Using GitHub Project Hosting
- Appendix F: What to do if there are teamwork issues