Assignment 1– Part 2 (10%)
Due date: 10.00am Monday, May 11th 2020
AIMS AND OBJECTIVES:
? to convert the ER/EER model into a relational data model;
? to implement a relational database system (using ORACLE).
This is an individual Assignment. You are not permitted to work as a group when writing this assignment.
Copying, Plagiarism: Plagiarism is the submission of somebody else’s work in a manner that gives the impression that the work is your own. The Department of Computer Science and Information Technology treats plagiarism very seriously. When it is detected, penalties are strictly imposed.
No extensions will be given: Penalties are applied to late assignments (5% of total assignment mark given is deducted per day, accepted up to 5 days after the due date only). If there are circumstances that prevent the assignment being submitted on time, an application for special consideration may be made. See Student Handbook for details. Note that delays caused by computer downtime cannot be accepted as a valid reason for a late submission without penalty. Students must plan their work to allow for both scheduled and unscheduled downtime.
This assignment is to be submitted in soft-copy (.pdf, .txt or .sql) formats using the CSE2DBF submission link on LMS by 10:00 am Monday May 11th, 2020. The submission link can be found under “CSE2DBF Assignment 1 – Part 2” on the subject’s LMS page.
? The transformation steps from your EER Model to your final tables (Task 1); Make sure to show each step of the transformation, and the final transformation tables;
? The DDL implementation for the ‘Getaway Holidays Reservation Database’ tables from Task 1 (create table statements), and the required insert statements (Task 2a and 2b respectively).
Students are referred to the Department of Computer Science and Information Technology’s Handbook and policy documents with regard to plagiarism and assignment return, and also to the section of ‘Academic Integrity’ on the subject learning guide.
1. Transform the EER model (Appendix A in the following page) to Relational tables, making sure you show all the steps. The final set of tables should contain necessary information such as table names, attribute names, primary keys (underlined) and foreign keys (in italics).
2. a) Implement the tables in the ORACLE Relational DBMS. When creating tables make sure you choose appropriate data types for the attributes and specify any null/not null or other constraints whenever applicable.
b) Write one insert statement for each of your tables using realistic data. Make sure you take into consideration all the necessary constraints.
APPENDIX A – EER Diagram