|
Java 124 (230.124)
6 points / Semester 2
Handbook Description
The official Handbook entryIncompatible Units: Foundations of Programming 120
Unit Aims
The first semester unit
This unit will lay the foundation for in-depth technical competence in
using object-oriented techniques for the production of
reliable, reusable and well-documented software.
At the end of this unit, a student should have
- A basic understanding of the object-oriented model of computation,
and the significance of its fundamental features.
- An in-depth understanding of the role of objects, classes and
methods in an object-oriented program.
- The ability to identify a computational problem, and design an
appropriate collection of classes to solve the problem.
- The ability to implement their designs in well-structured and
well-documented Java.
The generic skills addressed by this unit include:
-
Ability to apply knowledge of basic science and engineering fundamentals;
-
Ability to communicate effectively, not only with engineers but also with the community at large;
-
Ability to undertake problem identification, formulation and solution.
Teaching Staff
| Co-ordinator and Lecturer: |
Wei Liu |
Room 2.18 |
| Associate Lecturer: |
Tim French |
Room 2.14 |
| Email: admin124@csse.uwa.edu.au |
Textbook
(recommended) David Barnes, Object-Oriented Programming With Java - An Introduction., ISBN 0130869007, Part One.
(recommended) David Barnes & Michael Kolling, Objects First With Java, 2nd Edition, ISBN 0-13-124933-9.
Both books will be available in the Uni Co-op bookshop by the end of July or early August 2004.
Contact Hours
With regards to formal contact hours, you will be required to attend
two lectures and one 3-hour laboratory per week. There is an optional
tutorial (listed on the University Timetable as workshop on Thursdays) each week, mainly directed at those completely new to programming.
A six-point unit is deemed to be equivalent to one quarter of a
full-time workload,
and so you will be expected to commit 10-12 hours per week to the unit,
averaged over the entire semester. Careful attention to time management
will be needed to ensure that you are not overloaded when deadlines
approach.
| Type |
Time |
Day |
Location |
| Lecture |
12-1 |
Mon |
Social Sciences Lecture Theatre |
| Lecture |
9-10 |
Fri |
Social Sciences Lecture Theatre |
| Labs |
5 during week |
Timetable |
Lab 2.05 |
| Optional Tutorial |
4-5 |
Thu |
Alexander Lecture Theatre (Arts) |
Assessment
The assessment scheme for CS124 this year consists of laboratory
work, a midterm test, a programming project and a 2hr examination held in November.
As subsequent CSSE units require both theoretical and practical competence
in Java programming, passing
this unit requires achieving a 50% overall mark, with a
minimum score of 40%
in both the final examination and the in-semester
coursework (labs and project combined). There is no minimum
requirement for the mid-term.
| Assessment |
% of final mark |
Assessment Dates |
| Laboratories |
10 |
Weeks 3 (2%), 5 (2%), 7 (3%) and 9 (3%). |
| Mid-term Test |
15 |
Week 6 (Friday) |
| Project |
15 |
Week 12 |
| Examination |
60 |
November Examination Period |
Unsatisfactory Progress
Any student who does not demonstrate satisfactory progress in this
unit, as defined in the FECM
Policy on Assessment Practices and Procedures, may be refused admission to the
final examinations. The final deadline for notification of unsatisfactory progress is the
last day of Week 10.
Penalties
The School of Computer Science and Software Engineering has adopted a policy on
minimum penalties for late items of assessment.
This is the default policy of all units unless indicated otherwise, in writing, by the
specific unit coordinator.
This policy shall apply to all items of continuous assessment, whether
submitted either physically or electronically. Immediately after the submission deadline for an item of continuous
assessment, a penalty of 20 percent will be applied PER DAY or PART THEREOF.
The minimum mark possible for late submission is zero. The
percentage is based on the item´s total contribution to the unit´s
assessment. For example, a project contributing 40% to the unit´s
assessment will incur a penalty of 8 marks for each day late until it is submitted or
a mark of zero results.
A more detailed description is given in this School´s Policy on
Late Submission. The Faculty does have an appeals procedure, the details of which can found at the Policy for Appeals.
All projects are submitted electronically. Extensions are only granted
for university-sanctioned reasons, such as medical absences for which
a medical certificate has been provided. Application for extension
should be made as early as possible to the unit coordinator.
Plagiarism
Plagiarism is broadly defined to be when any portion
of the work presented for assessment, can be attributed
to another party. The student making the submission should acknowledge
what aspects of the presented work is not directly derived by
them. For the purposes of plagiarism it is irrelevant that you
have been given permission by someone to copy their work
and present it as your own.
You are directed to the School of Computer Science and Software Engineering Policy on Plagiarism and the Faculty of Engineering,Computing and Mathematics Policy on Plagiarism.
Faculty Scaling
Final assessment is subject to the Faculty Scaling Policy.
This information is correct as at 20-Jul-2004, but is subject
to change from time to time. In particular, The University
reserves the right to change the content and/or method of
presentation and/or the method of assessment of any unit of
study, to withdraw any unit of study or programme, and/or to
vary arrangements for any programme.
Copyright© 2004
School of Computer Science, & Software Engineering
The University of Western Australia
CRICOS Provider Code: 00126G
Last updated: 20-Jul-2004 |
