EX NO : 14 DESIGN OF ADMISSION MANAGEMENT SYSTEM

DATE :

AIM:
The aim of this experiment is to design and construct an Entity-Relationship (ER)
model and ER diagram tables for the Admission Management System.

REQUIREMENTS:
❖ Hardware Requirements: Intel Based desktop PC with minimum of 166 MHZ or faster
processor with at least 1GB RAM and 500 MB free disk space.
❖ MySQL 5.6.1

PROCEDURE:
(i) Identifying Entities and Attributes:
➢ Analyze the application domain and identify relevant entities and their
attributes.
➢ Create a list of entities and their respective attributes based on the
requirements.

(ii) Defining Relationships:

➢ Identify relationships between entities (e.g., one-to-one, one-to-many,
many-to-many).
➢ Determine the cardinality and participation constraints for each relationship.

(iii) Constructing the ER Diagram:

➢ Use an ER diagramming tool to create an Entity-Relationship (ER) diagram.
➢ Represent entities as rectangles, attributes as ovals connected to entities, and
relationships as diamonds connecting related entities.
➢ Label each relationship with cardinality and participation constraints (e.g., 1:1,
1:N, M:N).

(iv) Refining and Validating the ER Model:

➢ Review the ER diagram for completeness and correctness.
➢ Ensure that all entities, attributes, and relationships are properly represented.
➢ Validate the model to ensure data integrity and consistency.

(v) Documenting the ER Model:

➢ Provide a detailed description of each entity, including its attributes and
relationships.
➢ Document cardinality and participation constraints for each relationship.
➢ Include any additional notes or considerations related to the ER model.

53
ENTITIES:

❖ Student
➢ Attributes:
● StudentID (Primary Key),
● Name,
● Address,
● Email,
● Phone,
● DateOfBirth
❖ Course
➢ Attributes:
● CourseID (Primary Key),
● CourseName,
● Credits

RELATIONSHIPS:

❖ Enrollment
➢ Links Student and Course entities
➢ Attributes: EnrollmentID (Primary Key), StudentID (Foreign Key), CourseID
(Foreign Key), Semester, Year, Grade, etc.

❖ Belongs_to Links Faculty and Department entities

➢ Attributes: BelongsID (Primary Key), FacultyID (Foreign Key), DepartmentID
(Foreign Key), Position (e.g., Professor, Assistant Professor), etc.

PRIMARY KEY ATTRIBUTES:

1. StudentID (Student Entity)

2. CourseID (Course Entity)

E-R Model
Attributes of the following Entities
(i) STUDENT
❖ StudentID (Primary Key)
❖ Name
❖ Address
❖ Email
❖ Phone
❖ Date Of Birth
❖ Gender
SCHEMA
Student: StudentID (Primary Key), Name, Address, Email, Phone, DateOfBirth

54
TABLE NAME: STUDENT

Field Description Type Length

stud_ID (PK) Student ID Int 11

Stu_name Student Name Varchar 255

Stu_contact Student Mobile Number Int 11

stu_email Student Email 255 255

Date_of_Birth Student Date of Birth Int 08

stu_program Student Program Varchar 255

Stu_Gender Student Gender Varchar 255

Stu_Address Student Address Varchar 255

(ii) COURSE
❖ CourseID (Primary Key),
❖ CourseName,
❖ Credits
❖ Course Type

SCHEMA
Course: CourseID (Primary Key), CourseName, Credits, Course Type

55
TABLE NAME: COURSE

Field Description Type Length

Course_ID (PK) Course ID Int 11

Course_name Course Name Varchar 30

Course_desc Course Description Varchar 30

Course_type Course type varchar 30

Course_std_ID Student ID int 11

(iii) REGISTRATION
❖ Reg_ID (Primary Key)
❖ Reg_desc
❖ Reg_type
❖ Reg_date

SCHEMA
Registration: Reg_ID (Primary Key), Reg_desc, Reg_type, Reg_date

TABLE NAME: REGISTRATION

