1.

Introduction

1.1 Purpose

Recruitment Cell is a web application. One can access this application from anywhere
and it’s a 24x7 application i.e. it will be accessible at any time. This system can be
used to manage all the activities related to recruitments. The activities include
managing the student details required at the time of recruitment, time to time
maintenance and updation of the student’s results, contacting companies who are
interested in doing recruitments in the college, preparing databases according to a
particular company requirement etc.

1.2 Project Scope

This application can be accessed from any part of the world and at any time that is
convenient to user.

1.3 Existing System

The first problem is that there are loads of hard copied documents being generated.
This brings us to the age-old discussion of keeping information in the form databases
versus keeping the same on sheets of paper. Following problems exist in the existing
system:

1. Lack of space – It becomes a problem in itself to find space to keep the sheets of
paper being generated as a result of the ongoing discussion. The documents being
generated are too important to be ill-treated.

2. Redundancy – The same student record can be taken multiple times.

3. Filing poses a problem – Filing the documents categorically is a time consuming

and tedious exercise.

4. Filtering is not easy – It becomes hard to filter relevant documents or irrelevant

ones if the count of the same crosses a certain manageable number. It is also not easy
to keep check on number of students who are eligible for certain and who are not.

5. Reviewing becomes time consuming – All the process done manually at the
centers. So the maintenance of the record is very difficult in the departments and as
well as it’s very difficult for the workers to check the record.

6. Result processing is time consuming – Students are also sometimes not able to

1
get the results or have to wait a lot for the results. Through this software student can
view result as soon as it is declared.

1.4 Proposed System

To solve the problems of existing system, we require a computerized system to handle

all the works. They required a web based application that will provide a working
environment that will be flexible and will provide ease of work and will reduce the
time for report generation and other paper works.

The main purpose behind the proposed system is to provide a comprehensive

computerized system, which can capture, collate and analyze the data from these
wards and evaluate the impact of the program.

The proposed system would be an electronic process and will involve less labour and
will also perform the activities in a much organized way.

Some features of proposed system over the existing one:-

1. It will be an electronic process.

2. The data about students and recruitments details will be maintained and stored
in databases in an organized way which can be retrieved at any point of time

3. Less labour will be needed to manage the whole process

4. It will reduce the time needed to perform certain activities which would have
taken a lot of time if performed manually for eg. Preparing database of
students according to a particular company demand

5. Back up will be provided

6. Searching the records will become much more easier than the manual one

1.5 Abbreviations

1. HTML: Hypertext Markup Language is a markup language used to design

static web Pages.

2. J2EE: Java 2 Enterprise Edition is a programming platform— part of the Java

Platform—for developing and running distributed multitier architecture Java
applications, based largely on modular software components running on an
application server.

2
 3. JSP: Java Server Pages (JSP) is a Java technology that helps software
developers serve dynamically generated web pages based on HTML, XML, or
other document types. Architecturally, JSP may be viewed as a high-level
abstraction of Java servlets. JSP allows Java code and certain pre-defined
actions to be interleaved with static web markup content, with the resulting
page being compiled and executed on the server to deliver an HTML or XML
document.

4. MS ACCESS: MS ACCESS Database is the database management system

that is provided by Microsoft itself. It offers flexibility and easy of connecting
and maintaining data.

5. APACHE TOMCAT 6.0: Tomcat server is an application server that runs

business applications and supports the J2EE and web services standards.

6. HTTP: Hypertext Transfer Protocol is a transaction oriented client/server

protocol between web browser & a Web Server.

7. HTTPS: Secure Hypertext Transfer Protocol.

8. TCP/IP: Network protocols for packet data communication, routing.

1.6 Technologies

• JSP: Application Architecture

• MS ACCESS: Database

1.7 References

• IEEE SRS Format

• MDSU, ajmer(central library)

• DBMS book by Raghu Ramakrishnan

• DBMS book by Korth

3
2. Overall Description

2.1 Product Perspective

Figure 1: System Architecture

2.2 Product Features

1. Service Level Agreement

It contains the agreements of priority, the service related to software provided to

an instruction.

2. Maintaining Logins

The system will maintain the login information about users.

3. User Rights

Different powers are given to different users.

4. Other Features

• Manpower is reduced in this proposed system as it is an electronic process

that will require less manpower.

• The system would consume less time in maintaining the recruitment

details.

4
 • The system would be more efficient as it would be less prone to errors as it
does not include manual data management.

• The system would be more economical since it involves only one time
installation cost of software is involved.

2.3 Operating Environment

This application would support the following operating environments:-

Windows 95/97/98/2000/ME/XP

2.4 Constraints

1. GUI is only in English.

2. User can login only with his assigned username and password i.e. no guest
facility is available.
3. Limited to HTTP/HTTPS.

3. System Features

3.1 Detailed description of project

This system will manage recruitment details for various users. Recruitment cell is the
project which will ease the process of recruitments at college level. The main idea
behind this project is to manage the recruiting process at a much ease and efficient
level without involving extra unnecessary activities.

This proposed system will manage the login details, based on which various
privileges will be provided to various users.

The proposed system will have 4 types of users involved:-

1. Administrator

2. Students

3. Companies

4. Other users visiting the site

Administrator would be responsible for running the proposed system efficiently. He

would have all the authorities regarding the operations that can be performed using
the proposed system. He would add notifications that will be reflected on the home
page of the site and also in every student’s personal account. He can prepare the

5
database for every company that approaches the college or the companies whom the
college approaches. Similarly other various authorities would be provided solely to
him.

Students will have their personal accounts on the site and can view the notifications
issued by the administrator at any point of time after logging in. They will have the
authority to upgrade their academic results as when the results are declared. They can
edit their records in case of reevaluation. They can view the upcoming companies
schedule, details etc.

