Note: This unit is an archived version! See Overview tab for delivered versions.
INFO2120: Database Systems 1 (2017 - Semester 1)
| Unit: | INFO2120: Database Systems 1 (6 CP) |
| Mode: | Normal-Day |
| On Offer: | Yes |
| Level: | Intermediate |
| Faculty/School: | School of Computer Science |
| Unit Coordinator/s: |
Dr Jeffries, Bryn
|
| Session options: | Semester 1 |
| Versions for this Unit: | |
| Site(s) for this Unit: |
http://elearning.sydney.edu.au/) |
| Campus: | Camperdown/Darlington |
| Pre-Requisites: | INFO1003 OR INFO1103 OR INFO1903 OR INFS1000 OR DECO1012. |
| Prohibitions: | INFO2820 OR COMP5138 OR INFO2905. |
| Brief Handbook Description: | The ubiquitous use of information technology leaves us facing a tsunami of data produced by users, IT systems and mobile devices. The proper management of data is hence essential for all applications and for effective decision making within organizations. This unit of study will introduce the basic concepts of database designs at the conceptual, logical and physical levels. We will place particular emphasis on introducing integrity constraints and the concept of data normalization which prevents data from being corrupted or duplicated in different parts of the database. This in turn helps in the data remaining consistent during its lifetime. Once a database design is in place, the emphasis shifts towards querying the data in order to extract useful information. The unit will introduce different query languages with a particular emphasis on SQL, which is industry standard. Other topics covered will include the important concept of transaction management, application development with a backend database, an overview of data warehousing and OLAP. |
| Assumed Knowledge: | None. |
| Lecturer/s: |
Dr Jeffries, Bryn
|
||||||||||||||||||||||||||||||
| Timetable: | INFO2120 Timetable | ||||||||||||||||||||||||||||||
| Time Commitment: |
|
||||||||||||||||||||||||||||||
| T&L Activities: | A variety of learning situations will be employed during the unit of study, including lectures, on-line demos, tutorials, directed computer laboratory exercises, self-learning SQL exercises, assessed assignments and a small practical database project. To benefit fully from this unit it is necessary to participate fully in all aspects of the unit of study. Pre-Lecture Preparation: Introductory content will be released each week in advance of the main lecture. All students are expected to review this content and answer review questions prior to the main lecture. Independent Study: Preparatory study including introductory videos, reading reference material, attempting online homework questions and SQL tutorial questions. Project work: Group activities working on assignment projects, mostly performed outside of classes. Lectures: Attendance is expected, and students are required to take part in worksheet-based activities and in-class online questionnaires. Laboratory: Laboratory are facilitated by tutors, and expose students to hands-on use of a DBMS and other practical activities relating to assignment projects. |
Attributes listed here represent the key course goals (see Course Map tab) designated for this unit. The list below describes how these attributes are developed through practice in the unit. See Learning Outcomes and Assessment tabs for details of how these attributes are assessed.
| Attribute Development Method | Attribute Developed |
| Schema design including integrity constraints that capture business rules as part of tutorial work and online quizzes/exam. Design of database-backed application to meet user needs, in the Practical Assignment. | Design (Level 2) |
| Theory and Practice of Relational Database Management Systems, throughout the unit | Engineering/IT Specialisation (Level 2) |
| In-depth coverage of the relational data model and introduction to conceptual modelling using entity-relationship model and UML. | Maths/Science Methods and Tools (Level 2) |
| Learning of database systems and SQL editors through online documentation for the lab tasks; topics on information security and integrity as part of the lecture. | Information Seeking (Level 2) |
| The subjects covers basics of best-practices for SQL coding, schema naming conventions, database security, authorization mechanisms, and protection against SQL injection attacks. | Professional Conduct (Level 2) |
| Team assignment (with disparate members), in the practical database project assignments. | Project and Team Skills (Level 2) |
For explanation of attributes and levels see Engineering & IT Graduate Outcomes Table.
Learning outcomes are the key abilities and knowledge that will be assessed in this unit. They are listed according to the course goal supported by each. See Assessment Tab for details how each outcome is assessed.
Design (Level 2)
1. Ability to design a schema which says how information about a particular domain will be stored in a relational DBMS (given a conceptual data model); also ability to apply normalization theory to evaluate or improve a relational schema. Ability to capture business rules as integrity constraints in a database schema.
Engineering/IT Specialisation (Level 2)
2. Understanding of the concept of a DBMS: differences from other ways to store and share data; DBMS role in organizations; the types of work done with a DBMS.
3. Ability to work with data stored in a relational database management system (understand table definitions including integrity constraints, extract information through SQL queries, modify information through SQL queries, use views and permissions for security)
4. Experience of how application software can use data stored in a DBMS (eg a dynamic content web site) and understand the basic architectural alternatives for data management applications.
5. Understanding of the basic concepts of transaction management.
Maths/Science Methods and Tools (Level 2)
6. Understanding of the relational data model
7. Ability to connect general database concepts to both theoretical abstract formulations, and details of specific software platforms.
Professional Conduct (Level 2)
8. Understanding of the SQL mechanisms for basic concepts of data security and privacy
Project and Team Skills (Level 2)
9. Work effectively in a team with members whose skills and interests differ
| Assessment Methods: |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Assessment Description: |
* indicates an assessment task which must be repeated if a student misses it due to special consideration NOTE: All text-based written assignments make use of text-based similarity detecting software (Turnitin) DB concept exercises: Each week a set of questions will be posed on that week's topic, based on the recommended reading and supplied resources. Answers are submitted online and are mostly limited to simple formats such as multiple choice. Students can review their answers and will receive an overall score based upon their best 8 out of 10 weeks' submissions. DB design assignment: Students work together in small groups to model a database based upon a brief scenario description, generating an conceptual Entity-Relationship diagram and then mapping this to a relational model. Students then implement this database in PostgreSQL. DB application development assignment: The theme of the previous assignment is extended with the development of a client interface for the database, and the implementation of more advanced back-end features such as stored procedures and indexes. SQL: Students work through weekly online tutorials introducing increasingly sophisticated usage of SQL. Solutions are provided for each week, and the topics are assessed in an SQL quiz. Final Exam: Understanding of all of this unit`s material is reviewed in a written examination. |
||||||||||||||||||||||||||||||||||||||||||||||||
| Assessment Feedback: | SQL tutorials provide simple feedback and allow multiple attempts, and example solutions are available after the submission deadline has passed. Homework exercises include solutions after the submission deadline. Design and Application assignments are worked on progressively and draft submissions can receive formative feedback that can be used to make an improved final submission. |
||||||||||||||||||||||||||||||||||||||||||||||||
| Grading: |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Policies & Procedures: | IMPORTANT: School policy relating to Academic Dishonesty and Plagiarism. In assessing a piece of submitted work, the School of IT may reproduce it entirely, may provide a copy to another member of faculty, and/or to an external plagiarism checking service or in-house computer program and may also maintain a copy of the assignment for future checking purposes and/or allow an external service to do so. Other policies See the policies page of the faculty website at http://sydney.edu.au/engineering/student-policies/ for information regarding university policies and local provisions and procedures within the Faculty of Engineering and Information Technologies. |
| Recommended Reference/s: |
Note: References are provided for guidance purposes only. Students are advised to consult these books in the university library. Purchase is not required.
|
| Online Course Content: |
University of Sydney LMS ( http://elearning.sydney.edu.au/) will be used as the main gateway to all resources, including: - Lecture slides - Lecture recordings - Introductory videos - Activity Worksheets and solutions Discussion forums and SQL tutorials are run through separate systems, but linked from the eLearning site. |
| Note on Resources: | Some in-class activities may make use of students' own devices (smart-phones, tablets or laptops). It is not required to have a device, but students are encouraged to bring one to classes if they have one. |
Note that the "Weeks" referred to in this Schedule are those of the official university semester calendar https://web.timetable.usyd.edu.au/calendar.jsp
| Week | Description |
| Week 1 | Introduction and Administrativa |
| Week 2 | Conceptual Data Modeling |
| Week 3 | The Relational Data Model |
| Week 4 | Relational Algebra and SQL |
| Week 5 | Complex SQL: Nested Queries and Grouping |
| Assessment Due: DB Design | |
| Week 6 | Schema Refinement and Data Normalization |
| Week 7 | Data Security and Integrity |
| Assessment Due: DB Schema | |
| Week 8 | DB Application Development |
| Week 9 | Transaction Management |
| Assessment Due: SQL Quiz | |
| Week 10 | Indexing and Tuning |
| Week 11 | Introduction to Data Warehousing and OLAP |
| Week 12 | Further topics in database systems |
| Assessment Due: DB Programming | |
| Week 13 | Revision |
| Exam Period | Assessment Due: Final Exam |
Course Relations
The following is a list of courses which have added this Unit to their structure.
Course Goals
This unit contributes to the achievement of the following course goals:
| Attribute | Practiced | Assessed |
| Design (Level 2) | Yes | 19.15% |
| Engineering/IT Specialisation (Level 2) | Yes | 40.94% |
| Maths/Science Methods and Tools (Level 2) | Yes | 24.79% |
| Information Seeking (Level 2) | Yes | 0% |
| Communication (Level 2) | No | 0% |
| Professional Conduct (Level 2) | Yes | 11.15% |
| Project and Team Skills (Level 2) | Yes | 4% |
These goals are selected from Engineering & IT Graduate Outcomes Table which defines overall goals for courses where this unit is primarily offered. See Engineering & IT Graduate Outcomes Table for details of the attributes and levels to be developed in the course as a whole. Percentage figures alongside each course goal provide a rough indication of their relative weighting in assessment for this unit. Note that not all goals are necessarily part of assessment. Some may be more about practice activity. See Learning outcomes for details of what is assessed in relation to each goal and Assessment for details of how the outcome is assessed. See Attributes for details of practice provided for each goal.
