The document describes a proposed college placement management system that aims to automate the manual processes currently used. It discusses how the existing manual system is time-consuming and prone to errors. The proposed system would use a database to store and organize student and company information, and automatically match eligible students to company requirements. Key aspects like database structure, interface for different users, and use of Oracle 10g for management are covered at a high level.

1. DATABASE MANAGEMENT CASE STUDY
TOPIC:“COLLEGEPLACEMENTMANAGEMENT SYSTEM”
Department of Computer Science
C. V. RAMAN GLOBAL UNIVERSITY,
BHUBANESWAR

2. INTRODUCTION
• Manual Training and Placement which is done at various colleges is by human intervention due to which there is a
maximum chance of errors. The major problem is searching and updating of the student data. Placement officers
have to manage the student’s profile and their documents. Placement Officer has to collect the information of
various companies who comes for recruitment. They have to arrange profiles of students according to various
streams and notify them each time according to company requirements. Placement officers submit the information
of students and if any changes or updates are required in the profile of any student, it has to be done manually. This
process is so difficult and tedious when the number of users increases. This is tedious and time consuming. Chances
of missing data are also possible. It is also difficult for collecting, managing, and updating student data as the
number of students increases. ’Placement Management System’ like many other placement management web sites,
provides information on placement providers and the placements and also keeps up to date information of all
students. It is a platform where students can view and assess their opportunities. The system will be having
different types of accounts for different types of users such as Admin, Student, HODs, and tutor. A profile for each
student is created with the necessary credentials for the portal. The system uses Oracle 10g for database
management and will sort the data of the student based on eligibility criteria demanded by the respective
companies and a list of eligible candidates will be prepared and they can choose if they are interested to attend that
particular drive or test. Based on this a final data-set is created and the interested candidates will be registered
automatically by the system. This way it reduces the work of college staff or faculty from the problems caused by
human error and wastage of time doing all processes manually.
2

3. Abstract of the Project College Placement
Management System:
From a student’s perspective, placements can bring a wide range of benefits and
opportunities. Training and management of placement is a crucial part of an educational
institution in which most of the work is done manually. Manual system in the colleges
requires a lot of manpower and time. With this project we aim to develop a web portal to
solve this issue. The project is aimed at developing an application for the placement
department of the college. The system is an application which will be accessed and
effectively used throughout the organization with proper login enabled. It can also be used
as an application for the Placement Officers in the college to manage the student
information about placement thus reducing the manual work and consumes less paperwork.
The system also provides the facility of viewing the personal and academic information of
the student. The system gets the requested list of candidates for the companies who would
like to recruit the people according to their eligibility criteria. Laravel framework is used to
facilitate the process of making the program.
3

4. Objective of Project on College Placement
Management System:
4
• The main objective of the placement management system is to reduce
manual work and time. It is difficult and time-consuming to collect all
the details from each student. To avoid this problem, we have planned to
develop a web-based placement management system.
• Easy to find out the list of eligible students attending the drives
• It manages the details of student records, placement training, different
placements happening in and out of the college.
• Saves the time of placement officer and faculties.
• Reduces the manual works.
This system makes student information more secure.

5. Requirement Analysis are as follows:
Software requirement
Oracle 10g--Oracle Database 10g is the first database designed for enterprise grid
computing, the most flexible and cost effective way to manage information and
applications
System Requirements for Oracle 10g:
Architecture 32 bit or 64 bit
Windows OS : Windows 2000 with SP 1 or higher
Windows Server 2003
-Windows XP Professional
-Windows 10,11 Network protocol
- TCP/IP - TCP/IP with SSL
-Named Pipes
200 MHz minimum

6. Hardware Requirements:
Physical memory (RAM) 512 MB recommended
Virtual memory
Double the amount of RAM Temp disk space
Hard disk space 1.5 GB Video adapter
256 colors CPU Processor
200 MHz minimum

7. Problem Statement:
6
A placement cell contains the details of all the students studying in that organization. A
student is identified by different attributes like Student_regdno, Student_name,
Student_branch,Student_cgpa, Student_phone, Student_Email . A student can be placed in
many companies as per the requirements set by the company. Similarly a company have
many attributes like C_Id,C_Name,Cgpa,C_location. A student gets placed in the company
with the help of the placement cell which have details of both the student and the company.
We can get the details of every student placed in the company.
Existing System: -
 In colleges the records were stored in excel sheets hence sorting the data was always a
problem. The excel sheets are also less advanced. Hence sorting and searching problem
arises. Updates records is another tedious task.
 Another problem student faces are that they are not made aware of the training and
placement activity held in their intuitions hence there might have been a loss of
opportunities. The best solution here is to computerize the current environment.

8. Proposed System: -
 With the growth of technology, it is easy for the students as well as the companies
to get the information of newer placement programs.
 And this System also helps the placement cell to keep track of the data of the
students and the recruiting companies.
This System uses SQL (Oracle 10g) for Database management and will sort the
data of student based on eligibility criteria demanded by the respective
companies.

9. Table Description with all Constraints:
• Student Entity : Attributes of Student are STUDENT_NAME,
STUDENT_REGNO,STUDENT_BRANCH,STUDENT_CGPA,STUDENT_PHON
E,STUDENT_EMAIL.
• STUDENT_NAME: It will store the Name of the given Student.
• STUDENT_REGNO: It will store the Registration no. of the given Student.
• STUDENT_BRANCH: It will store the Branch of the given Student.
• STUDENT_CGPA: It will store the CGPA of the given Student.
• STUDENT_PHONE: It will store the phone no. of the given Student.
• STUDENT_EMAIL:It will store the mail id of the given Student.

