|
Data Structures and Algorithms (230.223)
6 points / Semester 1
Handbook Description
The official Handbook entry Unit Aims
On successful completion of this unit students will have:
- An understanding of the basic fundamentals of data structure
selection, analysis, design and application, and in-depth technical
knowledge of key abstract data types.
- The ability to undertake problem identification, formulation and
solution using ADT components for storing and retrieving data.
- The above will require the development of generic skills in
understanding, writing, and mathematically analysing the performance
of object-oriented (Java) code.
Teaching Staff
| Lecturer |
Mark Reynolds |
help223/admin223 |
| Assitant Lecturer |
Tim French |
help223/admin223 |
| Demonstrator |
Shih Ching |
help223 |
| Demonstrator |
Angel |
help223 |
Textbook
CSSE, Data Structures and Algorithms Notes, 2005
Kenneth Lambert and Martin Osborne, Java: A Framework for Program Design and Data Structures, 2nd Ed, Thomson, 2004
Recommended Reading
Sartaj Sahni, Data Structures, Algorithms, and Applications in Java, McGraw Hill, 2000
Mark Allen Weiss, Data Structures and Problem Solving Using Java, Addison-Wesley, 1998
Derick Wood, Data Structures, Algorithms, and Performance, Addison-Wesley, 1993
Contact Hours
Two hours lectures per week. Two hours scheduled laboratory per
week. One practice class per week (not compulsory).
You may attend extra laboratories, and prac classes, if there is room.
You are expected to complete work outside of scheduled
laboratory classes.
Timetable
| Type |
Time |
Day |
Location |
| Lecture |
3.00-3.45 |
Tuesday |
Geography and Geology 1.07 Woolnough Lecture Theatre |
| Lecture |
3.00-3.45 |
Thursday |
Geography and Geology 1.07 Woolnough Lecture Theatre |
| Laboratories |
various |
Wednesday-Thursday |
Laboratory 2.3 |
| Practice class |
4.00-4.45 |
Thursday |
General Purpose Building 2 G.16 - Lecture Theatre |
| Practice class(repeat) |
11.00-11.45 |
Tuesday |
General Purpose Building 2 G.16 - Lecture Theatre |
|
|
|
|
| Consult (Tim) |
10.00-12.00 |
Monday |
Rm 2.26 |
| Consult (Mark) |
1.00-2.45 |
Tuesday |
Rm 1.16 |
See the
UWA timetable for 230.223
Assessment
Assessed laboratory work tests students abilitiy to identify problems
and formulate solutions by building, testing and applying the
fundamental data structures covered in the course.
The exams/tests additionally test technical competence in the selection,
analysis, and comparison of abstract data types.
Both forms of assessment will examine the generic skills of understanding
and writing Java code. The exam and tests will additionally examine
the generic skill of mathematically analysing code performance.
The following dates are subject to change.
| Type |
%of final mark |
Dates |
| Laboratory work |
15% |
Weekly (from week 4) |
| Java test |
5% |
Thursday Week 3 |
| Mid-semester test |
5% |
Thursday Week 8 |
| Project/Programming test |
15% |
Week 11 Labs |
| Exam |
60% |
June |
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.
Scores below 35% in any two of the three assessment
components completed by the start of Week 9 (Java test, Mid-semester
test, and laboratory work due to
date) will constitute unsatisfactory progress in this unit and
warrant exclusion from the exam.
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.
Penalties Specific to this Unit
Laboratory work:
Laboratory work is intended for completion in
the week in which it is set. However, all students will be given an
automatic "extension" of at least one week after the laboratory in
which the work is set to submit the work. After this date work
submitted within one working day will receive a 1 mark penalty, and
work submitted after this time will receive zero. Extensions after
that time will not be given unless written medical evidence is
supplied showing that the student is unable to work right through
from the laboratory until the end of the default extension week.
Tests: Tests must be taken on the date and time set unless
suitable written evidence of circumstances are provided to and
approved by the lecturer prior to the time of the test
and an alternative time arranged. Otherwise a mark of zero will be recorded.
Penalties for Plagiarism in this Unit
While students are encouraged to discuss the concepts covered in
the exercise sheets, work submitted for the assessed laboratories
must be written, from scratch, by the person submitting. The
submissions will be spot-checked by sophisticated similarity checking
software. Where collusion is found all parties will receive zero,
regardless of who the original author was. More serious cases of
plagiarism or stealing may be referred to the Head of Department and
subsequently to the Dean of the Faculty.
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 14-Apr-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: 14-Apr-2005 |