Field Description Type Length

Reg_stu_ID Student registration ID int 11

Reg_ID Registration ID int 11

Reg_desc Description about registration varchar 255

Reg_type Type of registration varchar 30

Reg_date Date of registration varchar 30

56
(iv) PERMISSION
❖ Per_id (Primary Key)
❖ Per_role_id
❖ Per_module
❖ Per_name

SCHEMA
Permission: Per_id (Primary Key), Per_role_id, Per_module, Per_name

TABLE NAME: PERMISSION

Field Description Type Length

Per_id Permission id varchar 255

Per_role_id Permission role id varchar 255

Per_module Permission module Varchar 255

Per_name Permission name Varchar 255

(v) ROLES
❖ Role-id (Primary Key)
❖ Role_name
❖ Role_desc

SCHEMA
Roles: Role-id (Primary Key), Role_name, Role_desc

57
TABLE NAME: ROLES

Field Description Type Length

Role-id Role id varchar 255

Role_name Role name varchar 255

Role_desc Role decription varchar 255

(vi) LOG-IN
❖ Login-ID (Primary Key)
❖ Login-role-ID
❖ Login_username
❖ Login_password

SCHEMA
Login: Login-ID (Primary Key), Login-role-ID, Login_username, Login_password

TABLE NAME: LOG-IN

Field Description Type Length

Login-ID Login ID Varchar 255

Login-role-ID Login-role ID Varchar 255

Login_username User name Varchar 255

Login_password Password Varchar 255

58
 ER DIAGRAM FOR ADMISSION MANAGEMENT SYSTEM

Student Table:
❖ The Student table stores student details such as ID, name, contact information,
and password.
❖ It's crucial for managing student records, enrollment, and authentication.

Course Table:
❖ Courses' essential information like ID, name, description, type, and student
enrollment details are stored here.
❖ It aids in course management and tracking student enrollments.

College Table:
❖ This table holds data about colleges within the university, including IDs,
descriptions, and types.
❖ It’s useful for organizing academic units and resource allocation.

Registration Table:
❖ Tracks student registrations with ID, description, type, and registration date.
❖ It's pivotal for monitoring enrollment trends and managing course capacities.

Permission Table:
❖ Manages access permissions with unique IDs, role associations, module
details, and permission names.
❖ It ensures secure data access and user management.

59
Roles Table:
❖ Defines roles with IDs, names, and descriptions.
❖ It's essential for role-based access control and user administration.

Log-In Table:
❖ Logs login activities with unique IDs, role associations, usernames, and
passwords.
❖ It’s critical for security monitoring and audit trails.

Result Table:
❖ The Result table tracks academic performance by storing data such as ResultID
(unique identifier), linked StudentID and CourseID for student-course
associations, Semester and Year to denote when the course was taken, and
Grade to record the student's performance.
❖ This table enables efficient management and analysis of student results within
the Admission Management System.

RESULT:
Hence, the Entity-Relationship (ER) model and ER diagram tables were successfully
designed for the Admission Management System.

60
 EX NO : 15 DEPLOYMENT OF ADMISSION MANAGEMENT SYSTEM

DATE :

AIM:
To integrate a robust database management system aimed at streamlining university
operations, including managing student records, course information, and
administrative tasks effectively.

(i) ADMIN PAGE

TABLE CREATION:

