automated cool avenues

7/30/2019 automated cool avenues

1/49

Introduction

The main objective of this application is to make the recruitment process easy for any organization.

Through this application job seekers can register their details like skills and experience with the system;

on the other hand it allows job providers to post their requirements with the system. Effective way of

providing communication between Job providers and job seekers

1.2 Purpose of the project

Its purpose is to develop a common platform for both job providers and job seekers. So both ofthem can get registered here and can interact with each other to satisfy their requirements.

1.3. Objective of the project

In current market lot of job portals are existed physically as outlets and in online also. They are

providing different interfaces to job seekers as well as job providers to access these portals. By using

these portals either job providers or job seekers can post the jobs for searching right candidates and also

post resumes for searching right job respectively.

1.4. Limitations of the project

The limitations of the project are it cannot perform all operations which the tools performs and it

cannot perform all the files which are other than the format. This project mainly runs using the tomcat

server if the tomcat fails it doesnt works. This graphical user interface is connected with the database

using jdbc thus initially java, oracle and tomcat must be installed first if any of it fails it doesnt executes

1


2/49

2.1 Introduction

Literature survey is the documentation of a comprehensive review of the published and unpublished

work from secondary sources data in the areas of specific interest to researcher. This is an another job

portal with an open environment for the jobseekers and recruiters to meet on the same dais and know

about each other so that the right candidate is placed in a right company. The aim of job portal is

facilitate both the candidates seeking jobs as well as the employers looking for employees for their

companies. In this online application, any job seeker can search for the available jobs at any moment

with update information. When he finds a job, he can post his application to the job online.

2.2 Existing System

In current market lot of job portals are existed physically as outlets and in online also. They are

providing different interfaces to job seekers as well as job providers to access these portals. By using

these portals either job providers or job seekers can post the jobs for searching right candidates and also

post resumes for searching right job respectively.

2.3 Disadvantages of Existing system

But organizations (job providers) are not providing any online test to the candidates as for the first

round of interview section.

This disadvantage will be overcome by using a special web portal called automated cool

avenues.

2.4 PROPOSED SYSTEM

Automated Cool Avenues is a web-based tool to reduce communication gap betweenJob providers and job seekers. Especially in fast growing IT market technologies are changing very fast,

based on technology trend Organizations has to recruit the people. This process will make recruitment

process very easy and fast.

2


3/49

2.5 Conclusion

Automated Cool Avenues is a web-based tool to reduce communication gap between

Job providers and job seekers. Especially in fast growing IT market technologies are changing very fast,based on technology trend Organizations has to recruit the people. They are providing different

interfaces to job seekers as well as job providers to access these portals. By using these portals either job

providers or job seekers can post the jobs for searching right candidates and also post resumes for

searching right job respectively. This process will make recruitment process very easy and fast.

3


4/49

3.1 Introduction

After analyzing the requirements of the task to be performed, the next step is to analyze the

problem and understand its context. The first activity in the phase is studying the existing system

and other is to understand the requirements and domain of the new system. Both the activities are

equally important but the first activity serves as a basics of giving the functional specifications and

then successful design of the proposed system. Understanding the properties and requirements of a new

system is more difficult and requires creative thinking as well as understanding of existing system is also

difficult. Improper understanding of present system can lead diversion from solution.

3.2 Software Requirement Specification

The application consists following modules

1. Job Provider Module

2. Job Seeker Module

3. Online Test Module

4. Reports Module

1. Job Provider Module:

This Module is all about a job provider who provides jobs to users. Any user who maintains a

separate organization can register in this portal and they can search for the right candidates for any

employment in that organization based on their requirement and they are having full rights to shortlist a

candidate for the online test based on their requirement and also they can add, modify, delete and view

not only jobs but also questions for online test.

Add jobs:By using this functionality job provider can add different jobs to the portal on variousskill set.

4


5/49

Update jobs: By using this functionality job provider can update all jobs in the portal based on

changing requirement of jobs.

Delete jobs: By using this functionality job provider can delete all jobs which exist in this portal if

the last date of apply is over.

View jobs: By using this functionality job provider can view all jobs which are given by him.

Add Questions: By using this functionality job provider can add different questions to the portal

for online test.

Update Questions: By using this functionality job providers can update all questions based on

their requirement.

