Mid-Term Report

ON

College Placement System

IN

Computer Science and Engineering

Submitted in partial Fulfillment of the Degree
OF
BE(CSE)

Under the Guidence of: Submitted By

Name: Mr Himanshu Name: Deepika

Department: CSE University Id:
2111981338

Department of Computer Science and Engineering

 ACKNOWLEDGEMENT

I would like to express my heartfelt gratitude to Chitkara University

and the Department of Computer Science and Engineering for
providing an excellent learning environment and the resources needed
to complete this project on a College Placement System website. I am
especially grateful to my project supervisor, whose guidance, insights,
and feedback were invaluable in shaping the direction of this project
and in overcoming various challenges along the way. I would also
like to thank my professors and mentors for imparting the
foundational knowledge and technical skills necessary for this
undertaking. Additionally, my heartfelt appreciation goes out to my
family and friends for their unwavering encouragement, which kept
me motivated throughout the development process. This project has
been an invaluable experience that deepened my understanding of
real-world applications and enhanced my practical skills in the MERN
stack. Thank you to everyone who played a role, directly or indirectly,
in the successful completion of this project.

Department of Computer Science and Engineering

 PREFACE
Our project, College Placement Management System, is designed to
manage the registration of students, store their details, and facilitate
their placement processes. The software assigns a unique ID to each
student and keeps track of all students and placement staff
information. Through the system, users can check the availability of
job openings, companies visiting for campus placements, and student
placement records using their unique IDs.
The College Placement Management System can be accessed through
a username and password, ensuring security and restricted access.
Only authorized users, such as administrators and placement officers,
have permission to add data into the database. The system allows for
efficient data retrieval with a user-friendly interface, which helps
streamline data management and processing.
The system comprises two primary modules. One is at the
Administrative Level, managing company and student information,
and the other is at the User Level, including access for students and
company representatives. The application maintains authentication
protocols to ensure secure access. The administrator's tasks include
managing details related to student profiles, job postings, and
placements. A dedicated database was designed for both students and
companies, accessible only to authorized users.
Students can view available job opportunities, apply for roles, and
check their placement status through the student module.

Department of Computer Science and Engineering

 CONTENT

[Link] (5)
[Link] Study (6)
[Link] Analysis (7)
4. Risk Management (9)
5. Project schedule (10)
5. Diagrams (11)
6. Testing (15)
[Link] (19)

Department of Computer Science and Engineering

OFFER LETTER

Department of Computer Science and Engineering

 INTRODUCTION

This software will help colleges streamline the placement process by efficiently
managing student registrations, job applications, and interview schedules. It
enables placement officers and administrators to view and modify placement
schedules as needed. The purpose of this project is to computerize all details
related to student placement, company visits, and job offers.
The College Placement Management System serves educational institutions
such as colleges and universities, facilitating better organization and
communication within placement cells. The primary goal of this system is to
improve the placement process, increasing the number of students successfully
placed by providing an organized and secure platform for handling all
placement-related activities.
In a file-based placement management system, considerable effort is required to
secure physical records, which are vulnerable to risks like misplacement, natural
disasters, and other forms of data loss. By digitizing the placement process, this
system offers secure, efficient, and easily accessible data management,
minimizing the risks associated with traditional, manual systems.

Department of Computer Science and Engineering

 FEASIBILITY STUDY
1. Technical Feasibility:

o A College Placement Management System (CPMS) is a comprehensive

project, especially when developed with the MERN stack (MongoDB,
Express, React, [Link]).

o The CPMS would need to manage student data, company scheduling, job
applications, interview scheduling, and result tracking.

o Technical Skills: Given the popularity of the MERN stack, it’s feasible to find
developers proficient in it, which supports the scalability and maintainability
of the system for future updates and enhancements.

2. Legal Feasibility:

o Data Privacy Compliance: MERN-based applications can comply with data

privacy laws (such as GDPR) by implementing secure authentication and
encryption features using tools like JWT. This ensures that sensitive student
and company data is protected.

3. Operational Feasibility:

