Employee Recruitment System Report

This comprehensive report documents the development of an Employee Recruitment System (ERS). It begins with a thorough requirement analysis, identifying both functional and non-functional needs through brainstorming sessions. The report then details the system design, including hardw...Read More

Section/Topic
Chapter - 1
REQUIREMENT
ANALYSIS
1 | P a g e

1.1Analysis Study
The purpose of system requirements analysis is to obtain a thorough and detailed
understanding of the business need as defined in project origination and to break it down into
discrete requirements, which are then clearly defined, reviewed and agreed upon with the
users’ decision makers.
During System Requirements Analysis, the framework for the application is developed,
providing the foundation for all future design and development efforts.
Analysis Objectives
 Identify user needs.
 Evaluate system for feasibility.
 Perform economic and technical analysis.
 Allocate functions to system elements.
 Establish schedules and constraints.
 Create system definitions.
Need
 System Requirements Analysis can be a challenging phase, because all of the
major users and their interests are brought into the process of determining requirements.
 Since the requirements form the basis for all future work on the project, from
design and development to testing and documentation, it is of the utmost importance
that the project Team creates a complete and accurate representation of all requirements
that the system must accommodate.
 Accurately identified requirements result from effective communication and
collaboration among all members of the Project Team, and provide the best chance of
creating a system that fully satisfies the needs of customers.
2 | P a g e

 The primary goal of this phase is to create a detailed functional specification
defining the full set of system capabilities to be implemented, along with accompanying
data and process models illustrating the information to be managed and the processes to
be supported by the new system.
1.2 User Requirements
1.2.1 Types of requirements:
 Functional Requirements:
 Input/output
 Processing
 Error handling
 Non-functional requirements:
 Physical environment (equipment locations, multiple sites, etc.).
 Interfaces (data medium etc.).
 User and human factors (who are the users, their skill level etc.).
 Performance (how well is system functioning).
 Documentation.
 Data (qualitative stuff).
 Resources (finding, physical space).
 Security (backup, firewall).
3 | P a g e

1.2.2 Requirement Validation
 Correct
 Consistent
 Complete
o Externally – all desired properties are present.
o Internally – no undefined references.
 Each requirement describes something actually needed by the customer.
 Requirements are verifiable.
 Requirements are traceable.
1.3Brainstorming
The technique that is used for gathering requirements of the Employee Recruitment System is
brainstorming. Brainstorming is a group technique that is used during the requirement
elicitation to understand the requirements. The group discussions may lead to new ideas
quickly and help to promote creative thinking.
It is intended to generate lot of ideas, with full understanding. The theory is that having a
long list of requirements from which to choose is far superior to start with a blank slate.
Requirements in the long list can be categorized, prioritized and pruned.
Brainstorming has become very popular and is being used by most of the companies. It
promotes creative thinking, generates new ideas and provides platform to share views,
apprehensions, expectations and difficulties of implementation. All participants are
encouraged to say whatever ideas come to their mind, whether they seem relevant or not. No
one will be criticized for any ideas, no matter how goofy it seems, as the responsibility of the
participants is to generate views and not to vet them.
This group technique may be carried out with specialized groups like actual user, middle
level managers and stake holders. At times, only superficial requirements may be gathered to
technical questions. In order to handle such situations, a highly trained facilitator may be
4 | P a g e

required. The facilitator may handle group bias and group conflicts carefully. The facilitator
should also be cautious about individual egos, dominance and will be responsible for smooth
conduct of brainstorming sessions. He or she will encourage the participants, ensures proper
individual and group behavior and help to capture the ideas. The facilitator will follow a
published agenda and restart the creative process if it falters.
Every idea will be documented such a way that everyone can see it. White boards, overhead
transparencies or a computer projection system can be used to make it visible to every
participant. After the session, a detailed report will be prepared and facilitator will review the
report. Every idea will be written in simple English so that it conveys same meaning to every
stake holder. Incomplete ideas may be listed separately and should be discussed at length to
make them complete ideas, if possible. Finally, a document will be prepared which will have
a list of requirements and their priority, if possible.
1.4 Final Requirements
(i) User interfaces
The application will have a user friendly and menu based interface.
 Registration page for new user.
 Login page.
 Admin page, where admin approves / reject the company registration.
 There is a screen for displaying various information of employee.
 There is a screen for entering information of new employee.
