corporate recruitement system by yshu007

VIEWS: 65 PAGES: 68

									Corporate Recruitment Management System
                  A Mini Project Report
                           By
                         G.RAMESH
                         08QH1A0539

                   Under the Guidance of
             Mrs.B.V.Ramana,Asst. Professor


 Submitted in partial fulfillment for the award of the degree of

              BACHELOR OF TECHNOLOGY
                         In
          COMPUTER SCIENCE AND ENGINEERING

                     Submitted to




  DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING
         Holy Mary Institute of Technology
      (AFFILIATED TO JNTU-HYDERABAD, AP)
               Hyderabad-500090
                    2011-2012
               Holy Mary Institute of Technology
                        (AFFILIATED TO JNTU-HYDERABAD, AP)




                                         CERTIFICATE



This is to certify that G.RAMESH, 08QH1A0539 has successfully completed his project work at
CSE Department of HIT, Hyderabad entitled “Corporate Recruitment Management
System” in partial fulfilment of the requirements for the award of B.Tech degree during the
academic year 2011-2012

This work is carried out under my supervision and has not been submitted to any other
University/Institute for award of any degree/diploma.




Head of the Department:                                             Internal Guide:

Mrs.S.Kavitha,                                                  Mrs.B.V.Ramana,
Professor, .                                                    Asst.Professor,
Department of CSE,                                              Department of CSE,
HIT, Hyderabad-72.                                              HIT, Hyderabad-72.
                                       Declaration


I do, hereby, declare that the dissertation entitled “Corporate Recruitment Management

System” is an authentic work developed by me in HIT, Hyderabad, under the guidance of
Mrs.B.V.Ramana , Asst.Professor, and submitted as a partial fulfilment of the degree of B .Tech
(CSE.) in JNTU.


I also declare that, any or all contents incorporated in this dissertation have not been submitted in
any form for the award of any degree or diploma of any other institution or university.




                                                                                          G.RAMESH
                                                                                          08QH1A0539
                                                                                             B.TECH
                                                                                                CSE
                                                                                     HIT, Hyderabad.
                               Acknowledgement


        Firstly, I would like to express my immense gratitude towards my institution HIT which
created a great platform to attain profound technical skills in the field of Computer Science, there by
fulfilling my most cherished goal.


        I am thankful to my Principal and Management for providing the necessary infrastructure and
labs.


        I feel privileged to offer my sincere thanks and deep sense of gratitude to Mr. Dr
SONAGIRI CHINA VENKATESWARLU(principal),HIT Mrs.S.Kavitha (Head of the
Department), Mr. K.Ramakrishna ( Project Co-ordinator), of HIT for extending their co-operation
in doing this project.


        It’s   my   pleasure   to    express   my   sincere   gratitude   and   thankfulness      towards
Mrs.B.V.Ramana,Asst. Professor , of HIT for their valuable time and guidance throughout the
B.Tech project.
         My special thanks to all the Faculty members of the Department for their valuable advice at
every stage.
        Last but not the least; I would like to express my deep sense and earnest thanks giving to my
dear Parents for their moral support and heartful cooperation in doing the project. I would also like
to thank all my friends, whose direct or indirect help has enabled me to complete this project.


                                                                                          G.RAMESH
                                                                                               B.TECH
                                                                                                    CSE
                                                                                      HIT, Hyderabad
                                  INDEX

1. Abstract
2. Organizational Profile
3. Software Development Methodology
4. Introduction
       4.1 Purpose.
       4.2 Scope
              4.2.1 Existing system with limitations
               4.2.2 Proposed system features
               4.2.3 Automated process
        4.3 Acronyms and Abbreviations
        4.4 Definitions
        4.5 Overview
5. Overall Description
       5.1 User characteristics
       5.2 Product Perspective
       5.3 Product Functions
       5.4 General Constraints
                5.4.1 Pre conditions
              5.4.2 Post conditions
              5.4.3 Business Rules
6. Specification requirements
       6.1 Hardware requirements
       6.2Software requirements
       6.3 Communication Protocols
          6.4 User Interface requirements
7. Behavioral Description
       7.1 Data Flow.
            7.1.1 Data Flow Diagrams
            7.1.2 Use-Case Documentation
           7.2 Process Flow
            7.2.1 System flow Chart
            7.2.2 Activity Diagrams
8. Functional Description
9. Performance Requirements
10. Design
       10.1 Sequence and Collaboration Diagrams
         10.2 Class Diagrams
         10.3 E-R Diagrams
11. Sample Code
12. System Testing and Implementation
13. Screens
14. Reports
15. Conclusion
16.Bibliography
1. ABSTRACT

INTRODUCTION


Corporate Recruitment System (CRS) is a web based Recruitment System that helps Human
Resources departments of organization find that right talent for their manpower requirements while
optimizing the recruitment process and minimizing the recruitment costs. RS, which is the core
system of E-Recruitment, provides a single point interface and globally accessible workplace for
interaction between the HR department of a company and candidates who apply for job position
directly through an Intranet / Extranet.

CRS provides all the functionality required by HR departments of organizations to post resource
requirements, screen and shortlist candidates, schedule and track online tests and interviews all
through an easy to use web based interface, without capturing the relevant information in its
database, capture, process and analyses information about potential candidates. RS also serves as a
tool that helps HR or Recruitment Managers pay personal attention to each applicant.
.

EXISTING SYSTEM

At present the general recruitment procedure of the organization system is time consuming.
Recruiting employee manually is too much time consuming and economically not suitable.
Therefore there must be a very fast and easy to use system needed to perform the
organization recruitment system.

PROPOSED SYSTEM

The proposed system is online corporate recruitment system. Corporate Recruitment System CRS is
web based tool to reduce communication gap between Job Seekers and Job Providers. Especially in
the fast growing IT market technologies are changing fast, depending upon the fast growing
technologies trend Organizations has to recruit the people. This process will
make recruitment process very easy and fast. This system is designed by keeping in mind both
parties like Job providers and Job Seekers. System allows job seekers to register their details like
skills and experience with the system, and then on the other hand even it allows job providers to post
their requirements with the system. There will be a Administrator who will maintain the site info as
well as the users.
Software Requirements :


Presentation Layer              HTML and JavaScript
Network Layer                   TCP/IP
Web Server Layer                Web logic 8.1 ,Tomcat 6.0
Technologies                    Servlet 2.4 , JSP 2.0
Language Specification          J2SE 1.5
Databases                       Oracle 10g
Operating Systems               Windows 2000, Windows NT 4.0, Windows Xp


