300104 Database Design and Development - Western …zhuhan/current/outlines/...300104 Database Design and Development School of Computing, Engineering & Mathematics Learning Guide

300104

Database Design and Development

School of Computing, Engineering & Mathematics│Learning Guide

UNIT DETAILS

Unit Code: 300104 Unit Name: Database Design and Development

Level: 2 Contact hours per week: 4 Credit

Points: 10

Assumed Background:

Basic programming skills, including variable declaration, variable assignment, selection statement and loop structure.

STAFF

Unit Coordinator and point of f irst contact

Dr Zhuhan Jiang ER.1.04 Parramatta campus

Phone: (02) 9685 9336 Email: [email protected]

Teaching Team

Campbelltown: Dr Yi Zhou 26.1.45 Campbelltown campus


Penrith: Dr Yun Bai Y.2.16 Penrith campus


Parramatta: Dr Zhuhan Jiang See details for the unit coordinator in the above

Consultat ion Hours

Consultation hours for all lecturers are available on the unit website on vUWS (subject to alternations).

TEXTBOOK

Connolly, Thomas and Begg, Carolyn (2015). Database systems - a practical approach to design, implementation, and management (6th ed.). Pearson Education International.

EXECUTIVE SUMMARY This unit covers the database design, as well as the database queries via SQL. Each student needs to attend for each week a 2-hour lecture and a 2-hour practical. All teaching and learning resources are available on the unit website, accessible via the (smartphone-friendly) external portal at https://staff.scem.uws.edu.au/~zhuhan/current/ or via vUWS. All submissions of student work must be uploaded via the unit website.

The whole unit assessment consists of 2 major assignments to be completed individually or in a group of two students, additional exercises from the practicals to be completed individually and submitted in 2 batches, class performance for some pre-selected practicals, and a final exam a student also has to pass on its own in order to pass the unit.

All dates and schedules in this document should be used as a guide only, as they are subject to changes. Students will be advised of any changes, if any ever, as they become known.

Edition: Spring 2015 © Copyright: University of Western Sydney, 2015. No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any information storage and retrieval system, without the prior written permission from the Dean of the School of Computing, Engineering & Mathematics. Copyright for acknowledged materials reproduced herein is retained by the copyright holder. All readings in this publication are copied under licence in accordance with Part VB of the Copyright Act 1968.

Table of Contents

Table of Contents 1

1 About Database Design and Development 1 1.1 An Introduction to this Unit 1 1.2 What is Expected of You 1 1.3 Changes to Unit as a Result of Past Student Feedback 1

2 Assessment Information 2 2.1 Unit Learning Outcomes 2 2.2 Approach to Learning 2 2.3 UWS Graduate Attributes 3 2.4 Contribution to Course Learning Outcomes 3 2.5 Assessment Summary 4 2.6 Assessment Details 5

Assessment 1: Weekly Tutorial/Practicals 5 Assessment 2: Assignment 1 6 Assessment 3: Assignment 2 6 Assessment 4: Final Examination 7

2.7 General Submission Requirements 8

3 Teaching and Learning Activities 10

4 Learning Resources 11 4.1 Recommended Readings 11 4.2 Overview of Learning Resources 11 4.3 Other Resources 12

5 Important Information 13 5.1 Student responsibilities and code of conduct 13 5.2 Staff responsibilities and code of conduct 13 5.3 Links to Policies 14 5.4 Raising concerns 14

3 0 1 0 3 8 P R O G R A M M I N G P R O F I C I E N C Y

S P R I N G 2 0 1 5

1

1 About Database Design and Development

1.1 An Introduction to this Unit The main purpose of this unit is to provide students with an opportunity to gain the basic knowledge of database design and development including data modelling methods, database design techniques, database queries through the use of SQL or GUI tools, and the implementation of the database using a commercial relational database management system.

The unit also examines a number of important database concepts such as concurrency and scheduling, database administration, security and recovery. Some assessments are allowed to work in a small group of two so that students' learning and intercommunication skills are further enhanced.

This unit assumes the basic programming knowledge and skills. The practicals will be mostly based on Microsoft SQL Server for the database construction and queries. Microsoft Access will also be briefly utilized in the practicals.

This unit promotes teamwork - the two major assignments can be done in a group two.

There is no pre-requisite for this unit. However, basic programming skills, including variable declaration, variable assignment, selection statement and loop structure, are the assumed knowledge.

