You may assume the followings:    • Each material item has one or more vendor. Each vendor may supply one or more.  items or may not supply any items.  • The unit price for a material item may vary from one vendor to another.  • The terms for a supplier are the same for all material items ordered from that supplier.     Please answer the following questions:  1. Draw a dependency diagram to show the functional dependencies in the relation.   2. Decompose the relation into a set of 1NF, 2NF & 3NF relations with each normal form dependency diagram

Transform into relational model (relations). IMPORTANT: The diagram needed for the second part uses a different notation for cardinality constraints.  You can deduce the notation from the following: Each employee can work for exactly one department, and each department can have at least one employee. Each department has exactly one manager, and each employee manages at most one department. Each employee has at most one supervisor, and each supervisor can have several supervisees.

Question 1: Normalization  Please TYPE IF POSSIBLE OR WRITE CLEARLY Consider a relation X with six attributes WYSMFE where WS is a composite primary key for X. Assume X has the following functional dependencies (X is one table with the attributes W, Y, S, M, F, E): WS è YMFE S è YME E è M   In what normal form is relation X? Explain why?   Is it possible to decompose X into a number of relations in order to achieve a higher normal form? Explain how (this means using English sentences and a diagram showing the final relation(s)).

Consider a relation named as BOOK that contains data about the books in a library. BOOK relation was initially created with the attributes BookID (an id that library assigns), ISBN, CopyNr (used to differentiate copies of the same book), Title, PublYear, Author, and AuthorBornYear.  Primary key: BookID, CopyNr and Author Candidate key: ISBN, CopyNr and Author Below you see dependencies of attributes:    Dependency 1 (D1): ISBN, Title, PublYear, AuthorBornYear were dependent on BookID, CopyNr and Author Dependency 2 (D2): Title and PublYear were dependent on BookID, CopyNr Dependency 3 (D3): AuthorBornYear was dependent on Author  First determine which normal form (1NF, 2NF, 3NF or BCNF) the above relation is, and why. Then, if necessary, convert the above relation to the highest normal form (BCNF). Write any assumptions that you make.

Here we explain three cases when it makes sense to use a surrogate key in lieu of the relation's main key.

Swing Jazz Club ERD Problem Follow the Simple Procedure for ERD diagramming to design an ERD using the following user provided information.   Remember the ERD will eventually turn into the design for a database from a top down view.  Make sure you resolve any many to many conflicts.  Label an identifier or primary key and all pertinent attributes given.   If an attribute is not readily apparent from the user information, then make one up that makes sense for the particular entity.  Therefore, all entities should end up with at least an identifier and another attribute that makes sense.  You may use any of the approaches shown by the book, though the ER-Model and Crow’s foot are the most common.  Make sure you show entities, relationships, cardinality, and optionality.  Swing Jazz Club The Swing Jazz Club teaches swing and jazz dancing and offers both private and group lessons.  Swing Jazz charges $60 dollars per hour for a private lesson and $10 dollars per hour for a group lesson.…

Explain the process of decomposing a relation to achieve higher normal forms and the potential trade-offs involved.

Consider the following statements: (1) We can check if a functional dependency holds by examining a single relation instance. (1I) We can check if a functional dependency is violated by examining a single relation instance Only statement II is true Only statement I is true Both I and II are true Neither I nor |l is true

please explain better way .  Thank You.

An explanation of three different scenarios in which it might be appropriate to use a surrogate key in place of the relation's primary key is provided here.