Hardware Requirements :


 1. Pentium with 233MHz or better
 2. 64MB RAM minimum (128MB RAM) recommended
 3. 800*600 resolution; 16 bit color (1024*768, 24 bit is recommended)
 4. For offline message audio is preferred, but no need.
   15” monitor (17” monitor recommended for best results)
2. ORGANIZATION PROFILE


TRY LOGIC Soft Solutions AP Private Limited, having its Registered Office at:    # 7-65, 3rd
Floor, Habsiguda ‘X’ Roads, Nacharam Road, adj: Bharat Petroleum, HYDERABAD – 500 007.
A.P. (India), home of a world-class professional software services company. We specialize in
bespoke software development for business applications and outsourced commercial product
development (R&D). Our domain of expertise ranges from B2B eCommerce, ERP, POS, Portal
solutions, Human Resource & Payroll and Customer Relationship Management.

TRY LOGIC is a software development, web design & development Services Company that
specializes in creating tailor made custom applications for enterprises. We use innovative
engagement models, balancing a sophisticated understanding of business with a close attention to
detail, to custom-design our process models and meet our client's automation development needs.

The company has expertise to develop new solutions and products right from the requirement
definition stage to implementation and support. The company has specific skills Client/Server,
databases, intranets, data warehousing, web technologies, WAN, LAN, networking, software design
technologies. The company is capable of creating software solutions covering the entire spectrum of
typical Software Project Life-Cycle consisting of system studies, re-engineering, system design,
software development, testing, data migration, performance tuning and support, this is possible only
because of our core technology expertise, project management skills, software engineering
methodologies, talented, motivated team of software engineers and business domain knowledge
consultants.

With a view to identify and improve the latent talent in the students, primarily to cater their
ACADEMIC requirements and mainly to groom them as INDUSTRY READY PROFESSIONAL,
TRY LOGIC provides an opportunity for the much talented yet untapped students who were
studying professional academic courses of various stream(s) on processes and methodologies under
our unique program called TAC.

TAC (TRYLOGIC ACADEMIC CONCEPT) is a program from TSSPL, under which we shape
future of many students as techies who were supposed to undergo industry relevant technical
education program. The program consist of Technology updating as of the current industry
Requirements along with soft skills improvement and attitude enrichment, more importantly hands
on experience expertise during the project work of the participants under the observation of our
senior programmers on different platforms into our client / real-time projects.

The concept of “Knowledge for Knowledge” is replaced by 'Knowledge for Application'. In such a
situation, TAC try to accomplish everything possible to make learning application oriented. The
advantage and idea is to overcome – time, energy, and money in the recruitment process and to
provide reciprocal benefit to the industries as well as the students who roll out of academic life.

The company constantly focuses on learning, upgrading and disseminating state of art technologies
among its engineers. Keeping abreast with the changes is an on going process with regular in house
training programs. Besides technologies the engineers are trained on quality standards and
personality development

Our VISION is to be globally recognized as a provider of a trusted, reliable resource to quality
InformationTechnology(IT)service solutions.

TRY LOGIC has applied for the membership of STPI Hyderabad unit for software import & export
authorization and support as well for D & O trade license. TRY LOGIC is much interested to be
part of HYSEA & NASSCOM in near future as our applications are in progress. We are a learning
organization and we continually invest time and effort in the area of developing standards & process
documentation in line with our objective of getting ISO Quality Management System certification
and preparation for level 3 CMM-I certification.

                            For more details please visit www.trylogic.in
3. SOFTWARE DEVELOPMENT METHODOLOGY

The methodology used to develop this project is object-oriented methodology is based on function
and procedures. It can be said as the development of software by building self-contained modules as
objects that can be easily replaced, modified and reused. In this environment software is a collection
of discrete objects that encapsulate their data as well as the functionality to model real world
“objects”. Each object has attribute and methods. Objects are grouped into classes. Here each object
is responsible for itself.
This environment emphasizes its cooperative philosophy by allocating tasks among the objects of
the applications. Instead of writing a lot of code we can create a lot of code we can create a lot of
helps to take in an active role.
Object oriented methodology involves mainly
1. Analysis
2. Design
3. Prototyping and testing.
Analysis:
There are 5 important steps in the analysis. They are
        1. Identification of the users/actors.
        2. Development a simple business process model.
        3. Developing the use cases.
        4. Developing the interaction diagrams.
        5. Classifications.
Software Methodology:
Jacobson Methodologies is used to develop the proposed system.
Introduction:
In 1986 BOOCH developed the Object Oriented Design concept is called as BOOTCH METHOD. It
covers both analysis and Design phases of the Object Oriented System, The BOOTCH METHOD
consists o following diagrams:
                 Class diagrams
                 Object diagrams
                 State transition diagram
                 Module diagram
               Process diagram
               Interaction diagram
BOOTCH used the large set of symbols. Even though BOOTCH defines a lot of symbols to
document almost every design decision, if we work with his method, you will notice that you never
use all these symbols and diagrams; this is this main draw back of the BOOTCH METHOD.
In 1991 Jim Raumbaugh develop the OMT (Object Modeling Technique) with the help of his team It
covers analysis, Design and implementation of the system.
OMT separates Modeling into three different parts:
               Object Model
                   Presented by the Object Model and the data dictionary.
               Dynamic model
                   Presented by the State diagrams and Event flow diagrams.
               Functional Model
                   Presented by Data flow and constraints.
There is no traceability in the different phases, both forward and back ward; this is the main
disadvantage of the OMT.
In order to avoid the problems faced in the above two models JACOBSON invented the one model
called as the JACOBSON METHDOLOGIES (Object Oriented Software Engineering). It will cover
the entire life cycle and stress tractability between different phases, 0both forward and back ward,
Additionally he invented the Use case diagrams, these diagrams are necessary to understanding
system requirement. It captures the goal of the system. It is used to identify the Use cases and
External users (external users are the users who interact with our system to complete the task)
THE JACOBSON ET AL. METHDOLOGIES:
JACOBSON METHDOLOGIES (Object Oriented Software Engineering) OOSE cover the Entire
life cycle and stress trace ability between the different phases, both forward and backward. And Use
case diagrams, these diagrams are necessary to understanding system requirement. It captures the
goal of the system. It is used to identify the USE CASES and External users (external users are the
users who interact with our system to complete the task)
The Use case Description must contain
               HOW and WHEN the use case begins and ends.
               The interaction between the use case and its actors, including WHEN the interaction
                occurs and WHAT is exchanged.
               HOW and WHEN the use case will need data stored in the system or will store data
                in the system.
               EXCEPTION TO THE flow of events.
               HOW and WHEN concepts of the problem domain are handled.
