Professional Documents
Culture Documents
Features :
This project can be used very easily in the process of decision making in new
recruitments.
1.INTRODUCTION
FEATURES:Corporate Recruitment System (CRS) has all the features and functions
required for executing a successful recruitment task, providing exceptional case of use for
recruitment.
The Following are the overview of the features and benefits of CRS.
Database software installed and pre-configures for the immediate use of the
system effectively and efficiently.
Pre-configured and ready to run Jobs database with management module for
adding and deleting efficiently.
Provides information to the managers so that they can make judgment about
particular situations.
Reductions in the cost of hiring there will be between 50-60 percent decrease in
the cost of hiring.
OBJECTIVES:
This system provides service to the potential job applicants to search for working
opportunities.
This system helps the HR Personal in the recruitment of new candidates to the
company.
Corporate Recruitment System will allow job provider to establish one to one
relationships with candidates.
This corporate recruitment service system will primarily focus on the posting and
management of job vacancies.
This system is designed such that ultimately all vacancies will be posted online
and would offer employers the facilities to post their vacancies online.
It helps to review and manage the resulting applications efficiently through the
web.
USER REQUIREMENTS:
Helps to provide control access to database files using assigned user login and
password control.
Processor
Processor Speed
RAM
250MHz to 833MHz
Hard Disk
512MB RAM
:
40GB
Operating System
Windows XP
Database
Sql Server
ASP.Net
ASP
HTML
Web-Server
IIS
2.SYSTEM STUDY
2.1 EXISTING SYSTEM
The Job Providers carry out their activities through various meetings and
presentations. The HR-Manager takes the final decisions and assigns the tasks to HR
Senior Facilitators. The HR-Senior Facilitators completes the tasks assigned to them with
the help of Junior Facilitators. In the current scenario, all the information and activities
relies on paperwork. The problem that arises in such a scenario is that the process is too
cumbersome and demanding as well.
Highly inconsistent information across the department along with the overhead of
redundant data management across department.
High level of human intervention needed and hence usage of the system depends
on the skill of the individual.
requires that the database be adequately backed up so that in case of failure the
data can be recovered.
Features
Corporate Recruitment System (CRS) has all the features and functions required
for executing a successful recruitment task.
The following are the overview of the features and benefits of CRS
Provides information to the managers so that they can make judgment about
particular situations.
To build all communication on industry standards to ensure that code based on the
.NET Framework can integrate with any other code.
3.1Form Design:
The Corporate Recruitment System is broadly divided into 5 modules.
Job Details
Job Provider
Question Details
Resume Details
Seeker Registration
FORM Design:
Job Details:
Provider Details:
Question Details:
Resume Details:
Seeker Registration:
3.2INPUT DESIGN:
View Jobs:
Inbox
Online Test
Post Resume
View Jobs
Logout
1.2 Modules
The Corporate Recruitment System is broadly divided into 4 modules.
Login Module
Login Module
The module is the one, which allows only authorized people to access the
Application. Any person who needs an access to the application is needed to login in the
first step. The user needs to provide his or her login ID and the password. The password
is checked against the one stored in the database. If both the ID and Password are valid
then the user is given access to the application, else he/she is denied from it.
Requirements
Resume Processing
In Box
Post Resume
Update Resume
Introduction to HTML:
The hypertext markup language (HTML) is a simple markup language. Used
to create a hypertext documents that are portable from one platform to another HTML
documents are SGML (Standard generalized mark up language) documents with generic
semantics that are appropriate for representing information from a wide range of
applications. This specification defines HTML version 3.2. HTML 3.2 aims to capture
recommended practice as of early 96 and as such a replacement for HTML2.0 (RFC
1866).
A set of instructions embedded in a document is called mark up language.
These instructions describe what the document text means and how it should look like in
a display. Hyper Text Mark Up language (HTML) is the language used to encode World
Wide Web documents.
HTML LAYOUT:
An HTML document consists of text, which comprises the content of the document and
tags, which, defines the structure, and appearance of the document. The structure of an
HTML document is simple, consists of outer.
<HTML>tag enclosing the document header and body
<HTML>
<HEAD>
<TITLE>the title of HTML document</TITLE>
</HEAD>
<BODY>
This is where the actual HTML documents
Text lies, which is displayed in the browser
</BODY>
</HTML>
Each document has a head and body delimited by the <HEAD> and
<BODY> tag. The head is where you give your HTML document a title and where you
indicate other parameters the browser may use when displaying the document. This
includes the text for displaying the text. Tag also references special and indicates the hot
spots that link your document to other documents.
HTML FORMS:
Creating a form usually involves two independent steps: Creating the layout for the form
itself and then writing a script program on the server side to process the formation you
get back from a form.
To create a form, You use the <FORM> tag. Inside the opening and closing
FORM tags are each of the individual form elements plus any other HTML content to
create a layout for that form.
The opening tag of the FORM element usually includes the attributes:
METHOD and ACTION. The METHOD attributes can be either GET or POST which
determines how your form data is sent to the script to process it.
The ACTION attribute is a pointer to the script that processes the form on the
server side. The ACTION can be included by a relative path or by a full URL to a script
on your server or somewhere else. For example, the following <FORM> tag would call a
script called form-name in cgi-bin directory on server
<FORM Method= post action=http://www.mytservser.com/cgi-bin/form-name.pl>
</FORM>
METHOD ATTRIBUTE:
The other required attribute for the <form> tag sets the methods by which the
browser forms data to the server for processing. There are two ways: the POST method
and GET method. With POST method, the browser sends the data in two steps: the
browser first contacts the form-processing server specified in the action attributes, and
once contact is made, sends the data.
The GET method in the other hand, contacts the form processing server and
sends the form data in a single transaction step: the browser appends the data to the
forms action URL, separated by the question mark (?) character.
Input elements:
Use the <input> tag to define any one of a number of common form elements
including text fields multiple choice lists click able images and submission buttons.
There are many attributers for this tag only that types and name attributes are required for
each element, each type of input element uses only a subset of the followed attributes.
Additional <input> attributes may be required based upon which type of the form
element you specify.
Normalization:
Normalization is the process of organizing data in a database. This includes
creating tables and establishing relationships between those tables according to rules
designed both to protect the data and to make the database more flexible by eliminating
two factors: redundancy and inconsistent dependency.
Redundant data wastes disk space and creates maintenance problems. If data that
exists in more than one place must be changed, the data must be changed in exactly the
same way in all locations. A customer address change is much easier to implement if that
data is stored only in the Customers table and nowhere else in the database.
There are a few rules for database normalization. Each rule is called a "normal
form." If the first rule is observed, the database is said to be in "first normal form." If the
first three rules are observed, the database is considered to be in "third normal form."
Although other levels of normalization are possible, third normal form is considered the
highest level necessary for most applications.
Do not use multiple fields in a single table to store similar data. For example, to track an
inventory item that may come from two possible sources, an inventory record may
contain fields for Vendor Code 1 and Vendor Code 2. But what happens when you add a
third vendor? Adding a field is not the answer; it requires program and table
modifications and does not smoothly accommodate a dynamic number of vendors.
Instead, place all vendor information in a separate table called Vendors, then link
inventory to vendors with an item number key, or vendors to inventory with a vendor
code key.
Create separate tables for sets of values that apply to multiple records.
Records should not depend on anything other than a table's primary key (a compound
key, if necessary). For example, consider a customer's address in an accounting system.
The address is needed by the Customers table, but also by the Orders, Shipping, Invoices,
Accounts Receivable, and Collections tables. Instead of storing the customer's address as
a separate entry in each of these tables, store it in one place, either in the Customers table
or in a separate Addresses table.
Values in a record that are not part of that record's key do not belong in the table. In
general, any time the contents of a group of fields may apply to more than a single record
in the table, consider placing those fields in a separate
table.
Validation Testing: Validation testing demonstrates the traces the requirements of the
software. This can be achieved through a series of black box tests.
System Testing: System testing is actually a series of different tests whose primary
purpose is to fully exercise the computer-based system. Although each test has a different
purpose, all works should verify that all system elements have been properly integrated
and perform allocated functions. The various tests include recovery testing, stress testing,
and perform testing.
2. Adaptive Maintenance:
This is applied when changes is the external environment precipitate
modifications to software.
3. Preventive maintenance:
This improves future maintainability and reliability and provides basis
for future enhancements.
Test cases that reduced by a count that is greater than one, the number of
additional test cases that much be designed to achieve reasonable testing.
Test cases that tell us something about the presence or absence of classes of
errors, rather than an error associated only with the specific test at hand.
JOBSEEKER
.
CRMS
ADMINISTRATOR
LEVEL 1
Job Provider
Job Seeker
Online Test
Corporate
Recruitment
System
Login
Display the
Screen based
on the login
Coding:
Login Form:
using
using
using
using
using
using
using
using
using
using
using
using
System;
System.Data;
System.Configuration;
System.Collections;
System.Web;
System.Web.Security;
System.Web.UI;
System.Web.UI.WebControls;
System.Web.UI.WebControls.WebParts;
System.Web.UI.HtmlControls;
System.Data.SqlClient;
System.Windows.Forms;
}
con.Close();
Registration Form:
using
using
using
using
using
using
using
using
using
using
using
using
System;
System.Data;
System.Configuration;
System.Collections;
System.Web;
System.Web.Security;
System.Web.UI;
System.Web.UI.WebControls;
System.Web.UI.WebControls.WebParts;
System.Web.UI.HtmlControls;
System.Data.SqlClient;
System.Windows.Forms;
System;
System.Data;
System.Configuration;
System.Collections;
System.Web;
System.Web.Security;
System.Web.UI;
System.Web.UI.WebControls;
System.Web.UI.WebControls.WebParts;
System.Web.UI.HtmlControls;
System.Data.SqlClient;
System.Windows.Forms;
Conclusion:
From a proper analysis of positive points and constraints on the component, it can
be safely concluded that the product is a highly efficient GUI based component. This
application is working properly and meeting to all user requirements. This component
can be easily plugged in many other systems.
BIBLIOGRAPHY
The following books were referred during the analysis and execution phase of the project
SOFTWARE ENGINEERING
By Roger s. Pressman
COMPLETE HTML
Steven Holzner
MSDN 2005
By Microsoft