o Operational feasibility assesses whether the College Placement Management

System (CPMS) can be efficiently implemented and maintained within the
institution, given available resources, personnel, and processes. This involves
evaluating how placement officers, students, and administrators can adapt to
and benefit from this system, enabling smoother and more efficient placement
operations.

Department of Computer Science and Engineering

 REQUIREMENT ANALYSIS

Software Requirements:

• React for building the user interface, providing a smooth, interactive experience.

• Axios to handle HTTP requests between the frontend and backend seamlessly.

• React for displaying user-friendly notifications, enhancing app usability.

• [Link] and [Link] for server-side operations, enabling API management and routing.

• Postman for testing API endpoints during development to ensure proper backend
functionality.

• MongoDB, NoSQL database to store hospital data (patient records, appointments, medical

history) in a scalable format.

Hardware Requirements:

• Development System: A PC or laptop with at least an Intel i5 processor or equivalent for

efficient coding, testing, and multitasking during development.

• RAM: Minimum 8GB RAM to handle software like [Link], MongoDB, and code editors

without lags.

• Storage: At least 256GB SSD storage for faster loading and saving of files, databases, and

project dependencies.

• Internet Connectivity: Stable internet connection for API requests, testing, and server
access.

Department of Computer Science and Engineering

 Risk Management
Risk management is the process of identifying, assessing and controlling threats to a
organization's capital and earnings. These threats, or risks, could stem from avoid variety of
sources, including financial uncertainty, legal liabilities, strategic management errors,
accidents and natural disasters. The ISO recommended the following target areas, or
principles, should be part of the overall risk management process:

● The process should create value for the organization.

●
● It should be an integral part of the overall organizational process.
●
● It should factor into the company's overall decision-making process.
●
● It must explicitly address any uncertainty.
●
● It should be systematic and structured.
●
● It should be based on the best available information.

Risk Management Strategies and Process:

All risk management plans follow the same steps that combine to make up the overall risk
management process:

Risk identification
The company identifies and defines potential risks that may negatively influence a specific
company process or project.

Risk analysis
Once specific types of risk are identified, the company then determines the odds of it
occurring, as well as its consequences. The goal of the analysis is to further understand each
specific instance of risk, and how it could influence the company's projects and objectives.

Overview of risk mitigation, monitoring and management Risk Mitigation:

During this step, companies assess their highest-ranked risks and develop a plan to alleviate them
using specific risk controls. These plans include risk mitigation processes, risk prevention tactics and
contingency plans in the event the risk comes to fruition.

Risk Monitoring: -

Part of the mitigation plan includes following up on both the risks and the overall plan to
continuously monitor and track new and existing risks. The overall risk management process
should also be reviewed and updated accordingly.

Department of Computer Science and Engineering

Project Schedule
The biggest benefit of automation is that it saves labor. Our main objective was to save
energy and materials and to improve quality, accuracy and precision with the help of this
portal. According to our survey with the TnP coordinators (TPCs) on most tough and
annoying job that they have to do while working for TnP department and what features they
would like to see in the TnP web portal. Problems faced in existing system according to the
survey conducted is as follows:
• Notifying the students
• Writing Invites to the companies
• Mailing each and every student about company details and other information.
• Providing list of eligible students as per company format which is different for
each and every company.

Department of Computer Science and Engineering

 System Design
Architecture Diagram:

Department of Computer Science and Engineering

Use Case Diagram:

Department of Computer Science and Engineering

Class Diagram:
Class diagrams are one of the most useful types of diagrams in UML as they clearly
map out the structure of a particular system by modeling its classes, attributes,
operations, and relationships between objects.
Class diagrams offer a number of benefits for any organization. Use UML class
diagrams to:

● Illustrate data models for information systems, no matter how simple or

complex.
Better understand the general overview of the schematics of an application.

Class Diagram
Class diagrams are one of the most useful types of diagrams in UML as they clearly
map out the structure of a particular system by modeling its classes, attributes,
operations, and relationships between objects.
Class diagrams offer a number of benefits for any organization. Use UML class
diagrams to:

● Illustrate data models for information systems, no matter how simple or

complex.
Better understand the general overview of the schematics of an application.
Event Management :
[Link]’s login. Admin can update the details of student & receiver, able
to add events, can gives the approvals, uploads material, view student’s

Department of Computer Science and Engineering

details, able to add students, receives(recruiters),can mail to students &
receivers.
[Link]’ login. student’s
can change & update the details, able to change
their passwords and usernames, can mail to the admin.
[Link]’s login. Receiver’s view the details of students, can mail to the
admin.

Activity Diagram
Activity diagram is another important diagram in UML to describe the dynamic
aspects of the system. Activity diagram is basically a flowchart to represent the flow
from one activity to another activity. The activity can be described as an operation
of the system. The control flow is drawn from one operation to another. This flow
can be sequential, branched, or concurrent.
The purpose of an activity diagram can be described as

● Draw the activity flow of a system.

● Describe the sequence from one activity to another.
● Describe the parallel, branched and concurrent flow of the system.

Department of Computer Science and Engineering

Collaboration Diagram
A collaboration diagram, also called a communication diagram or interaction
diagram, is an illustration of the relationships and interactions among software object
is in the Unified Modeling Language (UML). A collaboration diagram is a type of
visual presentation that shows how various software objects interact with each other
within an overall IT architecture and how users can benefit from this collaboration.
A collaboration diagram often comes in the form of a visual chart that resembles a
flow chart. It can show, at a glance, how a single piece of software complements
other parts of a greater system.

Testing
In order to uncover the error present in different phases we have the concept of level
of testing. The basic levels of testing are

UNIT TESTING: -
It focuses verification effort on the smallest unit of software i.e. the module. Using
the detailed design & the process. Specification testing is done to uncover the error
within the boundary of the module. All modules must be successful in the unit test
before the start of integration testing begins.

INTEGRATION TESTING:-
After the unit testing we have to perform the integration testing. The goal here is to
see if the module can be integrated properly, the emphasis begins on the testing

Department of Computer Science and Engineering

 between module this testing activity can be considered as testing the design & hence
the emphases on testing module interaction.
SYSTEM TESTING: -
Here the entire software system is tested. The reference document for this process is
the requirement document, & the goal of operating system to see if software meets
its requirements.
ACCEPTANCE TESTING: -
It is performed with realistic data of the client to demonstrate that the software is
working satisfactorily. Testing here is focused on external behavior of the system:
the internal logic of the program is not emphasized.
WHITE BOX TESTING: -
This is the unit testing method where a unit will be taken at a time & tested
thoroughly at a statement level to find the maximum possible error.

BLACK BOX TESTING: -

This testing method considered a module as a single unit and checks the unit as
interface and communication with other module rather getting into details at
statement level. Here the module will be treated as black box that will take some
input and generate output. Output for given set of input combination are forwarded
to the other module.
Testing Plan
Software testing is a critical element of software quality assurance and represents
the ultimate review of specification, design and coding. Testing presents an
interesting anomaly for the software engineer.

Testing Objective includes

Testing is a process of executing a program with the intent of finding an error.
A good test case is one that has a probability of finding an as yet undiscovered
error. A successful test is one that uncovers an undiscovered error.

Testing Principles
-All tests should be traceable to end user requirements
-Tests should be planned long before testing begins
-Testing should begin on a small scale and progress towards testing in large.
-Exhaustive testing is not possible
-To be most effective testing should be conducted by an independent third
party.

Test results
WHITE BOX TESTING
(also known as Clear Box Testing, Open Box Testing,
Glass Box Testing, Transparent Box Testing, Code-Based Testing or Structural
Testing) is a software testing method in which the internal
structure/design/implementation of the item being tested is known to the tester. The
tester chooses inputs to exercise paths through the code and determines the
appropriate outputs. Programming know-how and the implementation knowledge is
essential. White box testing is testing beyond the user interface and into the nitty-
gritty of a system. This method is named so because the software program, in the
eyes of the tester, is like a white/transparent box; inside which one clearly sees
.