By using the use case model we will find the External users, External users are the users who will
interact with our system to complete the task. Every single use case should describe one main flow
of events. An exceptional additional flow of events could be added.
OBJECT ORIENTED SOFTEWARE ENGINEERING
Object oriented software engineering also called, as the objectory. It is build around several models:
                       USE CASE MODEL: The use-case model defines the outside (actor) and
                        inside (use case) of the systems behavior.
                       DOMAIN OBJECT MODEL: The objects of the “real” world are mapped in
                        to the main object model.
                       ANALYSS OBJECT MODEL: The analysis object model presents how the
                        source code (implementation) is carried out and written.
                       IMPLIMENTATON MODEL: The implementation model represents the
                        implementation of the system.
                       TEST MODEL: The test model constitutes the test plan, specification and
                        reports.
JACOBSON METHDOLOGY consists o following diagrams:
               Use case Diagrams
               UML activity diagram
               UML use Case Diagram
               Sequence diagrams
               Class diagrams
               Business class diagrams
USE CASE DIAGRAMS:
A use case describes a sequence of actions that provide something of measurable value to an actor
and is drawn as a horizontal ellipse an actor is a person, organization, or external system that plays a
role in one or more interactions with your system.
UML ACTIVITY DIAGRAM:
Activity diagrams are used to document workflows in a system, from the business level down to the
operational level. When looking at an Activity diagram, you'll notice elements from state diagram,
the Activity diagram is a variation of the state diagram where the "states" represent operations, and
the transitions represent the activities that happen when the operation is complete. The general
purpose of Activity diagrams is to focus on flows driven by internal processing vs. external events.
SEQUENCE DIAGRAMS:
UML sequence diagrams model the flow of logic within your system in a visual manner, enabling
you both to document and validate your logic, and are commonly used for both analysis and design
purposes. Sequence diagrams are the most popular UML artifacts for dynamic modeling, which
focuses on identifying the behavior within your system.
CLASS DIAGRAMS:
A class diagram describes the static structure of the symbols in your new system. It is a graphic
presentation of the static view that shows a collection of declarative (static) model elements, such as
classes, types, and their contents and relationships. Classes are arranged in hierarchies sharing
common structure and behavior, and are associated with other classes
4. INTRODUCTION


4.1 Purpose

The project entitled”Corporate Recruitment System” automates the Online Recruitment. This system
is one, which helps out the HR personnel in the Recruitment of new candidates to the company and
helps them the recruitment process as a whole. For the HR Personnel the options available in the
system would be mainly under four broad headings namely:

      Requirements
      Resume Processing
      Online Test Queries
      Message From Users

4.2 Scope:

Corporate Recruitment System (CRS) is a part of the Human Resource Management System that
structures and manages the entire recruitment process. This online recruitment service system will
primarily focus on the posting and management of job vacancies. However, this will be the initial
step towards achieving the longer-term goal of delivering broader services to support recruitment.

This will provide service to the potential job applicants to search for working opportunities.
Applicants will, if they choose, be able to make an application online. CRS will also allow Job
Provider to establish one-to-one relationships with candidates, by keeping in close communication
with them through out the application/interview/hiring process, even allowing the candidates to track
the progress of their application. In other words, enables the employer to treat candidates like
customers.


4.2.1 Existing System with Limitations:

       Existing System

       The Job Providers carries 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 either on paperwork or on in
       broken, distributed and isolated automation such as use of Microsoft Excel Sheets. The
       problem that arises in such a scenario is that the process is too cumbersome and demanding
       as well.
       Limitation of the Existing System
        Non-availability of data and when required.
        Exams are conducted manually, it is waste of papers and same questions will be repeated
          for more than one candidate.
        Highly inconsistent information across the department along with the overhead of
          redundant data management across department.
        Duplication of data gathering and maintenance efforts.
        High level of human intervention needed and hence usage of the system depends on the
          skill of the individual.
        Does not enable Decision Support System.
        No system to keep track of the resumes of the candidates.


4.2.2 Proposed System features:

   Proposed System


The proposed system “Corporate Recruitment System” in JSP and Oracle8 will include all the
features carried out by manual system and also add certain additional features so that the package
will form a definite improvement.

Corporate Recruitment System (CRS) has all the features and functions required for executing a
successful recruitment task, providing exceptional case of use for recruitment directors.

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, deleting
       and modifying apart from valuable search facility.
      Database to store the candidate’s details securely.
      Customizable authentication to control access to database files using assigned user login and
       password control.
      Provides authentication to write the online.
      Provides information to the managers so that they can make judgment about particular
       situations.
      Candidate applications are automatically scored and ranked against job description criterion.
      Reduction in the costs of hiring – there will be between 50 – 60 percent decrease in the cost
       of hiring.
      Reduction in the time to hire – the result of targeting candidates accurately in an online
       environment means less ‘Paper; administration and more time ‘face-to-face’ with the
       candidate.
      Automatic generation of the Login ID and the password for the candidates if selected for
       online test by the HR personnel.
4.2.3 Automated Process:

       The Corporate Recruitment System is broadly divided into 4 modules. They are:

               Login Module
               Job Provider Module
               Job Seeker Module
               Online Test Module

4.3 Acronyms, Abbreviations:

CRS                Corporate Recruitment System
ES                 Existing System
PS                 Proposed System
4.4 Definitions:
    Job Seeker:
Job seeker is a person who uses the system to find a job and use the recruitment process.
   Job Provider:
Job Provider uses the system to provide opportunities to the seeker. He acts just as an administrator.

4.5 Overview:

Corporate Recruitment system is an individual module of HR Personnel, developed to make
recruitment process an easy operation. In this system each user is authorized with user name,
password and authenticated by the super user .
This application is very much useful for job seekers and administrators, who arrange the seeking
processes
5. OVERALL DESCRIPTION

5.1 User Characteristics:

