logo

Course Title and Code:.

5 Pages645 Words1 Views
   

Added on  2022-10-02

Course Title and Code:.

   Added on 2022-10-02

ShareRelated Documents
Course Title and Code:
Student Code and Name:
Lecture Name:
Course Title and Code:._1
Solution
Normalization refers to the formal process of assignment of attributes to their
relevant entities. This process is required in database design because:
- It manages and reduces data control redundancies.
- It assists in the elimination of data anomalies in which updates, deletions
insertions destroy integrity of the database.
- Normalization ensures that the database tables are logically correct.
QUESTION 1
A dependency refers to a constraint which applies or defines the relationship among
attributes of a table. It takes place in databases when data stored in same database
table primarily determines other data kept in the same relation (Coronel & Morris,
2016). Below is the dependency diagram for our given table structure for sample
professor records.
Question 2
A functional dependency can be described as the relationship between the 2
attributes of an entity especially between the primary key and another non-primary
key fields within an entity. For example, for any relation table M, field F is
functionally dependent on field N (typically the primary key), if for every valid
instance of N, the value of M uniquely identifies the value of N.
A multivalued dependency refers to a complete constraint among two sets of fields
in a table. This necessitates that particular tuples have to be presented in a table.
It is important to understand dependencies in order to perform normalization on a
database. Dependencies are built on the basis of the business rules which apply.
They follow the below rules;
- The unique key constituents are underlined shaded in a different color and
bolded.
- The arrows which are above the entities show all the required dependencies
where the arrows below the dependencies diagram will show the less
required dependencies. The less desired dependencies are not built on the
basis of the primary key (Eckstein & Schultz, 2018).
Below are the multivalued dependencies from the provided case study
PROF_RANK DEPT_CODE
Ass.prof CHEM
Course Title and Code:._2

End of preview

Want to access all the pages? Upload your documents or become a member.

Related Documents
Entity Relationship Diagram (ERD) - Assignment
|11
|1160
|139

Achieve Scheme Database Analysis and Design
|9
|2172
|56

Data Model, Normalisation, DDL and DML for Spock Bank Database
|14
|1412
|148

Database Management System | Report | Assignment
|7
|719
|50

Entity Relationship Diagram : PDF
|10
|1685
|236

Entity Relationship Diagram and Schema | Assignment
|5
|141
|54