| UNIT OUTLINES 2005 |
| home > undergraduate > Discrete Structures 227 > Discrete Structures 227 Homepage |
|
Discrete Structures 227 (230.227) 6 points / Semester 2 Handbook Description
Unit Aims The aim of this unit is to give some formal theoretical tools used in the science of computation and the engineering of software. Students will be trained in the generic attributes of problem identification, formulation and solution and the ability to apply basic knowledge of science and engineering fundamentals to real problems. Teaching Staff
Textbook Gersting. Mathematical Structures for Computer Science, 4th edition 1999 OR 5th edition, 2002. Contact Hours Contact hours for this unit are two hours of lectures and one practical class each week. To complete the work in this unit you are expected to work out-of-hours. A total average workload of 10 hours per week is a reasonable estimate. Assessment Assessment is via an in-class test mid-way through the semester, a 2-hour examination and practical work submitted weekly, that are designed to demonstrate the student's in-depth technical competence in discrete structures for computer science and software engineering. The practical work portfolio assesses students' ability to apply team work and communication skills to problem solving in discrete structures. There will be practical exercises similar to those appearing in the test and the examination. Unsatisfactory Progress
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. 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. Faculty Scaling Final assessment is subject to the Faculty Scaling Policy.
This information is correct as at 01-Jul-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: 01-Jul-2005 |