Corporate Recruitment System User Roles.
         Job Provider.
         Job Seeker

         Job Provider

         For the HR Personnel the options available in the system would be mainly under four broad
         headings and we can call it as Sub Modules of Job Provider Module.

               Requirements
               Resume Processing
               Online Test Queries
               Message From Users


         Job Seeker

         This module provides an interface to the candidates, a web site to apply for the vacant
         positions. The candidate can directly apply for any of the jobs or can view their application
         status. The different functions made available for the candidate’s convenience are:

         For the Job Seeker the options available in the system would be mainly under some broad
         headings and we can call it as Sub Modules of Job Seeker Module.

               In Box
               Post Resume
               Update Resume
               View All Jobs
               Update Personal Information
               Change Password Information
               Feedback
               Faq’s
               Logout
5.2 Product Perspective:


         Home Page
             Job Provider
             Job Seeker
             Online Test
             Search Jobs
         Registration
         Login
         Job Provider
             Jobs
             Test Queries
             Resume Processing
             Message from users.
         Job Seeker
             Post Resume
             Search Jobs
             Personal Information

         Reports on Jobs
         Messages from Users



5.3 Product Functions:

   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.

   Job Provider Module

      For the HR Personnel the options available in the system would be mainly under four broad
      headings and we can call it as Sub Modules of Job Provider Module.

             Requirements
             Resume Processing
             Online Test Queries
             Message From Users
             Authentication
Requirements Module:

   The module would help the HR to maintain the opportunity list available in the company.
   The different functionality provided were:

Adding New Requirement:

   Whenever a new job position would be vacant, the HR can create a new one. The appropriate
   code for validation of the input details was coded.

Modifications of the Requirements List:

   The HR from time to time would need to view/modify the different job positions in the
   company. The listing is based on different criteria: all the job positions, based on the Skill set
   required, based on the status of the Application, Based on the experience required or On the
   Basis of the Last Date of Apply. The HR can know the complete details about a particular
   opportunity such as, the date on which it was created, the day on which it was modified and
   the HR who created it. If he/she needs to modify, then the details of it would be displayed as
   that the fields Description, Qualification, Skill Set, Last date to apply and Experience etc. and
   the same can be modified.

Cleaning Up of the Requirement list Data:

   The requirements with status as”Processed” would be listed. If the HR chooses to cleanup
   any of the requirement details, then all the candidate details pertaining to that particular job
   code would be deleted from the database and the details of the job code would be stored in
   the backup for future use.

Resume Processing Module:

   The module is useful for the maintenance of the resumes obtained for any job position
   available in the company.

   Different functions provided are:

          Adding a new Resume:
           The function provides provision for the HR to add a new resume to the database. The
           resume can be obtained in a number of different ways – through post or through web
           site. The details of the candidate will be stored in the database. The date on which the
           application was obtained would also be stored so that it can be checked that the
           application received after the last to apply is lapsed will not be considered for
           processing.

          View or Modification of the applicant’s list:
           The HR from time to time would need to view/modify the list of candidates applied
           for a job position in the company. The listing is based on different criteria: All
    candidates, Based on the Job Code for which the candidate has applied or Based on
    the Skill Set of the candidate, Based on Experience or Based on the Status of the
    application of candidate. The HR can view the details of a candidate to know the
    contact details or the mode through which the candidate has applied for that position.
    Provisions are provided where the HR can directly send mail to the candidate by just
    clicking the mail ID of the contact person. If needed to modify, then the details of the
    candidate would be displayed so that the fields of Candidate Name, Address, Mail ID,
    Skill Set, Qualification, and Experience etc. would be displayed and the same can be
    modified. If the HR pts to change the status for the candidate application, then he/she
    can provide an appropriate status and save the changes made. The details of the
    overall operation carried out during status change are stated in the function: Updating
    the application status below:

   Processing of the applications for different jobs:
    Once the last date of apply for any job position that was vacant is elapsed, the status
    of the job position would be made as ‘Invalid’. When the HR wants to process the
    applications, a list of all job codes for which the Lat date to apply has been over with
    the status as ‘Invalid’ and status not as ‘Processed’ will be listed. The HR when
    chooses to process for a particular job code, the system will list in the following basis:

       1. It would check that the candidate has applied before the last date to apply.
       2. It would check that the resume is not from the same candidate who is in the
          wait-for-list and for the same job position.
       3. It would check the resume satisfies the experience requirement for that job.
       4. The resume, which satisfies above three, would be examined further for
          percentage of marks obtained.
       5. If all above four were satisfied, the resume would be checked for the skill set.
          If it suffices at least 60% of the minimum skill for the position, then it would
          be considered as an eligible application for shortlist.

    All the applications that are eligible would be listed along with the status so that the
    HR can change it as needed. The updating of status is described as below:

   Updating the application Status:
    When status of application of a candidate is to be updated, the HR can update it to
    any of the following – Test Scheduled, Interview Rejected or Application Rejected. In
    case of Application Rejected, the reason for the rejection is to be specified. For Test
    or Interview Scheduled, the date, time and place of the schedule ahs to be stated along
    with the Group ID is to be stated. Before this the login ID and the Password for the
    candidate is generated.

   Cleaning up the database from unwanted Resumes:
    The list of resumes, which has been in the ‘Wait For’ list, would be selected and
    displayed. If the HR opts to clean these resumes, then he can select them and clean
    the database. Once the resume of a candidate has been cleaned up, he can apply to the
    position again, i.e. after 6 months once he has applied. The details pertaining to theses
          candidates would be deleted from the database and hence the database cleaned from
          unwanted information.

Online Test Queries Module

   Regarding the Online Test Questions the HR will have the following options:

   Adding New Questions: The HR can add the new questions for online test.

   View or Modifications of Questions: The HR can view or modify a particular question
   whichever he/she wants to view or modify.

   Deletion of Questions: For every 6 months old questions will be deleted and new questions
   will be added.

Authentication Module

   The module would help the HR to maintain the Authentication List available in the company.
   The different functionality provided were:

   Adding New Authentication: Whenever HR Manager wants to create a new authentication
   the HR can create a new one. The appropriate code for validation of the input details was
   coded.

   Modification of the Authentication List: HR can view or modify the existing Authentication.

