Instr. teaches (0,m) Instructor (0,n) Section Semester |(0,n) Section C is offered in S (0,n) Student enrolls in Section (0,m) Student Grade (0,m) Course (0,n) Course belongs to Major (8,12) Major The picture above shows the Data Model (Entity Relationship Diagram) of a Student Information System. Please answer the following questions about this data model: Question 1: Why is the "Grade" attribute associated with the relationship type between Student and Section? What would happen if we associated it either with Section, or with Student instead? Please explain your reasoning (5 points) Question 2: How many majors can a given course belong to at most? (5 points)

Instr. teaches (0,m) Instructor (0,n) Section Semester |(0,n) Section C is offered in S (0,n) Student enrolls in Section (0,m) Student Grade (0,m) Course (0,n) Course belongs to Major (8,12) Major The picture above shows the Data Model (Entity Relationship Diagram) of a Student Information System. Please answer the following questions about this data model: Question 1: Why is the "Grade" attribute associated with the relationship type between Student and Section? What would happen if we associated it either with Section, or with Student instead? Please explain your reasoning (5 points) Question 2: How many majors can a given course belong to at most? (5 points)

Principles of Information Systems (MindTap Course List)

12th Edition

ISBN:9781285867168

Author:Ralph Stair, George Reynolds

Publisher:Ralph Stair, George Reynolds

Chapter5: Database Systems And Applications

Section: Chapter Questions

Problem 4PSE: Using a graphics program, develop an entity-relationship diagram for a database application for an...

See similar textbooks

Similar questions

Entity-Relationship Diagram (ERD) is one of the data modeling tools that provides a software engineer with the ability to represent data objects, their characteristics, and their relationships. Use an ERD to describe the following scenario. A teacher is identified by an ID number (TID), last name (LName), and first name (FName). A project is identified by a project ID (PID) and title (T). A student is identified by an ID number (SID), last name (LName), and first name (FName). A teacher can supervise zero, one, or many students and a student is supervised by one teacher. A teacher must propose one or many projects and every project is proposed by one teacher. A student must work on one project and every project is worked by only one student.
Entity modeling is a top-down approach * that involves entities relationships tables foreign key classes هذا السؤال مطلوب
An Entity Relationship (ER) Diagram is a type of flowchart that illustrates how “entities” such as people, objects or concepts relate to each other within a system. Consider the following description of a system: A university registrar’s office maintains data about following entities: Courses, including number, title, credits, syllabus, and prerequisites. Course offerings, including course number, year, semester, section number, instructor, timings and classroom. Students, including student-id, name, and program. Instructors, including identification number, name, department, and title. Furthermore, the enrollment of students in courses and grades awarded to students in each course they are enrolled for must be appropriately modeled. Construct an ER Diagram for the registrar’s office. Document all assumptions that you make about the mapping constraints.
Learning Objective PI3.2 Understand the process of entity-relationship modeling. STEP 1: Background It is very important that you understand the connections among entities, attributes, and relationships. This section has defined each of these terms for you. Typically, entities are described by their attributes, and they are related to other entities. For example, if "student name" is the entity, then age, gender, country of origin, marital status, and other demographic data are the attributes (characteristics) of that particular student. That student is also related to other entities such as financial information, major, and course information. STEP 2: Activity An entity-relationship model is one of the most challenging aspects of designing a database because you have to (1) understand the rules that govern how processes work and (2) be able to define and describe these rules in a picture. This section has provided you with the necessary tools to draw a basic ER model. Imagine the…
ENHANCE ENTITY RELATIOSHIP DIAGRAM The entity type PERSON has the following attributes: SSN, name, address (City/State/Zip), date of birth, age, and contact number. The entity also has the three subtypes: CAMPER, BIKER, AND RUNNER. Draw a separate diagram segment for each of the following situations: 1. At a given time, a person must be exactly one of three subtypes. 2. A person may or may not be one of these subtypes. However, a person who is one of these subtypes cannot at the same time be one of the other subtypes. 3. A person may or may not be the one of these subtypes. On the other hand, a person may be any two (or even three) of these subtypes at the same time. 4. At a given time, a person must be at least one of these subtypes.
Examine the following entity relationship diagram, and select all statements that correctly describe this diagram. PHOTOGRAPHER PK PHOTOGRAPHER ID FIRST_NAME LAST_NAME ++ uses PK +PK,FK1 CAMERA MODEL NR PHOTOGRAPHER ID DESCRIPTION a. The CAMERA entity has a composite primary key. Ob. The existence of each CAMERA instance depends upon the existence of a PHOTOGRAPHER instance. c. Each CAMERA instance is associated with exactly one PHOTOGRAPHER instance. d. A PHOTOGRAPHER uses one or more CAMERAS. e. Both PHOTOGRAPHER and CAMERA are strong entities.
2- Design a class diagram of a course registration system. Note: utilize various class relations: generalization, aggregation, composition, and association; the class diagram should include but not be limited to the following class names User, Student, Instructor, Admin, Course, LogonPage, AddPage, DropPage, ChangePage, PrintPage, QueryPage, CoursenfoDB, StudentInfoDB, InstructorinfoDB, AdmintnfoDB, and EntireDB.
Expaination
Design the UML class diagram to support the system below and upload a picture of your diagram. Used Class Material Website: You are designing a website where students can resale their used material for a course. A course may have multiple sections. The course material is specific to each section of a class. Not all course may require class materials, but they may require many of them. A student can have many used materials for sale. The class material can be either: · Textbook: which has a price(mandatory), title(mandatory), authors(optional), edition(optional) · Software: which has a price(mandatory), title(mandatory), publisher(optional), and also its operating system (mandatory) · Equipment: which has a price(mandatory), title(mandatory), description(mandatory) All class material can be either available or sold. Do a class diagram with: 1. all the classes , 2. their associations 3. their multiplicity . 4. For each classes, where are the…
Modify the Er diagram given below and add 5 to 6 more additions to it such as entities attributes relationships etc
2- Design a class diagram of a course registration system. Note: utilize various class relations: generalization, aggregation, composition, and association; the class diagram should include but not be limited 10 the following class names User, Student, Instructor, Admin, Course, LogonPage, AddPage, DropPage, ChangePage, PrintPage, QueryPage, CourselnfoDB, StudentinfoDB, InstructorinfoDB, AdminlnfoDB, and EntireDB.
design an Enhanced Entity Relationship (EER) diagram Topic: Locomotives The ERR diagram should include Inheritance Relationships Constraints Union Types