Database Design and Implementation Report: CQU Coursework Assignment

Verified

Added on  2021/05/30

|6
|436
|452
Report
AI Summary
This report details a database design and implementation project, focusing on the creation of a database using Microsoft Access. It covers key aspects such as Entity-Relationship Diagrams (ERD), normalization processes (1st, 2nd, and 3rd normal forms), and the implementation of SQL queries. The report highlights the challenges faced, particularly in writing SQL queries within the Access environment. The author found the ERD mapping and database creation to be enjoyable, while the SQL query design proved to be the most complex part of the assignment. The report also includes a bibliography of relevant sources used during the project. This assignment provides a practical application of database design principles and techniques.
Document Page
Running head: DATABASE DESIGN
Database Design and Implementation: A Case Study of
CQU
Name of the Student
Name of the University
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
1DATABASE DESIGN AND IMPLEMENTATION
Table of Contents
1. Normalization 2
1.a. ERD: 2
1.b. Normalization Process (Dependency Diagram) 3
2. Implementation Report: 3
Bibliography: 5
Document Page
2DATABASE DESIGN AND IMPLEMENTATION
1. Normalization
1.a. ERD:
Figure 1: The Visualization of ERD
Document Page
3DATABASE DESIGN AND IMPLEMENTATION
(Source: Created by Author)
1.b. Normalization Process (Dependency Diagram)
Figure 2: Dependency Visualization of Selected Entities
(Source: Created by Author)
1. The 1st normalized form of the database’s normalization activity illustrates that
the Property and Report’s attributes in the 1st normal form should not be
multivalued. The above section means that the database attributes must not
contain more than one value. After analysing the selected entities, it is discovered
that the columns of the table have single value.
2. The 2nd normalized form entails that a database should not contain any
dependency between non-key attribute dependent more on another non-key
attribute. This dependency is called as partial dependency. The selected relations
do not have any partial dependency.
3. In order to be in 3rd normal form, the database must be transitive dependency
free. The transitive decency refers to a special dependency that create mostly
update anomalies.
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
4DATABASE DESIGN AND IMPLEMENTATION
2. Implementation Report:
Interesting Things or Procedures: One of the interesting procedure is the ERD mapping.
Studying the ERD and implementing the relation was very enjoyable and I liked it. During this
process I learned more about ERD. Creating the whole access database was very interesting also.
This is the first time I created an access database. I enjoyed the entire process of creating the
database, populating the tables with data and other processes.
Complex Requirement: The most complex requirements was writing the SQL queries. I
used the SQL view to design the queries. The access queries do not run like normal database
software. Creating the Queries using SQL view was one of the toughest task of the assignment.
Document Page
5DATABASE DESIGN AND IMPLEMENTATION
Bibliography:
Day, B. (2017). Using Hierarchical Data to Manage Sample and Contact Attempts in Microsoft
Access.
Nidzwetzki, J. K., & Güting, R. H. (2016). DISTRIBUTED SECONDO: An extensible highly
available and scalable database management system. FernUniversität, Fakultät für
Mathematik und Informatik.
chevron_up_icon
1 out of 6
circle_padding
hide_on_mobile
zoom_out_icon
[object Object]