1.2 What is Expected of You Study Load This unit is a 10-credit point unit and will require your full and continuous attention to maintain the highest possible grades. It is expected that you will spend at least 10 hours each week (on average) which includes information sessions and all kinds of meetings. Some weeks you will spend more time on doing project activities and in other weeks the workload may be somewhat less. Attendance While attendance at the lectures is not compulsory you are strongly advised to come to the classes. Attendance to the tut/practicals may be marked and may be taken into account when if a student appeals against his/her grade. In particular, student performance during some of the practical classes will be associated with certain marks. International students should also be careful that they do not fall foul of the requirements attached to their student visas. Online Learning Requirements Unit materials will be made available on the unit’s vUWS (E-Learning) site. You are expected to consult vUWS at least twice a week, as all unit announcements will be made via vUWS. Teaching and learning materials will be regularly updated and posted online, and are accessible via the (smartphone friendly) External Portal at https://staff.scem.uws.edu.au/~zhuhan/current directly without having to go through vUWS. Special Requirements for the Unit Access to a computer at home will be desirable.

1.3 Changes to Unit as a Result of Past Student Feedback Student feedback pays a vital role in improving the quality and educational effectiveness of UWS units and in ensuring academic staff keep in touch with student needs. You are welcome to provide feedback that is related to the teaching of this unit. At the end of the semester you will be given the opportunity to complete a Student Feedback on Unit (SFU) questionnaire to assess the unit. If requested by your unit coordinator, you may also have the opportunity to complete a Student Feedback on Teaching (SFT) questionnaire to provide feedback for individual teaching staff. As a result of the student feedback, refinement on the content selection, organisation and presentation has been made to further improve the delivery of this unit.


S P R I N G 2 0 1 5

2

2 Assessment Information

2.1 Unit Learning Outcomes Upon successfully completing this unit, students will be able to:

1 Describe components of a database system, advantages and disadvantages of a database system, roles peoples play and the historical development of a database system in the context of a Relational Database Management System (RDBMS).

2 Apply basic skills in database modelling, including ER diagrams and normalization in RDBMS.

3 Explain the basic concepts of relational algebra and apply them in queries.

4 Describe the general concepts of transaction management.

5 Identify concepts in database administration.

6 Describe concepts in database security and backup.

7 Be able to define and manipulate data using structured query language (SQL)

8 Design and develop a database for a business application using a commercial database management system.

2.2 Approach to Learning This unit enhances learning through the following means: Lectures - all regular lecture notes are available on the unit website. They contain the main points and key issues for the unit, and indicate the depth of understanding expected of the students. As such, lecturers may choose to elaborate more on certain more important or fundamental concepts or techniques during the class and leave the uncovered slides to be studied by the students themselves. Some lectures will also contain a few slides at the end on the SQL statements for the completeness of the notes; they are in general expected to be read by the students again, and briefly explained by the tutors during the tutorials/practicals on the need-to basis. Tutorials/Practicals - provide students with hands-on experience working with database design and construction as well as effectively formulating queries in SQL. The tutorial part will discuss with the students some selected topics in more detail. The combination of tutorials and practicals will typically consolidate what the students have already learned in the previous week/s, with possibly some relevant additional materials as well, and will provide feedback immediately in class and in person so that students are aware of their level of understanding of the material being presented Assignments - two assignments are set to go through the main aspects of database design and development. The design process entailed by these assignments will go a long way at enhancing the students' profound understanding on the design and the use of database. Making queries in SQL is another skill to be gained by the students through these assignments. Textbook - the text provides additional detail and examples on top of what is in the lecture notes. Students should refer to it if in difficulty with a concept or technique, and should try to read through the relevant parts as much as possible. Advanced Content - There are a variety of slides or practical paragraphs marked explicitly as advanced or optional. These are meant for the students of 300941, and will not be assessed in any way for the students of 300104, although they will help students a great deal in better understanding the topics in this unit. vUWS and External Portal - all announcements and teaching materials, including all assignments, are accessible via vUWS, as well as the External Portal outside vUWS. All submissions must be electronic and through the submission page at the unit website. Students are required to visit the unit website for the latest announcement on a regular basis.


S P R I N G 2 0 1 5

3

Unit 300104 will share the website with the unit 300941 - Database Design and Development (Advanced).