(ii) Hardware interfaces
 Support for printer for printing employee details.
 Screen resolution of at least 800X600 is required for proper and complete
viewing of screens. Higher resolution will be accepted.
(iii) Software interfaces
 Any windows based operating system.
 Mysql as the DBMS for database.
 IDE (STS) for developing code.
5 | P a g e

(iv) Memory Constraints
 At least 512 MB RAM and 2 GB space on hard disk will be required for
running the application.
(v) Site Adaptation Requirements
 Web browser with cookies enabled.
Product Functions
The website will allow access only to authorized users with specific roles (Administrator-
maintains the website & controls the company registration, HR – add/ modify/ view
employee details).
A summary of the major functions that the website will perform:
 Provide facility to company HR to register.
 HR can enter details of each employee in the organization and view the details
of other employees in different organization.
 Admin can login & accept/reject company registration.
User Characteristics
 Educational level: Users should be comfortable with the English language.
 Experience: No experience is required because of user friendly interface.
 Skills: Users should have basic knowledge and should be comfortable using general
purpose applications on computers.
6 | P a g e

Chapter - 2
DESIGN OF THE
SYSTEM
7 | P a g e

2.1 System Specification
The resources involved for development of the application plays a major role on successfully
developing application according to users’ needs. The resources would vary from human,
hardware, software and environmental resources.
The resources involved in development of ERS are:
2.1.1 Hardware Resources:
 Color Monitor
 Intel i5 processor
 Keyboard
 Mouse
 20 GB Hard Disk
 8 GB RAM
2.1.2 Software Resources:
 Operating System: Windows 7
 Tools: STS , Tomcat 8.1
2.2 Minimum Requirements
The minimum requirement is the basic requirement of the resources required for running the
application successfully without any problem or conflict.
The minimum requirements are:
 Operating System – Windows XP or above.
 Internet Connection – Minimum 512 Kbps speed.
 Device – Any mobile device or PC.
 Browser – Java Enabled Mozilla, Chrome, Safari, etc.
8 | P a g e

2.3 Use Case Diagram
9 | P a g e

Use Case Description
1. login
Name: login
ID: 001
Description: login to the corked wine
Actors: User
Preconditions: Should have user id and password
Post Conditions: Should be able to login successfully
Basic Flow: 1. Visit to the login page
2. Provide uid and password
3. Login
Alternate Flow: 1. Forgot password
2. Automatic register
2. Product Search
Name: Product search
ID: 002
Description: To search the wine, view the detail of wine
Actors: User
Preconditions: Should have user id and password
Post Conditions: Should be able to see the required details
Basic Flow: 1. Login to the corked wine.
2. Enter the user id and password
3. View details of the wine
Alternate Flow: NA
10 | P a g e

3 categories
Name: Categories
ID: 003
Description: To view all product and types of wine
Actors: User
Preconditions: Should have user id and password
Post Conditions: Should be able to view the details
Basic Flow: 1. Login to the corked wine.
2. Select categories and view wine details.
Alternate Flow: NA
4 Shopping cart
Name: Shopping cart
ID: 004
Description: To add/remove/update wine, submit order, checkout in cart,
view price/color/size/qty/subtotal/item discription
Actors: User
Preconditions: Should have user id and password
Post Conditions: Should be able to view the details, add/remove/update wine in
cart
Basic Flow: 1 Login to the corked wine.
2 add/remove/update wine in cart
3 submit order
4 Checkout
5 view wine details.
Alternate Flow: NA
5 User detail
11 | P a g e

Name: User detail
ID: 005
Description: To add name, add business name, Email, address
Actors: User
Preconditions: Should have user id and password
Post Conditions: To add name, add business name, Email, address
Basic Flow: 1 Login to the corked wine.
2 shopping cart
3 submit order
4 we need some information:- To add name, add business
name, Email, address
Alternate Flow: NA
2.4 Class Diagram
12 | P a g e

Chapter - 3
IMPLEMENTATION
&
CODING
13 | P a g e

