Scribd
Upload
8 views14 pages

Field Project 1

The document outlines a field project for designing and developing a database system to manage academic and non-academic data for a university. It details the entities, attributes, and relationships involved, including students, departments, courses, and faculty, and discusses the creation of an ER model and relational database schema. Additionally, it addresses data redundancy, multi-valued attributes, and includes tasks for SQL query design and testing.

Uploaded by

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

Field Project 1

The document outlines a field project for designing and developing a database system to manage academic and non-academic data for a university. It details the entities, attributes, and relationships involved, including students, departments, courses, and faculty, and discusses the creation of an ER model and relational database schema. Additionally, it addresses data redundancy, multi-valued attributes, and includes tasks for SQL query design and testing.

Uploaded by

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

FIELD PROJECT

NAME : U.SUDEEP NAGAMANIKANTA

REG.No : 231FA18060

BATCH.No : 03

BRANCH : AI&ML

SECTION : A
Design and Development of Database System - Field
Project
1. University decided to develop a database system for managing the
academic and non-academic data pertaining to its students. University
comprises of several departments, faculty, students, programs,
courses, class rooms, hostels, transport, library, exam-cell, finance
department etc., University offers several engineering programs under
different departments.

2. Every department offers one or more B.Tech. programs. Each


department has faculty to teach the courses relevant to the program
being offered. Department has sufficient number of class rooms to
conduct classes. At the beginning of the semester, every student is
expected to register for various core courses, dept. electives, open
electives and honors/minor courses. Department assigns faculty to
teach different courses relevant to the program. Classes for different
3. Departments will conduct assessments for various courses, students
will borrow books from central library, some students may use
public/private transport for commuting to the university, others may
use either university transport or may stay in the university hostels.
Students data need to be stored at multiple sections/functional units
of the University.

a. Identify entities, attributes, and relationships between entities from


the above problem statement. Database should contain the image of
a structured diagram. Draw an ER model for the above problem of a
database system using any ER modeling tool. Schema should be able
to depict primary key attributes, composite attributes, multi-valued
attributes, attributes of relationships, weak entity, strong entity, key
attributes in a relationship, identification of binary, ternary, etc.,
relationships between/among entities, relationship between
attributes of the same entity.
b) Does the relationship in an ER model represent redundancy in data?
Justify your answer with examples.

c) Does data in any organization exist without redundancy? Give


examples and your justification.

d) Assume a scenario where data redundancy is mandatory in a


database and explain the process to eliminate the inconsistency in data.

e) Why multi-valued attributes are discouraged in a relational database?


Write your justification.
f) Design relational database schema for the above said ER Model of the
database. Relational database schema should contain definitions of
relations, types of attributes, primary key, foreign key constraints,
domain integrity constraints, referential integrity constraints, not null
constraints and views. Schema should contain the definition to remove
all occurrences of single data item also it should include the update of all
occurrences of a single data element. Also, no relationship between a
non-existing entity and existing entity should present in the database.

g) Design all possible queries to extract different information from one


table and from two or more tables.

h) Design SQL statements to get responses for the above queries


designed.
i) Verify the correctness of the output of an SQL statement.
j) Design test cases to check whether valid data is getting stored into the
database.
ER – DIAGRAM :
ENTITIES AND ATTRIBUTES:

Student: S _ id , S _ Name , Email, Phone _ No, Age, Semester, Dept _ id , IMAGE

Department: Dept _ id , Dept _ name

Program: Pro _ id , Pro _ name , Duration

Course: C _ id , C_Name, C _ Credits, Pro _ id

Faculty: F _ id , F_ Name, Salary, Dept _ id

Classroom: Class _ Id , Capacity, Class _ Type

Library: L _ id , Title, Author, S _ id , Dept _ id

Transport: T _ id , Veh _ Id, Route

Finance: F _ id , Amount, S _ id
TYPES OF ATTRIBUTES :
2. Department:
1. Student:
Strong entity
Strong entity Attributes:
Attributes:
1. Dept_id (Primary Key)
1. S_id (Primary Key) 2. Dept_name (Simple)
2. F_Name (First Name) (Simple)
3. M_Name (Middle Name) (Simple)
4. L_Name (Last Name) (Simple)
5. S_Name: composite
(consists of F_ Name, M_Name, L_Name)
6. Age (Simple)
7. Semester (Simple)
8. Phn_No (Phone Number) (multivalued)
9. Email (multivalued)
10. Dept_id (Foreign Key)
11. Image (Multivalued)
3. Program: 6. Classroom: 9. Finance:
Strong entity Strong entity Weak entity
Attributes: Attributes: Attributes:
1. Pro _ id (Primary Key) 1. Class _ Id (Primary Key) 1. Fi _ Id (Primary Key)
2. Pro _ name (Simple) 2. Capacity (Simple) 2. Amount (Simple)
3. Duration (Simple) 3. Class _ Type (Simple)
4. Course: 7. Library:
Strong entity Strong entity
Attributes: Attributes:
1. C _ id (Primary Key) 1. L _ Id (Primary Key)
2. C _ Name (Simple) 2. Title (Simple)
3. C _ Credits (Simple) 3. Author (Simple)
4. Pro _ id (Foreign Key) 8. Transport:
Strong entity
5. Faculty: Attributes:
Strong entity 1. Veh _ Id (Primary Key)
Attributes: 2. Route (Simple)
1. E _ Id (Primary Key)
2. F _ Name (Simple)
3. Salary (Simple)
Attributes of Relationships:
1.Registers relationship between Student and Course may have an attribute like
Semester to track which semester a student registers for a course.
2.Assessment between Student and Course may have an attribute like Grade to
track the assessment results for a student in a particular course.

Identifying Binary and Ternary Relationships:


•Binary Relationships:
• Student – Finance (Has)
• Student – Transport (Uses)
• Student – Program (Enrolls)
• Student – Course (Registers)
• Faculty – Course (Teaches)
• Course – Classroom (Allocates)
• Student – Library (Borrows)
•Ternary Relationships:
• None identified in this scenario.
Relationships:
1.Has (Between Student and Finance)
1. Participation: Total for both entities.
2. Cardinality: One-to-One (1:1).
2.Borrows (Between Student and Library)
1. Participation: Partial for Student, Total for Library.
2. Cardinality: One-to-Many (N:1).
3.Registers (Between Student and Course)
1. Participation: Total for Student, Partial for Course.
2. Cardinality: Many-to-One (N:1).
4.Belongs (Between Course and Department)
1. Participation: Total for both entities.
2. Cardinality: Many-to-One (N:1).
5.Enrolled (Between Student and Program)
1. Participation: Total for both entities.
2. Cardinality: Many-to-One (N:1).
6.Uses (Between Student and Transport)
1. Participation: Partial for both entities.
2. Cardinality: Many-to-One (N:1).
7. Teaches (Between Faculty and Course)
7. Participation: Partial for both entities.
8. Cardinality: Many-to-One (N:1).
8. Allocates (Between Classroom and Course)
7. Participation: Total for both entities.
8. Cardinality: One-to-One (1:1).

You might also like