2.3 UWS Graduate Attributes As a graduate from UWS, students should be able to demonstrate all of the subsets of the major attributes which are:

1 Command multiple skills and literacies to enable adaptable lifelong learning;

2 Demonstrate knowledge of Indigenous Australia through cultural competency and professional capacity;

3 Demonstrate comprehensive, coherent and connected knowledge

4 Apply knowledge through intellectual inquiry in professional or applied contexts

5 Bring knowledge to life through responsible engagement and appreciation of diversity in an evolving world

2.4 Contribution to Course Learning Outcomes This is a common service unit, serving dozens of courses for their respective course goals. For the contribution to the course learning outcomes related to your specific course, please consult your Course Advisor or Director of Academic Program for more details.

3 0 1 0 3 8 P R O G R A M M I N G P R O F I C I E N C Y S P R I N G 2 0 1 5

4

2.5 Assessment Summary There are four assessment items in this unit, designed to enable you to demonstrate that you have achieved the unit learning outcomes. Completion and submission of all assessment items which have been designated as mandatory or compulsory is essential to receiving a passing grade. To pass this unit you must:

- Achieve 50% or more for the overall marks. - Pass the final examination.

Assessment Item Value % Due Date ULO’s Assessed Threshold

1 Weekly Tutorial/Practicals 20% Due: Different due date for different part, see Assessment Details in the next page for the breakdown.

1,2,3,4,5,6,7,8 No

2 Assignment 1 15% Due: Friday 11/9/2015 at 8pm. 1,2,3,7 No

3 Assignment 2 15% Due: Friday 23/10/2015 at 8pm. 2,6,7,8 No

4 Final Examination 50% Due: To be advised by UWS. 1,2,3,4,5,6,7,8 Must pass

Note: Results may be moderated before you receive your results. Moderation is a process whereby the unit coordinator regulates the marking of individual markers to achieve consistency in the application of unit objectives, performance standards and marking criteria. Marks for an individual piece of assessment will not be changed after you have your results. You should note that, consistent with the Assessment Policy - Criteria and Standards-Based Assessment, the final marks for the cohort may also be adjusted if marks are very high or low or there are inconsistencies between groups. Feedback on assessment Feedback is an important part of the learning process that can improve your progress towards achieving the learning outcomes. Feedback is any written or spoken response made in relation to academic work such as an assessment task, a performance or product. It can be given to you by a teacher, an external assessor or student peer and may be given to individually or to a group of students. As a UWS student, it is your responsibility to seek out and act on feedback that is provided to you as a resource to further your learning. Feedback in this unit will be in either written or oral form, or a combination of both, and will also make full use of the class time of all the practical classes.


5

2.6 Assessment Details

Assessment 1: Weekly Tutorial/Practicals

Weighting: 20% Due: different due date for different part, see below

Submission: Online via the unit website, and in-class for the performance component

Type of Collaboart ion: Individual

Format: - Written Work (13 marks): Additional Exercises at the end of each practical need to be submitted online via

the unit website in 2 specified batches, Part 1 (5 marks) and Part 2 (8 marks), due on Mon 31 Aug 2015 for Part 1 and on Mon 12 Oct 2015, see also the Additional Exercises page at the unit website for the potential update on the due dates.

- In-class Performance (7 marks): Student practical performance will be checked/marked for 7 selected practicals, Practicals 2-6, 8,9, unless overriden later on via the Assessment Timeline page at the unit website.

Instructions

- These are composed of brief discussions on the most rudimentary database design concepts, and comprehensive hands-on practicals on the use of commercial database software to create/manage user databases and conduct pertinent database queries.

- Students will typically go through a few review, or preview on some occasions, questions on the database design concepts with the tutors in class, and then conduct practicals largely following a step by step guide. The Additional Questions prescribed at the end of each practical, which are in general very similar to those illustrated step by step earlier on in the same practical, are to be completed by each student individually in class as well as in their own time if necessary.

Resources: - All resources including the Additional Exercises page and the Assessment Timeline page are available on

the unit website.

Marking Criteria and Standards: Assessment 1

Criteria Unsatisfactory Pass Credit Dist inction High Dist inction

Concepts and techniques covered in written questions

No proper understanding

Reasonable understanding and basic techniques

Sound grasp on the concepts and techniques

Full understanding plus the effective use

Super understanding and demonstrated proficiency

Marks for in-class performance are based on whether students have reasonably successfully gone through the exercise steps prescribed in the practicals. Marks for the Additional Exercises are based on the correctness and the completeness of the student answers.


6

Assessment 2: Assignment 1

Weighting: 15% Due: Fri 11/9/2015 at 8pm

Submission: Online via the unit website Type of Collaboart ion: Individual, or group of 2 students

Format: - Document in Microsoft Word containing all answers and relevant screenshots. SQL code or scripts need to

be also kept in a separate plain text file.

Instructions

- Assignment 1 is on the basic database design and queries, and the database modelling of a prescribed mini-case with ER diagrams.

- Assignment 1 can be done either individually or in a group of 2 students. Students should seek to form a group of their own as early as possible, and the group size must not exceed 2. Students not able to, or not willing to, form an assignment group will have to complete Assignment 1 on their own.

Resources: - All resources including the solution hints (8 pages) to a sample assignment (2 pages) are available on the

unit website.









Marks for Assignment 1 are based on the correctness and the completeness of the student answers. Other details will be indicated in the text of the assignment prescription on the unit website.

Assessment 3: Assignment 2

Weighting: 15% Due: Fri 23/10/2015 at 8pm

Submission: Online via the unit website Type of Collaboart ion: Individual, or group of 2 students

Format: - Document in Microsoft Word containing all answers and relevant screenshots. SQL code or scripts need to

be also kept in a separate plain text file.

Instructions

- Assignment 2 concentrates on the logical database design and its physical implementation. - Assignment 2 aims to refine the database modelling of the mini-case in assignment 1, with the

consideration of the relational model and normalization.


7

- It also involves the use of SQL for the actual implementation and queries. Unless approved otherwise, students must continue with the existing student group they formed for assignment 1.

Resources: - All resources including the solution hints (24 pages) to a sample assignment (4 pages) are available on the

unit website.









Marks for Assignment 2 are based on the correctness and the completeness of the student answers. Other details will be indicated in the text of the assignment prescription on the unit website.

Assessment 4: Final Examination

Weighting: 50% Due: UWS Spring semeter examination period

Submission: Attend the exam in person Type of Collaboart ion: Individual

Format: 3-hour closed book examination.

Instructions

- All aspects covered in lectures and tuts/practicals, including database design in different phases, SQL, transactions, and database security and administration.

- You must bring with you an HB or B pencil, and a rubber, to mark the multiple choice question (MCQ) sheets. These sheets will be processed automatically by a machine, and therefore you must mark your MCQ properly and carefully.

Resources: - Most resources are available on the unit website, including a sample final examination paper will be made

available on the unit website at a time close to the end of the semester.










8

2.7 General Submission Requirements Submission

– All assignments must be submitted by the specified due date and time, using a completed and signed Assignment Cover Sheet provided in the last page of this document.

– Complete your assignment, attach a completed and signed Assignment Cover Sheet, and follow the individual assessment items instructions on how to submit.

Turnitin – The Turnitin plagiarism prevention system may be used within this unit. Turnitin is accessed via logging

into vUWS for the unit. If Turnitin is being used with this unit, this means that your assignments have to be submitted through the Turnitin system.

– Turnitin from iParadigms is a web-based text-matching software that identifies and reports on similarities between documents. It is also widely utilised as a tool to improve academic writing skills.

– Turnitin compares electronically submitted papers against the following: o Current and archived web: Turnitin currently contains over 24 billion web pages including

archived pages o Student papers: including UWS student submissions since 2007 o Scholarly literature: Turnitin has partnered with leading content publishers, including library

databases, text-book publishers, digital reference collections and subscription-based publications (e.g. Gale, Proquest, Emerald and Sage)

– Turnitin is used by over 30 universities in Australia and is increasingly seen as an industry standard. It is an important tool to assist students with their academic writing by promoting awareness of plagiarism

Self-Plagiarising – You are to ensure that no part of any submitted assignment for this unit or product has been submitted by

yourself in another (previous or current) assessment from any unit, except where appropriately referenced, and with prior permission form the Lecturer/Tutor/Unit Co-ordinator of this unit.

Late Submission – If you submit a late assessment, without receiving approval for an extension of time, (see next item), you

will be penalised by 10% per day for up to 10 days. In other words, marks equal to 10% of the assignment’s weight will be deducted from the mark awarded.

