CAMPUS RECRUITMENT

MANAGEMENT SYSTEM

By:

Varun Mundra (07BCE113)

Hitarth Saini (07BCE127)

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

Ahmedabad 382481

April 2011
 CAMPUS RECRUITMENT
MANAGEMENT SYSTEM

Major Project

Submitted in partial fulfillment of the requirements

For the degree of

Bachelors of Technology in Computer Engineering

By:

Varun Mundra (07BCE113)

Hitarth Saini (07BCE125)

Guide

Prof D.J. Patel

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

Ahmedabad 382481
April 2011

- 22 -
 CERTIFICATE

This is to certify that Major Project entitled “Campus Recruitment Management”

submitted by Mr. Varun Mundra and Mr. Hitarth Saini, towards the partial fulfillment
of the requirements for the degree of Bachelors of Technology in Computer Science
Engineering of Institute of Technology, under Nirma University, Ahmedabad is the
record of work carried out by them under my supervision and guidance. In my
opinion, the submitted work has reached a level required for being accepted for
examination. The result embodied in this major project, to the best of my
knowledge, haven’t been submitted to any other university or institution for award
of any degree or diploma.

Prof. D. J. Patel Prof. D.J. Patel

Guide, Professor and Head, Professor and Head,

Department of Computer Engineering, CSE Department,
Institute of Technology, Institute of Technology,
Nirma University, Nirma University,
Ahmedabad. Ahmedabad.
 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.

We are also thankful to Dr. K. Kotecha, Director, Institute of Technology, Nirma

University for his kind support in all respects during our study.

Words are inadequate in offering our thanks to the Project Trainees and Project
Assistants, HMT ltd. for their encouragement and cooperation in carrying out the
project work.

We are also thankful to all the faculty members of the Department of Computer
Engineering, Nirma University for their special attention.

We feel grateful to god for the faith in that power made us pass through tough
times.

Finally, yet importantly, we would like to express our heartfelt thanks our beloved
parents for their blessings, our friends/classmates for their help and wishes for the
successful completion of this project.

VARUN MUNDRA (07BCE113)