Delete Questions: By using this functionality job providers can delete all questions based on their

requirement.

View Questions: By using this functionality job providers can view all questions which are given

by them existing in this portal.

Resume Processing: By using this functionality job providers can accept/reject resumes (for short

listing candidates)

Search: By using this functionality job providers can search all details about jobs in this portal.

Messages: By using this functionality job providers can view all feedback messages from

different users.

2. Job Seeker Module:

This module is all about job seekers who are searching jobs which are available in other

organizations through this portal. By using this module any user can register in this portal to search for a

job, if their resume is short listed they will under go for an online test and also job seeker can view all

jobs but he/she cant modify them.

Following are the functionalities of both job seeker and job provider.

Inbox: By using this functionality job seeker can view all messages which are from job provider

regarding online test.

5


6/49

Post Resume: By using this functionality job seekers can post their resumes to the job provider for

applying jobs.

Update Resume: By using this functionality job seeker can update their resumes which are posted

in this portal.

Change Personal Information: By using this functionality job seeker can not only view but also

update their personal information.

Change Password: By using this functionality job seekers can change their password.

Feedback: By using this functionality job seeker can send feedback to all job providers.

View Jobs: By using this functionality job seeker can view all jobs which are provided in this job

portal by all job providers.

Registration of Job Seekers and Job Providers:

System supports a facility of registering both parties like job providers and seekers. Both must be

registered in this portal and they must use login id and password for further transactions.

Advanced Search option for Job Providers and job seekers:

System will allow the Job providers to search from database for Suitable candidate for a positionbased on skill set and experience and also it sends intimation to suitable candidates through mail. A set

of reporting system is supported to the system for the immediate specific need of the organization by

different parameters. At the same time job seeker can search for a suitable job through this portal.

Sending Mails automatically to all suitable jobseekers:

Once Job providers posts their required jobs in this system then PRS sends automatic mails to all

registered job seekers with employment details, details of the job codes and the job providers details and

the number of posing etc. as well the job provider is forwarded with the matching profile of the job

seekers.

3. Online Test Module:

This module will provide a facility of conducting online test for selected candidates. And also it

prepares reports based on the results of the online test. Test can be random basis from the aptitude or

6


7/49

technical or HR questions; this is the option with the job provider to decide on the matter of the test. The

job provider will provide a password to the job seeker for attempting the test on line.

4. Reports Module:

PRS will allow job providers to generate reports based on criterias like based on technology, location,

education qualification, project experience and any specific experience.

3.2.1 Performancerequirements

Performance is measured in terms of the output provided by the application. Requirement

specification plays an important part in the analysis of a system. Only when the requirement

specifications are properly given, it is possible to design a system, which will fit into required

environment. This is because the requirements have to be known during the initial stages so that the

system can be designed according to those requirements.

The requirement specification for any system can be broadly stated as given below:

The system should be able to interface with the existing system

The system should be accurate

The system should be better than the existing system

The existing system is completely dependent on the user to perform all the duties.

3.2.2 Software requirements

Operating System : Windows

Technology : Java/j2ee (JDBC, Servlets, JSP)

Web Technologies : Html, JavaScript, CSS

Web Server : Tomcat

Database : Oracle

Softwares : J2SDK1.5, Tomcat 5.5, Oracle 9i

3.2.3Hardware requirements

7


8/49

Hardware : Pentium based systems with a minimum of P4

RAM : 256MB (minimum)

3.2.4 Additional Tools

HTML Designing : Dream weaver Tool

Development Tool kit : My Eclipse

3.3 System architecture

Below architecture diagram represents mainly flow of requests from users to database through

servers. In this scenario overall system is designed in three tires separately using three layers called

presentation layer, business logic layer and data link layer. This project was developed using 3-tire

architecture.

8

Server

User

DataBase

Request Response


9/49

3.3.1 3-tire architecture

9


10/49

URL Pattern

3.3.2 URL Pattern

URL pattern represents how the requests are flowing through one layer to another layer and how

the responses are getting by other layers to presentation layer through server in architecture diagram.

3.4 Conclusion

In this phase, we understand the software requirement specifications for the project. We arrange all

the required components to develop the project in this phase itself so that we will have a clear idea

regarding the requirements before designing the project. Thus we will proceed to the design phase

followed by the implementation phase of the project.

10