– For example, if the highest mark possible is 50, 5 marks will be deducted from your awarded mark for each late day.

– Saturday and Sunday are counted as one calendar day each. – Assessments will not be accepted after the marked assessment task has been returned to students. – This is consistent with Clause 51 of the University of Western Sydney’s Assessment Policy – Criteria and

Standards-Based Assessment.

Extension of Due Date for Submission – It is expected that you submit your assignments on time. You are expected to manage the balance

between your studies and other activities (employment, family life, etc). Extensions are only granted in EXCEPTIONAL CIRCUMSTANCES.

– Should there be any extenuating circumstance or illness that leads to the absence from an in-class assessment or late submission of other assessment items, the student must notify the unit coordinator via such as email within the first 12 hours of being able or fit to conduct such a communication. Otherwise the student will be deemed to have forfeited their appeal for the absence or late submission.

– To accompany any extension request, a student needs to submit the supporting evidences such as a medical certificate from a doctor. Moreover, a student needs to submit his or her assessment work that has already been part ial ly done in i ts whatever present form. This will register the extent of efforts that have already been made by the student prior to the misadventure or illness.

– To submit the supporting evidences like a medical certificate, and the current state of the partially-completed assessment item, please use the student dropbox hyperlink at the schedule page of the unit website or directly via the URL https://staff.scem.uws.edu.au/cgi-bin/cgiwrap/zhuhan/suite/dropbox.pl. Once uploaded, email the unit coordinator for the actual extension request, citing the uploaded


9

supporting evidences. The actual extension request can be either in the exact form of http://www.uws.edu.au/__data/assets/pdf_file/0004/118273/ARO_00205_0515_Request_for_Extension_WEB.pdf or written in some way to the same effect.

– Please beware that anything uploaded via this dropbox cannot be overwritten. Therefore additional items, if any, must bear different file names.

– Submit the Request for Extension as early as you can, because it may not be granted. If it is not granted, and you submit your assignment after the due date, penalties will apply.

– An application for an extension does not automatically mean that an extension will be approved. – Your unit coordinator will advise the outcome of your request for an extension via your UWS student

email address, as soon as is practicable. The unit coordinator may contact you to discuss the matter further, if necessary.

– If your Request for Extension is not granted you will have to submit the assignment on time and, if you do not, you will be penalised by losing marks for each calendar day that the assignment is overdue

Resubmission Resubmission of assessment items will not normally be granted if requested.

Application for Special Consideration It is strongly recommended that you attend all scheduled learning activities to support your learning. If you have suffered misadventure, illness, or you have experienced exceptional circumstances that have prevented your attendance at class or your completion and submission of assessment tasks, you may need to apply for Special Consideration via the UWS website. http://www.uws.edu.au/currentstudents/current_students/services_and_facilities/special_consideration2 or the Student Centre. Special Consideration is not automatically granted. It is your responsibility to ensure that any missed content has been covered. Your lecturer will give you more information on how this must be done.


10

3 Teaching and Learning Activities

Wk Date Topics or Notes Chapters Practicals 1 20/7- introduction to databases; file systems vs DBMS ( pdf ) 1 n/a 2 27/7- components of DBMS; ANSI/SPARC 3 level architecture,

database environment ( pdf ) 1, 2.1, 2.4 [P1]

3 3/8- overview of (and insights in) database design, intuitive table breaking, SQLite ( pdf )

skim 2.3, 12.1-12.6, 4.1-4.2

[P2]

4 10/8- basics of ER modelling, relational model, sets and Cartesian products ( pdf )

2.3, 12.1-12.6, 4.1-4.2 [P3]

5 17/8- relational model, relational algebra, SQL to create tables and insert records ( pdf )

4.3, 5.1.1-5.1.2, 12.2, 7.3.2, 6.3.10

[P4]

6 24/8- ER modelling; enhanced ER models; SQL to query (basics on SELECT, IN, LIKE, logical operators) ( pdf ) (addit ional exercises - part 1 due)

6.1-6.3.1, 12, optional: 11

[P5]

7 31/8- database design methodology; simple table joins in SQL ( pdf ) 10.1-10.6, 16, 17, 5.1.3, 6.3.7

[P6]

8 7/9- update anomalies; functional dependencies; lossless-join, aggregate functions and multiple table joins in SQL ( pdf ) (assignment 1 due)

