Databases (G6031)
Note to prospective students: this content is drawn from our database of current courses and modules. The detail does vary from year to year as our courses are constantly under review and continuously improving, but this information should give you a real flavour of what it is like to study at Sussex.
We’re currently reviewing teaching and assessment of our modules in light of the COVID-19 situation. We’ll publish the latest information as soon as possible.
Databases
Module G6031
Module details for 2024/25.
15 credits
FHEQ Level 5
Library
Thomas Conolly & Carolyn Begg: Database Systems, Addison-Wesley, latest edition.
Ramez Elmasri & Shamkant B. Navathe: Fundamentals of Database Systems, Addison-Wesley, latest edition.
Thomas Conolly & Carolyn Begg: Database Solutions (2nd edition), Addison-Wesley, 2004.
C.J.Date: An Introduction to Database Systems, Addison-Wesley, latest edition.
JDBC API: http://java.sun.com/j2se/1.4.2/docs/api/java/sql/package-summary.html
MySQL online documentation: http://dev.mysql.com/doc/index.html
Module Outline
This module provides an introduction to the concepts of Database Software, Database Design, Management, and Programming.
This includes Conceptual Database Design - using the Entity-Relationship approach -, Logical Database Design, and Physical Database Design. The module focuses on the relational data model. Students will learn how to design and implement a relational database using SQL. They will also learn how to retrieve and manipulate data via SQL queries.
Students will learn how to normalize relational databases, what normal forms there are, and how this eliminates certain anomalies based on redundancy.
Security via permission rights and indexes for tuning database queries are addressed. Students will learn how to write stored procedures and triggers using procedural SQL and how use Java Database Connectivity libraries (JDBC) to access databases in Java programs.
The exercise classes and coursework are based on a series of examples that help understand the theoretical principles. Practical experience is acquired by implementing these examples in a database management system and a graphical query browser.
Pre-Requisite
Introduction to Programming
Module learning outcomes
Demonstrate knowledge and critical understanding of established principles for data modelling, management and security in the context of relational databases.
Demonstrate the ability to apply underlying database concepts outside the context in which they were first studied. This includes the design of a database from a specification, and writing SQL code to set up, maintain and query a database.
Show an understanding of the limits of the Entity-Relationship Model and the Relational Model, and an appreciation of alternative database models.
| Type | Timing | Weighting |
|---|---|---|
| Coursework | 100.00% | |
| Coursework components. Weighted as shown below. | ||
| Test | T1 Week 11 (2 hours) | 100.00% |
Timing
Submission deadlines may vary for different types of assignment/groups of students.
Weighting
Coursework components (if listed) total 100% of the overall coursework weighting value.
| Term | Method | Duration | Week pattern |
|---|---|---|---|
| Autumn Semester | Lecture | 1 hour | 22222222222 |
| Autumn Semester | Laboratory | 1 hour | 11111111111 |
How to read the week pattern
The numbers indicate the weeks of the term and how many events take place each week.
Prof Ian Wakeman
Assess convenor
/profiles/10651
Dr Alessio Santamaria
Assess convenor
/profiles/580064
Please note that the University will use all reasonable endeavours to deliver courses and modules in accordance with the descriptions set out here. However, the University keeps its courses and modules under review with the aim of enhancing quality. Some changes may therefore be made to the form or content of courses or modules shown as part of the normal process of curriculum management.
The University reserves the right to make changes to the contents or methods of delivery of, or to discontinue, merge or combine modules, if such action is reasonably considered necessary by the University. If there are not sufficient student numbers to make a module viable, the University reserves the right to cancel such a module. If the University withdraws or discontinues a module, it will use its reasonable endeavours to provide a suitable alternative module.