This unit is a second unit in databases, and looks at the design and implementation issues of database management systems. Record, file and index structures are dealt with at the basic level. Higher level details of consistency, atomicity and durability are introduced along with modern trends in databases
Objectives
Students should be familiar with basics of relational databases including SQL query language, relational data model, normalisation etc. This subject deals with more advanced topics. In physical database design we study record structures, file organisation and indexing. Students learn to build small files and indexes with example data. Various algorithms and techniques for evaluating basic SQL queries are discussed. Students calculate the execution times of simple queries. Brief details of query optimisation, with Oracle as the example, will be provided.
The ideas of transactions and their processing are introduced along with concurrency control issues. The techniques for recovery of consistent database state after the failure of a transaction, the system or the computer hardware are discussed. Security mechanisms are described in terms of the security in Oracle.
Students learn about embedded SQL. We introduce a web database language (PHP) and a programming assignment is given to be written in PHP connecting to Oracle. Other topics include distributed databases, client server architecture etc. On the successful completion of this subject students will be able to: use a procedural programming language to access a relational database system; understand client/server database management; understand query optimisation and its impact on programming; understand the database management systems recovery, concurrency, security, benchmarking, performance measurement and transaction management mechanisms; understand Oracle DBMS architecture and database management issues; understand database trends and current research directions in database management
Prerequisites
Before attempting this unit you must have satisfactorily completed
CSE9002 or CSE2132 or CSE2138
, or equivalent. You should have knowledge of
relational data model ER modelling Query Languages SQL, relational algebra, relational calculus knowledge of programming (JAVA or C or C++ etc.) Database normalisation
Unit relationships
CSE3000 is a elective unit in the undergraduate degrees and post graduate diploma as well as MAIT in Information Technology.
It is a recommended prerequisite for CSE5200.
Before attempting this unit you must have satisfactorily completed
CSE9002 or CSE2132 or CSE2138 , or equivalent. You should have knowledge of relational data model ER modelling Query Languages SQL, relational algebra, relational calculus knowledge of programming (JAVA or C or C++ etc.) Database normalisation.
Texts and software
Required text(s)
Database Systems, Connolly and Begg 3rd edition, Addison-Wesley.
Database Management Systems, Raghu Ramakrishnan and Johannes Gehrke 2nd edition, McGraw-Hill
PHP4: A beginner's guide, Bill McCarty, Osborne-McGraw-Hill
Textbook availability
Text books are available from the Monash University Book Shops. Availability from other suppliers cannot be assured. The Bookshop orders texts in specifically for this unit. You are advised to purchase your text book early.
Software requirements
Oracle DBMS and PHP server are made available from ITS
Hardware requirements
Students studying off-campus are required to have the minimum system configuration specified by the Faculty as a condition of accepting admission, and regular Internet access. On-campus students, and those studying at supported study locations may use the facilities available in the computing labs. Information about computer use for students is available from the ITS Student Resource Guide in the Monash University Handbook. You will need to allocate up to 2 hours per week for use of a computer, including time for newsgroups/discussion groups.
Recommended reading
Database Systems, Connolly and Begg 3rd edition, Addison-Wesley.
Database Management Systems, Raghu Ramakrishnan and Johannes Gehrke 2nd edition, McGraw-Hill
PHP4: A beginner's guide, Bill McCarty, Osborne-McGraw-Hill
Library access
You may need to access the Monash library either personally to be able to satisfactorily complete the subject. Be sure to obtain a copy of the Library Guide, and if necessary, the instructions for remote access from the library website.
Study resources
Study resources for CSE3000 are:
The complete lecture material and other resources are downloadable from the subject web site.
The timetable for on-campus classes for this unit can be viewed in Allocate+
Assessment
Assessment weighting
Assessment Component Max. marks Min. for pass in the subject
Programming assignment 15 7.5
Homework asgs. 3 or 4 10 5
Exams (midterm + final) 75(25 + 50) 37.5
Assessment Policy
To pass this unit you must:
To pass the subject, you must pass each of the three components - secure at least the minimum score in each component. If you get below the minimum in any component, you will fail the subject, and the final mark calculated accordingly. For example, if you get 25/70 in the exams and 30/30 in the assignments, your total will be calculated as (100*25/70 = 42 N) independent of the marks obtained in the assignments.
Lecturer may also standardise the marks keeping in view of the relative grading in the department, marking standards, relative difficulty of the tasks given etc. However, this will be for the whole class.
Your score for the unit will be calculated by:
Assessment will consist of one examination, one midterm test, one programming assignment and 3-4 problem solving assignments. The relative weight of the individual components in final grading is as follows. To pass the subject, you must pass each of the three components - secure at least the minimum score in each component. If you get below the minimum in any component, you will fail the subject, and the final mark calculated accordingly. For example, if you get 25/70 in the exams and 30/30 in the assignments, your total will be calculated as (100*25/70 = 42 N) independent of the marks obtained in the assignments.
If you pass each of the component, the total marks is calculated as the sum of the three components: Homework + prog. Assignment + (midterm + final)exam
Assessment Requirements
Assessment
Due Date
Weighting
Programming Asgn
Not known
15%
HW asgn
various
10 %
Midterm test
not known
25 %
Final exam
not known
50 %
The exam is 2 hours long and is closed book.
Exam period (S2/06) starts on 23/10/06
50 %
Assignment specifications will be made available CSE3000 unit website.
Assignment Submission
This will be specified along with the specification. Generally hardcopy of homework need be submitted to boxes, and the programming assignment will have to be provided on an electronic medium.
Extensions and late submissions
Late submission of assignments
Assignments received after the due date will be subject to a penalty. This Will be specified later.
This policy is strict because comments or guidance will be given on assignments as they are returned, and sample solutions may also be published and distributed, after assignment marking or with the returned assignment.
Extensions
It is your responsibility to structure your study program around assignment deadlines, family, work and other commitments. Factors such as normal work pressures, vacations, etc. are seldom regarded as appropriate reasons for granting extensions.
Requests for extensions must be made by talking with the lecturer in person at least two days before the due date. You will be asked to forward original medical certificates in cases of illness, and may be asked to provide other forms of documentation where necessary. A copy of the email or other written communication of an extension must be attached to the assignment submission.
Grading of assessment
Assignments, and the unit, will be marked and allocated a grade according to the following scale:
Grade
Percentage/description
HD High Distinction -
very high levels of achievement, demonstrated knowledge and understanding, skills in application and high standards of work encompassing all aspects of the tasks.
In the 80+% range of marks for the assignment.
D Distinction -
high levels of achievement, but not of the same standards. May have a weakness in one particular aspect, or overall standards may not be quite as high.
In the 70-79% range.
C Credit -
sound pass displaying good knowledge or application skills, but some weaknesses in the quality, range or demonstration of understanding.
In the 60-69% range.
P Pass
acceptable standard, showing an adequate basic knowledge, understanding or skills, but with definite limitations on the extent of such understanding or application. Some parts may be incomplete.
In the 50-59% range.
N Not satisfactory
failure to meet the basic requirements of the assessment.
Below 50%.
Assignment return
We will aim to have assignment results made available to you within two weeks after assignment receipt.
Feedback
Feedback to you
You will receive feedback on your work and progress in this unit. This feedback may be provided through your participation in tutorials and class discussions, as well as through your assignment submissions. It may come in the form of individual advice, marks and comments, or it may be provided as comment or reflection targeted at the group. It may be provided through personal interactions, such as interviews and on-line forums, or through other mechanisms such as on-line self-tests and publication of grade distributions.
Feedback from you
You will be asked to provide feedback to the Faculty through a Unit Evaluation survey at the end of the semester. You may also be asked to complete surveys to help teaching staff improve the unit and unit delivery. Your input to such surveys is very important to the faculty and the teaching staff in maintaining relevant and high quality learning experiences for our students.
And if you are having problems
It is essential that you take action immediately if you realise that you have a problem with your study. The semester is short, so we can help you best if you let us know as soon as problems arise. Regardless of whether the problem is related directly to your progress in the unit, if it is likely to interfere with your progress you should discuss it with your lecturer or a Community Service counsellor as soon as possible.
Plagiarism and cheating
Plagiarism and cheating are regarded as very serious offences. In cases where cheating has been confirmed, students have been severely penalised, from losing all marks for an assignment, to facing disciplinary action at the Faculty level. While we would wish that all our students adhere to sound ethical conduct and honesty, I will ask you to acquaint yourself with Student Rights and Responsibilities and the Faculty regulations that apply to students detected cheating as these will be applied in all detected cases.
In this University, cheating means seeking to obtain an unfair advantage in any examination or any other written or practical work to be submitted or completed by a student for assessment. It includes the use, or attempted use, of any means to gain an unfair advantage for any assessable work in the unit, where the means is contrary to the instructions for such work.
When you submit an individual assessment item, such as a program, a report, an essay, assignment or other piece of work, under your name you are understood to be stating that this is your own work. If a submission is identical with, or similar to, someone else's work, an assumption of cheating may arise. If you are planning on working with another student, it is acceptable to undertake research together, and discuss problems, but it is not acceptable to jointly develop or share solutions unless this is specified by your lecturer.
Intentionally providing students with your solutions to assignments is classified as "assisting to cheat" and students who do this may be subject to disciplinary action. You should take reasonable care that your solution is not accidentally or deliberately obtained by other students. For example, do not leave copies of your work in progress on the hard drives of shared computers, and do not show your work to other students. If you believe this may have happened, please be sure to contact your lecturer as soon as possible.
Cheating also includes taking into an examination any material contrary to the regulations, including any bilingual dictionary, whether or not with the intention of using it to obtain an advantage.
Plagiarism involves the false representation of another person's ideas, or findings, as your own by either copying material or paraphrasing without citing sources. It is both professional and ethical to reference clearly the ideas and information that you have used from another writer. If the source is not identified, then you have plagiarised work of the other author. Plagiarism is a form of dishonesty that is insulting to the reader and grossly unfair to your student colleagues.
Communication
Communication methods
Discussion groups can be found from the subject web page.
Notices
Notices related to the unit during the semester will be placed on the Notices Newsgroup in the Unit Website. Check this regularly. Failure to read the Notices newsgroup is not regarded as grounds for special consideration.
Consultation Times
Mondays 12:00 noon to 2:00 pm.
If direct communication with your unit adviser/lecturer or tutor outside of consultation periods is needed you may contact the lecturer and/or tutors at:
This person's profile is not available.
All email communication to you from your lecturer will occur through your Monash student email address. Please ensure that you read it regularly, or forward your email to your main address. Also check that your contact information registered with the University is up to date in My.Monash.