14.1-14.4, 6.3.3 [P7]

9 14/9- INTRA-SESSION BREAK 10 21/9- normalisation process; 1NF to 3NF; create views in SQL ( pdf ) 14.5-14.9, 7.4 [P8] 11 28/9- case study: problem to 3NF relations; use of subqueries;

Transact SQL ( pdf ) 16, 17, 6.3.5-6.3.6 [P9]

12 5/10- database security and threats; RAID; data and database administration; constraints, inner/outer joins, and set operations in SQL ( pdf ) Monday is Labour Day - students on Monday classes are to self-study the lecture notes and/or the practical. (addit ional exercises - part 2 due)

20.1-20.2, 20.6, 6.3.7-6.3.10 holiday treat: past exam

[P10]

13 12/10- transation support; concurrency anomalies; serialisability; recoverable schedules; concurrency control techniques; locking and timestamping ( pdf )

22.1-22.2.5 [P11] sample exam

14 19/10- unit revision and sample exercises ( these slides will NOT be published!) (assignment 2 due)

all material already studied

[P12]

*The above timetable should be used as a guide only, as it is subject to change. Students will be advised of any changes as they become known.


S P R I N G 2 0 1 5

11

4 Learning Resources

4.1 Recommended Readings

Textbook Connolly, Thomas and Begg, Carolyn (2015). Database systems - a practical approach to design, implementation, and management (6th ed.). Pearson Education International.

Addit ional Reading List

To be provided by the UWS Library during the semester – they are very much optional.

Online Resources

Available via the unit website.

Literacy and/or numeracy resources

N/A

4.2 Overview of Learning Resources Resources How to Engage with the Resources External Portal – https://staff.scem.uws.edu.au/~zhuhan/current.

Lectures/Textbooks/Reading List

– Read the recommended chapters and lecture notes relevant to the topics. – Ensure the theory match your assumptions. – Summarise the contents of each topic and incorporate material from lectures and tutorials.

Teaching Team – Attend the tutorials and be prepared to participate. – Attend the lectures so you understand the topic of the week and any additional materials not

covered in the textbook. – If you have any questions about the unit, please check with the tutor, lecturer or unit

coordinator. – Consultation session times and locations are on the inside front page of this learning guide. – You may also ask questions on the unit vUWS discussion board.

vUWS – All unit materials (lectures, pre-readings and assessment) are available on vUWS. Check vUWS regularly to find information on unit updates, Discussion Board, links to useful websites, audio files and interesting seminars.

– Maintain contact on the discussion board as a way of sharing ideas and clarifying any concepts and theories that are important to your understanding.

– Review the discussion board to see if messages have been posted about the assessment or feedback from the assessment.

Library – See the library home page to get help from a librarian http://library.uws.edu.au – The Library Search Box is a great search engine that will help you to find references for

accomplishing the assignments for this unit. Please note that internet sources are discouraged and are generally not acceptable as a reference source. You should only use the online journal database available through UWS library website.

– You must use APA referencing style for this unit. If you have questions about referencing, on-line librarians can provide instant assistance http://library.uws.edu.au/citing.php.

Mathematics Education Support Hub

– MESH provides UWS students at all stages in their courses of study, with mathematics and statistics support. This website provides online resources to students who want to: - revise or ‘brush-up’ on their basic mathematical skills - understand and practice the mathematical calculations underpinning their discipline area/s - gain statistical skills for their industry

– Build your confidence in using mathematics by engaging in the activities provided by MESH. The link to their web site is http://www.uws.edu.au/mesh.


S P R I N G 2 0 1 5

12

PASS – Whether you are a top performer or could use some improvement, you will benefit from the skills and understanding gained from attending PASS. PASS sessions are facilitated by senior students who have excelled in this unit. Many students each year find this unit challenging, and PASS has a strong record of helping those students to get through the subject. To see the PASS timetable visit the website: www.uws.edu.au/pass.

– Any students with an AIP attending PASS sessions should contact the PASS Coordinator on [email protected] to ensure necessary adjustments are in place.

4.3 Other Resources

University l i fe Find out about life outside the lecture theatre – news and events, services and facilities, career information and more! http://www.uws.edu.au/currentstudents/current_students/services_and_facilities

