Professional Documents
Culture Documents
MANAGEMENT SYSTEM
By:
Varun Mundra (07BCE113)
Hitarth Saini (07BCE127)
CAMPUS RECRUITMENT
MANAGEMENT SYSTEM
Major Project
Guide
Prof D.J. Patel
CERTIFICATE
Prof. D. J. Patel
CSE Department,
Institute of Technology,
Institute of Technology,
Nirma University,
Nirma University,
Ahmedabad.
Ahmedabad.
-3-
ACKNOWLEDGEMENT
We take immense pleasure in thanking Mr. Alok Gaur, Training In charge at HMT
ltd for his continual support throughout the project work.
We wish to express our deep sense of gratitude to our Internal Guide, Prof. D.J.
Patel, HOD, Department of computer science engineering, Institute of Technology,
Nirma University, Ahmedabad for his valuable guidance and useful suggestions,
which helped us in completing the project work, in time. He also encouraged and
motivated us throughout the Major Project were a big source of inspiration.
-4-
(07BCE125)
ABSTRACT
Our project titled CAMPUS RECRUITMENT MANAGEMENT is website developed for
the company to facilitate the ease of application for internship or recruitment in the
company. This website acts as a time saving means for both the company and the
applicants in this large public sector undertaking.
Using the website the applicants can apply with their qualifications and need for the
work or internship with the company. The applicants can also pay the amount for
application online. The administrator thus can have a pool of technical as well as
non-technical but required in the company people. The administrator can anytime
fire a query to get the desired people for the job requirement, from the database.
The search can be limited with the addition of filters.
The information of the candidate is id fed into the database using forms. The back
end is ms-access database. Thus the required candidate can be called upon for the
interview and selection process at the campus. The details entered and fetched at
the time of filtering is crucial thus precise care has been taken while coding the way
filtering works.
The administrator has the privilege to modify the fields when the changes occur.
Thus making it exceptionally ease at the administrators side to operate the site
dynamically. The database is used to facilitate lower number of entries in it.
The selection and rejection is based on strict inspection of validity of application
forms by panel of HR members at HMT, where the candidate shortlisted is
summoned for interview on reports being generated after the specific search.
The initial phases of the development included the complete analysis of the
companys working process, the way the applications are processed. Thus the user
side is designed from the approach of ease of application and mandatory fields as
per the company, the administration side has been developed for HR persons in the
company. The website is designed taking care of small process to be doing by the
-5-
-6-
CONTENTS
1. CHAPTER 1 INTRODUCTION ....................................................................................................................................................- 11 1.1 About the company ...............................................................................................................................................................- 11 1.1.1 Introduction of the company .............................................................................................................................................- 11 1.1.2 Company profile .................................................................................................................................................................- 12 1.1.3 Technological base .............................................................................................................................................................- 12 1.1.4 Productivity & Quality ........................................................................................................................................................- 13 1.1.5 IT Department ....................................................................................................................................................................- 14 1.2 PROJECT INTRODUCTION .....................................................................................................................................................- 15 1.2.1 Project title .........................................................................................................................................................................- 15 1.2.2 Project definition ................................................................................................................................................................- 15 1.3 Purpose of study ...................................................................................................................................................................- 15 1.4 Scope of study .......................................................................................................................................................................- 16 1.5 Overview of project ...............................................................................................................................................................- 16 10 CHAPTER 10 BIBLIOGRAPHY AND REFERENCES......................................................................................................................- 54 10.1 Bibliography ........................................................................................................................................................................- 54 10.2 References ...........................................................................................................................................................................- 54 2. CHAPTER 2 SYSTEM REQUIREMENTS ......................................................................................................................................- 17 2.1 Software Specification ...........................................................................................................................................................- 17 2.2 Hardware Specification .........................................................................................................................................................- 17 3. CHAPTER 3 DYSTEM ANALYSIS ................................................................................................................................................- 18 3.1 Feasibility study .....................................................................................................................................................................- 18 3.1.1 Operational feasibility ........................................................................................................................................................- 18 3.1.2 Technical feasibility ............................................................................................................................................................- 19 3.1.3 Financial and economic feasibility......................................................................................................................................- 19 4. CHAPTER 4 SYSTEM DESIGN ....................................................................................................................................................- 21 4.1 Module description ...............................................................................................................................................................- 21 4.1.1 User module .......................................................................................................................................................................- 21 4.1.2 Applicant information module ...........................................................................................................................................- 21 4.1.3 Administrative module .......................................................................................................................................................- 22 4.1.4 Applicant management module .........................................................................................................................................- 22 4.2 Data flow model
MVC ........................................................................................................................................................................................- 23 4.3 Context level diagram ...........................................................................................................................................................- 26 4.4 Data flow diagrams ...............................................................................................................................................................- 27 4.4.1 DFD level 0 .........................................................................................................................................................................- 27 4.4.2 DFD level 1 .........................................................................................................................................................................- 28 4.4.3 DFD level 2 .........................................................................................................................................................................- 29 4.5 Class Diagram ........................................................................................................................................................................- 30 4.6 Sequence Diagrams ...............................................................................................................................................................- 31 4.6.1 Sequence diagram 1 ...........................................................................................................................................................- 31 4.6.2 Sequence diagram 2 ...........................................................................................................................................................- 32 4.7 Database description.............................................................................................................................................................- 34 4.7.1 Tables used .........................................................................................................................................................................- 35 4.7.1.1 Admin table .....................................................................................................................................................................- 35 4.7.1.2 Category table .................................................................................................................................................................- 35 4.7.1.3 Experience table ..............................................................................................................................................................- 36 4.7.1.4 Job application table .......................................................................................................................................................- 36 4.7.1.5 Menu table ......................................................................................................................................................................- 37 -
-7-
4.7.1.6 Qualification table ...........................................................................................................................................................- 37 5 CHAPTER 5 USER INTERFACE ....................................................................................................................................................- 38 5.1 Screen name home.aspx .......................................................................................................................................................- 38 5.2 Screen name applyforjobs.aspx ............................................................................................................................................- 39 5.3 Screen name applyforjobs.aspx ............................................................................................................................................- 40 5.4 Screen name administrator.aspx ...........................................................................................................................................- 42 5.5 Screen name jobapplication.aspx ..........................................................................................................................................- 43 5.6 Screen name jobapplication.aspx ..........................................................................................................................................- 44 5.7 Screen name viewprofile.aspx...............................................................................................................................................- 45 6 CHAPTER 6 TESTING .................................................................................................................................................................- 47 6.1 System testing .......................................................................................................................................................................- 47 6.2 Unit testing ............................................................................................................................................................................- 47 6.3 Module testing ......................................................................................................................................................................- 48 6.4 Integration testing .................................................................................................................................................................- 48 7 CHAPTER 7 IMPLEMENTATION PHASE .....................................................................................................................................- 49 8 CHAPTER 8 FUTURE ENHANCEMENT..........................................................................................................- 50 8.1 Commercializing website ......................................................................................................................................................- 50 8.2 Direct payment ......................................................................................................................................................................- 50 8.3 Automated notifications .......................................................................................................................................................- 50 8.4 Complete database control ...................................................................................................................................................- 51 9 CHAPTER 9 SUMMARY AND CONCLUSION ...............................................................................................................................- 52 9.1 Summary ...............................................................................................................................................................................- 52 9.2 Conclusion .............................................................................................................................................................................- 52 ABSTRACT ......................................................................................................................................................................................- 5 ACKNOWLEDGEMENT ...................................................................................................................................................................- 4 CERTIFICATE ..................................................................................................................................................................................- 3 Screen name administrator login.aspx ........................................................................................................................................- 41 -
-8-
LIST OF FIGURES
Figure 1 OVERVIEW OF HMT-IBM DEPARTMENT ............................................................... - 14 Figure 2 MVC architecture ..................................................................................................................... - 23 Figure 3 context level diagram ............................................................................................................... - 26 Figure 4 DFD level-0 ............................................................................................................................... - 27 Figure 5 DFD level-2 ............................................................................................................................... - 28 Figure 6 DFD level-2 ............................................................................................................................... - 29 Figure 7 class diagram ............................................................................................................................ - 30 Figure 8 At applicant user end ............................................................................................................... - 31 Figure 9 At admin user end .................................................................................................................... - 33 Figure 10 home ...................................................................................................................................... - 38 Figure 11 job application form ............................................................................................................... - 39 Figure 12 job application form filled ...................................................................................................... - 40 Figure 13 Admin window ....................................................................................................................... - 41 Figure 14 Administrator ......................................................................................................................... - 42 Figure 15 Aplication search .................................................................................................................... - 43 Figure 16 Search procedure ................................................................................................................... - 44 Figure 17 Display .................................................................................................................................... - 45 -
-9-
LIST OF TABLES
Table 1 Datbase description ................................................................................................................... - 34 Table 2 Admin table ............................................................................................................................... - 35 Table 3 Category table ........................................................................................................................... - 35 Table 4 Experience table ........................................................................................................................ - 36 Table 5 Job application table.................................................................................................................. - 36 Table 6 Menu table ................................................................................................................................ - 37 Table 7 Qualification table ..................................................................................................................... - 37 -
- 10 -
1.
INTRODUCTION
- 11 -
made to customers requirement. The unit has skilled and dedicated Work
Force and has strength of qualified & experienced Engineering personnel to
fulfill the requirement of business operations to the satisfaction of customers.
Unit has Machine Shops well equipped with 180 nos. precision machines.
Apart from these, Unit is also having Measuring Centre, Material Testing
Laboratory, CAD Centre and Foundry. The Unit has highly skilled and
dedicated work force. The Unit has qualified and experienced Design &
Engineering Personnel to fulfill requirement of Business Operations to the
entire satisfaction of customers.
- 13 -
1.1.5 IT Department
IBM department is actually the Information Technology Center of HMT. It is
called IBM because in the beginning HMT used to use machines of IBM.
- 14 -
1.3
Purpose of Study
The CRM is a powerful application designed to allow the organization to
streamline their human resource tasks and manage their recruitment
process
more
Information
efficiently
and
thereby
providing
including
Campus
Applicant
Recruitment
and
Company
Documentation
&
Management.
The CRM includes a comprehensive applicant information database, work
information, and more, for each applicant. It comes standard with
Recruitment
Manager
self-service
access
allowing
him
to
update
company, the site speeds up the complete process thereby saving time
and energy of manpower.
1.4
Scope of Study
CRM
allows
the
creation
of
an
application
specification
regarding
- 16 -
2.
2.1.
2.2.
SYSTEM REQUIREMENTS
Software Specification
Language : C#
Database : Ms-access
OS : windows vista or 7
MS visual studio 8
Hardware Specification
Server
- 17 -
SYSTEM ANALSIS
Introduction
As we all are aware of the fact that manpower plays a vital role in every
kind of organization, so to make proper use of manpower resource
feasibility study is needed. A feasibility study phase provides the analyst
with a more thorough understanding of the problems, opportunities related
to personnels. A feasibility study should be conducted to determine the
viability of an idea before proceeding with the development of the HUMAN
RESOURCE. An important outcome of the preliminary investigation phase of
the System Development Life cycle is the determination that the requested
system
is
feasible.
The
following
facets
Operational feasibility
Technical feasibility
describe
the
feasibility:
- 18 -
3.1.2
Technical feasibility
3.1.3
mind while recruitment of the personnel that more people should not
be employed than required as it can raise the cost. This thus
becomes a very crucial facet because every industry is governed by
finances.
Economic analysis is the most frequently used method for evaluating the
effectiveness of a new system. More commonly known as cost/benefit
analysis, the procedure is to determine the benefits and savings that are
expected from a candidate system and compare them with costs. If benefits
outweigh costs, then the decision is made to design and implement the
system. An entrepreneur must accurately weigh the cost versus benefits
before taking an action.
Cost-based study: It is important to identify cost and benefit factors, which
can be categorized as follows:
- 19 -
1. Development costs
2. Operating costs.
This is an analysis of the costs to be incurred in the system and the
benefits derivable out of the system.
Time-based study: This is an analysis of the time required to achieve a
return on investments. The future value of a project is also a factor.
- 20 -
SYSTEM DESIGN
4.1
Module description
We have developed four modules to finally get to the main working
site. These four modules work in an integrated environment to give
the end used, administrator exactly what he has fired as query.
User module
Administration module
- 21 -
pool of applicant available all the time for the HR department of the
company making it extremely viable for the heads to cling on to
whenever there is a need or vacancy.
4.1.3 Administrative Module
This module is the control panel of the whole site. The administrator has
power rights like update, delete, view, restrict other administrator
powers to access the data.
This module manages other module which is used for dynamic updates
of the site, changes to be offered in the site etc.
Administrator can access applicants profile any time, can shortlist
various applicants according to required need using the appropriate
search filters. This module also has been incorporated with feature to
retrieve, download and save the resume files from the database.
4.1.4 Application Management Module
This is the module which comes into picture during the finalization
process of the application. Who to call for interview, selected candidate
to be marked as employed candidate of the company, restoring the
information of the applicant in a separate database for future reference.
This module specially acts as a catalyst to the final process of
recruitment or internship in the company.
- 22 -
4.2
System Architecture
Model View Controller Architecture (MVC)
MVC stands for Model, View, and Controller. Here, the Model is the data access
layer, the Controller is the business-logic layer, and the View is the interface
- 23 -
layer. This separation means that one can assign different parts to different
people, and they dont necessarily have to interfere with each others code.
MVC defines the separation of these three types of objects:
Model objects hold data and define the logic for manipulating that data.
The model manages the behavior and data of the application domain,
responds to requests for information about its state (usually from the
view), and responds to instructions to change state (usually from the
controller). In event-driven systems, the model notifies observers (usually
views) when the information changes so that they can react.
Controller object acts as a Mediator between the Model and View objects.
A Controller object communicates data back and forth between the Model
objects and the View objects. A controller also performs all application
specific tasks, such as processing user input or loading configuration data.
There is usually one controller per application or window, in many
applications the Controller is tightly coupled to the view.
The controller receives user input and initiates a response by making calls
on model objects. A controller accepts input from the user and instructs
the model and viewport to perform actions based on that input.
- 24 -
Advantages :
Here are the main advantages of building applications using MVC framework.
of it. That makes applications load faster and some of the processing
can be done in web browsers. Not only the client site but the server
side execution is faster too. The integration with MVC makes it even
better and now we can write our code that runs in the browser and
takes away load from the server.
It also supports unit testing as a part of Visual Studio 2008 and 2010
Disadvantages
Some of the key challenges one may face while using MVC Framework are
- 25 -
4.3
- 26 -
4.4
4.4.1
DFD level 0
- 27 -
4.4.2
DFD level 1
- 28 -
- 29 -
4.5
Class Diagram
- 30 -
4.6
Sequence Diagrams
- 31 -
- 32 -
- 33 -
4.7
Database Description
Database
Name
Admin
Category
Content
department
Experience
jobapplication
Menu
Product
qualifications
Database Description
This stores the various attributes like admin user id, username,
password, type and email addresses of all the admin users.
This saves the attributes of categories of products featured on the
companys web page as category id, name, rank , status.
This saves the attributes of content of pages namely Home, About
us and Contact us like content id, title, meta_title , meta_keyword,
type, link, description.
This saves the attributes like id, name, meta title, meta keyword,
meta description and description of various aspx pages linked on
the mainframe of the website.
This saves the options presented for the experience field to be filled
by the applicant on the web page for job application form.
This saves the data presented by all the applicants belonging to
various fields on the job application form like first name, last name,
email address, phone number, age, gender, address, qualification,
experience and current salary.
This saves the attributes of various links on the control panel of the
administrator side like the link name, linked aspx page, parent id
and rank.
This saves the attributes of various products in different categories
and their descriptions.
This saves the options presented for the qualifications field to be
filled by the applicant on the web page for job application form.
Table 1 Datbase description
- 34 -
4.7.1.1
Admin Table
admin_i
d
1
2
admin_logi
n
narendra
Hitarth
admin_passwor
d
Admin
Hitarthsaini
admin_typ
e
admin
subadmin
Varun
Varunmundra
subadmin
admin_email
admin@admin.com
hitarthsaini@gmail.co
m
vm.admin@gmail.com
4.7.1.2
Id
1
3
4
5
6
7
8
Category Table
Category name
Turning
Grinding
Gear cutting
Broaching,Drilling
& Mining
Presses & Press
Brakes
Printing Machines
CNC Control
systems
rank
1
2
3
4
activestatus
active
active
active
active
active
6
7
active
Active
- 35 -
4.7.1.3
Experience Table
e_id
1
2
3
4
5
6
7
8
9
10
11
12
13
Experience
Fresher
less than one year
1 year
2 year
3 year
4 year
5 year
6 year
7 year
8 year
9 year
10 year
10+ year
Table 4 Experience table
uid
ufname
ulname
unumber
ag
e
m/
f
uqual
uexp
cursal
narendra
rathod
9989435678
naren
25
ma
le
BE
2year
8000
20
rahul
paliwal
9904032435
rpal@
23
ma
le
Bcom
1year
15000
- 36 -
menu_id
1
2
3
4
5
6
7
8
9
10
11
menu_name
adminmanager
administrator
contentmanager
content
departmentmanager
department
productmanager
category
products
jobapplicationmanager
jobapplication
ASPX_page
parent_id
0
adminuser.aspx
1
0
content.aspx
3
0
department.aspx
5
0
category.aspx
7
product.aspx
7
0
jobapplication.aspx 10
qname
12th
B.A
B.Arch
B.com
B.Ed
B .Pharm
B.Sc
BBA
BDS
BE/B.tech
BHM
BL/LLB
CA
CS
Diploma
M.Arch
M.com
M.Ed
M.Pharm
Table 7 Qualification table
- 37 -
rank
1
2
3
4
5
6
7
8
9
10
11
USER INTERFACE
5.1
Figure 10 home
Description:
5.2
Description :
The fields marked * are mandatory for the applicant to fill the
form.
- 39 -
5.3
Description :
The screen shows how after filling and submitting the form
the control is being transferred to another aspx page.
- 40 -
The user can return back to the previous screen and can also
skip the option of payment of fee.
This will only submit the profile filled online by the applicant
in the systems database which is accessible to the resource
manager or admin users anytime.
- 41 -
Description :
Until and unless the correct match is not provided, the site will not proceed and
will return back to reload of the same aspx page.
Figure 14 Administrator
- 42 -
Description :
This shows the map to various sections of site on its left and
also shows the profiles of various admin users.
This has also been incorporated with various features using aspx
toolbox.
- 43 -
Description :
This is the page which presents the admin user with all the
available job applicants from the pool created by the database.
The page gives admin user rights to view and delete various
profiles.
The page also is integrated with search options where the admin
user can search for a particular applicant fitting to some
particular job profile.
- 44 -
Description :
The options for qualifications are already in the aspx page which
were added during its design and can be changed by the system
administrator.
Figure 17 Display
- 45 -
Description :
This is the profile displayed of the applicant that admin user selects
and views.
- 46 -
TESTING
The testing phase involves the testing of the developed system using
various kinds of data. An elaborated testing of data is prepared and a
system is tested using the test data. While testing, errors are noted and
corrections remade, the corrections are also noted for future use.
It includes a vast variety of test put together to develop an active
application which can be used under varied stress and load situation.
The GUI is also tested with performance and error handling testing.
first
and
then
testing
- 47 -
the
sum
of
its
parts, integration
structure
while
correctly,
for
example
across
procedure
calls
or
process
activations, and this is done after testing individual modules, i.e. unit
testing. The overall idea is a "building block" approach, in which verified
assemblages are added to a verified base which is then used to support the
integration testing of further assemblages.
- 48 -
IMPLEMENTATION PHASE
The implementation is the final and important phase. It involves User training,
system testing and successful running of the developed system. The users test
the developed system when changes are made according to the needs. The
testing phase involves the testing of the developed system using various kinds of
data. An elaborate testing of data is prepared and system is tested using the
tests data.
Implementation is the stage where theoretical design turned into a working
system. Implementation is planed carefully to propose system to avoid
unanticipated problems. Many preparations involved before and during the
implementation of proposed system. The system needed to be plugged in to the
organizations network then it could be accessed from anywhere, after a user
logins into the portal. The tasks that had to be done to implement the system
were to create the database tables in the organization database domain. Then
the administrator was granted his role so that the system could be accessed.
The next phase in the implementation was to educate the system. A
demonstration of all the functions that can be carried out by the system was
given to examination department person, who will make extensive use of the
system.
- 49 -
FUTURE ENHANCEMENT
HR being a vast area of input in any organization these days requires
customized system to tackle or work with different organization. The website
for CRM at HMT has been tailored for the HMT, Ajmer. The website at present
is made to assist the recruitment and internship process. But the platform is
made open leaving scope of expansion of the work to a vibrant functional
website where complete HR related work will be automated through intranet
and internet available at the campus.
The website can also with little modifications as per the need of the
organization, can be used by recruiters anywhere in the world.
Below is a list of area where further development is possible :
the very same day, when he/she applies and will be notified as and when
there is a vacancy or job requirement in the company.
- 51 -
9.1 SUMMARY
Summary of activities carried out during major project training at HMT can
be listed below :
System testing
Website implementation.
Final documentation
9.2 CONCLUSION
By this internship program in HMT-MTA we have achieved a wonderful
experience in the field of industry .As HMT all manufacturing units are ISO
9001 accredited so it maintain the company to standardize in high quality
product. As our specialized department IBM is concerned actually it is the
IT department of the company. It is a main department. It handles all
works related to software, servers and networking. We learned lots of
things related to this department such as its activities, importance and
responsibility. Here we not only gained the technical knowledge but also the
professional qualities which one must have while working in a big company
- 52 -
- 53 -
10
10.1 BIBLIOGRAPHY
Walther Stephen, ASP.NET MVC Framework Unleashed, SAMS
Publishing.
Imar Spaanjaars ,Beginning ASP.NET 4: in C# and VB,
Wrox publications.
Chris Love,ASP.NET 3.5 Website Programming: Problem - Design
Solution, Wrox publications.
Kogent Learning Solutions Inc., Asp.Net 4.0: Covers C# And Vb Codes, Black
REFERENCES
www.asp.net
www.codeproject.com
www.dotnetspiders.com
www.w3schools.com/aspnet/default.asp
www.assignmenthelp.net/asp-assignment-help.php
www.learn-asp.net
www.learninggeeks.info
www.dotnetbips.com
www.silverlight.net/learn/tutorials
www.cristiandarie.ro/asp-net-tutorial
- 54 -