2

3
4
5
7
As per the rules:

Derived attributes are ignored.

Composite attributes are represented by components.
Multi-valued attributes are represented by a separate table.

8
Here dependant is a weak entity. Dependant doesn’t mean anything to the problem without the
information on for which employee the person is a dependant.

9
10
11
12
13
14
15
16
17
Link:
http://172.25.103.182/kshopsearch/aspx/KShopViewSummaryMainPage.aspx?DocId=9994&C
ontentType=External Literature&MainDoc=http://172.25.103.176/Extl_Lit/xlit_9994/xlit_9994.pd
f

18
19
For Many to many relationship and ternary relationship we create separate table otherwise the
existing table(created for Entities) is modified to express the relationship.

20
For Many to many relationship and ternary relationship we create separate table otherwise the
existing table(created for Entities) is modified to express the relationship.

21
For Many to many relationship and ternary relationship we create separate table otherwise the
existing table(created for Entities) is modified to express the relationship.

22
For Many to many relationship and ternary relationship we create separate table otherwise the
existing table(created for Entities) is modified to express the relationship.

23
25
26
27
28
29
30
In above example Marks is fully functionally dependent on STUDENT# COURSE# and not on
sub set of STUDENT# COURSE#. This means Marks can not be determined either by
STUDENT# OR COURSE# alone. It can be determined only using STUDENT# AND
COURSE# together. Hence Marks is fully functionally dependent on STUDENT# COURSE#.

31
CourseName is not fully functionally dependent on STUDENT# COURSE# because subset of
STUDENT# COURSE# i.e only COURSE# determines the CourseName and STUDENT#
does not have any role in deciding CourseName. Hence CourseName is not fully functionally
dependent on STUDENT# COURSE#.

In the above relationship CourseName is partially dependent on composite attributes

STUDENT# COURSE# because COURSE# alone defines the CourseName.

32
In above example, Grade depends on Marks and in turn Marks depends on
Student#COURSE#. Hence Grade transitively depends on Student#COURSE#.

Transitive: Indirect

33
34
35
36
In relational database design it is not practically possible to have a table which is not in 1NF.

37
38
39
40
41
42
43
44
45
46
47
48
49
Eliminate Transitive dependencies

50
51
52
53