An

Assignment 1/2 Report

On
A Relational Database
Submitted
For
Pearson BTEC International Level 3 Subsidiary Diploma
I Year – I SEM
2022-2023
In
Information Technology

Submitted By
Ibrahim Suliman alzoubi

Mr. Mohammed Nadeem Momin

(Faculty in Charge)

Department of Computer Science

British Applied College, Umm Al Quwain
Contents

Producing designs for a relational database that meets client requirements...........3

Developing a relational database to meet client requirements.........................................3
Validity and Integrity of data..............................................................................6
CreatingForms................................................................................................................... 18
QUERIES..............................................................................................................................29
Calculated Fields...................................................................................................29
Reports........................................................................................................30
Testing..............................................................................................................................32
SECURITY FOR THE DATABASE.....................................................................................37
RREFERENCES...................................................................................................42
creating a relational database that satisfies customer needs.
I have suggested the following entity-relationship diagram by the requirements of the client
as stated in the scenario.
The ER diagram for Al Ain Zoo is shown above. There will be five entities in my database that
are in the rectangle box above and are similar to the following: animal, keeper, enclosure,
species details, and nutrition. The first key that will help identify records in the table is the
oval-shaped icon, which is frequently seen above and also the ones underlined. This icon
can contain attributes like AID (animal id), arrival year, and other things in the primary
animal table. the connection is further As previously said, one keeper can raise multiple
animals, and one keeper will rear multiple animals, resulting in the formation of many-to-
one cardinality. Within the diamond-shaped box, there are relationships like belonging to,
animals, reared by, consuming, and containment. Initially, I had planned to include the
number of feeds in the diet table, but since the number of meals may vary depending on the
species, like a giraffe, I've decided to move it below the animal section. There will always be
a relationship between two entities that are shaped like a diamond and should be given a
clever term, such as "bound animal belongs to certain species. detail. To keep the diagram
from looking overpopulated, some abbreviations like AID, KID, etc. are employed. Because
each contains entirely different primary components that cannot be united together, each
entity has been unbroken apart. Even my emergency room diagnosis is stored in this format
for ease of understanding, data organization, and preservation.

creating relational database designs that satisfy customer needs.

creating a relational database to satisfy client needs.

To prevent any duplications, I modified my ID as seen above because enclosure E2 has north
and west directions.
All of the tables were successfully built and imported from other sources.
Validity and Integrity of data

For M or F, I've made a lookup wizard that only accepts accurate data and is simple to use.
Since the zoo was established on January 1, 2000, I have used a validation rule to ensure
that the dates are after the establishment and before the current date.
Additionally, I've applied a validation rule to limit the number of feeds so that they make
sense; otherwise, the value would be denied.
To make database creation simple and ensure that only the right value is allowed, I set up a
lookup wizard for the keeper rank.
I selected the cascade delete option, so if I make any changes to the species id, it will
prompt me to confirm that the changes will also affect the details in the linked table.
As we have also used the cascade update related fields’ option, to make sure it works, I have
changed s10 to s1 in the species detail table and so automatically it was changed in the
animal list table as well.
To prevent needless repetition, I used a lookup wizard; as a result, diet id the as drop-down
options for all diet ids', making it simple to complete.

Enforced referential integrity links each of the five tables together and connects them.
Creating Forms
using the form wizard to create a form for the enclosure.

I can't duplicate fields, it says.

The list now includes the new data that I created.
A form was made for entering animal information.

A method to make sure the user can input the data you want is to use an input mask.
An application for a new animal was completed and entered into the database.
I verified the keeper’s date of birth to ensure that they were at least 18 years old and to
reject any erroneous information.
I made a new entry that is visible in the list above when the form for keeper entry data was
produced (tabularly).
A similar species details entry form (datasheet) was made, and a new entry was added,
expanding the list.
The values are input using the same format as the other forms on a diet entry form that was
constructed (justified).
MAIN FORM
The user can choose which item (detail) he needs to enter on the main form, which was
developed using a form design that uses buttons and text fields. He will be directed to the
entry form after pressing a specific button.
QUERIES
Query one:

All of the herbivore animals should be found by this query and be kept by Kayden.
The preceding query produced the following, which lists all herbivore animals under the
keeper "Kayden".

QUERY TWO:

This search ought to produce a female carnivore under Suki.

All of the female carnivores' animals were placed under "Suki's" care as a consequence of
the aforementioned inquiry.

Query three:

The omnivorous creatures, which are also mammals, and the animals Dave is taking care of
in an enclosure should appear in the query table above.
The search that produced the results above revealed omnivorous mammals and creatures in
the care of keeper "Dave."

Calculated Fields

The total number of years the animals have been at the zoo has been obtained using
calculated fields.
Because we thought that the zoo had opened on January 1, 2000, we utilized expression
builder to guarantee that the date entered had to be greater than and less than today's
date.
Reports
The report for the mammals that are omnivores under the keeper Dave is shown above.
Both the layout view and the design view are visible.
The table-based reports for the keeper details are shown here.

Testing
 FORMS WERE CREATED AND TESTED SUCCESSFUL

THE VALIDITY AND INTEGRITY OF DATA TESTING WERE SUCCESSFUL.

THE VALIDATION RULE WAS TESTED SUCCESSFULLY.
 REFERENTIAL TESTING WAS SUCCESSFUL.

THE CASCADE OPTION WAS TESTED SUCCESSFULLY.

QUERIES WERE CREATED SUCCESSFULLY
 THE REPORT WAS CREATED SUCCESSFULLY.

I've already entered an alphabet and two numbers, but it's still letting me put in another
two.
WE REMOVED ALL THE DUPLICATES TO ENSURE THAT THE PRIMARY KEYS CONTINUE TO BE
UNIQUE.

Testing is done for each of the things we created in this report across the entire
document.

SECURITY FOR THE DATABASE

THE ACCESS FILE MUST BE OPENED IN EXCLUSIVE, AND THEN FILE > INFO > ENCRYPT WITH
PASSWORD MUST BE SELECTED. A DATABASE PASSWORD CAN BE SET THIS WAY TO
PREVENT UNAUTHORIZED ACCESS.
REFERENCES