544 views

3 Answers

Best answer
1 votes
1 votes
                  MAKE             MODEL
M1 A
M2 C
M1 B
M2 D

Now consider make--> model

make alone cannot distinguish different models

like in above example for M1 you get A as well as B not a unique make hence this is invalid.

Now consider model -->  make

given any model we can clearly tell to which make it belongs. as any model can only associate with only one make.

eg. given A we can clearly conclude that make is M1

hence model --> make is valid .

selected by
0 votes
0 votes
Model -> Make is a FD because a Make can have multiple models.
edited by
0 votes
0 votes
model → make seems to be the most correct answer. As the requirement is for each model we need a different name(make), so according to the relationship model → make, for every model we have a single name(make) and to each of this name(make) no more than 1 model can be matched as it is an m:1 relationship.

Related questions

0 votes
0 votes
0 answers
1
practicalmetal asked Oct 26, 2023
361 views
Can someone please provide me with the correct explanation for this question
0 votes
0 votes
2 answers
4
kd..... asked Apr 26, 2019
779 views
Here if check_txn contains its own attributes then during converting into a relational model where does its attributes will be placed either in account side ( strong enti...