Companies can visit the site and can get an idea of previous recruitments done in the
college and can search for the required candidates. The company can leave its details
on the visit to the site which will give the administrator and college authority to
approach that company personally and welcome it to their college for recruitments.

Other arbitrarily users involving the teachers of the college can only visit the home
page of the site and can get an idea of the processes going on for the recruitments by
seeing the notifications issued by administrator which will be self explanatory. For
more details the contact us page can be invoked and they can approach the concerned
authority of the college.

4. External Interface Requirements

4.1 Software Interface

Client on internet: Client software, web browser, operating system (any)

Web Server: Apache Tomcat, operating system (any)

Database Server: MS ACCESS, operating system (any)

Development End: J2EE, Java, JSP, HTML, MS ACCESS, operating system

(windows), web server

4.2 Hardware Interface

• At Client

Processor: Pentium II or later version

RAM: 256 MB or greater

Disk Space: 250 MB or greater

6
 Browser: Internet Explorer 6.0 or higher version

• At Server

Processor: Pentium III or later version

RAM: 512 MB or greater

Disk Space: 2GB or greater (as required according to requirement)

Database: MS ACCESS

4.3 Communication Interface

Client on Internet will be using TCP/IP protocol. The system should be accessed over
LAN or WAN. For Clients to access application server the network should be running
TCP/IP protocol.

Client Side

Interactive operations using options provided in the application, Example Data Entry
generation and viewing of reports.

Server Side

Database backup should be taken every day. In case of data base crash, last backup
should be restored.

5. Other Non-Functional Requirements

5.1 Performance Requirements

• Constraints of the Internet & Intranet will be applicable to the system.

• The performance of the system will be dependent on the network conditions

like network congestion, bandwidth etc.

• The primary memory (RAM) and the secondary memory (Hard Disk Space)
requirement of the system at the client end will be the same as that required by
the web browser and the operating system.

• At the server end memory requirements will be that of the server software
(Operating system, Database Software, etc) and the space required to store the
data.

7
 • The space required to store the data would increase as more and more records
are added to the system.

5.2 Safety Requirements

This system will not take care of any virus problem, which might occur either on the
client or the server system. Avoiding the use of pirated software and ensuring that
suspected files and the removable media are scanned for viruses before use could
minimize the possibility of viral infection.

Backups are needed to be maintained to recover the data in case of system crash.

5.3 Security Requirements

• To provide security and confidentiality to a user about his personal data,

authentication has to be done.

• User will be authenticated by the use of login id and password.

5.4 Software Quality Attributes

• Fast service: - It can give the fast service (test taking, result analyzing etc.) to
the users of the system.
• Reduces the workload: All the tasks are done by the automated
system/machine which greatly reduces the burden on the person managing the
data.
• Good management: The system provides the good management in the
management of data. Everything can be managed in a quicker way.
• Provide satisfaction to the users: As the users are taking test according to
their convenience in terms of time and place, the major advantage of this
system, and getting the results immediately followed by test, so they are
completely satisfied because the system fulfils their need and requirements of
accuracy, ease and speed.
• Able to maintain the question bank more efficiently: The system is able to
maintain the question bank of each subject separately and in an orderly
manner which makes it more efficient and effective as compared to the manual
process of maintaining and storing the data.
• Remove complexity in the operations: The system provides the real life
features to provide the service. The underlying complexities of the various

8
 processes generation are all hidden from the user. Hence complexity is
removed at the user end.
• Provide flexibility in organizing the test: A wide variety of different tests
can be generated and presented to the user which overcomes the overhead of
organizing the test papers manually. The test generation process is automated
one i.e. the test will be automatically prepared by the system with equal ratio
of easy, medium and difficult type questions.

6. Feasibility Study

The main objective of the feasibility study is to treat the technical, Operational,
logical and economic feasibility of developing the computerized system. All systems
are feasible, given unlimited resources and infinite time. It is both necessary and
prudent to evaluate the feasibility of the project at System study phase itself. The
feasibility study to be conducted for the project involves:-

• Technical Feasibility

• Operational Feasibility

• Economic Feasibility

• Legal Feasibility

6.1 Technical Feasibility

Technical feasibility includes Risk Resources availability and technologies. The

management provides latest hardware and software facilities for the successful
completion of the projects. With the latest hardware and software support the system
will perform extremely well. The proposed system is available through Internet.

Tools used in developing the system are:

HTML, SQL, JAVA, JSP and MS ACCESS (Database)

6.2 Operational Feasibility

In the existing manual system it is very difficult to maintain and update huge amount
of information. The development of the system was started because of the

9
requirement to automate the exam/test taking process. This system will handle the
request in a better way and make the process easier thus, it is sure that the system
developed is operationally feasible.

6.3 Economic Feasibility

In the economic feasibility the development cost of the system is evaluated weighing
it against the ultimate benefit derived from the new system. The proposed system’s
benefit would surely be more than the cost and time involved in its development.

6.4 Legal Feasibility

In the legal feasibility it is necessary to check that the software we are going to
develop is legally correct which means that the ideas taken for the system will be
legally implemented or not. The proposed system is legally feasible as it abides all
the legal rules.

7. Low Level Design

7.1 Use Case Diagram

The users of this system can be:-

• Administrator

• Student

• Company

The various functions performed by each type of user are shown via use case
diagrams of each type of user.

10
Figure 2: Use Case Diagram of Administrator

11
Figure 3: Use Case Diagram of Student

12
Figure 4: Use Case Diagram of Company

13
7.2 Entity Relationship Diagram (E-R Diagram)

Figure 5: Entity Relationship Diagram

14
7.3 Data Flow Diagram

Figure 6: Data Flow Diagram

15