PresentationLayer

SERVLETS AT

THE SERVERSIDE

URL Request sent

through the browser

Response sent from the

servlet

DATABASE

Verifying or updating the

database through astatement

Reply from the

database according tothe statement


11/49

4.1 Introduction

Systems design is the process or art of defining the architecture, components, modules, interfaces

and data for a system to satisfy specifiedrequirements. One could see it as the application of systemstheory to product development. There is some overlap and synergy with the disciplines of systems

analysis, systems architecture and system engineering.

4.2 DATA FLOW DIAGRAMS

Data flow diagram will act as a graphical representation of the system in terms of interaction between

the system, external entities, and process and how data stored in certain location

Context Level DFD

The major objective of a context diagram is to provide a graphical representation of the whole

system. As I stated earlier it consists of all the system boundaries, all the external entities that interact

with the system and major data flow between the entities in the system. Refer to the following diagram.

Online AdministrationScheduling Registration

Summary Scheduling

Search Tutorials Session

For jobs

Search results

Fig.4.2.1 Context Level DFD

11

Job Provider

Job

Seeker

Online

Test

0

Online Job Access


12/49

D3 Job seeker D2 job provider

Seeker Details Provider Details

Admin Login info

Job seeker Login info

Search Results

Search Jobs

D4 Online Test

Seeker

Details Online test questions

Search Details

Seeker summary

D2 Provider file

Fig. 4.2.2 Level-0 Data Flow

12

Login

Authentication

DisplayProvider

Main Page

Display jobseeker Page

Job seekers

Adding jobs&

Questions

AccountManipulation

AccountUpdating

Online

testMessage

from

Provider

Update

Sendingmessage to

seeker

Login

Providers


13/49

Provider Details

Provider DetailsUpdate Provider

File

D1 Provider Details

Provider Details

Fig.4.2.3 level 1 job Provider

13

6.1

Account Updating

6.3

UpdateRecord

6.2

View Providerinformation

Job Provider


14/49

Figure 3.5 shows the locus on viewing the actual tutorial and learning environment. In this process, once the user has chosen their respective session, they

will be directed to a learning environment for that particular session. The session details will be accessed from session file.

Online Test

D4 Online testFile

Fig.4.2.4 Level 1 Active Session.

14

7.1

Message from

job provider to

job seeker

7.2

Online test


15/49

User details

Summary

D4 Session File

User Info

User Details

Fig. 4.2.5 Level 1 Register Session

4.3 UML DIAGRAMS

Unified Modeling Language:

15

8.1

Register

Session

8.2

Display User

Summary

User Details


16/49

The Unified Modeling Language allows the software engineer to express an analysis model using the

modeling notation that is governed by a set of syntactic semantic and pragmatic rules.

A UML system is represented using five different views that describe the system from distinctlydifferent perspective. Each view is defined by a set of diagram, which is as follows.

User Model View:

i. This view represents the system from the users perspective.

ii. The analysis representation describes a usage scenario from the end-users

perspective.

Structural model view:

i. In this model the data and functionality are arrived from inside the system.

ii. This model view models the static structures.

Behavioral Model View: It represents the dynamic of behavioral as parts of the system

depicting the interactions of collection between various structural elements described in

the user model and structural model view.

Implementation Model View: In this the structural and behavioral as parts of the system

are represented as they are to be built.

Environmental Model View: In this the structural and behavioral aspects of the

environment in which the system is to be implemented are represented.

UML is specifically constructed through two different domains they are:

UML Analysis modeling, this focuses on the user model and structural model views of the

system.

UML design modeling, which focuses on the behavioral modeling, implementation modeling

and environmental model views.

UML DIAGRAMS

16


17/49

USE-Case Diagram

Fig.4.3.1 UML Use-case diagram

Class Diagram

17


18/49

Fig.4.3.2 UML Class diagram

Sequence Diagram for Job seeker

18


19/49

Sequence Diagram for Job seeker

19


20/49

Fig.4.3.3 UML Sequence diagram for Job seeker

Sequence Diagram for Job Provider

20


21/49

Fig.4.3.4 UML Sequence diagram for Job Provider

State Diagram for Job seeker

21


22/49

Fig.4.3.5 UML State diagram for job seeker

State Diagram for Job Provider

22


23/49

Fig.4.3.6 UML State diagram for job provider