Department of Computer Science and Engineering

BLACK BOX TESTING:
also known as Behavioral Testing is a software testing method in which the internal
structure/design/implementation of the item being tested is not known to the tester. These
tests can be functional or non-functional, though usually functional.

This method is named so because the software program, in the eyes of the tester, is
like a black box; inside which one cannot see.
Black Box testing method is applicable to the following levels of software testing:

● Integration Testing
● System Testing
● Acceptance Testing

UNIT TESTING:
Unit testing concentrates verification on the smallest element of the program the
module. Using the detailed design description important control paths are tested to
establish errors within the bounds of the module. In this system each sub module is
tested individually as per the unit testing such as campaign, lead, contact etc are
tested individually. Their input field validations are tested.
INTEGRATION TESTING:
Once all the individual units have been tested there is a need to test how they were
put together to ensure no data is lost across interface, one module does not have an
adverse impact on another and a function is not performed correctly. After unit
testing each and every sub module is tested with integrating each other.
SYSTEM TESTING FOR CURRENT SYSTEM:
Modules of the project. We are testing whether system is giving correct output or
not. All the modules were integrated and the flow of information among different
modules was checked. It was also checked that whether the flow of data is as per the
requirements or not. It was also checked that whether any particular module is non-
functioning or not i.e. once the integration is over each and every module is functioning in its
entirety or not. In this level of testing we tested the following: - Whether all the forms are
properly working or not. Whether all the forms are properly linked or not. Whether
all the images are properly displayed or not. Whether data travel is proper or not.

Department of Computer Science and Engineering

Conclusion and Future Scope
Summary & Conclusion
Our proposed system work according to IEEE paper. It can successfully login
authorized person to system and register them. In our system admin can check the
Student list those eligible according to criteria given by the Company and notify
them instantly and update the information anytime successfully. Our system is
Secure and User-friendly for all of three modules.
Increasing need of comfort and inculcating all the data at one place has always been
a challenging process for everybody. With the introduction of this web based
training and placement portal we promise to make the lives of students and
administration a little easier by proposing an alternative for the current system being
used. Easy accessibility and functioning of this portal will allow easy management
of the allocation process during placement period. With the increasing demand of
digitalization in every aspect of day to day activities we can anticipate the great
demand for such portals in the near future and the comfort it will bring with it to the
lives of all. Also the rapidly increasing concerns of global warming due to increase
deforestation for large amount of paper that it requires we here have a minor role to
save Mother Nature. So we hope all of you can sit back and relax and enjoy the
luxury of Digitalization. More so in this busy and exhausting life we are saving one
of the most crucial factor that keeps us running that is human energy.

Future Scope
The main aim of developing this website was to reduce maximum chances of errors
in manual work.

Save time for the process. Also students get notified by the SMS instantly.
Other features such as giving notification to students about the jobs that are available
both on and off campus can be included in the upgraded versions. The system cannot
provide the SMS integration. Hence, it can be modified to give the SMS integration.
Other features like analytics can be added in future to this portal for tracking the
progress of student in specific areas. After analysis this system will notify students
of the areas they are lacking in.

Limitations of project work

● Internet is necessary.

Department of Computer Science and Engineering

 Reference / Bibliography
[Link] K," Human Resource Management", Tata McGraw Hill, sixth edition,
2011.
[Link] Dar et al., " Skill Development in India the Vocational Education and
Training System", Human Development Unit South Asia Region the World Bank. 5-
10, 2006.
[Link] Mantri, Sunil Dutta et al., "imbedding soft skills in technical studies: The
problem based learning way", The Indian Journal of Technical Education, Vol. 30,
pp. 79-83, 2007.

[Link], Jorden BPB Publications (2000) - “Mastering SQL Server”

5. Luke Welling and Laura Thomson (5th Edition) - “PHP and MySQL Web
Development”
6. Roger S. Pressmen, T. Mc. GH. – Software Engineering (Theoretical Approach)
7. Thereon Willis Worx publications (2000) - “Beginning SQL Server”

Department of Computer Science and Engineering