Job Seeker Module:

   This module is an interface to the candidates to apply for the vacant positions. The candidate
   can directly apply for any of the jobs or can view their application status. The different
   functions made available for the candidate’s convenience are:

   For the Job Seeker the options available in the system would be mainly under some broad
   headings and we can call it as Sub Modules of Job Seeker Module.

         In Box
         Post Resume
         Update Resume
         View All Jobs
         Update Personal Information
         Change Password Information
         Feedback
         Faq’s
         Logout
   In Box
   The list of all information about the online test. Whether he was accepted or rejected for
   online test. If he accepted for online test then he can write the online test and every
   information stored on Inbox sent by the Job Provider.

   Post Resume
   The CRS will provide to the Job Seeker can post his resume to the HR Persons for further
   processing.

   Update Resume
   The CRS will provide to the Job Seeker can update his resume for further processing.

   View All Jobs
   Job Seekers can view all Jobs existing in the Organizations and can apply for particular jobs
   also.


   Update Personal Information
   The CRS provides to Job Seekers can Update his personals and as well as Password also.

   Change Password Information
   The CRS provides to Job Seekers can change his Password details.


   Feedback
   The CRS provides to users can send feedback to Job providers.

   FAQ’S
   The CRS also provides the various FAQ’s regarding technical skills and other sections i.e.
   documentation on some advanced technologies like J2EE., .Net etc.

Online Test Module:

   This module helps the HR to conduct the online test for the selected candidates. Here the HR
   will provide separate login and password for each candidate. This module will fetch
   questions randomly from the database and displays to the candidate. The time limit to write
   the test maintained automatically. The result will be displayed immediately after clicking on
   the submit button.
5.4 General Constraints:
5.4.1 Pre Conditions:

          Every user must posses valid user name and password to enter the system.



5.4.2 Post Conditions:

          User should submit Resume after logging in.
          Provider should maintain updated information regarding jobs.




6. SPECIFICATION REQUIREMENTS
6.1 Hardware Requirements:

    1. Pentium4 with 233MHz or better
    2. 256MB RAM minimum recommended
    3. 800 * 600 resolution; 16 bit color (1024*768, 24 bit is recommended)


6.2 Software Requirements:



 Presentation Layer                HTML & DHTML and JavaScript
 Network Layer                     TCP/IP
 Web Server Layer                  Web logic 8.1
 Technologies                      JSP and JDBC
 Language Specification            J2EE 1.4
 Databases                         Oracle 8i
 Operating Systems                 Windows 2000, Windows NT 4.0, Windows 9x

4 User Interface Requirements:

    List of screens:

           Home Page
           Login Page
           Registration Page
        Job Seeker Modules Page
        Change Password Page
        Job Provider Registration
        Job Provider Modules
        Job Provider and Requirements page
        Online Test Page
        Jobs Report Page
        Response from Users
7. BEHAVIORAL DESCRIPTION
7.1. Data Flow:
7.1.1 DFD:


Main process (0.level)
1 Corporate Recruitment System (1.level)
2. Detailed Level (2 Level)
7.1.2 Use Case Documentation:

Registration




                         Provider


                                                      Registration


                          Seeker



 Document Version                            1.0
 Document Id                                 UC-001
 Document Title                              Use-case Documentation for Registration

 Use-case ID :        UC-100                 Use-case Name :         Login
 Version     :        2.0
 Source       :Corporate                   Date             :      16-12-2006
 Recruitment System
 Summary      : Job provider and Job Seeker need to register with the system to access it

 Preconditions:

 Trigger          :
 Actors        : Job Provider, job Seeker
 Basic Course of Events:

 Actor Interactions : users enter valid information.
 System Response : System registers the users.
 Alternative Paths : Not Applicable
Conclusion          :On entering the information, users get registered

Post Conditions     : Every user will be allotted with a with id & pwd provide

Business Rules      : Not Applicable.

Assumptions         : Not Applicable

Author              :
Remarks             : Not Applicable



Login




        Provider                              <<extend>>




                                  Login                      Modules


        Seeker




Document Version                            1.0
Document Id                                 UC-001
Document Title                              Use-case Documentation for Login

Use-case ID    :   UC-101                   Use-case Name :         Login
Version        :   2.0
Source       :Corporate                   Date            :       16-12-2006
Recruitment System
Summary      : Job provider and Job Seeker need to enter valid credentials to enter the system
Preconditions: Users Need to register with the system

Trigger        : System Validates the users.
Actors           : Job Provider, job Seeker

Basic Course of Events:

Actor Interactions :      users enter valid Credentials
System Response :         System validates.

Alternative Paths : Not Applicable
Conclusion        :On entering the n\valid credentials, Users enter into the
system

Post Conditions      :



Business Rules       : Not Applicable.

Assumptions          : Not Applicable

Author               :
Remarks              : Not Applicable
Job Provider Module




                                               Modules



                                         <<include>>
                                                            Jobs
                                            <<include>>


      Provider                 Modules      <<include>>
                                                          Queries




                                                       Resume process




Document Version                           1.0
Document Id                                UC-003
Document Title                             Use-case Documentation for Provider Module

Use-case ID   :   UC-103                   Use-case Name : Provider module
Version       :   2.0
Source       :Corporate                   Date             :        16-12-2006
Recruitment System
Summary      : Job provider access his modules in the system
Preconditions: N/A

Trigger       : All the corresponding links are displayed.
Actors           : Job Provider

Basic Course of Events:

Actor Interactions : Provider accesses the links in the module.
System Response : System provides the links requested

Alternative Paths : Not Applicable
Conclusion           : Provider Can manipulate the information in modules.
Post Conditions      :


Business Rules       : Not Applicable.

Assumptions          : Not Applicable

Author               :
Remarks              : Not Applicable
Job Seeker Module



                                        seeker modules


                                         <<include>>

                                                           Resume
                                          <<include>>


      Seeker                modules
                                         <<include>>
                                                            Jobs




                                                        Personal Info




Document Version                          1.0
Document Id                               UC-003
Document Title                            Use-case Documentation for Seeker Module

Use-case ID   :   UC-104                  Use-case Name : Seeker module
Version       :   2.0
Source       :Corporate                  Date             :        16-12-2006
Recruitment System
Summary      : Job Seeker access his modules in the system

Preconditions: N/A
Trigger        : All the corresponding links are displayed.
Actors           : Job Seeker

Basic Course of Events:

Actor Interactions : Seeker access the links in the module.
System Response : System provides the links requested

Alternative Paths : Not Applicable
Conclusion        : Seeker can view information related to jobs and can add
details
Post Conditions   : If Seeker qualifies, he gets job using this system


Business Rules       : Not Applicable.

Assumptions          : Not Applicable

Author               :
Remarks              : Not Applicable
7.2. Process Flow:

System Flow Chart:
7.2.2   Activity Diagrams:




                                         Seeker



                                     Login




                No
                                             Validate User



                                       Yes



                     Module                        Online test




          Post          Job Report   Personal Info
         Resume




                                                      Logout
                              Provider




                         Login




          no
                                 Validate




                             yes

                        Module