4.4 E-R DIAGRAMS

23


24/49

Fig.4.4.1 E-R diagram

4.5 Conclusion

24


25/49

In this way we can design the layout of the project which is to be implemented during the

construction phase. Thus we will have a clear picture of the project before being coded. Hence any

necessary enhancements can be made during this phase and coding can be started

5.1 Introduction

25


26/49

The implementation part is the most important phase of the project. In this phase, we code the

entire project in the chosen software according to the design laid during laid during the previous phase.

The code has to be in such a way that the user requirements are satisfied and also not complicated for the

user i.e., the user interface or GUI has to be easy to navigate. The code should be efficient in all terms

like space, easy to update, etc. In this manner, we can complete the coding part of the project and later it

can be sent for testing before being delivered to the customer.

5.2 Explanation of key function

login:

Welcome To Login

function valid(ThisForm)

{

if(ThisForm.uname.value==""){

alert("Enter Login id") ;

ThisForm.uname.focus();

return false;

}

if(ThisForm.password.value=="")

{

alert("Enter password");

return false;

}

}

26


27/49

&nbsp

;

Welcome To Jobprovider Login !

&n

bsp; Login ID

27


28/49

Password

28


29/49

If New User Click

Here


30/49

ThanQ

for Using this Site.... if

u want to Relogin ?

30


31/49

5.3 Method of implementation

5.3.1 Forms

NORMALIZATION

Normalization is built around the concept of normal forms. A relation is said to be in a particular

normal form if it satisfies a certain specified set of constraints on the kind of functional dependencies

that could be associated with the relation. The normal forms are used to ensure that various types of

anomalies and inconsistencies are not introduced into the database.

First Normal Form:

A relation R is in first normal form if and only if all underlying domains contained atomic values onl

Second Normal Form:

A relation R is said to be in second normal form if and only if it is in first normal form

and every non-key attribute is fully dependent on the primary key.

Third Normal Form:

A relation R is said to be in third normal form if and only if it is in second normal form

and every non key attribute is non transitively depend on the primary key.

31


32/49

5.3.2 Output screens

The above screen represents the home page

32


33/49

The above screenshot shows the jobseeker registration form

33


34/49

This screen shows after the registration form submitted

34


35/49

This screenshot shows the new jobprovider registration page

35


36/49

The above screen shows after the job provider registration page submitted

36


37/49

The above screen shows test queries for the job seeker

37


38/49

The above screen shows the feedback from users

38


39/49

The above screen represents the searching of jobs through experience

39


40/49

The above screen represents the logout page

40


41/49

5.3.3 Result analysis

This project has been implemented for several users where it allows us to perform maximum

operations. Thus using this automated cool avenues we can easily register for jobs and we can easily

post the resumes through this portal.

5.4 Conclusion

In this way we implemented the project successfully with the help of Java for an easy interaction

for the developers. We proceed to the next phase i.e.; testing which is very important before delivering

the project.

6.1 INTRODUCTION TO TESTING

41


42/49

Testing is a process, which reveals errors in the program. It is the major quality measure

employed during software development. During testing, the program is executed with a set of test cases

and the output of the program for the test cases is evaluated to determine if the program is performing as

it is expected to perform.

6.2 Design of test cases and scenarios

In order to make sure that the system does not have errors, the different levels of testing that are

applied at differing phases of software development are:

Unit Testing

Unit Testing is done on individual modules as they are completed and become executable. It is

confined only to the designer's requirements.

Each module can be tested using the following two Strategies:

Black Box Testing

In this strategy some test cases are generated as input conditions that fully execute all

functional requirements for the program. This testing has been uses to find errors in the following

categories:

correct or missing functions

Interface errors

Errors in data structure or external database access

Performance errors

Initialization and termination errors.

In this testing only the output is checked for correctness.

The logical flow of the data is not checked.

42


43/49

White Box testing

In this the test cases are generated on the logic of each module by drawing flow graphs of that

module and logical decisions are tested on all the cases. It has been uses to generate the test cases in

the following cases:

Guarantee that all independent paths have been Executed.

Execute all logical decisions on their true and false Sides.

Execute all loops at their boundaries and within their operational bounds

Execute internal data structures to ensure their validity.

Integrating Testing

Integration testing ensures that software and subsystems work together a whole. It tests the

