Concept explainers
a.
Normalization:
The process used to minimize data redundancy and dependency in a relational
First normal form (1NF):
- If a table does not contain any replicate fields or groups of fields then that model is called as first normal form.
- In this form, entities do not contain any single instance of the repeating variable.
- It means that the entities contain only one instance of the attributes, multi-valued attributes are neglected.
Second normal form (2NF):
- The value of all non-primary key attributes should be dependent on the primary key attribute.
- If any attribute is depending on the partial primary key then it should determine the other attributes for an instance of the entity.
- The partial dependencies should be removed from the data model.
Third normal form (3NF):
- The value of any non-primary key attributes will not depend on any other non-primary key attributes.
- If any non-primary key attributes depend on any other non-primary key attribute then it should be moved or deleted.
- It is termed as transitive dependency.
Partial dependency:
A partial dependency exists at that time of an attributes depends only a part of primary key. This dependency is related with 1st normal form.
Transitive dependency:
A transitive dependency exists at that time of an attributes depends on another attribute which is not part of primary key.
Functional dependency:
An association between two attributes or two set of attributes in a same relational database table, which is having some constraints is known as functional dependency.
- In a table one attribute is functionally dependent on another attribute to take one value.
b.
Explanation of Solution
Dependencies diagrams for each database table:
Table1:
Create the database table with name of Table1 is given below:
Table1 (ISBN, BookTitle, Edition)
- Here, “ISBN” indicates the primary key.
- “BookTitle” and “Edition” are partial dependent on ISBN.
Normal form:
- The relation is in third normal form (3NF), since there is no transitive dependency and no repeated attributes.
The representation of dependency diagram for table1 is shown below:
Table2:
Create the database table with name of Table2 is given below:
Table2 (BookTitle, Publisher)
- “BookTitle” are transitive dependent on “Publisher”.
Normal form:
- The relation is in second normal form (2NF), because there is transitive dependency in this database table.
The representation of dependency diagram for table2 is shown below:
Table3:
Create the database table with name of Table3 is given below:
Table3 (Author_Num, LastName)
- Here, “Author_Num” indicate the primary key...
Trending nowThis is a popular solution!
Chapter 6 Solutions
Database Systems: Design, Implementation, & Management
- QUESTION 1 The dependency diagram in figure below indicates that authors are paid royalties for each book that they write for a publisher. The amount of the royalty can vary by author, by book, and by edition of the book. Book royalty dependency diagram See attached for diagram Based on the dependency diagram, create a database whose tables are at least in 2NF, showing the dependency diagram for each table Create a database whose tables are at least in 3NF, showing the dependency diagram for each table.arrow_forwardplz help with the following: Create a database whose tables are at least in 3NF, showing the dependency diagrams for each table.arrow_forwardThe dependency diagram below indicates that authors are paid royalties for each book they write for a publisher. The amount of the royalty can vary by author, by book, and by edition of the book. (10) a) Based on the dependency diagram above, create a database whose tables are at least in 2NF, showing the dependency diagram for each table. b) Create a database whose tables are in 3NF, showing the dependency diagram for each table. (8) (8)arrow_forward
- Question 2:- The dependency diagram shown indicates that authors are paid royalties for each book that they write for a publisher. The amount of the royalty can vary by author, by book, and by edition of the book. ISBN Book Title Author Num LastName Publisher Royalty Edition a) Based on the dependency diagram, create a database whose tables are at least in 2NF, showing the dependency diagram for each table. For full points, make sure to clearly label all partial and transitive dependencies.arrow_forwardThe following tables describe the content of a relational database:arrow_forwardSuppose you are a manufacturer of product ABC, which is composed of parts A, B, and C When a new product is created, the involved parts in table PART must be reduced. As such, when product ABC is created, PROD_QTY is increased by one, and the quantity of parts A, B, and C in table PART (i.e. PART_QTY) is reduced by one respectively. The database content is shown in the following tables. How many database requests can you identify when a product ABC is created? List all.arrow_forward
- Read the following business rules carefully and use common sense when necessary to come up with a good database design as follows: 1- First, develop an ER model. Make sure to use meaningful entity names and relations. 2- Translate ER model into a set of tables, relations and constraints. 3- Label appropriate columns as primary keys and foreign keys. Business rules: A patient can make many appointments with one or more doctors in the clinic, and a doctor can accept appointments with many patients. However, each appointment is made with only one doctor and one patient. Emergency cases do not require an appointment. However, for appointment management purposes, an emergency is entered in the appointment book as “unscheduled.” If kept, an appointment yields a visit with the doctor specified in the appointment. The visit yields a diagnosis and, when appropriate, treatment. With each visit, the patient’s records are updated to provide a medical history Each patient visit…arrow_forwardBelow given relations of a database are in First Normal Form (1st NF). Decompose (Split) the relations to Normalize in 2NF and 3NF. tbl Project Project Code Project Name Project Manager Budget Reservation System HR System Attendance System PC010 Mr. Said 25000 PC011 MS. Malak 32000 PC012 Mr. Rajesh 19000 DBMS tbl Emp Dept Project Code Emp No Hourly Pay Emp Name Dept No Dept Name Ali Mohd. PC010 S100 D03 Database 7.500 PC010 S101 Hamood D02 Testing 5.500 PC010 S102 Riyaz D01 IT 8.200 PC011 S103 Pavan D03 Database 6.500 PC011 S104 Basma D02 Testing 5.400 PC011 S115 Asaad D01 IT 7.900 PC012 S137 Fathima D03 Database 6.200 PC012 S218 Avinash D02 Testing 6.100 PC012 S109 Роoja D01 IT 9.300arrow_forwardConsider the following relational schema for a library database: Book (Title, Author, Catalog_no, Publisher, Year, Price, bookCoverType, contractDate) Collection (Title, Author, Catalog_no) Assume {Author, Title} is the key for both relations Additional functional dependencies are Title,Author --> Catalog_no Catalog_no --> Publisher, Year, bookCoverType Publisher, bookCoverType --> Price Author --> contractDate a) Explain what normal form the relation is in. b) Apply normalization until the 3rd State reasons behind each normalizationarrow_forward
- Below given relations of a database are in First Normal Form (1* NF). Decompose (Split) the relations to Normalize in 2NF and 3NF. tbl_Project Project Code Project Name Project Manager Budget PC010 Reservation System Mr. Said HR System Attendance System Mr. Rajesh 25000 PC011 MS. Malak 32000 PC012 19000 tbl_Emp_Dept Project Code Emp No Emp Name Dept No Dept Name Hourly Pay PC010 S100 Ali Mohd. D03 Database 7.500 PC010 S101 Hamood D02 Testing 5.500 PC010 S102 Riyaz D01 IT 8.200 PC011 S103 Pavan D03 Database 6.500 PC011 S104 Basma D02 Testing 5.400 PC011 S115 Asaad D01 IT 7.900 PC012 S137 Fathima D03 Database 6.200 PC012 S218 Avinash D02 Testing 6.100 PC012 S109 Роja D01 IT 9.300arrow_forwardname ID admit_date SSN address phone Patient responsible Physician Room id {disjoint,complete) 0..2 Room assigned ISA bed# 1.1 out Patient resident Patient assigned bed (disjoint,complete} Checkback_date discharge_date ISA ICU bed Regular bed Provide a complete Relational Schema of the database described by the following Entity Relationship diagram. You must use Merge Rule whenever possible.arrow_forwardTask 1: ER diagram for give scenario Consider building a database for a shopping mall with requirements as follows: Each product of the shopping mall has a unique project No, and also has a name, a supplier name, a category, a purchase price and a selling price. Products need to be supplied from suppliers. Each product has one supplier, but a supplier may supply many products for the shopping mall. Each supplier has a supplier name and address. A purchase order for product from a supplier has a unique order No, and a date. The order specifies one or more products and their quantities required for a product. A sales order for product to customers has a unique order No, and a date. The order specifies one or more products and their quantities required for a product The shopping mall has warehouses. Each warehouse has a warehouse number, an address and a contact phone number. Each warehouse has shelves to store products. Each shelf has a shelf-number and a capacity. The shelf…arrow_forward
- Database Systems: Design, Implementation, & Manag...Computer ScienceISBN:9781305627482Author:Carlos Coronel, Steven MorrisPublisher:Cengage LearningDatabase Systems: Design, Implementation, & Manag...Computer ScienceISBN:9781285196145Author:Steven, Steven Morris, Carlos Coronel, Carlos, Coronel, Carlos; Morris, Carlos Coronel and Steven Morris, Carlos Coronel; Steven Morris, Steven Morris; Carlos CoronelPublisher:Cengage LearningA Guide to SQLComputer ScienceISBN:9781111527273Author:Philip J. PrattPublisher:Course Technology Ptr