Scribd
Upload
8 views2 pages

Hands On Er For University DB PDF

The document outlines the requirements for a database to track student enrollments and grades at a university, detailing the structure of colleges, departments, courses, instructors, students, and sections. It specifies the attributes for each entity type and the relationships between them, including cardinality and participation constraints. The task is to design an ER diagram that accurately represents this conceptual schema using the specified ER design concepts.

Uploaded by

piloda4490
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
8 views2 pages

Hands On Er For University DB PDF

The document outlines the requirements for a database to track student enrollments and grades at a university, detailing the structure of colleges, departments, courses, instructors, students, and sections. It specifies the attributes for each entity type and the relationships between them, including cardinality and participation constraints. The task is to design an ER diagram that accurately represents this conceptual schema using the specified ER design concepts.

Uploaded by

piloda4490
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

CSC430/530 – Database Management Systems

Hands-on activity – ER diagram

Suppose that a database is needed to keep track of student enrollments in classes and students’ final grades.
After analyzing the mini-world rules and the users’ needs, the requirements for this database were determined
to be as follows:

The university is organized into colleges (COLLEGE), and each college has a unique name (CName), a main office
(COffice) and phone (CPhone), and a particular faculty member who is dean of the college. Each college administers
a number of academic departments (DEPARTMENT). Each department has a unique name (DName), a unique code
number (DCode), a main office (DOffice) and phone (DPhone), and a particular faculty member who chairs the
department. We keep track of the start date (CStartDate) when that faculty member began chairing the department.
A department offers a number of courses (COURSE), each of which has a unique course name (CoName), a unique
code number (CCode), a course level (Level: this can be coded as 1 for freshman level, 2 for sophomore, 3 for junior,
4 for senior, 5 for graduate level), a course credit hours (Credits), and a course description (CDesc).
The database also keeps track of instructors (INSTRUCTOR); and each instructor has a unique identifier (Id), name
(IName), office (IOffice), phone (IPhone), and rank (Rank); in addition, each instructor works for one primary
academic department.
The database will keep student data (STUDENT) and stores each student’s name (SName, composed of first name
(FName), middle name (MName), last name (LName)), student id (Sid, unique for every student), address (Addr),
phone (Phone), major code (Major), and date of birth (DoB). A student is assigned to one primary academic
department. It is required to keep track of the student’s grades in each section the student has completed.
Courses are offered as sections (SECTION). Each section is related to a single course and a single instructor, and has
a unique section identifier (SecId). A section also has a section number (SecNo), semester (Sem), year (Year),
classroom (CRoom: this is coded as a combination of building code (Bldg) and room number (RoomNo) within the
building), and days/times (DaysTime: for example, ‘MWF 9am-9.50am’ or ‘TR 3.30pm-5.20pm’). The database keeps
track of the students in each section, and the grade is recorded when available (this is a many-to-many relationship
between students and sections).

Your task is to design an ER diagram that represents a conceptual schema for the described mini-world.
Make sure you use following ER design concepts:
• Entity types.
o Attributes of entity types.
o Types of attributes (e.g. key, composite, multivalued).
• Relationship types.
o Attributes of relationship types (if applicable).
o Role names (if applicable).
o Cardinality ratio and participation constraints of relationship types.
Solution:

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy