DATABASE MANAGEMENT SYSTEM r4
DATABASE MANAGEMENT SYSTEM r4
NORMALIZATION
Alumni Information System
Pre-Existing Tables
Initial Tables
CREATE TABLE Login (
Login_username VARCHAR(255),
Login_password VARCHAR(255),
PRIMARY KEY(Login_ID)
);
USER_NAME VARCHAR(255),
USER_EMAIL VARCHAR(255),
USER_MOBILE INT,
USER_ADDRESS VARCHAR(255),
PRIMARY KEY(USER_ID)
);
Role_Name VARCHAR(255),
Role_desc VARCHAR(255),
PRIMARY KEY(Role_id)
);
PER_NAME VARCHAR(255),
PER_MODULES VARCHAR(255),
PRIMARY KEY(PER_ID)
);
ALU_DESC VARCHAR(255),
ALU_TYPE VARCHAR(255),
PRIMARY KEY(ALU_ID)
);
STU_NAME VARCHAR(255),
STU_EMAIL VARCHAR(255),
STU_MOBILE INT,
PRIMARY KEY(STU_ID)
);
CO_NAME VARCHAR(255),
CO_DESC VARCHAR(255),
PRIMARY KEY(CO_ID)
);
n
AFTER NORMALIZATION
1. First Normal Form (1NF): All tables have atomic values, meaning each
column contains only indivisible values.
2. Second Normal Form (2NF): All non-key attributes are fully functional
dependent on the primary key. In our schema, each table has a primary key,
and non-key attributes depend on it.
3. Third Normal Form (3NF): There are no transitive dependencies. Each non-
key attribute is directly dependent on the primary key. In our schema, we've
avoided transitive dependencies by splitting data into separate tables.
Here, We have introduced a new foreign key ALU_ID in the Student table to reference the
alumni to which the student belongs. This normalization ensures that the Student table is not
indirectly dependent on the Alumni table.
PRIMARY KEY(Login_ID)
);
USER_MOBILE VARCHAR(20),
USER_ADDRESS VARCHAR(255),
PRIMARY KEY(USER_ID),
);
Role_desc VARCHAR(255),
PRIMARY KEY(Role_id)
);
PER_MODULES VARCHAR(255),
PRIMARY KEY(PER_ID)
);
ALU_TYPE VARCHAR(255),
PRIMARY KEY(ALU_ID)
);
STU_MOBILE VARCHAR(20),
PRIMARY KEY(STU_ID),
);
CO_DESC VARCHAR(255),
PRIMARY KEY(CO_ID)
);