CREATE TABLE admin (

id int(11) NOT NULL,
username varchar(100) NOT NULL,
password varchar(100) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1 COLLATE=latin1_swedish_ci;
This SQL code creates a table named admin with three columns:
❖ id of type integer, serving as the primary key.
❖ username of type varchar(100), storing the username of administrators.
❖ password of type varchar(100), storing the hashed passwords of administrators.

DATA INSERTION:
INSERT INTO admin (id, username, password) VALUES (1, 'admin',
'202cb962ac59075b964b07152d234b70');
❖ This SQL code inserts two rows of data into the admin table.
❖ The first row has id 1, username 'admin', and the same hashed password.
('202cb962ac59075b964b07152d234b70').
SQL TABLE :

61
USER INTERFACE:

(ii) STUDENT DATABASE PAGE

TABLE CREATION:

CREATE TABLE st_info (

st_id int(11) NOT NULL,
name varchar(100) NOT NULL,
password varchar(32) NOT NULL,
email varchar(50) NOT NULL,
bday date NOT NULL,
program varchar(10) NOT NULL,
contact varchar(20) NOT NULL,
gender varchar(10) NOT NULL,
address varchar(255) NOT NULL,
img varchar(255) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1 COLLATE=latin1_swedish_ci;

Student information Table has several columns:

❖ st_id: An integer serving as the primary key for identifying students.
❖ name: A varchar(100) field for storing the names of students.
❖ password: A varchar(32) field for storing the hashed passwords of students.
❖ email: A varchar(50) field for storing the email addresses of students.
❖ bday: A date field for storing the birthdays of students.
❖ program: A varchar(10) field for storing the program or course enrolled by the
students.
❖ contact: A varchar(20) field for storing the contact numbers of students.
❖ gender: A varchar(10) field for storing the gender of students.
❖ address: A varchar(255) field for storing the addresses of students.

62
 ❖ img: A varchar(255) field (nullable) for storing image file names or paths related to
students.
The table uses the InnoDB engine with a default character set of Latin1 and collation
latin1_swedish_ci.

DATA INSERTION:
INSERT INTO st_info (st_id, name, password, email, bday, program, contact, gender,
address, img) VALUES
(23011, 'Praveen V',
'ceec1b7bb465741becf6c09d5361249a',’Praveenvignesh2001@gmail.com',
'2001-03-30', 'MTech - CS', '9940199447', 'Male', 'Korattur',
'71E9C62A-C144-9916-D357-8EBCDF77C2C4.jpg');
-- Several rows of student data are inserted here,
(23004, 'Madhavan V', '73d8fbed9c39995b371b394c71b5e962',
'maddy2k2@gmail.com', '2002-02-07', 'MTech - CS', '9841131412', 'Male',
'Chromepet', '763CD630-8AC4-FF35-1855-3254E11CB3AF.jpg'),
;

❖ This part of the code inserts rows of data into the st_info table, providing information
about different students.
❖ Each row includes values for st_id, name, password (hashed), email, bday (birthdate),
program, contact, gender, address, and optionally img.

SQL TABLE :

63
USER INTERFACE:

(iii) COURSE PAGE

TABLE CREATION:
CREATE TABLE `tbl_course` (
`cid` int(11) NOT NULL,
`cshort` varchar(250) NOT NULL,
`cfull` varchar(250) NOT NULL,
`cdate` varchar(50) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

This SQL statement creates a table named tbl_course with four columns:
❖ cid: An integer field serving as the primary key for the course records.
❖ cshort: A varchar(250) field storing the short name or abbreviation of the course.
❖ cfull: A varchar(250) field storing the full name of the course.
❖ cdate: A varchar(50) field storing the date when the course was introduced.
❖ The table is configured to use the InnoDB storage engine with a default character set
of Latin1.

DATA INSERTION:
INSERT INTO `tbl_course` (`cid`, `cshort`, `cfull`, `cdate`) VALUES
(10, M.TECH', 'MASTER OF TECHNOLOGY', '12-04-2016'),
(11, 'M.B.A', 'MASTER OF BUSINESS ADMINISTRATION', '17-04-2016');
❖ This part of the code inserts rows of data into the tbl_course table. Each INSERT
INTO statement adds a row to the table, providing values for the cid, cshort, cfull, and
cdate columns. In this case, five rows of data are being inserted, each representing a
different course along with its abbreviation, full name, and introduction date.
❖ Each row includes values for id, st_id, marks, sub, and semester.

64
SQL TABLE :

USER INTERFACE:

RESULT:
Hence, The Deployment of the Admission Management System involves designing
the database, creating the model, SQL Tables and implementing the model to ensure effective
data management.

65