All problem classes will be taken from the CS1113 Problem Handbook
|3||January 29th||Set 5: Q1-Q3||solutions|
|4||February 5th||Set 5: Q4 to Q14||solutions (1/2) | solutions (2/2)|
|5||February 12th||Set 5: Q15 to Q19||solutions|
|6||February 19th||Set 7: Q1 to 7||solutions|
|7||February 26th||Set 7: Q8 to 17||solutions (1/2) | solutions (2/2)|
|8||No problem classes this week since we're ahead of lectures.|
|9||March 12th||Set 8: Q1 to 24||solutions|
|10||No problem classes due to Bank Holiday.|
|11||April 9th||Problems 9: Q1 to 17||solutions (1/2) | solutions (2/2)|
|12||No problem classes this week.|
Each week, you will be told the range of questions from the list of CS1113 problems that you are able to answer. We will look at one or two of these on the whiteboard during the problem class, and you will work through the other problems in class. You are expected to have all the problems requested each week completed for the problem class of the following week. Professor O'Sullivan will meet each student in turn to review your answers with you.
The exercises include definitions and techniques that we will use throughout the module, and similar questions may appear in the exams.
Take this Advice
Computer Science relies on practical skills needing discipline and perseverance, so attendance at, and participation in, CS1113 problem classes is a required part of the module. Attendance and participation will be monitored.
The problem classes are for your benefit, to give you a timetabled session when you can try to solve problems, and get assistance from coursemates and from teaching staff.
If you do not treat the problem classes seriously, and don't practice your skills steadily throughout the year, you will struggle badly when it comes to the exams. Every year, in this module and in other practical modules, some students don't treat the problem classes seriously. They don't attend regularly. They don't work when they do attend. They don't ask for help. They don't read the lecture notes. At the end of the year, they panic, and try to cram the module into a couple of weeks revision. They fail. They sit the repeat exam, and they fail that too. They then either come back for another year, or drop out entirely.
Don't let this happen to you. You are now at university. You will not be spoonfed material, or hand-held through the module. Instead, you have to take responsibility for your own learning. If you are not understanding something, then you need to take action to sort it out. You will need to read the notes, you will need to find other sources of information, you will need to practice, and you will need to ask for help in the problem classes. In order to pass this module, you will have to acquire skills, and if you don't acquire the skills, but rely on memorising large chunks of lecture notes, you will fail. You have to build up the skills gradually. You will know quite early on if you are not keeping up with the module. If so, do not leave it until March - sort it out now!
Attendance will be taken at problem classes.
You are expected to attend all of your allocated sessions Do not sit in silence if you are struggling. Within about the first 10 minutes of the class, you should know whether or not you understand how to do what you are being asked. If you don't, then ASK FOR HELP. Do not do work for other courses, don't browse the web, don't play games, don't read the newspaper, don't update your Facebook page, and don't send and read text messages. You can do all that in your own time, when you don't need the help of the teaching staff. You will have to put in the time in order to pass the exam, so do it now, when the help is available. Do not leave early. Do discuss the problems with the people around you - you will learn more by arguing about how to solve the problems, and explaining the material to others - but do attempt to solve them yourself. You will learn nothing if you simply copy what someone else has done.