Rough Dbms
Rough Dbms
ABSTRACT
This project is focused on creating an automated students result management system using
DATA BASE MANAGEMENT SYSTEM. This is a computerized exam results management
system for student’s examination records. The system presents a single platform that will be
used to manage the processing of all examination records within the institution.
The system will store and organize student information, exam details, and
corresponding marks. It will allow users to search and retrieve results
based on various criteria, such as student ID, subject, or semester. Additionally, the system
will generate reports and statistical analysis to help evaluate student performance and identify
areas for improvement.
The project will utilize relational database models to establish relationships between entities
and ensure data integrity. Overall, this project aims to streamline the process of managing and
accessing exam results, providing a comprehensive and reliable platform for all stakeholders.
OBSTACLE:
• Before DBMS, data was stored in separate sites, making it difficult to manage.
• Data was stored in the file system which made it difficult to manage.
• Data security was a major concern as it was difficult to restrict access to sensitive data.
RESOLUTION:
• DBMS ensures data integrity, security and consistency which were difficult to maintain
earlier.
• The objective of creating a DBMS project for showing exam results could be to provide
a centralized and secure platform for students to view their exam results.
• The project could help to automate the process of generating and publishing exam
results, reducing the workload of the administrative staff.
• The project could provide a platform for teachers to input and manage student grades,
reducing the possibility of errors and ensuring that all grades are recorded accurately.
• It ensures data privacy and protection from unauthorized access or data breaches.
• Overall, the objective of the project would be to make the process of viewing and
managing exam results more efficient, accurate, and accessible.
TABLE DESCRIPTION
The “STUDENT DETAILS” table stores the details of the students including ROLL
(primary key), NAME, ADDRESS, EMAIL ID, CONTACT,
DEPARTMENT. It uniquely identifies each student using roll number and ensure
mandatory information is provided for name, address, email id, contact number and
department.
The “SUBJECT DETAILS” table stores the data including SUBJECT_CODE (primary
key), SUBJECT_NAME, STAFF_ID AND CREDITS. It uniquely identifies each subject
using subject code and ensure mandatory information is provided for subject name, staff id
and credit points.
Field name Type Index Description
Subject_code varchar(10) Primary key Unique identifier
for each subject
The “EXAM DETAILS” table stores data including EXAM_CODE (primary key),
EXAM_NAME, EXAM_DATE, EXAM_DURATION. It uniquely identifies each exam
using a exam id and ensures mandatory information is provided for exam name, exam date,
exam duration.
The “ATTENDANCE” table stores the data including ATTENDANCE_ID, (primary key),
A_PERCENT, ROLL (foreign key), TOTA_ NUMBER_OF_WORKING_DAYS,
NUMBER_OF_DAYS_PRESENT. It uniquely identifies each student using Attendance_id
and ensures mandatory information is provided for total number of working days and number
of days present.
TABLE 5 – RESULTS
The “RESULTS” table stores the data including RESULT_ID(primary key), ROLL
(FOREIGN KEY), EXAM_CODE (foreign key), SUBJECT CODE (foreign
key),TOTAL_OBTAINED, ATTENDANCE_ID (foreign key), GRADE_OBTAINED. It
uniquely identifies each student using result_id and ensures mandatory information is provided
for grade obtained.
Field name Type Index Description
NORMALIZATION
• ATTENDANCE TABLE
-Attendance_id (Primary key)
-A_points
-Name
-Roll (Foreign key)
-Total_no_of_working days
-Number_of_days_present
• RESULT TABLE
-Result_id (Primary key)
-Roll (Foreign key)
-Exam_code (Foreign key)
-Subject_code (Foreign key)
- Total scored
-Attendance_id (Foreign key)
-A_points
-Grade_obtained
CARDINALITY AND RELATIONSHIP:
Result Table:
CARDINALITY: One-to-Many(1:N)
RELATIONSHIP: Each student can get multiple result, but each result is associated with only
one student.
Attendance Table:
CARDINALITY: One-to-many(1:N)
RELATIONSHIP: Each student can be associated with multiple attendance details, but each
attendance detail is associated with only one student.
NORMAL FORM:
RESULT TABLE
ER DIAGRAM
Primary key
Foreign Key
Composite Key
Composite Attributes :
Simple Attributes
Derived Attributes :
Stored Attributes
Key Attributes
DDL is a subset of SQL used to define and manage the structure of a database, including
creating, altering, and deleting database objects like tables, indexes, and constraints.
DML is a subset of SQL used to manipulate data stored in a database, including operations like
selecting, inserting, updating, and deleting data within tables.
5.3. UPDATE : WRITE A QUERY TO UPDATE THE Department AS “BBA” WHERE THE
Roll=4.
mysql> COMMIT;
Query OK, 0 rows affecyed (0.00 sec)
mysql> ROLLBACK;
Query OK, 0 rows affected (0.00 sec)
mysql> COMMIT;
Query OK, 0 rows affected (0.00 sec)
mysql> COMMIT;
Query OK, 0 rows affected (0.00 sec)
8.1. PRIMARY KEY - Ensures uniqueness and identifies each row uniquely in a table.
CREATE :
INSERT :
INSERT :
8.3. NOT NULL - Ensures that a column cannot have a null (empty) value.
CREATE :
INSERT :
8.4. UNIQUE - Ensures that values in a column are unique across rows.
CREATE:
mysql> CREATE TABLE EXAM_DETAILS TABLE(Exam_code varchar PRIMARY
KEY, Exam_name VARCHAR(20), Exam_date VARCHAR(20) UNIQUE, Exam_duration
VARCHAR(20));
Query OK, 0 rows affected (0.01 sec)
INSERT :
8.5. CHECK - Defines conditions that must be met for data in a column.
CREATE :
INSERT :