HITARTH SAINI (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
company’s 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
website instead manually like payment process, resume filtering, department
details etc.

Although the site is designed for the internship and campus recruitment purpose
but with little modifications can also serve as a working site of the companies,
Ajmer division. Wherein the company’s, Ajmer, division can put up their products
online and give quotations for the specific requirement to the buyer. Thus it can
precisely facilitate growth of business in companies favor.

Things learnt:

• Ease with which asp.net can be used.

• Various other places where asp.net can be exceptional judicial.
• The on-field problem which occur real time.
• Specific needs of the system developed.
• The way commercial organizations work.
• Dynamic updating of database with the help of administrator.
 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 -
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
-
 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 -
 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 -
1. INTRODUCTION

1.1 ABOUT THE COMPANY

1.1.1 Introduction of the

Company

The H.M.T Ajmer previously called as Machine Tools Corporation of India Ltd.
which was incorporated in January. In 1967 to set-up a Grinding Machine
Tools Plant at Ajmer to specialize in the manufacturing, development,
marketing of high precision and sophisticated grinding machine tools, which
are urgently required for our rapid development national economy. It was
installed as a branch of H.M.T under the technical collaboration with TOS
HITIVAR, Czechoslovakia.

Commencing its production with highly versatile universal tool post Grinder.
“MTC” MODEL (ITG-15a) in the year 1970. The factory has been able to
progressively tools like Universal Tools & Cutter Grinder “MTC” MODEL (GIF-
80), Crankshaft Grinding “MTC” MODEL (GCS-500), Vertical surface grinder
“MTC” MODEL, Centre less Grinding Machine. However it has the production
of center lathe of various sized also.

The H.M.T Ajmer has its own design & development in which new designs are
being development to cover requirements of small scale as well as
specialized industries such as Ball & Roller Bearing Industry.

It has a well developed machining and inspecting facilities and a most

modern tools room where Jigs and Fixture and tools are manufactured to
very standards comparable with the best in world.
1.1.2 Company Profile

The Unit was established at Ajmer as “MACHINE TOOL CORPORATION OF

INDIA LIMITED” a Government of India. Undertaking in January, 1967 with
the collaboration of Czechoslovakia M/s Skoda-export and M/s. WMW.GDR.
The EAST GERMANY for the purpose of making India self-reliant in
manufacture of precision Grinding Machines. This Unit was merging with M/s
HMT Limited in 1975. From 1.4.2000 as per the Turnaround Plan, approved
by the Govt. of India, it became a Unit of HMT MACHINE TOOLS LTD. which
is wholly owned Subsidiary of nation’s prestigious company. HMT LIMITED.
This Unit situated over 178 acres of land, out of 68 acres are for factory
campus and 116 acres for a beautiful Township comprising 136 quarters for
housing its employees with community center, club playground etc.

The Unit pioneered manufacturing technology for grinding machines in India,

which was a milestone for country's journey towards self-reliance. Unit has
positioned itself as "Centre of Excellence for Grinding Solution". It caters to
requirement of sun rising user sectors like Automobile, Auto Ancillaries,
Tractors, Bearings. It also caters to requirement of General Engineering,
Defense & Power Sectors. Reliability and precision are hallmark to have a
fleet of 7500 machines working in every corner of country & abroad.

1.1.3 Technological Base

The Unit is well equipped with modern machine shops having 200 nos. of
different types of precision machine ,such as CNC Machining Centers, CNC
Lathes, High precision jig boring machines, High precision Cylindrical
Grinders and Sideways Grinders and Slide, High Precision Cylindrical grinders
and slide way grinders, besides. Well equipped Heat Treatment Shop,
Measuring Centre, Material Testing Laboratory, and Cad Centre for Design &
Development & Foundry. Unit has also captive power generation Capacity of
1850 KVA to meet power shortage. Ajmer unit is capable to meet the
requirement of all types of Grinding Machine Tools for Indian as well as world
market including CNC, tooled-up machines& special purpose machines tailor
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.

1.1.4 Productivity & Quality

Great emphasis is given on Productivity and Quality in HMT. The Unit has
achieved substantial progress in implementation of productivity improvement
activities i.e. KAIZEN, ISO-9000, Total Customer Satisfaction, TQM, Multi-
trade training, Good House Keeping through 5-S, Waste Elimination, Small
Group Activities etc. Unit was the first to receive the ISO-9000 Certification
in Rajasthan and second in HMT Units, on 24.2.1994. The Unit has the
distinction of getting “National Productivity Award” (instituted by National
Productivity Council of India), in Machine Tool Category for the year 1986-87
from the Humble President of India.
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.

Figure 1 OVERVIEW OF HMT-IBM DEPARTMENT

1.2 PROJECT INTRODUCTION

1.2.1 Project title

The title of the project is:

CAMPUS RECRUITMENT MANAGEMENT

1.2.2 Project Definition

A web application that supports the application specific to the HMT’s CRM,
it supplements the recruitment process on the campus, thus filling the gap
between the applicant and the HR department of the company. The portal
will allow integration of all the applicants applying to that organization at
one place to be process at later stages of recruitment. CRM helps to
maintain a database that will help to keep track of the applicant’s
information regarding recruitment and rejecting them on the basis of their
rejection criteria. Also it will facilitate the company specific process of
payment for the application placed under different heads, i.e. department,
internship or job.

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 efficiently thereby including Applicant and Company
Information and providing Campus Recruitment 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
applicant’s personal information.
The application is designed keeping in mind the nature and need of the
company’s daily process of recruitment. The dearth of bench strength
increases drastically with the use of CRM site. There are also plenty of real
time problems such as processing of draft and mailing of resume to the
 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

recruitment information related to the applicant. This website has been
designed as s sub-site for a major site in the pipeline. It deals with the
recruitment related aspects of the company. Using the portal the
customers will also be facilitated with quotations of the heavy machineries
manufactured at the company’s campus. The recruitment and internship
process will be a automated affair after the site is being implemented.

1.5 Overview of Project

The project can be used to identify an applicant in the organization. The
database would maintain the complete details of the applicant.
Each applicant will be assigned a specific applicant number.
2. SYSTEM REQUIREMENTS

2.1. Software Specification

• Language : C#
• Tool used : asp.net
• Database : Ms-access
• OS : windows vista or 7
• MS visual studio 8

2.2. Hardware Specification

• Server
• Minimum 2Gb Ram processor
3 SYSTEM ANALSIS

3.1 Feasibility study

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 personnel’s. 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 describe the feasibility:

• Operational feasibility
• Technical feasibility
• Financial and Economic feasibility

3.1.1 Operational feasibility

The proposed system is beneficial if and only if it can be turned into an
information system that will meet the operating requirements of the
organization. This facet of feasibility asks: if the system will work when it is
developed and installed and are there any major barriers for system
implementation and many more issues. Before switching to new technology,
it mainly examines whether the employees at work are comfortable with
organizational framework. The requirements, specifications and design are
clearly explained to the employees, so that they conduct their operations
successfully. The system up gradations are done in accordance to the
application developed or the application is developed in accordance to the
available system.
3.1.2 Technical feasibility
The investigation is done mainly keeping in mind this aspect of feasibility.
The analyst has to keep in mind while performing requirement elicitation
that the requested work flow is what is feasible technically. Major issues in
technical feasibility are to see if the required resources-trained manpower,
software and hardware are available or not. The assessment is based on an
outline design of system requirements in terms of Input, Processes,
Output, Fields, Programs, and Procedures. This can be quantified in terms
of volumes of data, trends, frequency of updating, etc. in order to estimate
whether the new system will perform adequately or not. Technological
feasibility is carried out to determine whether the company has the
capability, in terms of software, hardware, personnel and expertise, to
handle the completion of the project.

3.1.3 Financial and economic feasibility

As the word denotes that the economic feasibility means more

benefit at less expenditure. So every organization must keep in
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:
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.

-
2020
4 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
• Applicant information module
• Administration module
• Application management module.

4.1.1 User Module

This is the basic structure of the website containing all the necessary
information about the company. This has multiple links to other
modules which have been created in order to facilitate the user and
the administrator.

4.1.2 Applicant Information Module

This is the module designed to update the database. Here the

applicants submit all their professional and personal details regarding
the job or internship they seek.

This module saves the details in a specified format so that the

database is updated in an analogous way for every applicant. All the
data entered by the applicant is arranged in tables and can be
retrieved as and when required by the administrator.

It also has been incorporated to pay the applicant fees online using
the applicant information forms.This information module makes a
 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.
4.2 Data Flow Model : MVC

Figure 2 MVC architecture

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
layer. This separation means that one can assign different parts to different
people, and they don’t necessarily have to interfere with each other’s 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.
• View objects represent something visible in the user interface, for
example a panel or button. The view renders the model into a form
suitable for interaction, typically a user interface element. Multiple views
can exist for a single model for different purposes. A viewport typically
has a one to one correspondence with a display surface and knows how to
render to it.
• 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.

Many applications use a persistent storage mechanism such as a database to

store data. MVC does not specifically mention the data access layer because
it is understood to be underneath or encapsulated by the model.
Advantages :

Here are the main advantages of building applications using MVC framework.

• MVC Framework is built upon a proven MVC design-pattern.

• One of the biggest problems in ASP.NET is HTML size of controls and
view state. View state stores all the data rendered and final HTML gets
too large. If one is on a slow internet connection, he/she will notice
load time delays. This has been taken care in MVC framework. There is
no view state concept in MVC framework.
• Client caching is available and by integrating, we can take advantage
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.
• MVC supports multiple views.
• 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

• It is not easy to understand and code when one needs some

customization. If one is building based on a 100% mature database it
works well. But if one has frequent changes in the database, he/she
may find it annoying to keep building application again and again. It
may also break several other parts of the application.
 4.3 Context Level Diagram

Figure 3 context level diagram

Involved entity’s in the context level diagram :

Modules -> Applicant user, Recruitment manager, System admin.

Sub modules -> Processes in modules.

Involved association’s in the context level diagram :

 Modules -> modules connected to Campus Recruitment Management.

Sub modules -> various processes interconnected among their respective

modules.

4.4 Data Flow Diagrams

4.4.1 DFD level 0

Figure 4 DFD level-0

4.4.2 DFD level 1

Figure 5 DFD level-2

4.4.3 DFD level 2

Figure 6 DFD level-2

4.5 Class Diagram

Figure 7 class diagram

-
3030
4.6 Sequence Diagrams

4.6.1 Sequence Diagram 1

Sequence name : creation and storage of profile at applicant user

information module.

Figure 8 At applicant user end

Sequence description : shows the sequential interaction of various processes
while the creation and updating of applicant profile from the front end of the site.

4.6.2 Sequence Diagram 2

Sequence name : searching, short listing, viewing and recruitment of

applicant from admin user module.

Sequence Description : shows the sequential interaction of various

processes while the applicants are searched from the database,
shortlisted, their profiles are viewed and resumes downloaded for
recruitment.
Figure 9 At admin user end

- 33 -
 4.7 Database Description

Database Database Description

Name
Admin This stores the various attributes like admin user id, username,
password, type and email addresses of all the admin users.
Category This saves the attributes of categories of products featured on the
company’s web page as category id, name, rank , status.
Content 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.
department 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.
Experience This saves the options presented for the experience field to be filled
by the applicant on the web page for job application form.
jobapplication 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.
Menu 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.
Product This saves the attributes of various products in different categories
and their descriptions.
qualifications 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

-
3434
4.7.1 Tables used

4.7.1.1 Admin Table

admin_i admin_logi admin_passwor admin_typ admin_email

d n d e
1 narendra Admin admin [email protected]
2 Hitarth Hitarthsaini subadmin [email protected]
m
3 Varun Varunmundra subadmin [email protected]

Table 2 Admin table

4.7.1.2 Category Table

Id Category name rank activestatus

1 Turning 1 active
3 Grinding 2 active
4 Gear cutting 3 active
5 Broaching,Drilling 4 active
& Mining
6 Presses & Press 5 active
Brakes
7 Printing Machines 6 active
8 CNC Control 7 Active
systems

Table 3 Category table

 4.7.1.3 Experience Table

e_id Experience
1 Fresher
2 less than one year
3 1 year
4 2 year
5 3 year
6 4 year
7 5 year
8 6 year
9 7 year
10 8 year
11 9 year
12 10 year
13 10+ year

Table 4 Experience table

4.7.1.4 Job - Application table

uid ufname ulname unumber email ag m/ uqual uexp cursal

e f

1 narendra rathod 9989435678 naren 25 ma BE 2year 8000

le

20 rahul paliwal 9904032435 rpal@ 23 ma Bcom 1year 15000

le

Table 5 Job application table

4.7.1.5 Menu table

menu_id menu_name ASPX_page parent_id rank

1 adminmanager 0 1
2 administrator adminuser.aspx 1 2
3 contentmanager 0 3
4 content content.aspx 3 4
5 departmentmanager 0 5
6 department department.aspx 5 6
7 productmanager 0 7
8 category category.aspx 7 8
9 products product.aspx 7 9
10 jobapplicationmanager 0 10
11 jobapplication jobapplication.aspx 10 11

Table 6 Menu table

4.7.1.6 Qualification Table

qid qname
th
1 12
2 B.A
3 B.Arch
4 B.com
5 B.Ed
6 B .Pharm
7 B.Sc
8 BBA
9 BDS
10 BE/B.tech
11 BHM
12 BL/LLB
13 CA
14 CS
15 Diploma
16 M.Arch
17 M.com
18 M.Ed
19 M.Pharm

Table 7 Qualification table

 5 USER INTERFACE

The following are the screens with their corresponding description:

5.1 Screen name : home.aspx

Figure 10 home

Description:

• This is the menu screen displayed to the user as soon as he/she

opens the website.
• This screen contains links to various pages/screens.
5.2 Screen Name : applyforjobs.aspx

Figure 11 job application form

Description :

• This is the form that is presented to the applicant for applying to

job.
• This form has various options as provided by the asp.net
toolbox like dropdown, submit, upload buttons.
• The fields marked * are mandatory for the applicant to fill the
form.
 • Some fields have options already presented that need to be
selected while others have a set of defined inputs for them.

5.3 Screen Name : applyforjobs.aspx

Figure 12 job application form filled

Description :

• This is an example of how the applicant has to fill the various

fields as presented in the form.
• The screen shows how after filling and submitting the form
the control is being transferred to another aspx page.

-
4040
 • The next screen that is loaded after this is the paypal
sandbox screen where the applicant has to pay for the
application online.
• It is mere transfer of control from one site to other.
• 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 system’s database which is accessible to the resource
manager or admin users anytime.

5.3 Screen name : administratorlogin.aspx

Figure 13 Admin window

Description :

• This is the site which admin users can access anytime.

• For security reasons it has been featured to submit username and
password of the admin user.

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.

5.4 Screen name : administrator.aspx

Figure 14 Administrator
Description :

• This is the main page of the admin user side.

• 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.
• There is a search by email option, add and delete admin user
profile option, a clock presented all the time and an edit profile
option.
5.5 Screen name : jobapplication.aspx

Figure 15 Aplication search

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.
• A search can be made when the search parameters are set.

5.6 Screen name : jobapplication.aspx

Figure 16 Search procedure

Description :

• This shows the available qualification parameters that can be

selected for the search of the applicants.
• The options for qualifications are already in the aspx page which
were added during its design and can be changed by the system
administrator.

5.7 Screen name : viewprofile.aspx

Figure 17 Display
Description :

• This is the profile displayed of the applicant that admin user selects
and views.
• The profile is presented to admin user and the details of the
applicant are shown.
6 TESTING

6.1 System 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.

6.2 Unit Testing

Testing is a set of activities that can be planned in advance and conducted

systematically. The proposed system is tested in parallel with the software
that consists of its own phases of analysis, implementation, testing and
maintenance. Following are the tests conducted on the system.

During the implementation of the system each module of the system was
tested separately to uncover errors within its boundaries. User interface
was used as a guide in the process.

Unit testing may reduce uncertainty in the units themselves and can be
used in a bottom-up testing style approach. By testing the parts of a
program first and then testing the sum of its parts, integration
testing becomes much easier.
6.3 Module Testing

A module is composed of various programs related to that module. Module

testing is done to check the module functionality and interaction between
units within a module. It checks the functionality of each program with
relation to other programs within the same module. It then tests the
overall functionality of each module. Modules being the integral part of the
system have to interact with each other efficiently and without errors,
because error here would bring the complete system to a stand still. The
server would run out of responses thus causing a massive system crash.

6.4 Integration Testing

The purpose of integration testing is to verify functional, performance, and

reliability requirements placed on major design items. Integration testing is
a systematic technique for constructing the program structure while
conducting tests to uncover errors associated with interfacing. The
objective is to take unit-tested module and build a program structure that
has been dictated by design.
Test cases are constructed to test that all components within assemblages
interact 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.
7 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
organization’s 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.
8 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 :

8.1 Commercializing website

At present, the website is just a basic one detailing some information about
the company along with other features. In future the website can be
developed as a commercial website to enhance the marketing and sales of
the company. Detailed description of every product and its uses along with
its price and general instructions can be posted on the site.

8.2 Direct Paymet

As of now, the sales and marketing department of the company does not
take online orders. The process of closing a sale to the shipment of the
merchandise is filled with a lot of documentation and is too much time
consuming. In future, this can be incorporated with a facility of direct
payment (online) of the products as mentioned in the company’s website.
This will render the ease of selling and save plenty of valuable time.

8.3 Automated Notifications

Presently, the selected candidates (recruited) are notified by the HR

department manually about their present status and about further
proceedings. The website can be designed so as whenever required an
automated email can be send to the candidate. This feature will make sure
that the candidate applying for job or intern in the company will get an email

-
5050
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.

8.4 Complete database Control

The website can be enhanced to include a feature so as the complete

database of the company can be managed directly from it.
Leave application management, personalized corporate email id’s for every
employee, official notices and news of the company, online training modules
for different specializations, etc are some of the features that will be very
useful.
9 SUMMARY AND CONCLUSION

9.1 SUMMARY

Summary of activities carried out during major project training at HMT can
be listed below :

• Fundamental learning about the platform, technology and tools to be

implemented in full throttle.
• System requirement analysis, to construct the project.
• Complete design of the system including database, GUI, application
forms, payment mode usage.
• Project integration on .net framework, i.e. complete coding.
• Development of visual diagrams such as class diagram, context
diagrams, DFD’s, sequence diagrams to understand the real time
working process of the system before coding.
• 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
like HMT-MTA as it is called as “centre for excellence for grinding solution”.
Also it is world class machinery and ‘State of the Art’ equipments, updated
manufacturing process & professionally trained human resource are the
major factors which have resulted in quality products as well as have given
all of us quantitative and qualitative exposure to high technology. The HMT
machine tool Ltd. Amounts to 43% share in the Rs 2000/- crores machines
tools market .Also machine tools division recently bagged Rs 600/- crores
export order. In the next five years the turnover of the company is likely to
exceed Rs 1500/- crores.
 10 BIBLIOGRAPHY AND REFERENCES

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
Book, Wiley publications India.

10.2 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