Introduction to Computer Programming

Every year several students fail the course because of dishonest practice. Please do not be among them. You are encouraged to discuss the general aspects of a problem with others. However, anything you submit for credit must be entirely your own work and not copied, with or without modification, from any other person. If you share details of your work with anybody else then you are likely to be in breach of the University's General Course and Examination Regulations and/or Computer Regulations (both of which are set out in the University Calendar) and/or the Computer Science Department's policy. The Department treats cases of dishonesty very seriously and, where appropriate, will not hesitate to notify the University Proctor.
If you need help with specific details relating to your work, or are not sure what you are allowed to do, then contact your tutors or lecturer for advice.

Laboratory Work
Practical work is an essential part, or even the essential part, of learning to program. Laboratories are presented as on-line quizzes. Each quiz includes information panels interleaved with questions and programming exercises. The quizzes are electronically graded and the sum of all your quiz marks contributes 10% of your total course mark.

There is one laboratory quiz made available each week and the content of that laboratory is closely tied to the material covered in lectures that week. You should aim to be working on the lab material while it is being covered in lectures. You can work on the laboratory quizzes during scheduled laboratory times (see below) and/or in your own time at home or after hours in our labs.

Scheduled laboratory sessions are available for students who need the discipline of a regular time slot and/or support from course tutors. You should allocate yourself to one of the available lab streams using your personal timetable on My Timetable. Numbers in each stream are limited and it’s first-come-first-served, so if you have a strong preference for which stream you wish to attend, get in early. The laboratory streams can be thought of as “help sessions”, at which you can get help from a tutor if you need it. Being booked into a lab stream means that there is at least one time in each week when you are guaranteed to have access to tutor support. You are welcome to attend extra lab sessions provided there are free machines available.

Although lab tutors are available to help you work through the exercises when you are stuck, you should try to solve the problems yourself before calling for help. In programming there are infinitely many possible programming exercises and each one has a huge number of possible solutions. It’s not the solution to the problem that’s important; it’s the mental processes you use to get even one solution that matter. Tutors can provide only limited assistance with guiding your mental processes – ultimately you yourself have to acquire the necessary problem-solving skills.

If you don’t finish a lab quiz within a single sitting you can just log-off and then resume later. However, you must submit each quiz by its final submission date. Extensions will generally not be given except on medical grounds.

Mid-Course Quiz/Test
An online test will be administered in the second term: details to be announced. The quiz/test will be worth 15% of your course grade. The test will be an open book online examination, similar in style and question-type to the lab quizzes, but invigilated and with a strict time limit.

Programming Assignment
As explained above, the programming assignment is actually a series of stand-alone programs handed out throughout the course, starting in the third week. These will be submitted through the same online quiz system that is used in labs. Each quiz question will have a due date and unless specified otherwise in the task description late submissions will not be accepted.

Examination
The examination will be 3 hours long (to be confirmed) and will count for 55% of the final grade. Details on how the examination will be run will be advised in lectures. The date and location of examinations is determined by the Registry, not the department. They’ll be sent to you by email when they’ve been finalised. Also, they will be available through the University Course Information System. If you have an examination clash then please consult the course supervisor immediately.

Aegrotats
If factors beyond your control (such as illness or family bereavement) prevent you from completing some item of course work (including laboratory sessions), or prevent you from giving your best, then you may be eligible for aegrotat or impaired performance consideration. Details of these may be found in the University Calendar. Supporting evidence, such as a medical certificate, is normally required. If in doubt, talk to your lecturer..

The Computer Science department's grading policy states that in order to pass a course you must meet two requirements:
1. You must achieve an average grade of at least 50% over all assessment items.
2. You must achieve an average mark of at least 45% on invigilated assessment items.
If you satisfy both these criteria, your grade will be determined by the following University- wide scale for converting marks to grades: an average mark of 50% is sucient for a C- grade, an average mark of 55% earns a C grade, 60% earns a B- grade and so forth. However if you do not satisfy both the passing criteria you will be given either a D or E grade depending on marks. Marks are sometimes scaled to achieve consistency between courses from year to year.

Week 1 Introduction to the Course and Python
Week 2 Strings and Modules
Week 3 Objects, methods and lists
Week 4 Conditionals: the if statement
Week 5 Iteration (looping)
Week 6 File Processing
Week 7 Style and Program Design
Week 8 Sets and Dictionaries
Week 9 Objected Oriented Programming
Week 10 Graphical User Interfaces
Week 11 Introduction to Software Engineering
Week 12 Overflow (probably no lectures)