E-Learning Check your vUWS sites regularly for unit announcements and to keep up with online discussions. If you do not have access to vUWS please contact e-learning on https://vuws.uws.edu.au/

Disabil i ty Service

Students with a disability should visit: http://www.uws.edu.au/currentstudents/current_students/getting_help/disability_services

Course and unit rules

This site provides information on pre-requisites, co-requisites and other matters concerning how your course is structured. http://www.uws.edu.au/currentstudents/current_students/managing_your_study/enrolment/course_and_unit_rules

Policies This site includes the full details of policies that apply to you as a UWS student. http://www.uws.edu.au/policies/a-z


S P R I N G 2 0 1 5

13

5 Important Information

5.1 Student responsibilities and code of conduct

Student responsibi l i t ies

Familiarise yourself with university policies on assessment and examinations. More information, including links to the policies, can be found at section 5.3 of this Learning Guide

Ensure that you understand the requirements, including timetables, for examinations and other assessments tasks.

Ensure you read and understand the assessment requirements and note the submission dates, and seek assistance from the lecturer and/or unit coordinator when needed.

Notify relevant staff (e.g. lecturer, unit coordinator, disability adviser) as soon as possible prior to, or at the beginning of, the semester to have special requirements accommodated.

Submit your own individual and unassisted assessment work, except as otherwise permitted. Cheating, plagiarism, fabrication or falsification of data will be severely dealt with as per policy.

Behave ethically and appropriately, avoiding any action or behaviour which would unfairly disadvantage or advantage another student. Where group work is assigned, ensure that every group member has the opportunity to contribute in a meaningful way to the assignment.

Student conduct and behaviour

Attend all lectures, tutorials, practicals and workshops – not attending these classes is often the main cause of failure and low grades. Respect the needs of other students who are participating in any class activities. Pay attention in lectures, tutorials, practicals and workshops for key information on examinable material. Do not use mobile phones during the lectures, tutorials, practicals and workshops and do not have ongoing conversations with fellow students during the lecture or if another student/tutor is presenting work in any of the classes. Please use electronic devices for taking notes and other class activities, not surfing the net or checking email.

5.2 Staff responsibilities and code of conduct Academic staff will carry out their teaching responsibilities under the authority of the Dean of the School of Computing, Engineering and Mathematics. The responsibilities of staff are outlined in the following table.

Staff responsibi l i t ies

Assess students' work fairly, objectively and consistently and when in doubt consult with the unit coordinator or the discipline Director of Academic Programs.

Provide students with appropriate, helpful and explanatory feedback on all work submitted for assessment.

Make reasonable accommodation (e.g. length of time to complete) in assessment tasks and examinations for students with special requirements and to seek assistance from the Disability Advisor and Counsellor where appropriate and needed.

Ensure deadlines for the submission of examination papers to the Academic Registrar are met.

Immediately report any issues or concerns related to student academic and non-academic misconduct to the Director of Academic Programs.


S P R I N G 2 0 1 5

14

5.3 Links to Policies The University has a number of policies that relate to teaching and learning. Important policies affecting students include:

§ Assessment Policy § Bullying Prevention Policy and Guidelines § Enrolment Policy (includes a section on the UWS Student Email Account) § Examinations Policy § Misconduct – Student Academic Misconduct Policy (see extract below) § Misconduct – Student Non-academic Misconduct Policy (see extract below) § Review of Grade Policy § Sexual Harassment Prevention Policy § Special Consideration Policy § Teaching and Learning – Fundamental Code

There are two policies that relate to misconduct – academic and non-academic misconduct. Breaches of these policies can have very serious consequences. It is essential that you are familiar with these policies and how to avoid misconduct of any type.

What is academic misconduct? Academic misconduct may involve plagiarism, collusion or cheating. Plagiarism involves submitting or presenting work in a unit as if it were the student's own work when, in fact, it was not. Collusion includes inciting, assisting, facilitating, concealing or being involved in plagiarism, cheating or other academic misconduct with others. Cheating includes dishonest conduct (or attempted dishonest conduct) in exams. For the full definition of academic misconduct and the consequences of such behaviour, you are advised to read the Misconduct – Student Academic Misconduct Policy.

There are many resources to help you avoid academic misconduct. Library staff can help you with referencing and the Student Learning Unit can assist with academic writing and plagiarism. If you are unsure about any of your work you should also ask your tutor or lecturer for advice and feedback.

