B01DBFN212 Database Fundamentals: IPS System Design & MS Access

Verified

Added on  2022/11/17

|9
|573
|288
Project
AI Summary
This report details the design and implementation of a database system for International Parcel Service (IPS) using MS Access. It covers the logical design, represented by an ER diagram in crow’s foot notation with tables in the third normal form, and the physical implementation within MS Access. The report includes relational schema, functional dependency analysis, database implementation details (forms and queries), and a final report generated from a specific query. The queries demonstrate data retrieval and aggregation, while the form provides a user interface for data entry. The project fulfills the requirements of the IPS database system, showcasing the capabilities of MS Access for database development.
Document Page
Student ID:
Student Name:
Date:
tabler-icon-diamond-filled.svg

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
Report
Introduction
The report is explaining the database system of International Parcel Service (IPS). The logical
design and physical design both are explained in the report. The report is showing the database
report, database form and all developed queries. The logical design is developed by the ER
diagram and physical design is implemented into the MS Access database.
ER Diagram
Document Page
The ER diagram is showing the database in pictorial form. Each entity and its attributes are being
shown in the report. The ER diagram is made in the crow’s foot notation. The tables in the ER
diagram are in the third normalized form.
Relational Schema inThird Normal Form Relations
TabCustomer (FlcustomerID, FlCustomerName, Fladdress, Flphone, Flemail)
Primary Key FlCustomerID
TabItem (FlitemNumber, Flweight, Fldimensions, FlinsuranceAmount, Fldestination,
FlfinalDeliveryDate, Flinstructions)
Primary Key FlitemNumber
TabRetailCentre (FlretailCentreID, Fltype, Fladdress)
Primary Key FlretailCentreID
TabEmployee (FlemployeeID, FlemployeeName, Fladdress, Flphone, Flemail,
FlretailCentreID)
Primary Key FlemployeeID
FlretailCentreID references Tabretail_Centre (FlretailCentreID)
TabReceipt (FlitemNumber, FlreceivedDate, Flcharges, FlretailCentreID, FlemployeeID)
Primary Key FlitemNumber
FlretailCentreID references Tabretail_Centre (FlretailCentreID)
FlemployeeID references TabEmployee (FlemployeeID)
FlitemNumber references TabItem (FlitemNumber)
TabTransportation (FlscheduleNumber, FlcustomerID, Fltype, FldeliveryRoute,
FlitemNumber)
Primary Key FlscheduleNumber
FlcustomerID references TabCustomer (FlcustomerID)
FlitemNumber references TabItem (FlitemNumber)
Document Page
Functional Dependency in Retail Centre Table/ Dependency Diagram
Type RetailCentreID
Address RetailCentreID
- The table has no repeated group.
- All fields depend upon the primary key only. The primary key is single primary key. So,
there is no partial dependency in the table.
- There is no transitive dependency because all fields depend upon the primary key only.
The table is satisfying all the above mentioned rules of third normalization. Therefore, the retail
table is in third normal form.
All the tables are satisfying the same normalization rule in the database.
There is not any partial or transitive dependency in the above table. All tables are following the
same third normalization rules.
(Guru99 2016)
tabler-icon-diamond-filled.svg

Secure Best Marks with AI Grader

Need help grading? Try our AI Grader for instant feedback on your assignments.
Document Page
Database Implementation
(Access Programmers n.d.)
Item Form
Document Page
Queries
Query 1
SELECT * FROM TabEmployee WHERE RetailCentreID=1001;
Query 2
SELECT RetailCentreID, Count(employeeID) AS NumberOfEmployees FROM TabEmployee
GROUP BY RetailCentreID;
Query 3
SELECT TabEmployee.retailCentreID, TabRetailCentre.address, TabEmployee.employeeID,
TabEmployee.employeeName, TabEmployee.address, TabEmployee.phone, TabEmployee.email
FROM TabRetailCentre INNER JOIN TabEmployee ON
TabRetailCentre.retailCentreID=TabEmployee.retailCentreID;
Document Page
Report
The report is based upon the query 3 as shown below-
tabler-icon-diamond-filled.svg

Paraphrase This Document

Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
Document Page
Conclusion
The report is fulfilling all the requirements of the IPS database system which is developed in MS
Access database. MS Access database is the complete package in itself because it gives the
features to make queries, forms and reports. The report is the complete justification of all the
tasks completed for the IPS database system.
References
Guru99 (2016). Learn Database Normalization with the help of a case study. Online. Available:
http://www.guru99.com/database-normalization.html. [Accessed: 22-May-2019]
Access Programmers (n.d.). Normalizing the Table Design. Online. Available:
https://www.access-programmers.com/normalizing-the-table-design.aspx. [Accessed: 22-May-
2019]
Document Page
chevron_up_icon
1 out of 9
circle_padding
hide_on_mobile
zoom_out_icon
logo.png

Your All-in-One AI-Powered Toolkit for Academic Success.

Available 24*7 on WhatsApp / Email

[object Object]