CA166: Computer Programming II

2009-10


Contents

Course Material

Everything in the notes below is examinable unless a note on this page indicates otherwise.
This applies even if the material was not covered in lectures. Note also that some sections of the notes are tagged "Optional" or "Advanced" but these tags do not apply to CA166.

Printing: The font sizes are adequate for printing two pages per sheet

1. Basic Java

Lectures Review of Basic Java
Program code: Console class Place the text in the same directory as your program and compile. Then use freely.
Exercises: Exercise Sheet 1.

2. Static Methods and Strings

Lectures  Static methods and Strings
Exercises: Exercise Sheet 2.

3. Classes: Introduction

Lectures Classes Introduction   
Exercises: Exercise Sheet 3.

4. Classes: Instance Methods

Lectures Instance Methods
Exercises: Exercise Sheet 4.

5. Programming with Classes

Lectures Programming with classes
Exercises: Exercise Sheet 5.

6. Arrays: Sorting and Searching

Lectures Arrays
Exercises: Exercise Sheet 6
Assessed Exercise: Assessed Exercise 1    Deadline: see Weekly Schedule

7. Exceptions

Lectures Exceptions   Only Sections 1 to 3, incl., are part of the course.

8. Text files

Lectures Text Files Text files   You may omit sections 4 and 6.
Code ConsoleReader.java
Exercises: Exercise Sheet 8

9. Recursion

Lectures Recursion
Exercises: Exercise Sheet 9
Extra Large example
Extra exercises: Exercise Sheet 9b. Solutions are in Solutions 9b. Do not look at these until you have attempted the problems yourself.

10. Binary Files

Lectures Binary Files  Section 8 on copying files is not examinable.
Exercises: Exercise Sheet 10   (A sample courses file: courses.dat  is provided for Exercise 4 -- right-click and "Save target as ...")
Assessed Exercise 2: Assessed Exercise 2 A sample inventory file: books.dat  (right-click and "Save target as ...")     Deadline: see Weekly Schedule

11. Complexity Analysis

Lectures Running Times of Methods  Sections 9 & 10 and calculating the running time of methods with nested loops is not examinable.
Exercises: Exercise Sheet 11  Solutions are in Solutions to Exercise Sheet 11. Do not look at these until you have attempted the problems yourself.

12. Object and Wrapper Classes

Lectures Object & Wrapper classes

13. Collections: Lists

Lectures Lists
Exercises: Exercise Sheet 13  

14. Collections: Sets and Maps

Lectures Sets and Maps
Exercises: Exercise Sheet 14  

15. Quicksort

Lectures Quicksort     Section 3 is not examinable. You may be asked to explain Quicksort, but you will not be asked to code it.
                                    The partitioning code is fiully examinable, however.

16. Randomly Accessed Files

Lectures Random access files 

17. Serialization

Lectures Serialization  You will not be examined on serialization.


Java on Windows

There is a quick guide to getting started with Java in the School of Computing under Windows XP. and for installing and using Java on a home computer. For  more on the basics of using Windows XP take a look at this Windows shell tutorial.

Attendance Requirements

You are expected to attend all lectures.
 

You are obliged to attend your allocated tutorials and supervised labs.


An attendance record will be kept. You must attend at the time and place allocated to you. You may not attend sessions allocated to groups other than your own, except in exceptional circumstances and with permission. If you miss tutorials or labs more than occasionally, the course team will not be sympathetic if you subsequently get into difficulties. If an illness leads to a prolonged absence, provide a medical certificate and due allowance will be made. If you find yourself not attending, you are very likely on a path that will lead to failure. Seek advice immediately, in the first instance from your course tutor, or if that is not satisfactory from the module coordinator.

Preparing for Tutorials