3.1 Operating System
Windows 7 is a personal computer operating system developed by Microsoft, a version of
Windows NT. Development of 7 occurred as early as 2006 under the codename
"Blackcomb". Windows 7 was released to manufacturing on July 22, 2009, and became
generally available on October 22, 2009, less than three years after the release of its
predecessor, Windows Vista. Windows 7's server counterpart, Windows Server 2008 R2, was
released at the same time.
Windows 7 was primarily intended to be an incremental upgrade to the operating system,
intending to address criticisms faced by its predecessor, Windows Vista (such as performance
improvements), whilst maintaining compatibility with hardware and software designed for
Vista. While retaining a similar appearance to Vista, 7's interface was streamlined, with the
addition of a redesigned taskbar that allows applications to be "pinned" to it, and new
window management features. Other new features were added to the operating system,
including libraries, the new file sharing system HomeGroup, and support for multitouch
input. A new "Action Center" interface was also added to provide an overview of system
security and maintenance information, and tweaks were made to the User Account Control
system to make it less intrusive. 7 also shipped with updated versions of several stock
applications, including Internet Explorer, Windows Media Player, and Windows Media
Center.
3.2 Programming Languages
Java
Java is a small, simple, safe, object oriented, interpreted or dynamically optimized, byte
coded, architectural, garbage collected, multithreaded programming language with a strongly
typed exception-handling for writing distributed and dynamically extensible programs.
Java supports this application and the follow features make it one of the best programming
languages.
 It is simple and object oriented.
 It helps to create user friendly interfaces.
 It is very dynamic.
 It supports multithreading.
14 | P a g e

 It is platform independent.
 It is highly secure and robust.
 It supports internet programming.
Java is a programming language originally developed by Sun Microsystems and released in
1995 as a core component of Sun's Java platform. The language derives much of its syntax
from C and C++ but has a simpler object model and fewer low-level facilities. Java
applications are typically compiled to byte code which can run on any Java virtual machine
(JVM) regardless of computer architecture.
The Java language was created by James Gosling in June 1991 for use in a set top box
project. The language was initially called Oak, after an oak tree that stood outside Gosling's
office - and also went by the name Green - and ended up later being renamed to Java, from a
list of random words. Gosling's goals were to implement a virtual machine and a language
that had a familiar C/C++ style of notation.
JavaBeans Component Architecture
The server and client tiers might also include components based on the JavaBeans component
architecture (JavaBeans component) to manage the data flow between an application client or
applet and components running on the J2EE server or between server components and a
database. JavaBeans components are not considered J2EE components by the J2EE
specification.
JavaBeans components have instance variables and get and set methods for accessing the data
in the instance variables. JavaBeans components used in this way are typically simple in
design and implementation, but should conform to the naming and design conventions
outlined in the JavaBeans component architecture.
Introduction to JDBC
JDBC (Java Database connectivity) is a front-end tool for connecting to a server to ODBC in
that respect, however JDBC can connect only java client and it uses ODBC for the
connectivity. JDBC is essentially a low-level API since any data manipulation, storage and
15 | P a g e

retrieval has to be done by the program itself. Some tools, which provide a higher-level
abstraction, are expected shortly.
The next question that needs to be answered is why we need JDBC, once we have ODBC on
hand. We can use the same ODBC to connect the entire database and ODBC is a proven
technology.
Problem for doing this is ODBC gives a ‘c’ language API, which uses pointers extensively.
Since java does not have any pointes and is object-oriented sun Microsystems, inventor of
java developed to suit its needs.
Requirements to use JDBC
To use JDBC you need a basic knowledge of databases and SQL.A JDK(Java Development
Kit) is required. After that you need to have a back-end database engine for which a JDBC
driver is available. When JDBC drivers are not available JDBC-ODBC bridge drivers are
used to access the database through ODBC. Back-end is not needed when JDBC driver is
capable of storing and retrieving the data itself, or if JDBC-ODBC Bridge and the ODBC
driver can be used to store and retrieve the information.
JDBC Driver Types
The JDBC drivers that we are aware of at this time fit into one of four categories:
1. JDBC-ODBC bridge plus ODBC driver
The java soft bridge product provides JDBC access via ODBC drivers. Note that ODBC
binary code end in many cases database client code must be loaded on each client machine
that uses this driver. As a result, this kind of driver is most appropriate on a corporate
network where client installations are not major problem, or for application server code
written in java in a 3-tier architecture.
2. Native API Partly-Java driver
This kind of driver converts JDBC calls into calls on the client API for oracle Sybase,
Informix, DB2, or other DBMS. Note that, like the bridge driver, this style of driver requires
that some binary code be loaded on each client machine.
16 | P a g e

