Business Scenario based on Employee Referral Management System

The Max-IT Company is planning to conduct recruitment drive for referrals of their associates. The
company will send e-mail to the associates about the resource requirement details with the skills the
candidate should possess and expected number of work experience in years. The Associates of the
company can go through this information through their referral portal and convey the same to their
friends. The Associates referral details need to be loaded in the database along with latest resume. The
date and time of the interview will be emailed to the associates referral. Finally the status of the
interview of each referral will be updated in the database after the interview.
As a software consultant/developer, build an application using Hibernate (version 4.x) to ease the
Referral management activities. Our important NFR is to make performance oriented software thereby
reducing the number of database visits. The presentation layer will be developed by a dedicated
development team.
Four scenarios are planned to automate in the first release. The detailed explanation of each scenario is
given below.
Database Design:

Note: Referral and Skill has Many-to-Many Relation

Referral and Interview has Many-to-Many Relation

Table Creation:
A Script document is attached below to create the tables.

referralscript.sql
 2

Scenario 1: Register Referrals:

The Referral details need to be registered before the interview. The referrals details will then be
uploaded in the database. These details will be examined by the interview panel and the panel has to
short list the referrals for the interview. The short listed referrals will be intimated through their email-Id.
A note about the associates referral short list will also be intimated to the concerned associate.

Sometime an associate wants to change his contact no and the facility should be available to perform the
changes.

An associate can also refer more than one referrals for the interview.

Populate records into Associate and Referral table for this scenario.
Do not populate record into other table for this scenario.

Method Specification:
Component Method Description
Name Method Name Arguments Output
AssociateDAO createAssociate This method will store the Associate associate void
associates details
AssociateDAO ReferFriends This method will help the Set<Referral> referrals, int void
associate to refer his/her associateId
friends
AssociateDAO AddReferral( From many This method will add referral Referral referral, Associate void
side) details from the many associate
side( Referral side)

C3: Protected
 3

Design Constraint:

Follow the association mentioned in the database design diagram.

Dont use SQL Insert or HQL Insert statements to store the data. Use only hibernate methods for
Insertion.
During updation make sure only the changed property alone take part in the generated SQL
update query

Sequence diagram:

C3: Protected