What is non-academic misconduct? Non-academic misconduct includes unlawful activities and crimes, falsifying documents (like a medical certificate or academic records), harassing other students (or staff), stealing or damaging university property (like library books or computers) and disrupting other students or staff. These are just some of the types of non-academic misconduct and while these things are rare they do happen. If you believe you have been the victim of non-academic misconduct or you are aware of any academic misconduct it is very important that you report it. You should report all matters of non-academic misconduct directly to the School of Computing, Engineering and Mathematics or Campus Security.

5.4 Raising concerns If you have a concern about this unit, please contact your lecturer or tutor in the first instance. If the matter is not resolved, then you may contact the unit coordinator (see inside front cover). If you would prefer to speak to someone else, you are advised to contact the Director of Academic Program responsible for this unit. Please note the Director of Academic Program may refer your concern to a delegate to investigate and to respond to you. The University also has a confidential Complaints Resolution Unit (see link below). You may contact this unit of the University at any time; however, we would appreciate the opportunity to resolve the complaint in the first instance. http://www.uws.edu.au/about_uws/uws/governance/complaints_management_and_resolution

School of Computing Engineering & Mathematics

ASSIGNMENT / REPORT COVER SHEET This sheet must be attached to all material being submitted for marking.

Student name:

Student number:

Unit name and number:

Tutorial day and time:

Lecturer/Tutor:

Title of Assignment:

Length: (optional)

Date due:

Date submitted:

Student Declaration (must be signed)

Declaration: q I hold a copy of this assignment if the original is lost or damaged. q I hereby certify that no part of this assignment or product has been copied from any other student’s work or from any

other source except where due acknowledgement is made in the assignment. q No part of the assignment/product has been written / produced for me by any other person except where collaboration

has been authorised by the subject lecturer/tutor concerned q I am aware that this work may be reproduced and submitted to plagiarism detection software programs for the purpose

of detecting possible plagiarism (which may retain a copy on its database for future plagiarism checking)) q I hereby certify that no part of this assignment or product has been submitted by me in another (previous or current)

assessment, except where appropriately referenced, and with prior permission from the Lecturer/Tutor/ Unit Co-ordinator for this unit.

Student signature and date:

Note: An examiner or lecturer/tutor has the right to not mark this assignment if the above declaration has not been signed.

Student Receipt

Student Number and Name:

Unit Number and Name:


ASSIGNMENTS TO BE HANDED IN AT RECEPTION MUST BE RECEIVED BY 12 NOON

zhuhan

Typewritten Text

Receipts for online submissions will be automatically generated, and should be kept by students as the proof of their submissions.

School of Computing Engineering & Mathematics GROUP ASSIGNMENT / REPORT COVER SHEET This sheet MUST BE attached to al l material being submitted for marking.

Student name: Student number:

Student name: Student

number:



number:



number:

Unit name & number:

Tutorial group:

Tutorial day and time:

Lecturer/Tutor:


Length: (optional)

Date due:

Date submitted:

Student Declaration (must be signed) Declaration: q I hold a copy of this assignment if the original is lost or damaged. q I hereby certify that no part of this assignment or product has been copied from any other student’s work or from any

other source except where due acknowledgement is made in the assignment. q No part of the assignment/product has been written / produced for me by any other person except where

collaboration has been authorised by the subject lecturer/tutor concerned q I am aware that this work may be reproduced and submitted to plagiarism detection software programs for the

purpose of detecting possible plagiarism (which may retain a copy on its database for future plagiarism checking)

q I hereby certify that no part of this assignment or product has been submitted by me in another (previous or current) assessment, except where appropriately referenced, and with prior permission from the Lecturer/Tutor/ Unit Co-ordinator for this unit.

Student signature and date:

(Submitting for group)

Note: An examiner or lecturer / tutor has the right to not mark this assignment if the above declaration has not been signed.

Student Receipt.

Student Number and Name:

Unit Number and Name:


ASSIGNMENTS TO BE HANDED IN AT RECEPTION MUST BE RECEIVED BY 12 NOON

zhuhan

Typewritten Text

Receipts for online submissions will be automatically generated, and should be kept by students as the proof of their submissions.

Documents

300104 Database Design and Development - Western …zhuhan/current/outlines/...300104 Database Design and Development School of Computing, Engineering & Mathematics Learning Guide