home > undergraduate > Databases 313  > Databases 313 Homepage

Databases 313 (231.313) 6 points / Semester 2 Handbook Description The official handbook entry for Databases 313 from the Faculty of Engineering, Computing and Mathematics. Unit Aims To learn about the current practices of database methodologies. To be able to capture the semantics of data using various data models including ER model, relational model, and object oriented model. To understand open database practices using ODBC, JDBC, object persistency, and distributed objects. To gain some practical experience in designing and implementing a database system. Teaching Staff Coordinator/Lecturer C P Tsang Rm 2.65 (Physics Building) Email it313_mail@cs.uwa.edu.au Textbook Ramakrishnan, R. and Gehrke, J., Database Management Systems, (3th ed), McGraw-Hill Contact Hours You will be required to attend 25 hours of lectures, 5 hours of tutorials and 30 hours of laboratories. To complete the work in this unit you are expected to work out-of-hours. The lectures are supported by tutorial and laboratory exercises so that a minimum of one additional hour per laboratory and tutorial hour is a reasonable estimate for this. Type Time Day Location Lecture 9-10 Tue Murdoch LT, Arts Lecture 2-3 Thu Clews LT, Physics Tute1 11-12 Tue Rm 1.24 CS Tute2 12-1 Tue Rm 1.24 CS Tute3 9-10 Wed Rm 1.24 CS Tute4 12-1 Wed Rm 1.24 CS Tute6 1-2 Thu Rm 1.24 CS Tute7 3-4 Thu Rm 1.24 CS Tute8 10-11 Fri Rm 1.24 CS Lab1 1-3 Mon Lab 2.3 Lab2 10-12 Tue Lab 2.3 Lab3 1-3 Wed Lab 2.3 Lab4 9-11 Thu Lab 2.3 Lab5 11-1 Thu Lab 2.3 Lab6 9-11 Fri Lab 2.3 Assessment Assessment for this unit is made up of three parts: a laboratory-based project, tutorial attendance and participation and a 2-hour examination. Assessment % of final mark Assessment Due Dates Tutorials 10 Monday of the week following the Tute Project 30 Friday October 17 Examination 60 November Exam Period Unsatisfactory Progress Any student who does not demonstrate satisfactory progress in this unit, as defined in the FEMS 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 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 the School´s Policy on Late Submission Projects MUST be handed in on the prescribed due date. The exact dates will be given to you on the day you receive the project specification. Projects will have deducted 10% from the final mark for each day late. All work submitted for assessment must be the individual student's own work. 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 Policy on Plagiarism.     home > undergraduate > Databases 313  > Databases 313 Homepage    This information is correct as at 25-Jul-2003, 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© 2003 School of Computer Science, & Software Engineering The University of Western Australia CRICOS Provider Code: 00126G Last updated: 25-Jul-2003