JAVA SERVER PAGE (JSP)
Java Server Pages technology is the Java platform technology for building applications
containing dynamic Web content such as HTML, DHTML and XML. The Java Server Pages
technology enables the authoring of Web pages that create dynamic content easily but with
maximum power and flexibility.JSPs are translated into servlets at runtime; each JSP's servlet
is cached and re-used until the original JSP is modified. JSP is comparable to Microsoft's
Active Server Page (ASP) technology. Whereas a Java Server Page calls a Java program that
is executed by the Web server, an Active Server Page contains a script that is interpreted by a
script interpreter (such as VBScript or JScript) before the page is sent to the user.
JavaScript
A scripting language developed by Netscape to enable Web authors to design
interactive sites. Although it shares many of the features and structures of the full Java
language, it was developed independently. JavaScript can interact with HTML source code,
enabling Web authors to spice up their sites with dynamic content. JavaScript is endorsed by
a number of software companies and is an open language that anyone can use without
purchasing a license. It is supported by recent browsers from Netscape and Microsoft,
though Internet Explorer supports only a subset, which Microsoft calls Jscript.
JavaScript is used in Web site development to do such things as:
 Automatically change a formatted date on a Web page.
 Cause a linked-to page to appear in a popup window.
 Cause text or a graphic image to change during a mouse rollover.
3.3 Software Tools/Technology
 STS
 Mysql
 JDK 7 or above
 Tomcat 8.1
Development Technology: J2EE, Spring, JDBC, Servlets, JSP, HTML5, CSS3, Bootstrap.
17 | P a g e

Chapter - 4
Sample runs
18 | P a g e

4.1 Main Page (Home)
This is the main home page, when user searches URL this page will appear initially.
19 | P a g e

4.2 checkout
20 | P a g e

4.3 User/login
This page is for users, it will redirect them to the login.
21 | P a g e

4.4 Forgot password
22 | P a g e

4.5 Email:-new password
4.6 Add/remove/update wine in cart
23 | P a g e

4.7 Categories:-all products, types of wine
24 | P a g e

4.8 Product Search
25 | P a g e

4.9 shopping cart
26 | P a g e

4.10 user detail
27 | P a g e

28 | P a g e

Chapter - 5
CONCLUSION
&
REFERENCES
29 | P a g e

5.1 Conclusion
The conclusion is that the ERS system is one in all complete solution for the recruitment
activities and will also help in reducing the overheads of the recruitment process including
cost, effort and complex procedures.
The future of the system is very bright as the organizations will widely adapt the system in
order to reduce the overheads and improve the process of the recruitment. The HR play a
vital role in the recruitment process and this system will work as E-HR as well as do the
background verification for the company.
More over more and more companies will collaborate with each other in order to support and
benefit each other and recruiting the best work force in their companies.
5.2 Limitations
 The system doesn’t have the certificates and document uploading facility, the
improvement is required in that phase.
 The system needs a lot of maintenance and operating cost as large distributed databases
are involved.
 The system has rights transfer issue that needs to be resolved in order to maintain the
integrity of the data.
 The system needs to be more secured in terms of intruder security as it contains most
important and critical data for the user and employee.
30 | P a g e

5.3 Future Scope
The future scope of the Employee Recruitment System is that is can help HR and the
organizations in reducing the load of recruitment and can be used to minimize the
complexity of the process.
This can be implemented as a standardized product for the interview and recruitment
process.
5.4 REFERENCES
5.4.1 Book References
1. Spring in Action by Craig Walls
2. Head First Servlets & JSP, Second Edition, O’Reilly
3. Jquery in Action, Mannings
4. Bootstrap, Jake Spurlock
5. The Testing Fundamentals, Joelle
5.4.2 Web References
1. www.youtube.com
2. www.spring.io
3. www.tutorialspoint.com
4. www.w3schools.com
5. www.javatpoint.com
6. www.google.com
31 | P a g e