Process        Job reports            Queries     User
resume                                          Feedback




                                   Logout
   8. FUNCTIONAL DESCRIPTION


       Corporate Recruitment System provides over all Functionality of recruiting, that
integrates all the methodologies of corporate recruitment. This system involves external
entities, processes etc… which integrate with each other and describes the flow between
them. The external entities are Job Provider and Job seeker. The processes are
Registration, login, online test, post resume, Jobs, Resume processing, Queries, Update
etc… Provider is a designated person who is in charge of overseeing all the resumes and
processing the resumes. Job seeker logs into the system for seeking a job and posts his
resume. He has the privileges of manipulating his details and can have an online test and
can move further in the process.
9. PERFORMANCE REQUIREMENTS

This part of the SRS specifies the performance constraints on the software system,
specifying the requirements relating to the performance characteristics of the system.
Two types of performance requirements:
   1. Static Requirements
   2. Dynamic Requirements
Static Requirements are those that do not impose constraint on the execution
characteristics of the system. These include requirements like the number of terminals to
be supported, the number of simultaneous users to be supported, and the number of files
that the system has to process and their sizes.
Dynamic Requirements are which specify constraints on the execution behavior of the
system. These typically include response time and throughput constraints on the system.
Response time is the expected time for the completion of an operation under specified
circumstances. Throughput is the expected number of operations that can be performed at
a time.
Performance Requirements Include:
Security:
The system that we developed is the secure One. That is the system cannot be used by a
third party person who has not got registered to the system.
Reliability:
The system that we developed is a reliable one. That is once the event is managed
Scalability:
The system that we developed can be extended in future. That is our system is scalable.
Accuracy of data:
The system which we developed is very accurate. Event Management generated to the
event is accurate.
Safety:
The system which we developed is safe.
Privacy:
The system is very much private because it is available to only those who have got
registered to the system.
Portability:
The system which we developed is of portable because once it is developed it can run on
any platform.
Modifiability and Extensibility:
The system which we developed can be modified and can be extended in future.
10. DESIGN

The main focus of the analysis phase of Software development is on “What needs to be

done”. The objects discovered during the analysis can serve as the framework or Design.

The class’s attributes, methods and association identified during analysis must be

designed for implementation language. New classes must be introduced to store

intermediate results during the program execution.

Emphasis shifts from the application domain o implementation and computer such as user

interfaces or view layer and access layer. During analysis, we look at the physical entities

or business objects in the system, that is, which players and how they cooperate to do the

work of the application. These objects represent tangible elements of the business.

During the Design phase, we elevate the model into logical entities, some of which might

relate more to the computer domain as people or employees. Here his goal is to design

the classes that we need to implement the system the difference is that, at this level we

focus on the view and access classes, such as how to maintain information or the best

way o interact with a user or present information.

Design process:

During the design phase the classes identified in object-oriented analysis Must be

revisited with a shift focus to their implementation. New classes or attribute and Methods

must be an added for implementation purposes and user interfaces. The object-oriented

design process consists of the following activities:

1. Apply design axioms to design classes, their attributes, methods, associations, structure

And protocols Refine and complete the static UML class diagram by adding details to the

UML diagram. This step consists of following activities. *Refine attributes *Design
methods and protocols by utilizing a UML activity diagram to represent the method’s

algorithms.

*Refine associations between classes

*Refine class hierarchy and design with inheritance

*Iterate and refine again

2. Design the access layer

      Create mirror classes: For every business class identified and created. For

       example, if there are three business classes, create three access layer classes.

      Identify access layer class relationships.

      Simplify classes and their relationships: The main goal here is to eliminate

       redundant classes and structures.

       *Redundant classes: Do not keep two classes that perform similar translate results

        activities. Simply select one and eliminate the other.

       *Method classes: Revisit the classes that consist of only one or two methods to

       see if they can be eliminated or combined with existing classes.

      Iterate and refine again.

       Define the view layer classes

              Design the macro level user interface, identifying view layer objects.

              Design the micro level user interface, which includes these activities:

               * Design the view layer objects by applying the design axioms and

                 corollaries.

               * Built a prototype of the view layer interface.

                      Test usability and user satisfaction
                     Iterate and refine.

   4. Iterate refine the whole design process.

   From the class diagram, you can begin to extrapolate which classes you will have to

   built and which existing classes you can reuse. As you do this, also begin this, also

   begin thinking about the inheritance structure. If you have several classes that seem

   relates but have specific differences.

   Design also must be traceable across requirements, analysis, design from the

   Requirements model.




DESIGN AXIOMS:

Axioms are a fundamental truth that always is observed to be valid and for which there is
no counter example or exception. Such explains that axioms may be hypothesized form a
large number of observations by nothing the common phenomena shared by all cases;
they cannot be proven or derived, but they can be invalidated by counter examples or
exceptions. A theorem is a proposition that may not be self-evident but can be proven
from accepted axioms. If, therefore, is equivalent to a law or principle. A corollary is a
proposition that follows from an axioms or another proposition that has been proven.
Again, corollary is shown to be valid or not valid in the same manner as a theorem. In the
two important axioms axiom 1 deals with relationships between system components and
axiom 2 deals with the complexity of design.
The following the two important axioms:
Axiom 1: The independence axiom, which maintain the independence of the components.

Axiom 2: The information axioms that maintain the information content of the design.
Axioms1 states that, during the design process, as we go from requirement and use case

to a system component, each component must satisfy that requirement without affecting

other requirements.

An axiom 2 is concerned with simplicity. Scientific theoreticians often rely on a general

rule known as Occam’s razor, after William of Occam. He says, “The best theory

explains the known facts with a minimum amount of complexity and maximum

simplicity and straightforwardness.”

The best designs usually involve the least complex code but not necessarily the fewest

number of classes or methods. Minimizing complexity should be the goal, because that

produces the most easily maintained and enhanced application. In an object-oriented

system, the best way to minimize complexity is to use inheritance and the systems built in

classes and to add as little as possible to what already is there.

From the two design axioms, many corollaries may be derived as a direct consequence of

the axioms. These corollaries may be more useful in marking specific design decisions,