10. Given below is the Student Table:

11. Table Description with all Constraints:
Company Entity : Attributes of Company are
C_NAME,C_ID,CGPA,C_LOCATION.
• C_NAME: It will store the Company Name of the given company.
• C_ID: It will store the Company ID of the given company.
• CGPA: It will store the CGPA of the Student.
• C_LOCATION: It will store the Location of the given company.

12. Given Below is the Company Table:

13. Table Description with all Constraints
Placement Cell Entity : Attributes of Placement cell are
P_ID,DEPARTMENT,STUDENT_REGNO,C_ID.
• P_ID: It will store the Placement id of the given placement cell entity.
• DEPARTMENT: It will store the Department of the given placement cell
entity.
• STUDENT_REGNO: It will store the Student registration no.
• C_ID: It will store the Company id.

14. Given below is the Placement Cell Table:

15. ER Diagram:
This ER (Entity Relationship) Diagram represents
the model of College Placement Management
System Entity. The entity-relationship diagram of
College Placement Management System shows all
the visual instrument of database tables and the
relations between Students, Company etc. It used
structure data and to define the relationships
between structured data groups of College
Placement Management System functionalities.
The main entities of the College Placement
Management System are Students, Company, and
Placement Cell.

16. Symbols used in ER – Diagram:

17. ATTRIBUTES USED:
 Student Entity : Attributes of Student are STUDENT_NAME,
STUDENT_REGNO,STUDENT_BRANCH,STUDENT_CGPA,STUDENT_PHONE,STU
DENT_EMAIL.
 Company Entity : Attributes of Company are
C_NAME,C_ID,CGPA,C_LOCATION.
 Placement Cell Entity : Attributes of Placement cell are
P_ID,DEPARTMENT,STUDENT_REGNO,C_ID.

18. KEYS:
 STUDENT STUDENT_REGDNO (PRIMARY KEY)
 COMPANY C_ID(PRIMARY KEY)
 PLACEMENT_CELL P_ID(PRIMARY KEY)
 PLACEMENT_CELL (STUDENT(STUDENT_REGDNO)FOREIGN KEY)
 PLACEMENT_CELL (COMPANY(C_ID)FOREIGN KEY)

19. STUDENT
STUDENT_PHOINE
STUDENT_EMAIL
STUDEN
T_CGPA
STUDENT_BR
ANCH
STUDENT
_NAME
STUDENT_REGDNO
GET
PLACED
COMPANY
C_NAME
CGPA C_LOCATION
C_ID
MANAGE
PLACEMENT
CELL
MANAGE
P_ID
DEPARTMENT
STUDENT_
REGDNO
C_ID

20. Relationship:
Student get placed in company. so cardinality ratio is 1:1.
Placement cell manages many student. so cardinality ratio is 1:N.
company
places student
Placement cell
manages student
Placement cell manages many company. so cardinality ratio is 1:N
Placement cell manages company

21. Relational Database
Schema

22. STUDENT_REGDNO STUDENT_NAME STUDENT_BRANCH STUDENT_CGPA STUDENT_EMAIL STUDENT_PHONE
C_ID C_NAME CGPA C_LOCATION
STUDENT
COMPANY
P_ID C_ID STUDENT_REGDNO DEPARTMENT
PLACEMENT CELL

23. Normalization:
Normalization is the process of reorganizing data in a database so that it meets
two basic requirements: There is no redundancy of data, all data is stored in
only one place. Data dependencies are logical,all related data items are stored
together.
Tables in database are designed to use third normal form (3NF), AS we know
that to use third normal form our table must satisfy the requirement of first
normal form ((1NF) and second normal form (2NF).Most of the tables in
database have been designed to keep optimization in mind. We use
normalization to remove update, delete & insert anomalies.

24. 1nf :
By implementing First Normal formal we have to check that there should be no
multiple values against any field of a table and we have to create a separate
table for each set of related data with unique primary key.
 A table is referred to as being in its First Normal Form if atomicity of the table
is 1.
 Here, atomicity states that a single cell cannot hold multiple values. It must
hold only a single-valued attribute.
 The First normal form disallows the multi-valued attribute, composite
attribute, and their combinations.

25. Student Table

26. Normalized Table

27. 2nf:
For 2nd Normal form the non key attributes should be fully dependent on
composite primary key, partial dependency is not allowed. First we
created two tables from above tables to associate with repeating group of
data and relate them with foreign key.
The first condition for the table to be in Second Normal Form is that the
table has to be in First Normal Form. The table should not possess partial
dependency. The partial dependency here means the proper subset of
the candidate key should give a non-prime attribute.

28. 2 NF
28
Student Name C_ID
Ram Singh 104
Sanjeev Kumar 102
Ram Singh 105
Ritika Mishra 106
Student name P_ID
Ram Singh 6
Sanjeev Kumar 3
Ritika Mishra 18
As per the second normal form definition,
our enrollment table above isn’t in the
second normal form. To achieve the same
(1NF to 2NF), we can rather break it into 2
tables:
Here the second column is unique and it indicates the C_ID for the student.
Clearly, the C_ID is unique. Now, we can attach each of these C_ID with
P_ID.

29. 2 NF
29
C_ID P_ID
104 6
102 3
105 6
106 18
These 2 tables together provide us with the exact same information as
our original table.

30. TEAM DETAILS:
o RUDRA PRATAP PATRA – 20010595
o PRIYANSHU PATRA – 20010596
o RITIKA MISHRA – 20010597
o NOVLESH PRADHAN - 20010598

31. Thank You