🎓 Academic Help! Pa unlock Course hero

Status
Not open for further replies.

Hirai Momo

🅢🅞🅨
Eto po sana :

You do not have permission to view the full content of this post. Log in or register now.

Same question po pero sa Çℎḙḡḡ..

https://www.Çℎḙḡḡ.com/homework-help...ersons-successful-operation-organiz-q58675412

Thank you in advance sa tutulong 🙂
 

Answer
Relational schema.webp

 
Arcturus pa unlock po ulit please

You do not have permission to view the full content of this post. Log in or register now.

Answer


Step-by-step explanation
Why not in 1NF?

A table is in 1 NF iff:
  1. There are only Single Valued Attributes.
  2. Attribute Domain does not change.
  3. There is a Unique name for every Attribute/Column.

This table is not in 1NF because it has an attribute that is not single valued. It has several values for each cell in the column telNos.


Why not in 2NF?

A table is in the second normal form if it fulfills the following two requirements:
  1. It is in first normal form.
  2. It does not have any non-prime attribute that is functionally dependent on any proper subset of any candidate key of the relation. A non-prime attribute of a relation is an attribute that is not a part of any candidate key of the relation.

In this case, the candidate key is staffNo, branchNo since you can derive all the other attributes from these attributes.

We can see here that branchAddress is functionally dependent on branchNo, a subset of the candidate key. Since branchAddress is a non-prime attribute, this violates the 2nd condition of being in 2NF. Hence, this table is not in 2NF.


Why not in 3NF?

A table is in 3NF if and only if for each of its functional dependencies XA, at least one of the following conditions holds:
  1. X contains A (that is, A is a subset of X, meaning XA is trivial functional dependency),
  2. X is a superkey,
  3. every element of A \ X, the set difference between A and X, is a prime attribute (i.e., each attribute in A \ X is contained in some candidate key).

In this table, the candidate key is branchNo since we can derive all the other attributes from this attribute alone. We can also see that name is functionally dependent on mgrStaffNo. Since mgrStaffNo does not contain name (Rule 1), mgrStaffNo is not a superkey (Rule 2), and the set difference of mgrStaffNo and name is not a prime attribute (Rule 3), this table is not in 3NF.

Reference:
You do not have permission to view the full content of this post. Log in or register now.

Please tag this answer as helpful if you found it to be so. If you have any further questions, let me know in the comments before and I'll get back to you as soon as I can :).
 

Attachments

Attachments

Status
Not open for further replies.

Similar threads

About this Thread

  • 5
    Replies
  • 521
    Views
  • 2
    Participants
Last reply from:
Unknown user

New Topics

Online now

Members online
353
Guests online
1,020
Total visitors
1,373

Forum statistics

Threads
2,275,082
Posts
28,960,548
Members
1,233,583
Latest member
Natsuuuu77
Back
Top