since they can be applied to actual situations.

   1. Uncoupled design with less information content: Highly cohesive objects can

        improve coupling because only a minimal amount of essential information need

        be passed between objects. The degree or strength of coupling between two

        components is measured by the amount and complexity of information

        transmitted between them.

   2.   Single purpose: Each class must have single, clearly defined purposes.

   3.   Large number of simple classes: Keeping the classes simple allows

        reusability.Large and complex classes are too specialized to be reused.
   4.   Strong mapping: There must be a strong association between the physical system

        and logical design. During the design phase, we need to design this class, design

        its methods, its association with other objects. So a strong mapping links classes

        should be identified.

   5. Standardization: promote standardization by designing interchangeable and

        reusing existing classes or components.

   6. Design with inheritance: Common behavior must be moved to super classes. The

        super class-sub class structure must make logical sense.

Refining attributes and methods:

Attributes identified in object oriented analyzed must be refined in the design phase. In

the analysis phase, the name of the attributes was sufficient. But in the design phase,

detailed information must be added to the model. The three basic types of attributes are:

   1. Single valued attributes: This has only value or state.

   2. Multiplicity or multivalue attributes: This has a collection of many values at any

        point in time.

   3. Instance connection attributes: This is required to provide the mapping needed by

        an object to fulfill its responsibilities.



UML attribute presentation:

Visibility name: type-expression=initial-value

   Visibility indicates either public visibility or protected visibility or private visibility.

   The public visibility indicates that the attribute can be accessible to all classes. The

   protected visibility indicates that the accessibility is given to the subclasses and
   operations of the class. Where as the private visibility indicates that the accessibility

   can be given only to the operations of the class only.

   Type expression is a language dependent specification of the implementation type of

   an attribute. Initial value is a language dependent expression for the initial value is

   optional.



10.1 Sequence Diagrams and Collaboration Diagrams


Step 1:
Object List:
Nouns:
         Job Provider
         Job Seeker
         Online Test.
         Jobs
Concepts:
         Registration
         Login
         Post Resume
         Update Resume
         Resume Processing
         Test Queries
         Edit Queries
         Add Queries
         Search Jobs
         Performance


Step 2:
Refined Objects:
          Job Provider----- (registration, Login, Resume Processing)
      Job Seeker------ (Registration, Login, post Resume, Update Resume)
      Jobs---------- (jobs, search Jobs)
      Queries------- (Test Queries, Add Queries, Edit Queries)

Interaction Diagrams:

Case 1:
10.1 Sequence Diagram:




     Provider        Seeker          Login              Provider         Seeker          Online Test          Logout
                                                         module          Module




                      1:
                                2:


                                3:
                                              4:

                                                          5:
                                                                                   6:
                                                                                             7:

                                                                                                       8:




       Seeker         Module         Online Test           Post          Edit Profile         Jobs             Logout
                                                          Resume
                1:

                           2:
                                         3:


                                                   4:


                                                               5:


                                                                    6:
                                                                             7:
                                                                                        8:

                                                                                                  9:

                                                                                                        10:
             Provider        Module        Jobs        Queries        Resume           User           Logout
                                                                      Process        Feedback
                        1:

                                      2:
                                           3:
                                                  4:

                                                        5:
                                                                 6:
                                                                        7:

                                                                                8:

                                                                                        9:


                                                                                                10:




10.2   Class Diagram:




   R Diagram:
10.3 E-R DIAGRAM




11. Sample Code
12. SYSTEM TESTING AND IMPLEMENTATION
TESTING CONCEPTS

Testing Methodologies

       •      Black box Testing:
       •      White box Testing.
       •      Gray Box Testing.

Levels Of Testing
       •      Unit Testing.
       •      Module Testing.
       •      Integration Testing.
       •      System Testing.
       •      User Acceptance Testing.

Types Of Testing
      •       Smoke Testing.
       •      Sanitary Testing.
       •      Regression Testing.
       •      Re-Testing.
       •      Static Testing.
       •      Dynamic Testing.
       •      Alpha-Testing.
       •      Beta-Testing.
       •      Monkey Testing.
       •      Compatibility Testing.
       •      Installation Testing.
       •      Adhoc Testing.
       •      Ext….
Test Case Documentation

STLC
   •                Test Planning.
   •                Test Development.
   •                Test Execution.
   •                Result Analysis.
   •                Bug-Tracing.
   •                Reporting.

Microsoft windows standards
Manual Testing
Automation Testing Tools
      •      Win Runner.
           •        Test Director

Testing:
          The process of executing a system with the intent of finding an error.
          Testing is defined as the process in which defects are identified, isolated,
           subjected for rectification and ensured that product is defect free in order to
           produce the quality product and hence customer satisfaction.
          Quality is defined as justification of the requirements
          Defect is nothing but deviation from the requirements
          Defect is nothing but bug.
          Testing --- The presence of bugs
          Testing can demonstrate the presence of bugs, but not their absence
          Debugging and Testing are not the same thing!
          Testing is a systematic attempt to break a program or the AUT
          Debugging is the art or method of uncovering why the script /program did not
           execute properly.


Testing Methodologies:
              Black box Testing: is the testing process in which tester can perform testing on
               an application without having any internal structural knowledge of application.
               Usually Test Engineers are involved in the black box testing.
          White box Testing: is the testing process in which tester can perform testing
           on an application with having internal structural knowledge.
           Usually The Developers are involved in white box testing.
          Gray Box Testing: is the process in which the combination of black box and
           white box techniques are used.
Levels of Testing:




           Module1                  Module2                   Module3
            Units                     Units                      Units



                     i/p       Integration o/p i/p       Integration o/p




 System Testing: Presentation + business +Databases
 UAT: user acceptance testing




STLC (SOFTWARE TESTING LIFE CYCLE)
Test   Planning:           1.Test   Plan is    defined    as     a   strategic   document which
                           describes the procedure how to perform various testing on the total
                           application in the most efficient way.
                           2. This document involves the scope of testing,
                           3. Objective of testing,
                           4. Areas that need to be tested,
                           5. Areas that should not be tested,
                           6. Scheduling Resource Planning,
                           7. Areas to be automated, various testing tools
                          Used….
Test Development:      1. Test case Development (check list)
                       2. Test Procedure preparation. (Description of the test cases)
Test Execution:        1. Implementation of test cases. Observing the result.
Result Analysis:       1. Expected value: is nothing but expected behavior
                          Of application.
                      2. Actual value: is nothing but actual behavior of the
                          application
Bug Tracing:            Collect all the failed cases, prepare documents.
Reporting:              Prepare document (status of the application)