interface of all the modules to make sure that the modules behave properly when integrated

together.

System Testing

Involves in-house testing of the entire system before delivery to the user. It's aim is to satisfy the

user the system meets all requirements of the client's specifications.

Acceptance Testing

It is a pre-delivery testing in which entire system is tested at client's site on real world data to find

errors.

Test Approach

Testing can be done in two ways

43


44/49

Bottom up approach

Top down approach

Bottom up Approach

Testing can be performed starting from smallest and lowest level modules and proceeding

one at a time. For each module in bottom up testing a short program executes the module and

provides the needed data so that the module is asked to perform the way it will when embedded with

in the larger system. When bottom level modules are tested attention turns to those on the next level

that use the lower level ones they are tested individually and then linked with the previously

examined lower level modules.

Top down approach

This type of testing starts from upper level modules. Since the detailed activities usually

performed in the lower level routines are not provided stubs are written. A stub is a module shell

called by upper level module and that when reached properly will return a message to the calling

module indicating that proper interaction occurred. No attempt is made to verify the correctness of

the lower level module.

Testing

The system test cases mentioned below are expected to work and give the expected behavior if the

explorer is configured to run jar files as mentioned in the project folder. The necessary library files

and standard jar files are in the appropriate project directories and the path and class path

environment variables are appropriately set.

44


45/49

Test

C.N

o.

Testcase

descriptio

n

Expected ResultsActual

Results

Result

P = Passed

F = Failed

1

Login as a Job

provider with

correct login

details

Job provider Home

page for manager

should be displayed

-do- P

2

Login as manager

with wrong login

details

Error message should

be displayed

-do- P

3

Add a New Entry

for an User

It should add a new

record in the database

with new user details -do- P

4

Delete Entry It should delete an

existing user from the

database

-do- P

5

View the list of

users

It should display the

list of current availableusers

-do-

P

6

Sim sales Details

entry form

It should display an

entry form -do- P

45


46/49

7 Easy refilling

form


form with outlet name

and recharge amount

-do- P

8

Paper card sales

form

It should display a form

with plan name, outlet

name, number of cards.

-do- P

9

Reports


repots menu

-do- P

10 Login as Operator It should display

operator home page -do- P

11 Subscriber

Details entry form


subscriber form -do- P

12

Stock details

entry form


stock details entry

process form

-do- P

6.3 Validation

46


47/49

The system has been tested and implemented successfully and thus ensured that all the

requirements as listed in the software requirements specification are completely fulfilled. In case of

erroneous input corresponding error messages are displayed

6.4 Conclusion

In this way we also completed the testing phase of the project and ensured that the system is

ready to give to the customer.

7. Conclusion

47


48/49

Automated Cool Avenues is a web-based tool to reduce communication gap between

Job providers and job seekers. Especially in fast growing IT market technologies are changing very fast,

based on technology trend Organizations has to recruit the people. This process will make recruitment

process very easy and fast.Through this application job seekers can register their details like skills and

experience with the system; on the other hand it allows job providers to post their requirements with the

system. Effective way of providing communication between Job providers and job seekers

Future Enhancement

In future we can enhance our project by providing options like, include many site information.This system can be implemented for online transactions without the intervention of the authority. If it is

done so, the employer can post a job and jobseeker can search for a job from anywhere in the world. He

can apply for the required job without wastage of time. In other words the future scope is to provide the

service over the internet.

48


49/49

References for the Projec t Development Were Taken From the fo l lowing Books

and Web Si t es .

JAVA Complete Reference By Patric Naughton

Java Script Programming by Yehuda Shiran

Mastering JAVA Security By Johennie helton,Rich helton

JAVA2 Networking By Pistoria

JAVA Security By Scotl oaks

Head First EJB By Sierra Bates

J2EE Professional by Shadab siddiqui

JAVA server pages by Larne Pekowsley

JAVA Server pages by Nick Todd

Core Java2 Volume I Fundamentals; SunSoft Press; S. Horstmann & Gary Cornell

Core Java2 Volume II Advanced Features SunSoft Press; S. Horstmann & Gary Cornell

HTML Black Book by Holzner

Java Database Programming with JDBC by Patel moss.

System Analysis And Design By James A.senn

Software Engineering by Roger Pressman

Documents

automated cool avenues