Note: This unit version is currently being edited and is subject to change!
ISYS2120: Data & Information Management (2019 - Semester 2)
| Unit: | ISYS2120: Data & Information Management (6 CP) |
| Mode: | Normal-Day |
| On Offer: | Yes |
| Level: | Intermediate |
| Faculty/School: | School of Computer Science |
| Unit Coordinator/s: |
Khushi, Matloob
|
| Session options: | Semester 2 |
| Versions for this Unit: | |
| Site(s) for this Unit: |
| Campus: | Camperdown/Darlington |
| Pre-Requisites: | INFO1113 OR INFO1103 OR INFO1105 OR INFO1905 OR INFO1003 OR INFO1903 OR DECO1012. |
| Prohibitions: | INFO2120 OR INFO2820 OR COMP5138. |
| 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 the SQL database query languages, which is industry standard. Other topics covered will include the important concept of transaction management, application development with a backend database, and an overview of data warehousing and OLAP. |
| Assumed Knowledge: | Programming skills |
| Lecturer/s: |
Khushi, Matloob
|
|||||||||||||||||||||||||
| Tutor/s: | Sidath Randenikadupitige (Tutor and Teaching Assistant) | |||||||||||||||||||||||||
| Timetable: | ISYS2120 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 (`SQL Challenge`), 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. Laboratory: Laboratory and Tutorial work includes hands-on use of DBMS, an SQL online tutorial, and also practice in problem-solving related to the content. Independent Study: Work on assignments and homeworks, reading material from notes/references, etc; this should allow students to engage with the material and to integrate it into their understanding. Project Work - own time: Group Work on a practical database application project assignment (extra to time provided in Lab sessions) |
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.
(7) Project and Team Skills (Level 2)
1. Work effectively in a team with members whose skills and interests differ
(8) Professional Effectiveness and Ethical Conduct (Level 2)
2. Understanding of the SQL mechanisms for basic concepts of data security and privacy
(4) Design (Level 2)
3. 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.
(2) Engineering/ IT Specialisation (Level 2)
4. 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.
5. 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)
6. 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.
7. Understanding of the basic concepts of transaction management.
(1) Maths/ Science Methods and Tools (Level 2)
8. Understanding of the relational data model
9. Connect general database concepts to both theoretical abstract formulations, and details of specific software platforms.
| Assessment Methods: |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Assessment Description: |
1. In-tutorial quizzes. These quizzes are conducted as online tests using the University`s eLearning system, most are mulitple-choice and graded automatically; some may be marked manually. Each quiz is worth 1 point, and then the actual mark awarded for this component will be the sum of the quiz scores but capped at 9. In case of special consideration, mark adjustment will be applied, so the affected quiz is replaced by the average score from the others. 2. SQL Challenge: Milestone activities over multiple weeks to learn to write SQL queries using an online tutorial system. This is marked automatically, but is mainly for formative feedback. One point is awarded to any student who completes all the tasks. 3. SQL Quiz: Online, automatically graded quiz held in scheduled lab session, about the content studied via SQL Challenge in the weeks before. 4. Asst 1 (DB Schema Design): Group assignment, in which a given E-R diagram must be used to produce a relational schema and appropriate table creation. Group members should all be attending the same lab session. 5. Asst 2 (DB Conceptual Design): Group assignment, on modeling the data needs for a real-world scenario, solution to be expressed using an E-R diagram. Group members should all be attending the same lab session. Note: groups will be different than for asst1. 6. Asst 3 (DB Programming): Group assignment, to complete a given code skeleton, so it acts as a database application for a given database. Also, write a report on the decisions taken. Group members should all be attending the same lab session. Note: groups will be different than for asst1 and asst2. 7. Final written examination (2 hours) Penalties for lateness on assignment submission (except when covered by special permission or simple-extension): 10% of the maximimum available marks per calendar day late; maximum 5 days late (after that: 0) There may be statistically defensible moderation when combining the marks from each component to ensure consistency of marking between markers, and alignment of final grades with unit outcomes. We expect students to follow the University`s `Academic Dishonesty and Plagiarism in Coursework` policy and to always honestly submit their own results (in case of a group assignment: the result of the corresponding team). Where material has been used from a third source or person, this must be properly disclosed in the submission. If in doubt, students should contact their tutor before submission and clarify these expectations. Students should note that all submitted work (including code) may be processed through similarity detecting software. |
||||||||||||||||||||||||||||||||||||||||||||||||
| Assessment Feedback: | Some tasks are automatically marked, others are marked by hand with general class-wide feedback on a sample solution and common mistakes. Individual discussion is encouraged between student and tutor in cases of uncertainty about the grading or the correct solution. | ||||||||||||||||||||||||||||||||||||||||||||||||
| Grading: |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Policies & Procedures: | IMPORTANT: School policy relating to Academic Dishonesty and Plagiarism. In assessing a piece of submitted work, the School of Computer Science 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: |
Lecture slides (and recordings if the technology works properly), tutorial handouts, assessment instructions, and documentation, are available through the University of Sydney eLearning portal (Canvas). From the unit`s eLearning site, there will be also available a discussion forum, feedback for online quizzes and assignments. Self-study exercises on SQL are available through the School of IT`s Challenge system in Grok, reached from the Canvas site. |
| Note on Resources: | On-line manuals for the PostgreSQL database platform. |
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 ; The role of data and information management in the enterprise |
| Week 2 | The Relational Data Model; Simple SQL (SELECT-FROM-WHERE); Entity-Relationship notation for expression of a conceptual data model |
| Week 3 | Converting an ER conceptual design to a relational schema; SQL schema definition commands (including simple integrity constraints) |
| Week 4 | Relational algebra and its relationship with SQL; More Complex SQL |
| Week 5 | Conceptual Data Modelling; Extended Entity-Relationship notation; relational schema design choices for inheritance |
| Assessment Due: Asst1 (DB Schema Design) | |
| Week 6 | Evaluating and improving relational schema; Relational design theory (functional dependencies, Boyce-Codd Normal Form; schema decomposition |
| Week 7 | Views; Access control; Data Security; Triggers and sophisticated integrity mechanisms |
| Week 8 | DB Applications (architecture, technology choices, development approaches) |
| Week 9 | Transactions |
| Assessment Due: Asst2 (DB Conceptual Design) | |
| Week 10 | Analytic Processing; Data warehouse |
| Week 11 | Information models and ontologies; Data integration |
| Assessment Due: SQL Quiz | |
| Week 12 | Indexing and database system tuning |
| Assessment Due: Asst 3 (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 |
| (6) Communication and Inquiry/ Research (Level 2) | No | 0% |
| (7) Project and Team Skills (Level 2) | No | 3% |
| (8) Professional Effectiveness and Ethical Conduct (Level 2) | No | 9.9% |
| (5) Interdisciplinary, Inclusiveness, Influence (Level 2) | No | 0% |
| (4) Design (Level 2) | No | 26.9% |
| (2) Engineering/ IT Specialisation (Level 2) | No | 39.85% |
| (3) Problem Solving and Inventiveness (Level 2) | No | 0% |
| (1) Maths/ Science Methods and Tools (Level 2) | No | 20.35% |
These goals are selected from Engineering & IT Graduate Outcomes Table 2018 which defines overall goals for courses where this unit is primarily offered. See Engineering & IT Graduate Outcomes Table 2018 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.