Types Of Testing:
> Smoke Testing: is the process of initial testing in which tester looks for the
availability of all the functionality of the application in order to perform detailed testing
on them. (Main check is for available forms)
> Sanity Testing: is a type of testing that is conducted on an application initially to
check for the proper behavior of an application that is to check all the functionality are
available before the detailed testing is conducted by on them.
> Regression Testing: is one of the best and important testing. Regression testing is
the process in which the functionality, which is already tested before, is once again tested
whenever some new change is added in order to check whether the existing functionality
remains same.
>Re-Testing: is the process in which testing is performed on some functionality which
is already tested before to make sure that the defects are reproducible and to rule out the
environments issues if at all any defects are there.
Static Testing: is the testing, which is performed on an application when it is not been
executed.ex: GUI, Document Testing
Dynamic Testing: is the testing which is performed on an application when it is being
executed.ex: Functional testing.
Alpha Testing: it is a type of user acceptance testing, which is conducted on an
application when it is just before released to the customer.
 Beta-Testing: it is a type of UAT that is conducted on an application when it is
released to the customer, when deployed in to the real time environment and being
accessed by the real time users.
 Monkey Testing: is the process in which abnormal operations, beyond capacity
operations are done on the application to check the stability of it in spite of the users
abnormal behavior.
Compatibility testing: it is the testing process in which usually the products are tested
on the environments with different combinations of databases (application servers,
browsers…etc) In order to check how far the product is compatible with all these
environments platform combination.
Installation Testing: it is the process of testing in which the tester try to install or try
to deploy the module into the corresponding environment by following the guidelines
produced in the deployment document and check whether the installation is successful or
not.
Adhoc Testing: Adhoc Testing is the process of testing in which unlike the           formal
testing where in test case document is used, with out that test case document testing can
be done of an application, to cover that testing of the future which are not covered in that
test case document. Also it is intended to perform GUI testing which may involve the
cosmotic issues.
TCD (Test Case Document):
Test Case Document Contains
      Test Scope (or) Test objective
      Test Scenario
      Test Procedure
      Test case


   Test Cases:
   Guidelines for Test Cases:
   1. GUI Test Cases:
      Total no of features that need to be check
      Look & Feel
   Look for Default values if at all any (date & Time, if at all any require)
   Look for spell check
Example for GUI Test cases:
T.C.No            Description               Expected value            Actual       Result
                                                                      value
                  Check for all the         The       screen    must 40            Correct
1                 features in the screen contain all the features features         outcome
                  Check for the             The alignment should      Right        Correct
2                 alignment of the          be in proper way                       Outcome
                  objects as per the
                  validations


2. Positive Test Cases:
   The positive flow of the functionality must be considered
   Valid inputs must be used for testing
   Must have the positive perception to verify whether the requirements are justified.
Example for Positive Test cases:


T.C.No            Description          Expected value Actual value            Result
1                 Check for the        The date and       Displayed           Correct outcome
                  date Time Auto time of the              correctly
                  Display              system must be
                                       displayed
2                 Enter the valid      It should accept Accepted              Correct outcome
                  Roll no into the
                  student roll no
                  field


3. Negative Test Cases:
   Must have negative perception.
   Invalid inputs must be used for test.
   Example for Negative Test cases:
  T.C.No           Description         Expected value Actual value     Result
  1                Try to modify The Modification       Cannot Modify Correct Outcome
                   information in      should not be
                   date and time       allow
  2                Enter invalid data It should not     Not Accepted   Correct Outcome
                   in to the student   accept invalid
                   details form, click data, save
                   on save             should not
                                       allow

Test Cases 1
13. SCREENS
14. REPORTS

Corporate Recruitment Management system is helpful for the job providers i.e.
companies which are in need of employees, job seekers who are in need of job, (for both
Exp and freshers). This portals main aim is to provide the vacancies available for the job
seekers without taking any charge from them in IT technologies.CRS will automatically
send mails to all job seekers whose skills are matched with the requirement.

Features :

• This project can be used very easily in the process of decision making in new
recruitments.
• Effective way of providing communication between job providers and job seekers.
• Reliable and consistent way of searching jobs.
• Conducting secured and restricted online exam for screened employees.
• Sending Email notification to all job seekers.

Corporate recruitment system offers significant cost savings for employers and reduces
the time taken to fill vacancies.(But most are worry of missing out on potential
candidates by using the internet to exclusion of all other media).Traditional recruitment
advertising is therefore set to retain an important role particularly when recruiting locally
(or) for head-to-fill jobs.Many organizations have found a considered combination of
both online and traditional approaches maximize their chances of securing the best
candidate.

       An corporate recruitment system presence shows organizations to be forward
thinking and therefore more attractive to potential employees for candidates, corporate
recruitment system offers great flexibility and case of access to job searches.

       To provide recruitment services through internet for graduates.

       This project generally deals with providing for job seekers through this system.
The graduates can easily get contact with the organization. At the same time it makes
easy for company to get an employee. For this purpose initially both employers and
graduates have to register on this website.

        When graduates register this website they have to give their complete personal
details and skills they possess. Thus a resume is generated by this details that is seen by
company. In the same way the companies have to give complete details of jobs they are
providing. By this the employee and job seeker can communicate with each other.

        Thus this project plays an important role for recruiting of employees. The
companies can access even remote areas of the country. It also give good opportunity for
the freshly graduates to access the information about the organization. Thus this project
satisfies both graduates and employees.
SCOPE OF THE PROJECT:

1.   To ensure portability and therefore compatibility.

2. To ensure our system moves with time i.e. allow for maintenance, upgrades and
periodic back ups by developed and authorized personnel.
15. CONCLUSION


Corporate Recruitment System (CRS) is a web based Recruitment System that helps
Human Resources departments of organization find that right talent for their manpower
requirements while optimizing the recruitment process and minimizing the recruitment
costs. RS, which is the core system of E-Recruitment, provides a single point interface
and globally accessible workplace for interaction between the HR department of a
company and candidates who apply for job position directly through an Intranet /
Extranet.

CRS provides all the functionality required by HR departments of organizations to post
resource requirements, screen and shortlist candidates, schedule and track online tests and
interviews all through an easy to use web based interface, without capturing the relevant
information in its database, capture, process and analyses information about potential
candidates. RS also serves as a tool that helps HR or Recruitment Managers pay personal
attention to each applicant.




16. BIBLIOGRAPHY
   1. System Analysis And Design
                              -   Lee
   2. An Analysis and Design of Information Systems
                              -   James. A. Senn
   3. Software Engineering
                              - Roger. S. Pressman
   4. Database Management System
                              - William. S. Robert

								
To top