Using the STUDENT table structure shown in Table P6.4, do the following:
a. Write the relational schema and draw its dependency diagram. Identify all dependencies, including all transitive dependencies.
b. Write the relational schema and draw the dependency diagram to meet the 3NF requirements to the greatest practical extent possible. If you believe that practical considerations dictate using a 2NF structure, explain why your decision to retain 2NF is appropriate. If necessary, add or modify attributes to create appropriate determinants and to adhere to the naming conventions.
c. Using the results of Problem 4, draw the Crow's Foot ERD.
Note: Although the completed student hours (STU_HOURS) do determine the student classification (STU_ClASS), this dependency is not as obvious as you might initially assume it to be. For example, a student is considered a junior if the student has completed between 61 and 90 credit hours.
To upload and submit your assignment, click the Choose File button below to find and select your saved document. Make sure that the file is saved with your last name in the file name. (Example: ch6_problem1_Jones.doc)
Trending nowThis is a popular solution!
Step by stepSolved in 3 steps with 8 images
- a) Consider the following EER diagram. Map it to the relational model. Specify the relational schema in DBDL notation. b) Convert the following relational schema to BCNF (FD1, FD2 and FD3 are functional dependencies. CourseOffering(coId, courseId, semesterId, year, campus, courseName) Primary key (coId) Alternate Key (courseId, semesterId, year, campus) FD1: coId courseId, semesterId,arrow_forwardCreate an Entity Relationship Diagram (ERD) of the normalized version of this table using Visio's crows-foot notation. The ERD should show the PK and FK columns, plus all of the appropriate column attributes (column name, data type/size, null/not null) plus the relationships (with minimum and maximum cardinality) between tables. Requirements: Show the results of the normalization as individual tables Show the FK and PK columns using Visio's notation You must solve the multi-column issue with grades (Hint: This will require a new column) Show the 3-part column definition as noted Show min/max cardinality Tables are attachedarrow_forwardHere are three examples of when it makes sense to create a surrogate key in place of the primary key in a relation.arrow_forward
- Instructions: In this assignment, you will convert an Entity-Relationship diagram into a set of related tables. Given the following ERD, write the table definitions for the entities displayed below. You do not have to indicate data types nor “not null” constraints in this lab. Use the format TableName ( attribute, attribute…attribute). Designate primary keys with an underline and foreign keys with a broken underline. To illustrate, the Regions and Countries table definitions have been created for you below the diagram. Type your answers in this document and upload it to the appropriate Blackboard assignment link by Monday at 11:59 p.m. ET of this module/week. Note that you should read the “Table Conversions Explained” document in your Reading & Study folder. I created it to help you better understand how ERDs will ultimately be transformed into real tables. ERD for the Hourglass timekeeping databasearrow_forward25. In the relational model, relationships between relations or tables are created by using: a. composite keys b. determinants c. candidate keys d. foreign keysarrow_forwardUse the following business rule to create a Crow's Foot ERD that can be implemented in the Relational Model. A CUSTOMER may rent many DVD's in a movie rental company and a DVD can be rented by many CUSTOMER's. Show the primary and foreign keys in your entities.arrow_forward
- Use the technique of normalization to validate the structure of your relational schema. Demonstrate that each of your relations is in third normal form (3NF) by displaying the functional dependencies between attributes in each relation. Note, if any of your relations are not in 3NF, this may indicate that your ER model is structurally incorrect or that you have introduced errors in the process of deriving relations from your model.arrow_forwardPlease draw an relational ERD with multiplicities and all the attributes based on following description: ( Please identify the primary key in each entity.) An Adult Education Department runs various courses during the daytime and evenings, and at different times of the year. For example, ‘Spanish level 1’ is offered on Monday mornings, Monday evenings or Wednesday evenings, and runs over 25 weeks from October to March. On the other hand, ‘Introduction to Digging Up Your Ancestors’ only runs for 8 weeks, but is offered on Tuesday or Wednesday evenings from October to December, January to March, and April to June, with an optional field week in August. There is always a maximum number of places for each course offering, which is dependent on the individual teacher. For example, ‘Spanish level 1’ on Monday evenings may be limited to 20 places, but on Wednesday evenings the limit may be 25. Each course offering is only taken by one teacher, however teacher may take…arrow_forwardConsider the follow relations’ schemas to answer the following questions: Student (sid, name, level, address) Book(bid, title, author) BorrowedBook(sid, bid, date) 1) Assume that, there are 10,000 Student records stored on 1,000 pages/blocks, 50,000 Book records stored on 5,000 pages, 300,000 BorrowedBook records stored on 15,000 pages, and there are 500 different authors. Find out what is the record size for each of the previous relation?, and what is the blocking factor for each relation?arrow_forward
- PLz help with the following: Translate your ER diagram into a relational schema in the form of SQL DDLs. Choose appropriate data types for each attribute and include primary key and foreign key constraints, Check and Not Null constraints.arrow_forwardCreate ERD of a hospital with these requirements "and then" write relation schema (underline primary key and connect foreign key with arrow): (use Chen Notation) 1. Hospital have many department, each department have it's own ID, name, and head of department. 2. Hospital need to collect Patient data included : ID, Name, Sexuality, Age, Address, Health Insurance, Telnum 3, Patient may have data stored about people they can contact, should be more than 1 people they can contact 4. Doctor should have : DocID, Name, Sex, TelNum, Specialty, Years of service, Salary, Qualification 5. 1 doctor can be assigned to only 1 department 6. some doctor may not have their assigned patient 7. patient can be assigned to more than 1 doctor for treatment 8. each treatment shall be stored (date, detail, next appointment) Specification for the diagram: - describe what should be describe and what can be describe inside the diagram - also explain others that can be describe inside the diagram briefly (don't…arrow_forwardWhich relational process describes a binary relationship? Multiple occurrences of an entity type are bound together by intersection data. A single occurrence of one entity type is associated with intersection data. A single occurrence of one entity type is associated with a single occurrence of another entity type. Multiple occurrences of an entity type are associated with multiple occurrences of another entity typearrow_forward
- Computer Networking: A Top-Down Approach (7th Edi...Computer EngineeringISBN:9780133594140Author:James Kurose, Keith RossPublisher:PEARSONComputer Organization and Design MIPS Edition, Fi...Computer EngineeringISBN:9780124077263Author:David A. Patterson, John L. HennessyPublisher:Elsevier ScienceNetwork+ Guide to Networks (MindTap Course List)Computer EngineeringISBN:9781337569330Author:Jill West, Tamara Dean, Jean AndrewsPublisher:Cengage Learning
- Concepts of Database ManagementComputer EngineeringISBN:9781337093422Author:Joy L. Starks, Philip J. Pratt, Mary Z. LastPublisher:Cengage LearningPrelude to ProgrammingComputer EngineeringISBN:9780133750423Author:VENIT, StewartPublisher:Pearson EducationSc Business Data Communications and Networking, T...Computer EngineeringISBN:9781119368830Author:FITZGERALDPublisher:WILEY