My question is how should this look. Below this is my chart but not sure if I am corrrectly?

 

 

The purpose of this assignment is to practice on the creation of a Relational Data Model from an Entity -Relationship Diagram.

Directions

 

Last unit, you were given the task to create an ER Diagram for the entities and relationships found in a small college.

This unit, you will convert an ER diagram for a similar situation into a Relational Data Model. The ER Diagram is shown at the end of the directions and represents a slightly different scenario from last week. In particular, the differences are as follows:

1. Schools and Departments are not considered to be entities on their own, but just attributes in other tables.
2. Course offerings are an associative relationship between Faculty and Course entities. A Faculty member teaches a course that is being offered. An offering has a unique OfferingID that is never repeated. The offering relationship keeps track of the Semester in which the Offering took place, the name of the section and the classroom where it was taught. As before, when a semester ends, student's grades are reported to a file of Official Records. Every student with grades as references to the Official Records where all her/his grades are saved.
3. Student associations may now be advised by none, one or more than one Faculty member.

You must convert the given ER Diagram into a Relational Data Model following the guidelines of the textbook and the course shell. Be sure to create rows of boxes for every required table, each box should contain a field within the table. Primary keys should be properly underlined and foreign key relations should be clearly indicated with arrows.

 

Deliverables

 

submit a Relational Data Model Design with a diagram showing all tables, primary keys, and foreign key relationships that describe the given ER Diagram.

To draw the diagram, students may use Microsoft Office software like Word (.docx), Excel (.xlsx), or PowerPoint (.pptx) and submit them. Students may also use any other software that creates diagrams available to them, as long as they produce a PDF file to be submitted. Alternatively, diagrams may also be drawn by hand, and a picture may be taken (.jpg) for submission. Therefore, only the following file types will be accepted: .docx, .xlsx, .pptx, .pdf and .jpg. In all cases, be sure that the diagram is neatly organized and readable.

 

Unit 3: Assignment Rubric

 

Criteria

Ratings

Pts

This criterion is linked to a Learning OutcomeSubmission of an Relational Data Model Design to solve the assignment

 

2 pts Meets Expectations Student submits a viewable and readable Relational Data Model Design to solve the assignment. To be readable, it should be properly organized and formatted. It should also be clear, understandable, and written in correct English and/or correct Relational Data Model Design conventions.

1 pts Developing Student submits a viewable diagram but it is not a readable Relational Data Model Design that solves the assignment or it is not drawn using the correct Relational Data Model Design conventions.

0 pts No Marks Student does not present a viewable or readable Relational Data Model Design.

2 pts
 

This criterion is linked to a Learning OutcomeRelational Data Model Design includes a Student Table with appropriate fields and designated primary key.

 

0.7 to >0.0 pts Meets Expectations Submitted Relational Data Model Design contains a Student Table with appropriate fields required by the assignment and a designated primary key. Number of points will reflect the quality of the fields included in the entity.

0 pts No Marks Relational Data Model Design does not contain a Student table.

0.7 pts
 

This criterion is linked to a Learning OutcomeRelational Data Model Design includes a Faculty Table with appropriate fields and designated primary key.

 

0.7 to >0.0 pts Meets Expectations Submitted Relational Data Model Design contains a Faculty Table with appropriate fields required by the assignment and a designated primary key. Number of points will reflect the quality of the fields included in the entity.

0 pts No Marks Relational Data Model Design does not contain a Faculty table.

0.7 pts
 

This criterion is linked to a Learning OutcomeRelational Data Model Design includes a Course Table with appropriate fields and designated primary key.

 

0.7 to >0.0 pts Meets Expectations Submitted Relational Data Model Design contains a Course Table with appropriate fields required by the assignment and a designated primary key. Number of points will reflect the quality of the fields included in the entity.

0 pts No Marks Relational Data Model Design does not contain a Course table.

0.7 pts
 

This criterion is linked to a Learning OutcomeRelational Data Model Design includes an Offerings Table with appropriate fields and designated primary key.

 

0.7 to >0.0 pts Meets Expectations Submitted Relational Data Model Design contains a Offerings Table with appropriate fields required by the assignment and a designated primary key. Number of points will reflect the quality of the fields included in the entity.

0 pts No Marks Relational Data Model Design does not contain a Offerings table.

0.7 pts
 

This criterion is linked to a Learning OutcomeRelational Data Model Design includes a OfficialRecords Table with appropriate fields and designated primary key.

 

0.7 to >0.0 pts Meets Expectations Submitted Relational Data Model Design contains a Official Records Table with appropriate fields required by the assignment and a designated primary key. Number of points will reflect the quality of the fields included in the entity.

0 pts No Marks Relational Data Model Design does not contain a Official Records table.

0.7 pts
 

This criterion is linked to a Learning OutcomeRelational Data Model Design includes a StudentAssociation Table with appropriate fields and designated primary key.

 

0.7 to >0.0 pts Meets Expectations Submitted Relational Data Model Design contains a Student Association Table with appropriate fields required by the assignment and a designated primary key. Number of points will reflect the quality of the fields included in the entity.

0 pts No Marks Relational Data Model Design does not contain a Student Association table.

0.7 pts
 

This criterion is linked to a Learning OutcomeRelational Data Model Design includes an Advise Table with appropriate fields and designated primary key.

 

0.7 to >0.0 pts Meets Expectations Relational Data Model Design includes an Advise Table with appropriate fields and designated primary key.

0 pts No Marks Relational Data Model Design does not contain an Advise table.

0.7 pts
 

This criterion is linked to a Learning OutcomeRelational Data Model Design includes a MemberList Table with appropriate fields and designated primary key.

 

0.7 to >0.0 pts Meets Expectations Submitted Relational Data Model Design contains a Member List Table with appropriate fields required by the assignment and a designated primary key. Number of points will reflect the quality of the fields included in the entity.

0 pts No Marks Relational Data Model Design does not contain a Member List table.

0.7 pts
 

This criterion is linked to a Learning OutcomeCaptured Relationships

 

2.4 to >0.0 pts Meets Expectations Student receives 0.3 points under this criterion for each correct foreign key relationship correctly described in the Relational Data Model Design presented among the following pair of Tables: 1. Student to Faculty 2. Offerings to Faculty 3. Official Records to Offerings 4. Official Records to Student 5. Advise to Faculty 6. Advise to Faculty to Student Association 7. Member List to Student 8. Member List to Student Association Partial credit may be given for incorrectly captured relationships.

0 pts No Marks None of the required relationships is presented.

2.4 pts

 

Transcribed Image Text:

Faculty FacultyID First Name Initials Last Name Position Office Phone No Student StudentID First Name Initials Last Name Classification School Major FacultyID Offering OfferingID Section Classroom FacultyID CourseID Advise FacultyID AssociationID Member List StudentID AssociationID Student Association AssociationID Association Name FacultyID StudentID Course CourseID Name Department Credit Hours OfferingID Offical Records OfferingID StudentID Grade Faculty FacultyID First Name Initials Last Name Position Office Phone No Student StudentID First Name Initials Last Name Classification School Major FacultyID Offering OfferingID Section Classroom FacultyID CourseID Advise FacultyID AssociationID Member List StudentID AssociationID Student Association AssociationID Association Name FacultyID StudentID Course CourseID Name Department Credit Hours OfferingID Offical Records OfferingID StudentID Grade