Database Design and Implementation Report: CQU - Fall Semester 2024

This report details the design and implementation of a database, focusing on normalization and ERDs. It includes a breakdown of the normalization process, highlighting the transition through different normal forms. The report also features an implementation section, discussing query design in Access, and the challenges faced during the process. It covers interesting aspects of the database design, such as the use of query design tools and report generation, along with discussions on complex requirements and the use of subqueries. Additionally, it includes a bibliography with relevant research papers. This report is a comprehensive overview of database design principles and practical application, offering insights into database management and development.

Running head: DATABASE DESIGN
Database Design and Implementation: A Case Study of
CQU
Name of the Student
Name of the University

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

2DATABASE DESIGN AND IMPLEMENTATION
1. Normalization
1.a. ERD:
Figure 1: The Entity Relationship Diagram
(Source: Created by Author)

3DATABASE DESIGN AND IMPLEMENTATION
1.b. Normalization Process (Dependency Diagram)
Figure 2: Dependency Diagram
(Source: Created by Author)
1. The first normal type of the database normalization process expresses that the
qualities in the first normal shape must be atomic. This implies the database traits
must not be multivalued characteristics. Subsequent to examining the chose
relations, it has been distinguished that the qualities are atomic.
2. The second normal form depicts that the database must not have any non-key
column rely more on another non-key column. This reliance is called as
incomplete reliance. The chose relations do not have any fractional dependence.
3. In request to be in third normal frame, the database must be transitive reliance
free. The transitive tolerability alludes to an uncommon reliance that make
generally refresh peculiarities.
2. Implementation Report:
Interesting things/procedures: The query design process in the access database was very
interesting. In other Database Software I had to manually write the queries. In access database I
have used the query design option. In this process I selected the tables required to run the queries

4DATABASE DESIGN AND IMPLEMENTATION
and selected the options that are appropriate. Another interesting thing is the report. I created a
query that was able to show the details of the rejected claim. I liked how easily I could create a
report based on the developed query.
Complex Requirements: Though the query was very interesting to create but it was one
of the most complex requirements. I was not familiar with the query design in the access
database. That is why I faced various issues in creating the queries. First I was not able to select
the proper tables and attributes. The main issues were creating the query 1,3 and 6. According to
my database I had to generate result from two different tables that were not linked directly. Then
I learned that access allows sub queries very special way.

5DATABASE DESIGN AND IMPLEMENTATION
Bibliography:
Nidzwetzki, J.K. and 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.
Achpal, A., Kumar, V.B. and Mahesh, K., 2016. Modeling Ontology Semantic Constraints in
Relational Database Management System. In Proceedings of the International MultiConference
of Engineers and Computer Scientists (Vol. 1).