The University of Western Australia
CITS2002 Systems Programming
 

Department of Computer Science and Software Engineering

CITS2002 Systems Programming

General information about CITS2002 laboratories

Practical work is an essential component of this unit, with overall success strongly correlated to regular practice and completion of laboratory tasks. Weekly labsheets reinforce the core concepts introduced in lectures, testing students' understanding and ability to implement concise programs to simple problems. Subsequent labsheets will heavily rely on knowledge learned from earlier labsheets, and the programming projects will assume you have completed these tasks, so be sure to complete the labsheets in a timely manner. It is anticipated that you will need to work outside your allocated laboratory time in order to successfully complete the labsheets.

Laboratory sessions are not run as regimented, formal sessions. Instead, laboratory sessions provide times at which we guarantee that there will be a demonstrator there to answer questions. Further:

  • you are free to attend any lab in which there is space. In the first few weeks, you may find that your initially allocated lab is quite full, but after a couple of weeks students choose to work at different times, and there's plenty of access to lab demonstrators.
  • please keep in mind that other units also use Lab 2.03, (at Tuesday 9-11, Tuesday 2-6, and Wednesday 2-4) and may not welcome CITS2002 students at these times.
  • you do not have to attend each lab,
  • you do not have to attend any lab if you are progressing unaided,
  • you do not have to attend the same lab each week, and
  • laboratory work is not assessed, but it provides great preparation for the assessed project work.

Sessions will be held at various times throughout the week, see: UWA Timetable for CITS2002. Each laboratory session is listed to last 2 hours, and a lab demonstrator will be available to assist you with questions during that time. Note also that there are fewer available "seats" in some laboratory sessions. This is because we anticipate that many students will choose not to work in the nominated laboratory times, will choose to work in the laboratories at other times, and undertake much of their work at home or on their laptop computers.

Labsheets include questions designed for students from all experience levels. Determine your level based on your current level of experience, and how well you understand and can complete questions.

More advanced tasks are identified by one or more chillis (chilli chilli...). All students will be keeping up with the requirements of the unit if they complete all of the introductory (non-chilli) tasks each week. More advanced students, with a deeper understanding of another programming language (probably Java or Python), should aim to complete all introductory and all advanced tasks each week, even if they think a question is trivial - there may well be some important subtlety being raised by the question.

What's next?

Department of Computer Science and Software Engineering

This Page

Written by: Chris.McDonald@uwa.edu.au