|
Object-Oriented Programming 224 (230.224)
6 points / Semester 1
Handbook Description
The official Handbook entry Unit Aims
- To develop an
understanding of the most up-to-date, fundamental programming concepts
and techniques, the principles on which they are based, and the issues
involved in their design.
- To become proficient at designing and implementing software
solutions using several programming languages, in particular advanced
features of Java.
- The generic attributes addressed in this unit
are the following:
- The students will be able to apply
knowledge of basic science and engineering in problem solving
related to programming.
- The students will gain in-depth
technical competence in software engineering issues related to
object-oriented programming.
- The students will learn to
identify the problems in a task and formulate the solutions for
those problems.
- The students will learn to function effectively
as an individual and in multi-disciplinary and multi-cultural
teams, with the capacity to be a leader or manager as well as an
effective team member.
Teaching Staff
| Lecturer: |
Peter Jones |
Rm G.08 |
Textbook
For 2005 there are several suggestions for textbook purchase/reading.
(See the main OOP224 web-page's link "Books".)
One excellent text is (now in its 3rd edition):
An Introduction to Object-Oriented Programming, 3rd ed Tim Budd © 2002 —
Author's site
Addison-Wesley Pub Co; ISBN: 0-201-76031-2
Contact Hours
59 hours (lectures: 26 hrs; labs: 26 hrs;
plus about ½hr week online).
Lectures have an audio recording available off iLectures.
| Type |
Day |
Time |
Location |
| Lecture (45m) |
Tue |
4pm |
Ross Lect Th., Physics |
| Lecture (45m) |
Fri |
10am |
Ross Lect Th., Physics |
| Lab (110m) |
Tue |
9am |
CS Lab 2.05 |
| Lab (110m) |
Wed |
11am |
CS Lab 2.05 |
| Lab (110m) |
Wed |
3pm |
CS Lab 2.05 |
| Lab (110m) |
Thur |
1pm |
CS Lab 2.05 |
Assessment
The assessment in this unit is via individual projects that are designed to emphasize the generic attributes mentioned in the aims section. In
particular the ability to undertake problem identification, formulation
and solution will be assessed both in the programming projects and the
examination. The students' knowledge in object-oriented programming and
their ability to apply knowledge of basic science and engineering
fundamentals will be assessed both in the programming projects and in the
examination.
| Type |
% of final mark |
Dates |
| Exam |
60% |
June Examinations |
| Assessment #1 |
10% |
Week 4 |
| Assessment #2 |
10% |
Week 8 |
| Assessment #3 |
20% |
Week 12+change in 13 |
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.
For Object-Oriented Programming 230.224:
Late submissions will not be accepted without supporting medical evidence
or other extenuating circumstances approved by the Sub-Dean.
Students should consult the School's Policy on Plagiarism prior to undertaking any
assessment.
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 17-Feb-2005, 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© 2005
School of Computer Science, & Software Engineering
The University of Western Australia
CRICOS Provider Code: 00126G
Last updated: 17-Feb-2005 |