Tutorials  and labs provide you with practice in applying the material of the course, and a supportive environment in which you can get help with particular diffciulties. Each tutorial will cover one or two topics, usually drawn from the preceding week's lectures. You are expected to have familiarised yourself with the subject matter of the tutorials in advance; you are not expected to have mastered the material, but you should at least know your way around the associated lecture notes. The tutorial problems are published in advance so that you know what to expect.
 

You must bring the associated exercise sheet and the relevant lecture notes to the tutorial.


You are expected to spend additional study time on your own to master the material of the course.

Regulations for assessed exercises

Projects are individual

All assessed exercises are individual projects, to be carried out on your own. They are not carried out in partnership with anyone else, whether they are on the course or not. Help is available from tutorial staff.

Ethics

Assessed exercises are part of the examination process and must be treated accordingly. It is a serious offence to copy or collude in assessed exercises. The course employs copying detection software for all assessed exercises. Read the University’s policy on copying and collusion, and the School’s supplement to this Academic Ethics and Assessed Exercises. For a detailed guide specifically pertaining to programming exercises in CA166 read Frequently Asked Questions on doing assessed exercises.

Submission

Assessed exercises are not directly submitted, but rather are automatically collected as specific files from specific directories. You are given the details in each case. You receive an e-mail  shortly after the submission date  informing you that your solution has been collected. The e-mail goes to your DCU  e-mail account. If you don't appear to have got an e-mail even though you submitted an exercise, you should first make sure it has not ended up in your Spam directory. Check also your School of Computing account (this is different from your DCU account -- read more here).

Submission by e-mail or in person

It is not possible to submit your program except through the automatic system -- programs go through automatic checks (such as looking for compile time errors) that cannot be easily be done otherwise. If you make a submission by e-mail it will not be marked.

Retaining submitted work

You must not remove your program or (or otherwise do anything that might impede collection) at least until you have received the confirmation e-mail. You are strongly advised to preserve your directory and files (with date stamps) to resolve any dispute that might later arise.

Presentation

Assessed exercises must be professionally presented, with appropriate variable names, well indented to reveal structure, easily i9dentified separation between classes, lines that fit on standard A4 paper, etc.

Late submissions

Every assessed exercise has a hand-in date. There is no facility for late submissions except in serious personal circumstances, most typically a case of prolonged serious illness. An illness of a couple of days immediately prior to the deadline is not normally treated as a prolonged serious illness. If an assessed exercise is to be submitted late, you must normally get clearance in advance by e-mailing the module lecturer. You will be asked to submit evidence of the special circumstances (typically a medical cert).
 

Examinations

The module is assessed by continuous assessment (weighted at 20%) and a written exam at the end of the course (weighted at 80%). A clear pass is obtained by achieving at least 40% overall. The autumn repeats use the same continuous assessment marks as the apply for the summer exams; there is no opportunity to repeat continuous assessment for the autumn exams..

Students who repeat the module in the following year  must also repeat  the continuous assessment.

A sample exam paper from a previous year is provided.  Solutions to previous exam papers are not available.


A Java Reference will be provided in written exams. You should study this is advance and be comfortable with reading it.

Contacting Staff

The course lecturer is available for questions after every lecture, and most queries should be raised then. You should normally raise issues with your tutor during tutorial sessions; 


If a matter is so urgent that it cannot wait till the next lecture or tutorial, you may contact the relevant staff member via e-mail. Bear in mind, however, that academic staff  receive large amounts of e-mail, so please do not e-mail them without thought. Staff do not offer help with programs through e-mail; instead, ask for help at labs, tutorials, lectures, or clinics.
.

Continuous Assessment

Continuous assessment accounts for 20% of the final mark for the module. This consists of credit for work done in labs, and two assessed exercises. The second assessed exercise carries more weight than the first one. A typical breakdown is lab: 6%, Assessed Exercise 1: 6%, Assessed Exercise 2: 8%. The assessed exercises may carry additional weight when some lab sessions cannot be scheduled. 

Continuous Assessment Marks

Continuous assessment are available  here at the end of the course.