ICT701 Relational Database Systems: ER Diagram, Schema & Design Req

This document presents a relational database systems project, likely for the course ICT701, focusing on the design and implementation of a database. It includes an Entity-Relationship (ER) Diagram visually representing the database structure and relationships between entities, followed by a Relational Schema that translates the ER Diagram into a set of tables with defined columns and data types. The project also outlines supplementary design requirements, such as specifying data types and lengths for various attributes (e.g., varchar for postcode, int for primary keys), and assumptions made during the design process, including relationships between entities like carers and patients, breeds and animals, and rescuers and animals. The design emphasizes data integrity through primary and foreign keys and considers factors like data storage efficiency and the need for distinct records during treatment updates. This assignment is available on Desklib, where students can access a wealth of solved assignments and study resources.

ICT701 Relational Database Systems

Table of Contents
Part A............................................................................................................................................................................................................................................ 3
ER Diagram............................................................................................................................................................................................................................... 3
Relational Schema..................................................................................................................................................................................................................... 3
Supplementary design requirements.......................................................................................................................................................................................... 4
Assumptions.............................................................................................................................................................................................................................. 4
List of Figures
Figure 1- ERD............................................................................................................................................................................................................................... 3
Figure 2- Relational Schema.......................................................................................................................................................................................................... 3

Part A
ER Diagram
Figure 1- ERD
Relational Schema
Figure 2- Relational Schema

Supplementary design requirements
The supplementary design requirements for the designing of the database are as follows:
 The data type for postcode is varchar and the length are 10. This is to avoid the allocation of extra memory.
 The primary key such as permit number, patient_id, accession_number etcetera is of data type, int. The length of these are 20 which is to avoid
allocation of extra memory.
 Most of the data are in data type varchar. Varchar facilitates easy storage of data and allows any format of data to be stored.
 The required data in the tables are the primary keys of every table.
 The foreign key is used to establish referential integrity among tables.
 All the notes are in data type text.
Assumptions
 One carer can take care of one or more patients.
 One breed can be established with only one type.
 One animal can belong to only one breed.
 One breed constitutes one or more animals.
 One animal can be rescued by one rescuer.
 One person can be rescuer to one or more animals.
 One patient has to be mentioned in the accession form.
 During the treatment, the updating has to be done and all the records should be distinct.
 The rescue suburb could be fetched from location.
 The rescue postcode could be fetched from rescue suburb.
 The permit number can be used to fetch permit name of the carers.